[Kernel-packages] [Bug 1929892] Re: [TGL] enable USB-dw3
Tried latest desktop image[1]. USB-dw3 is enabled. Here is the log: u@tgl:~$ dmesg | grep 3fe [ 21.103681] pci :00:0d.1: [8086:9a15] type 00 class 0x0c03fe [ 21.199707] pci :00:14.1: [8086:43ee] type 00 class 0x0c03fe u@tgl:~$ sudo modprobe dwc3_pci u@tgl:~$ lspci -v ... 00:0d.1 USB controller: Intel Corporation Device 9a15 (rev 04) (prog-if fe [USB Device]) Subsystem: Intel Corporation Device 7270 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at 607d20 (64-bit, non-prefetchable) [size=2M] Memory at 607d4f1000 (64-bit, non-prefetchable) [size=4K] Capabilities: [80] Power Management version 3 Capabilities: [90] Vendor Specific Information: Len=14 Kernel driver in use: dwc3-pci Kernel modules: dwc3_pci ... 00:14.1 USB controller: Intel Corporation Device 43ee (prog-if fe [USB Device]) Subsystem: Intel Corporation Device 7270 Flags: fast devsel, IRQ 17 Memory at 607d00 (64-bit, non-prefetchable) [size=2M] Memory at 607d4ed000 (64-bit, non-prefetchable) [size=4K] Capabilities: [80] Power Management version 3 Capabilities: [90] Vendor Specific Information: Len=14 Kernel modules: dwc3_pci u@tgl:~$ dpkg -l | grep linux-image ii linux-image-5.11.0-1012-intel 5.11.0-1012.14 amd64Signed kernel image generic ii linux-image-intel 5.11.0.1012.15 amd64Generic Linux kernel image --- [1] https://private-fileshare.canonical.com/~brian/iotg-focal-desktop-20210813.img -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929892 Title: [TGL] enable USB-dw3 Status in intel: New Status in linux package in Ubuntu: New Status in linux-intel package in Ubuntu: In Progress Bug description: Description Enable USB-dw3 for Tiger Lake Hardware: Tiger Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939528] Re: Need support of Qualcomm WCN6856
PPA: https://launchpad.net/~vicamo/+archive/ubuntu/linux-firmware- staging starting from version 1.187.16+staging.12 ** Description changed: + [SRU Justification] + + [Impact] + + Qualcomm WCN6856 not supported yet. + + [Fix] + + Upstream fixes in thread + https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/ + has been merged in mainline starting from commit 755b1f73173e ("ath11k: + add hw reg support for WCN6855"). + + [Test Case] + TBD. + + [Where problems could occur] + While this introduces a new hardware, it might need further polishments. + + == original bug report == + Wireless Driver support: PCI\VEN_17CB_1103_E0B8105B_01 BT driver support: USB\VID_0489_E0C9_0001 Wireless Driver support: PCI\VEN_17CB_1103_01 BT driver support: USB\VID_0489_E0CC_0001 https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/ Already landed to mainline kernel v5.14-rc1. ** Changed in: linux (Ubuntu Impish) Status: In Progress => Incomplete ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: In Progress => Incomplete -- 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/1939528 Title: Need support of Qualcomm WCN6856 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Incomplete Status in linux-oem-5.13 source package in Focal: Incomplete Status in linux source package in Hirsute: Won't Fix Status in linux-firmware source package in Hirsute: New Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Incomplete Status in linux-firmware source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] Qualcomm WCN6856 not supported yet. [Fix] Upstream fixes in thread https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/ has been merged in mainline starting from commit 755b1f73173e ("ath11k: add hw reg support for WCN6855"). [Test Case] TBD. [Where problems could occur] While this introduces a new hardware, it might need further polishments. == original bug report == Wireless Driver support: PCI\VEN_17CB_1103_E0B8105B_01 BT driver support: USB\VID_0489_E0C9_0001 Wireless Driver support: PCI\VEN_17CB_1103_01 BT driver support: USB\VID_0489_E0CC_0001 https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/ Already landed to mainline kernel v5.14-rc1. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939528] Re: Need support of Qualcomm WCN6856
No hardware to verify yet, but probably we'll also need this from linux- firmware: 4adb20b4 QCA: Add Bluetooth firmware for WCN685x ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Focal) Status: New => Incomplete ** Changed in: linux-firmware (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1939528 Title: Need support of Qualcomm WCN6856 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Incomplete Status in linux-oem-5.13 source package in Focal: Incomplete Status in linux source package in Hirsute: Won't Fix Status in linux-firmware source package in Hirsute: New Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Incomplete Status in linux-firmware source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] Qualcomm WCN6856 not supported yet. [Fix] Upstream fixes in thread https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/ has been merged in mainline starting from commit 755b1f73173e ("ath11k: add hw reg support for WCN6855"). [Test Case] TBD. [Where problems could occur] While this introduces a new hardware, it might need further polishments. == original bug report == Wireless Driver support: PCI\VEN_17CB_1103_E0B8105B_01 BT driver support: USB\VID_0489_E0C9_0001 Wireless Driver support: PCI\VEN_17CB_1103_01 BT driver support: USB\VID_0489_E0CC_0001 https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/ Already landed to mainline kernel v5.14-rc1. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939528] Re: Need support of Qualcomm WCN6856
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Impish) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Impish) Importance: Undecided => High ** Changed in: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-5.13 (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1939528 Title: Need support of Qualcomm WCN6856 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Bug description: Wireless Driver support: PCI\VEN_17CB_1103_E0B8105B_01 BT driver support: USB\VID_0489_E0C9_0001 Wireless Driver support: PCI\VEN_17CB_1103_01 BT driver support: USB\VID_0489_E0CC_0001 https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/ Already landed to mainline kernel v5.14-rc1. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930645] Re: Fix Ethernet not working by hotplug - RTL8106E
verified on 5.11.0-33-generic ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1930645 Title: Fix Ethernet not working by hotplug - RTL8106E Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] After hot-plug the Ethernet cable, the status of Ethernet is always down. [Fix] Because ASPM is enabled on RTL8106E, the link change interrupt can't be fired immediately. Must wait a long time to get the link change interrupt. After discuss with maintainer, he give some suggestions 1. use PHY_POLL. 2. he send a workaround(Ref. [1]) to disable ASPM on RTL8106E. For 2, because don't know the details about operated registers in rtl_hw_aspm_clkreq_enable, it have higher risk on power usage during suspend. For 1, Use PHY_POLL have a lower risk because don't change any register operations and use polling method to query link change status. SRU the patches for 1 first. Currently keep discussing with Realtek but don't figure out yet. Will re-SRU the official solution once Realtek resolve the issue. Ref [1], https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=1ee8856de82faec9bc8bd0f2308a7f27e30ba207 [Test] Verified on machines with Realtek Ethernet device, the Ethernet works well after hotplug 30 times. [Regression Potential] Medium, use polling methond may have higher cpu usage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940204] Re: AMDGPU: Fix System hang after resume from suspend
** Tags added: originate-from-1931664 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1940204 Title: AMDGPU: Fix System hang after resume from suspend Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: New Status in linux-oem-5.13 source package in Hirsute: New Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: New Status in linux-oem-5.13 source package in Impish: New Bug description: [Impact] With AMD-GPU and don't use it as a display output, After multiple Suspend, system would hang. [Fix] Disable BACO for polaris12 series. BACO allow the graphics cards on Linux to support S4 / hibernation support. [Test Case] 1. Must plug AMD GPU and don't use it as display output 2. Plug DP/HDMI on iGPU. 3. Suspend machine. 4. check if system hangs. [Where problems could occur] Disable BACO would cause higher power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940204/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936296] Re: Fix display output on HP hybrid GFX laptops
** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1936296 Title: Fix display output on HP hybrid GFX laptops Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] Video output MUX switched from Intel GPU to Nvidia GPU after S3, so display settings are lost. [Fix] Always use Nvidia GPU to do the video output. This matches the behavior on the other OS. [Test] Connect and external monitor, and change the scaling factor or resolution, suspend the laptop. After wakeup, the custom monitor setting is kept. [Where problems could occur] If nvidia.ko or nouveau.ko is blacklisted, the video output may stop working, as it's now routed away from i915 device. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940154] Re: Xorg freeze (nouveau/ttm use-after-free with full-screen video)
The nouveau driver has never been well supported. It remains buggy for years even for old hardware so the outlook is not great there. If you would like to debug the nouveau driver then it lives in the Linux kernel at: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/nouveau The other information I've been referring to comes from these pages: https://www.nvidia.com/Download/index.aspx?lang=en-us https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340 https://launchpad.net/ubuntu/+source/linux https://launchpad.net/ubuntu/+source/linux-hwe-5.11 https://nvidia.custhelp.com/app/answers/detail/a_id/3142/~/support-timeframes-for-unix-legacy-gpu-releases Nvidia has never supported their own chips for more than a few years and your Samsung machine appears to be 11 years old. You would have less trouble if the machine had AMD or Intel graphics. Otherwise if you use Nvidia you will either need newer hardware or to stay on an older OS like Ubuntu 20.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940154 Title: Xorg freeze (nouveau/ttm use-after-free with full-screen video) Status in linux package in Ubuntu: New Bug description: Since upgrading to Ubuntu 21.04 yesterday, I've noticed several hangs during full-screen video playback (watching Youtube videos in Chromium). Often, it happens just after or during the switch to full- screen. The system stays running and I can connect via ssh, but restarting gdm3 has no effect and most of the time I've had to reboot. The latest hang recovered automatically when I left the machine alone for about 2 minutes, and produced the following messages in dmesg (I'll attach a more complete log): ``` [ 3520.856803] [TTM] Buffer eviction failed [ 3520.856856] [ cut here ] [ 3520.856859] refcount_t: underflow; use-after-free. [ 3520.856888] WARNING: CPU: 3 PID: 6842 at lib/refcount.c:28 refcount_warn_saturate+0xae/0xf0 ... [ 3520.857292] Call Trace: [ 3520.857305] ttm_bo_put+0x3f/0x50 [ttm] [ 3520.857331] nouveau_gem_new+0xc4/0x100 [nouveau] [ 3520.857611] ? nouveau_gem_new+0x100/0x100 [nouveau] [ 3520.857871] nouveau_gem_ioctl_new+0x5b/0x100 [nouveau] [ 3520.858133] ? nouveau_gem_new+0x100/0x100 [nouveau] [ 3520.858398] drm_ioctl_kernel+0xae/0xf0 [drm] [ 3520.858500] drm_ioctl+0x245/0x400 [drm] [ 3520.858586] ? nouveau_gem_new+0x100/0x100 [nouveau] [ 3520.858850] ? __fget_files+0x5f/0x90 [ 3520.858864] ? __fget_light+0x32/0x80 [ 3520.858879] nouveau_drm_ioctl+0x66/0xc0 [nouveau] [ 3520.859145] __x64_sys_ioctl+0x91/0xc0 [ 3520.859158] do_syscall_64+0x38/0x90 [ 3520.859170] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 3520.859182] RIP: 0033:0x7fce8ceb0317 ``` ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 16 23:36:04 2021 DistUpgraded: 2021-08-15 02:10:41,733 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GT218M [GeForce 310M] [10de:0a70] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd GT218M [GeForce 310M] [144d:c079] InstallationDate: Installed on 2014-06-27 (2607 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. Q430/Q530 ProcEnviron: LANGUAGE=en_IE:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IE.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic root=UUID=fc20db83-0138-4e0c-b7e9-04da38c1e9e9 ro quiet splash acpi_backlight=vendor crashkernel=512M-:192M acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to hirsute on 2021-08-15 (1 days ago) dmi.bios.date: 05/29/2010
[Kernel-packages] [Bug 1940332] Re: hci0: Failed to send firmware data (-38)
** Description changed: This report is related to a problem reported in IRC #ubuntu whereby (Intel 8260 Wifi) Bluetooth device cannot load its firmware file at boot time but can later. Appears to be a race condition between the wifi chipset setting up the device and enabling the attached USB interface to the Bluetooth device fully. Bluetooth: hci0: Failed to send firmware data (-38) Bluetooth: hci0: Intel reset sent to retry FW download The solution is to introduce a delay in loading the 'btusb' module: echo "install btusb /usr/bin/sleep 2; /usr/sbin/modprobe --ignore- install btusb" | sudo tee -a /etc/modprobe.d/btusb.conf This imposes a 2 second delay before the 'btusb' module is loaded. - Reporting user tells us this works around the problem + Reporting user tells us this works around the problem. + + The code responsible is net/bluetooth/hci_request.c::__hci_cmd_sync_ev() + and/or + + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/hci_request.c#n147 + + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/hci_request.c#n234 + + as the result of the calls: + + err = wait_event_interruptible_timeout(...) + + since only these are followed by calls to + net/bluetooth/lib.c::bt_to_errno() and that is the only function that + can return -ENOSYS (-38) + + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/lib.c#n132 + + default: + return ENOSYS; + } -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940332 Title: hci0: Failed to send firmware data (-38) Status in linux package in Ubuntu: Confirmed Bug description: This report is related to a problem reported in IRC #ubuntu whereby (Intel 8260 Wifi) Bluetooth device cannot load its firmware file at boot time but can later. Appears to be a race condition between the wifi chipset setting up the device and enabling the attached USB interface to the Bluetooth device fully. Bluetooth: hci0: Failed to send firmware data (-38) Bluetooth: hci0: Intel reset sent to retry FW download The solution is to introduce a delay in loading the 'btusb' module: echo "install btusb /usr/bin/sleep 2; /usr/sbin/modprobe --ignore- install btusb" | sudo tee -a /etc/modprobe.d/btusb.conf This imposes a 2 second delay before the 'btusb' module is loaded. Reporting user tells us this works around the problem. The code responsible is net/bluetooth/hci_request.c::__hci_cmd_sync_ev() and/or https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/hci_request.c#n147 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/hci_request.c#n234 as the result of the calls: err = wait_event_interruptible_timeout(...) since only these are followed by calls to net/bluetooth/lib.c::bt_to_errno() and that is the only function that can return -ENOSYS (-38) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/lib.c#n132 default: return ENOSYS; } To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940332] [NEW] hci0: Failed to send firmware data (-38)
Public bug reported: This report is related to a problem reported in IRC #ubuntu whereby (Intel 8260 Wifi) Bluetooth device cannot load its firmware file at boot time but can later. Appears to be a race condition between the wifi chipset setting up the device and enabling the attached USB interface to the Bluetooth device fully. Bluetooth: hci0: Failed to send firmware data (-38) Bluetooth: hci0: Intel reset sent to retry FW download The solution is to introduce a delay in loading the 'btusb' module: echo "install btusb /usr/bin/sleep 2; /usr/sbin/modprobe --ignore- install btusb" | sudo tee -a /etc/modprobe.d/btusb.conf This imposes a 2 second delay before the 'btusb' module is loaded. Reporting user tells us this works around the problem ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Attachment added: "Kernel Log" https://bugs.launchpad.net/bugs/1940332/+attachment/5518599/+files/kernel.log ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940332 Title: hci0: Failed to send firmware data (-38) Status in linux package in Ubuntu: Confirmed Bug description: This report is related to a problem reported in IRC #ubuntu whereby (Intel 8260 Wifi) Bluetooth device cannot load its firmware file at boot time but can later. Appears to be a race condition between the wifi chipset setting up the device and enabling the attached USB interface to the Bluetooth device fully. Bluetooth: hci0: Failed to send firmware data (-38) Bluetooth: hci0: Intel reset sent to retry FW download The solution is to introduce a delay in loading the 'btusb' module: echo "install btusb /usr/bin/sleep 2; /usr/sbin/modprobe --ignore- install btusb" | sudo tee -a /etc/modprobe.d/btusb.conf This imposes a 2 second delay before the 'btusb' module is loaded. Reporting user tells us this works around the problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940083] Re: zfs send encrypt causes kernel NULL pointer dereference
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940083 Title: zfs send encrypt causes kernel NULL pointer dereference Status in linux package in Ubuntu: In Progress Bug description: zfs send -I works well: # uname -a Linux sdeziel-desktop 5.11.0-27-generic #29~20.04.1-Ubuntu SMP Wed Aug 11 15:58:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux # zfs send -I data/simon/musique@laptop-2020-11-30 data/simon/musique@o | wc -c 5660616 # dmesg -c # but when sending encrypted data sets, some snapshot combinations cause problem: # zfs send -wI data/simon/musique@laptop-2020-11-30 data/simon/musique@o | wc -c # # hung as nothing is written to the pipe. # dmesg -c [ 1179.862792] BUG: kernel NULL pointer dereference, address: 0030 [ 1179.862798] #PF: supervisor read access in kernel mode [ 1179.862801] #PF: error_code(0x) - not-present page [ 1179.862803] PGD 0 P4D 0 [ 1179.862806] Oops: [#5] SMP PTI [ 1179.862809] CPU: 1 PID: 13834 Comm: zfs Tainted: P D IO 5.11.0-27-generic #29~20.04.1-Ubuntu [ 1179.862813] Hardware name: /D54250WYK, BIOS WYLPT10H.86A.0054.2019.0902.1752 09/02/2019 [ 1179.862815] RIP: 0010:dmu_dump_write+0x22c/0x320 [zfs] [ 1179.862922] Code: d0 48 89 43 58 49 8b 45 60 48 89 43 38 49 8b 45 68 48 89 43 40 49 8b 45 70 48 89 43 48 49 8b 45 78 48 89 43 50 e9 9f fe ff ff <49> 8b 45 30 45 85 c0 74 39 48 85 c0 78 04 80 4b 31 02 48 8d 53 70 [ 1179.862924] RSP: 0018:a51ae62678f0 EFLAGS: 00010206 [ 1179.862927] RAX: d1141450686f75df RBX: 952730fdde00 RCX: [ 1179.862929] RDX: 80f7 RSI: 0013 RDI: 952730fddf38 [ 1179.862931] RBP: a51ae6267938 R08: 0100 R09: 0002 [ 1179.862933] R10: 80f7 R11: 0002 R12: a51ae6267ab8 [ 1179.862935] R13: R14: 0002 R15: [ 1179.862937] FS: 7fa6a03ac7c0() GS:95298fa8() knlGS: [ 1179.862939] CS: 0010 DS: ES: CR0: 80050033 [ 1179.862941] CR2: 0030 CR3: 00025a648001 CR4: 001706e0 [ 1179.862943] Call Trace: [ 1179.862945] ? wait_woken+0x80/0x80 [ 1179.862951] do_dump+0x5da/0x900 [zfs] [ 1179.863035] ? spl_kmem_free+0x28/0x30 [spl] [ 1179.863046] dmu_send_impl+0xdf6/0x1570 [zfs] [ 1179.863129] ? dbuf_rele_and_unlock+0x32e/0x6d0 [zfs] [ 1179.863204] ? dbuf_rele+0x3d/0x50 [zfs] [ 1179.863279] ? dmu_buf_rele+0xe/0x10 [zfs] [ 1179.863354] dmu_send_obj+0x24c/0x360 [zfs] [ 1179.863435] ? mze_find+0xd4/0xf0 [zfs] [ 1179.863551] zfs_ioc_send+0x11d/0x2c0 [zfs] [ 1179.863665] ? zfs_ioc_send+0x2c0/0x2c0 [zfs] [ 1179.863778] zfsdev_ioctl_common+0x679/0x930 [zfs] [ 1179.863892] ? __kmalloc_node+0x40d/0x4e0 [ 1179.863899] zfsdev_ioctl+0x57/0xe0 [zfs] [ 1179.864008] __x64_sys_ioctl+0x91/0xc0 [ 1179.864012] do_syscall_64+0x38/0x90 [ 1179.864018] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 1179.864023] RIP: 0033:0x7fa6a09a050b [ 1179.864026] Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48 [ 1179.864028] RSP: 002b:7ffdb9687fb8 EFLAGS: 0246 ORIG_RAX: 0010 [ 1179.864032] RAX: ffda RBX: 55dd6be41f60 RCX: 7fa6a09a050b [ 1179.864033] RDX: 7ffdb968b5c0 RSI: 5a1c RDI: 0003 [ 1179.864035] RBP: 7ffdb968b580 R08: 5a1c R09: 0003 [ 1179.864037] R10: 0009 R11: 0246 R12: 7ffdb968b5c0 [ 1179.864038] R13: 55dd6be41f70 R14: R15: 0001 [ 1179.864041] Modules linked in: vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock ccm nf_log_ipv6 ip6table_filter ip6table_nat ip6t_rpfilter ip6table_mangle ip6table_raw ip6_tables nf_log_ipv4 nf_log_common xt_owner xt_LOG xt_conntrack iptable_filter xt_MASQUERADE xt_nat xt_tcpudp iptable_nat nf_nat iptable_mangle iptable_raw bpfilter nls_iso8859_1 zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) intel_rapl_msr spl(O) intel_rapl_common snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio x86_pkg_temp_thermal snd_hda_codec_hdmi intel_powerclamp coretemp snd_hda_intel snd_intel_dspcfg mei_hdcp kvm_intel soundwire_intel at24 soundwire_generic_allocation kvm soundwire_cadence snd_hda_codec snd_hda_core soundwire_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_soc_core rapl
[Kernel-packages] [Bug 1940083] Re: zfs send encrypt causes kernel NULL pointer dereference
** Package changed: zfs-linux (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940083 Title: zfs send encrypt causes kernel NULL pointer dereference Status in linux package in Ubuntu: New Bug description: zfs send -I works well: # uname -a Linux sdeziel-desktop 5.11.0-27-generic #29~20.04.1-Ubuntu SMP Wed Aug 11 15:58:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux # zfs send -I data/simon/musique@laptop-2020-11-30 data/simon/musique@o | wc -c 5660616 # dmesg -c # but when sending encrypted data sets, some snapshot combinations cause problem: # zfs send -wI data/simon/musique@laptop-2020-11-30 data/simon/musique@o | wc -c # # hung as nothing is written to the pipe. # dmesg -c [ 1179.862792] BUG: kernel NULL pointer dereference, address: 0030 [ 1179.862798] #PF: supervisor read access in kernel mode [ 1179.862801] #PF: error_code(0x) - not-present page [ 1179.862803] PGD 0 P4D 0 [ 1179.862806] Oops: [#5] SMP PTI [ 1179.862809] CPU: 1 PID: 13834 Comm: zfs Tainted: P D IO 5.11.0-27-generic #29~20.04.1-Ubuntu [ 1179.862813] Hardware name: /D54250WYK, BIOS WYLPT10H.86A.0054.2019.0902.1752 09/02/2019 [ 1179.862815] RIP: 0010:dmu_dump_write+0x22c/0x320 [zfs] [ 1179.862922] Code: d0 48 89 43 58 49 8b 45 60 48 89 43 38 49 8b 45 68 48 89 43 40 49 8b 45 70 48 89 43 48 49 8b 45 78 48 89 43 50 e9 9f fe ff ff <49> 8b 45 30 45 85 c0 74 39 48 85 c0 78 04 80 4b 31 02 48 8d 53 70 [ 1179.862924] RSP: 0018:a51ae62678f0 EFLAGS: 00010206 [ 1179.862927] RAX: d1141450686f75df RBX: 952730fdde00 RCX: [ 1179.862929] RDX: 80f7 RSI: 0013 RDI: 952730fddf38 [ 1179.862931] RBP: a51ae6267938 R08: 0100 R09: 0002 [ 1179.862933] R10: 80f7 R11: 0002 R12: a51ae6267ab8 [ 1179.862935] R13: R14: 0002 R15: [ 1179.862937] FS: 7fa6a03ac7c0() GS:95298fa8() knlGS: [ 1179.862939] CS: 0010 DS: ES: CR0: 80050033 [ 1179.862941] CR2: 0030 CR3: 00025a648001 CR4: 001706e0 [ 1179.862943] Call Trace: [ 1179.862945] ? wait_woken+0x80/0x80 [ 1179.862951] do_dump+0x5da/0x900 [zfs] [ 1179.863035] ? spl_kmem_free+0x28/0x30 [spl] [ 1179.863046] dmu_send_impl+0xdf6/0x1570 [zfs] [ 1179.863129] ? dbuf_rele_and_unlock+0x32e/0x6d0 [zfs] [ 1179.863204] ? dbuf_rele+0x3d/0x50 [zfs] [ 1179.863279] ? dmu_buf_rele+0xe/0x10 [zfs] [ 1179.863354] dmu_send_obj+0x24c/0x360 [zfs] [ 1179.863435] ? mze_find+0xd4/0xf0 [zfs] [ 1179.863551] zfs_ioc_send+0x11d/0x2c0 [zfs] [ 1179.863665] ? zfs_ioc_send+0x2c0/0x2c0 [zfs] [ 1179.863778] zfsdev_ioctl_common+0x679/0x930 [zfs] [ 1179.863892] ? __kmalloc_node+0x40d/0x4e0 [ 1179.863899] zfsdev_ioctl+0x57/0xe0 [zfs] [ 1179.864008] __x64_sys_ioctl+0x91/0xc0 [ 1179.864012] do_syscall_64+0x38/0x90 [ 1179.864018] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 1179.864023] RIP: 0033:0x7fa6a09a050b [ 1179.864026] Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48 [ 1179.864028] RSP: 002b:7ffdb9687fb8 EFLAGS: 0246 ORIG_RAX: 0010 [ 1179.864032] RAX: ffda RBX: 55dd6be41f60 RCX: 7fa6a09a050b [ 1179.864033] RDX: 7ffdb968b5c0 RSI: 5a1c RDI: 0003 [ 1179.864035] RBP: 7ffdb968b580 R08: 5a1c R09: 0003 [ 1179.864037] R10: 0009 R11: 0246 R12: 7ffdb968b5c0 [ 1179.864038] R13: 55dd6be41f70 R14: R15: 0001 [ 1179.864041] Modules linked in: vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock ccm nf_log_ipv6 ip6table_filter ip6table_nat ip6t_rpfilter ip6table_mangle ip6table_raw ip6_tables nf_log_ipv4 nf_log_common xt_owner xt_LOG xt_conntrack iptable_filter xt_MASQUERADE xt_nat xt_tcpudp iptable_nat nf_nat iptable_mangle iptable_raw bpfilter nls_iso8859_1 zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) intel_rapl_msr spl(O) intel_rapl_common snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio x86_pkg_temp_thermal snd_hda_codec_hdmi intel_powerclamp coretemp snd_hda_intel snd_intel_dspcfg mei_hdcp kvm_intel soundwire_intel at24 soundwire_generic_allocation kvm soundwire_cadence snd_hda_codec snd_hda_core soundwire_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_soc_core rapl snd_usb_audio snd_compress ac97_bus intel_cstate snd_pcm_dmaengine iwldvm uvcvideo videobuf2_vmalloc btusb snd_usbmidi_lib btrtl snd_hwdep btbcm mac80211 [ 1179.864103]
[Kernel-packages] [Bug 1939460] Re: Unable to play media from Google Chrome with Bluetooth headeset in HSP/HFP profile
Attaching the "make.log" from the first error message. ** Attachment added: "make.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939460/+attachment/5518597/+files/make.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/1939460 Title: Unable to play media from Google Chrome with Bluetooth headeset in HSP/HFP profile Status in linux package in Ubuntu: New Bug description: Tried to use the microphone of my bluetooth headset. No audio while using my bluetooth headset in HSP/HFP profile. Media gets forzeen. My goal is to use the headset with A2DP Sink while using the microphone. This is possible on the same system in Windows. Listing information from the system, used audio card and bluetooth information. lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 /etc/bluetooth$ pacmd list-cards index: 12 name: driver: owner module: 51 properties: device.description = "PXC 550" device.string = "00:16:94:23:D1:27" device.api = "bluez" device.class = "sound" device.bus = "bluetooth" device.form_factor = "headset" bluez.path = "/org/bluez/hci0/dev_00_16_94_23_D1_27" bluez.class = "0x240404" bluez.alias = "PXC 550" device.icon_name = "audio-headset-bluetooth" device.intended_roles = "phone" profiles: headset_head_unit: Headset head unit (HSP/HFP) (priority 30, available: yes) a2dp_sink: High fidelity playback (A2DP Sink) (priority 40, available: unknown) off: Av (priority 0, available: yes) active profile: sinks: bluez_sink.00_16_94_23_D1_27.headset_head_unit/#44: PXC 550 sources: bluez_sink.00_16_94_23_D1_27.headset_head_unit.monitor/#53: Monitor of PXC 550 bluez_source.00_16_94_23_D1_27.headset_head_unit/#54: PXC 550 ports: headset-output: Headset (priority 0, latency offset 0 usec, available: yes) properties: headset-input: Headset (priority 0, latency offset 0 usec, available: yes) properties: /etc/bluetooth$ sudo dmesg | grep -i bluetooth [ 10.913222] Bluetooth: Core ver 2.22 [ 10.913242] Bluetooth: HCI device and connection manager initialized [ 10.913245] Bluetooth: HCI socket layer initialized [ 10.913246] Bluetooth: L2CAP socket layer initialized [ 10.913249] Bluetooth: SCO socket layer initialized [ 11.031423] Bluetooth: hci0: BCM: chip id 63 [ 11.032420] Bluetooth: hci0: BCM: features 0x07 [ 11.048478] Bluetooth: hci0: fredrik [ 11.048486] Bluetooth: hci0: BCM20702A1 (001.002.014) build [ 11.049496] Bluetooth: hci0: BCM: firmware Patch file not found, tried: [ 11.049499] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0b05-17cb.hcd' [ 11.049500] Bluetooth: hci0: BCM: 'brcm/BCM-0b05-17cb.hcd' [ 11.599665] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 11.599668] Bluetooth: BNEP filters: protocol multicast [ 11.599672] Bluetooth: BNEP socket layer initialized [ 12.734502] Bluetooth: RFCOMM TTY layer initialized [ 12.734507] Bluetooth: RFCOMM socket layer initialized [ 12.734511] Bluetooth: RFCOMM ver 1.11 [27256.450493] Bluetooth: hci0: urb 7dc40568 submission failed (90) [27256.450505] Bluetooth: hci0: sending frame failed (-90) [27256.450511] Bluetooth: hci0: urb 7dc40568 submission failed (90) [27256.450515] Bluetooth: hci0: sending frame failed (-90) [28116.001485] Bluetooth: hci0: urb cbbd81d7 submission failed (90) [28116.001498] Bluetooth: hci0: sending frame failed (-90) [28116.001504] Bluetooth: hci0: urb cbbd81d7 submission failed (90) [28116.001508] Bluetooth: hci0: sending frame failed (-90) [28125.939480] Bluetooth: hci0: urb 508f2223 submission failed (90) [28125.939494] Bluetooth: hci0: sending frame failed (-90) [28125.939501] Bluetooth: hci0: urb 508f2223 submission failed (90) [28125.939505] Bluetooth: hci0: sending frame failed (-90) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fredrik1324 F pulseaudio /dev/snd/controlC1: fredrik1324 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 11 01:23:14 2021 MachineType: ASUS
[Kernel-packages] [Bug 1939460] Re: Unable to play media from Google Chrome with Bluetooth headeset in HSP/HFP profile
Thanks for the response. Executed the command "sudo dpkg -i *.deb" again to follow any issues with the module install. There seamse to be some issue with the installation related to the nvidia? Any sugestions? Adding a screenshot from running the command above. ** Attachment added: "Error installing kernel.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939460/+attachment/5518596/+files/Error%20installing%20kernel.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939460 Title: Unable to play media from Google Chrome with Bluetooth headeset in HSP/HFP profile Status in linux package in Ubuntu: New Bug description: Tried to use the microphone of my bluetooth headset. No audio while using my bluetooth headset in HSP/HFP profile. Media gets forzeen. My goal is to use the headset with A2DP Sink while using the microphone. This is possible on the same system in Windows. Listing information from the system, used audio card and bluetooth information. lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 /etc/bluetooth$ pacmd list-cards index: 12 name: driver: owner module: 51 properties: device.description = "PXC 550" device.string = "00:16:94:23:D1:27" device.api = "bluez" device.class = "sound" device.bus = "bluetooth" device.form_factor = "headset" bluez.path = "/org/bluez/hci0/dev_00_16_94_23_D1_27" bluez.class = "0x240404" bluez.alias = "PXC 550" device.icon_name = "audio-headset-bluetooth" device.intended_roles = "phone" profiles: headset_head_unit: Headset head unit (HSP/HFP) (priority 30, available: yes) a2dp_sink: High fidelity playback (A2DP Sink) (priority 40, available: unknown) off: Av (priority 0, available: yes) active profile: sinks: bluez_sink.00_16_94_23_D1_27.headset_head_unit/#44: PXC 550 sources: bluez_sink.00_16_94_23_D1_27.headset_head_unit.monitor/#53: Monitor of PXC 550 bluez_source.00_16_94_23_D1_27.headset_head_unit/#54: PXC 550 ports: headset-output: Headset (priority 0, latency offset 0 usec, available: yes) properties: headset-input: Headset (priority 0, latency offset 0 usec, available: yes) properties: /etc/bluetooth$ sudo dmesg | grep -i bluetooth [ 10.913222] Bluetooth: Core ver 2.22 [ 10.913242] Bluetooth: HCI device and connection manager initialized [ 10.913245] Bluetooth: HCI socket layer initialized [ 10.913246] Bluetooth: L2CAP socket layer initialized [ 10.913249] Bluetooth: SCO socket layer initialized [ 11.031423] Bluetooth: hci0: BCM: chip id 63 [ 11.032420] Bluetooth: hci0: BCM: features 0x07 [ 11.048478] Bluetooth: hci0: fredrik [ 11.048486] Bluetooth: hci0: BCM20702A1 (001.002.014) build [ 11.049496] Bluetooth: hci0: BCM: firmware Patch file not found, tried: [ 11.049499] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0b05-17cb.hcd' [ 11.049500] Bluetooth: hci0: BCM: 'brcm/BCM-0b05-17cb.hcd' [ 11.599665] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 11.599668] Bluetooth: BNEP filters: protocol multicast [ 11.599672] Bluetooth: BNEP socket layer initialized [ 12.734502] Bluetooth: RFCOMM TTY layer initialized [ 12.734507] Bluetooth: RFCOMM socket layer initialized [ 12.734511] Bluetooth: RFCOMM ver 1.11 [27256.450493] Bluetooth: hci0: urb 7dc40568 submission failed (90) [27256.450505] Bluetooth: hci0: sending frame failed (-90) [27256.450511] Bluetooth: hci0: urb 7dc40568 submission failed (90) [27256.450515] Bluetooth: hci0: sending frame failed (-90) [28116.001485] Bluetooth: hci0: urb cbbd81d7 submission failed (90) [28116.001498] Bluetooth: hci0: sending frame failed (-90) [28116.001504] Bluetooth: hci0: urb cbbd81d7 submission failed (90) [28116.001508] Bluetooth: hci0: sending frame failed (-90) [28125.939480] Bluetooth: hci0: urb 508f2223 submission failed (90) [28125.939494] Bluetooth: hci0: sending frame failed (-90) [28125.939501] Bluetooth: hci0: urb 508f2223 submission failed (90) [28125.939505] Bluetooth: hci0: sending frame failed (-90) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USER
[Kernel-packages] [Bug 1937004] Re: Add additional Mediatek MT7921 WiFi/BT device IDs
What about Hiruse? Bluetooth does not work for me, I'm using Hirsute + linux 5.14 RC6. mario@Asus-Ubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 21.04 Release: 21.04 Codename: hirsute mario@Asus-Ubuntu:~$ = mario@Asus-Ubuntu:~$ inxi -nz Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 IF: enp2s0 state: down mac: Device-2: MEDIATEK driver: mt7921e IF: wlp3s0 state: up mac: IF-ID-1: docker0 state: down mac: IF-ID-2: Pr0 state: down mac: IF-ID-3: virbr0 state: down mac: IF-ID-4: vpn0 state: down mac: N/A mario@Asus-Ubuntu:~$ = mario@Asus-Ubuntu:~$ hciconfig hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 mario@Asus-Ubuntu:~$ == mario@Asus-Ubuntu:~$ dpkg -l linux-firmware Deseado=desconocido(U)/Instalar/eliminaR/Purgar/retener(H) | Estado=No/Inst/ficheros-Conf/desempaqUetado/medio-conF/medio-inst(H)/espera> |/ Err?=(ninguno)/requiere-Reinst (Estado,Err: mayúsc.=malo) ||/ Nombre Versión Arquitectura Descripción +++-==---= ii linux-firmware 1.197.3 all Firmware for Linux kernel drivers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1937004 Title: Add additional Mediatek MT7921 WiFi/BT device IDs Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] Some Mediatek MT7921 Bluetooth doesn't work out of box. [Fix] One ID for Lite-On was included in upstream, but we need two additional more from different vendors. [Test Case] With firmware from bug 1936452, this will bring up MT7921 Bluetooth. Check BD address from output of `hciconfig`. [Where problems could occur] This brings up new devices that wasn't working. After being up and running, we may face some other runtime issue, e.g. power consumption. == original bug description == Mediatek MT7921 has been added to mainline kernel & firmware. Firmware part is being handled by bug 1936452, and WiFi fw loading failure in bug 1936790. This issue will focus on backport/add device IDs for MT7921: * Bus 001 Device 004: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device * Bus 002 Device 003: ID 13d3:3567 IMC Networks linux$ git log --graph --oneline korg/master -- \ drivers/bluetooth/ \ drivers/net/wireless/mediatek/mt76/mt7921/ linux-firmware$ git log --graph --oneline korg/master -- \ mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin \ mediatek/WIFI_RAM_CODE_MT7961_1.bin \ mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin * a7882719 linux-firmware: update frimware for mediatek bluetooth chip (MT7921) * 2fd5139f linux-firmware: update firmware for MT7921 WiFi device to 20210612122753 * 42a66e5b linux-firmware: update firmware for MT7921 WiFi device * 58fb90a0 linux-firmware: add frimware for mediatek bluetooth chip (MT7921) * 391fd50d linux-firmware: add firmware for MT7921 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1278 F pulseaudio CasperMD5CheckResult: skip Dependencies: 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-davos-adl+X135 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-05 (16 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 192f:0616 Avago Technologies, Pte. ADNS-5700 Optical Mouse Controller (5-button) Bus 001 Device 002: ID 03f0:344a HP, Inc HP USB Slim Keyboard Bus 001 Device 004: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3910 Package: linux-firmware 1.187.15+staging.9 [origin: LP-PPA-vicamo-linux-firmware-staging] PackageArchitecture: all ProcFB: 0
[Kernel-packages] [Bug 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot
Can we get a fix after over a year now? I think we have enough people suffering to deserve a fix for this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot Status in Linux: Confirmed Status in Ubuntu: Confirmed Status in linux-signed-hwe package in Ubuntu: In Progress Status in linux-signed-hwe package in Fedora: New Bug description: Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5 14IIL05 81YH' from first system start on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tilman 1607 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 21:22:22 2020 InstallationDate: Installed on 2020-05-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN23WW(V1.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05: dmi.product.family: IdeaPad 5 14IIL05 dmi.product.name: 81YH dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05 dmi.product.version: IdeaPad 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936452] Re: [SRU][F/H/I] Add MT7921 wifi fw
Bluetooth does not work for me, I'm using Hirsute + linux 5.14 RC6. mario@Asus-Ubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 21.04 Release:21.04 Codename: hirsute mario@Asus-Ubuntu:~$ = mario@Asus-Ubuntu:~$ inxi -nz Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 IF: enp2s0 state: down mac: Device-2: MEDIATEK driver: mt7921e IF: wlp3s0 state: up mac: IF-ID-1: docker0 state: down mac: IF-ID-2: Pr0 state: down mac: IF-ID-3: virbr0 state: down mac: IF-ID-4: vpn0 state: down mac: N/A mario@Asus-Ubuntu:~$ -- 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/1936452 Title: [SRU][F/H/I] Add MT7921 wifi fw Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Status in linux-firmware source package in Impish: Fix Released Bug description: SRU justification: [Impact] No support for MT7921 wifi card. [Fix] MT7921 needs both driver and firmware, driver is almost ready, add firmware first, then get driver bug fixed later. [Test] Verified on hardware, cold boot system wifi works fine. Reboot make it fail, but I will fix it in SRU of kernel patch. After that, it works fine. [Where problems could occur] The MT7921 wifi may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940154] Re: Xorg freeze (nouveau/ttm use-after-free with full-screen video)
Hi Daniel, thanks for your quick reply. Do you mean the nouveau driver is abandoned, or just doesn't have much activity lately? Rolling back to an old kernel version (and Ubuntu distro) really feels like a failure. I'd be happy to try to debug the nouveau driver, although it sounds like I'm on my own and I don't really know anything about graphics drivers. Do you know of a good resource for getting started? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940154 Title: Xorg freeze (nouveau/ttm use-after-free with full-screen video) Status in linux package in Ubuntu: New Bug description: Since upgrading to Ubuntu 21.04 yesterday, I've noticed several hangs during full-screen video playback (watching Youtube videos in Chromium). Often, it happens just after or during the switch to full- screen. The system stays running and I can connect via ssh, but restarting gdm3 has no effect and most of the time I've had to reboot. The latest hang recovered automatically when I left the machine alone for about 2 minutes, and produced the following messages in dmesg (I'll attach a more complete log): ``` [ 3520.856803] [TTM] Buffer eviction failed [ 3520.856856] [ cut here ] [ 3520.856859] refcount_t: underflow; use-after-free. [ 3520.856888] WARNING: CPU: 3 PID: 6842 at lib/refcount.c:28 refcount_warn_saturate+0xae/0xf0 ... [ 3520.857292] Call Trace: [ 3520.857305] ttm_bo_put+0x3f/0x50 [ttm] [ 3520.857331] nouveau_gem_new+0xc4/0x100 [nouveau] [ 3520.857611] ? nouveau_gem_new+0x100/0x100 [nouveau] [ 3520.857871] nouveau_gem_ioctl_new+0x5b/0x100 [nouveau] [ 3520.858133] ? nouveau_gem_new+0x100/0x100 [nouveau] [ 3520.858398] drm_ioctl_kernel+0xae/0xf0 [drm] [ 3520.858500] drm_ioctl+0x245/0x400 [drm] [ 3520.858586] ? nouveau_gem_new+0x100/0x100 [nouveau] [ 3520.858850] ? __fget_files+0x5f/0x90 [ 3520.858864] ? __fget_light+0x32/0x80 [ 3520.858879] nouveau_drm_ioctl+0x66/0xc0 [nouveau] [ 3520.859145] __x64_sys_ioctl+0x91/0xc0 [ 3520.859158] do_syscall_64+0x38/0x90 [ 3520.859170] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 3520.859182] RIP: 0033:0x7fce8ceb0317 ``` ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 16 23:36:04 2021 DistUpgraded: 2021-08-15 02:10:41,733 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GT218M [GeForce 310M] [10de:0a70] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd GT218M [GeForce 310M] [144d:c079] InstallationDate: Installed on 2014-06-27 (2607 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. Q430/Q530 ProcEnviron: LANGUAGE=en_IE:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IE.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic root=UUID=fc20db83-0138-4e0c-b7e9-04da38c1e9e9 ro quiet splash acpi_backlight=vendor crashkernel=512M-:192M acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to hirsute on 2021-08-15 (1 days ago) dmi.bios.date: 05/29/2010 dmi.bios.release: 2.0 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 02KF.M008.20100529.KSJ dmi.board.asset.tag: Tag 12345 dmi.board.name: Q430/Q530 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias:
[Kernel-packages] [Bug 1934557] Re: Backlight (screen brightness) on Lenovo P14s AMD Gen2 inop
I no longer have access to the hardware. So, I - the original reporter - cannot verify the fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1934557 Title: Backlight (screen brightness) on Lenovo P14s AMD Gen2 inop Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Confirmed Bug description: Backlight does not change. Neither with the keys, nor with the slider. Values in /sys/class/backlight/amdgpu_bl0/brightness do change. However without effect on the actual brightness of the screen, which seems to be stuck at maximum brightness. Following the instructions from here: https://wiki.ubuntu.com/Kernel/Debugging/Backlight ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: simon 1886 F pulseaudio /dev/snd/pcmC2D0p: simon 1886 F...m pulseaudio /dev/snd/controlC1: simon 1886 F pulseaudio /dev/snd/controlC0: simon 1886 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 3 09:46:53 2021 InstallationDate: Installed on 2021-07-03 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 21A0CTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 1.5 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET35W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0CTO1WW 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.5 dmi.modalias: dmi:bvnLENOVO:bvrR1MET35W(1.05):bd04/23/2021:br1.5:efr1.5:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0CTO1WW dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO == SRU justification: [Impact] backlight can't be controlled on AMD platform. [Fix] AUX doesn't work on HDR panel, fallback to PWM mode to make backlight be controlled. [Test] Verified on hardware, backlight brightness works fine. [Where problems could occur] It may break backlight control on AMD platform. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1934557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933388] Re: SR-IOV broken in Ubuntu 20.04.2 LTS
Hi Marcelo, Thank you for following up on this. Unfortunately, even with the 5.11 kernel the problem still exists. -- 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/1933388 Title: SR-IOV broken in Ubuntu 20.04.2 LTS Status in linux-azure package in Ubuntu: New Bug description: SR-IOV does not work since Ubuntu Server 18.04.2 LTS, once the HWE kernel (4.18.0-15 generic x86_64)) has been installed on that version. Please also see ticket: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1818400 This bug report was created for Ubuntu 20.04.02 LTS, since the kernel for the previous bug report is no longer being supported and a developer requested us to make a new bug report for the new Ubuntu version... Environment: Windows Server 2019 Fresh Hyper-V generation 2 VM (configuration version 9.0) SR-IOV enabled on the virtual switch (Intel I350-T2 physical network adapter) SR-IOV enabled on the virtual network card of the VM Steps to reproduce: Install Ubuntu Server 20.04.2 LTS Verify SR-IOV is enabled in the Networking tab of the Hyper-V manager Check SR-IOV status in the Networking tab of the Hyper-V manager. It will show status degraded (SR-IOV not operational) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-1033-azure 5.8.0-1033.35~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-1033.35~20.04.1-azure 5.8.18 Uname: Linux 5.8.0-1033-azure x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jun 23 23:00:26 2021 InstallationDate: Installed on 2020-09-15 (281 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-azure-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1933388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940320] [NEW] Touchpad not detected on Toshiba Portege z10t-a
Public bug reported: Hello, the touchpad of the Toshiba Portege z10t-a is not detected at all by the linux kernel (linux 5.11). It can't be found in /proc/bus/input/devices nor trough xinput. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: knizontes 1525 F pulseaudio /dev/snd/controlC0: knizontes 1525 F pulseaudio CasperMD5CheckResult: unknown Date: Tue Aug 17 19:47:45 2021 MachineType: TOSHIBA PORTEGE Z10t-A ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=2a98e48e-2171-4367-8b05-bb88c8d5d985 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: linux-image-5.11.0-31-generic linux-base RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2014 dmi.bios.release: 2.10 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 2.10 dmi.board.asset.tag: 00 dmi.board.name: PORTEGE Z10t-A dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion2.10:bd09/19/2014:br2.10:efr1.40:svnTOSHIBA:pnPORTEGEZ10t-A:pvrPT141A-05M03Y:rvnTOSHIBA:rnPORTEGEZ10t-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.family: 00 dmi.product.name: PORTEGE Z10t-A dmi.product.sku: PT141A dmi.product.version: PT141A-05M03Y dmi.sys.vendor: TOSHIBA ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940320 Title: Touchpad not detected on Toshiba Portege z10t-a Status in linux package in Ubuntu: New Bug description: Hello, the touchpad of the Toshiba Portege z10t-a is not detected at all by the linux kernel (linux 5.11). It can't be found in /proc/bus/input/devices nor trough xinput. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: knizontes 1525 F pulseaudio /dev/snd/controlC0: knizontes 1525 F pulseaudio CasperMD5CheckResult: unknown Date: Tue Aug 17 19:47:45 2021 MachineType: TOSHIBA PORTEGE Z10t-A ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=2a98e48e-2171-4367-8b05-bb88c8d5d985 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: linux-image-5.11.0-31-generic linux-base RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2014 dmi.bios.release: 2.10 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 2.10 dmi.board.asset.tag: 00 dmi.board.name: PORTEGE Z10t-A dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion2.10:bd09/19/2014:br2.10:efr1.40:svnTOSHIBA:pnPORTEGEZ10t-A:pvrPT141A-05M03Y:rvnTOSHIBA:rnPORTEGEZ10t-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.family: 00 dmi.product.name: PORTEGE Z10t-A dmi.product.sku: PT141A dmi.product.version: PT141A-05M03Y dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940320/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900338] Re: nvidia-dkms-450 450.66-0ubuntu0.20.04.1: nvidia kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1900338 Title: nvidia-dkms-450 450.66-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Bug description: I do not have further information since while I was surfing on web (Brave web browser) a emergent window of ubuntu system appear asking if sharing the issue. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-450 450.66-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.4.0-51-generic Date: Sun Oct 18 18:06:58 2020 InstallationDate: Installed on 2020-09-13 (34 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 450.66-0ubuntu0.20.04.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.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-450 Title: nvidia-dkms-450 450.66-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1900338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940315] [NEW] Bionic update: upstream stable patchset 2021-08-17
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-08-17 Ported from the following upstream stable releases: v4.14.242, v4.19.201 from git://git.kernel.org/ selftest: fix build error in tools/testing/selftests/vm/userfaultfd.c KVM: x86: determine if an exception has an error code only when injecting it. net: split out functions related to registering inflight socket files UBUNTU: [Config] updateconfigs for UNIX_SCM af_unix: fix garbage collect vs MSG_PEEK net/802/mrp: fix memleak in mrp_request_join() net/802/garp: fix memleak in garp_request_join() net: annotate data race around sk_ll_usec sctp: move 198 addresses from unusable to private scope hfs: add missing clean-up in hfs_fill_super hfs: fix high memory mapping in hfs_bnode_read hfs: add lock nesting notation to hfs_find_init ARM: dts: versatile: Fix up interrupt controller node names virtio_net: Do not pull payload in skb->head gro: ensure frag0 meets IP header alignment x86/kvm: fix vcpu-id indexed array sizes ocfs2: fix zero out valid data ocfs2: issue zeroout to EOF blocks can: raw: raw_setsockopt(): fix raw_rcv panic for sock UAF can: mcba_usb_start(): add missing urb->transfer_dma initialization can: usb_8dev: fix memory leak can: ems_usb: fix memory leak can: esd_usb2: fix memory leak NIU: fix incorrect error return, missed in previous revert nfc: nfcsim: fix use after free during module unload x86/asm: Ensure asm/proto.h can be included stand-alone cfg80211: Fix possible memory leak in function cfg80211_bss_update netfilter: conntrack: adjust stop timestamp to real expiry value netfilter: nft_nat: allow to specify layer 4 protocol NAT only tipc: fix sleeping in tipc accept routine mlx4: Fix missing error code in mlx4_load_one() net: llc: fix skb_over_panic net/mlx5: Fix flow table chaining sctp: fix return value check in __sctp_rcv_asconf_lookup tulip: windbond-840: Fix missing pci_disable_device() in probe and remove sis900: Fix missing pci_disable_device() in probe and remove can: hi311x: fix a signedness bug in hi3110_cmd() i40e: Fix log TC creation failure when max num of queues is exceeded i40e: Add additional info to PHY type error UBUNTU: upstream stable to v4.14.242, v4.19.201 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + upstream stable patchset 2021-08-17 -upstream stable patchset 2021-08-17 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v4.14.242, v4.19.201 + + from git://git.kernel.org/ + + selftest: fix build error in tools/testing/selftests/vm/userfaultfd.c + KVM: x86: determine if an exception has an error code only when injecting it. + net: split out functions related to registering inflight socket files + UBUNTU: [Config] updateconfigs for UNIX_SCM + af_unix: fix garbage collect vs
[Kernel-packages] [Bug 1933173] Re: [21.10 FEAT] KVM: Provide a secure guest indication
Thx 'fran...@de.ibm.com' for the verification! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933173 Title: [21.10 FEAT] KVM: Provide a secure guest indication Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: SRU Justification: == [Impact] * It is difficult for customers to identify if a KVM guest on s390x runs in secure execution more or not. Hence several requests came up that asked about providing a better indication. * If the mode is not known, one may venture oneself into deceptive security. * Patches that allow a better indication via 'prot_virt_host' using the sysfs firmware interface were added to upstream kernel 5.13. * Secure execution was initially introduced in Ubuntu with focal / 20.04, hence this request to SRU. [Fix] * 37564ed834aca26993b77b9b2a0119ec1ba6e00c 37564ed834ac "s390/uv: add prot virt guest/host indication files" * df2e400e07ad53a582ee934ce8384479d5ddf48b df2e400e07ad "s390/uv: fix prot virt host indication compilation" [Test Case] * A z15 or LinuxONE III LPAR is needed that runs KVM in secure execution. * Have a look for the 'prot_virt_host' key at the sysfs firmware interface - '1' indicates that the ultravisor is active and that the guest is running protected (in secure execution mode). [Regression Potential] * The patch is s390x specific and modifies file arch/s390/kernel/uv.c only. * An entirely new new function 'uv_is_prot_virt_guest' was added and initialized and used in uv_info_init - hence the regression risk in existing code is rather small. * However, in case the initialization was done errornously the indication might be wrong, maybe showing that the system is not protected in the way it should be (wrong indication). * More general code deficiencies in these two functions will be largely indicated by the test compiles. * But the code was already tested based on kernel 5.13 - and for SRU- ing a cherry-pick of the patches was sufficient, hence the exact same code as in 5.13 is used. * Further tests of the SRU kernels (5.11 and 5.4) can be done based on the test kernel available from the PPA (see below). [Other] * Patches are upstream accepted with since 5.13-rc1. * Request was to add the patches to focal / 20.04. * To avoid potential regressions on upgrades, the patches need to be added to hirsute / 20.10, too. __ Provide an indication in the guest that it's running securely. Cannot replace a real attestation and doesn't really provide additional security (or could even create the false impression of security), but has been frequently requested by customers. Value: Usability, lower the effort to prepare and deploy secure workloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1933173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933173] Re: [21.10 FEAT] KVM: Provide a secure guest indication
--- Comment From fran...@de.ibm.com 2021-08-17 11:34 EDT--- Enabled proposed on a 21.04 host and updated the kernel to "5.11.0-33-generic #35-Ubuntu" If PV is disabled both prot_virt_* files show 0. If PV is enabled prot_virt_host shows 1 and prot_virt_guest shows 0. If queried on a secure guest prot_virt_guest shows one and _host shows 0. Code is successfully verified. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933173 Title: [21.10 FEAT] KVM: Provide a secure guest indication Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: SRU Justification: == [Impact] * It is difficult for customers to identify if a KVM guest on s390x runs in secure execution more or not. Hence several requests came up that asked about providing a better indication. * If the mode is not known, one may venture oneself into deceptive security. * Patches that allow a better indication via 'prot_virt_host' using the sysfs firmware interface were added to upstream kernel 5.13. * Secure execution was initially introduced in Ubuntu with focal / 20.04, hence this request to SRU. [Fix] * 37564ed834aca26993b77b9b2a0119ec1ba6e00c 37564ed834ac "s390/uv: add prot virt guest/host indication files" * df2e400e07ad53a582ee934ce8384479d5ddf48b df2e400e07ad "s390/uv: fix prot virt host indication compilation" [Test Case] * A z15 or LinuxONE III LPAR is needed that runs KVM in secure execution. * Have a look for the 'prot_virt_host' key at the sysfs firmware interface - '1' indicates that the ultravisor is active and that the guest is running protected (in secure execution mode). [Regression Potential] * The patch is s390x specific and modifies file arch/s390/kernel/uv.c only. * An entirely new new function 'uv_is_prot_virt_guest' was added and initialized and used in uv_info_init - hence the regression risk in existing code is rather small. * However, in case the initialization was done errornously the indication might be wrong, maybe showing that the system is not protected in the way it should be (wrong indication). * More general code deficiencies in these two functions will be largely indicated by the test compiles. * But the code was already tested based on kernel 5.13 - and for SRU- ing a cherry-pick of the patches was sufficient, hence the exact same code as in 5.13 is used. * Further tests of the SRU kernels (5.11 and 5.4) can be done based on the test kernel available from the PPA (see below). [Other] * Patches are upstream accepted with since 5.13-rc1. * Request was to add the patches to focal / 20.04. * To avoid potential regressions on upgrades, the patches need to be added to hirsute / 20.10, too. __ Provide an indication in the guest that it's running securely. Cannot replace a real attestation and doesn't really provide additional security (or could even create the false impression of security), but has been frequently requested by customers. Value: Usability, lower the effort to prepare and deploy secure workloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1933173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
@65 tbh I haven't analyzed what you've offered, but a quick glance over your post *and* knowing what *I've* done to get it working tells me that no, it's not the same. What I've done barely breaks into the usual workflow of installing the image/headers from mainline and building the out-of-tree modules against it. Maybe you're offering the same but it's hard to be positive about it from your post. @66 Just build why? If everything needed is already there. Basically just copy over those pesky fixdep and modpost from a compatable release and you're set. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930527] Re: [SRU][OEM-5.10/H] UBUNTU: SAUCE: Fix backlight control on Samsung 16727 panel
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1930527 Title: [SRU][OEM-5.10/H] UBUNTU: SAUCE: Fix backlight control on Samsung 16727 panel Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Bug description: SRU justification: [Impact] Backlight can't be controlled on 5.11- version of kernel. [Fix] The panel needs DPCD to get control of backlight. After 5.12 kernel introduced new Intel HDR backlight control, and it works well on this panel. Add quirk ID to enable DPCD on 5.11- kernel. [Test] Vendor Verified on hardware, with this quirk backlight can be changed on 5.10 and 5.11 kernel. [Where problems could occur] The panel backlight may not be changed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Status in alsa-ucm-conf source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in linux-firmware source package in Focal: Confirmed Status in alsa-ucm-conf source package in Groovy: Won't Fix Status in linux source package in Groovy: Won't Fix Status in linux-firmware source package in Groovy: Won't Fix Status in alsa-ucm-conf source package in Hirsute: Won't Fix Status in linux source package in Hirsute: Fix Committed Status in linux-firmware source package in Hirsute: Confirmed Status in alsa-ucm-conf source package in Impish: Won't Fix Status in linux source package in Impish: Confirmed Status in linux-firmware source package in Impish: Confirmed Bug description: [SRU Justification] [Impact] Skylake, Kabylake, Kabylake-refresh, Amberlake and some other platforms where audio is of SPT (PCH) type, HDA (with DSP capabilities) plus DMIC configuration is supported on these with skylake driver since kernel 5.8. However, no sound card can be detected w/o the topology binary file in /lib/firmware and corresponding ucm file. [Fix] The kernel config CONFIG_SND_SOC_INTEL_SKYLAKE_HDAUDIO_CODEC needa to be enabled for the snd_soc_skl driver to support HDA+DMIC configuration. And the topology binary file and UCM files need to be located in the correct path based on Intel's suggestion. https://gist.github.com/crojewsk/4e6382bfb0dbfaaf60513174211f29cb. [Test] On the Skylake/Kabylake platforms with either the PCI device 8086:9d70 and 8086:9d71, boot up the machine and check the existence of the sound card by either 'aplay -l' or 'pactl list' command. [Where problems could occur] Should be low risk, it only affects limited Intel Platforms with particular PCI device IDs + HDA plus DMIC configuration. == Original Bug Description == Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago)
[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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux 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 Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Hirsute: Fix Committed 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 1930645] Re: Fix Ethernet not working by hotplug - RTL8106E
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1930645 Title: Fix Ethernet not working by hotplug - RTL8106E Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] After hot-plug the Ethernet cable, the status of Ethernet is always down. [Fix] Because ASPM is enabled on RTL8106E, the link change interrupt can't be fired immediately. Must wait a long time to get the link change interrupt. After discuss with maintainer, he give some suggestions 1. use PHY_POLL. 2. he send a workaround(Ref. [1]) to disable ASPM on RTL8106E. For 2, because don't know the details about operated registers in rtl_hw_aspm_clkreq_enable, it have higher risk on power usage during suspend. For 1, Use PHY_POLL have a lower risk because don't change any register operations and use polling method to query link change status. SRU the patches for 1 first. Currently keep discussing with Realtek but don't figure out yet. Will re-SRU the official solution once Realtek resolve the issue. Ref [1], https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=1ee8856de82faec9bc8bd0f2308a7f27e30ba207 [Test] Verified on machines with Realtek Ethernet device, the Ethernet works well after hotplug 30 times. [Regression Potential] Medium, use polling methond may have higher cpu usage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926579] Re: On TGL platforms screen shows garbage when browsing website by scrolling mouse
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1926579 Title: On TGL platforms screen shows garbage when browsing website by scrolling mouse Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: In Progress Bug description: [Impact] On Dell TGL platforms screen shows garbage when browsing website by scrolling mouse [Fix] This patch fixes the issue https://patchwork.freedesktop.org/patch/430153/?series=89348=1 [Test] Verified on Dell TGL-H platforms. [Where problems could occur] It disable PSR2 on A0 and B0 TGL-H platforms, should introduce no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926579/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931301] Re: NIC unavailable after suspend to RAM
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931301 Title: NIC unavailable after suspend to RAM Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: Fix Committed Bug description: [SRU Justification] [Impact] The network card will be unavailable after system resume if the interface is not UP before suspend. [Fix] It's because we added the WOL support for this driver. The driver with WoL feature does detach the network interface even the interface is DOWN. However, it doesn't attach the network interface back on resume if it was DOWN. That's why it's unavailable after resume. Fix this by correctly netif_device_attach according to the interface status. [Test Case] 1. Plug the ethernet cable to the Atheros E220x ethernet adapter 2. Suspend the system and check if the ethernet interface available after resume 3. Unplug the ethernet cable 4. Suspend the system and check if the ethernet interface available after resume [Regression Potential] Low. The driver code would be identical to working Groovy version after fix. == Original Bug Description == Upgraded to 21.04 (hirsute) and now the network card is unavailable after suspend to RAM (sleep state S3). It worked flawlessly up until 20.10. My workaround for now is unloading and reloading the kernel module, but that won't work for normal users, hence this report. NIC in its unavailable state: 2: enp4s0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether d0:50:99:27:02:11 brd ff:ff:ff:ff:ff:ff NIC (from lspci): 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 10) Trying to ifconfig it down/up results in: SIOCSIFFLAGS: No such device journalctl shows (right after recovering from suspend): NetworkManager[1911]: [1623181236.9371] manager: sleep: wake requested (sleeping: yes enabled: yes) NetworkManager[1911]: [1623181236.9372] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') NetworkManager[1911]: [1623181236.9382] manager: NetworkManager state is now CONNECTED_LOCAL ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jun 8 21:59:15 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-25 (1748 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2021-06-04 (4 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931301/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937991] Re: Skip rtcpie test in kselftests/timers if the default RTC device does not exist
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1937991 Title: Skip rtcpie test in kselftests/timers if the default RTC device does not exist Status in ubuntu-kernel-tests: In Progress 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 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: [Impact] This test will require /dev/rtc0, the default RTC device, or one specified by user to run. Since this default RTC is not guaranteed to exist on all of the devices, so check its existence first, otherwise skip this test with the kselftest skip code 4. Without this patch this test will fail like this on a s390x zVM: $ selftests: timers: rtcpie $ /dev/rtc0: No such file or directory not ok 1 selftests: timers: rtcpie # exit=22 We have this test disabled in our test suite with an if check [1], thus we're not seeing this failure recently. With this patch applied we can remove that code block later. [1] https://kernel.ubuntu.com/git/ubuntu/autotest-client- tests.git/tree/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py#n133 [Fix] * 0d3e5a057992bd selftests: timers: rtcpie: skip test if default RTC device does not exist [Test] Run this test with patched source tree on a s390x zVM and it will be skipped correctly: $ selftests: timers: rtcpie $ Default RTC /dev/rtc0 does not exist. Test Skipped! not ok 9 selftests: timers: rtcpie # SKIP [Where problems could occur] If this fix is incorrect we might see it failing again on systems that without /dev/rtc0 (after removing our local hacks in autotest-client-tests) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1937991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936296] Re: Fix display output on HP hybrid GFX laptops
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1936296 Title: Fix display output on HP hybrid GFX laptops Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] Video output MUX switched from Intel GPU to Nvidia GPU after S3, so display settings are lost. [Fix] Always use Nvidia GPU to do the video output. This matches the behavior on the other OS. [Test] Connect and external monitor, and change the scaling factor or resolution, suspend the laptop. After wakeup, the custom monitor setting is kept. [Where problems could occur] If nvidia.ko or nouveau.ko is blacklisted, the video output may stop working, as it's now routed away from i915 device. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931072] Re: USB Type-C hotplug event not handled properly in TGL-H system during 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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1931072 Title: USB Type-C hotplug event not handled properly in TGL-H system during 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-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] The system will be hold by the infinite loop in ACPI method IPCS after exiting s2idle in TGL-H systems if the docking station with external display connected is unplugged when the system is still in s2idle. It's because the system is unaware of the unplug event and it seems keep something asserted which will never be released while the system trying to exit s2idle. [Fix] Disconnect TypeC PHYs during system suspend and shutdown, even with the corresponding TypeC sink still plugged to its connector. The HPD event is no longer triggered when the system is in s2idle so the resume process will not be hindered. [Test Case] 1. On all TigerLake-H and later platforms with NVIDIA GPU, make sure the NVIDIA GPU is running in either On-Demand mode or Performance mode. 2. Connect the docking station with the external display connected. 3. Suspend the system. 4. Remove the docking station when the system is suspended. 5. Press power button to wake up the system and wait > 1 minutes to make sure if the display comes back. [Where problems could occur] Low. This will only make a difference in the TypeC DP alternate mode, and the display driver will detect the display connector after resume. == Original Bug Description == [Summary] As mentioned in #1929166, the NVIDIA GPU will fall off the bus after exiting s2idle in TGL-H systems if the USB Type-C docking/dongle with external display connected is unplugged when the system is still in s2idle. The system will be hold by the infinite loop in ACPI method IPCS and then the PCIe root port of NVIDIA gpu fails the power transition from D3cold to D0. It's because the display connector hotplug event not handled properly in graphics drivers and the system will freeze for > 30 seconds to wait for ACPI method IPCS to exit. [ 154.446781] [ 154.446783] [ 154.446783] Initialized Local Variables for Method [IPCS]: [ 154.446784] Local0: 9863e365 Integer 09C5 [ 154.446790] [ 154.446791] Initialized Arguments for Method [IPCS]: (7 arguments defined for method invocation) [ 154.446792] Arg0: 25568fbd Integer 00AC [ 154.446795] Arg1: 9ef30e76 Integer [ 154.446798] Arg2: fdf820f0 Integer 0010 [ 154.446801] Arg3: 9fc2a088 Integer 0001 [ 154.446804] Arg4: 3a3418f7 Integer 0001 [ 154.446807] Arg5: 20c4b87c Integer [ 154.446810] Arg6: 8b965a8a Integer [ 154.446813] [ 154.446815] ACPI Error: Aborting method \IPCS due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446824] ACPI Error: Aborting method \MCUI due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446829] ACPI Error: Aborting method \SPCX due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446835] ACPI Error: Aborting method \_SB.PC00.PGSC due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446841] ACPI Error: Aborting method \_SB.PC00.PGON due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446846] ACPI Error: Aborting method \_SB.PC00.PEG1.NPON due to previous error
[Kernel-packages] [Bug 1934557] Re: Backlight (screen brightness) on Lenovo P14s AMD Gen2 inop
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1934557 Title: Backlight (screen brightness) on Lenovo P14s AMD Gen2 inop Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Confirmed Bug description: Backlight does not change. Neither with the keys, nor with the slider. Values in /sys/class/backlight/amdgpu_bl0/brightness do change. However without effect on the actual brightness of the screen, which seems to be stuck at maximum brightness. Following the instructions from here: https://wiki.ubuntu.com/Kernel/Debugging/Backlight ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: simon 1886 F pulseaudio /dev/snd/pcmC2D0p: simon 1886 F...m pulseaudio /dev/snd/controlC1: simon 1886 F pulseaudio /dev/snd/controlC0: simon 1886 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 3 09:46:53 2021 InstallationDate: Installed on 2021-07-03 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 21A0CTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 1.5 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET35W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0CTO1WW 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.5 dmi.modalias: dmi:bvnLENOVO:bvrR1MET35W(1.05):bd04/23/2021:br1.5:efr1.5:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0CTO1WW dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO == SRU justification: [Impact] backlight can't be controlled on AMD platform. [Fix] AUX doesn't work on HDR panel, fallback to PWM mode to make backlight be controlled. [Test] Verified on hardware, backlight brightness works fine. [Where problems could occur] It may break backlight control on AMD platform. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1934557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938143] Re: Include product_sku info to modalias
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1938143 Title: Include product_sku info to modalias Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] When we add DMI quirks for the new platforms, it's hard to prevent from leaking its model name. Our customer doesn't like it. [Fix] Introduce the product sku modalias to DMI table, so that we can use more meaningless product sku string to match the platform. [Test] No real DMI quirk is added in this commit, so need to do any tests. [Where problems could occur] It's safe to add one more DMI entry, nothing could be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1938143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932029] Re: Support builtin revoked certificates
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932029 Title: Support builtin revoked certificates Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] Upstream linux kernel now supports configuring built-in revoked certificates for the .blacklist keyring. Add support in our kernel configuration to have built-in revoked certificates. Revoke UEFI amd64 & arm64 2012 signing certificate. Under UEFI Secureboot with lockdown, shim may attempt to communicate revoked certificates to the kernel and depending on how good EFI firmware is, this may or may not succeed. By having these built-in, it will be prohibited to kexec file_load older kernels that were signed with now revoked certificates, however one boots. [Test Plan] * Boot kernel directly, or just with grub, and without shim * Check that $ sudo keyctl list %:.blacklist Contains assymetric 2012 key. [Where problems could occur] * Derivative and per-arch kernels may need to revoke different keys, thus this should be evaluated on per arch & flavour basis as to which keys to revoke. [Other Info] * In theory, this only needs to be revoked on amd64 and arm64, but empty revocation list is not allowed by the kernel configury, thus at the moment revoking 2012 UEFI cert for all architectures. * an ubuntu kernel team regression test is being added to assert that expected revoked certificates have been revoked see https://lists.ubuntu.com/archives/kernel-team/2021-August/122986.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933173] Re: [21.10 FEAT] KVM: Provide a secure guest indication
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933173 Title: [21.10 FEAT] KVM: Provide a secure guest indication Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: SRU Justification: == [Impact] * It is difficult for customers to identify if a KVM guest on s390x runs in secure execution more or not. Hence several requests came up that asked about providing a better indication. * If the mode is not known, one may venture oneself into deceptive security. * Patches that allow a better indication via 'prot_virt_host' using the sysfs firmware interface were added to upstream kernel 5.13. * Secure execution was initially introduced in Ubuntu with focal / 20.04, hence this request to SRU. [Fix] * 37564ed834aca26993b77b9b2a0119ec1ba6e00c 37564ed834ac "s390/uv: add prot virt guest/host indication files" * df2e400e07ad53a582ee934ce8384479d5ddf48b df2e400e07ad "s390/uv: fix prot virt host indication compilation" [Test Case] * A z15 or LinuxONE III LPAR is needed that runs KVM in secure execution. * Have a look for the 'prot_virt_host' key at the sysfs firmware interface - '1' indicates that the ultravisor is active and that the guest is running protected (in secure execution mode). [Regression Potential] * The patch is s390x specific and modifies file arch/s390/kernel/uv.c only. * An entirely new new function 'uv_is_prot_virt_guest' was added and initialized and used in uv_info_init - hence the regression risk in existing code is rather small. * However, in case the initialization was done errornously the indication might be wrong, maybe showing that the system is not protected in the way it should be (wrong indication). * More general code deficiencies in these two functions will be largely indicated by the test compiles. * But the code was already tested based on kernel 5.13 - and for SRU- ing a cherry-pick of the patches was sufficient, hence the exact same code as in 5.13 is used. * Further tests of the SRU kernels (5.11 and 5.4) can be done based on the test kernel available from the PPA (see below). [Other] * Patches are upstream accepted with since 5.13-rc1. * Request was to add the patches to focal / 20.04. * To avoid potential regressions on upgrades, the patches need to be added to hirsute / 20.10, too. __ Provide an indication in the guest that it's running securely. Cannot replace a real attestation and doesn't really provide additional security (or could even create the false impression of security), but has been frequently requested by customers. Value: Usability, lower the effort to prepare and deploy secure workloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1933173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934489] Re: Make Intel GPUs choose YCbCr420 encoding automatically when required for 4k 60Hz output
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934489 Title: Make Intel GPUs choose YCbCr420 encoding automatically when required for 4k 60Hz output Status in linux package in Ubuntu: New Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: Fix Committed Bug description: SRU Justification: Impact: On some setups, while the monitor and the GPU support display modes with pixel clocks of up to 600MHz, the connector might not. This prevents RGB encoding for 4k60Hz, but YCbCr420 encoding might still be possible. However, which color mode is used is decided before the pixel clock capabilities are checked, causing the check to fail and discarding 4k60Hz from the list of possible display modes. Fix: This patch fixes the problem by retrying to find a display mode with YCbCr420 enforced and using it, if it is valid. It's very similar to a patch submitted to amdgpu which fixed the same problem. Testcase: I personally tested on a Clevo NV40MB, but generally: Find a PC with a current Intel iGPU, but only a HDMI 1.4 output. Connect a 4k@60Hz display supporting YCbCr420 encoding to the HDMI port. Without the patch the maximum that can be set via xrandr is 3840 × 2160 30Hz. With the Patch 3840 × 2160 60Hz can be selected which will use YCbCr420 automatically. Prerequisite (included in this email patchset as 1/4): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3c4442aa22878091f16c8d9592f5f5b6a94d1556 Patchset already got accepted upstream and reached the torvalds tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eacba74d4d561ea6487d944417526e1b025cbebd https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=84d95f77f4aea3f22a486cd04777afd4ab0f0ea5 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=388b863509f76f6a5ecedd7ffdaf184aa813241e and needs only a minor modifications to apply to ubuntu-focal/hwe-5.8 Commit-hashes: 3c4442aa22878091f16c8d9592f5f5b6a94d1556 eacba74d4d561ea6487d944417526e1b025cbebd 84d95f77f4aea3f22a486cd04777afd4ab0f0ea5 388b863509f76f6a5ecedd7ffdaf184aa813241e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937056] Re: Touchpad not working with ASUS TUF F15
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1937056 Title: Touchpad not working with ASUS TUF F15 Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: == SRU Justification == [Impact] Touchpad and touchscreen don't work on TGL-H laptops. [Fix] Update GPIO mapping so the values can match between Linux and BIOS. [Test] After applying the patch, both touchpad and touchscreen can work correctly. [Where problems could occur] If somehow any of the new pin value is incorrect, it can break devices that require Intel GPIO to work. == Original Bug Report == I am using Kubuntu 21.04 on my ASUS TUF F15 FX506HM_FX566HM. The touchpad isn't detected in Settings and neither in xinput, nor in cat /proc/bus/input/devices. Laptop model: ASUS TUF F15 FX506HM_FX566HM. Manufacturer of the Touchpad: Probably ELAN1203 When the symptom first appeared: From beginning Output of lsb_release -rd Description:Ubuntu 21.04 Release:21.04 Using kernel version 5.13.6. Also tried 5.11, 5.12.8, 5.12.15, 5.13.1, 5.13.2, 5.13.4, 5.13.5, 5.14-rc2, 5.14-rc3 Output of xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Asus Wireless Radio Control id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Button id=9[slave keyboard (3)] ↳ Sleep Button id=10 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=11 [slave keyboard (3)] ↳ Intel HID events id=12 [slave keyboard (3)] ↳ Intel HID 5 button array id=13 [slave keyboard (3)] ↳ Asus WMI hotkeys id=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)] Output of lspci :00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 05) :00:01.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #1 (rev 05) :00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) :00:04.0 Signal processing controller: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant (rev 05) :00:06.0 System peripheral: Intel Corporation Device 09ab :00:07.0 PCI bridge: Intel Corporation Tiger Lake-H Thunderbolt 4 PCI Express Root Port #0 (rev 05) :00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 05) :00:0a.0 Signal processing controller: Intel Corporation Tigerlake Telemetry Aggregator Driver (rev 01) :00:0d.0 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 USB Controller (rev 05) :00:0d.2 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 NHI #0 (rev 05) :00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller :00:14.0 USB controller: Intel Corporation Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller (rev 11) :00:14.2 RAM memory: Intel Corporation Tiger Lake-H Shared SRAM (rev 11)
[Kernel-packages] [Bug 1938689] Re: [SRU][H/OEM-5.10/OEM-5.13/U] Fix system hang after unplug tbt dock
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1938689 Title: [SRU][H/OEM-5.10/OEM-5.13/U] Fix system hang after unplug tbt dock Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: New Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: New Bug description: SRU justification: [Impact] System hang after unplug thunderbolt dock with Intel igc lan. [Fix] igc driver continue reading and writing MMIO address after PCI device is unplugged. This cause system page fault, and system hang. Add safe check and prevent reading and writing the MMIO. The patch is in maintainer's tree, but not merged to Linus's tree. Due to the schedule, send SRU as SAUCE patch. [Test] Verified on hardware, after unplug the thunderbolt cable, system work fine. [Where problems could occur] It may break the igc driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1938689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935040] Re: dev_forward_skb: do not scrub skb mark within the same name space
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935040 Title: dev_forward_skb: do not scrub skb mark within the same name space 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 Hirsute: Fix Committed Status in linux source package in Impish: In Progress Bug description: [Impact] The ebpf function 'bpf_redirect' reset the mark when used with the flag BPF_F_INGRESS. There are two main problems with that: - it's not consistent between legacy tunnels and ebpf; - it's not consistent between ingress and egress. In fact, the eBPF program can easily reset the mark, but it cannot preserve it. This kind of patch was already done in the past, see commit 963a88b31ddb ("tunnels: harmonize cleanup done on skb on xmit path"), commit ea23192e8e57 ("tunnels: harmonize cleanup done on skb on rx path") and commit 213dd74aee76 ("skbuff: Do not scrub skb mark within the same name space"). This is fixed upstream with commit ff70202b2d1a ("dev_forward_skb: do not scrub skb mark within the same name space"). https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff70202b2d1a [Test Case] Mark a packet in the POSTROUTING hook, redirect it to another interface and display it with a netfilter log rule to check the mark. [Regression Potential] A user could expect that the mark is reset after a call to bpf_redirect(BPF_F_INGRESS), but he could easily reset it in the eBPF program himself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933566] Re: XPS 9510 (TGL) Screen Brightness could not be changed
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1933566 Title: XPS 9510 (TGL) Screen Brightness could not be changed Status in HWE Next: New Status in linux package in Ubuntu: Invalid 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: Won't Fix Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] Dell XPS 15 9510(TGL) uses DPCD to control backlight, and need to add this panel to edid_quirk. kernel: [ 1.719773] 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. Kernel 5.12+ support the backlight via: commit: <4a8d79901d5b> ("drm/i915/dp: Enable Intel's HDR backlight interface (only SDR for now)"), and doesn't need this quirk. [Fix] Adding the panel's MFG to edid_quirk makes system switch to use DPCD to control backlight. [Test] Verified on Dell XPS 9510(TGL) [Where problems could occur] The quirk is for a dedicate panel, and won't affect other platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1933566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939638] Re: [regression] USB device is not detected during boot
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1939638 Title: [regression] USB device is not detected during boot Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-intel package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-intel source package in Focal: New Status in linux source package in Hirsute: Fix Committed Status in linux-intel source package in Hirsute: Invalid Bug description: [SRU Justification] [Impact] The USB devices (keyboard, storage...) are failed to be detected when connecting to the problematic root hubs which need longer PowerOn-to-PowerGood delay than it claims in the hub descriptor. It's caused by the upstream fix 90d28fb53d4a ("usb: core: reduce power-on-good delay time of root hub"). [Fix] Reverting the upstream fix until a formal fix been placed. [Test Case] 1. Plug the USB device to the ports of problematic root hub. 2. Power on the machine. 3. Check if the USB device can work or not after boot. [Regression Potential] Low. The longer delay is proven safe in old kernels. == Original Bug Description == [Summary] The USB devices (keyboard, storage...) are failed to be detected during boot after upgrade to UBUNTU focal kernel 5.4.0-78 and hirsute 5.11.0-26. However, they will be detected and working ok after re-plugging. The kernel output shows as down below during boot [ 39.350435] hub 1-0:1.0: USB hub found [ 39.398835] hub 1-0:1.0: 12 ports detected [ 39.622744] usb usb1-port3: couldn't allocate usb_device And when I plug out then plug in the same device, it shows [57210.794140] usb 1-3: new low-speed USB device number 4 using xhci_hcd [57210.951289] usb 1-3: New USB device found, idVendor=17ef, idProduct=6099, bcdDevice= 1.14 [57210.951293] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 After doing kernel bisecting, we found the upstream commit https://github.com/torvalds/linux/commit/90d28fb53d4a51299ff324dede015d5cb11b88a2 makes the difference. It indicates that the delay for the root hub from power_on to power_good is not long enough. There was no problem if the delay is 100 ms. From the Hub Descriptor of the root hub, the value is 10 * 2 milliseconds. And the XHCI spec also says in section 5.4.8 """ The host is required to have power stable to the port within 20 milliseconds of the '0' to '1' transition of PP. If PPC = '1', software is responsible for waiting 20ms. """ The commit seems to follow the SPEC but could cause problems on some hubs. [Reproduce Steps] 1. Plug the USB device to the physical port #1 and #4 which belongs to high-speed hub. 2. Power on the machine. 3. Check if the USB device can work or not after boot. [Results] Expected: All usb devices connect to the hub should work OK. Actual: USB devices connects to high-speed hub can not be probed. [Additional Information] Kernel Version: focal 5.4.0-78 and hirsute 5.11.0-26 [Upstream bug] https://bugzilla.kernel.org/show_bug.cgi?id=214021 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940107] Re: libvirtd fails to create VM
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940107 Title: libvirtd fails to create VM Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] libvirtd won't be able to create VMs. [Test case] Start a VM using virsh/libvirtd: virsh start focal [Potential regression] Some other processes won't be able to start inside some cgroups. --- $ virsh start focal error: Failed to start domain focal error: internal error: process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 22 Invalid argument 2021-08-16T15:11:23.005201Z qemu-system-x86_64: failed to initialize KVM: Invalid argument $ sudo dmesg | grep kvm [ 135.237378] kvm: Nested Virtualization enabled [ 135.237384] SVM: kvm: Nested Paging enabled [ 166.209556] kvm [4082]: kvm_vm_worker_thread: cgroup_attach_task_all failed with err -22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889137] Re: HWE kernel is missing firmwares
I started seeing the issues that Sergio mentioned lately as well. I think this was caused by the recent automatic move from 5.8 to 5.11. I had the oem kernel installed (20.04 install) but then apt recently moved me to the hwe-5.8 kernel. More recently apt pulled in hwe-5.11 and I believe that is when I started seeing this issue. I didn't look at this super carefully, but it appears that some packaging for the lenovo oem-sutton.newell-ace-meta ppa transitioned me to linux-image-generic-hwe-20.04 (fine) which at the time was 5.8 (on Jul 22 linux-generic-hwe-20.04:amd64 5.8.0.63.71~20.04.45 got installed, according to /var/log/dpkg.log.1). I rebooted into this kernel and was happy. Sometime in July, 5.11.0.22.23~20.04.6 came into -security and -updates, but I didn't install it. Later I performed an apt-get dist-upgrade and was upgraded to 5.11.0.25.27~20.04.10 on Aug 6. Today I upgraded again to 5.11.0-27.29~20.04.1. As it happens, I did not boot into either of the 5.11 kernels and am still on 5.8 (5.8.0-63.71~20.04.1-generic). I reinstalled linux-firmware just now and it readily demonstrates the issue: $ sudo dpkg -i ./linux-firmware_1.187.16_all.deb (Reading database ... 260812 files and directories currently installed.) Preparing to unpack .../linux-firmware_1.187.16_all.deb ... Unpacking linux-firmware (1.187.16) over (1.187.16) ... Setting up linux-firmware (1.187.16) ... update-initramfs: Generating /boot/initrd.img-5.11.0-27-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915 update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915 update-initramfs: Generating /boot/initrd.img-5.8.0-63-generic $ >From the above, we can see that the 5.8 kernel had no errors, but both the 5.11 ones do. As I have the i915 chipset on this device, I haven't rebooted yet as I need a functional system. -- 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/1889137 Title: HWE kernel is missing firmwares Status in linux-firmware package in Ubuntu: Confirmed Bug description: After install linux-generic-hwe-18.04: update-initramfs: Generating /boot/initrd.img-5.4.0-42-generic W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169 W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_04.bin for module i915 W: Possible missing firmware /lib/firmware/i915/skl_guc_33.0.0.bin for module i915 W: Possible missing firmware
[Kernel-packages] [Bug 1933388] Re: SR-IOV broken in Ubuntu 20.04.2 LTS
Does the problem happen when using the 5.11 provided by linux-azure- edge? This kernel can be installed with `apt-get install linux-azure- edge`. The 5.11 kernel is scheduled to become the default linux-azure kernel soon. -- 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/1933388 Title: SR-IOV broken in Ubuntu 20.04.2 LTS Status in linux-azure package in Ubuntu: New Bug description: SR-IOV does not work since Ubuntu Server 18.04.2 LTS, once the HWE kernel (4.18.0-15 generic x86_64)) has been installed on that version. Please also see ticket: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1818400 This bug report was created for Ubuntu 20.04.02 LTS, since the kernel for the previous bug report is no longer being supported and a developer requested us to make a new bug report for the new Ubuntu version... Environment: Windows Server 2019 Fresh Hyper-V generation 2 VM (configuration version 9.0) SR-IOV enabled on the virtual switch (Intel I350-T2 physical network adapter) SR-IOV enabled on the virtual network card of the VM Steps to reproduce: Install Ubuntu Server 20.04.2 LTS Verify SR-IOV is enabled in the Networking tab of the Hyper-V manager Check SR-IOV status in the Networking tab of the Hyper-V manager. It will show status degraded (SR-IOV not operational) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-1033-azure 5.8.0-1033.35~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-1033.35~20.04.1-azure 5.8.18 Uname: Linux 5.8.0-1033-azure x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jun 23 23:00:26 2021 InstallationDate: Installed on 2020-09-15 (281 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-azure-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1933388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904632] Re: Ubuntu 18.04 Azure VM host kernel panic
** Changed in: linux-azure (Ubuntu) Status: New => Invalid -- 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/1904632 Title: Ubuntu 18.04 Azure VM host kernel panic Status in linux-azure package in Ubuntu: Invalid Bug description: Running a container on an DV3 Standard_D8_v3 Azure host, as the container comes up, the Azure host VM kernel panics per the logs below. Isolated the issue to a process in the container which uses the virtual NICs available on the Azure host. The container also is running Ubuntu 18.04 based packages. The problem happens every single time the container is started, unless its NIC access process is not started. Has this sort of kernel panic on Azure been seen and what is the root cause and remedy please. Also the kernel logs on the Azure host show it vulnerable to the following CVE. There are other VMs and containers that can run on the Azure host without a kernel panic on it, but providing this info in case there is some tie-in to the panic. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3646 Kernel panic from the Azure Host console: Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux_1.13.33_e857c609-bc35-4b66-9a8b-e86fd8707e82.scope 2020-11-17T00:50:11.537914Z INFO MonitorHandler ExtHandler Stopped tracking cgroup: Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux-1.13.33, path: /sys/fs/cgroup/memory/system.slice/Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux_1.13.33_e857c609-bc35-4b66-9a8b-e86fd8707e82.scope 2020-11-17T00:50:23.291433Z INFO ExtHandler ExtHandler Checking for agent updates (family: Prod) 2020-11-17T00:51:11.677191Z INFO ExtHandler ExtHandler [HEARTBEAT] Agent WALinuxAgent-2.2.52 is running as the goal state agent [DEBUG HeartbeatCounter: 7;HeartbeatId: 8A2DD5B7-02E5-46E2-9EDB-F8CCBA274479;DroppedPackets: 0;UpdateGSErrors: 0;AutoUpdate: 1] [11218.537937] PANIC: double fault, error_code: 0x0 [11218.541423] Kernel panic - not syncing: Machine halted. [11218.541423] CPU: 0 PID: 9281 Comm: vmxt Not tainted 4.15.18+test #1 [11218.541423] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 12/07/2018 [11218.541423] Call Trace: [11218.541423] <#DF> [11218.541423] dump_stack+0x63/0x8b [11218.541423] panic+0xe4/0x244 [11218.541423] df_debug+0x2d/0x30 [11218.541423] do_double_fault+0x9a/0x130 [11218.541423] double_fault+0x1e/0x30 [11218.541423] RIP: 0010:0x1a80 [11218.541423] RSP: 0018:2200 EFLAGS: 00010096 [11218.541423] RAX: 0102 RBX: f7a40768 RCX: 002f [11218.541423] RDX: f7ee9970 RSI: f7a40700 RDI: f7c3a000 [11218.541423] RBP: fffd6430 R08: R09: [11218.541423] R10: R11: R12: [11218.541423] R13: R14: R15: [11218.541423] [11218.541423] Kernel Offset: 0x2a40 from 0x8100 (relocation range: 0x8000-0xbfff) [11218.541423] ---[ end Kernel panic - not syncing: Machine halted. [11218.636804] [ cut here ] [11218.640802] sched: Unexpected reschedule of offline CPU#2! [11218.640802] WARNING: CPU: 0 PID: 9281 at arch/x86/kernel/smp.c:128 native_smp_send_reschedule+0x3f/0x50 [11218.640802] Modules linked in: xt_nat xt_u32 vxlan ip6_udp_tunnel udp_tunnel veth nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter aufs xt_owner iptable_security xt_conntrack overlay openvswitch nsh nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack nls_iso8859_1 joydev input_leds mac_hid kvm_intel hv_balloon kvm serio_raw irqbypass intel_rapl_perf sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov [11218.640802] async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic crct10dif_pclmul crc32_pclmul hid_hyperv ghash_clmulni_intel hv_utils hv_storvsc pcbc ptp hv_netvsc hid pps_core scsi_transport_fc hyperv_keyboard aesni_intel aes_x86_64 crypto_simd hyperv_fb floppy glue_helper cryptd psmouse hv_vmbus i2c_piix4 pata_acpi [11218.640802] CPU: 0 PID: 9281 Comm: vmxt Not tainted 4.15.18+test #1 [11218.640802] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 12/07/2018 [11218.640802] RIP: 0010:native_smp_send_reschedule+0x3f/0x50 [11218.640802]
[Kernel-packages] [Bug 1937056] Re: Touchpad not working with ASUS TUF F15
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1937056 Title: Touchpad not working with ASUS TUF F15 Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: == SRU Justification == [Impact] Touchpad and touchscreen don't work on TGL-H laptops. [Fix] Update GPIO mapping so the values can match between Linux and BIOS. [Test] After applying the patch, both touchpad and touchscreen can work correctly. [Where problems could occur] If somehow any of the new pin value is incorrect, it can break devices that require Intel GPIO to work. == Original Bug Report == I am using Kubuntu 21.04 on my ASUS TUF F15 FX506HM_FX566HM. The touchpad isn't detected in Settings and neither in xinput, nor in cat /proc/bus/input/devices. Laptop model: ASUS TUF F15 FX506HM_FX566HM. Manufacturer of the Touchpad: Probably ELAN1203 When the symptom first appeared: From beginning Output of lsb_release -rd Description:Ubuntu 21.04 Release:21.04 Using kernel version 5.13.6. Also tried 5.11, 5.12.8, 5.12.15, 5.13.1, 5.13.2, 5.13.4, 5.13.5, 5.14-rc2, 5.14-rc3 Output of xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Asus Wireless Radio Control id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Button id=9[slave keyboard (3)] ↳ Sleep Button id=10 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=11 [slave keyboard (3)] ↳ Intel HID events id=12 [slave keyboard (3)] ↳ Intel HID 5 button array id=13 [slave keyboard (3)] ↳ Asus WMI hotkeys id=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)] Output of lspci :00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 05) :00:01.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #1 (rev 05) :00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) :00:04.0 Signal processing controller: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant (rev 05) :00:06.0 System peripheral: Intel Corporation Device 09ab :00:07.0 PCI bridge: Intel Corporation Tiger Lake-H Thunderbolt 4 PCI Express Root Port #0 (rev 05) :00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 05) :00:0a.0 Signal processing controller: Intel Corporation Tigerlake Telemetry Aggregator Driver (rev 01) :00:0d.0 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 USB Controller (rev 05) :00:0d.2 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 NHI #0 (rev 05) :00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller :00:14.0 USB controller: Intel Corporation Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller (rev 11) :00:14.2 RAM memory: Intel Corporation Tiger Lake-H Shared SRAM (rev 11) :00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H Serial IO I2C Controller #0 (rev 11) :00:16.0 Communication controller: Intel Corporation Tiger Lake-H Management Engine Interface (rev 11) :00:1c.0 PCI bridge: Intel Corporation Device 43bf (rev 11) :00:1d.0 PCI bridge: Intel Corporation Device 43b6 (rev 11) :00:1f.0 ISA bridge: Intel Corporation Tiger Lake-H LPC/eSPI Controller (rev 11) :00:1f.3 Audio device: Intel Corporation Tiger Lake-H HD Audio Controller (rev 11) :00:1f.4 SMBus: Intel
[Kernel-packages] [Bug 1934557] Re: Backlight (screen brightness) on Lenovo P14s AMD Gen2 inop
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1934557 Title: Backlight (screen brightness) on Lenovo P14s AMD Gen2 inop Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Confirmed Bug description: Backlight does not change. Neither with the keys, nor with the slider. Values in /sys/class/backlight/amdgpu_bl0/brightness do change. However without effect on the actual brightness of the screen, which seems to be stuck at maximum brightness. Following the instructions from here: https://wiki.ubuntu.com/Kernel/Debugging/Backlight ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: simon 1886 F pulseaudio /dev/snd/pcmC2D0p: simon 1886 F...m pulseaudio /dev/snd/controlC1: simon 1886 F pulseaudio /dev/snd/controlC0: simon 1886 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 3 09:46:53 2021 InstallationDate: Installed on 2021-07-03 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 21A0CTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 1.5 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET35W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0CTO1WW 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.5 dmi.modalias: dmi:bvnLENOVO:bvrR1MET35W(1.05):bd04/23/2021:br1.5:efr1.5:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0CTO1WW dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO == SRU justification: [Impact] backlight can't be controlled on AMD platform. [Fix] AUX doesn't work on HDR panel, fallback to PWM mode to make backlight be controlled. [Test] Verified on hardware, backlight brightness works fine. [Where problems could occur] It may break backlight control on AMD platform. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1934557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936708] Re: Wobbly graphics on built-in display since linux-image-5.11.0-22-generic
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1936708 Title: Wobbly graphics on built-in display since linux- image-5.11.0-22-generic Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Bug description: == SRU Justification == [Impact] Wobbly graphics after a kernel update. [Fix] Older panels may require more bandwidth then advertised, so we need to use max params for them. [Test] Multiple users tested with positive result. [Where problems could occur] This patch reverts to the old behavior, which is to use max parameters, for older panels. If there's any new panel reports with older DP version, this might change the behavior on it. == Original Bug Report == Lenovo laptop with Intel + Nvidia graphics. Since booting from linux-image-5.11.0-22-generic, the built-in display is unusable, with wobbling horizontal stripes from the disk decryption prompt onwards: https://www.youtube.com/watch?v=LyRTuPzCe2I HDMI output works fine. If I boot from linux-image-5.11.0-18-generic instead, all is well. If I use Recovery mode with linux-image-5.11.0-22-generic and continue bootup, it's usable but there's no HDMI output. I think others may be having this issue too: https://askubuntu.com/questions/1351188/weird-graphical-glitches-appears-only-on-integrated-display-on-any-ubuntu-base# ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 1598 F pulseaudio /dev/snd/controlC0: alex 1598 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 17 09:50:31 2021 InstallationDate: Installed on 2021-01-03 (194 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 80DU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-05-22 (55 days ago) dmi.bios.date: 08/18/2014 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN31WW(V1.14) dmi.board.asset.tag: 31900058WIN dmi.board.name: Lenovo Y70-70 Touch dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y70-70 Touch dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvr9ECN31WW(V1.14):bd08/18/2014:br1.49:efr1.49:svnLENOVO:pn80DU:pvrLenovoY70-70Touch:rvnLENOVO:rnLenovoY70-70Touch:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY70-70Touch: dmi.product.family: IDEAPAD dmi.product.name: 80DU dmi.product.sku: LENOVO_MT_80DU_BU_idea_FM_Lenovo Y70-70 Touch dmi.product.version: Lenovo Y70-70 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940085] Re: Sync drivers/gpu/drm from v5.14
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1940085 Title: Sync drivers/gpu/drm from v5.14 Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: Fix Committed Bug description: [Impact] We need to support new hardware from AMD and Intel, but backporting support to oem-5.13 is very laborous and prone to errors. [Fix] The only sane way to add a better base for the new hw is by syncing the whole drivers/gpu/drm directory from current 5.14. We also need to update drivers/dma-buf and include a minor abi revert for NVIDIA. [Test case] Boot current and new hw from AMD & Intel with the new kernel, and also test that NVIDIA dkms still builds. [Where things could go wrong] Any drm driver could regress, but since v5.14 is already at rc6 this is less likely, and for oem-5.13 we mostly care about drm/amdgpu and drm/i915 anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.13/+bug/1940085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934239] Re: mute/micmute LEDs no function on HP EliteBook 830 G8 Notebook PC
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux (Ubuntu Groovy) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1934239 Title: mute/micmute LEDs no function on HP EliteBook 830 G8 Notebook PC Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: New Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP EliteBook 830 G8 Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938689] Re: [SRU][H/OEM-5.10/OEM-5.13/U] Fix system hang after unplug tbt dock
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-oem-5.13 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1938689 Title: [SRU][H/OEM-5.10/OEM-5.13/U] Fix system hang after unplug tbt dock Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: New Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: New Bug description: SRU justification: [Impact] System hang after unplug thunderbolt dock with Intel igc lan. [Fix] igc driver continue reading and writing MMIO address after PCI device is unplugged. This cause system page fault, and system hang. Add safe check and prevent reading and writing the MMIO. The patch is in maintainer's tree, but not merged to Linus's tree. Due to the schedule, send SRU as SAUCE patch. [Test] Verified on hardware, after unplug the thunderbolt cable, system work fine. [Where problems could occur] It may break the igc driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1938689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927438] Re: Commits To Fix Kdump Failures
** Changed in: linux-azure (Ubuntu) Status: New => Fix Released -- 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/1927438 Title: Commits To Fix Kdump Failures Status in linux-azure package in Ubuntu: Fix Released Bug description: Microsoft received a customer report of failures when trying to take a kdump. This issue was resolved by three small Linux kernel fixes. Microsoft would like to request this following three commits in all supported releases: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1927438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-oem-5.13 (Ubuntu Focal) Status: In Progress => Fix Committed -- 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-oem-5.13 package in Ubuntu: Invalid 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-oem-5.13 source package in Focal: Fix Committed 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
[Kernel-packages] [Bug 1889137] Re: HWE kernel is missing firmwares
>From the warnings, this seems to be happening again on 20.04 with the latest HWE kernel (5.11) and i915 related firmware files. -- 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/1889137 Title: HWE kernel is missing firmwares Status in linux-firmware package in Ubuntu: Confirmed Bug description: After install linux-generic-hwe-18.04: update-initramfs: Generating /boot/initrd.img-5.4.0-42-generic W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169 W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_04.bin for module i915 W: Possible missing firmware /lib/firmware/i915/skl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_33.0.0.bin for module i915 cd /lib/firmware/rtl_nicroot@h2:~# cd /lib/firmware/rtl_nic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-18.04 (not installed) ProcVersionSignature: Ubuntu 5.4.0-7634.38~1595345317~20.04~a8480ad-generic 5.4.41 Uname: Linux 5.4.0-7634-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Jul 28 10:43:18 2020 HibernationDevice: #RESUME=UUID=9926e754-5beb-4353-ab1b-8e22f798efc6 RESUME=UUID=aa434b5f-9af6-4b25-986e-216eb0e20a2e InstallationDate: Installed on 2018-06-28 (760 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N551JK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-7634-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-7634-generic N/A linux-backports-modules-5.4.0-7634-generic N/A linux-firmware 1.187.2 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-30 (58 days ago) dmi.bios.date: 10/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N551JK.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N551JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN551JK.203:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N551JK dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1889137/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939844] Re: Intel GT2 ID[8086:46A0] is required
the pci-id is included by bug 1940085, but further fixes are still necessary -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1939844 Title: Intel GT2 ID[8086:46A0] is required Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: In Progress Bug description: [Impact] The GT2 ID is required. [Fix] This commit adds some ADL-P IDs and need to be cherry-picked 760759f2cf71 drm/i915/adl_p: Add PCI Devices IDs [Test] Currently we have no h/w to verify it. [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.13/+bug/1939844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940204] Re: AMDGPU: Fix System hang after resume from suspend
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1940204 Title: AMDGPU: Fix System hang after resume from suspend Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: New Status in linux-oem-5.13 source package in Hirsute: New Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: New Status in linux-oem-5.13 source package in Impish: New Bug description: [Impact] With AMD-GPU and don't use it as a display output, After multiple Suspend, system would hang. [Fix] Disable BACO for polaris12 series. BACO allow the graphics cards on Linux to support S4 / hibernation support. [Test Case] 1. Must plug AMD GPU and don't use it as display output 2. Plug DP/HDMI on iGPU. 3. Suspend machine. 4. check if system hangs. [Where problems could occur] Disable BACO would cause higher power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940204/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939937] Re: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability
** Changed in: linux (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939937 Title: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability Status in linux package in Ubuntu: Triaged Bug description: Hello, I use Ubuntu 20.04.2 LTS. The kernel was recently updated to 5.11 5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Since then the ath10k_core driver for my QCA9984 card is broken and only loads ~3 firmware versions from the 3.9.0.2 branch https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2 The firmware versions 70 / 86 / 91 are functional (but these firmware versions are already 2 years old) Responsible for this is the defective patch "ath10k: add target IRAM recovery feature support" https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.11=9af7c32ceca85da27867dd863697d2aafc80a3f8 If I understand the patch correctly then the driver tries to load firmware with the feature "iram recovery" into the memory of the host (for recvovery purposes). If this fails, the firmware is discarded and the network controller remains unusable. Of course, this is not a desirable behavior for optional firmware features. dmesg: [3.074952] ath: loading out-of-tree module taints kernel. [3.090522] ath: module verification failed: signature and/or required key missing - tainting kernel [3.110879] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [3.178741] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [3.229944] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [3.229948] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [3.230274] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00149 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 5f41acd7 [3.291329] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [3.291333] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [3.291678] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00149 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 5f41acd7 [4.463156] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 85498734 [4.520649] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 85498734 [7.047910] ath10k_pci :03:00.0: failed to copy target iram contents: -12 [7.103260] ath10k_pci :03:00.0: could not init core (-12) [7.103267] ath10k_pci :03:00.0: could not probe fw (-12) [7.108570] ath10k_pci :04:00.0: failed to copy target iram contents: -12 [7.163247] ath10k_pci :04:00.0: could not init core (-12) [7.163268] ath10k_pci :04:00.0: could not probe fw (-12) In the ath10k mailing list I found a second patch which makes it possible to load the latest firmware on the card again. https://www.mail-archive.com/ath10k@lists.infradead.org/msg13655.html I have tested the patch and it works. dmesg: [18245.610112] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [18245.674800] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [18245.731606] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [18245.731620] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [18245.733172] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00152 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 723f9771 [18245.790380] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [18245.790383] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [18245.790703] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00152 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 723f9771 [18246.963760] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 85498734 [18247.019699] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 85498734 [18249.514054] ath10k_pci :03:00.0: No hardware memory [18249.514057] ath10k_pci :03:00.0: failed to copy target iram contents: -12 [18249.570423] ath10k_pci :04:00.0: No hardware memory [18249.570426] ath10k_pci :04:00.0: failed to copy target iram
[Kernel-packages] [Bug 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)
Hi, I am having the same issue, with a TP Link Archer Tx50e (which uses Intel AX200). On boot logs: [8.084096] Bluetooth: hci0: command 0xfc05 tx timeout [8.084101] Bluetooth: hci0: Reading Intel version information failed (-110) [8.084110] Bluetooth: hci0: Intel Read version failed (-110) The workaround I use for this to make it work after my computer boot: sudo modprobe -r btusb && sudo modprobe btusb Ubuntu: 20.04 Kernel: 5.11.0-27-generic Is there a fix for this? Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939937] Re: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability
** Tags added: hirsute impish patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939937 Title: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability Status in linux package in Ubuntu: Triaged Bug description: Hello, I use Ubuntu 20.04.2 LTS. The kernel was recently updated to 5.11 5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Since then the ath10k_core driver for my QCA9984 card is broken and only loads ~3 firmware versions from the 3.9.0.2 branch https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2 The firmware versions 70 / 86 / 91 are functional (but these firmware versions are already 2 years old) Responsible for this is the defective patch "ath10k: add target IRAM recovery feature support" https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.11=9af7c32ceca85da27867dd863697d2aafc80a3f8 If I understand the patch correctly then the driver tries to load firmware with the feature "iram recovery" into the memory of the host (for recvovery purposes). If this fails, the firmware is discarded and the network controller remains unusable. Of course, this is not a desirable behavior for optional firmware features. dmesg: [3.074952] ath: loading out-of-tree module taints kernel. [3.090522] ath: module verification failed: signature and/or required key missing - tainting kernel [3.110879] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [3.178741] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [3.229944] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [3.229948] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [3.230274] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00149 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 5f41acd7 [3.291329] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [3.291333] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [3.291678] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00149 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 5f41acd7 [4.463156] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 85498734 [4.520649] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 85498734 [7.047910] ath10k_pci :03:00.0: failed to copy target iram contents: -12 [7.103260] ath10k_pci :03:00.0: could not init core (-12) [7.103267] ath10k_pci :03:00.0: could not probe fw (-12) [7.108570] ath10k_pci :04:00.0: failed to copy target iram contents: -12 [7.163247] ath10k_pci :04:00.0: could not init core (-12) [7.163268] ath10k_pci :04:00.0: could not probe fw (-12) In the ath10k mailing list I found a second patch which makes it possible to load the latest firmware on the card again. https://www.mail-archive.com/ath10k@lists.infradead.org/msg13655.html I have tested the patch and it works. dmesg: [18245.610112] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [18245.674800] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [18245.731606] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [18245.731620] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [18245.733172] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00152 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 723f9771 [18245.790380] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [18245.790383] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [18245.790703] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00152 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 723f9771 [18246.963760] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 85498734 [18247.019699] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 85498734 [18249.514054] ath10k_pci :03:00.0: No hardware memory [18249.514057] ath10k_pci :03:00.0: failed to copy target iram contents: -12 [18249.570423] ath10k_pci :04:00.0: No hardware memory [18249.570426] ath10k_pci :04:00.0: failed to copy target iram contents: -12
[Kernel-packages] [Bug 1940262] Re: The modalias in 470 is not compatible to 460
As per our discussion, this is fixed in LP: #1939673 ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Fix Committed ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided => Critical ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Importance: Critical => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1940262 Title: The modalias in 470 is not compatible to 460 Status in OEM Priority Project: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Committed Bug description: There are many modalias be removed from 470 those supporting in 460. If 470 is a LTS version and 460 will be transited to 470 then the driver installing will have different behavior between both version. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1940262/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1939743] Re: No Touchpad on TravelMate-P2 laptop
The suspend/resume does not seem to make any difference, and I cannot see the device listed in dmesg. The BIOS for this device doesn't appear to have an advanced mode, but if it helps the device is only capable of UEFI booting, so ubermix has been installed as UEFI. Attached is the output of the dmesg command. On Mon, Aug 16, 2021 at 11:10 PM Chris Chiu <1939...@bugs.launchpad.net> wrote: > Per the dmesg output, your touchpad should connect via i8042 interface and > seems detected. > [0.549357] serio: i8042 KBD port at 0x60,0x64 irq 1 > [0.549493] mousedev: PS/2 mouse device common for all mice > > Does the suspend/resume makes any difference? > > If not, you can go back to BIOS menu and change the BIOS setting from > "Basic mode" to "Advanced mode", then boot into Ubuntu to see if it's > detected or not. Please also paste the dmesg output here for the Advance > mode. Thanks. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1939743 > > Title: > No Touchpad on TravelMate-P2 laptop > > Status in linux package in Ubuntu: > New > > Bug description: > On the TravelMate P215-53 V1.10 by Acer when running Ubuntu, the > trackpad is entirely non-functional and does not appear in the > /proc/bus/input/devices list. A wired usb mouse works perfectly, but > there does not seem to be a tweak that enables the trackpad to be seen > by the kernel. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: linux-image-5.4.0-54-generic 5.4.0-54.60 > ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 > Uname: Linux 5.4.0-54-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Thu Aug 12 14:30:39 2021 > InstallationDate: Installed on 2020-12-09 (245 days ago) > InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 > (20200731) > MachineType: Acer TravelMate P215-53 > ProcFB: 0 EFI VGA > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic > root=/dev/nvme0n1p2 ro quiet splash vt.handoff=1 > RelatedPackageVersions: >linux-restricted-modules-5.4.0-54-generic N/A >linux-backports-modules-5.4.0-54-generic N/A >linux-firmware1.187.15 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > WifiSyslog: > > dmi.bios.date: 12/17/2020 > dmi.bios.vendor: INSYDE Corp. > dmi.bios.version: V1.10 > dmi.board.asset.tag: Type2 - Board Asset Tag > dmi.board.name: BassDrum_TL > dmi.board.vendor: TGL > dmi.board.version: V1.10 > dmi.chassis.type: 10 > dmi.chassis.vendor: Chassis Manufacturer > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnINSYDECorp.:bvrV1.10:bd12/17/2020:svnAcer:pnTravelMateP215-53:pvrV1.10:rvnTGL:rnBassDrum_TL:rvrV1.10:cvnChassisManufacturer:ct10:cvrChassisVersion: > dmi.product.family: TravelMate P2 > dmi.product.name: TravelMate P215-53 > dmi.product.sku: > dmi.product.version: V1.10 > dmi.sys.vendor: Acer > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939743/+subscriptions > > ** Attachment added: "dmesg" https://bugs.launchpad.net/bugs/1939743/+attachment/5518518/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939743 Title: No Touchpad on TravelMate-P2 laptop Status in linux package in Ubuntu: New Bug description: On the TravelMate P215-53 V1.10 by Acer when running Ubuntu, the trackpad is entirely non-functional and does not appear in the /proc/bus/input/devices list. A wired usb mouse works perfectly, but there does not seem to be a tweak that enables the trackpad to be seen by the kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 12 14:30:39 2021 InstallationDate: Installed on 2020-12-09 (245 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer TravelMate P215-53 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=/dev/nvme0n1p2 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.15 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 12/17/2020 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.10 dmi.board.asset.tag:
[Kernel-packages] [Bug 1940285] Re: Laptop screen flickering on kernels above 5.4 (not included)
** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940285 Title: Laptop screen flickering on kernels above 5.4 (not included) Status in linux package in Ubuntu: Incomplete Bug description: Recently, I installed Ubuntu 21.04 on my laptop and I was having the same problem I had like with others distros such as Fedora; for some reason, the screen just ramdonly and briefly turns off, (more like a flickering) and it also "autoregulates" a the brightness, just a little bit down and then a little bit up. I noticed I don't have this problem on Linux Mint, and I also noticed that going back to Kernel 5.8 on either Ubuntu 21.04 or 20.04.2 this problem stops. I have been using Mainline ( https://github.com/bkw777/mainline ) to install previous kernels (5.8 and 5.4 wok just fine, but anything above this problem comes again). Thanks so much beforehand. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940285] Re: Laptop screen flickering on kernels above 5.4 (not included)
I should especifice also that my laptop (Teclast F7) uses an Intel Celeron n3450 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940285 Title: Laptop screen flickering on kernels above 5.4 (not included) Status in linux package in Ubuntu: Incomplete Bug description: Recently, I installed Ubuntu 21.04 on my laptop and I was having the same problem I had like with others distros such as Fedora; for some reason, the screen just ramdonly and briefly turns off, (more like a flickering) and it also "autoregulates" a the brightness, just a little bit down and then a little bit up. I noticed I don't have this problem on Linux Mint, and I also noticed that going back to Kernel 5.8 on either Ubuntu 21.04 or 20.04.2 this problem stops. I have been using Mainline ( https://github.com/bkw777/mainline ) to install previous kernels (5.8 and 5.4 wok just fine, but anything above this problem comes again). Thanks so much beforehand. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940285] Re: Laptop screen flickering on kernels above 5.4 (not included)
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1940285 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Many details have not been provided; including and especially video hardware & kernel modules in use. the apport-collect will gather this information and allow this bug to be worked on. Currently I believe it's incomplete and I'm marking it as such. Once you've run apport-collect, please change the status to "New". If you believe I'm in error, you can leave a comment explaining why, then change status to "New", however the bug may not be worked on until such details have been provided. Note: if you're not using Ubuntu or flavor of Ubuntu (eg. Linux Mint is neither), additional packages may require install before you can run `apport-collect`. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940285 Title: Laptop screen flickering on kernels above 5.4 (not included) Status in linux package in Ubuntu: Incomplete Bug description: Recently, I installed Ubuntu 21.04 on my laptop and I was having the same problem I had like with others distros such as Fedora; for some reason, the screen just ramdonly and briefly turns off, (more like a flickering) and it also "autoregulates" a the brightness, just a little bit down and then a little bit up. I noticed I don't have this problem on Linux Mint, and I also noticed that going back to Kernel 5.8 on either Ubuntu 21.04 or 20.04.2 this problem stops. I have been using Mainline ( https://github.com/bkw777/mainline ) to install previous kernels (5.8 and 5.4 wok just fine, but anything above this problem comes again). Thanks so much beforehand. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940285] Re: Laptop screen flickering on kernels above 5.4 (not included)
I had to select a package. Since I have read that problems regarding the kernel should be listed as "linux" (and I think this is the case), that is why I selected that package. ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940285 Title: Laptop screen flickering on kernels above 5.4 (not included) Status in linux package in Ubuntu: Incomplete Bug description: Recently, I installed Ubuntu 21.04 on my laptop and I was having the same problem I had like with others distros such as Fedora; for some reason, the screen just ramdonly and briefly turns off, (more like a flickering) and it also "autoregulates" a the brightness, just a little bit down and then a little bit up. I noticed I don't have this problem on Linux Mint, and I also noticed that going back to Kernel 5.8 on either Ubuntu 21.04 or 20.04.2 this problem stops. I have been using Mainline ( https://github.com/bkw777/mainline ) to install previous kernels (5.8 and 5.4 wok just fine, but anything above this problem comes again). Thanks so much beforehand. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940285] [NEW] Laptop screen flickering on kernels above 5.4 (not included)
You have been subscribed to a public bug: Recently, I installed Ubuntu 21.04 on my laptop and I was having the same problem I had like with others distros such as Fedora; for some reason, the screen just ramdonly and briefly turns off, (more like a flickering) and it also "autoregulates" a the brightness, just a little bit down and then a little bit up. I noticed I don't have this problem on Linux Mint, and I also noticed that going back to Kernel 5.8 on either Ubuntu 21.04 or 20.04.2 this problem stops. I have been using Mainline ( https://github.com/bkw777/mainline ) to install previous kernels (5.8 and 5.4 wok just fine, but anything above this problem comes again). Thanks so much beforehand. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment flickering laptop screen -- Laptop screen flickering on kernels above 5.4 (not included) https://bugs.launchpad.net/bugs/1940285 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940204] Re: AMDGPU: Fix System hang after resume from suspend
** Changed in: linux (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1940204 Title: AMDGPU: Fix System hang after resume from suspend Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: New Status in linux-oem-5.13 source package in Hirsute: New Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: New Status in linux-oem-5.13 source package in Impish: New Bug description: [Impact] With AMD-GPU and don't use it as a display output, After multiple Suspend, system would hang. [Fix] Disable BACO for polaris12 series. BACO allow the graphics cards on Linux to support S4 / hibernation support. [Test Case] 1. Must plug AMD GPU and don't use it as display output 2. Plug DP/HDMI on iGPU. 3. Suspend machine. 4. check if system hangs. [Where problems could occur] Disable BACO would cause higher power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940204/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940134] Re: fails to launch linux L2 guests on AMD
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940134 Title: fails to launch linux L2 guests on AMD Status in linux package in Ubuntu: New Status in linux-hwe-5.8 package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-hwe-5.8 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-hwe-5.8 source package in Focal: Invalid Status in linux source package in Hirsute: Invalid Status in linux-hwe-5.8 source package in Hirsute: Invalid Bug description: [Impact] Users won't be able to run a Linux inside a Linux guest. [Test case] Launch an L1 guest with libvirt, then launch an L2 guest using qemu inside that first/L1 guest. [Potential regression] There might be reduced performance due to vmexits for interrupt handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880645] Re: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1880645 Title: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H 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.13 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Won't Fix Status in linux source package in Groovy: Won't Fix Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.13 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.13 source package in Hirsute: Invalid Status in linux-oem-5.6 source package in Hirsute: Invalid Bug description: [Impact] The IPv6: mtu exception plus redirect test in icmp_redirect.sh test from kselftest/net is expected to fail due to a known bug in the IPv6 logic. When trying to run this test you will see this sub test fail with: TEST: IPv6: mtu exception plus redirect [FAIL] and thus causing non-zero return value for this script. [Fix] * 0a36a75c681880 selftests: icmp_redirect: support expected failures This fix can be cherry-picked into all affected series. And it has already landed on Unstable, test passed with Impish 5.13. Although we have this script in Focal kernel as well, but it's not being executed at all. This is another issue that will be dealt in a different bug report. [Test] Run the patched icmp_redirect.sh test manually in tools/testing/selftests/net, this sub-test will be marked as XFAIL and the return value of this script will be 0: $ sudo ./icmp_redirect.sh # Routing with nexthop objects and VRF # TEST: IPv6: mtu exception plus redirect [XFAIL] Tests passed: 36 Tests failed: 0 Tests xfailed: 4 $ echo $? 0 [Where problems could occur] Change limited to testing tool, not affecting actual kernel functionality. The only possible issue that I can think of is that as this script is no longer complaining about this failure, people might forgot there is such an issue exist in ipv6. [Original Bug Report] Issue found on Focal 5.6.0-1011.11-oem ubuntu@rizzo:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./icmp_redirect.sh ### Legacy routing ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Legacy routing with VRF ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect
[Kernel-packages] [Bug 1929027] Re: drm/i915: Drop force_probe requirement for ADL-S
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 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-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released 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: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929902] Re: [EHL] enable USB-dw3
Hi @chaoqin, I can't find the device "8086:4b7e", I have also tried the mainline kernel v5.14-rc6 but no luck. I also tried to boot into the UEFI shell and use the 'pci' command to list the devices, but still no luck. [1] Do I need to enable some settings in BIOS so that I can see the device "8086:4b7e"? Thanks! BIOS version: EHLSFWI1.R00.3044.A01.2101210945 -- [1] Shell> pci Seg Bus Dev Func --- --- --- 00 00 0000 ==> Bridge Device - Host/PCI bridge Vendor 8086 Device 452E Prog Interface 0 00 00 0200 ==> Display Controller - VGA/8514 controller Vendor 8086 Device 4571 Prog Interface 0 00 00 0800 ==> Base System Peripherals - Other system peripheral Vendor 8086 Device 4511 Prog Interface 0 00 00 1000 ==> Serial Bus Controllers - Other bus type Vendor 8086 Device 4B44 Prog Interface 0 00 00 1001 ==> Serial Bus Controllers - Other bus type Vendor 8086 Device 4B45 Prog Interface 0 00 00 1100 ==> Simple Communications Controllers - Other communication device Vendor 8086 Device 4B96 Prog Interface 8 00 00 1101 ==> Simple Communications Controllers - Other communication device Vendor 8086 Device 4B97 Prog Interface 9 00 00 1300 ==> Serial Bus Controllers - Other bus type Vendor 8086 Device 4B84 Prog Interface 14 00 00 1400 ==> Serial Bus Controllers - USB Vendor 8086 Device 4B7D Prog Interface 30 00 00 1402 ==> Memory Controller - RAM memory controller Vendor 8086 Device 4B7F Prog Interface 0 00 00 1500 ==> Serial Bus Controllers - Other bus type Vendor 8086 Device 4B78 Prog Interface 0 00 00 1502 ==> Serial Bus Controllers - Other bus type Vendor 8086 Device 4B7A Prog Interface 0 00 00 1503 ==> Serial Bus Controllers - Other bus type Vendor 8086 Device 4B7B Prog Interface 0 00 00 1600 ==> Simple Communications Controllers - Other communication device Vendor 8086 Device 4B70 Prog Interface 0 00 00 1700 ==> Mass Storage Controller - Serial ATA controller Vendor 8086 Device 4B63 Prog Interface 1 00 00 1900 ==> Serial Bus Controllers - Other bus type Vendor 8086 Device 4B4B Prog Interface 0 00 00 1902 ==> Simple Communications Controllers - Other communication device Vendor 8086 Device 4B4D Prog Interface 0 00 00 1A00 ==> Base System Peripherals - SD Host controller Vendor 8086 Device 4B47 Prog Interface 1 00 00 1A01 ==> Base System Peripherals - SD Host controller Vendor 8086 Device 4B48 Prog Interface 1 00 00 1B00 ==> Serial Bus Controllers - Other bus type Vendor 8086 Device 4BB9 Prog Interface 0 00 00 1B01 ==> Serial Bus Controllers - Other bus type Vendor 8086 Device 4BBA Prog Interface 1 00 00 1B06 ==> Serial
[Kernel-packages] [Bug 1866591] Re: vmx_pending_event_test failed in ubuntu_kvm_unit_tests
** Tags added: xe -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866591 Title: vmx_pending_event_test failed in ubuntu_kvm_unit_tests Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Issue found on bare-metal node r5.metal, i3.metal, c5.metal timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.132aLPLaXz -smp 1 -cpu host,+vmx -append vmx_pending_event_test # -initrd /tmp/tmp.nWvh3t6ooD enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: vmx_pending_event_test FAIL: x86/vmx_tests.c:2184: Assertion failed: (expected) == (actual) LHS: 0x0012 - ''''''''''''''0001'0010 - 18 RHS: 00 - ''''''''''''''' - 0 Expected VMX_VMCALL, got VMX_EXC_NMI. STACK: 405e1c 405e46 4060e4 4061a1 401556 4039f1 400312 SUMMARY: 4 tests, 1 unexpected failures FAIL vmx_pending_event_test (4 tests, 1 unexpected failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853797] Re: pmu in ubuntu_kvm_unit_tests fails
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oracle (Ubuntu) Status: New => Confirmed -- 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/1853797 Title: pmu in ubuntu_kvm_unit_tests fails Status in ubuntu-kernel-tests: Triaged Status in linux-oracle package in Ubuntu: Confirmed Status in linux-oracle-5.0 package in Ubuntu: Confirmed Bug description: 4 failures: FAIL: rdpmc: fixed cntr-0 FAIL: rdpmc: fixed cntr-1 FAIL: rdpmc: fixed cntr-2 FAIL: all counters Test log: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/pmu' BUILD_HEAD=e2c275c4 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.UfviUpwSjB -smp 1 -cpu host # -initrd /tmp/tmp.7jA5GK5kyl enabling apic paging enabled cr0 = 80010011 cr3 = 45a000 cr4 = 20 PMU version: 2 GP counters: 4 GP counter width: 48 Mask length: 7 Fixed counters: 3 Fixed counter width: 48 PASS: core cycles-0 PASS: core cycles-1 PASS: core cycles-2 PASS: core cycles-3 PASS: instructions-0 PASS: instructions-1 PASS: instructions-2 PASS: instructions-3 PASS: ref cycles-0 PASS: ref cycles-1 PASS: ref cycles-2 PASS: ref cycles-3 PASS: llc refference-0 PASS: llc refference-1 PASS: llc refference-2 PASS: llc refference-3 PASS: llc misses-0 PASS: llc misses-1 PASS: llc misses-2 PASS: llc misses-3 PASS: branches-0 PASS: branches-1 PASS: branches-2 PASS: branches-3 PASS: branch misses-0 PASS: branch misses-1 PASS: branch misses-2 PASS: branch misses-3 PASS: fixed-0 PASS: fixed-1 PASS: fixed-2 PASS: rdpmc: cntr-0 PASS: rdpmc: fast-0 PASS: rdpmc: cntr-1 PASS: rdpmc: fast-1 PASS: rdpmc: cntr-2 PASS: rdpmc: fast-2 PASS: rdpmc: cntr-3 PASS: rdpmc: fast-3 FAIL: rdpmc: fixed cntr-0 PASS: rdpmc: fixed fast-0 FAIL: rdpmc: fixed cntr-1 PASS: rdpmc: fixed fast-1 FAIL: rdpmc: fixed cntr-2 PASS: rdpmc: fixed fast-2 FAIL: all counters PASS: overflow: cntr-0 PASS: overflow: status-0 PASS: overflow: status clear-0 PASS: overflow: irq-0 PASS: overflow: cntr-1 PASS: overflow: status-1 PASS: overflow: status clear-1 PASS: overflow: irq-1 PASS: overflow: cntr-2 PASS: overflow: status-2 PASS: overflow: status clear-2 PASS: overflow: irq-2 PASS: overflow: cntr-3 PASS: overflow: status-3 PASS: overflow: status clear-3 PASS: overflow: irq-3 PASS: overflow: cntr-4 PASS: overflow: status-4 PASS: overflow: status clear-4 PASS: overflow: irq-4 PASS: cmask SUMMARY: 67 tests, 4 unexpected failures FAIL pmu (67 tests, 4 unexpected failures) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1005-oracle 5.0.0-1005.9 ProcVersionSignature: User Name 5.0.0-1005.9-oracle 5.0.21 Uname: Linux 5.0.0-1005-oracle x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Nov 25 04:29:43 2019 SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1853797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866591] Re: vmx_pending_event_test failed in ubuntu_kvm_unit_tests
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866591 Title: vmx_pending_event_test failed in ubuntu_kvm_unit_tests Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Issue found on bare-metal node r5.metal, i3.metal, c5.metal timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.132aLPLaXz -smp 1 -cpu host,+vmx -append vmx_pending_event_test # -initrd /tmp/tmp.nWvh3t6ooD enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: vmx_pending_event_test FAIL: x86/vmx_tests.c:2184: Assertion failed: (expected) == (actual) LHS: 0x0012 - ''''''''''''''0001'0010 - 18 RHS: 00 - ''''''''''''''' - 0 Expected VMX_VMCALL, got VMX_EXC_NMI. STACK: 405e1c 405e46 4060e4 4061a1 401556 4039f1 400312 SUMMARY: 4 tests, 1 unexpected failures FAIL vmx_pending_event_test (4 tests, 1 unexpected failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917616] Re: vmx test from ubuntu_kvm_unit_tests failed on Bionic/Focal
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917616 Title: vmx test from ubuntu_kvm_unit_tests failed on Bionic/Focal Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Bug description: Appearing in bionic 5.4.0-67.75~18.04.1 affecting lowlatency and hwe flavors. 2538. 02/25 00:10:11 DEBUG| utils:0153| [stdout] Unhandled exception 13 #GP at ip 004071a3 2539. 02/25 00:10:11 DEBUG| utils:0153| [stdout] error_code= rflags=00010006 cs=0008 2540. 02/25 00:10:11 DEBUG| utils:0153| [stdout] rax=0078 rcx=0809 rdx= rbx=0009 2541. 02/25 00:10:11 DEBUG| utils:0153| [stdout] rbp=0047efdf rsi=0042568d rdi=0042568d 2542. 02/25 00:10:11 DEBUG| utils:0153| [stdout] r8=000a r9=03f8 r10=000d r11= 2543. 02/25 00:10:11 DEBUG| utils:0153| [stdout] r12= r13= r14=00403dcc r15= 2544. 02/25 00:10:11 DEBUG| utils:0153| [stdout] cr0=80010031 cr2=e000 cr3=00477000 cr4=2020 2545. 02/25 00:10:11 DEBUG| utils:0153| [stdout] cr8=0007 2546. 02/25 00:10:11 DEBUG| utils:0153| [stdout] STACK: @4071a3 40170b 4004dd 2547. 02/25 00:10:11 DEBUG| utils:0153| [stdout] FAIL vmx 2548. 02/25 00:10:11 ERROR| test:0414| Exception escaping from test: 2549. Traceback (most recent call last): 2550. File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec 2551. _call_test_function(self.execute, *p_args, **p_dargs) 2552. File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function 2553. return func(*args, **dargs) 2554. File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute 2555. postprocess_profiled_run, args, dargs) 2556. File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once 2557. self.run_once(*args, **dargs) 2558. File "/home/ubuntu/autotest/client/tests/ubuntu_kvm_unit_tests/ubuntu_kvm_unit_tests.py", line 80, in run_once 2559. raise error.TestError("Test failed for {}".format(test_name)) 2560. TestError: Test failed for vmx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1917616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923284] Re: vmx_host_state_area / vmx_intr_window_test / vmx_nmi_window_test / vmx_hlt_with_rvi_test fails with timeout on Bionic
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923284 Title: vmx_host_state_area / vmx_intr_window_test / vmx_nmi_window_test / vmx_hlt_with_rvi_test fails with timeout on Bionic Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: vmx_host_state_area / vmx_intr_window_test / vmx_nmi_window_test fails with timeout on Bionic 4.15.0-141.145 host rizzo this failed on the previous version of bionic 4.15.0-140.144 as well, so not a regression. vmx_host_state_area has an error before giving timeout: 04/10 01:29:18 DEBUG| utils:0153| [stderr] KVM: entry failed, hardware error 0x8021 04/10 01:29:18 DEBUG| utils:0153| [stderr] 04/10 01:29:18 DEBUG| utils:0153| [stderr] If you're running a guest on an Intel machine without unrestricted mode 04/10 01:29:18 DEBUG| utils:0153| [stderr] support, the failure can be most likely due to the guest entering an invalid 04/10 01:29:18 DEBUG| utils:0153| [stderr] state for Intel VT. For example, the guest maybe running in big real mode 04/10 01:29:18 DEBUG| utils:0153| [stderr] which is not supported on less recent Intel processors. 04/10 01:29:18 DEBUG| utils:0153| [stderr] 04/10 01:29:47 DEBUG| utils:0153| [stderr] qemu-system-x86_64: terminating on signal 15 from pid 21956 (timeout) 04/10 01:29:47 DEBUG| utils:0153| [stdout] FAIL vmx_host_state_area (timeout; duration=30) vmx_intr_window_test / vmx_nmi_window_test shows passing until the timeout: 28. 04/10 01:29:49 DEBUG| utils:0153| [stdout] PASS: interrupt-window: active, RFLAGS.IF = 0: Activity state (0) is 'ACTIVE' 29. 04/10 01:30:19 DEBUG| utils:0153| [stderr] qemu-system-x86_64: terminating on signal 15 from pid 22161 (timeout) 30. 04/10 01:30:19 DEBUG| utils:0153| [stdout] FAIL vmx_intr_window_test (timeout; duration=30) 31. 04/10 01:30:19 ERROR| test:0414| Exception escaping from test: -- 26. 04/10 01:30:24 DEBUG| utils:0153| [stdout] PASS: NMI-window: active, blocking by NMI: #UD handler executed once (actual 1 times) 27. 04/10 01:30:53 DEBUG| utils:0153| [stderr] qemu-system-x86_64: terminating on signal 15 from pid 22570 (timeout) 28. 04/10 01:30:53 DEBUG| utils:0153| [stdout] FAIL vmx_nmi_window_test (timeout; duration=30) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1923284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853797] Re: pmu in ubuntu_kvm_unit_tests fails
** Tags added: hinted -- 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/1853797 Title: pmu in ubuntu_kvm_unit_tests fails Status in ubuntu-kernel-tests: Triaged Status in linux-oracle package in Ubuntu: New Status in linux-oracle-5.0 package in Ubuntu: Confirmed Bug description: 4 failures: FAIL: rdpmc: fixed cntr-0 FAIL: rdpmc: fixed cntr-1 FAIL: rdpmc: fixed cntr-2 FAIL: all counters Test log: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/pmu' BUILD_HEAD=e2c275c4 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.UfviUpwSjB -smp 1 -cpu host # -initrd /tmp/tmp.7jA5GK5kyl enabling apic paging enabled cr0 = 80010011 cr3 = 45a000 cr4 = 20 PMU version: 2 GP counters: 4 GP counter width: 48 Mask length: 7 Fixed counters: 3 Fixed counter width: 48 PASS: core cycles-0 PASS: core cycles-1 PASS: core cycles-2 PASS: core cycles-3 PASS: instructions-0 PASS: instructions-1 PASS: instructions-2 PASS: instructions-3 PASS: ref cycles-0 PASS: ref cycles-1 PASS: ref cycles-2 PASS: ref cycles-3 PASS: llc refference-0 PASS: llc refference-1 PASS: llc refference-2 PASS: llc refference-3 PASS: llc misses-0 PASS: llc misses-1 PASS: llc misses-2 PASS: llc misses-3 PASS: branches-0 PASS: branches-1 PASS: branches-2 PASS: branches-3 PASS: branch misses-0 PASS: branch misses-1 PASS: branch misses-2 PASS: branch misses-3 PASS: fixed-0 PASS: fixed-1 PASS: fixed-2 PASS: rdpmc: cntr-0 PASS: rdpmc: fast-0 PASS: rdpmc: cntr-1 PASS: rdpmc: fast-1 PASS: rdpmc: cntr-2 PASS: rdpmc: fast-2 PASS: rdpmc: cntr-3 PASS: rdpmc: fast-3 FAIL: rdpmc: fixed cntr-0 PASS: rdpmc: fixed fast-0 FAIL: rdpmc: fixed cntr-1 PASS: rdpmc: fixed fast-1 FAIL: rdpmc: fixed cntr-2 PASS: rdpmc: fixed fast-2 FAIL: all counters PASS: overflow: cntr-0 PASS: overflow: status-0 PASS: overflow: status clear-0 PASS: overflow: irq-0 PASS: overflow: cntr-1 PASS: overflow: status-1 PASS: overflow: status clear-1 PASS: overflow: irq-1 PASS: overflow: cntr-2 PASS: overflow: status-2 PASS: overflow: status clear-2 PASS: overflow: irq-2 PASS: overflow: cntr-3 PASS: overflow: status-3 PASS: overflow: status clear-3 PASS: overflow: irq-3 PASS: overflow: cntr-4 PASS: overflow: status-4 PASS: overflow: status clear-4 PASS: overflow: irq-4 PASS: cmask SUMMARY: 67 tests, 4 unexpected failures FAIL pmu (67 tests, 4 unexpected failures) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1005-oracle 5.0.0-1005.9 ProcVersionSignature: User Name 5.0.0-1005.9-oracle 5.0.21 Uname: Linux 5.0.0-1005-oracle x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Nov 25 04:29:43 2019 SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1853797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853797] Re: pmu in ubuntu_kvm_unit_tests fails
Found on xenial/linux-oracle/4.15.0-1079.87~16.04.1 and xenial/linux- oracle/4.15.0-1077.85~16.04.1 (Oracle instances). ** Tags added: 4.15 sru-20210719 xenial -- 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/1853797 Title: pmu in ubuntu_kvm_unit_tests fails Status in ubuntu-kernel-tests: Triaged Status in linux-oracle package in Ubuntu: New Status in linux-oracle-5.0 package in Ubuntu: Confirmed Bug description: 4 failures: FAIL: rdpmc: fixed cntr-0 FAIL: rdpmc: fixed cntr-1 FAIL: rdpmc: fixed cntr-2 FAIL: all counters Test log: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/pmu' BUILD_HEAD=e2c275c4 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.UfviUpwSjB -smp 1 -cpu host # -initrd /tmp/tmp.7jA5GK5kyl enabling apic paging enabled cr0 = 80010011 cr3 = 45a000 cr4 = 20 PMU version: 2 GP counters: 4 GP counter width: 48 Mask length: 7 Fixed counters: 3 Fixed counter width: 48 PASS: core cycles-0 PASS: core cycles-1 PASS: core cycles-2 PASS: core cycles-3 PASS: instructions-0 PASS: instructions-1 PASS: instructions-2 PASS: instructions-3 PASS: ref cycles-0 PASS: ref cycles-1 PASS: ref cycles-2 PASS: ref cycles-3 PASS: llc refference-0 PASS: llc refference-1 PASS: llc refference-2 PASS: llc refference-3 PASS: llc misses-0 PASS: llc misses-1 PASS: llc misses-2 PASS: llc misses-3 PASS: branches-0 PASS: branches-1 PASS: branches-2 PASS: branches-3 PASS: branch misses-0 PASS: branch misses-1 PASS: branch misses-2 PASS: branch misses-3 PASS: fixed-0 PASS: fixed-1 PASS: fixed-2 PASS: rdpmc: cntr-0 PASS: rdpmc: fast-0 PASS: rdpmc: cntr-1 PASS: rdpmc: fast-1 PASS: rdpmc: cntr-2 PASS: rdpmc: fast-2 PASS: rdpmc: cntr-3 PASS: rdpmc: fast-3 FAIL: rdpmc: fixed cntr-0 PASS: rdpmc: fixed fast-0 FAIL: rdpmc: fixed cntr-1 PASS: rdpmc: fixed fast-1 FAIL: rdpmc: fixed cntr-2 PASS: rdpmc: fixed fast-2 FAIL: all counters PASS: overflow: cntr-0 PASS: overflow: status-0 PASS: overflow: status clear-0 PASS: overflow: irq-0 PASS: overflow: cntr-1 PASS: overflow: status-1 PASS: overflow: status clear-1 PASS: overflow: irq-1 PASS: overflow: cntr-2 PASS: overflow: status-2 PASS: overflow: status clear-2 PASS: overflow: irq-2 PASS: overflow: cntr-3 PASS: overflow: status-3 PASS: overflow: status clear-3 PASS: overflow: irq-3 PASS: overflow: cntr-4 PASS: overflow: status-4 PASS: overflow: status clear-4 PASS: overflow: irq-4 PASS: cmask SUMMARY: 67 tests, 4 unexpected failures FAIL pmu (67 tests, 4 unexpected failures) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1005-oracle 5.0.0-1005.9 ProcVersionSignature: User Name 5.0.0-1005.9-oracle 5.0.21 Uname: Linux 5.0.0-1005-oracle x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Nov 25 04:29:43 2019 SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1853797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940261] Re: ubuntu_seccomp 11-basic-basic_errors failure on X/oracle
** Attachment added: "Full log" https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1940261/+attachment/5518481/+files/sru-oracle-oracle-VM.Standard2.1-ubuntu_seccomp-log.txt -- 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/1940261 Title: ubuntu_seccomp 11-basic-basic_errors failure on X/oracle Status in ubuntu-kernel-tests: New Status in linux-oracle package in Ubuntu: New Status in linux-oracle source package in Xenial: New Bug description: Xenial/Oracle 4.15.0-1079.87~16.04.1 fails 11-basic-basic_errors test from ubuntu_seccomp on all Oracle cloud instances: batch name: 11-basic-basic_errors test mode: c test type: basic Test 11-basic-basic_errors%%001-1 result: FAILURE 11-basic-basic_errors rc=255 Base kernel bionic/linux-oracle/4.15.0-1079.87 is OK. Previous cycle (xenial/linux-oracle/4.15.0-1077.85~16.04.1) is OK, so this looks like regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1940261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940262] Re: The modalias in 470 is not compatible to 460
The attachment is what I got from nvidia-driver-[460,470], please see the diff[1]. [1] $ diff nvidia-4* 1,1345c1 < Modaliases: nvidia(pci:v10DEd0FD2sv*sd*bc03sc*i* < pci:v10DEd1028sv*sd*bc03sc*i* < pci:v10DEd0595sv*sd*bc03sc*i* < pci:v10DEd0FD2sv*sd*bc03sc*i* < pci:v10DEd1028sv*sd*bc03sc*i* < pci:v10DEd05B2sv*sd*bc03sc*i* < pci:v10DEd0FE3sv*sd*bc03sc*i* < pci:v10DEd103Csv*sd*bc03sc*i* < pci:v10DEd2B16sv*sd*bc03sc*i* < pci:v10DEd0FE3sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd3675sv*sd*bc03sc*i* < pci:v10DEd1185sv*sd*bc03sc*i* < pci:v10DEd10DEsv*sd*bc03sc*i* < pci:v10DEd106Fsv*sd*bc03sc*i* < pci:v10DEd1189sv*sd*bc03sc*i* < pci:v10DEd10DEsv*sd*bc03sc*i* < pci:v10DEd1074sv*sd*bc03sc*i* < pci:v10DEd1199sv*sd*bc03sc*i* < pci:v10DEd1458sv*sd*bc03sc*i* < pci:v10DEdD001sv*sd*bc03sc*i* < pci:v10DEd11E3sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd3683sv*sd*bc03sc*i* < pci:v10DEd1290sv*sd*bc03sc*i* < pci:v10DEd103Csv*sd*bc03sc*i* < pci:v10DEd2AFAsv*sd*bc03sc*i* < pci:v10DEd1292sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd3675sv*sd*bc03sc*i* < pci:v10DEd1292sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd367Csv*sd*bc03sc*i* < pci:v10DEd1292sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd3684sv*sd*bc03sc*i* < pci:v10DEd1295sv*sd*bc03sc*i* < pci:v10DEd103Csv*sd*bc03sc*i* < pci:v10DEd2B0Dsv*sd*bc03sc*i* < pci:v10DEd1295sv*sd*bc03sc*i* < pci:v10DEd103Csv*sd*bc03sc*i* < pci:v10DEd2B0Fsv*sd*bc03sc*i* < pci:v10DEd1295sv*sd*bc03sc*i* < pci:v10DEd103Csv*sd*bc03sc*i* < pci:v10DEd2B20sv*sd*bc03sc*i* < pci:v10DEd1295sv*sd*bc03sc*i* < pci:v10DEd103Csv*sd*bc03sc*i* < pci:v10DEd2B21sv*sd*bc03sc*i* < pci:v10DEd1295sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd367Asv*sd*bc03sc*i* < pci:v10DEd1295sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd367Csv*sd*bc03sc*i* < pci:v10DEd1299sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd30BBsv*sd*bc03sc*i* < pci:v10DEd1299sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd30DAsv*sd*bc03sc*i* < pci:v10DEd1299sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd30DCsv*sd*bc03sc*i* < pci:v10DEd1299sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd30DDsv*sd*bc03sc*i* < pci:v10DEd1299sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd30DFsv*sd*bc03sc*i* < pci:v10DEd1299sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd3117sv*sd*bc03sc*i* < pci:v10DEd1299sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd361Bsv*sd*bc03sc*i* < pci:v10DEd1299sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd362Dsv*sd*bc03sc*i* < pci:v10DEd1299sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd362Esv*sd*bc03sc*i* < pci:v10DEd1299sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd3630sv*sd*bc03sc*i* < pci:v10DEd1299sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd3637sv*sd*bc03sc*i* < pci:v10DEd1299sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd369Bsv*sd*bc03sc*i* < pci:v10DEd1299sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd36A7sv*sd*bc03sc*i* < pci:v10DEd1299sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd36AFsv*sd*bc03sc*i* < pci:v10DEd1299sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd36F0sv*sd*bc03sc*i* < pci:v10DEd1299sv*sd*bc03sc*i* < pci:v10DEd1B0Asv*sd*bc03sc*i* < pci:v10DEd01C6sv*sd*bc03sc*i* < pci:v10DEd1340sv*sd*bc03sc*i* < pci:v10DEd103Csv*sd*bc03sc*i* < pci:v10DEd2B2Bsv*sd*bc03sc*i* < pci:v10DEd1341sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd3697sv*sd*bc03sc*i* < pci:v10DEd1341sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd3699sv*sd*bc03sc*i* < pci:v10DEd1341sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd369Csv*sd*bc03sc*i* < pci:v10DEd1341sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd36AFsv*sd*bc03sc*i* < pci:v10DEd1346sv*sd*bc03sc*i* < pci:v10DEd17AAsv*sd*bc03sc*i* < pci:v10DEd30BAsv*sd*bc03sc*i* < pci:v10DEd1346sv*sd*bc03sc*i* <
[Kernel-packages] [Bug 1940262] Re: The modalias in 470 is not compatible to 460
** Attachment added: "nvidia-460-modalias" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1940262/+attachment/5518462/+files/nvidia-460-modalias ** Tags added: oem-priority originate-from-1940264 sutton ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1940262 Title: The modalias in 470 is not compatible to 460 Status in OEM Priority Project: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: There are many modalias be removed from 470 those supporting in 460. If 470 is a LTS version and 460 will be transited to 470 then the driver installing will have different behavior between both version. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1940262/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940262] [NEW] The modalias in 470 is not compatible to 460
Public bug reported: There are many modalias be removed from 470 those supporting in 460. If 470 is a LTS version and 460 will be transited to 470 then the driver installing will have different behavior between both version. ** Affects: oem-priority Importance: High Assignee: jeremyszu (os369510) Status: Triaged ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1940264 sutton -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1940262 Title: The modalias in 470 is not compatible to 460 Status in OEM Priority Project: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: There are many modalias be removed from 470 those supporting in 460. If 470 is a LTS version and 460 will be transited to 470 then the driver installing will have different behavior between both version. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1940262/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940261] [NEW] ubuntu_seccomp 11-basic-basic_errors failure on X/oracle
Public bug reported: Xenial/Oracle 4.15.0-1079.87~16.04.1 fails 11-basic-basic_errors test from ubuntu_seccomp on all Oracle cloud instances: batch name: 11-basic-basic_errors test mode: c test type: basic Test 11-basic-basic_errors%%001-1 result: FAILURE 11-basic-basic_errors rc=255 Base kernel bionic/linux-oracle/4.15.0-1079.87 is OK. Previous cycle (xenial/linux-oracle/4.15.0-1077.85~16.04.1) is OK, so this looks like regression. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu Xenial) Importance: Undecided Status: New ** Tags: 4.15 amd64 oracle sru-20210719 ubuntu-seccomp xenial ** Description changed: Xenial/Oracle 4.15.0-1079.87~16.04.1 fails 11-basic-basic_errors test from ubuntu_seccomp on all Oracle cloud instances: - batch name: 11-basic-basic_errors - test mode: c - test type: basic + batch name: 11-basic-basic_errors + test mode: c + test type: basic Test 11-basic-basic_errors%%001-1 result: FAILURE 11-basic-basic_errors rc=255 Base kernel bionic/linux-oracle/4.15.0-1079.87 is OK. + Previous cycle (xenial/linux-oracle/4.15.0-1077.85~16.04.1) is OK, so this looks like regression. ** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: 4.15 oracle xenial ** Tags added: amd64 sru-20210719 ubuntu-seccomp -- 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/1940261 Title: ubuntu_seccomp 11-basic-basic_errors failure on X/oracle Status in ubuntu-kernel-tests: New Status in linux-oracle package in Ubuntu: New Status in linux-oracle source package in Xenial: New Bug description: Xenial/Oracle 4.15.0-1079.87~16.04.1 fails 11-basic-basic_errors test from ubuntu_seccomp on all Oracle cloud instances: batch name: 11-basic-basic_errors test mode: c test type: basic Test 11-basic-basic_errors%%001-1 result: FAILURE 11-basic-basic_errors rc=255 Base kernel bionic/linux-oracle/4.15.0-1079.87 is OK. Previous cycle (xenial/linux-oracle/4.15.0-1077.85~16.04.1) is OK, so this looks like regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1940261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939673] Re: Update the 470 and the 470-server NVIDIA drivers
This bug was fixed in the package nvidia-graphics-drivers-470-server - 470.57.02-0ubuntu0.18.04.3 --- nvidia-graphics-drivers-470-server (470.57.02-0ubuntu0.18.04.3) bionic; urgency=medium * debian/nvidia_supported, debian/rules (LP: #1939673): - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. -- Alberto Milone Thu, 12 Aug 2021 13:38:20 +0200 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1939673 Title: Update the 470 and the 470-server NVIDIA drivers Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Released Bug description: Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic, Focal, Hirsute. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 470.57.02 (470-server) == * debian/nvidia_supported, debian/rules (LP: #1939673): - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. == 470.63.01 (470) == * New upstream release (LP: #1939673): - Added support for the following GPUs: NVIDIA RTX A2000 - Fixed a Vulkan performance regression that affected rFactor2. * debian/nvidia_supported, debian/rules: - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939673/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939673] Re: Update the 470 and the 470-server NVIDIA drivers
This bug was fixed in the package nvidia-graphics-drivers-470-server - 470.57.02-0ubuntu0.20.04.3 --- nvidia-graphics-drivers-470-server (470.57.02-0ubuntu0.20.04.3) focal; urgency=medium * debian/nvidia_supported, debian/rules (LP: #1939673): - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. -- Alberto Milone Thu, 12 Aug 2021 13:37:07 +0200 ** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1939673 Title: Update the 470 and the 470-server NVIDIA drivers Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Released Bug description: Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic, Focal, Hirsute. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 470.57.02 (470-server) == * debian/nvidia_supported, debian/rules (LP: #1939673): - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. == 470.63.01 (470) == * New upstream release (LP: #1939673): - Added support for the following GPUs: NVIDIA RTX A2000 - Fixed a Vulkan performance regression that affected rFactor2. * debian/nvidia_supported, debian/rules: - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939673/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939673] Re: Update the 470 and the 470-server NVIDIA drivers
This bug was fixed in the package nvidia-graphics-drivers-470-server - 470.57.02-0ubuntu0.21.04.3 --- nvidia-graphics-drivers-470-server (470.57.02-0ubuntu0.21.04.3) hirsute; urgency=medium * debian/nvidia_supported, debian/rules (LP: #1939673): - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. -- Alberto Milone Thu, 12 Aug 2021 13:31:15 +0200 ** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1939673 Title: Update the 470 and the 470-server NVIDIA drivers Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Released Bug description: Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic, Focal, Hirsute. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 470.57.02 (470-server) == * debian/nvidia_supported, debian/rules (LP: #1939673): - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. == 470.63.01 (470) == * New upstream release (LP: #1939673): - Added support for the following GPUs: NVIDIA RTX A2000 - Fixed a Vulkan performance regression that affected rFactor2. * debian/nvidia_supported, debian/rules: - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939673/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940085] Re: Sync drivers/gpu/drm from v5.14
** Description changed: [Impact] We need to support new hardware from AMD and Intel, but backporting support to oem-5.13 is very laborous and prone to errors. [Fix] - There only sane way to add a better base for the new hw is by syncing the whole drivers/gpu/drm directory from current 5.14. We also need to update drivers/dma-buf and include a minor abi revert for NVIDIA. + The only sane way to add a better base for the new hw is by syncing the whole drivers/gpu/drm directory from current 5.14. We also need to update drivers/dma-buf and include a minor abi revert for NVIDIA. [Test case] Boot current and new hw from AMD & Intel with the new kernel, and also test that NVIDIA dkms still builds. [Where things could go wrong] - any drm driver could regress, but since v5.14 is already at rc6 this is less likely, and for oem-5.13 we mostly care about drm/amdgpu and drm/i915 anyway. + Any drm driver could regress, but since v5.14 is already at rc6 this is less likely, and for oem-5.13 we mostly care about drm/amdgpu and drm/i915 anyway. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1940085 Title: Sync drivers/gpu/drm from v5.14 Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: New Bug description: [Impact] We need to support new hardware from AMD and Intel, but backporting support to oem-5.13 is very laborous and prone to errors. [Fix] The only sane way to add a better base for the new hw is by syncing the whole drivers/gpu/drm directory from current 5.14. We also need to update drivers/dma-buf and include a minor abi revert for NVIDIA. [Test case] Boot current and new hw from AMD & Intel with the new kernel, and also test that NVIDIA dkms still builds. [Where things could go wrong] Any drm driver could regress, but since v5.14 is already at rc6 this is less likely, and for oem-5.13 we mostly care about drm/amdgpu and drm/i915 anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.13/+bug/1940085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927211] Re: After latest update screen randomly flickers
Possible duplicate of this bug: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1934652 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1927211 Title: After latest update screen randomly flickers Status in linux-signed-hwe-5.8 package in Ubuntu: New Bug description: After the most recent automatic update, my screen will flicker randomly. This is not screen tearing but a random, arbitrary flicker/tearing that gets worse when i use calculator, terminal and firefox. It is particularly bad when using firefox. It's reasonably stable when using google chrome. Description: Ubuntu 20.04.2 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-50-generic 5.8.0-50.56~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 5 12:05:06 2021 InstallationDate: Installed on 2020-05-09 (360 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1927211/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940225] [NEW] invalid opcode: 0000 [#1] SMP NOPTI
Public bug reported: Here is a kernel bug. I attached the error log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 17 10:02:28 2021 SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "error.txt" https://bugs.launchpad.net/bugs/1940225/+attachment/5518376/+files/error.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1940225 Title: invalid opcode: [#1] SMP NOPTI Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: Here is a kernel bug. I attached the error log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 17 10:02:28 2021 SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1940225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940225] Re: invalid opcode: 0000 [#1] SMP NOPTI
** Attachment added: "error1.txt" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1940225/+attachment/5518381/+files/error1.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1940225 Title: invalid opcode: [#1] SMP NOPTI Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: Here is a kernel bug. I attached the error log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 17 10:02:28 2021 SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1940225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936452] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1936452 Title: [SRU][F/H/I] Add MT7921 wifi fw Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Status in linux-firmware source package in Impish: Fix Released Bug description: SRU justification: [Impact] No support for MT7921 wifi card. [Fix] MT7921 needs both driver and firmware, driver is almost ready, add firmware first, then get driver bug fixed later. [Test] Verified on hardware, cold boot system wifi works fine. Reboot make it fail, but I will fix it in SRU of kernel patch. After that, it works fine. [Where problems could occur] The MT7921 wifi may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938149] Re: To support AMD W6600 and W6700
This bug was fixed in the package linux-firmware - 1.187.16 --- linux-firmware (1.187.16) focal; urgency=medium * Intel Killer(R) Wi-Fi 6 AX1650i [8086:a0f0] Subsystem [1a56:1651]: iwlwifi firmware crash under iperf stress tests: Microcode SW error detected. Restarting 0x0 (LP: #1934217) - iwlwifi: update and add new FWs from core56-54 release * [SRU] Update amdgpu/renoir firmware (LP: #1934014) - amdgpu: update renoir firmware from 21.20 * To support AMD W6600 and W6700 (LP: #1938149) - amdgpu: add sienna cichlid firmware for 20.45 - amdgpu: update sienna cichlid firmware for 20.50 - amdgpu: update sienna cichlid firmware from 21.10 - amdgpu: update sienna cichlid firmware from 21.20 - amdgpu: add initial dimgrey cavefish firmware from 21.20 * [SRU][F/H/I] Add MT7921 wifi fw (LP: #1936452) - linux-firmware: add firmware for MT7921 - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for MT7921 WiFi device to 20210612122753 - linux-firmware: add frimware for mediatek bluetooth chip (MT7921) - linux-firmware: update frimware for mediatek bluetooth chip (MT7921) * Intel AX210 iwlwifi firmware crash under stress tests: Microcode SW error detected. Restarting 0x0. (LP: #1933415) - iwlwifi: add new FWs from core60-51 release -- Timo Aaltonen Mon, 02 Aug 2021 18:41:24 +0300 ** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: linux-firmware (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1938149 Title: To support AMD W6600 and W6700 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Bug description: [Impact] To support AMD Radeon Pro W6600/W6700 graphic card, we need some new firmware. [Fix] AMD suggests us to include below 2 commits, and to avoid conflicts I cherry pick sienna cichlid firmware from the beginning when it's been added. Impish already have both commits. amdgpu: add initial dimgrey cavefish firmware from 21.20 https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=87619e4114cc631efcb6868dca54d481dc467034 amdgpu: update sienna cichlid firmware from 21.20 https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=4043da4f77f84b75a0f818ab7e83ead187ebf441 [Test] Verified on AMD Radeon Pro W6600 graphic card. [Where problems could occur] This series of patches introduce dimgrey cavefish and sienna cichlid firmware. The 2 GPUs are still new and have little chance to affect old platforms, should be safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1938149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934014] Re: [SRU] Update amdgpu/renoir firmware
This bug was fixed in the package linux-firmware - 1.187.16 --- linux-firmware (1.187.16) focal; urgency=medium * Intel Killer(R) Wi-Fi 6 AX1650i [8086:a0f0] Subsystem [1a56:1651]: iwlwifi firmware crash under iperf stress tests: Microcode SW error detected. Restarting 0x0 (LP: #1934217) - iwlwifi: update and add new FWs from core56-54 release * [SRU] Update amdgpu/renoir firmware (LP: #1934014) - amdgpu: update renoir firmware from 21.20 * To support AMD W6600 and W6700 (LP: #1938149) - amdgpu: add sienna cichlid firmware for 20.45 - amdgpu: update sienna cichlid firmware for 20.50 - amdgpu: update sienna cichlid firmware from 21.10 - amdgpu: update sienna cichlid firmware from 21.20 - amdgpu: add initial dimgrey cavefish firmware from 21.20 * [SRU][F/H/I] Add MT7921 wifi fw (LP: #1936452) - linux-firmware: add firmware for MT7921 - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for MT7921 WiFi device to 20210612122753 - linux-firmware: add frimware for mediatek bluetooth chip (MT7921) - linux-firmware: update frimware for mediatek bluetooth chip (MT7921) * Intel AX210 iwlwifi firmware crash under stress tests: Microcode SW error detected. Restarting 0x0. (LP: #1933415) - iwlwifi: add new FWs from core60-51 release -- Timo Aaltonen Mon, 02 Aug 2021 18:41:24 +0300 ** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1934014 Title: [SRU] Update amdgpu/renoir firmware Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Bug description: [Impact] Renoir based systems can't resume from s2idle. [Fix] Update firmware for renoir into 21.10 or 21.20 release in linux-firmware.git Accompanying kernel driver updates are distributed with linux-oem-5.10. [Test] Verify s2idle on OEM system. [Where problems could occur] The firmware update is specific to Renoir systems, which are relative new so the impact is limited. We also have direct involvement with AMD, in case any regression happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1934014/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934217] Re: Intel Killer(R) Wi-Fi 6 AX1650i [8086:a0f0] Subsystem [1a56:1651]: iwlwifi firmware crash under iperf stress tests: Microcode SW error detected. Restarting 0x0
This bug was fixed in the package linux-firmware - 1.187.16 --- linux-firmware (1.187.16) focal; urgency=medium * Intel Killer(R) Wi-Fi 6 AX1650i [8086:a0f0] Subsystem [1a56:1651]: iwlwifi firmware crash under iperf stress tests: Microcode SW error detected. Restarting 0x0 (LP: #1934217) - iwlwifi: update and add new FWs from core56-54 release * [SRU] Update amdgpu/renoir firmware (LP: #1934014) - amdgpu: update renoir firmware from 21.20 * To support AMD W6600 and W6700 (LP: #1938149) - amdgpu: add sienna cichlid firmware for 20.45 - amdgpu: update sienna cichlid firmware for 20.50 - amdgpu: update sienna cichlid firmware from 21.10 - amdgpu: update sienna cichlid firmware from 21.20 - amdgpu: add initial dimgrey cavefish firmware from 21.20 * [SRU][F/H/I] Add MT7921 wifi fw (LP: #1936452) - linux-firmware: add firmware for MT7921 - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for MT7921 WiFi device to 20210612122753 - linux-firmware: add frimware for mediatek bluetooth chip (MT7921) - linux-firmware: update frimware for mediatek bluetooth chip (MT7921) * Intel AX210 iwlwifi firmware crash under stress tests: Microcode SW error detected. Restarting 0x0. (LP: #1933415) - iwlwifi: add new FWs from core60-51 release -- Timo Aaltonen Mon, 02 Aug 2021 18:41:24 +0300 ** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1934217 Title: Intel Killer(R) Wi-Fi 6 AX1650i [8086:a0f0] Subsystem [1a56:1651]: iwlwifi firmware crash under iperf stress tests: Microcode SW error detected. Restarting 0x0 Status in HWE Next: New Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/1934217 [Impact] iwlwifi firmware crash under iperf stress tests: "Microcode SW error detected. Restarting 0x0." [Fix] iwlwifi FWs from core56-54 release may fix this issue. [Test Case] This affects plenty of models: * iwlwifi-9000-pu-b0-jf-b0-*: - killer 1550* - 9461/9462/9560 * iwlwifi-9260-th-b0-jf-b0-*: - 9260 * iwlwifi-Q*-hr-b0-*: - AX201 - AX1650* * iwlwifi-Q*-jf-b0-*: - 9560 * iwlwifi-cc-a0-*: - AX200 While -59 fw is only used by 5.11-hwe kernel in Focal, they are tested only against hwe-5.11. For iwlwifi-9* fw, they are used by kernel since 5.1, they're tested against 5.4/5.6/5.8 and 5.11 kernels. Test steps: - Connect both DUTs to the 5G wifi AP - on DUT 1 - $ iperf3 -s -B 192.168.50.188 - on DUT 2 - $ iperf3 -c 192.168.50.188 -B 192.168.50.91 -t 6000 - After about 30 mins the wifi crashed with firmware related error [Where problems could occur] We have little info about each update of firmware blobs. So far we only know that their revisions match those claimed by kernel driver and we did not find other issues under the tests. [Other Info] Groovy 5.8 kernel supports -58 at max, and Hirsute has this already. So only Focal is nominated for hwe-5.11 kernel support. For 5.13-oem, -63 fw is being SRU-ed in bug 1933415. == original bug description == - Connect both DUTs to the 5G wifi AP - on DUT 1 - $ iperf3 -s -B 192.168.50.188 - on DUT 2 - $ iperf3 -c 192.168.50.188 -B 192.168.50.91 -t 6000 - After about 30 mins the wifi crashed with firmware related error [105396.990450] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [105396.990539] iwlwifi :00:14.3: Start IWL Error Log Dump: [105396.990541] iwlwifi :00:14.3: Status: 0x0040, count: 6 [105396.990543] iwlwifi :00:14.3: Loaded firmware version: 55.d9698065.0 QuZ-a0-hr-b0-55.ucode [105396.990545] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [105396.990547] iwlwifi :00:14.3: 0x22F0 | trm_hw_status0 [105396.990548] iwlwifi :00:14.3: 0x | trm_hw_status1 [105396.990549] iwlwifi :00:14.3: 0x004CA3DE | branchlink2 [105396.990551] iwlwifi :00:14.3: 0x07F6 | interruptlink1 [105396.990552] iwlwifi :00:14.3: 0x07F6 | interruptlink2 [105396.990553] iwlwifi :00:14.3: 0x00016504 | data1 [105396.990554] iwlwifi :00:14.3: 0x1000 | data2 [105396.990555] iwlwifi :00:14.3: 0x | data3 [105396.990557] iwlwifi :00:14.3: 0x900148E4 | beacon time [105396.990558] iwlwifi :00:14.3: 0x0C6FF71A | tsf low [105396.990559] iwlwifi :00:14.3: 0x01B4 | tsf hi [105396.990560] iwlwifi :00:14.3: 0x | time gp1
[Kernel-packages] [Bug 1934217] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1934217 Title: Intel Killer(R) Wi-Fi 6 AX1650i [8086:a0f0] Subsystem [1a56:1651]: iwlwifi firmware crash under iperf stress tests: Microcode SW error detected. Restarting 0x0 Status in HWE Next: New Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/1934217 [Impact] iwlwifi firmware crash under iperf stress tests: "Microcode SW error detected. Restarting 0x0." [Fix] iwlwifi FWs from core56-54 release may fix this issue. [Test Case] This affects plenty of models: * iwlwifi-9000-pu-b0-jf-b0-*: - killer 1550* - 9461/9462/9560 * iwlwifi-9260-th-b0-jf-b0-*: - 9260 * iwlwifi-Q*-hr-b0-*: - AX201 - AX1650* * iwlwifi-Q*-jf-b0-*: - 9560 * iwlwifi-cc-a0-*: - AX200 While -59 fw is only used by 5.11-hwe kernel in Focal, they are tested only against hwe-5.11. For iwlwifi-9* fw, they are used by kernel since 5.1, they're tested against 5.4/5.6/5.8 and 5.11 kernels. Test steps: - Connect both DUTs to the 5G wifi AP - on DUT 1 - $ iperf3 -s -B 192.168.50.188 - on DUT 2 - $ iperf3 -c 192.168.50.188 -B 192.168.50.91 -t 6000 - After about 30 mins the wifi crashed with firmware related error [Where problems could occur] We have little info about each update of firmware blobs. So far we only know that their revisions match those claimed by kernel driver and we did not find other issues under the tests. [Other Info] Groovy 5.8 kernel supports -58 at max, and Hirsute has this already. So only Focal is nominated for hwe-5.11 kernel support. For 5.13-oem, -63 fw is being SRU-ed in bug 1933415. == original bug description == - Connect both DUTs to the 5G wifi AP - on DUT 1 - $ iperf3 -s -B 192.168.50.188 - on DUT 2 - $ iperf3 -c 192.168.50.188 -B 192.168.50.91 -t 6000 - After about 30 mins the wifi crashed with firmware related error [105396.990450] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [105396.990539] iwlwifi :00:14.3: Start IWL Error Log Dump: [105396.990541] iwlwifi :00:14.3: Status: 0x0040, count: 6 [105396.990543] iwlwifi :00:14.3: Loaded firmware version: 55.d9698065.0 QuZ-a0-hr-b0-55.ucode [105396.990545] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [105396.990547] iwlwifi :00:14.3: 0x22F0 | trm_hw_status0 [105396.990548] iwlwifi :00:14.3: 0x | trm_hw_status1 [105396.990549] iwlwifi :00:14.3: 0x004CA3DE | branchlink2 [105396.990551] iwlwifi :00:14.3: 0x07F6 | interruptlink1 [105396.990552] iwlwifi :00:14.3: 0x07F6 | interruptlink2 [105396.990553] iwlwifi :00:14.3: 0x00016504 | data1 [105396.990554] iwlwifi :00:14.3: 0x1000 | data2 [105396.990555] iwlwifi :00:14.3: 0x | data3 [105396.990557] iwlwifi :00:14.3: 0x900148E4 | beacon time [105396.990558] iwlwifi :00:14.3: 0x0C6FF71A | tsf low [105396.990559] iwlwifi :00:14.3: 0x01B4 | tsf hi [105396.990560] iwlwifi :00:14.3: 0x | time gp1 [105396.990562] iwlwifi :00:14.3: 0x58CF3E54 | time gp2 [105396.990563] iwlwifi :00:14.3: 0x0001 | uCode revision type [105396.990564] iwlwifi :00:14.3: 0x0037 | uCode version major [105396.990565] iwlwifi :00:14.3: 0xD9698065 | uCode version minor [105396.990567] iwlwifi :00:14.3: 0x0351 | hw version [105396.990568] iwlwifi :00:14.3: 0x00C89004 | board version [105396.990569] iwlwifi :00:14.3: 0x800FFC03 | hcmd [105396.990570] iwlwifi :00:14.3: 0x0002 | isr0 [105396.990572] iwlwifi :00:14.3: 0x0040 | isr1 [105396.990573] iwlwifi :00:14.3: 0x08F2 | isr2 [105396.990574] iwlwifi :00:14.3: 0x04C338C8 | isr3 [105396.990575] iwlwifi :00:14.3: 0x | isr4 [105396.990577] iwlwifi :00:14.3: 0x05D6001C | last cmd Id [105396.990578] iwlwifi :00:14.3: 0x00016504 | wait_event [105396.990579] iwlwifi :00:14.3: 0x00C4 | l2p_control [105396.990580] iwlwifi :00:14.3: 0x | l2p_duration [105396.990582] iwlwifi
[Kernel-packages] [Bug 1936452] Re: [SRU][F/H/I] Add MT7921 wifi fw
This bug was fixed in the package linux-firmware - 1.187.16 --- linux-firmware (1.187.16) focal; urgency=medium * Intel Killer(R) Wi-Fi 6 AX1650i [8086:a0f0] Subsystem [1a56:1651]: iwlwifi firmware crash under iperf stress tests: Microcode SW error detected. Restarting 0x0 (LP: #1934217) - iwlwifi: update and add new FWs from core56-54 release * [SRU] Update amdgpu/renoir firmware (LP: #1934014) - amdgpu: update renoir firmware from 21.20 * To support AMD W6600 and W6700 (LP: #1938149) - amdgpu: add sienna cichlid firmware for 20.45 - amdgpu: update sienna cichlid firmware for 20.50 - amdgpu: update sienna cichlid firmware from 21.10 - amdgpu: update sienna cichlid firmware from 21.20 - amdgpu: add initial dimgrey cavefish firmware from 21.20 * [SRU][F/H/I] Add MT7921 wifi fw (LP: #1936452) - linux-firmware: add firmware for MT7921 - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for MT7921 WiFi device to 20210612122753 - linux-firmware: add frimware for mediatek bluetooth chip (MT7921) - linux-firmware: update frimware for mediatek bluetooth chip (MT7921) * Intel AX210 iwlwifi firmware crash under stress tests: Microcode SW error detected. Restarting 0x0. (LP: #1933415) - iwlwifi: add new FWs from core60-51 release -- Timo Aaltonen Mon, 02 Aug 2021 18:41:24 +0300 ** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: linux-firmware (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1936452 Title: [SRU][F/H/I] Add MT7921 wifi fw Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Status in linux-firmware source package in Impish: Fix Released Bug description: SRU justification: [Impact] No support for MT7921 wifi card. [Fix] MT7921 needs both driver and firmware, driver is almost ready, add firmware first, then get driver bug fixed later. [Test] Verified on hardware, cold boot system wifi works fine. Reboot make it fail, but I will fix it in SRU of kernel patch. After that, it works fine. [Where problems could occur] The MT7921 wifi may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp