[Kernel-packages] [Bug 1882439] Re: Power down and restart after shut down doesn't work.
[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/1882439 Title: Power down and restart after shut down doesn't work. Status in linux package in Ubuntu: Expired Bug description: It only works with hard shutdown. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dordom 953 F pulseaudio /dev/snd/controlC0: dordom 953 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (66 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 MachineType: LENOVO 81N6 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=b6af4cf2-3243-4b15-81ef-1b166a90e68b ro quiet splash ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-48-generic N/A linux-backports-modules-5.8.0-48-generic N/A linux-firmware1.187.10 Tags: ulyssa Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/08/2020 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: AGCN27WW(V1.10) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad C340-14API dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrAGCN27WW(V1.10):bd07/08/2020:br1.27:efr1.27:svnLENOVO:pn81N6:pvrLenovoIdeaPadC340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadC340-14API: dmi.product.family: IdeaPad C340-14API dmi.product.name: 81N6 dmi.product.sku: LENOVO_MT_81N6_BU_idea_FM_IdeaPad C340-14API dmi.product.version: Lenovo IdeaPad C340-14API dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873334] Re: Secondary HDD hard drive spin down abruptly when shutting down or restarting
[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/1873334 Title: Secondary HDD hard drive spin down abruptly when shutting down or restarting Status in linux package in Ubuntu: Expired Bug description: I have recently replaced the main HDD of my ASUS a53s laptop with an SSD. I have placed the HDD hard drive in the SATA port where the DVD drive was located. I have not had any problems and the speed of my system has increased a lot. However, I have noticed that every time I turn off the system, a click of the needle of the HDD hard disk sounds, as if it were turned off suddenly (this did not happen when it was placed in the main SATA port). Could you do some configuration in Ubuntu to avoid this? Thank you very much. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907416] Re: skype microphone problem after suspend
[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/1907416 Title: skype microphone problem after suspend Status in linux package in Ubuntu: Expired Bug description: skype microphone problem after suspend. After suspend I need to restart skype, because microphone of skype not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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.1104.107)
All autopkgtests for the newly accepted linux-meta-snapdragon (4.15.0.1104.107) 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 1929147] Re: fix system hang with 5.10 kernel + RX540 on RKL platform
** Changed in: linux-firmware (Ubuntu) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Hirsute) Importance: Undecided => High -- 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/1929147 Title: fix system hang with 5.10 kernel + RX540 on RKL platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Hirsute: Fix Committed Bug description: [Impact] On RKL platform with AMD RX540, system would hang during boot-up. [Fix] AMD introduce a brand new firmware, polaris 12 MC firmware. This fix the issue and the system wouldn't hang during boot-up with AMD RX540. [Test] Verified on RKL platform and AMD RX540 System would boot-up and login to desktop successfully. [Where problems could occur] This's a brand new firmware to support Polaris-series, it may introduce new issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1929147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926236] Re: Fix The sound has noise while audio volume is maximum
linux-firmware (1.198) impish; urgency=medium * Rebase against git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git f8462923ed8fc874f770b8c6dfad49d39b381f14 - qcom: update a650 firmware files - qcom: sm8250: update remoteproc firmware - brcm: Add nvram for the Predia Basic tablet - brcm: Add nvram for the Chuwi Hi8 (CWI509) tablet - rtl_bt: Add rtl8723bs_config-OBDA0623.bin symlink - amdgpu: add arcturus firmware - nfp: update Agilio SmartNIC flower firmware to rev AOTC-2.14.A.6 - WHENCE: link to similar config file for rtl8821a support - QCA: Update Bluetooth firmware for QCA6174 - amdgpu: update navi10 SMC firmware - amdgpu: update navi14 smc firmware - linux-firmware: Update firmware file for Intel Bluetooth AX201 - brcm: Link CM4's WiFi firmware with DMI machine name. - Mellanox: Add new mlxsw_spectrum firmware xx.2008.2438 - cxgb4: Update firmware to revision 1.25.4.0 - rtl_nic: add new firmware for RTL8153 and RTL8156 series - amdgpu: update raven firmware from 21.10 - amdgpu: update raven2 firmware from 21.10 - amdgpu: update navi10 firmware from 21.10 - amdgpu: update renoir firmware from 21.10 - amdgpu: update vega10 firmware from 21.10 - amdgpu: update navi12 firmware from 21.10 - amdgpu: update vega12 firmware from 21.10 - amdgpu: update green sardine firmware from 21.10 - amdgpu: update navi14 firmware from 21.10 - amdgpu: update picasso firmware from 21.10 - amdgpu: update vega20 firmware from 21.10 - amdgpu: update sienna cichlid firmware from 21.10 - amdgpu: update navy flounder firmware from 21.10 - amdgpu: update arcturus firmware from 21.10 - brcm: add missing symlink for Pi Zero W NVRAM file - rtw88: 8822c: Update normal firmware to v9.9.9 - mrvl: prestera: Add Marvell Prestera Switchdev firmware 3.0 version - qcom: update venus firmware files for v5.4 - linux-firmware: Update firmware file for Intel Bluetooth 8265 - linux-firmware: Intel BT 7265: Fix Security Issues - 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 9260 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth AX210 - rtw89: 8852a: update fw to v0.13.8.0 - qcom: Add venus firmware files for VPU-2.0 - rtl_bt: Update RTL8852A BT USB firmware to 0xD9A8_7893 - rtw89: 8852a: update fw to v0.13.8.0 - brcm: Add a link to enable khadas VIM2's WiFi - qcom: add gpu firmwares for sc7280 - firmware: nvidia: Add VIC firmware for Tegra194 - amdgpu: add new polaris 12 MC firmware (LP: #1929147) - i915: Add ADL-P DMC Support - linux-firmware: update firmware for mhdp8546 - nvidia: Update Tegra210 XUSB firmware to v50.26 - nvidia: Update Tegra186 XUSB firmware to v55.18 - nvidia: Update Tegra194 XUSB firmware to v60.09 - iwlwifi: add new FWs from core60-51 release - iwlwifi: update 9000-family firmwares to core60-51 - iwlwifi: update 8000 family firmwares - rtw88: 8822c: Update normal firmware to v9.9.10 - nvidia: fix symlinks for tu104/tu106 acr unload firmware -- Seth Forshee Tue, 25 May 2021 08:35:16 -0500 ** Changed in: linux-firmware (Ubuntu) Status: New => Fix Released ** Changed in: linux-firmware (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-firmware (Ubuntu Focal) Importance: Undecided => Medium -- 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/1926236 Title: Fix The sound has noise while audio volume is maximum Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Bug description: [Impact] The sound has noise while turning the audio volume to maximum [Fix] For VEGA & Polaris, need two patches(landed on mainline kernel) to fix and a modprobe 1.(50ceb1fe7a) drm/amd/pm: bug fix for pcie dpm, has landed on oem kernel. 2.(9d03730ecb) drm/amd/pm: workaround for audio noise issue, has landed on oem kernel 3. #modprobe amdgpu ppfeaturemask=0xfff7bffb. For Navi_1x, need smc firmware to fix. 1. (4fe6e53b96 linux-firmware) amdgpu: update navi10 SMC firmware 1. (8ab7abaf63 linux-firmware) amdgpu: update navi14 SMC firmware [Test] Verified on RKL platform A. with wx3200(Polaris series) and the following configuration 1. With these two patch, 1.1. (50ceb1fe7a) drm/amd/pm: bug fix for pcie dpm, has landed on oem kernel. 1.2. (9d03730ecb) drm/amd/pm: workaround
[Kernel-packages] [Bug 1890641] Re: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169
** Changed in: linux-firmware (Ubuntu) Status: Invalid => Fix Released ** Changed in: linux-firmware (Ubuntu) Importance: Undecided => High -- 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/1890641 Title: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Released Bug description: [SRU Justification] [Impact] Missing firmware for Realtek RTL8153 Based USB Ethernet Adapters, which is supported by linux-generic-hwe-18.04 kernel (currently v5.4). [Fix] Two upstream commit necessary: * commit b27d12383e7a ("rtl_nic: add firmware files for RTL8153") * commit 6f89735800fe ("rtl_nic: update firmware for RTL8153A") [Test Case] Without firmware, drive probe would fail with: $ dmesg | grep firmware | grep rtl8153 r8152 2-4.1:1.0: firmware: failed to load rtl_nic/rtl8153a-2.fw (-2) r8152 2-4.1:1.0: Direct firmware load for rtl_nic/rtl8153a-2.fw failed with error -2 r8152 2-4.1:1.0: unable to load firmware patch rtl_nic/rtl8153a-2.fw (-2) With firmware, it should succeed: $ dmesg | grep rtl8152 r8152 2-1:1.0: load rtl8153a-3 v2 02/07/20 successfully r8152 2-1:1.0 eth0: v1.11.11 r8152 2-1:1.0 enp0s20f0u1: renamed from eth0 [Where problems could occur] While this introduces new firmware blobs and enabled devices supported by new kernels, it should have little effect on existing systems, but with new devices up and running, it may still affect power consumptions, ability to enter deep suspend, etc. [Other Info] RTL8153 firmware has been available on Eoan and newer, so only Bionic is nominated. == original bug report == Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169 after running sudo apt upgrade in ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 22:38:31 2020 InstallationDate: Installed on 2019-06-16 (417 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-03-08 22:54:00.439353 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1890641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930775] Re: package nvidia-dkms-465 465.27-0ubuntu0.20.04.2 failed to install/upgrade: installed nvidia-dkms-465 package post-installation script subprocess returned error exit
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/1930775 Title: package nvidia-dkms-465 465.27-0ubuntu0.20.04.2 failed to install/upgrade: installed nvidia-dkms-465 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-465 package in Ubuntu: Confirmed Bug description: I tried to install the graphics drivers for an nvidia graphics card on a 2021 ASUS scar 15 laptop with an amd ryzen processor and a 3070 graphics card. I tried to do it multiple times in multiple different ways; through the additional software GUI and through the terminal. Neither worked and threw up the prior mentioned error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-465 465.27-0ubuntu0.20.04.2 Uname: Linux 5.11.0-051100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jun 3 16:11:50 2021 ErrorMessage: installed nvidia-dkms-465 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-06-01 (2 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: nvidia-graphics-drivers-465 Title: package nvidia-dkms-465 465.27-0ubuntu0.20.04.2 failed to install/upgrade: installed nvidia-dkms-465 package post-installation script subprocess returned error exit status 10 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-465/+bug/1930775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921345] Re: Support MIPI camera through Intel IPU6
** Changed in: linux-firmware (Ubuntu) Status: Invalid => Won't Fix ** Changed in: linux-firmware (Ubuntu Hirsute) Status: Invalid => Won't Fix -- 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/1921345 Title: Support MIPI camera through Intel IPU6 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Won't Fix Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Won't Fix Bug description: [SRU Justification] [Impact] There are new platforms with MIPI camera based on Intel IPU6(Imaging Processing Unit version 6) currently unsupported in Ubuntu. [Fix] Intel IPU6 can be enabled by integration of following kernel driver, firmware, userspace HAL libraries as well as a GStreamer source element: * https://github.com/intel/ipu6-drivers * https://github.com/intel/ipu6-camera-bins * https://github.com/intel/ipu6-camera-hal * https://github.com/intel/icamerasrc This patchset took kernel patches from intel/ipu6-drivers. [Test Case] With kernel/firmware properly installed, the hardware should be ready for further development: $ dmesg | grep ipu intel-ipu6 intel-ipu: enabling device ( -> 0002) intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1) intel-ipu6 intel-ipu: physical base address 0x605400 intel-ipu6 intel-ipu: mapped as: 0x97793328 intel-ipu6 intel-ipu: IPU in secure mode intel-ipu6 intel-ipu: IPC reset done intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin intel-ipu6 intel-ipu: FW version: 20201222 intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE intel-ipu6 intel-ipu: CSE authenticate_run done intel-ipu6 intel-ipu: IPU driver version 1.0 intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 intel-ipu6-isys intel-ipu6-isys0: bind ov01a1s 20-0036 nlanes is 1 port is 1 intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed. intel-ipu6-isys intel-ipu6-isys0: stream on ov01a1s 20-0036 There should be nearly 24 video4linux devices created under /dev. [Where problems could occur] MIPI camera through Intel IPU6 takes also firmware blobs loaded in runtime from user space, addtional softwares are also required to fully enable it for oridinary use. The exposed video devices are hidden from general users and a relay daemon+v4l2loopback is used to enable use from existing applications. >From kernel's point of view, there is still a known issue that it takes root priviledge to access these devices. [Other Info] So far Intel has no plan to commit this driver to upstream yet, so it's only nominated for oem-5.10. It will only be nominated to generic kernels when the plan/requirements have changed. The original driver Kconfig would disable VIDEO_IPU3_CIO2, but that's reverted to avoid unnecessary changes to existing users. == original bug description == The Intel imaging processing unit version 6, found in Intel SoCs and used for capturing images and video from a camera sensor is enabled by integration of following kernel driver, firmware, userspace HAL libraries as well as a GStreamer source element: * https://github.com/intel/ipu6-drivers * https://github.com/intel/ipu6-camera-bins * https://github.com/intel/ipu6-camera-hal * https://github.com/intel/icamerasrc With all components properly installed, the hardware should be ready for further development: intel-ipu6 intel-ipu: enabling device ( -> 0002) intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1) intel-ipu6 intel-ipu: physical base address 0x605400 intel-ipu6 intel-ipu: mapped as: 0x97793328 intel-ipu6 intel-ipu: IPU in secure mode intel-ipu6 intel-ipu: IPC reset done intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin intel-ipu6 intel-ipu: FW version: 20201222 intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE intel-ipu6 intel-ipu: CSE authenticate_run done intel-ipu6 intel-ipu: IPU driver version 1.0 intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 intel-ipu6-isys intel-ipu6-isys0: bind ov01a1s 20-0036 nlanes is 1 port is 1 intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed. intel-ipu6-isys intel-ipu6-isys0: stream on ov01a1s 20-0036 This one equips an OV01A1S sensor, and HM11B1 is also supported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND
[Kernel-packages] [Bug 1930422] Re: thermald_1.9.1-1ubuntu0.4_amd64 breaks system
I encountered the similar issue since 1.9.1-1ubuntu0.4 update. On the previous version 1.9.1-1build1, if I run a CPU stress test, the fan will keep going up until full speed (~6000rpm) as the temp rises. On 1.9.1-1ubuntu0.4, the fan sometimes is kept at 3600rpm or remains at zero. Once CPU reaches over ~90C, it got throttled down to min freq 400MHz. I didn't know the problem was thermald until I reinstalled a fresh Ubuntu 20.04.2, which worked perfectly, and then basically did a binary search to find which package update caused the issue. To verify it's really thermald 1.9.1-1ubuntu0.4, I reinstalled Ubuntu 20.04.2 again, and the fan worked fine as expected, and then updated thermald alone, and this issue happened. Then I downgraded thermald to the stock version come with Ubuntu 20.04.2, the issue went away. lshw --short: system Latitude 7400 (08E1) /0 bus07WDVW /0/0 memory 64KiB BIOS /0/20memory 32GiB System Memory /0/20/0 memory 16GiB SODIMM DDR4 Synchronous 2667 MHz (0.4 ns) /0/20/1 memory 16GiB SODIMM DDR4 Synchronous 2667 MHz (0.4 ns) /0/29memory 256KiB L1 cache /0/2amemory 1MiB L2 cache /0/2bmemory 8MiB L3 cache /0/2cprocessor Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz /0/100 bridge Coffee Lake HOST and DRAM Controller /0/100/2 displayUHD Graphics 620 (Whiskey Lake) /0/100/4 genericXeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem /0/100/8 genericXeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model /0/100/12genericCannon Point-LP Thermal Controller /0/100/14busCannon Point-LP USB 3.1 xHCI Controller /0/100/14/0 usb1busxHCI Host Controller /0/100/14/0/6multimedia Integrated_Webcam_HD /0/100/14/0/8generic58200 /0/100/14/0/acommunication Bluetooth wireless interface /0/100/14/1 usb2busxHCI Host Controller /0/100/14.2 memory RAM memory /0/100/14.3 wlo1networkCannon Point-LP CNVi [Wireless-AC] /0/100/15busCannon Point-LP Serial IO I2C Controller #0 /0/100/15.1 busCannon Point-LP Serial IO I2C Controller #1 /0/100/15.3 busIntel Corporation /0/100/16communication Cannon Point-LP MEI Controller #1 /0/100/16.3 communication Cannon Point-LP Keyboard and Text (KT) Redirection /0/100/19busCannon Point-LP Serial IO I2C Host Controller /0/100/1cbridge Cannon Point-LP PCI Express Root Port #5 /0/100/1c/0 bridge JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] /0/100/1c/0/0bridge JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] /0/100/1c/0/0/0 genericJHL6340 Thunderbolt 3 NHI (C step) [Alpine Ridge 2C 2016] /0/100/1c/0/1bridge JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] /0/100/1c/0/2bridge JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] /0/100/1c/0/2/0 busJHL6340 Thunderbolt 3 USB 3.1 Controller (C step) [Alpine Ridge 2C 2016] /0/100/1c/0/2/0/0usb3busxHCI Host Controller /0/100/1c/0/2/0/1usb4busxHCI Host Controller /0/100/1dbridge Intel Corporation /0/100/1d/0 genericRTS525A PCI Express Card Reader /0/100/1d.4 bridge Cannon Point-LP PCI Express Root Port #13 /0/100/1d.4/0storageSK hynix /0/100/1d.4/0/0 /dev/nvme0 storagePC601 NVMe SK hynix 512GB /0/100/1d.4/0/0/1/dev/nvme0n1disk 512GB NVMe namespace /0/100/1d.4/0/0/1/1 volume 511MiB Windows FAT volume /0/100/1d.4/0/0/1/2 /dev/nvme0n1p2 volume 732MiB EXT4 volume /0/100/1d.4/0/0/1/3 /dev/nvme0n1p3 volume 475GiB EFI partition /0/100/1fbridge Cannon Point-LP LPC Controller /0/100/1f.3
[Kernel-packages] [Bug 1836858] Re: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background
Affects me as well. Reproduced on: * Dell XPS 7390, i7-10510U, integrated graphics, laptop screen * Focal with latest updates * Kernels: * 5.8.0-55-generic (linux-image-generic-hwe-20.04) * 5.13.0-rc4 (vanilla from mainline-ppa) In the kernel log, "fb0: switching to inteldrmfb from EFI VGA" is the last line I see before the mode change, and "clocksource: tsc: mask: 0x..." is the first line once the screen turns back on. i915.fastboot=1 is set in kernel cmdline, didn't make any difference. Resolution is visually the same before and after the mode change. [1.202214] fb0: switching to inteldrmfb from EFI VGA [1.204981] Console: switching to colour dummy device 80x25 [1.205002] i915 :00:02.0: vgaarb: deactivate vga console [1.257470] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [1.257523] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [1.258039] i915 :00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [1.266513] i915 :00:02.0: [drm] Panel advertises DPCD backlight support, but VBT disagrees. If your backlight controls don't work try booting with i915.enable_dpcd_backlight=1. If your machine needs this, please file a _new_ bug report on drm/i915, see https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs for details. [1.278853] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [1.388057] usb 1-9: new high-speed USB device number 2 using xhci_hcd [1.528528] usb 4-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd [1.543379] usb 1-9: New USB device found, idVendor=2109, idProduct=2812, bcdDevice= d.a0 [1.543392] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [1.543399] usb 1-9: Product: USB2.0 Hub [1.543404] usb 1-9: Manufacturer: VIA Labs, Inc. [1.544575] hub 1-9:1.0: USB hub found [1.545569] hub 1-9:1.0: 4 ports detected [1.564060] tsc: Refined TSC clocksource calibration: 2303.993 MHz [1.564082] clocksource: tsc: mask: 0x max_cycles: 0x2135f10e1ea, max_idle_ns: 440795202126 ns -- 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/1836858 Title: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background Status in Plymouth: Unknown Status in linux package in Ubuntu: Confirmed Status in plymouth package in Ubuntu: Confirmed Bug description: I am trying flickerfree boot in 19.10 [1], but find it actually flickers part way through: 1. BIOS logo on a black background. 2. Display mode resets, no image on a black background briefly. 3. BIOS logo on a black background. The flicker occurs seemingly during kernel startup since my peripherals are lit up before the problem occurs. Suspecting this might be related to FB handover: [2.751028] fb0: switching to inteldrmfb from EFI VGA I tried disabling that with a big hammer: i915.modeset=0 so it stays in efifb, and that works -- no more flickering, providing I don't let i915 take over the framebuffer. [1] https://discourse.ubuntu.com/t/testing-flickerfree-boot/11854 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic 5.2.0-8.9 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Jul 17 16:34:36 2019 InstallationDate: Installed on 2019-05-02 (76 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501) MachineType: LENOVO 10M7CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=9bfb5f01-bdd4-4854-bfce-1c28e2f2f3bc ro quiet splash i915.fastboot=1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.180 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060530 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO
[Kernel-packages] [Bug 1929870] Re: AMD desktop often fails to resume from deep suspend
Okay, I've attached the requested log. ** Attachment added: "journalctl -b -1 -k after suspend failed" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929870/+attachment/5502666/+files/jrnl.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929870 Title: AMD desktop often fails to resume from deep suspend Status in linux package in Ubuntu: Confirmed Bug description: Machine setup: Desktop PC Ubuntu 21.04 Linux version 5.11.0-17-generic AMD Ryzen 3900X Asus X590 PRIME PRO motherboard NVIDIA P400 GPU Approximately one in every 4 attempts to resume from a deep suspend fails. When the issue occurs the fans spin up but the monitor displays no output and input devices do not function, the system appears frozen and must be restarted using power or reset buttons. I have tried using different dNVIDIA isplay drivers (proprietary as well as open source) as well as trying an AMD Radeon HD 6450 GPU instead of the NVIDIA GPU. I have tried the following kernel parameters: processor.max_cstate=1 rcu_nocbs=0-23 I have updated the BIOS several times. I had similar problems with Ubuntu 20.10. I have enabled some additional kernel logging with initcall_debug. Fairly consistently the last message printed in the kernel log is from the ethernet driver: May 27 09:19:43 jacob-tm kernel: [ 230.878348] OOM killer enabled. May 27 09:19:43 jacob-tm kernel: [ 230.878349] Restarting tasks ... May 27 09:19:43 jacob-tm kernel: [ 230.879023] usb 5-2.3: USB disconnect, device number 4 May 27 09:19:43 jacob-tm kernel: [ 230.879026] usb 5-2.3.1: USB disconnect, device number 5 May 27 09:19:43 jacob-tm kernel: [ 230.879285] done. May 27 09:19:43 jacob-tm kernel: [ 230.879318] PM: suspend exit May 27 09:19:43 jacob-tm kernel: [ 230.880916] rfkill: input handler enabled May 27 09:19:43 jacob-tm kernel: [ 230.955727] kauditd_printk_skb: 1 callbacks suppressed May 27 09:19:43 jacob-tm kernel: [ 230.955731] audit: type=1400 audit(1622132383.424:64): apparmor="DENIED" operation="capab le" profile="/usr/sbin/cupsd" pid=4418 comm="cupsd" capability=12 capname="net_admin" May 27 09:19:43 jacob-tm kernel: [ 230.966192] audit: type=1400 audit(1622132383.432:65): apparmor="DENIED" operation="capab le" profile="/usr/sbin/cups-browsed" pid=4429 comm="cups-browsed" capability=23 capname="sys_nice" May 27 09:19:43 jacob-tm kernel: [ 231.120385] rfkill: input handler disabled May 27 09:19:43 jacob-tm kernel: [ 231.225924] usb 5-2.3.2: USB disconnect, device number 6 May 27 09:19:43 jacob-tm kernel: [ 231.481893] usb 5-2.3.5: USB disconnect, device number 7 May 27 09:19:47 jacob-tm kernel: [ 235.009576] igb :05:00.0 enp5s0: igb: enp5s0 NIC Link is Up 1000 Mbps Full Duplex, Fl ow Control: RX/TX May 27 09:19:47 jacob-tm kernel: [ 235.009913] IPv6: ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-17-generic 5.11.0-17.18 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacob 2024 F pulseaudio /dev/snd/controlC0: jacob 2024 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 27 14:12:33 2021 InstallationDate: Installed on 2020-10-28 (211 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp5s0no wireless extensions. docker0 no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=f721d5df-ceec-434a-919a-0680ee380996 ro quiet splash initcall_debug processor.max_cstate=1 rcu_nocbs=0-23 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-17-generic N/A linux-backports-modules-5.11.0-17-generic N/A linux-firmware 1.197 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-05-14 (13 days ago) dmi.bios.date: 05/08/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3604 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
** Also affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI Status in nvidia-graphics-drivers-460 package in Ubuntu: New Status in nvidia-graphics-drivers-465 package in Ubuntu: Confirmed Bug description: I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute Jun 03 16:26:57 willow kernel: Oops: [#1] SMP PTI Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P OE 5.11.0-18-generic #19-Ubuntu Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019 Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 RDI: Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 R09: 8e318220acb8 Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 R12: 0400 Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 R15: 0800 Jun 03 16:26:57 willow kernel: FS: 7f5807f38a40() GS:8e3466dc() knlGS: Jun 03 16:26:57 willow kernel: CS: 0010 DS: ES: CR0: 80050033 Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 CR4: 003706e0 Jun 03 16:26:57 willow kernel: DR0: DR1: DR2: Jun 03 16:26:57 willow kernel: DR3: DR6: fffe0ff0 DR7: 0400 Jun 03 16:26:57 willow kernel: Call Trace: Jun 03 16:26:57 willow kernel: ? _nv015556rm+0x7fd/0x1020 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv027155rm+0x22c/0x4f0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017787rm+0x303/0x5e0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017789rm+0xe1/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv022829rm+0xed/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv023065rm+0x30/0x60 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv000704rm+0x16da/0x22b0 [nvidia] Jun 03 16:26:57 willow kernel: ? rm_init_adapter+0xc5/0xe0 [nvidia] Jun 03 16:26:57 willow kernel: ? nv_open_device+0x122/0x8e0 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_open+0x2b7/0x560 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_frontend_open+0x58/0xa0 [nvidia] Jun 03 16:26:57 willow kernel: ? chrdev_open+0xf7/0x220 Jun 03 16:26:57 willow kernel: ? cdev_device_add+0x90/0x90 Jun 03 16:26:57 willow kernel: ? do_dentry_open+0x156/0x370 Jun 03 16:26:57 willow kernel: ? vfs_open+0x2d/0x30 Jun 03 16:26:57 willow kernel: ? do_open+0x1c3/0x340 Jun 03 16:26:57 willow kernel: ? path_openat+0x10a/0x1d0 Jun 03 16:26:57 willow kernel: ? do_filp_open+0x8c/0x130 Jun 03 16:26:57 willow kernel: ? __check_object_size+0x1c/0x20 Jun 03 16:26:57 willow kernel: ? do_sys_openat2+0x9b/0x150 Jun 03 16:26:57 willow kernel: ? __x64_sys_openat+0x56/0x90 Jun 03 16:26:57 willow kernel: ? do_syscall_64+0x38/0x90 Jun 03 16:26:57 willow kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 03 16:26:57 willow kernel: Modules linked in: snd_seq_dummy snd_hrtimer vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) > Jun 03 16:26:57 willow kernel: sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd c> Jun 03 16:26:57 willow kernel: CR2: 0170 Jun 03 16:26:57 willow kernel: ---[ end trace 0013b6989b267f32 ]--- Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 RDI: Jun 03 16:26:57 willow kernel: RBP:
[Kernel-packages] [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-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/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI Status in nvidia-graphics-drivers-465 package in Ubuntu: Confirmed Bug description: I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute Jun 03 16:26:57 willow kernel: Oops: [#1] SMP PTI Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P OE 5.11.0-18-generic #19-Ubuntu Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019 Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 RDI: Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 R09: 8e318220acb8 Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 R12: 0400 Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 R15: 0800 Jun 03 16:26:57 willow kernel: FS: 7f5807f38a40() GS:8e3466dc() knlGS: Jun 03 16:26:57 willow kernel: CS: 0010 DS: ES: CR0: 80050033 Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 CR4: 003706e0 Jun 03 16:26:57 willow kernel: DR0: DR1: DR2: Jun 03 16:26:57 willow kernel: DR3: DR6: fffe0ff0 DR7: 0400 Jun 03 16:26:57 willow kernel: Call Trace: Jun 03 16:26:57 willow kernel: ? _nv015556rm+0x7fd/0x1020 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv027155rm+0x22c/0x4f0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017787rm+0x303/0x5e0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017789rm+0xe1/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv022829rm+0xed/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv023065rm+0x30/0x60 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv000704rm+0x16da/0x22b0 [nvidia] Jun 03 16:26:57 willow kernel: ? rm_init_adapter+0xc5/0xe0 [nvidia] Jun 03 16:26:57 willow kernel: ? nv_open_device+0x122/0x8e0 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_open+0x2b7/0x560 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_frontend_open+0x58/0xa0 [nvidia] Jun 03 16:26:57 willow kernel: ? chrdev_open+0xf7/0x220 Jun 03 16:26:57 willow kernel: ? cdev_device_add+0x90/0x90 Jun 03 16:26:57 willow kernel: ? do_dentry_open+0x156/0x370 Jun 03 16:26:57 willow kernel: ? vfs_open+0x2d/0x30 Jun 03 16:26:57 willow kernel: ? do_open+0x1c3/0x340 Jun 03 16:26:57 willow kernel: ? path_openat+0x10a/0x1d0 Jun 03 16:26:57 willow kernel: ? do_filp_open+0x8c/0x130 Jun 03 16:26:57 willow kernel: ? __check_object_size+0x1c/0x20 Jun 03 16:26:57 willow kernel: ? do_sys_openat2+0x9b/0x150 Jun 03 16:26:57 willow kernel: ? __x64_sys_openat+0x56/0x90 Jun 03 16:26:57 willow kernel: ? do_syscall_64+0x38/0x90 Jun 03 16:26:57 willow kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 03 16:26:57 willow kernel: Modules linked in: snd_seq_dummy snd_hrtimer vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) > Jun 03 16:26:57 willow kernel: sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd c> Jun 03 16:26:57 willow kernel: CR2: 0170 Jun 03 16:26:57 willow kernel: ---[ end trace 0013b6989b267f32 ]--- Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 RDI: Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08:
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp/5.4.0.1045.54)
All autopkgtests for the newly accepted linux-meta-gcp (5.4.0.1045.54) for focal have finished running. The following regressions have been reported in tests triggered by the package: dpdk/19.11.7-0ubuntu0.20.04.1 (amd64) nat-rtsp/0.7+4.18-0.1ubuntu1 (amd64) gost-crypto/0.3.2-2ubuntu0.2 (amd64) rtl8821ce/5.5.2.1-0ubuntu4~20.04.3 (amd64) broadcom-sta/6.30.223.271-12 (amd64) iptables-netflow/2.4-2ubuntu0.4 (amd64) bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 (amd64) v4l2loopback/0.12.3-1ubuntu0.4 (amd64) acpi-call/1.1.0-5ubuntu0.2 (amd64) xtables-addons/3.9-1ubuntu0.2~20.04.1 (amd64) lime-forensics/1.9-1ubuntu0.2 (amd64) lttng-modules/2.12.2-1ubuntu1~20.04.2 (amd64) dm-writeboost/2.2.9-1ubuntu1.2 (amd64) bbswitch/0.8-8ubuntu0.20.04.1 (amd64) tp-smapi/0.43-1 (amd64) nvidia-graphics-drivers-418-server/418.197.02-0ubuntu0.20.04.1 (amd64) jool/4.0.7-1 (amd64) nvidia-graphics-drivers-460/460.80-0ubuntu0.20.04.2 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 (amd64) backport-iwlwifi-dkms/8324-0ubuntu3~20.04.3 (amd64) ddcci-driver-linux/0.3.3-1 (amd64) virtualbox/6.1.16-dfsg-6~ubuntu1.20.04.2 (amd64) adv-17v35x/5.0.3.0-2 (amd64) nvidia-graphics-drivers-390/390.143-0ubuntu0.20.04.1 (amd64) sl-modem/2.9.11~20110321-16ubuntu1 (amd64) ndiswrapper/1.60-8ubuntu3 (amd64) nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (amd64) openrazer/2.5.0+dfsg-1ubuntu2 (amd64) nvidia-graphics-drivers-450-server/450.119.04-0ubuntu0.20.04.2 (amd64) oss4/4.2-build2010-5ubuntu6~20.04.2 (amd64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (amd64) west-chamber/20100405+svn2007.r124-12ubuntu0.3~20.04.1 (amd64) openafs/1.8.4~pre1-1ubuntu2.1 (amd64) langford/0.0.20130228-6build1 (amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2 (amd64) nvidia-graphics-drivers-460-server/460.73.01-0ubuntu0.20.04.1 (amd64) sysdig/0.26.4-1ubuntu0.3 (amd64) r8168/8.048.00-1ubuntu0.20.04.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-gcp [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 1930980] Re: Hang on loading initial ramdisk on kernels 5.4.0-72+, 5.11.0-16+ with nvidia drivers 440+
This looks similar to https://bugs.launchpad.net/ubuntu/+source/nvidia- graphics-drivers-465/+bug/1930733 Do you use DisplayPort? If yes can you try with HDMI? For me it only happens with DisplayPort -- 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/1930980 Title: Hang on loading initial ramdisk on kernels 5.4.0-72+, 5.11.0-16+ with nvidia drivers 440+ Status in linux package in Ubuntu: New Status in nvidia-graphics-drivers-460 package in Ubuntu: New Status in nvidia-graphics-drivers-465 package in Ubuntu: New Bug description: Affected Ubuntu Versions: Release: 20.04 Kernel: 5.4.0-73,74 Nvidia Driver: 440,450,460,465 Kernel: 5.4.0-72 Nvidia Driver: 460, 465 Release: 21.04 Kernel: 5.11.0-16,18 Nvidia Driver: 440, 450, 460, 465 For 21.04 with all kernels, driver 390 works correctly Issue occurs during bootup where after starting to load the initial ramdisk, the system hangs indefinitely with no output. Booting in recovery mode and examining the logs, there is a series of bug messages. Updating motherboard bios to latest had no effect. Note: This exact hardware setup worked as recently as June 2, 2021 on ubuntu 20.04. After applying the latest set of OS updates and rebooting, the issue began occurring. Trace follows: Jun 4 21:51:06 ultra kernel: [7.262411] BUG: kernel NULL pointer dereference, address: Jun 4 21:51:06 ultra kernel: [7.262412] #PF: supervisor write access in kernel mode Jun 4 21:51:06 ultra kernel: [7.262413] #PF: error_code(0x0002) - not-present page Jun 4 21:51:06 ultra kernel: [7.262414] PGD 0 P4D 0 Jun 4 21:51:06 ultra kernel: [7.262415] Oops: 0002 [#1] SMP NOPTI Jun 4 21:51:06 ultra kernel: [7.262416] CPU: 3 PID: 998 Comm: Xorg Tainted: P IO 5.11.0-18-generic #19-Ubuntu Jun 4 21:51:06 ultra kernel: [7.262417] Hardware name: ASUS System Product Name/PRIME Z390-A, BIOS 1802 12/01/2020 Jun 4 21:51:06 ultra kernel: [7.262418] RIP: 0010:_nv008453rm+0xa8/0x5f0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.262673] Code: 8b 84 24 60 04 00 00 ba 01 00 00 00 4c 89 e6 48 89 df 4d 89 e5 e8 c8 64 c4 e0 41 89 c6 45 85 f6 0f 84 3c 02 00 00 48 8b 45 08 <4c> 89 28 5b 44 89 f0 41 5c 41 5d 41 5e 41 5f 48 83 c5 40 c3 0f 1f Jun 4 21:51:06 ultra kernel: [7.262675] RSP: 0018:be91018bf8c8 EFLAGS: 00010282 Jun 4 21:51:06 ultra kernel: [7.262676] RAX: RBX: a08c06e14008 RCX: Jun 4 21:51:06 ultra kernel: [7.262676] RDX: 0020 RSI: d9a4 RDI: a08c06e14008 Jun 4 21:51:06 ultra kernel: [7.262677] RBP: a08c0a0c5db0 R08: 0025 R09: a08c0a0c5d18 Jun 4 21:51:06 ultra kernel: [7.262678] R10: a08c06e14008 R11: a08c06e150a0 R12: a08c07440008 Jun 4 21:51:06 ultra kernel: [7.262678] R13: a08c07440010 R14: R15: a08c0a0c5de0 Jun 4 21:51:06 ultra kernel: [7.262679] FS: 7f7d29194a40() GS:a09b2dac() knlGS: Jun 4 21:51:06 ultra kernel: [7.262680] CS: 0010 DS: ES: CR0: 80050033 Jun 4 21:51:06 ultra kernel: [7.262680] CR2: CR3: 00010f6fe006 CR4: 003706e0 Jun 4 21:51:06 ultra kernel: [7.262681] DR0: DR1: DR2: Jun 4 21:51:06 ultra kernel: [7.262681] DR3: DR6: fffe0ff0 DR7: 0400 Jun 4 21:51:06 ultra kernel: [7.262682] Call Trace: Jun 4 21:51:06 ultra kernel: [7.262684] ? _nv032332rm+0x10c/0x280 [nvidia] Jun 4 21:51:06 ultra kernel: [7.262884] ? _nv032330rm+0x145/0x180 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263075] ? _nv014647rm+0x213/0x300 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263255] ? _nv014704rm+0x6dd/0xf80 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263435] ? _nv026937rm+0x226/0x4e0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263616] ? _nv016954rm+0x4a8/0x5e0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263819] ? _nv016956rm+0xdd/0x230 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264009] ? _nv09rm+0xcd/0x1d0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264256] ? _nv022467rm+0x30/0x60 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264394] ? _nv000701rm+0x143f/0x2100 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264552] ? rm_init_adapter+0xc5/0xe0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264709] ? nv_open_device+0x122/0x8e0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264805] ? nvidia_open+0x2b7/0x560 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264901] ? nvidia_frontend_open+0x58/0xa0 [nvidia] Jun 4
[Kernel-packages] [Bug 1928146] Re: Please SRU nvidia-modprobe 465.24
Enabled proposed for this file, does exactly what is described and allows for CUDA library installation on Hirsute, Groovy, and Focal. ** Tags removed: verification-needed verification-needed-focal verification-needed-groovy verification-needed-hirsute ** Tags added: verification-done verification-done-focal verification-done-groovy verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1928146 Title: Please SRU nvidia-modprobe 465.24 Status in nvidia-modprobe package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-modprobe source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Released Status in nvidia-modprobe source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Released Status in nvidia-modprobe source package in Hirsute: Fix Committed Status in nvidia-settings source package in Hirsute: Fix Released Status in nvidia-modprobe source package in Impish: Fix Released Status in nvidia-settings source package in Impish: Fix Released Bug description: [Impact] Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are unable to install and/or upgrade to version 460.73 of the CUDA libraries. This is because the new libraries have a versioned hard dependency on nvidia-modprobe >= 460.73 and nvidia-settings >= 460.73. This is impacting data scientists and deep learning customers. [Test Case] * Add the Nvidia CUDA repositories below: echo 'deb http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 / deb http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64 / ' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list sudo apt-get update * Ensure nvidia and libnvidia files come from the Ubuntu repository: echo 'Package: nvidia-* libnvidia-* xserver-xorg-* Pin: release l=NVIDIA CUDA Pin-Priority: -1' |sudo tee /etc/apt/preferences.d/nvidia-libs.conf sudo apt-get update * Install nvidia-driver-460 from the Ubuntu repository: sudo apt-get install nvidia-driver-460 * Confirm that almost all Nvidia driver packages are set to the same version (460.73.01) except for nvidia-settings and nvidia-modprobe: dpkg --list |grep nvidia |grep ^ii |awk '{print $3"\t" $2}' |sort -n * Attempt to install the CUDA package from Nvidia sudo apt-get install cuda-drivers-460 * The drivers will not install due to a version mismatch as show below: sudo apt-get install cuda-drivers-460 ... The following packages have unmet dependencies: cuda-drivers-460 Depends: nvidia-modprobe (>= 460.73.01) but 460.32.03-0ubuntu20.04.1 is to be installed Depends: nvidia-settings (>= 460.73.01) but 460.39-0ubuntu0.20.04.1 is to be installed E: Unable to correct problems, you have held broken packages. [Where problems could occur] * This may potentially cause issues with older versions of the Nvidia driver, but this is low since this is for users of the 460 drivers. [Other Information] Can nvidia-modprobe and nvidia-settings be synchronized to match the other versions provided in this and all future nvidia-drivers-* metapackages? This should resolve the issue forever going forward. Debdiffs: Hirsute: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files /nvidia- settings_460.56-0ubuntu2_460.73.01-0ubuntu1~ubuntu21.04.1~ppa1.diff.gz Groovy: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files /nvidia- settings_440.82-0ubuntu1_460.73.01-0ubuntu1~ubuntu20.10.1~ppa1.diff.gz Focal: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files/nvidia-settings_440.64-0ubuntu1_460.73.01-0ubuntu1~ubuntu20.04.1~ppa1.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-modprobe/+bug/1928146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925685] Re: [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer
Verified fixes work in Groovy as well using the above method. ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- 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/1925685 Title: [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Bionic: Won't Fix Status in linux-hwe-5.8 source package in Bionic: Confirmed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.8 source package in Focal: Confirmed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-hwe-5.8 source package in Groovy: Confirmed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Committed Status in linux-hwe-5.8 source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-hwe-5.8 source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Bug description: Filing this with my Kubuntu Focus (kfocus.org) OEM hat on: [Impact] We are having screen flickering and glitching issues with some of our hardware upon wake from suspend. We have worked with our ODM to figure out a fix for this. They had reported there were no issues when running Windows on the same hardware. As such, we tested, and found that this issue first began as a regression in kernel 5.0 (did not exist in kernel 4.18 per our tests). We identified a patch via https://gitlab.freedesktop.org/drm/intel/-/issues/272 in which this has been solved. Per our testing by recompiling the kernel, this completely fixes our hardware issue. As of 4-21, this fix has been merged into the Linux kernel per Timo Aaltonen, and will be included in the kernel in the 5.13 release. Our hardware ships with Kubuntu 20.04 LTS, which means the 5.13 kernel will not see these machines, at least in the forseeable future. As such, we request that this patch be added to the kernel. Per our testing, this patch is straightforward to add and works flawlessly. The patch that works best was created in collaboration with Kai-Heng Feng, is attached to this bug report, and can be found here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+attachment/5491421/+files /drm-intel-both.patch Until this is fixed, we have a whole batch of hardware we cannot sell, so, as an OEM, this is a high priority. [Test Plan] * Install Kubuntu on an affected Kubuntu Focus M2 computer (not in the hands of customers at this time) * Notice screen glitching/flickering after wake-from-suspend. * Install kernel compiled with the attached patch. Boot from patched kernel. * Suspend laptop, resume. No glitches. [Where problems could occur] * Although this solves the problem for us and has been confirmed to work with the Intel developers that developed this patch, it could cause another display type to have problems. This is unlikely as it has been vetted by Intel and by the mainline Linux kernel developers. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1925685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927866] Re: Root filesystem becomes readonly frequenty freezing system
The system ran for a whole day without crashing and it had gone into screen lock multiple times but did not crash. Yesterday night I disconnected power and closed laptop. Today when I opened, the lock screen came up, I entered password and it crashed at that point. The screen scrolled too much and I couldn't get a screenshot. However the first line was error while async write back metadata I also recollect the third line which said failed to set APST feature I think I saw -19 after that, not sure though. I ran this sudo nvme id-ctrl /dev/nvme0 NVME Identify Controller: vid : 0x15b7 ssvid : 0x15b7 sn: 205135806243 mn: WDC PC SN530 SDBPMPZ-512G-1101 fr: 21160001 rab : 4 ieee : 001b44 cmic : 0 mdts : 7 cntlid: 0x1 ver : 0x10400 rtd3r : 0x7a120 rtd3e : 0xf4240 oaes : 0x200 ctratt: 0x2 rrls : 0 cntrltype : 1 fguid : crdt1 : 0 crdt2 : 0 crdt3 : 0 oacs : 0x17 acl : 4 aerl : 7 frmw : 0x14 lpa : 0x1e elpe : 255 npss : 4 avscc : 0x1 apsta : 0x1 wctemp: 353 cctemp: 358 mtfa : 50 hmpre : 51200 hmmin : 823 tnvmcap : 512110190592 unvmcap : 0 rpmbs : 0 edstt : 57 dsto : 1 fwug : 1 kas : 0 hctma : 0x1 mntmt : 273 mxtmt : 358 sanicap : 0x6002 hmminds : 0 hmmaxd: 8 nsetidmax : 0 endgidmax : 0 anatt : 0 anacap: 0 anagrpmax : 0 nanagrpid : 0 pels : 1 sqes : 0x66 cqes : 0x44 maxcmd: 0 nn: 1 oncs : 0x5f fuses : 0 fna : 0 vwc : 0x7 awun : 0 awupf : 0 nvscc : 1 nwpc : 0 acwu : 0 sgls : 0 mnan : 0 subnqn: nqn.2018-01.com.wdc:guid:E8238FA6BF53-0001-001B448B484DAFF7 ioccsz: 0 iorcsz: 0 icdoff: 0 ctrattr : 0 msdbd : 0 ps0 : mp:3.50W operational enlat:0 exlat:0 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:0.6300W active_power:2.10W ps1 : mp:2.40W operational enlat:0 exlat:0 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:0.6300W active_power:1.60W ps2 : mp:1.90W operational enlat:0 exlat:0 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:0.6300W active_power:1.50W ps3 : mp:0.0250W non-operational enlat:3900 exlat:11000 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:0.0250W active_power:- ps4 : mp:0.0050W non-operational enlat:5000 exlat:39000 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:0.0050W active_power:- I am going to try to replicate the error by running through the same scenario. Allowing the laptop to suspend while power disconnected and then try to login after that. -- 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/1927866 Title: Root filesystem becomes readonly frequenty freezing system Status in linux package in Ubuntu: Confirmed Bug description: I have a brand new Lenovo Ideapad Flex 5.14 which came with Windows 10 and I have installed Ubuntu 21.04 with dual boot. I am running into this problem where the root filesystem becomes readonly and the system freezes with a screen full of errors shown about unable to write to filesystem. I booted into a live boot usb and did fsck and e2fsck but did not see any errors there. I read online that this could be because of io errors but smartctl and fsck does not show any errors So I was wondering if this could be a bug vs a hardward issue. Please let me know if you need any further information from the system. = = fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: WDC PC SN530 SDBPMPZ-512G-1101 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: E8803E28-C4F7-4FA5-9B6D-0F3CAB7027A5 Device StartEnd Sectors Size Type /dev/nvme0n1p1 2048 534527532480 260M EFI System /dev/nvme0n1p2534528 567295 3276816M Microsoft reserved /dev/nvme0n1p3567296 199446527 198879232 94.8G Microsoft basic data /dev/nvme0n1p4 998166528 1000214527 2048000 1000M Windows recovery environmen /dev/nvme0n1p5 199446528 203352063 3905536 1.9G Linux filesystem /dev/nvme0n1p6 203352064 219353087 16001024 7.6G Linux swap /dev/nvme0n1p7 219353088 414664703 195311616 93.1G Linux filesystem /dev/nvme0n1p8 414664704 998166527 583501824 278.2G Microsoft basic data = = smartctl -a /dev/nvme0 smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.11.0-16-generic] (local build) Copyright (C) 2002-20,
[Kernel-packages] [Bug 1928606] Re: package libnvidia-compute-390 390.143-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different fr
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1928606 Title: package libnvidia-compute-390 390.143-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:i386 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: i changed nvidia driver from 390 to 340 and after reboot i saw black screen and i can just going to tty and i tried to solve this problem and delete nvidia and i had a mistake and delete kernel headers. with ubuntu live and chroot , connected to host and i could use internet. i tried to update apt and solve this problem. but i can not tell you the way because it solved suddenly. i hope to you to solve nvidia proplem. tnx ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-compute-390 390.143-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 17 01:51:44 2021 Df: ErrorMessage: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:i386 InstallationDate: Installed on 2021-03-18 (59 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 390.143-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1928606/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930980] Re: Hang on loading initial ramdisk on kernels 5.4.0-72+, 5.11.0-16+ with nvidia drivers 440+
** Also affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-465 (Ubuntu) Importance: Undecided Status: New -- 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/1930980 Title: Hang on loading initial ramdisk on kernels 5.4.0-72+, 5.11.0-16+ with nvidia drivers 440+ Status in linux package in Ubuntu: New Status in nvidia-graphics-drivers-460 package in Ubuntu: New Status in nvidia-graphics-drivers-465 package in Ubuntu: New Bug description: Affected Ubuntu Versions: Release: 20.04 Kernel: 5.4.0-73,74 Nvidia Driver: 440,450,460,465 Kernel: 5.4.0-72 Nvidia Driver: 460, 465 Release: 21.04 Kernel: 5.11.0-16,18 Nvidia Driver: 440, 450, 460, 465 For 21.04 with all kernels, driver 390 works correctly Issue occurs during bootup where after starting to load the initial ramdisk, the system hangs indefinitely with no output. Booting in recovery mode and examining the logs, there is a series of bug messages. Updating motherboard bios to latest had no effect. Note: This exact hardware setup worked as recently as June 2, 2021 on ubuntu 20.04. After applying the latest set of OS updates and rebooting, the issue began occurring. Trace follows: Jun 4 21:51:06 ultra kernel: [7.262411] BUG: kernel NULL pointer dereference, address: Jun 4 21:51:06 ultra kernel: [7.262412] #PF: supervisor write access in kernel mode Jun 4 21:51:06 ultra kernel: [7.262413] #PF: error_code(0x0002) - not-present page Jun 4 21:51:06 ultra kernel: [7.262414] PGD 0 P4D 0 Jun 4 21:51:06 ultra kernel: [7.262415] Oops: 0002 [#1] SMP NOPTI Jun 4 21:51:06 ultra kernel: [7.262416] CPU: 3 PID: 998 Comm: Xorg Tainted: P IO 5.11.0-18-generic #19-Ubuntu Jun 4 21:51:06 ultra kernel: [7.262417] Hardware name: ASUS System Product Name/PRIME Z390-A, BIOS 1802 12/01/2020 Jun 4 21:51:06 ultra kernel: [7.262418] RIP: 0010:_nv008453rm+0xa8/0x5f0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.262673] Code: 8b 84 24 60 04 00 00 ba 01 00 00 00 4c 89 e6 48 89 df 4d 89 e5 e8 c8 64 c4 e0 41 89 c6 45 85 f6 0f 84 3c 02 00 00 48 8b 45 08 <4c> 89 28 5b 44 89 f0 41 5c 41 5d 41 5e 41 5f 48 83 c5 40 c3 0f 1f Jun 4 21:51:06 ultra kernel: [7.262675] RSP: 0018:be91018bf8c8 EFLAGS: 00010282 Jun 4 21:51:06 ultra kernel: [7.262676] RAX: RBX: a08c06e14008 RCX: Jun 4 21:51:06 ultra kernel: [7.262676] RDX: 0020 RSI: d9a4 RDI: a08c06e14008 Jun 4 21:51:06 ultra kernel: [7.262677] RBP: a08c0a0c5db0 R08: 0025 R09: a08c0a0c5d18 Jun 4 21:51:06 ultra kernel: [7.262678] R10: a08c06e14008 R11: a08c06e150a0 R12: a08c07440008 Jun 4 21:51:06 ultra kernel: [7.262678] R13: a08c07440010 R14: R15: a08c0a0c5de0 Jun 4 21:51:06 ultra kernel: [7.262679] FS: 7f7d29194a40() GS:a09b2dac() knlGS: Jun 4 21:51:06 ultra kernel: [7.262680] CS: 0010 DS: ES: CR0: 80050033 Jun 4 21:51:06 ultra kernel: [7.262680] CR2: CR3: 00010f6fe006 CR4: 003706e0 Jun 4 21:51:06 ultra kernel: [7.262681] DR0: DR1: DR2: Jun 4 21:51:06 ultra kernel: [7.262681] DR3: DR6: fffe0ff0 DR7: 0400 Jun 4 21:51:06 ultra kernel: [7.262682] Call Trace: Jun 4 21:51:06 ultra kernel: [7.262684] ? _nv032332rm+0x10c/0x280 [nvidia] Jun 4 21:51:06 ultra kernel: [7.262884] ? _nv032330rm+0x145/0x180 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263075] ? _nv014647rm+0x213/0x300 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263255] ? _nv014704rm+0x6dd/0xf80 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263435] ? _nv026937rm+0x226/0x4e0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263616] ? _nv016954rm+0x4a8/0x5e0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263819] ? _nv016956rm+0xdd/0x230 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264009] ? _nv09rm+0xcd/0x1d0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264256] ? _nv022467rm+0x30/0x60 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264394] ? _nv000701rm+0x143f/0x2100 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264552] ? rm_init_adapter+0xc5/0xe0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264709] ? nv_open_device+0x122/0x8e0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264805] ? nvidia_open+0x2b7/0x560 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264901] ? nvidia_frontend_open+0x58/0xa0 [nvidia] Jun 4
[Kernel-packages] [Bug 1930980] Re: Hang on loading initial ramdisk on kernels 5.4.0-72+, 5.11.0-16+ with nvidia drivers 440+
Additional Data on ubuntu 21.04 with kernel 5.11.0-18 Have tried several of the available drivers directly from NVIDIA on the 450, 460 and 465 driver lines. 465.31 - FAIL 465.27 - FAIL 465.24.02 - FAIL 460.84 - FAIL 460.80 - FAIL 460.73.01 - PASS 460.67 - PASS 460.56 - PASS 450.119.03 - PASS The crash occurs as soon as the new module is loaded, even without a reboot. Logs follow: Jun 5 13:24:23 ultra kernel: [ 148.830777] nvidia-uvm: Unloaded the UVM driver. Jun 5 13:24:23 ultra kernel: [ 148.850676] [drm] [nvidia-drm] [GPU ID 0x0100] Unloading driver Jun 5 13:24:23 ultra kernel: [ 148.914137] nvidia-modeset: Unloading Jun 5 13:24:23 ultra kernel: [ 148.964524] nvidia-nvlink: Unregistered the Nvlink Core, major device number 234 Jun 5 13:24:38 ultra dbus-daemon[1614]: [session uid=1000 pid=1614] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.1' (uid=1000 pid=1609 comm="/usr/libexec/tracker-miner-fs " label="unconfined") Jun 5 13:24:38 ultra systemd[1598]: Starting Tracker metadata database store and lookup manager... Jun 5 13:24:38 ultra dbus-daemon[1614]: [session uid=1000 pid=1614] Successfully activated service 'org.freedesktop.Tracker1' Jun 5 13:24:38 ultra systemd[1598]: Started Tracker metadata database store and lookup manager. Jun 5 13:24:38 ultra dbus-daemon[1614]: [session uid=1000 pid=1614] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.1' (uid=1000 pid=1609 comm="/usr/libexec/tracker-miner-fs " label="unconfined") Jun 5 13:24:38 ultra systemd[1598]: Starting Tracker metadata extractor... Jun 5 13:24:38 ultra tracker-extract[2705]: Set scheduler policy to SCHED_IDLE Jun 5 13:24:38 ultra tracker-extract[2705]: Setting priority nice level to 19 Jun 5 13:24:38 ultra dbus-daemon[1614]: [session uid=1000 pid=1614] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract' Jun 5 13:24:38 ultra systemd[1598]: Started Tracker metadata extractor. Jun 5 13:24:42 ultra systemd[1]: Reloading. Jun 5 13:24:42 ultra systemd[1]: /lib/systemd/system/plymouth-start.service:17: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. Jun 5 13:24:53 ultra systemd[1598]: tracker-extract.service: Succeeded. Jun 5 13:24:57 ultra kernel: [ 183.521086] nvidia-nvlink: Nvlink Core is being initialized, major device number 234 Jun 5 13:24:57 ultra kernel: [ 183.521090] Jun 5 13:24:57 ultra kernel: [ 183.521525] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=none,decodes=none:owns=io+mem Jun 5 13:24:57 ultra kernel: [ 183.637186] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 465.24.02 Thu Apr 8 17:55:47 UTC 2021 Jun 5 13:24:57 ultra systemd[1]: Starting NVIDIA Persistence Daemon... Jun 5 13:24:57 ultra nvidia-persistenced: Verbose syslog connection opened Jun 5 13:24:57 ultra nvidia-persistenced: Now running with user ID 127 and group ID 134 Jun 5 13:24:57 ultra nvidia-persistenced: Started (10237) Jun 5 13:24:57 ultra nvidia-persistenced: device :01:00.0 - registered Jun 5 13:24:57 ultra nvidia-persistenced: Local RPC services initialized Jun 5 13:24:57 ultra systemd[1]: Started NVIDIA Persistence Daemon. Jun 5 13:24:57 ultra nvidia-persistenced: Received signal 15 Jun 5 13:24:57 ultra systemd[1]: Stopping NVIDIA Persistence Daemon... Jun 5 13:24:57 ultra kernel: [ 183.646973] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 465.24.02 Thu Apr 8 17:50:51 UTC 2021 Jun 5 13:24:57 ultra kernel: [ 183.648525] [drm] [nvidia-drm] [GPU ID 0x0100] Loading driver Jun 5 13:24:57 ultra kernel: [ 183.648527] [drm] Initialized nvidia-drm 0.0.0 20160202 for :01:00.0 on minor 0 Jun 5 13:24:57 ultra nvidia-persistenced: Socket closed. Jun 5 13:24:57 ultra nvidia-persistenced: PID file unlocked. Jun 5 13:24:57 ultra nvidia-persistenced: PID file closed. Jun 5 13:24:57 ultra nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced Jun 5 13:24:57 ultra nvidia-persistenced: Shutdown (10237) Jun 5 13:24:57 ultra systemd[1]: nvidia-persistenced.service: Succeeded. Jun 5 13:24:57 ultra systemd[1]: Stopped NVIDIA Persistence Daemon. Jun 5 13:24:58 ultra kernel: [ 183.663123] nvidia_uvm: module uses symbols from proprietary module nvidia, inheriting taint. Jun 5 13:24:58 ultra kernel: [ 183.665101] nvidia-uvm: Loaded the UVM driver, major device number 510. Jun 5 13:24:58 ultra systemd-udevd[10242]: nvidia_uvm: Process '/sbin/create-uvm-dev-node' failed with exit code 1. Jun 5 13:24:58 ultra systemd[1]: Starting NVIDIA Persistence Daemon... Jun
[Kernel-packages] [Bug 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed- groovy'. 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-groovy -- 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/1896578 Title: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1896578 [Impact] Block discard is very slow on Raid10, which causes common use cases which invoke block discard, such as mkfs and fstrim operations, to take a very long time. For example, on a i3.8xlarge instance on AWS, which has 4x 1.9TB NVMe devices which support block discard, a mkfs.xfs operation on Raid 10 takes between 8 to 11 minutes, where the same mkfs.xfs operation on Raid 0, takes 4 seconds. The bigger the devices, the longer it takes. The cause is that Raid10 currently uses a 512k chunk size, and uses this for the discard_max_bytes value. If we need to discard 1.9TB, the kernel splits the request into millions of 512k bio requests, even if the underlying device supports larger requests. For example, the NVMe devices on i3.8xlarge support 2.2TB of discard at once: $ cat /sys/block/nvme0n1/queue/discard_max_bytes 2199023255040 $ cat /sys/block/nvme0n1/queue/discard_max_hw_bytes 2199023255040 Where the Raid10 md device only supports 512k: $ cat /sys/block/md0/queue/discard_max_bytes 524288 $ cat /sys/block/md0/queue/discard_max_hw_bytes 524288 If we perform a mkfs.xfs operation on the /dev/md array, it takes over 11 minutes and if we examine the stack, it is stuck in blkdev_issue_discard() $ sudo cat /proc/1626/stack [<0>] wait_barrier+0x14c/0x230 [raid10] [<0>] regular_request_wait+0x39/0x150 [raid10] [<0>] raid10_write_request+0x11e/0x850 [raid10] [<0>] raid10_make_request+0xd7/0x150 [raid10] [<0>] md_handle_request+0x123/0x1a0 [<0>] md_submit_bio+0xda/0x120 [<0>] __submit_bio_noacct+0xde/0x320 [<0>] submit_bio_noacct+0x4d/0x90 [<0>] submit_bio+0x4f/0x1b0 [<0>] __blkdev_issue_discard+0x154/0x290 [<0>] blkdev_issue_discard+0x5d/0xc0 [<0>] blk_ioctl_discard+0xc4/0x110 [<0>] blkdev_common_ioctl+0x56c/0x840 [<0>] blkdev_ioctl+0xeb/0x270 [<0>] block_ioctl+0x3d/0x50 [<0>] __x64_sys_ioctl+0x91/0xc0 [<0>] do_syscall_64+0x38/0x90 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] Xiao Ni has developed a patchset which resolves the block discard performance problems. These commits have now landed in 5.13-rc1. commit cf78408f937a67f59f5e90ee8e6cadeed7c128a8 Author: Xiao Ni Date: Thu Feb 4 15:50:43 2021 +0800 Subject: md: add md_submit_discard_bio() for submitting discard bio Link: https://github.com/torvalds/linux/commit/cf78408f937a67f59f5e90ee8e6cadeed7c128a8 commit c2968285925adb97b9aa4ede94c1f1ab61ce0925 Author: Xiao Ni Date: Thu Feb 4 15:50:44 2021 +0800 Subject: md/raid10: extend r10bio devs to raid disks Link: https://github.com/torvalds/linux/commit/c2968285925adb97b9aa4ede94c1f1ab61ce0925 commit f2e7e269a7525317752d472bb48a549780e87d22 Author: Xiao Ni Date: Thu Feb 4 15:50:45 2021 +0800 Subject: md/raid10: pull the code that wait for blocked dev into one function Link: https://github.com/torvalds/linux/commit/f2e7e269a7525317752d472bb48a549780e87d22 commit d30588b2731fb01e1616cf16c3fe79a1443e29aa Author: Xiao Ni Date: Thu Feb 4 15:50:46 2021 +0800 Subject: md/raid10: improve raid10 discard request Link: https://github.com/torvalds/linux/commit/d30588b2731fb01e1616cf16c3fe79a1443e29aa commit 254c271da0712ea8914f187588e0f81f7678ee2f Author: Xiao Ni Date: Thu Feb 4 15:50:47 2021 +0800 Subject: md/raid10: improve discard request for far layout Link: https://github.com/torvalds/linux/commit/254c271da0712ea8914f187588e0f81f7678ee2f There is also an additional commit which is required, and was merged after "md/raid10: improve raid10 discard request" was merged. The following commit enables Radid10 to use large discards, instead of splitting into many bios, since the technical
[Kernel-packages] [Bug 1887661] Re: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed- groovy'. 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-groovy -- 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/1887661 Title: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.6 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.6 source package in Impish: Invalid Bug description: [Impact] The pmtu.sh test in net from ubuntu_kernel_selftests will be marked as failed even there is no obvious failure message from the test: $ sudo ./pmtu.sh TEST: ipv4: PMTU exceptions [ OK ] TEST: ipv6: PMTU exceptions [ OK ] vxlan4 not supported TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] vxlan4 not supported TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] geneve4 not supported TEST: IPv4 over geneve4: PMTU exceptions [SKIP] geneve4 not supported TEST: IPv6 over geneve4: PMTU exceptions [SKIP] TEST: IPv4 over geneve6: PMTU exceptions [ OK ] TEST: IPv6 over geneve6: PMTU exceptions [ OK ] TEST: IPv4 over fou4: PMTU exceptions [ OK ] TEST: IPv6 over fou4: PMTU exceptions [ OK ] TEST: IPv4 over fou6: PMTU exceptions [ OK ] TEST: IPv6 over fou6: PMTU exceptions [ OK ] TEST: IPv4 over gue4: PMTU exceptions [ OK ] TEST: IPv6 over gue4: PMTU exceptions [ OK ] TEST: IPv4 over gue6: PMTU exceptions [ OK ] TEST: IPv6 over gue6: PMTU exceptions [ OK ] TEST: vti6: PMTU exceptions [ OK ] TEST: vti4: PMTU exceptions [ OK ] TEST: vti4: default MTU assignment [ OK ] TEST: vti6: default MTU assignment [ OK ] TEST: vti4: MTU setting on link creation [ OK ] TEST: vti6: MTU setting on link creation [ OK ] TEST: vti6: MTU changes on link changes [ OK ] vxlan4 not supported TEST: ipv4: cleanup of cached exceptions [SKIP] TEST: ipv6: cleanup of cached exceptions [ OK ] TEST: ipv4: list and flush cached exceptions [ OK ] TEST: ipv6: list and flush cached exceptions [ OK ] $ echo $? 1 This is because the test script treats all non-zero return code as a failure, thus it will be marked as FAILED when some sub-test got skipped. [Fix] * ef1220a7d4bbdb selftests: pmtu.sh: use $ksft_skip for skipped return code * 2a9d3716b810a4 selftests: pmtu.sh: improve the test result processing This patchset will: 1. Use the kselftest framework skip code $ksft_skip to replace the hardcoded SKIP return code. 2. Improve the result processing, the test will be marked as PASSED if nothing goes wrong and not all the tests were skipped. These have already landed in newer releases and this test does not exist in B, thus we just need this for F/F-OEM-5.6/F-OEM-5.10/G. The first patch needs to be backported (except on F-OEM-5.10) as some test cases were not added yet. The second one can be cherry-picked. [Test] Run this test directly on a patched kernel. The skipped test will cause failure to this test. [Where problems could occur] Changes limited to testing tools, it's unlikely to cause any problem to kernel functions. [Original Bug Report] Issue found on B-5.4 oracle 5.4.0-1021.21~18.04.1 The pmtu.sh test in net from ubuntu_kernel_selftests will be marked as failed even there is no obvious failure message from the test: $ sudo ./pmtu.sh TEST: ipv4: PMTU exceptions [ OK ] TEST: ipv6: PMTU exceptions
[Kernel-packages] [Bug 1920180] Re: Can't detect intel wifi 6235
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed- groovy'. 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-groovy -- 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/1920180 Title: Can't detect intel wifi 6235 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: In Progress Bug description: [Impact] Wifi doesn't work on systems with Centrino Advanced-N 6235 [8086:526a]. [Fix] The patch adds the device ID 0x526A. [Test Case] Wifi works after installing test kernel (#19 & #20 in LP:1920180) [Regression Potential] Low to none. This adds a hardware ID and does not affects systems output such a wifi card. [Note] Patch was also sent for upstream reviews and can be viewed at https://www.spinics.net/lists/stable/msg452937.html == Original descriptions Can't detect Wireless intel advance 6235 03:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6235 [8086:088f] (rev 24) Subsystem: Intel Corporation Centrino Advanced-N 6235 [8086:526a] Flags: fast devsel, IRQ 255 Memory at e040 (64-bit, non-prefetchable) [size=8K] Capabilities: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sgo1245 F pulseaudio /dev/snd/controlC0: sgo1245 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-03-15 (4 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: LENOVO 20AWS0DS0T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=7bbc36d4-b65d-4291-a3b9-dc840a88f20a ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 RelatedPackageVersions: linux-restricted-modules-5.4.0-67-generic N/A linux-backports-modules-5.4.0-67-generic N/A linux-firmware1.187.10 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no Tags: ulyssa Uname: Linux 5.4.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: GLETA1WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AWS0DS0T dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLETA1WW(2.55):bd04/20/2020:svnLENOVO:pn20AWS0DS0T:pvrThinkPadT440p:rvnLENOVO:rn20AWS0DS0T:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AWS0DS0T dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925685] Re: [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed- groovy'. 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-groovy -- 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/1925685 Title: [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Bionic: Won't Fix Status in linux-hwe-5.8 source package in Bionic: Confirmed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.8 source package in Focal: Confirmed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-hwe-5.8 source package in Groovy: Confirmed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Committed Status in linux-hwe-5.8 source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-hwe-5.8 source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Bug description: Filing this with my Kubuntu Focus (kfocus.org) OEM hat on: [Impact] We are having screen flickering and glitching issues with some of our hardware upon wake from suspend. We have worked with our ODM to figure out a fix for this. They had reported there were no issues when running Windows on the same hardware. As such, we tested, and found that this issue first began as a regression in kernel 5.0 (did not exist in kernel 4.18 per our tests). We identified a patch via https://gitlab.freedesktop.org/drm/intel/-/issues/272 in which this has been solved. Per our testing by recompiling the kernel, this completely fixes our hardware issue. As of 4-21, this fix has been merged into the Linux kernel per Timo Aaltonen, and will be included in the kernel in the 5.13 release. Our hardware ships with Kubuntu 20.04 LTS, which means the 5.13 kernel will not see these machines, at least in the forseeable future. As such, we request that this patch be added to the kernel. Per our testing, this patch is straightforward to add and works flawlessly. The patch that works best was created in collaboration with Kai-Heng Feng, is attached to this bug report, and can be found here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+attachment/5491421/+files /drm-intel-both.patch Until this is fixed, we have a whole batch of hardware we cannot sell, so, as an OEM, this is a high priority. [Test Plan] * Install Kubuntu on an affected Kubuntu Focus M2 computer (not in the hands of customers at this time) * Notice screen glitching/flickering after wake-from-suspend. * Install kernel compiled with the attached patch. Boot from patched kernel. * Suspend laptop, resume. No glitches. [Where problems could occur] * Although this solves the problem for us and has been confirmed to work with the Intel developers that developed this patch, it could cause another display type to have problems. This is unlikely as it has been vetted by Intel and by the mainline Linux kernel developers. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1925685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927518] Re: Fix kdump failures
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed- groovy'. 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-groovy -- 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/1927518 Title: Fix kdump failures Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in linux-azure-4.15 package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: Fix Released Status in linux-azure-4.15 source package in Focal: Invalid Status in linux source package in Groovy: Fix Committed Status in linux-azure source package in Groovy: Fix Released Status in linux-azure-4.15 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Committed Status in linux-azure source package in Hirsute: Fix Released Status in linux-azure-4.15 source package in Hirsute: Invalid Bug description: SRU Justification [Impact] Microsoft relayed a customer report of failures when trying to take a kdump. These 3 patches fix the issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/video/fbdev/hyperv_fb.c?id=aa5b7d11c7cb87c266d705b237368985e7171958 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/channel_mgmt.c?id=77db0ec8b7764cb9b09b78066ebfd47b2c0c1909 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/channel_mgmt.c?id=8c2d5e0640e53c14b6240e9bf1e32a2226e6e6ca Patch #1 solves a problem where the “Unable to send packet via vmbus” message is output continuously. But with that problem fixed, the second problem can occur where the kdump kernel panics due to receiving an unexpected VMbus UNLOAD complete message. Patch #2 prevents the UNLOAD complete message from ever occurring in the kdump kernel. But if the UNLOAD complete message does occur at some unexpected time, Patch #3 prevents it from causing a panic. These patches seem worthy of application to all affected master kernels. [Test Plan] Cause a guest kernel to crash and successfully acquire a kdump. [Where problems could occur] The extended Hyper-V wait while flushing could cause side effects. [Other Info] SF: #00310145 https://canonical.lightning.force.com/lightning/r/Case/5004K05pZNNQA2/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926030] Re: IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed- groovy'. 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-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926030 Title: IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49 Status in linux package in Ubuntu: Fix Released Status in linux source package in Groovy: Fix Committed Bug description: [Impact] Patch: * media: rc: fix timeout handling after switch to microsecond durations * media: rc: ite-cir: fix min_timeout calculation Were applied to Groovy with our stable update process (bug 1918516) User reported that IR Remote key press will be repeated for multiple times with these patches applied. Commit 528222d853f92 ("media: rc: harmonize infrared durations to microseconds") that needs to be fixed by these two does not exist in 5.8 kernel. The patch author Matthias Reichl also state these are for 5.10 and onward. [Fix] Revert these two patches for groovy. [Test] Test kernels for G-5.8 / F-5.8 can be found here: https://people.canonical.com/~phlin/kernel/lp-1926030-revert-for-ir/ User Ted L confirmed that F-5.8 test kernel can fix the problem. [Where problems could occur] The chance to cause regression can be considered as low since the original patch that need to be fix by these two patches does not exist in 5.8 at all. [Original Bug Report] I use an IR remote with the ir-keytable package. Everything was working fine until kernel 5.8.0-49 was automatically installed by Software Updater on Ubuntu 20.04.2. When any key is pressed on the remote, the key is repeated about 500 times. The kernel is now 5.8.0-50, and the problem persists. Other users on the MythTV mailing list are reporting the issue, and it appears that the problem is related to changes in the following files: drivers/media/rc/ir-mce_kbd-decoder.c drivers/media/rc/rc-main.c b/drivers/media/rc/rc-main.c drivers/media/rc/serial_ir.c It has been reported that reverting the ir-mce_kbd-decoder.c and rc- main.c files to the older versions fixes the problem. /proc/version_signature > version.log: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 lspci -vnvn: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:590f] (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1043:8694] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore ir-keytable -V: IR keytable control version 1.18.0 lsb_release -rd: Description: Ubuntu 20.04.2 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ted1020 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-09-19 (217 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp3s0no wireless extensions. enp0s31f6 no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=529cae8e-19cd-4732-80d5-b3dca123afc6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 RfKill: Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd mythtv plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/05/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3405 dmi.board.asset.tag: Default
[Kernel-packages] [Bug 1922651] Re: r8152 tx status -71
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed- groovy'. 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-groovy -- 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/1922651 Title: r8152 tx status -71 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: I've bought ThinkPad T14s with a USB-based docking station. Everything is working marvelously, but from time to time the ethernet port on the docking station won't connect. I've discovered the following messages in my dmesg: [ 400.597506] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 401.164370] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 463.168412] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 465.314415] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 529.409871] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 533.718163] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 591.168537] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 594.335383] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 Rebooting the machine doesn't seem to work, turning the ethernet connection off and on doesn't seem to work. I have a dualboot Linux+Windows (one wants to play games from time to time :-p ) and it could be that rebooting from Win to Lin causes this issue, but this needs to be confirmed yet. I will try to power off the computer and/or the docking station, to see whether that would help. I've found numerous bug reports, but they are rather old or may not apply to this situation, therefore I figured it's best to open a new bug report. Thank you so much for your hard work! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-48-generic 5.8.0-48.54 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 6 10:00:29 2021 InstallationDate: Installed on 2021-03-24 (12 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UH001QMX ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-48-generic root=UUID=14a0-0947-4e58-ade1-ad9963053d85 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-48-generic N/A linux-backports-modules-5.8.0-48-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2020 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET61W(1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UH001QMX dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.30 dmi.modalias: dmi:bvnLENOVO:bvrR1CET61W(1.30):bd12/21/2020:br1.30:efr1.30:svnLENOVO:pn20UH001QMX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001QMX:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14s Gen 1 dmi.product.name: 20UH001QMX dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1 dmi.product.version: ThinkPad T14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922651/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed- groovy'. 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-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1928242 Title: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] All of 3 different WD19(TB/SC/DC) docks have 3 Type-A ports and 2 Type-C ports, and there're highspeed Hubs(0bda:5487 and its substream hub 0bda:5413) and Superspeed Hubs (0bda:0487 and its downstream hub 0bda:0413). In the bug description below, we will refer the 2 highspeed hubs as Hub A and Hub A.3, and the 2 superspeed hubs as Hub B and Hub B.3. All devices connected via either Type-A or Type-C ports will connect to either Hub A.3 or Hub B.3. If we connect a wakup enabled device (keyboard) to a Type-A port, the Hub A.3 will fail to activate after exiting s2idle and all downstream devices will not be detected. If we have a superspeed device connected to other Type-A port in addition to the keyboard, this superspeed device actually connects to Hub B.3, and the Hub B.3 will also fails to work after exiting s2idle. If the wakeup enabled device connects via Type-C port, there's no such problem. As a summary, a wakeup enabled device connect to Type-A port will cause the failure of Hub A.3 and Hub B.3. Hub B.3 only fails when a wakeup enabled device and a superspeed device both connect via Type-A port. [Fix] Before the resume failure, the upstream hub(Hub A or B) will hit the timeout problem while doing SetPortFeature(PORT_SUSPEND) to the port of the downstream hub (Hub A.3 or Hub B.3). However, the PORT_SUSPEND bit of the wPortStatus is actually turned on for the Hub A.3, we simply need to make the kernel believe it's already suspended. Then the ClearPortFeature will be done during resume and the problem will go away. The Hub B.3 will be tricky. The PORT_SUSPEND bit is not on after the suspend timeout, but it needs the ClearPortFeature(PORT_SUSPEND) for Hub B.3 to avoid resume failure. It doesn't comply with the USB spec so it's hard to create a generic fix for it. Because it only happens when timeout happens on suspending Hub A.3 and there's a superspeed device connecting to Type-A port, we choose to leave it as-is and try to address it in the future. [Test Case] 1. Make sure that the WD19 connects to the laptop 2. Connect USB keyboard/mouse to USB Type-A ports. 3. Suspend the system 4. Press the Enter key or power button to wake up the system 5. Check if the USB keyboard/mouse are still working Repeat 4 and 5 for > 10 times w/o losing any USB devices. [Where problems could occur] A wakeup enabled device (keyboard) connect to Type-A port will cause the failure of Hub A.3 and Hub B.3 during resume. Hub B.3 only fails when a wakeup enabled device and a superspeed device both connect via Type-A port. All devices connects to Hub A.3 (and B.3 if superspeed device connect via Type-A port) will be lost after resume. [Regression Potential] Minimum. The fix is only triggered when timeout happens during USB port suspend and it follows the standard USB protocol to do either resume or reset_resume. == Original Bug Description == ● Summary Plug in USB mouse and USB keyboard to WD19/WD19DC USB ports near LAN port. Plug dock into SUT and check USB keyboard and mouse work. SUT enter suspend. After 1 min resume SUT, check USB keyboard/mouse function. Sometimes USB keyboard/mouse no function. Isolation: 1. VP on UMA and Discrete 2. When issue occur, both front and back port on WD19 can't work using USB keyboard/mouse but USB Key. ● Reproduce Steps 1.Plug in USB mouse and USB
[Kernel-packages] [Bug 1920944] Re: kvm: properly tear down PV features on hibernate
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed- groovy'. 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-groovy -- 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/1920944 Title: kvm: properly tear down PV features on hibernate Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-aws source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux-aws source package in Groovy: New Status in linux source package in Hirsute: Fix Committed Status in linux-aws source package in Hirsute: New Bug description: [Impact] In LP: #1918694 we applied a fix and a workaround to solve the hibernation issues on c5.18xlarge. The workaround was in the form of a SAUCE patch: "UBUNTU: SAUCE: aws: kvm: double the size of hv_clock_boot" It looks like we can replace this workaround with a proper fix, by applying this patch: http://next.patchew.org/Linux/20210414123544.1060604-1-vkuzn...@redhat.com/ This is required because various PV features (Async PF, PV EOI, steal time) work through memory shared with hypervisor and when we restore from hibernation we must properly tear down all these features to make sure hypervisor doesn't write to stale locations after we jump to the previously hibernated kernel. For this reason it is safe to apply this patch set also to all the generic kernels and not just AWS. [Test plan] This can be easily tested on AWS (but it should be reproduced by hibernating any kvm instance with multiple CPUs). Create a c5.18xlarge instance, run the memory stress test script (the same test script that we are using to stress test hibernation), trigger the hibernate event, trigger the resume event. Repeat a couple of times and the problem is very likely to happen. [Fix] On the AWS kernel replace "UBUNTU: SAUCE: aws: kvm: double the size of hv_clock_boot" with: http://next.patchew.org/Linux/20210414123544.1060604-1-vkuzn...@redhat.com/ For the other kernels, simply apply this patch set. The fix has been tested extensively in the AWS infrastructure with positive results. [Regression potential] This new code introduced by the fix can be executed also when a CPU is put offline, so we may see potential regressions in the KVM CPU hot- plugging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920944/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926517] Re: [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed- groovy'. 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-groovy -- 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/1926517 Title: [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] Whenever the driver is adding a vSES to virtual-phys list it is reinitializing the list head. Hence those vSES devices which were added previously are lost. [FIXES] Stop reinitializing the list every time a new vSES device is added. https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=4c51f9569651 CommitID: 4c51f956965120b3441cdd39c358b87daba13e19 [TESTING] Load the mpt3sas driver on the system where Brodcom's HBA 9500 Tri-Mode Storage Adapter (IT HBA Aero/Ventura) is connected to two backplanes (so that two vSES device get configured on the HBA). After loading the driver user should able to access both the vSES devices. Also even after performing host reset operation user must able to access both the vSES devices. i.e. lsscsi must list both the vSES devices after loading the driver and also after performing host reset operation. [REGRESSION RISK] There is no regression risk with this bug fix patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930626] Re: scsi: storvsc: Parameterize number hardware queues
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed- groovy'. 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-groovy -- 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/1930626 Title: scsi: storvsc: Parameterize number hardware queues Status in linux package in Ubuntu: Fix Committed Status in linux-azure package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux-azure source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-azure source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux-azure source package in Impish: Fix Committed Bug description: Microsoft would like to request inclusion of the following patch in the 5.4 and later kernels: a81a38cc6dda ("scsi: storvsc: Parameterize number hardware queues") https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/storvsc_drv.c?id=a81a38cc6ddaf128c7ca9e3f21c243f33c97 This patch adds the ability to set the number of hardware queues with new module parameter, storvsc_max_hw_queues. This functionality is useful in Microsoft Azure) where decreasing the number of hardware queues has been shown to improve performance. https://canonical.lightning.force.com/lightning/r/Case/5004K05qB6EQAU/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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/4.15.0.145.132)
All autopkgtests for the newly accepted linux-meta (4.15.0.145.132) for bionic have finished running. The following regressions have been reported in tests triggered by the package: systemd/237-3ubuntu10.47 (amd64) linux/4.15.0-145.149 (amd64, ppc64el, arm64, s390x, i386) 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 [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 1883840] Re: Double free in DCCP module causing kernel panic
Hey guys, I know its been a while but you made a small mistake in : https://ubuntu.com/security/CVE-2020-16119 and all other security notices that you mention me, you wrote my name wrong my name is Hadar Manor and not 'Hador'. I don't know if its a lot to ask but it would be nice if you will fix my name in the advisories to 'Hadar Manor'. Thank you, and have a nice week :) -- 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/1883840 Title: Double free in DCCP module causing kernel panic Status in linux package in Ubuntu: Fix Released Bug description: The problem is when the sock object gets cloned via dccp_create_openreq_child(), it gives all its attributes to the child sock object, and no reference counter is taken for the object dccps_hc_tx_ccid. If one of the sock objects (the parent or the cahild) is closes or disconnected, it frees the target objects dccps_hc_tx_ccid and provides us a dagling pointer in the other sock object. This causes an exploitable double free for an object contains function pointers. We can free dccps_hc_tx_ccid by calling connect(AF_UNSPEC),then spray the heap with other allocations, then call close() we'll potentially have a RIP control. This chunk of code is the responsible of freeing dccps_hc_tx_ccid, if called again it will call ccid_hc_tx_exit() from a freed object void ccid_hc_tx_delete(struct ccid *ccid, struct sock *sk) { if (ccid != NULL) { if (ccid->ccid_ops->ccid_hc_tx_exit != NULL) ccid->ccid_ops->ccid_hc_tx_exit(sk); // <-- Calling a function pointer kmem_cache_free(ccid->ccid_ops->ccid_hc_tx_slab, ccid); } } disassembly : (gdb) disas ccid_hc_tx_delete Dump of assembler code for function ccid_hc_tx_delete: 0x81a7a3a0 <+0>: test rdi,rdi 0x81a7a3a3 <+3>: je 0x81a7a3cd 0x81a7a3a5 <+5>: push rbx 0x81a7a3a6 <+6>: movrbx,rdi 0x81a7a3a9 <+9>: movrdi,rsi 0x81a7a3ac <+12>:movrax,QWORD PTR [rbx] 0x81a7a3af <+15>:movrdx,QWORD PTR [rax+0x80]<— rax points to a freed object 0x81a7a3b6 <+22>:test rdx,rdx 0x81a7a3b9 <+25>:je 0x81a7a3c0 0x81a7a3bb <+27>:call rdx // <-- arbitrary call 0x81a7a3bd <+29>:movrax,QWORD PTR [rbx] 0x81a7a3c0 <+32>:movrsi,rbx 0x81a7a3c3 <+35>:movrdi,QWORD PTR [rax+0x18] 0x81a7a3c7 <+39>:poprbx 0x81a7a3c8 <+40>:jmp0x811fb980 0x81a7a3cd <+45>:repz ret End of assembler dump. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883840/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930980] [NEW] Hang on loading initial ramdisk on kernels 5.4.0-72+, 5.11.0-16+ with nvidia drivers 440+
Public bug reported: Affected Ubuntu Versions: Release: 20.04 Kernel: 5.4.0-73,74 Nvidia Driver: 440,450,460,465 Kernel: 5.4.0-72 Nvidia Driver: 460, 465 Release: 21.04 Kernel: 5.11.0-16,18 Nvidia Driver: 440, 450, 460, 465 For 21.04 with all kernels, driver 390 works correctly Issue occurs during bootup where after starting to load the initial ramdisk, the system hangs indefinitely with no output. Booting in recovery mode and examining the logs, there is a series of bug messages. Updating motherboard bios to latest had no effect. Note: This exact hardware setup worked as recently as June 2, 2021 on ubuntu 20.04. After applying the latest set of OS updates and rebooting, the issue began occurring. Trace follows: Jun 4 21:51:06 ultra kernel: [7.262411] BUG: kernel NULL pointer dereference, address: Jun 4 21:51:06 ultra kernel: [7.262412] #PF: supervisor write access in kernel mode Jun 4 21:51:06 ultra kernel: [7.262413] #PF: error_code(0x0002) - not-present page Jun 4 21:51:06 ultra kernel: [7.262414] PGD 0 P4D 0 Jun 4 21:51:06 ultra kernel: [7.262415] Oops: 0002 [#1] SMP NOPTI Jun 4 21:51:06 ultra kernel: [7.262416] CPU: 3 PID: 998 Comm: Xorg Tainted: P IO 5.11.0-18-generic #19-Ubuntu Jun 4 21:51:06 ultra kernel: [7.262417] Hardware name: ASUS System Product Name/PRIME Z390-A, BIOS 1802 12/01/2020 Jun 4 21:51:06 ultra kernel: [7.262418] RIP: 0010:_nv008453rm+0xa8/0x5f0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.262673] Code: 8b 84 24 60 04 00 00 ba 01 00 00 00 4c 89 e6 48 89 df 4d 89 e5 e8 c8 64 c4 e0 41 89 c6 45 85 f6 0f 84 3c 02 00 00 48 8b 45 08 <4c> 89 28 5b 44 89 f0 41 5c 41 5d 41 5e 41 5f 48 83 c5 40 c3 0f 1f Jun 4 21:51:06 ultra kernel: [7.262675] RSP: 0018:be91018bf8c8 EFLAGS: 00010282 Jun 4 21:51:06 ultra kernel: [7.262676] RAX: RBX: a08c06e14008 RCX: Jun 4 21:51:06 ultra kernel: [7.262676] RDX: 0020 RSI: d9a4 RDI: a08c06e14008 Jun 4 21:51:06 ultra kernel: [7.262677] RBP: a08c0a0c5db0 R08: 0025 R09: a08c0a0c5d18 Jun 4 21:51:06 ultra kernel: [7.262678] R10: a08c06e14008 R11: a08c06e150a0 R12: a08c07440008 Jun 4 21:51:06 ultra kernel: [7.262678] R13: a08c07440010 R14: R15: a08c0a0c5de0 Jun 4 21:51:06 ultra kernel: [7.262679] FS: 7f7d29194a40() GS:a09b2dac() knlGS: Jun 4 21:51:06 ultra kernel: [7.262680] CS: 0010 DS: ES: CR0: 80050033 Jun 4 21:51:06 ultra kernel: [7.262680] CR2: CR3: 00010f6fe006 CR4: 003706e0 Jun 4 21:51:06 ultra kernel: [7.262681] DR0: DR1: DR2: Jun 4 21:51:06 ultra kernel: [7.262681] DR3: DR6: fffe0ff0 DR7: 0400 Jun 4 21:51:06 ultra kernel: [7.262682] Call Trace: Jun 4 21:51:06 ultra kernel: [7.262684] ? _nv032332rm+0x10c/0x280 [nvidia] Jun 4 21:51:06 ultra kernel: [7.262884] ? _nv032330rm+0x145/0x180 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263075] ? _nv014647rm+0x213/0x300 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263255] ? _nv014704rm+0x6dd/0xf80 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263435] ? _nv026937rm+0x226/0x4e0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263616] ? _nv016954rm+0x4a8/0x5e0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263819] ? _nv016956rm+0xdd/0x230 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264009] ? _nv09rm+0xcd/0x1d0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264256] ? _nv022467rm+0x30/0x60 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264394] ? _nv000701rm+0x143f/0x2100 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264552] ? rm_init_adapter+0xc5/0xe0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264709] ? nv_open_device+0x122/0x8e0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264805] ? nvidia_open+0x2b7/0x560 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264901] ? nvidia_frontend_open+0x58/0xa0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264996] ? chrdev_open+0xf7/0x220 Jun 4 21:51:06 ultra kernel: [7.264999] ? cdev_device_add+0x90/0x90 Jun 4 21:51:06 ultra kernel: [7.265000] ? do_dentry_open+0x156/0x370 Jun 4 21:51:06 ultra kernel: [7.265001] ? vfs_open+0x2d/0x30 Jun 4 21:51:06 ultra kernel: [7.265003] ? do_open+0x1c3/0x340 Jun 4 21:51:06 ultra kernel: [7.265004] ? path_openat+0x10a/0x1d0 Jun 4 21:51:06 ultra kernel: [7.265005] ? do_filp_open+0x8c/0x130 Jun 4 21:51:06 ultra kernel: [7.265007] ? __check_object_size+0x1c/0x20 Jun 4 21:51:06 ultra kernel: [7.265009] ? do_sys_openat2+0x9b/0x150 Jun 4 21:51:06 ultra kernel: [7.265010] ? __x64_sys_openat+0x56/0x90 Jun 4 21:51:06 ultra kernel: [7.265012] ?
[Kernel-packages] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
I just solved my 30bit problem with an Displayport to HDMI adapter[1]. Now the screens operate at 4k 60Hz 24bits in Linux and no more screen corruption. -- 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/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 Status in gnome-control-center: Unknown Status in HWE Next: New Status in Linux: Unknown Status in Mutter: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Won't Fix Status in xorg-server package in Ubuntu: Invalid Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. existed upstream bug: - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927832] Re: [radeon] Static effect on HDMI out using kernel 5.11 and later (but 5.8.0-50-generic works)
Kernel version 5.11.0-18 fixed this issue, should I mark it resolved/fixed? -- 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/1927832 Title: [radeon] Static effect on HDMI out using kernel 5.11 and later (but 5.8.0-50-generic works) Status in linux package in Ubuntu: Confirmed Bug description: lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 package version : kernel-image 5.11.0-16-generic what I expect to happen : to show my desktop correctly on second hdmi monitor what happens : static effect like shown in attached photo Since upgrade to hirsute (21.04) from groovy (20.10) my hdmi port on my graphic card stopped to work correctly and started to display static effect on second monitor, as you can see from the attached photo. Here it is mine videocards: Code: $ lspci | grep VGA 01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470] I was able to test it with 3 different kernels : Code: 5.12.1-051201-generic # last mainline kernel 5.11.0-16-generic # last official kernel from hirsute 5.8.0-50-generic # probably a old kernel still there from groovy Only the older one, 5.8.0-50-generic was working correctly with dual monitor with no issues. Kind regards ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,move,gnomecompat,vpswitch,place,grid,regex,session,snap,mousepoll,imgpng,resize,wall,animation,unitymtgrabhandles,expo,ezoom,fade,workarounds,scale,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 8 18:45:37 2021 DistUpgraded: 2021-04-22 22:22:18,672 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Failed to execute child process “./xorg_fix_proprietary.py”: Failed to execve: File o directory non esistente (1)) DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.18, 5.11.0-16-generic, x86_64: installed virtualbox, 6.1.18, 5.8.0-50-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RS880M [Mobility Radeon HD 4225/4250] [103c:1441] Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470] [1002:68e0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Park [Mobility Radeon HD 5430/5450/5470] [103c:1441] InstallationDate: Installed on 2019-10-26 (560 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=a5324660-5421-487c-ad0f-b562bd39c622 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-04-22 (15 days ago) dmi.bios.date: 02/25/2013 dmi.bios.release: 15.41 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.29 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1441 dmi.board.vendor: Hewlett-Packard dmi.board.version: 67.33 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.ec.firmware.release: 103.51 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.29:bd02/25/2013:br15.41:efr103.51:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr059C1124301020100:rvnHewlett-Packard:rn1441:rvr67.33:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.sku: XD610EA#ABZ dmi.product.version: 059C1124301020100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-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 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1930976] Re: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers
** Also affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New -- 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/1930976 Title: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers Status in nvidia-graphics-drivers-460 package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: Kernel: 5.8.0-55 The last kernel destroyed my Ubuntu 20.04.02 installation, something went wrong with some kernel packages. It seems like Ubuntu is unable to find my video card correctly and the device drivers from Nvidia don't seem to work anymore. I had to do a clean installation, but even that doesn't solve the problem. I think this is a serious issue that needs to be looked into. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sat Jun 5 16:50:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation Device [10de:2206] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:403f] InstallationDate: Installed on 2021-06-05 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=4984fe2f-d45f-4734-884c-2426bcf10ca4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33j dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33j:bd04/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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.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: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1930976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925522] Re: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
I have a problem with DisplayPort on the new drivers too and created https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-465/+bug/1930733 about it. -- 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/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-465 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Released Status in fabric-manager-460 source package in Bionic: Fix Released Status in libnvidia-nscq-450 source package in Bionic: Fix Released Status in libnvidia-nscq-460 source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Committed Status in fabric-manager-450 source package in Focal: Fix Released Status in fabric-manager-460 source package in Focal: Fix Released Status in libnvidia-nscq-450 source package in Focal: Fix Released Status in libnvidia-nscq-460 source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-465 source package in Focal: Fix Released Status in nvidia-settings source package in Focal: Fix Committed Status in fabric-manager-450 source package in Groovy: Fix Committed Status in fabric-manager-460 source package in Groovy: Fix Committed Status in libnvidia-nscq-450 source package in Groovy: Fix Committed Status in libnvidia-nscq-460 source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Released Status in nvidia-settings source package in Groovy: Fix Committed Status in fabric-manager-450 source package in Hirsute: Fix Released Status in fabric-manager-460 source package in Hirsute: Fix Released Status in libnvidia-nscq-450 source package in Hirsute: Fix Released Status in libnvidia-nscq-460 source package in Hirsute: Fix Released Status in linux-restricted-modules source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Released Status in nvidia-settings source package in Hirsute: Fix Committed Bug description: Introduce the new NVIDIA 465 driver series, fabric-manager and libnvidia-nscq. Also migrate the UDA 450 series to the 460 series. [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] == 450-server == * New upstream release (LP: #1925522). - Fixed an issue with the NSCQ library that caused clients such as DCGM to fail to load the library. Since the NSCQ library version needs to match the driver
[Kernel-packages] [Bug 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
I'm using a Dell 7567 with a GTX 1050 TI and even with a untested version (465.27) the issue still here. ~ nvidia-smi Sat Jun 5 11:38:05 2021 +-+ | NVIDIA-SMI 465.27 Driver Version: 465.27 CUDA Version: 11.3 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 NVIDIA GeForce ... Off | :01:00.0 Off | N/A | | N/A 55CP0N/A / N/A |292MiB / 4040MiB | 2% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 1370 G /usr/lib/xorg/Xorg 45MiB | |0 N/A N/A 2355 G /usr/lib/xorg/Xorg103MiB | |0 N/A N/A 2634 G /usr/bin/gnome-shell 103MiB | |0 N/A N/A 3186 G ...A= --shared-files 29MiB | +-+ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1911055 Title: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: After a recent update to nvidia-460, suspend then resume results in a black screen, then a hang for around 120 seconds, and then the text: nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer dmesg shows: [ 188.352670] ACPI: Waking up from system sleep state S3 ... [ 309.142164] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 309.142319] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.142165] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 313.142348] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.151885] acpi LNXPOWER:08: Turning OFF [ 313.151898] acpi LNXPOWER:04: Turning OFF [ 313.152351] acpi LNXPOWER:03: Turning OFF [ 313.153064] acpi LNXPOWER:02: Turning OFF ... [ 325.010192] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DELL 2209WA (HDMI-0) [ 325.010577] BUG: kernel NULL pointer dereference, address: 0050 [ 325.010579] #PF: supervisor read access in kernel mode [ 325.010580] #PF: error_code(0x) - not-present page [ 325.010580] PGD 0 P4D 0 [ 325.010582] Oops: [#1] SMP PTI [ 325.010583] CPU: 9 PID: 2247 Comm: Xorg Tainted: P O 5.4.0-60-generic #67-Ubuntu [ 325.010584] Hardware name: Razer Blade/DANA_MB, BIOS 01.01 08/31/2018 [ 325.010595] RIP: 0010:_nv000112kms+0xd/0x30 [nvidia_modeset] [ 325.010596] Code: 16 00 74 06 83 7e 0c 02 77 03 31 c0 c3 c7 46 0c 01 00 00 00 b8 01 00 00 00 c3 0f 1f 00 0f b7 46 04 0f b7 56 08 39 d0 0f 47 c2 <3b> 47 18 77 06 83 7e 10 02 77 08 31 c0 c3 0f 1f 44 00 00 c7 46 10 [ 325.010597] RSP: 0018:b89542e5b8a8 EFLAGS: 00010246 [ 325.010598] RAX: 0280 RBX: 0038 RCX: 03ff [ 325.010598] RDX: 0280 RSI: b89542e5bba0 RDI: 0038 [ 325.010599] RBP: b89542e5b9c8 R08: R09: c379e440 [ 325.010600] R10: R11: R12: b89542e5b948 [ 325.010600] R13: b89542e5b948 R14: b89542e5b930 R15: c3a50e60 [ 325.010601] FS:
[Kernel-packages] [Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot
*** This bug is a duplicate of bug 1872159 *** https://bugs.launchpad.net/bugs/1872159 Hi, I had also same problem (after update to Ubuntu 20.04, had only blank screen on my monitor), but recently found a 'solution' accidentally! MAYBE, it is the same problem like mine! My monitor is being connected via 'D-Sub' and 'HDMI' cables. It seems, separate monitor instance is created in display settings ("Single Display") for each connection type and you won't see anything in the monitor if you had selected a wrong monitor instance (non-HDMI). In my case, I had selected 'D-Sub' monitor instance and 'HDMI' output didn't work or I had blank screen for HDMI input. Seems now I have selected the correct monitor instance for HDMI. So, maybe you also had the same issue that you had selected a 'non-HDMI' monitor instance! -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921632] Re: build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later
** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New -- 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/1921632 Title: build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later Status in linux package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: New Status in linux source package in Hirsute: Fix Committed Status in linux-oracle source package in Hirsute: New Status in linux source package in Impish: Confirmed Status in linux-oracle source package in Impish: New Bug description: [Impact] Ubuntu users ran the kernel on the Dell soundwire audio machines, the dmesg shows the audio mchine driver is not found, then the audio fails to initialize [Fix] Enable the intel soundwire audio machine driver and some related codec driver. [Test] run fakeroot debian/rules clean updateconfigs, and check the config.common.ubuntu, the content is not changed. Build the kernel with this patch applied, the soundwire audio machine driver is built. [Where problems could occur] This could possibly introduce the building failure, I tested it, so far no failure. See also https://bugzilla.kernel.org/show_bug.cgi?id=212465 Default kernel from https://cdimage.ubuntu.com/kubuntu/daily-live/20210327/ and also upstream kernel https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.12-rc4/ tested and both do not work. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-28 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210326) MachineType: HP HP Spectre x360 Convertible 13-aw2xxx Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-11-generic root=/dev/mapper/sys-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-11-generic N/A linux-backports-modules-5.11.0-11-generic N/A linux-firmware 1.195 Tags: hirsute Uname: Linux 5.11.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 15.10 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8709 dmi.board.vendor: HP dmi.board.version: 31.30 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 31.30 dmi.modalias: dmi:bvnAMI:bvrF.10:bd12/08/2020:br15.10:efr31.30:svnHP:pnHPSpectrex360Convertible13-aw2xxx:pvr:rvnHP:rn8709:rvr31.30:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-aw2xxx dmi.product.sku: 2G2D8EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929455] Re: Hirsute update: v5.11.21 upstream stable release
** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New -- 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/1929455 Title: Hirsute update: v5.11.21 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: New Status in linux source package in Hirsute: Fix Committed Status in linux-oracle source package in Hirsute: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.11.21 upstream stable release from git://git.kernel.org/ Bluetooth: verify AMP hci_chan before amp_destroy bluetooth: eliminate the potential race condition when removing the HCI controller net/nfc: fix use-after-free llcp_sock_bind/connect Revert "USB: cdc-acm: fix rounding error in TIOCSSERIAL" usb: roles: Call try_module_get() from usb_role_switch_find_by_fwnode() tty: moxa: fix TIOCSSERIAL jiffies conversions tty: amiserial: fix TIOCSSERIAL permission check USB: serial: usb_wwan: fix TIOCSSERIAL jiffies conversions staging: greybus: uart: fix TIOCSSERIAL jiffies conversions USB: serial: ti_usb_3410_5052: fix TIOCSSERIAL permission check staging: fwserial: fix TIOCSSERIAL jiffies conversions tty: moxa: fix TIOCSSERIAL permission check staging: fwserial: fix TIOCSSERIAL permission check drm: bridge: fix LONTIUM use of mipi_dsi_() functions usb: typec: tcpm: Address incorrect values of tcpm psy for fixed supply usb: typec: tcpm: Address incorrect values of tcpm psy for pps supply usb: typec: tcpm: update power supply once partner accepts usb: xhci-mtk: remove or operator for setting schedule parameters usb: xhci-mtk: improve bandwidth scheduling with TT ASoC: samsung: tm2_wm5110: check of of_parse return value ASoC: Intel: kbl_da7219_max98927: Fix kabylake_ssp_fixup function ASoC: tlv320aic32x4: Register clocks before registering component ASoC: tlv320aic32x4: Increase maximum register in regmap MIPS: pci-mt7620: fix PLL lock check MIPS: pci-rt2880: fix slot 0 configuration FDDI: defxx: Bail out gracefully with unassigned PCI resource for CSR PCI: Allow VPD access for QLogic ISP2722 KVM: x86: Defer the MMU unload to the normal path on an global INVPCID PCI: keystone: Let AM65 use the pci_ops defined in pcie-designware-host.c PM / devfreq: Unlock mutex and free devfreq struct in error path soc/tegra: regulators: Fix locking up when voltage-spread is out of range iio: inv_mpu6050: Fully validate gyro and accel scale writes iio: sx9310: Fix write_.._debounce() iio:accel:adis16201: Fix wrong axis assignment that prevents loading iio:adc:ad7476: Fix remove handling iio: sx9310: Fix access to variable DT array sc16is7xx: Defer probe if device read fails phy: cadence: Sierra: Fix PHY power_on sequence misc: lis3lv02d: Fix false-positive WARN on various HP models phy: ti: j721e-wiz: Invoke wiz_init() before of_platform_device_create() misc: vmw_vmci: explicitly initialize vmci_notify_bm_set_msg struct misc: vmw_vmci: explicitly initialize vmci_datagram payload selinux: add proper NULL termination to the secclass_map permissions x86, sched: Treat Intel SNC topology as default, COD as exception async_xor: increase src_offs when dropping destination page md/bitmap: wait for external bitmap writes to complete during tear down md-cluster: fix use-after-free issue when removing rdev md: split mddev_find md: factor out a mddev_find_locked helper from mddev_find md: md_open returns -EBUSY when entering racing area md: Fix missing unused status line of /proc/mdstat MIPS: generic: Update node names to avoid unit addresses mt76: mt7615: use ieee80211_free_txskb() in mt7615_tx_token_put() ipw2x00: potential buffer overflow in libipw_wx_set_encodeext() cfg80211: scan: drop entry from hidden_list on overflow rtw88: Fix array overrun in rtw_get_tx_power_params() mt76: fix potential DMA mapping leak FDDI: defxx: Make MMIO the configuration default except for EISA drm/qxl: use ttm bo priorities drm/ingenic: Fix non-OSD mode drm/panfrost: Clear MMU irqs before handling the fault drm/panfrost: Don't try to map pages that are already mapped drm/radeon: fix copy of uninitialized variable back to userspace drm/dp_mst: Revise broadcast msg lct & lcr drm/dp_mst: Set CLEAR_PAYLOAD_ID_TABLE as broadcast drm: bridge: fix ANX7625 use of mipi_dsi_() functions drm: bridge/panel: Cleanup connector on
[Kernel-packages] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
I came across this bug because of my problem which I described in https://askubuntu.com/questions/1314639/weird-graphics-artifacts- monitor-off-with-ubuntu-20-04-and-nvidia-rtx-5000/1343876#1343876 In my case the Dell monitors tell, they can support 30bit. I came to the conclusion, that the dockingstation's Displayports cannot handle 30bit which leads to strange screen artifacts. However, the HDMI port of the dockingstation outputs 24bits and I have no screen corruption, connecting them directly to laptop is also no problem. In Windows the output is limited at 24bits and the output is reliable. xrandr with "max bpc" 8" is not working me and brings strange errors. Is there any other way to tell Linux system to limit to 24bits? Even before the Desktop appears the console has already switched to 30 bit (according to Monitor OSD info) without any EDID hacking? The Laptop is used daily across different dockingstations with different monitors (Home/Work) System config: - Dell Precision 15" 7540, Xeon E-2286M@2.4GHz, 128 GB ECC RAM, NVIDIA Quadro RTX 5000 16GB VRAM - Dockingstations at Home and offices: WD19DC - Dockingstation 1 WD19DC: 2xDell 43' U4320Q - Dockingstation 2 WD19DC: 2xDellxU3818DW, 37.5" + Laptopdisplay ** Attachment added: "Edid of Dell 43' U4320Q" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890772/+attachment/5502614/+files/edid_U4320Q_Linux.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 Status in gnome-control-center: Unknown Status in HWE Next: New Status in Linux: Unknown Status in Mutter: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Won't Fix Status in xorg-server package in Ubuntu: Invalid Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. existed upstream bug: - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1930941] Re: upgrade ALSA libraries to version 1.2.5
** Package changed: linux (Ubuntu) => alsa-lib -- 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/1930941 Title: upgrade ALSA libraries to version 1.2.5 Status in ALSA Libraries: New Bug description: Please build the latest alsa libraries (version 1.2.5) for impish/ upgrade from version 1.2.4 libasound2 1.2.4-1.1ubuntu2 libasound2-data 1.2.4-1.1ubuntu2 alsa-utils 1.2.4-1ubuntu3 alsa-topology-conf 1.2.4-1 alsa-ucm-conf 1.2.4-2ubuntu1.1 alsa-tools 1.2.2-1 alsa-base 1.0.25+dfsg-0ubuntu7 https://alsa-project.org/wiki/Main_Page See also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632/comments/48 Modern hardware (HP spectre X360) seems to need the latest alsa libraries and configurations. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-lib/+bug/1930941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928679] Re: Support importing mokx keys into revocation list from the mok table
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1928679 Title: Support importing mokx keys into revocation list from the mok table Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx) which revokes many Ubuntu kernel hashes and 2012 signing key. * Kernel should import those into it's %:.blacklist keyring such that it prohibits signed kexec of the revoked kernels. * v5.13-rc1 kernel has learned how to import mokx and how to import full certs into the %:.blacklist keyring. * However, it only does so by reading MokListXRT efi variable. * Due to the large size of Ubuntu's vendor-dbx, shim does not create MokListXRT efi variable, but instead creates MokListXRT1 MokListXRT2 MokListXRT3 which currently v5.13-rc1 kernel cannot read. Shim also exposes MokListXRT via mokvar table, which is easier to parse and contains all the revocations in full. Kernel needs a patch to read MokListXRT via mokvar table. * We have two options on how to proceed from here, either we include the same hashes and certs as our vendordbx in in the kernel as revocation list, or we fix kernel to read MokListXRT via mokvar table * The above is known as CVE-2020-26541 * Separately it would be nice to add informational dmesg messages when revoking signing certificates, as a good indication that signing key rotation events have happened and have been applied correctly. [Test Plan] * Boot kernel with 15.4 based Ubuntu shim * Install keyutils package * Execute $ sudo keyctl list %:.blacklist it should list in exccess of 300+ hash entries. It also must list assymetric Canonical signing key from 2012. * Separately check dmesg to observe that asymmetric canonical signing key from 2012 is revoked. [Where problems could occur] * EFI variable storage can be full thus preventing shim to mirror efivars and the moktable. On decent hardware this should not happen, but has been observed to be corrupted on some older EDKII based OVMF instances with small EFI variable storage space (pre-4MB). [Other Info] * The patches to fix the above have been submitted upstream https://lore.kernel.org/keyrings/20210512153100.285169-1-dimitri.led...@canonical.com/ https://lore.kernel.org/keyrings/20210512110302.262104-1-dimitri.led...@canonical.com/ This will now be submitted as SAUCE patches for the Ubuntu UNSTABLE kernel, until accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929027] Re: drm/i915: Drop force_probe requirement for ADL-S
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929027 Title: drm/i915: Drop force_probe requirement for ADL-S Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: [SRU Justification] [Impact] ADL-S i915 PCI ID has been in v5.13-rc1 in commit 0883d63b19bbd ("drm/i915/adl_s: Add ADL-S platform info and PCI ids"), but it is marked require_force_probe currently, therefore early phase development takes an extra i915.force_probe=4680 boot parameter to enable i915. [Fix] Intel should remove this flag sometime later when ADL-S drm is stable enough. But before that, we can simply remove that flag from adl_s_info in drivers/gpu/drm/i915/i915_pci.c. [Test Case] i915 should be loaded automatically with patched kernel, so do: $ lsmod|grep i915 i915 [Where problems could occur] While this is still an alpha platform in development in OEM projects, this should not introduce trouble for others. As for ADL, troubles are expected and to be resolved. == original bug description == ADL i915 PCI IDs have been in v5.13-rc1 in commit 0883d63b19bbd ("drm/i915/adl_s: Add ADL-S platform info and PCI ids"), but it is marked require_force_probe. We need drop this requirement from this kernel so that machines being tested don't need to work around it locally. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1601 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (413 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE 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/8p, 2M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 13: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Intel Corporation Alder Lake Client Platform Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-2002-oem root=UUID=19a0773e-f33a-413d-bb6a-f1e1cc674a3a ro quiet splash vt.handoff=7 i915.force_probe=4680 ProcVersionSignature: Ubuntu 5.13.0-2002.2+lp1922856.1.i915.mm.bug-oem 5.13.0-rc2 RelatedPackageVersions: linux-restricted-modules-5.13.0-2002-oem N/A linux-backports-modules-5.13.0-2002-oem N/A linux-firmware 1.187.12 RfKill: Tags: focal Uname: Linux 5.13.0-2002-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/25/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLSFWI1.R00.2081.A02.2102250858 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2081.A02.2102250858:bd02/25/2021:efr1.25:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1001002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 1001002B0100 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1929027/+subscriptions -- Mailing list: