[Kernel-packages] [Bug 2008085] Re: net:veth.sh in ubuntu_kernel_selftests hang with J-intel-iotg (BUG: unable to handle page fault)
Issue still visible in this cycle, confirmed with Jian Hui that this is expected. ** Tags added: sru-20230227 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2008085 Title: net:veth.sh in ubuntu_kernel_selftests hang with J-intel-iotg (BUG: unable to handle page fault) Status in HWE Next: Invalid Status in ubuntu-kernel-tests: New Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: In Progress Bug description: Issue found on node "onibi" with J-intel-iotg 5.15.0-1026.31 this cycle. The veth.sh test in net category will hang and timeout, causing test report incomplete. I can see some traces in dmesg with manual test. ubuntu@onibi:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./veth.sh default - gro flag ok - peer gro flag ok - tso flag ok - peer tso flag ok - aggregationok - aggregation with TSO off ok with gro on - gro flag ok - peer gro flag ok - tso flag ok - peer tso flag ok - aggregation with TSO off ok default channels ok with gro enabled on link down - gro flag ok - peer gro flag ok - tso flag ok - peer tso flag ok - aggregation with TSO off ok setting tx channels ok setting both rx and tx channels ok bad setting: combined channels ok setting invalid channels nr fail rx:3:3 tx:3:5 combined:n/a:n/a bad setting: XDP with RX nr less than TX ok (hangs here) dmesg output: [ 547.520923] BUG: unable to handle page fault for address: b7380001 [ 547.520999] #PF: supervisor write access in kernel mode [ 547.521045] #PF: error_code(0x0002) - not-present page [ 547.521089] PGD 10067 P4D 10067 PUD 0 [ 547.521133] Oops: 0002 [#1] SMP PTI [ 547.521168] CPU: 1 PID: 1559 Comm: ip Not tainted 5.15.0-1026-intel-iotg #31-Ubuntu [ 547.521233] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.8.2 08/17/2011 [ 547.521293] RIP: 0010:veth_xdp+0x18f/0x1e0 [veth] [ 547.521342] Code: ff 41 89 9d 1c 01 00 00 49 21 85 e8 00 00 00 e9 74 ff ff ff 48 c7 c7 80 e3 b0 c0 e8 2b 3b 06 c1 b8 e4 ff ff ff 4d 85 ff 74 85 <49> c7 07 80 e3 b0 c0 e9 79 ff ff ff 48 c7 c7 20 e4 b0 c0 e8 09 3b [ 547.521488] RSP: 0018:b738c254f420 EFLAGS: 00010282 [ 547.521535] RAX: ffe4 RBX: 0db2 RCX: b738c254fb20 [ 547.521594] RDX: c0b0bf90 RSI: b738c254f468 RDI: c0b0e380 [ 547.521653] RBP: b738c254f450 R08: 0001 R09: b738c0081000 [ 547.521711] R10: R11: R12: 8c65ced9 [ 547.521769] R13: 8c65c12f6000 R14: R15: b7380001 [ 547.521828] FS: 7faa028b3b80() GS:8c66f764() knlGS: [ 547.521895] CS: 0010 DS: ES: CR0: 80050033 [ 547.521943] CR2: b7380001 CR3: 00010f068000 CR4: 06e0 [ 547.522004] Call Trace: [ 547.522029] [ 547.522052] ? veth_open+0x90/0x90 [veth] [ 547.522094] dev_xdp_install+0x66/0xf0 [ 547.522135] dev_xdp_attach+0x1fc/0x590 [ 547.522171] ? __bpf_prog_get+0x1f/0xe0 [ 547.522212] dev_change_xdp_fd+0x200/0x240 [ 547.522252] do_setlink+0xba2/0xc70 [ 547.522288] ? dev_get_alias+0x35/0x50 [ 547.522326] __rtnl_newlink+0x61e/0xa20 [ 547.522363] ? security_sock_rcv_skb+0x2f/0x50 [ 547.522406] ? skb_queue_tail+0x48/0x60 [ 547.522444] ? sock_def_readable+0x4b/0x80 [ 547.522485] ? __netlink_sendskb+0x62/0x80 [ 547.522528] ? netlink_unicast+0x2fb/0x340 [ 547.522566] ? rtnl_getlink+0x398/0x420 [ 547.522611] ? kmem_cache_alloc_trace+0x17e/0x2a0 [ 547.522657] rtnl_newlink+0x49/0x70 [ 547.522692] rtnetlink_rcv_msg+0x15d/0x400 [ 547.522731] ? rtnl_calcit.isra.0+0x130/0x130 [ 547.524524] netlink_rcv_skb+0x56/0x100 [ 547.526314] rtnetlink_rcv+0x15/0x20 [ 547.528102] netlink_unicast+0x223/0x340 [ 547.529837]
[Kernel-packages] [Bug 2009767] Re: External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system
This might become a "Won't fix" for 525 but let's track it more accurately there for the time being. ** Summary changed: - external HDMI monitor is laggy on NV reverse PRIME system + External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system ** Also affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-525 (Ubuntu) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Kinetic) Status: New => Confirmed ** No longer affects: nvidia-graphics-drivers (Ubuntu Kinetic) ** No longer affects: nvidia-graphics-drivers (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2009767 Title: External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system Status in OEM Priority Project: New Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Confirmed Status in nvidia-graphics-drivers-525 source package in Kinetic: Confirmed Status in xorg-server source package in Kinetic: Fix Released Bug description: [Summary] When the graphic mode is on-demand mode and plug in the monitor to HDMI port, there are two issue occures: 1. External monitor's screen is very laggy in external monitor mode only. 2. External monitor's screen sometimes (~50%) will be blak in join display mode. [Steps to reproduce] 1. Boot in OS 2. Plug in the external monitor in HDMI port 3. Find the cursor moving in external monitor is laggy [Workaround] Downgrade to NVIDIA driver 515. [Additional information] Feedback from NV: An NVIDIA driver built with the features needed to get rid of the laggy monitor problem causes Xorg 1.21.1.3 to crash. There's a patch for Xorg to fix the crash (https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275) and it was first included in the 1.21.1.4 release. Since the older X servers crash, NVIDIA deliberately does a version check in the driver and enables these features for Xorg servers that are known to work, i.e. 1.21.1.4 or higher. This unfortunately prevents backporting the fix to 1.21.1.3. Engineering has chosen this approach since a crash is worse than the low FPS lag and the user might lose work merely by plugging/unplugging displays. If it was about a performance degradation, slight corruption, or something non-fatal, we wouldn't need to check Xorg version To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011768] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2011768 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Jammy) 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/2011768 Title: Fix NVME storage with RAID ON disappeared under Dell factory WINPE environment Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: Incomplete Status in linux-oem-6.1 source package in Jammy: New Status in linux source package in Lunar: Incomplete Status in linux-oem-6.1 source package in Lunar: New Bug description: [Impact] NVME storage disappeared under Dell factory WINPE environment with RAID ON mode when this WINPE boot entry touched by efibootmgr [Fix] Reset the VMD msi remapping during shutdown. [Test Case] 1. Install Ubuntu 2. Then, system will reboot to WINPE to do some cleanup work. 3. in WINPE, the NVME storage could be listed. [Where problems could occur] Low, the issue may be observed on VMD MSI remapping. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011768] [NEW] Fix NVME storage with RAID ON disappeared under Dell factory WINPE environment
Public bug reported: [Impact] NVME storage disappeared under Dell factory WINPE environment with RAID ON mode when this WINPE boot entry touched by efibootmgr [Fix] Reset the VMD msi remapping during shutdown. [Test Case] 1. Install Ubuntu 2. Then, system will reboot to WINPE to do some cleanup work. 3. in WINPE, the NVME storage could be listed. [Where problems could occur] Low, the issue may be observed on VMD MSI remapping. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2011768 Title: Fix NVME storage with RAID ON disappeared under Dell factory WINPE environment Status in linux package in Ubuntu: New Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.1 source package in Jammy: New Status in linux source package in Lunar: New Status in linux-oem-6.1 source package in Lunar: New Bug description: [Impact] NVME storage disappeared under Dell factory WINPE environment with RAID ON mode when this WINPE boot entry touched by efibootmgr [Fix] Reset the VMD msi remapping during shutdown. [Test Case] 1. Install Ubuntu 2. Then, system will reboot to WINPE to do some cleanup work. 3. in WINPE, the NVME storage could be listed. [Where problems could occur] Low, the issue may be observed on VMD MSI remapping. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999836] Re: Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500]
** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1999836 Title: Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500] Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] SUT can't displayed after resume from WB/CB with dGFX installed. Recovery: SUT can display when the DP cable unplug and plug . [Fix] Use quirk to block the affected SKUes. [Test Case] 1.Install Ubuntu 22.04 on SUT with dGFX card. 2.Connect the DP cable to the dGFX port. 3.SUT do power off/restart. 4.SUT can display. [Where problems could occur] Add SKU's id to a quirk table, the impact would be small. [Other Info] * For the pure Jammy, Confronted the error of compilation. 1. Need 8e794421bc98) drm/amd/display: Fork thread to offload work ~~~ drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1449:38: error: implicit declaration of function 'hpd_rx_irq_create_ workqueue'; did you mean 'hdcp_create_workqueue'? [-Werror=implicit-function-declaration] 18848 1449 | adev->dm.hpd_rx_offload_wq = hpd_rx_irq_create_workqueue(adev->dm.dc); 18849 | ^~~ 18850 | hdcp_create_workqueue ~~~ 2. Need 3ce51649cdf2) drm/amdgpu/display: add quirk handling for stutter ~~~ drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1505:13: error: implicit declaration of function 'dm_should_disable_ stutter' [-Werror=implicit-function-declaration] 18838 1505 | if (dm_should_disable_stutter(adev->pdev)) ~~~ * hpd_disconnect_quirk_table is placed to the different location on J/OEM-5.17 and on K/OEM-6.0, so can't use a single patch for all. * Result from CBD ~~~ Jammy, remote: *** kernel-cbd * remote: * Queueing builds (your 'j_gen_nxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-820f542767e6-ESq2 remote: * 192/672 cores busy (2/7 hosts), 0 builds queued remote: 2022-12-15 17:09:15 kobako-jammy-820f542767e6-ESq2/amd64/BUILD-OK remote: 2022-12-15 17:11:13 kobako-jammy-820f542767e6-ESq2/arm64/BUILD-OK remote: 2022-12-15 17:07:30 kobako-jammy-820f542767e6-ESq2/armhf/BUILD-OK remote: 2022-12-15 17:10:17 kobako-jammy-820f542767e6-ESq2/ppc64el/BUILD-OK remote: 2022-12-15 17:04:55 kobako-jammy-820f542767e6-ESq2/s390x/BUILD-OK remote: To 54.69.112.110:jammy.git ~~~ Kinetic remote: *** kernel-cbd * remote: * Queueing builds (your 'k_gen_nxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-kinetic-857358673609-X4Nz remote: * 0/672 cores busy (0/7 hosts), 0 builds queued remote: 2022-12-15 17:41:37 kobako-kinetic-857358673609-X4Nz/amd64/BUILD-OK remote: 2022-12-15 17:42:13 kobako-kinetic-857358673609-X4Nz/arm64/BUILD-OK remote: 2022-12-15 17:35:54 kobako-kinetic-857358673609-X4Nz/armhf/BUILD-OK remote: 2022-12-15 17:40:54 kobako-kinetic-857358673609-X4Nz/ppc64el/BUILD-OK remote: 2022-12-15 17:34:47 kobako-kinetic-857358673609-X4Nz/s390x/BUILD-OK remote: To 54.69.112.110:kinetic.git ~~~ To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1999836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998115] Re: Fix iosm: WWAN cannot build the connection (DW5823e)
** Tags removed: verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998115 Title: Fix iosm: WWAN cannot build the connection (DW5823e) Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] WWAN(DW5823e) can't build the connection successfully. [Fix] With INTEL_IOMMU disable config or by forcing intel_iommu=off from grub some of the features of IOSM driver like browsing, flashing & coredump collection is not working. When driver calls DMA API - dma_map_single() for tx transfers. It is resulting in dma mapping error. Set the device DMA addressing capabilities using dma_set_mask() and remove the INTEL_IOMMU dependency in kconfig so that driver follows the platform config either INTEL_IOMMU enable or disable. Because the generic jammy(5.15) doesn't contain NET_DEVLINK and RELAY CONFIGs yet on iosm module, the single patch is necessary for Jammy. [Test Case] 1. boot up with kernel applied the FIX. 2. check the status of wwan by "mmcli -m 0" Status| unlock retries: sim-pin (3) | state: ^[32mconnected^[0m |power state: on |access tech: lte | signal quality: 45% (recent) -- 3GPP | imei: ## | enabled locks: sim, fixed-dialing |operator id: 46692 | operator name: Chunghwa Telecom | registration: home | packet service state: attached |pco: | 0: (complete) [Where problems could occur] remove the dependency for intel_iommu, iosm would fit better on other platforms not only Intel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998115/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990161] Re: Fix RPL-S support on powercap/intel_rapl
** Tags removed: verification-needed-focal verification-needed-kinetic ** Tags added: verification-done-focal verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1990161 Title: Fix RPL-S support on powercap/intel_rapl Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] proc_thermal driver is not loaded [Fix] Add RPL-S id on device id table of powercap/intel_rapl. [Test Case] 1. sudo checkbox-cli run com.canonical.certification::miscellanea/proc_thermal [Where problems could occur] Low, only add RPL-S id on powercap/intel_rap but may lack of RPL-S features. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1990161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003161] Re: Fix speaker mute hotkey doesn't work on Dell G16 series
** Tags removed: verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2003161 Title: Fix speaker mute hotkey doesn't work on Dell G16 series Status in HWE Next: New Status in HWE Next lunar series: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Kinetic: New Status in linux-oem-6.1 source package in Kinetic: New Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Speaker mute and Mic mute hotkey no function on the G16. [Fix] speaker mute event is sent by EC then dell-wmi can't recognize it. Add a new keymap for KEY_MUTE. Send for OEM kernels first then will SRU for generic kernel once the patch is merged. [Test Case] 1. boot-up with the kernel applied the fix. 2. Play video/audio. 3. Press the speak-mute hotkey 4. can't hear any sounds. [Where problems could occur] Low, only add a keymap the affect would be very limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2003161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008085] Re: net:veth.sh in ubuntu_kernel_selftests hang with J-intel-iotg (BUG: unable to handle page fault)
** Tags added: lookout-canyon oem-priority originate-from-2011522 ** Changed in: hwe-next Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2008085 Title: net:veth.sh in ubuntu_kernel_selftests hang with J-intel-iotg (BUG: unable to handle page fault) Status in HWE Next: Invalid Status in ubuntu-kernel-tests: New Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: In Progress Bug description: Issue found on node "onibi" with J-intel-iotg 5.15.0-1026.31 this cycle. The veth.sh test in net category will hang and timeout, causing test report incomplete. I can see some traces in dmesg with manual test. ubuntu@onibi:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./veth.sh default - gro flag ok - peer gro flag ok - tso flag ok - peer tso flag ok - aggregationok - aggregation with TSO off ok with gro on - gro flag ok - peer gro flag ok - tso flag ok - peer tso flag ok - aggregation with TSO off ok default channels ok with gro enabled on link down - gro flag ok - peer gro flag ok - tso flag ok - peer tso flag ok - aggregation with TSO off ok setting tx channels ok setting both rx and tx channels ok bad setting: combined channels ok setting invalid channels nr fail rx:3:3 tx:3:5 combined:n/a:n/a bad setting: XDP with RX nr less than TX ok (hangs here) dmesg output: [ 547.520923] BUG: unable to handle page fault for address: b7380001 [ 547.520999] #PF: supervisor write access in kernel mode [ 547.521045] #PF: error_code(0x0002) - not-present page [ 547.521089] PGD 10067 P4D 10067 PUD 0 [ 547.521133] Oops: 0002 [#1] SMP PTI [ 547.521168] CPU: 1 PID: 1559 Comm: ip Not tainted 5.15.0-1026-intel-iotg #31-Ubuntu [ 547.521233] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.8.2 08/17/2011 [ 547.521293] RIP: 0010:veth_xdp+0x18f/0x1e0 [veth] [ 547.521342] Code: ff 41 89 9d 1c 01 00 00 49 21 85 e8 00 00 00 e9 74 ff ff ff 48 c7 c7 80 e3 b0 c0 e8 2b 3b 06 c1 b8 e4 ff ff ff 4d 85 ff 74 85 <49> c7 07 80 e3 b0 c0 e9 79 ff ff ff 48 c7 c7 20 e4 b0 c0 e8 09 3b [ 547.521488] RSP: 0018:b738c254f420 EFLAGS: 00010282 [ 547.521535] RAX: ffe4 RBX: 0db2 RCX: b738c254fb20 [ 547.521594] RDX: c0b0bf90 RSI: b738c254f468 RDI: c0b0e380 [ 547.521653] RBP: b738c254f450 R08: 0001 R09: b738c0081000 [ 547.521711] R10: R11: R12: 8c65ced9 [ 547.521769] R13: 8c65c12f6000 R14: R15: b7380001 [ 547.521828] FS: 7faa028b3b80() GS:8c66f764() knlGS: [ 547.521895] CS: 0010 DS: ES: CR0: 80050033 [ 547.521943] CR2: b7380001 CR3: 00010f068000 CR4: 06e0 [ 547.522004] Call Trace: [ 547.522029] [ 547.522052] ? veth_open+0x90/0x90 [veth] [ 547.522094] dev_xdp_install+0x66/0xf0 [ 547.522135] dev_xdp_attach+0x1fc/0x590 [ 547.522171] ? __bpf_prog_get+0x1f/0xe0 [ 547.522212] dev_change_xdp_fd+0x200/0x240 [ 547.522252] do_setlink+0xba2/0xc70 [ 547.522288] ? dev_get_alias+0x35/0x50 [ 547.522326] __rtnl_newlink+0x61e/0xa20 [ 547.522363] ? security_sock_rcv_skb+0x2f/0x50 [ 547.522406] ? skb_queue_tail+0x48/0x60 [ 547.522444] ? sock_def_readable+0x4b/0x80 [ 547.522485] ? __netlink_sendskb+0x62/0x80 [ 547.522528] ? netlink_unicast+0x2fb/0x340 [ 547.522566] ? rtnl_getlink+0x398/0x420 [ 547.522611] ? kmem_cache_alloc_trace+0x17e/0x2a0 [ 547.522657] rtnl_newlink+0x49/0x70 [ 547.522692] rtnetlink_rcv_msg+0x15d/0x400 [ 547.522731] ? rtnl_calcit.isra.0+0x130/0x130 [ 547.524524] netlink_rcv_skb+0x56/0x100 [ 547.526314] rtnetlink_rcv+0x15/0x20 [ 547.528102] netlink_unicast+0x223/0x340 [ 547.529837]
[Kernel-packages] [Bug 2011520] Re: Bluetooth: btusb: Add module firmware information for MT7622 and MT7961
** Changed in: hwe-next Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2011520 Title: Bluetooth: btusb: Add module firmware information for MT7622 and MT7961 Status in HWE Next: Invalid Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: In Progress Bug description: [ Impact ] * Export the required module firmware information of MT7622 and M7961 used by modinfo. [ Test Plan ] * execute the following command, you should be able to see the firmware information $ modinfo btusb.ko ... firmware: mediatek/mt7668pr2h.bin firmware: mediatek/mt7663pr2h.bin srcversion: 93D172DBD10743ABF2E68FD ... mediatek/mt7622pr2h.bin and mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin are missing [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2011520/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011521] Re: USB: serial: option: add Quectel EM05CN modem
** Changed in: hwe-next Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2011521 Title: USB: serial: option: add Quectel EM05CN modem Status in HWE Next: Invalid Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: In Progress Bug description: [ Impact ] * add Quectel EM05CN modem id [ Test Plan ] * testing on the system with this modem [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2011521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-oracle-5.15/5.15.0-1031.37~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-oracle-5.15 (5.15.0-1031.37~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-oracle-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011520] Re: Bluetooth: btusb: Add module firmware information for MT7622 and MT7961
** Tags added: austin-charlotte oem-priority originate-from-2007252 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2011520 Title: Bluetooth: btusb: Add module firmware information for MT7622 and MT7961 Status in HWE Next: New Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: In Progress Bug description: [ Impact ] * Export the required module firmware information of MT7622 and M7961 used by modinfo. [ Test Plan ] * execute the following command, you should be able to see the firmware information $ modinfo btusb.ko ... firmware: mediatek/mt7668pr2h.bin firmware: mediatek/mt7663pr2h.bin srcversion: 93D172DBD10743ABF2E68FD ... mediatek/mt7622pr2h.bin and mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin are missing [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2011520/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011521] Re: USB: serial: option: add Quectel EM05CN modem
** Tags added: austin-charlotte oem-priority originate-from-2002494 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2011521 Title: USB: serial: option: add Quectel EM05CN modem Status in HWE Next: New Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: In Progress Bug description: [ Impact ] * add Quectel EM05CN modem id [ Test Plan ] * testing on the system with this modem [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2011521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998905] Re: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
This bug is awaiting verification that the linux- riscv-5.15/5.15.0-1030.34~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-riscv-5.15 verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1998905 Title: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic) Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] On the development, we found sometimes there is no audio output device when headphone is connected to the rear audio jack. [Fix] Cirrus Logic provides a patch to fix this https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/ The patch is included in v6.2-rc1 9fb9fa18fb50 ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock. [Test] Verified by our QA and ODM. [Where problems could occur] It extends the delay time, should be no harm for existing platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000299] Re: Fix W6400 hang after resume of S3 stress
This bug is awaiting verification that the linux- riscv-5.15/5.15.0-1030.34~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-riscv-5.15 verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000299 Title: Fix W6400 hang after resume of S3 stress Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Bug description: [Impact] amdgpu hang when stress S3 on AMD W6400 GPU. [Fix] Add a WA to manually adjust strobe calculation using FCLK restrict. [Test] Suspend AMD W6400 for 40 times, it works fine. [Where problems could occur] Low risk, upstream fix. It may cause AMD GPU hang. The patch is in 5.16, only Jammy kernel needs it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2000299/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002812] Re: Revoke & rotate to new signing key
** Tags removed: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002812 Title: Revoke & rotate to new signing key Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * Revoke & rotate to new signing key * Update revocations, which match the next Ubuntu shim 15.7 revocations. Specifically - revoke certs that were previously protected with by-hash revocations, revoke lost/unused certificates. * Start using advantage2021v1 and ubuntu2022v1 signing keys. * This is a routine key rotation. [ Test Plan ] * Check that old shim/grub boot this kernel * Check that the upcomming future shim/grub can boot this kernel * Check that these kernels can do signed kexec into itself [ Where problems could occur ] * Kernels with this patch applied should be signed using ubuntu/4 pro/3 core/2 signing streams. [ Other Info ] * TPM PCR values and measurements will change when changing the signing key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003053] Re: NFS: client permission error after adding user to permissible group
This bug is awaiting verification that the linux- riscv-5.15/5.15.0-1030.34~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-riscv-5.15 -- 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/2003053 Title: NFS: client permission error after adding user to permissible group Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: [Impact] The NFS client's access cache becomes stale due to the user's group membership changing on the server after the user has already logged in on the client. The access cache only expires if either NFS_INO_INVALID_ACCESS flag is on or timeout (without delegation). Adding a user to a group in the NFS server will not cause any file attributes to change. The client will encounter permission errors until other file attributes are changed or the memory cache is dropped. [Fix] The access cache shall be cleared once the user logs out and logs back in again. 0eb43812c0270ee3d005ff32f91f7d0a6c4943af NFS: Clear the file access cache upon login 029085b8949f5d269ae2bbd14915407dd0c7f902 NFS: Judge the file access cache's timestamp in rcu path 5e9a7b9c2ea18551759833146a181b14835bfe39 NFS: Fix up a sparse warning [Test Plan] 1.[client side] testuser is not part of testgroup testuser@kinetic:~$ ls -ld /mnt/private/ drwxrwx--- 2 root testgroup 4096 Nov 24 08:23 /mnt/private/ testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied 2.[server side] add testuser into testgroup, which has access to folder root@kinetic:~$ usermod -aG testgroup testuser && echo `date +'%s'` > /proc/net/rpc/auth.unix.gid/flush 3.[client side] create a file again but still fail testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied [Where problems could occur] The fix will apply upstream commits, so the regression can be considered as low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002889] Re: 5.15.0-58.64 breaks xen bridge networking (pvh domU)
This bug is awaiting verification that the linux- riscv-5.15/5.15.0-1030.34~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-riscv-5.15 -- 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/2002889 Title: 5.15.0-58.64 breaks xen bridge networking (pvh domU) Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Xen guests will not have network access. This fixes a regression due to the fix for CVE-2022-3643. [Testing] This has only been build-tested. [Potential regression] Xen guests might not have network access. -- With 5.15.0-58.64-generic, bridge networking on xen is broken : no packet (check with tcpdump) flowing between dom0 and any domUs attached to a network bridge. downgrading to 5.15.0-57-generic fix the issue. Thus the patch to the netback driver seems the cause. relevant network config : brtctl show : br0 8000.XXXno eno1 vif1.0 relevant domU config : kernel = '/usr/lib/grub-xen/grub-i386-xen_pvh.bin' type = 'pvh' vif = [ 'ip=192.168.10.10 ,bridge=br0' ] No message in dmesg, journal, xen logs.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007798] Re: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
This bug is awaiting verification that the linux- riscv-5.15/5.15.0-1030.34~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-riscv-5.15 verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007798 Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: == SRU Justification == [Impact] Audio playback becomes silent on some Intel SoF systems. [Fix] Revert offending commit. [Test] The speaker can always play sound after the commit gets reverted. [Where problems could occur] Audio on linux 5.15 has been working fine without the patch for a long time, so this only restore it to where it was. == Original Bug Report == [Summary] During the kernel SRU testing on focal-hwe, I found the audio output of some machines are broken. I've tested some of machine on Jammy using same kernel(5.15.0-66-generic) and haven't seen this happened. The volume bars in settings react to what sound is played correctly and device is detected as well. [Reproduce steps] 1. install focal 2. enable -proposed 3. run apt dist-upgrade. 4. reboot. 5. press fn keys to volume up then volume down or play a short youtube video. 6. after a while can't hear any sound from the speaker. [Failure rate] 10/10 [Additional info] If I run "sudo alsa force-reload" can make audio work again, but after a while it breaks again. These are machines that impacted by this bug: https://certification.canonical.com/hardware/202007-28045/ https://certification.canonical.com/hardware/201906-27109/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/202007-28047/ https://certification.canonical.com/hardware/202007-28055/ https://certification.canonical.com/hardware/202005-27899/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-66.73~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1303 F pulseaudio CasperMD5CheckResult: skip Date: Sun Feb 19 21:24:59 2023 InstallationDate: Installed on 2020-08-03 (930 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Feb 19 20:53:23 dell-inspiron-7591-nebula-n15a-c2-201903-26881 dbus-daemon[985]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1303 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd11/06/2019:br1.5:svnDellInc.:pnInspiron7590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0922: dmi.product.family: Inspiron dmi.product.name: Inspiron 7590 dmi.product.sku: 0922 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007798/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011748] Re: lunar/linux 6.2 fails to boot on arm64
** Description changed:
[Impact]
On certain bare metal arm64 boards the latest lunar/linux
6.2.0-17-generic fails to boot, the kernel gets stuck reporting the
following oops:
[ 72.043484] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 72.049571] rcu: 22-...0: (30 GPs behind)
idle=b10c/1/0x4000 softirq=164/164 fqs=6443
[ 72.058520] (detected by 28, t=15005 jiffies, g=449, q=174 ncpus=32)
[ 72.064949] Task dump for CPU 22:
[ 72.068251] task:kworker/u64:5 state:R running task stack:0
pid:447 ppid:2 flags:0x000a
[ 72.078156] Workqueue: efi_rts_wq efi_call_rts
[ 72.082595] Call trace:
[ 72.085029] __switch_to+0xbc/0x100
The bug doesn't seem to happen on arm64 virtual machines, it happens
only on physical arm64 systems.
+ This regression has been introduced by:
+
+ e7b813b32a42 ("efi: random: refresh non-volatile random seed when RNG is
+ initialized")
+
[Test case]
Boot the kernel on a physical arm64 board (i.e., kuzzle in our lab).
+
+ [Fix]
+
+ Revert commit e7b813b32a42 for now, at the same time address this issue
+ upstream in order to find a proper fix.
+
+ [Regression potential]
+
+ We may want to address this upstream to find a proper fix. Reverting the
+ commit restores the previous behavior, but we also lose the capability
+ of having a better RNG on the affected arm64 hardware.
--
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/2011748
Title:
lunar/linux 6.2 fails to boot on arm64
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Lunar:
Incomplete
Bug description:
[Impact]
On certain bare metal arm64 boards the latest lunar/linux
6.2.0-17-generic fails to boot, the kernel gets stuck reporting the
following oops:
[ 72.043484] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 72.049571] rcu: 22-...0: (30 GPs behind)
idle=b10c/1/0x4000 softirq=164/164 fqs=6443
[ 72.058520] (detected by 28, t=15005 jiffies, g=449, q=174 ncpus=32)
[ 72.064949] Task dump for CPU 22:
[ 72.068251] task:kworker/u64:5 state:R running task stack:0
pid:447 ppid:2 flags:0x000a
[ 72.078156] Workqueue: efi_rts_wq efi_call_rts
[ 72.082595] Call trace:
[ 72.085029] __switch_to+0xbc/0x100
The bug doesn't seem to happen on arm64 virtual machines, it happens
only on physical arm64 systems.
This regression has been introduced by:
e7b813b32a42 ("efi: random: refresh non-volatile random seed when RNG
is initialized")
[Test case]
Boot the kernel on a physical arm64 board (i.e., kuzzle in our lab).
[Fix]
Revert commit e7b813b32a42 for now, at the same time address this
issue upstream in order to find a proper fix.
[Regression potential]
We may want to address this upstream to find a proper fix. Reverting
the commit restores the previous behavior, but we also lose the
capability of having a better RNG on the affected arm64 hardware.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011748/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000709] Re: net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19
Tested using linux kinetic version 5.19.0-37.38: # make run_tests -C net TEST_PROGS=cmsg_ipv6.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='' make: Entering directory '/root/linux-5.19.0/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/root/linux-5.19.0' INSTALL ./usr/include make[1]: Leaving directory '/root/linux-5.19.0' TAP version 13 1..1 # selftests: net: cmsg_ipv6.sh # OK ok 1 selftests: net: cmsg_ipv6.sh Linux ubuntu-kinetic 5.19.0-37-generic #38-Ubuntu SMP PREEMPT_DYNAMIC Wed Mar 1 18:08:14 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- 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/2000709 Title: net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Kinetic: Fix Committed Bug description: Issue found with 5.19.0-28.29 Running 'make run_tests -C net TEST_PROGS=cmsg_ipv6.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' TAP version 13 1..1 # selftests: net: cmsg_ipv6.sh # Case TCLASS UDP setsock - packet data returned 1, expected 0 # Case TCLASS ICMP setsock - packet data returned 1, expected 0 # Case TCLASS RAW setsock - packet data returned 1, expected 0 # Case TCLASS UDP cmsg - packet data returned 1, expected 0 # Case TCLASS ICMP cmsg - packet data returned 1, expected 0 # Case TCLASS RAW cmsg - packet data returned 1, expected 0 # Case TCLASS UDP both - packet data returned 1, expected 0 # Case TCLASS ICMP both - packet data returned 1, expected 0 # Case TCLASS RAW both - packet data returned 1, expected 0 # Case TCLASS UDP diff - packet data returned 1, expected 0 # Case TCLASS ICMP diff - packet data returned 1, expected 0 # Case TCLASS RAW diff - packet data returned 1, expected 0 # Case HOPLIMIT UDP setsock - packet data returned 1, expected 0 # Case HOPLIMIT ICMP setsock - packet data returned 1, expected 0 # Case HOPLIMIT RAW setsock - packet data returned 1, expected 0 # Case HOPLIMIT UDP cmsg - packet data returned 1, expected 0 # Case HOPLIMIT ICMP cmsg - packet data returned 1, expected 0 # Case HOPLIMIT RAW cmsg - packet data returned 1, expected 0 # Case HOPLIMIT UDP both - packet data returned 1, expected 0 # Case HOPLIMIT ICMP both - packet data returned 1, expected 0 # Case HOPLIMIT RAW both - packet data returned 1, expected 0 # Case HOPLIMIT UDP diff - packet data returned 1, expected 0 # Case HOPLIMIT ICMP diff - packet data returned 1, expected 0 # Case HOPLIMIT RAW diff - packet data returned 1, expected 0 # FAIL - 24/93 cases failed not ok 1 selftests: net: cmsg_ipv6.sh # exit=1 This is not a regression as the net test build was blocked with bug 1993155 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000709/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011748] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2011748 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2011748 Title: lunar/linux 6.2 fails to boot on arm64 Status in linux package in Ubuntu: Incomplete Status in linux source package in Lunar: Incomplete Bug description: [Impact] On certain bare metal arm64 boards the latest lunar/linux 6.2.0-17-generic fails to boot, the kernel gets stuck reporting the following oops: [ 72.043484] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 72.049571] rcu: 22-...0: (30 GPs behind) idle=b10c/1/0x4000 softirq=164/164 fqs=6443 [ 72.058520] (detected by 28, t=15005 jiffies, g=449, q=174 ncpus=32) [ 72.064949] Task dump for CPU 22: [ 72.068251] task:kworker/u64:5 state:R running task stack:0 pid:447 ppid:2 flags:0x000a [ 72.078156] Workqueue: efi_rts_wq efi_call_rts [ 72.082595] Call trace: [ 72.085029] __switch_to+0xbc/0x100 The bug doesn't seem to happen on arm64 virtual machines, it happens only on physical arm64 systems. [Test case] Boot the kernel on a physical arm64 board (i.e., kuzzle in our lab). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011748] [NEW] lunar/linux 6.2 fails to boot on arm64
Public bug reported: [Impact] On certain bare metal arm64 boards the latest lunar/linux 6.2.0-17-generic fails to boot, the kernel gets stuck reporting the following oops: [ 72.043484] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 72.049571] rcu: 22-...0: (30 GPs behind) idle=b10c/1/0x4000 softirq=164/164 fqs=6443 [ 72.058520] (detected by 28, t=15005 jiffies, g=449, q=174 ncpus=32) [ 72.064949] Task dump for CPU 22: [ 72.068251] task:kworker/u64:5 state:R running task stack:0 pid:447 ppid:2 flags:0x000a [ 72.078156] Workqueue: efi_rts_wq efi_call_rts [ 72.082595] Call trace: [ 72.085029] __switch_to+0xbc/0x100 The bug doesn't seem to happen on arm64 virtual machines, it happens only on physical arm64 systems. [Test case] Boot the kernel on a physical arm64 board (i.e., kuzzle in our lab). ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Lunar) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2011748 Title: lunar/linux 6.2 fails to boot on arm64 Status in linux package in Ubuntu: Incomplete Status in linux source package in Lunar: Incomplete Bug description: [Impact] On certain bare metal arm64 boards the latest lunar/linux 6.2.0-17-generic fails to boot, the kernel gets stuck reporting the following oops: [ 72.043484] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 72.049571] rcu: 22-...0: (30 GPs behind) idle=b10c/1/0x4000 softirq=164/164 fqs=6443 [ 72.058520] (detected by 28, t=15005 jiffies, g=449, q=174 ncpus=32) [ 72.064949] Task dump for CPU 22: [ 72.068251] task:kworker/u64:5 state:R running task stack:0 pid:447 ppid:2 flags:0x000a [ 72.078156] Workqueue: efi_rts_wq efi_call_rts [ 72.082595] Call trace: [ 72.085029] __switch_to+0xbc/0x100 The bug doesn't seem to happen on arm64 virtual machines, it happens only on physical arm64 systems. [Test case] Boot the kernel on a physical arm64 board (i.e., kuzzle in our lab). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007633] Re: amdgpu fails to init with kernel 5.19.0
I see that the error "amdgpu: Move buffer fallback to memcpy unavailable" comes from drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c. I downloaded the Ubuntu source code for 5.19.0-35 and compiled with the amdgpu_ttm.c from the Linux 5.19 snapshot on github. This eliminated the error and my Kaveri machine boots successfully with amdgpu. If that helps at all. Though my Cezanne 5600G works fine with 5.19.0-35. -- 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/2007633 Title: amdgpu fails to init with kernel 5.19.0 Status in linux package in Ubuntu: Confirmed Bug description: Update 2023-03-04: A new version of the 5.19 kernel, 5.19.0-35-generic, will now boot into a GUI desktop instead of leaving me with a completely unusable system, BUT, there is no working Vulkan implementation, as if the amdgpu driver still failed to load so the new kernel did a fallback to the radeon driver, I would guess. Partial output from vulkaninfo with 5.19 kernel: -- Device Properties and Extensions: = GPU0: VkPhysicalDeviceProperties: --- apiVersion= 4206816 (1.3.224) driverVersion = 1 (0x0001) vendorID = 0x10005 deviceID = 0x deviceType= PHYSICAL_DEVICE_TYPE_CPU deviceName= llvmpipe (LLVM 15.0.6, 256 bits) pipelineCacheUUID = 76616c2d-2573--- END of Update 2023-03-04 I recently installed apt upgrades, and among the upgrades, was the 5.19.0-32-generic kernel. I also still have installed the 5.15.0-58-generic kernel. Every time I try to boot with the 5.19 kernel, my AMD Radeon R9 280 GPU fails to init. This results in the computer effectively getting 'hung' part way through the kernel boot as X or Wayland, whatever should start up, doesn't. The kernel keeps running (I can see the hard drive light occasionally flash on my case, and the kernel logs continue after the point of the apparent hang - although kernel messages stop getting output to the console - to see the messages, I have to reboot with 5.15 then use journalctl to review the previous boot messages). It inits fine with the older kernel. Not sure what the root cause of the failure is. Found this in kernel boot logs (via "journalctl -b -1" to get the logs for the previous boot, that failed), which I think is indicative of the problem: Feb 16 21:37:17 jeff-linux kernel: status: Feb 16 21:37:17 jeff-linux kernel: [drm] amdgpu: dpm initialized Feb 16 21:37:17 jeff-linux kernel: [drm] Found UVD firmware Version: 64.0 Family ID: 13 Feb 16 21:37:17 jeff-linux kernel: amdgpu: Move buffer fallback to memcpy unavailable Feb 16 21:37:17 jeff-linux kernel: [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init of IP block failed -19 Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu_device_ip_init failed Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: Fatal error during GPU init Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu: finishing device. Feb 16 21:37:17 jeff-linux kernel: BUG: kernel NULL pointer dereference, address: 0090 -- version signature info (line 2 from kernel boot log): Feb 16 21:37:14 jeff-linux kernel: Linux version 5.19.0-32-generic (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 (Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17) - root@jeff-linux:/home/jeff# lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 See attached lspci-vnvn.log --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jeff 1525 F pulseaudio /dev/snd/controlC0: jeff 1525 F pulseaudio /dev/snd/controlC1: jeff 1525 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-27 (355 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=bd9a6ac0-c013-4645-a8d7-23af9e13d239 ro quiet splash radeon.si_support=0 radeon.cik_support=0
[Kernel-packages] [Bug 1612916] Re: [Tohsiba Portege Z20T-C] Internal speakers don't work after standby
I am using Kubuntu 20.10 on a Toshiba Z20T-C-140 and this bug still exists. Any way I can help to solve this issue by providing logfiles? It would be a shame not being able to use this laptop because of this old bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1612916 Title: [Tohsiba Portege Z20T-C] Internal speakers don't work after standby Status in linux package in Ubuntu: Confirmed Status in Arch Linux: New Status in linux package in Debian: New Bug description: On initial boot, sound on internal speakers is working. After standby it doesn work anymore, but a analog headset does. Switching around in pavucontrol doesn't work... Internal microphone works. I'm using Ubuntu 16.04 64 bit on a 4.4.0-34-generic kernel. Toshiba/Dynabook Portege Z20T-C: https://support.dynabook.com/support/modelHome?freeText=1200015981=785 WORKAROUND: Use suspend to disk. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michi 6510 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/1tb-swap MachineType: TOSHIBA PORTEGE Z20t-C Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed root=/dev/mapper/1tb-miniubuntu ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/27/2016 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 5.60 dmi.board.asset.tag: 00 dmi.board.name: PORTEGE Z20t-C 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.modalias: dmi:bvnTOSHIBA:bvrVersion5.60:bd06/27/2016:svnTOSHIBA:pnPORTEGEZ20t-C:pvrPT16BE-00W006GR:rvnTOSHIBA:rnPORTEGEZ20t-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z20t-C dmi.product.version: PT16BE-00W006GR dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009271] Re: Too many BDL entries regression
FYI: You can see this every time you login to a terminal screen (not X). So, Ctl-Alt-F2, then login. You'll generate ~26 of them each time. -- 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/2009271 Title: Too many BDL entries regression Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: Hello, Thanks for your hard work :) I got this error after kernel update to 5.19.0-35 as explained here : https://askubuntu.com/questions/1457367/snd-hda-intel-001f-3-too-many-bdl-entries-messages-in-system-log and here : https://lore.kernel.org/stable/cab1lbmv1ky+kuubwvxroe+mbqbjtjofvzb8smmbcuy2mdvg...@mail.gmail.com/T/#u A load of syslog "Too many BDL entries" appears. Have a nice week-end, best regards, Laurent Lyaudet ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-35-generic 5.19.0-35.36 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent5004 F wireplumber /dev/snd/controlC1: laurent5004 F wireplumber /dev/snd/seq:laurent5000 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 16:47:55 2023 InstallationDate: Installed on 2020-07-01 (976 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. GL73 8SD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=894d943a-5e5a-4980-96c2-64d37638009d 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. RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-21 (134 days ago) dmi.bios.date: 03/29/2019 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C7IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-17C7 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1: dmi.product.family: GL dmi.product.name: GL73 8SD dmi.product.sku: 17C7.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011738] Re: Add ATX related reporting nodes in mlxbf-ptm debugfs driver
** Description changed: SRU Justification: [Impact] mlxbf-ptm is a kernel driver that provides debufgs interface for system software to monitor Bluefield devices' power and thermal management parameters. [Fix] * This change adds additional debugfs nodes that provide ATX status and - power profile data. + power profile data. Replaces S_IRUGO with 0444 inline with checkpatch + expectation. [Test Case] * After installing the kernel module, debugfs entry at /sys/kernel/debug/mlxbf-ptm will be created * monitors/status folder contains read-only parameters reported from the Bluefield device [Regression Potential] * Minimal - as these are read-only parameters that report Bluefield device information. [Other] * This code is likely to change depending on feedback we received from maintainers. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2011738 Title: Add ATX related reporting nodes in mlxbf-ptm debugfs driver Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] mlxbf-ptm is a kernel driver that provides debufgs interface for system software to monitor Bluefield devices' power and thermal management parameters. [Fix] * This change adds additional debugfs nodes that provide ATX status and power profile data. Replaces S_IRUGO with 0444 inline with checkpatch expectation. [Test Case] * After installing the kernel module, debugfs entry at /sys/kernel/debug/mlxbf-ptm will be created * monitors/status folder contains read-only parameters reported from the Bluefield device [Regression Potential] * Minimal - as these are read-only parameters that report Bluefield device information. [Other] * This code is likely to change depending on feedback we received from maintainers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2011738/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956104] Re: firmware-sof description is inaccurate and misleading
** Tags added: kinetic lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/1956104 Title: firmware-sof description is inaccurate and misleading Status in firmware-sof package in Ubuntu: Confirmed Bug description: Package description says Intel firmware. https://thesofproject.github.io/latest/platforms/index.html https://www.cadence.com/en_US/home/tools/ip/tensilica-ip/tensilica- xtensa-controllers-and-extensible-processors.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1956104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011738] [NEW] Add ATX related reporting nodes in mlxbf-ptm debugfs driver
Public bug reported: SRU Justification: [Impact] mlxbf-ptm is a kernel driver that provides debufgs interface for system software to monitor Bluefield devices' power and thermal management parameters. [Fix] * This change adds additional debugfs nodes that provide ATX status and power profile data. [Test Case] * After installing the kernel module, debugfs entry at /sys/kernel/debug/mlxbf-ptm will be created * monitors/status folder contains read-only parameters reported from the Bluefield device [Regression Potential] * Minimal - as these are read-only parameters that report Bluefield device information. [Other] * This code is likely to change depending on feedback we received from maintainers. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2011738 Title: Add ATX related reporting nodes in mlxbf-ptm debugfs driver Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] mlxbf-ptm is a kernel driver that provides debufgs interface for system software to monitor Bluefield devices' power and thermal management parameters. [Fix] * This change adds additional debugfs nodes that provide ATX status and power profile data. [Test Case] * After installing the kernel module, debugfs entry at /sys/kernel/debug/mlxbf-ptm will be created * monitors/status folder contains read-only parameters reported from the Bluefield device [Regression Potential] * Minimal - as these are read-only parameters that report Bluefield device information. [Other] * This code is likely to change depending on feedback we received from maintainers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2011738/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996536] Re: selftests/.../nat6to4 breaks the selftests build
After installing clang in my chroot, this builds as expected. Marking verification done. -- 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/1996536 Title: selftests/.../nat6to4 breaks the selftests build Status in linux package in Ubuntu: Fix Committed Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: Unused test program tools/testing/selftests/net/bpf/nat6to4 cannot easily be built in the standard Ubuntu kernel build environment. The "tools/testing/selftests/" are not built at all by Ubuntu kernel package builds, but are part of my build-test workflow, which is interrupted by this breakage. This mainline bpf selftest (nat6to4) requires additional package dependencies not satisfied by the Ubuntu kernel Build-depends and unsatisfiable when cross compilers are installed. Disable it to allow the rest of selftests/ to build. [Impact] * No impact on Ubuntu kernel package builds. [Test Case] * Allows internal (manual) testing of the `fakeroot debian/rules compileselftests` build target. [Regression Potential] * None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996536] Re: selftests/.../nat6to4 breaks the selftests build
** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- 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/1996536 Title: selftests/.../nat6to4 breaks the selftests build Status in linux package in Ubuntu: Fix Committed Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: Unused test program tools/testing/selftests/net/bpf/nat6to4 cannot easily be built in the standard Ubuntu kernel build environment. The "tools/testing/selftests/" are not built at all by Ubuntu kernel package builds, but are part of my build-test workflow, which is interrupted by this breakage. This mainline bpf selftest (nat6to4) requires additional package dependencies not satisfied by the Ubuntu kernel Build-depends and unsatisfiable when cross compilers are installed. Disable it to allow the rest of selftests/ to build. [Impact] * No impact on Ubuntu kernel package builds. [Test Case] * Allows internal (manual) testing of the `fakeroot debian/rules compileselftests` build target. [Regression Potential] * None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968310] Re: arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K
test is now passing on Kinetic ** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1968310 Title: arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-hwe-5.17 source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-hwe-5.17 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In selftests: net: arp_ndisc_evict_nocarrier.sh, even all of the sub-tests from this script have passed, the overall test result is still a fail. # selftests: net: arp_ndisc_evict_nocarrier.sh # run arp_evict_nocarrier=1 test # ok # run arp_evict_nocarrier=0 test # ok # run all.arp_evict_nocarrier=0 test # ok # run ndisc_evict_nocarrier=1 test # ok # run ndisc_evict_nocarrier=0 test # ok # run all.ndisc_evict_nocarrier=0 test # ok not ok 1 selftests: net: arp_ndisc_evict_nocarrier.sh # exit=255 This is caused by the cleanup() in the script, as it's trying to access a non-existing file. [Fix] * 9c4d7f45d6 selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier This patch can be cherry-picked into all affected kernels. [Test] Run the patched test and the test will pass. [Where problems could occur] Change limited to testing tools, no impact to real kernel function or test performances. [Original Bug Report] Issue found on Jammy OEM 5.17.0-1003.3 It looks like all the sub-tests has passed, but the final return value is not 0. Running 'make run_tests -C net TEST_PROGS=arp_ndisc_evict_nocarrier.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' TAP version 13 1..1 # selftests: net: arp_ndisc_evict_nocarrier.sh # run arp_evict_nocarrier=1 test # ok # run arp_evict_nocarrier=0 test # ok # run all.arp_evict_nocarrier=0 test # ok # run ndisc_evict_nocarrier=1 test # ok # run ndisc_evict_nocarrier=0 test # ok # run all.ndisc_evict_nocarrier=0 test # ok not ok 1 selftests: net: arp_ndisc_evict_nocarrier.sh # exit=255 make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1968310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003640] Re: Integrate NVIDIA Grace kernel fixes for vGIC
This bug was fixed in the package linux-nvidia-5.19 - 5.19.0-1007.7 --- linux-nvidia-5.19 (5.19.0-1007.7) jammy; urgency=medium * jammy/linux-nvidia-5.19: 5.19.0-1007.7 -proposed tracker (LP: #2003754) * Integrate NVIDIA Grace kernel fixes for vGIC (LP: #2003640) - SAUCE: KVM: arm64: GICv4.1: Fix race with doorbell on VPE activation/deactivation -- Ian May Tue, 24 Jan 2023 16:28:34 -0600 ** Changed in: linux-nvidia-5.19 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2003640 Title: Integrate NVIDIA Grace kernel fixes for vGIC Status in linux-nvidia-5.19 package in Ubuntu: Fix Released Bug description: [Impact] To save the vgic LPI pending state with GICv4.1, the VPEs must all be unmapped from the ITSs so that the sGIC caches can be flushed. The opposite is done once the state is saved. This is all done by using the activate/deactivate irqdomain callbacks directly from the vgic code. Crutially, this is done without holding the irqdesc lock for the interrupts that represent the VPE. And these callbacks are changing the state of the irqdesc. What could possibly go wrong? If a doorbell fires while we are messing with the irqdesc state, it will acquire the lock and change the interrupt state concurrently. Since we don't hole the lock, curruption occurs in on the interrupt state. Oh well. While acquiring the lock would fix this (and this was Shanker's initial approach), this is still a layering violation we could do without. A better approach is actually to free the VPE interrupt, do what we have to do, and re-request it. It is more work, but this usually happens only once in the lifetime of the VM and we don't really care about this sort of overhead. The upstream maintainer acknowledged the bug, fixed the issue. and it will be available in v6.2. [Fixes] - single patch to address the race condition on VPE activation/deactivation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-5.19/+bug/2003640/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008833] Re: mlxbf-gige: Fix intermittent no ip issue
This bug is awaiting verification that the linux- bluefield/5.15.0-1014.16 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-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2008833 Title: mlxbf-gige: Fix intermittent no ip issue Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Although the link is up, and the PHY interrupt is cleared, there is no ip assigned. Nothing is being transmitted, and nothing is received. The RX error count keeps on increasing (check ifconfig oob_net0). After several minutes, the RX error count stagnates and the oob finally gets an ip and is pingable. [Fix] The issue is in the mlxbf_gige_rx_init function. As soon as the RX DMA is enabled, the RX CI reaches the max 128, it becomes equal to RX PI. And RX CI doesn't decrease since the code hasn't ran phy_start yet. The solution is to move the rx init after phy_start. This fix applies to both 5.4 and 5.15. [Test Case] * Check if the gige driver is loaded * Check that the oob_net0 interface is up and pingable from an external host * Do at ~1000 resets and powercycles and check the oon_net0 interface again [Regression Potential] * No known regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2008833/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933090] Re: systemd/245.4-4ubuntu3.6 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** Merge proposal linked:
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/438988
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1933090
Title:
systemd/245.4-4ubuntu3.6 ADT test failure with linux-
hwe-5.11/5.11.0-20.21~20.04.1
Status in linux-hwe-5.11 package in Ubuntu:
Won't Fix
Status in linux-hwe-5.15 package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Fix Released
Status in linux-hwe-5.11 source package in Focal:
Won't Fix
Status in linux-hwe-5.15 source package in Focal:
Invalid
Status in systemd source package in Focal:
Triaged
Bug description:
[SRU Impact]
Sysctl was removed from 5.5 kernels. In src/test/test-seccomp.c,
test_protect_syscall
sysctl is called with the expectation the error result is EFAULT and not
ENOSYS.
This affects autotests for all focal-5.15 linux kernels (hwe, azure, gcp,
oem, gke, oracle).
[Fix]
Assertion checks if either EFAULT or ENOSYS is returned. This way it will
work for focal-5.4 kernels and focal-5.15 kernels.
[Test to reproduce the issue]
1. Create a vm and install one of the focal-5.15 kernels (i.e
5.15.0-1029.35~20.04.1 linux-oracle-5.15).
2. Run the autotests for upstream and/or root-unittests:
autopkgtest --test-name=upstream systemd -- qemu
[Test to verify the fix]
1. Same as above
2. Apply the fix in your local repo and run the tests using your local repo
autopkgtest --test-name=upstream -- qemu
[Where problems could occur]
This is not gonna affect end users since it is a change in the test only.
It may impact autotests, but it's a very low probability.
[Original Description]
This is a scripted bug report about ADT failures while running systemd
tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this
is caused by the dep8 tests of the tested source or the kernel has yet
to be determined.
Testing failed on:
amd64:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz
armhf:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz
ppc64el:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz
s390x:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz
In arm64, ppc64el and s390x, 'root-unittests' fails with:
/* test_protect_sysctl */
Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function
test_protect_sysctl(). A
borting.
sysctlseccomp terminated by signal ABRT.
Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) ==
EXIT_SUCCESS' failed at s
rc/test/test-seccomp.c:324, function test_protect_sysctl(). Aborting.
FAIL: test-seccomp (code: 134)
In amd64, 'upstream' also fails on 'TEST-24-UNIT-TESTS', which
apparently is caused by the same 'test-seccomp.c:311' assertion
failure.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933090/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144
** Merge proposal linked: https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/438988 -- 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/1991285 Title: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144 Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Status in linux source package in Focal: New Status in systemd source package in Focal: Incomplete Bug description: [Impact] The armhf autopkgtests currently fail in Focal due to this, and failures are not marked as regressions. This limits our ability to catch other regressions on armhf. [Test Plan] The boot-and-services autopkgtest should not fail on armhf. Specifically, the test_no_failed test should ignore systemd-remount-fs.service failures on armhf only. [Where problems could occur] The fix is limited to the boot-and-services autopkgtest, so there is limited risk. Any bugs would show up in that test. [Original Description] This is a scripted bug report about ADT failures while running systemd tests for linux/5.4.0-128.144 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009522] Re: Upgrade Kernel 5.19.0-35-generic [Sound Blaster Recon3D / Z-Series] not detected anymore
https://askubuntu.com/questions/1457574/upgrade- kernel-5-19-0-35-generic-sound-blaster-recon3d-z-series-not-detected Same in my case. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009522 Title: Upgrade Kernel 5.19.0-35-generic [Sound Blaster Recon3D / Z-Series] not detected anymore Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: Upgrade Kernel 5.19.0-35-generic [Sound Blaster Recon3D / Z-Series] not detected anymore Operating System: Kubuntu 22.10 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-35-generic (64-bit) Graphics Platform: X11 Processors: 16 × Intel® Core™ i9-9900KF CPU @ 3.60GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z390 UD See also https://askubuntu.com/questions/1457574/upgrade- kernel-5-19-0-35-generic-sound-blaster-recon3d-z-series-not-detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 failed on Oracle kernels
** Tags added: sru-20230227 -- 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 failed on Oracle kernels Status in ubuntu-kernel-tests: Triaged Status in linux-oracle package in Ubuntu: Confirmed Status in linux-oracle-5.0 package in Ubuntu: Confirmed Status in linux-oracle-5.4 package in Ubuntu: New Bug description: With test case updated, there are just 3 failures reported on 2023.02.09: B-oracle-4.15, B-oralce-5.4, F-oracle: FAIL: Intel: all counters FAIL: Intel: running counter wrmsr: cntr FAIL: Intel: running counter wrmsr: status msr bit F-oracle-5.15, J-oracle, K-oracle: FAIL: Intel: all counters [Original Bug Report] 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 2008672] Re: focal linux-xilinx-zynqmp promote from universe to main
** Merge proposal linked: https://code.launchpad.net/~xnox/ubuntu-seeds/+git/platform/+merge/438973 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2008672 Title: focal linux-xilinx-zynqmp promote from universe to main Status in linux-meta-xilinx-zynqmp package in Ubuntu: Triaged Status in linux-xilinx-zynqmp package in Ubuntu: Triaged Bug description: focal linux-xilinx-zynqmp promote from universe to main new kernel published in the wrong component. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-xilinx-zynqmp/+bug/2008672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814234] Re: rtcpie in timers from ubuntu_kernel_selftests randomly failing
Didn't see this issue on F-oem-5.14.0-1059.67 ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814234 Title: rtcpie in timers from ubuntu_kernel_selftests randomly failing Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: Node: Standard_D11_v2 Kernel: 4.18.0-1008.8~18.04.1 selftests: timers: rtcpie Periodic IRQ rate is 1024Hz. Counting 20 interrupts at: 2Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 4Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 8Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 16Hz:1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 32Hz:1 2 3 4 5 6 7 PIE delta error: 0.034667 should be close to 0.031250 181. 01/30 20:08:46 DEBUG| utils:0153| [stdout] not ok 1..9 selftests: timers: rtcpie [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1814234/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008672] Re: focal linux-xilinx-zynqmp promote from universe to main
@Steve These packages only exist in focal. components-missmatches report is for devel only. in devel, there is a binary package pattern to automatically seed all kernels, as in practice we don't have almost any non-main kernels. I can add these package to focal seeds, but it will not actually make this package appear in the components missmatches. But also nothing will cause it to be downgraded. Please promote these focal-only packages, to main, in focal only. ** Changed in: linux-meta-xilinx-zynqmp (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2008672 Title: focal linux-xilinx-zynqmp promote from universe to main Status in linux-meta-xilinx-zynqmp package in Ubuntu: Triaged Status in linux-xilinx-zynqmp package in Ubuntu: Triaged Bug description: focal linux-xilinx-zynqmp promote from universe to main new kernel published in the wrong component. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-xilinx-zynqmp/+bug/2008672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996048] Re: Screen freeze after resuming from suspend (nvme0: I/O timeout)
Since this arrived in Jammy/5.15 via stable and those normally do not need to be verified I am marking the verification here as done. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1996048 Title: Screen freeze after resuming from suspend (nvme0: I/O timeout) Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] The system hangs after S3 with VMD mode is on. [Fix] Intel provides a fix and still under discussion https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/ Included in v6.2-rc1 d899aa668498 PCI: vmd: Disable MSI remapping after suspend [Test] Verified by us and ODM. [Where problems could occur] The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1996048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003816] Re: Regression in ext4 during online resize
This looks to have been picked into derivative 5.15 kernels and verified there already. So I am taking that as base for the distro kernel fix. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2003816 Title: Regression in ext4 during online resize Status in linux package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-gcp source package in Jammy: Fix Released Bug description: Issue resize2fs utility is used to resize the filesystem and is idempotent in nature. But in the 5.15 kernel, successive execution of resize2fs is returning error. Reproduction step (on AWS): Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 5.15.0-1022-aws) in us-west-2 region and attach an EBS volume. Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p /mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0 Increase the size of EBS volume. Run sudo resize2fs /dev/xvdb multiple times. The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 5242880 (4k) blocks long. Nothing to do! When you run the same step on the latest image ami-0a1d6d351894df6cc (Linux 5.15.0-1026-aws). The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) resize2fs: Superblock checksum does not match superblock while trying to open /dev/xvdb Couldn't find valid filesystem superblock. FIX: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971151] Re: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support
** Changed in: linux (Ubuntu Jammy) 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/1971151 Title: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: f304d35e5995 scsi: mpi3mr: Update driver version to 8.0.0.69.0 7dbd0dd8cde3 scsi: mpi3mr: Add support for NVMe passthrough 986d6bad2103 scsi: mpi3mr: Expose adapter state to sysfs 43ca11005098 scsi: mpi3mr: Add support for PEL commands 506bc1a0d6ba scsi: mpi3mr: Add support for MPT commands f3de4706c1e0 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header f5e6d5a34376 scsi: mpi3mr: Add support for driver commands 4268fa751365 scsi: mpi3mr: Add bsg device support 1fcbe4c49039 scsi: mpi3mr: Fix kernel-doc 4094981db7b6 scsi: mpi3mr: Rework mrioc->bsg_device model to fix warnings 9feb5c4c3f95 scsi: mpi3mr: Add target device related sysfs attributes e51e76edddb1 scsi: mpi3mr: Add shost related sysfs attributes bc7896d31a92 scsi: mpi3mr: Return error if dma_alloc_coherent() fails a25eafd13e5f scsi: mpi3mr: Fix a NULL vs IS_ERR() bug in mpi3mr_bsg_init() 256bd4f23d9c scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR 2dd8389f96d6 scsi: mpi3mr: Hidden drives not removed during soft reset 1aa529d40025 scsi: mpi3mr: Increase I/O timeout value to 60s [Test Plan] 1. Install and boot kernel 2. Run basic I/O tests [Where problems could occur] Moderate to low regression risk for the kernel as most changes are in the driver [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpi3mr_bsg_support_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009436] Re: dkms modules are not built anymore for linux-kvm
** Description changed:
- Since 23th of Feb, some adt test for dkms packages (digimend-dkms is an
example) started to pass even though it should fail.
- Before, the test would fail during build, because CONFIG_USB=n.
+ SRU Justification
- Logs from last time it failed:
-
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/d/digimend-dkms/20230213_171044_032fa@/log.gz
+ [Impact]
- Logs where test passes.
+ Some dkms modules are not built anymore when a retry is triggred from adt
matrix page.
+ It was noticed because these modules previously failed during build (because
a config options is disabled) but now they pass (artificial pass).
+
+ Affected modules:
+ 1. digimend-dkms
+ 2. oss4
+ 3. rtl8812au
+ 4. rtl8812ce
+
+ Looking at digimend-dkms for jammy:linux-kvm, first time the test was correct
(it failed) was when the new kernel was just pushed to proposed and adt testing
was triggered. When a manual retry was done, it passed because build was
ignored.
+ Looking at the artifacts (attached for both cases), ADT_TEST_TRIGGERS differs:
+ 1. when build is triggered, ADT_TEST_TRIGGERS=linux-meta-kvm/5.15.0.1030.26
linux-kvm/5.15.0-1030.35 linux-signed-kvm/5.15.0-1030.35
+ logs
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/d/digimend-dkms/20230213_171044_032fa@/log.gz
+
+ 2. when build is not triggered,
ADT_TEST_TRIGGERS=linux-meta-kvm/5.15.0.1030.26
+ logs:
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/d/digimend-dkms/20230301_110606_17e6d@/log.gz
- Could not reproduce it locally, in a vm, a simple sudo apt install
digimend-dkms will fail during build.
- ```
+
+ Last log line present in both cases is:
+ "I: Testing binary package $pkg".
+
+ Looking at dkms: debian/scripts/dkms-autopkgtest
+
+ After that line and the line where build is triggered the following code:
+ dkms_pkg=$(bash -c ". $dkms_conf > /dev/null; echo \$PACKAGE_NAME"
2>/dev/null)
+ dkms_ver=$(bash -c ". $dkms_conf > /dev/null; echo \$PACKAGE_VERSION"
2>/dev/null)
+
+ for k in /lib/modules/*/build
+ do
+ test -d "$k" || continue
+ kver="${k%/build}"
+ kver="${kver#/lib/modules/}"
+
+ # If any linux-meta is in triggers, only test abistems that
+ # match triggers otherwise continue. This helps integration
+ # with adt-matrix which specifically requests test results
+ # against each individual linux-meta and tracks unique results
+ # per kernel abi.
+ abistem=$(echo $kver | sed 's/-[a-z]*$//')
+ ## abistem is 5.15.0-130
+ case "${ADT_TEST_TRIGGERS-}" in
+ *linux-meta*)
+ case "$ADT_TEST_TRIGGERS" in
+ *"$abistem"*)
+ ;;
+ *)
+ continue
+ ;;
+ esac
+ esac
+
+ echo "I: Trying to build $dkms_pkg/$dkms_ver for $kver"
+
+ What happens here is that it never gets passed the switch case and build
+ is not triggered when ADT_TEST_TRIGGERS consists of linux-meta only,
+ because abistem=-, but meta
+ version=.. Notice the dot instead of the
+ dash.
+
+ This justifies why the module is built when ADT_TEST_TRIGGERS=linux-
+ meta-kvm/5.15.0.1030.26 linux-kvm/5.15.0-1030.35 linux-signed-
+ kvm/5.15.0-1030.35, but not when ADT_TEST_TRIGGERS=linux-meta-
+ kvm/5.15.0.1030.26
+
+ [Fix]
+ Add an extra check for meta_version in that switch case statement.
+
+ [Testcase]
+ 1. Tested locally with ADT_TEST_TRIGGERS=linux-meta.. before fix
+ I: linux-headers-virtual
I: Testing binary package digimend-dkms
- I: Trying to build digimend/10 for 5.15.0-1028-kvm
+ autopkgtest [11:14:45]: test dkms-autopkgtest: ---]
+ autopkgtest [11:14:46]: test dkms-autopkgtest: - - - - - - - - - - results -
- - - - - - - - -
+ dkms-autopkgtest PASS
+ autopkgtest [11:14:47]: summary
+ dkms-autopkgtest PASS
+ qemu-system-x86_64: terminating on signal 15 from pid 15111 (/usr/bin/python3)
+ 2. Tested locally with ADT_TEST_TRIGGERS=linux-meta.. with the fix
+ I: Testing binary package digimend-dkms
+ I: Trying to build digimend/10 for 5.15.0-1029-kvm
Creating symlink /var/lib/dkms/digimend/10/source -> /usr/src/digimend-10
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
- make -j1 KERNELRELEASE=5.15.0-1028-kvm KVERSION=5.15.0-1028-kvm...(bad exit
status: 2)
- Error! Bad return status for module build on kernel: 5.15.0-1028-kvm (x86_64)
+ make -j1 KERNELRELEASE=5.15.0-1029-kvm KVERSION=5.15.0-1029-kvm...(bad exit
status: 2)
+ ERROR (dkms apport): kernel package linux-headers-5.15.0-1029-kvm is not
supported
+ Error! Bad return status for module build on kernel: 5.15.0-1029-kvm (x86_64)
Consult /var/lib/dkms/digimend/10/build/make.log for more information.
- E: digimend/10 failed to build for 5.15.0-1028-kvm
+
[Kernel-packages] [Bug 2009442] Re: glibc fails for bionic-kvm 4.15.0-1136.141
** Changed in: autopkgtest (Ubuntu) Status: Incomplete => Invalid ** Changed in: autopkgtest (Ubuntu Bionic) Status: New => Invalid ** Changed in: autopkgtest (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2009442 Title: glibc fails for bionic-kvm 4.15.0-1136.141 Status in autopkgtest package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: Invalid Status in autopkgtest source package in Bionic: Invalid Status in linux-kvm source package in Bionic: In Progress Status in autopkgtest source package in Focal: Invalid Status in linux-kvm source package in Focal: In Progress Bug description: SRU Justification: [Impact] bionic linux-kvm failure https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/g/glibc/20230213_154436_b51c9@/log.gz From logs FAIL: misc/tst-bz21269 original exit status 1 error: ../sysdeps/unix/sysv/linux/i386/tst-bz21269.c:55: not true: syscall (SYS_modify_ldt, 1, ptr, bytecount) == 0 error: 1 test failures Syscall modify_ldt is not enabled because CONFIG_MODIFY_LDT_SYSCALL=n for bionic-kvm, even though generic and newer versions (even kvm derivativatives) have it enabled. [Fix] Custom patch to bionic-kvm to enable CONFIG_MODIFY_LDT_SYSCALL [Test Plan] Before the fix, autopkgtest for glibc will fail with +-+ | Encountered regressions that don't match expected failures. | +-+ FAIL: misc/tst-bz21269 After the fix, it should pass [Where problems could occur] Regression probability is pretty low, we are adding functionality not previously present but looking at focal,jammy this test was fine. Note: Not sure why this was not enabled for bionic-kvm, even though newer versions of linux kvm has it enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2009442/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011389] Re: vmd may fail to create sysfs entry while `pci_rescan_bus()` called in some other drivers like wwan
While we cannot reproduce this on kernels older than 6.1, we will skip this. ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011389 Title: vmd may fail to create sysfs entry while `pci_rescan_bus()` called in some other drivers like wwan Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] With wwan t7xx driver patched, vmd may fail the probe process because it does not lock properly. [Fix] https://lore.kernel.org/linux- pci/20230313173733.1815277-1-vicamo.y...@canonical.com/T/#u [Test Case] Verify on platforms with FM350 wwan module with prebuilt oem-6.1 or above kernels. No vmd probe error should be found in dmesg. [Where problems could occur] This is the way it should have been done. [Other Info] This is not reproducible with v6.0 or older kernels, so only Lunar and oem-6.1 are nominated for fix. OEM-6.0 patch goes to Gerrit instead. == original bug report == vmd may fail to create sysfs entry while `pci_rescan_bus()` called in some other drivers like wwan. This happens after bug 2002089 re-added pci rescan feature back to wwan t7xx driver to support firmware updates via devlink. t7xx may call `pci_rescan_bus()` with proper locks, but vmd doesn't. sysfs: cannot create duplicate filename '/devices/.../resource0' Call Trace: sysfs_warn_dup.cold+0x17/0x34 sysfs_add_bin_file_mode_ns+0xc0/0xf0 sysfs_create_bin_file+0x6d/0xb0 pci_create_attr+0x117/0x260 pci_create_resource_files+0x6b/0x150 pci_create_sysfs_dev_files+0x18/0x30 pci_bus_add_device+0x30/0x80 pci_bus_add_devices+0x31/0x80 pci_bus_add_devices+0x5b/0x80 vmd_enable_domain.constprop.0+0x6b7/0x880 [vmd] vmd_probe+0x16d/0x193 [vmd] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2011389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011389] Re: vmd may fail to create sysfs entry while `pci_rescan_bus()` called in some other drivers like wwan
SRU: https://lists.ubuntu.com/archives/kernel- team/2023-March/137761.html (lunar, unstable) ** Description changed: + [SRU Justification] + + [Impact] + + With wwan t7xx driver patched, vmd may fail the probe process because it + does not lock properly. + + [Fix] + + https://lore.kernel.org/linux- + pci/20230313173733.1815277-1-vicamo.y...@canonical.com/T/#u + + [Test Case] + + Verify on platforms with FM350 wwan module with prebuilt oem-6.1 or + above kernels. No vmd probe error should be found in dmesg. + + [Where problems could occur] + + This is the way it should have been done. + + [Other Info] + + This is not reproducible with v6.0 or older kernels, so only Lunar and + oem-6.1 are nominated for fix. OEM-6.0 patch goes to Gerrit instead. + + == original bug report == + vmd may fail to create sysfs entry while `pci_rescan_bus()` called in some other drivers like wwan. This happens after bug 2002089 re-added pci rescan feature back to wwan t7xx driver to support firmware updates via devlink. t7xx may call `pci_rescan_bus()` with proper locks, but vmd doesn't. sysfs: cannot create duplicate filename '/devices/.../resource0' Call Trace: sysfs_warn_dup.cold+0x17/0x34 sysfs_add_bin_file_mode_ns+0xc0/0xf0 sysfs_create_bin_file+0x6d/0xb0 pci_create_attr+0x117/0x260 pci_create_resource_files+0x6b/0x150 pci_create_sysfs_dev_files+0x18/0x30 pci_bus_add_device+0x30/0x80 pci_bus_add_devices+0x31/0x80 pci_bus_add_devices+0x5b/0x80 vmd_enable_domain.constprop.0+0x6b7/0x880 [vmd] vmd_probe+0x16d/0x193 [vmd] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011389 Title: vmd may fail to create sysfs entry while `pci_rescan_bus()` called in some other drivers like wwan Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] With wwan t7xx driver patched, vmd may fail the probe process because it does not lock properly. [Fix] https://lore.kernel.org/linux- pci/20230313173733.1815277-1-vicamo.y...@canonical.com/T/#u [Test Case] Verify on platforms with FM350 wwan module with prebuilt oem-6.1 or above kernels. No vmd probe error should be found in dmesg. [Where problems could occur] This is the way it should have been done. [Other Info] This is not reproducible with v6.0 or older kernels, so only Lunar and oem-6.1 are nominated for fix. OEM-6.0 patch goes to Gerrit instead. == original bug report == vmd may fail to create sysfs entry while `pci_rescan_bus()` called in some other drivers like wwan. This happens after bug 2002089 re-added pci rescan feature back to wwan t7xx driver to support firmware updates via devlink. t7xx may call `pci_rescan_bus()` with proper locks, but vmd doesn't. sysfs: cannot create duplicate filename '/devices/.../resource0' Call Trace: sysfs_warn_dup.cold+0x17/0x34 sysfs_add_bin_file_mode_ns+0xc0/0xf0 sysfs_create_bin_file+0x6d/0xb0 pci_create_attr+0x117/0x260 pci_create_resource_files+0x6b/0x150 pci_create_sysfs_dev_files+0x18/0x30 pci_bus_add_device+0x30/0x80 pci_bus_add_devices+0x31/0x80 pci_bus_add_devices+0x5b/0x80 vmd_enable_domain.constprop.0+0x6b7/0x880 [vmd] vmd_probe+0x16d/0x193 [vmd] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2011389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007668] Re: Intel 12th gen: Noisy screen corruption during cursor movement, and whole screen freezes, in 5.19 kernels
I can confirm that disabling PSR fixes the problem on my laptop (see bug #2008053). Thanks a lot to @vanvugt for suggesting the workaround. When there is a real fix for this issue in Ubuntu 22.04, I will try to re- enable PSR and check if it works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007668 Title: Intel 12th gen: Noisy screen corruption during cursor movement, and whole screen freezes, in 5.19 kernels Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: This always happens when the cursor sweeps over a height range (approximately 960px ~ 990px from the top). Even when watching a video, the top of the screen sometimes glitches. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 17 16:24:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:46aa] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b14] InstallationDate: Installed on 2022-08-13 (187 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=3ba28059-7aea-46a5-bf4e-44dd0203b83d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 02GGG1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn02GGG1:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007668/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009442] Re: glibc fails for bionic-kvm 4.15.0-1136.141
** Changed in: linux-kvm (Ubuntu) Status: New => Invalid ** Changed in: linux-kvm (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-kvm (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-kvm (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux-kvm (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2009442 Title: glibc fails for bionic-kvm 4.15.0-1136.141 Status in autopkgtest package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: Invalid Status in autopkgtest source package in Bionic: New Status in linux-kvm source package in Bionic: In Progress Status in autopkgtest source package in Focal: New Status in linux-kvm source package in Focal: In Progress Bug description: SRU Justification: [Impact] bionic linux-kvm failure https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/g/glibc/20230213_154436_b51c9@/log.gz From logs FAIL: misc/tst-bz21269 original exit status 1 error: ../sysdeps/unix/sysv/linux/i386/tst-bz21269.c:55: not true: syscall (SYS_modify_ldt, 1, ptr, bytecount) == 0 error: 1 test failures Syscall modify_ldt is not enabled because CONFIG_MODIFY_LDT_SYSCALL=n for bionic-kvm, even though generic and newer versions (even kvm derivativatives) have it enabled. [Fix] Custom patch to bionic-kvm to enable CONFIG_MODIFY_LDT_SYSCALL [Test Plan] Before the fix, autopkgtest for glibc will fail with +-+ | Encountered regressions that don't match expected failures. | +-+ FAIL: misc/tst-bz21269 After the fix, it should pass [Where problems could occur] Regression probability is pretty low, we are adding functionality not previously present but looking at focal,jammy this test was fine. Note: Not sure why this was not enabled for bionic-kvm, even though newer versions of linux kvm has it enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2009442/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008085] Re: net:veth.sh in ubuntu_kernel_selftests hang with J-intel-iotg (BUG: unable to handle page fault)
** Changed in: linux-intel-iotg (Ubuntu) Status: New => Invalid ** Changed in: linux-intel-iotg (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-intel-iotg (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2008085 Title: net:veth.sh in ubuntu_kernel_selftests hang with J-intel-iotg (BUG: unable to handle page fault) Status in ubuntu-kernel-tests: New Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: In Progress Bug description: Issue found on node "onibi" with J-intel-iotg 5.15.0-1026.31 this cycle. The veth.sh test in net category will hang and timeout, causing test report incomplete. I can see some traces in dmesg with manual test. ubuntu@onibi:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./veth.sh default - gro flag ok - peer gro flag ok - tso flag ok - peer tso flag ok - aggregationok - aggregation with TSO off ok with gro on - gro flag ok - peer gro flag ok - tso flag ok - peer tso flag ok - aggregation with TSO off ok default channels ok with gro enabled on link down - gro flag ok - peer gro flag ok - tso flag ok - peer tso flag ok - aggregation with TSO off ok setting tx channels ok setting both rx and tx channels ok bad setting: combined channels ok setting invalid channels nr fail rx:3:3 tx:3:5 combined:n/a:n/a bad setting: XDP with RX nr less than TX ok (hangs here) dmesg output: [ 547.520923] BUG: unable to handle page fault for address: b7380001 [ 547.520999] #PF: supervisor write access in kernel mode [ 547.521045] #PF: error_code(0x0002) - not-present page [ 547.521089] PGD 10067 P4D 10067 PUD 0 [ 547.521133] Oops: 0002 [#1] SMP PTI [ 547.521168] CPU: 1 PID: 1559 Comm: ip Not tainted 5.15.0-1026-intel-iotg #31-Ubuntu [ 547.521233] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.8.2 08/17/2011 [ 547.521293] RIP: 0010:veth_xdp+0x18f/0x1e0 [veth] [ 547.521342] Code: ff 41 89 9d 1c 01 00 00 49 21 85 e8 00 00 00 e9 74 ff ff ff 48 c7 c7 80 e3 b0 c0 e8 2b 3b 06 c1 b8 e4 ff ff ff 4d 85 ff 74 85 <49> c7 07 80 e3 b0 c0 e9 79 ff ff ff 48 c7 c7 20 e4 b0 c0 e8 09 3b [ 547.521488] RSP: 0018:b738c254f420 EFLAGS: 00010282 [ 547.521535] RAX: ffe4 RBX: 0db2 RCX: b738c254fb20 [ 547.521594] RDX: c0b0bf90 RSI: b738c254f468 RDI: c0b0e380 [ 547.521653] RBP: b738c254f450 R08: 0001 R09: b738c0081000 [ 547.521711] R10: R11: R12: 8c65ced9 [ 547.521769] R13: 8c65c12f6000 R14: R15: b7380001 [ 547.521828] FS: 7faa028b3b80() GS:8c66f764() knlGS: [ 547.521895] CS: 0010 DS: ES: CR0: 80050033 [ 547.521943] CR2: b7380001 CR3: 00010f068000 CR4: 06e0 [ 547.522004] Call Trace: [ 547.522029] [ 547.522052] ? veth_open+0x90/0x90 [veth] [ 547.522094] dev_xdp_install+0x66/0xf0 [ 547.522135] dev_xdp_attach+0x1fc/0x590 [ 547.522171] ? __bpf_prog_get+0x1f/0xe0 [ 547.522212] dev_change_xdp_fd+0x200/0x240 [ 547.522252] do_setlink+0xba2/0xc70 [ 547.522288] ? dev_get_alias+0x35/0x50 [ 547.522326] __rtnl_newlink+0x61e/0xa20 [ 547.522363] ? security_sock_rcv_skb+0x2f/0x50 [ 547.522406] ? skb_queue_tail+0x48/0x60 [ 547.522444] ? sock_def_readable+0x4b/0x80 [ 547.522485] ? __netlink_sendskb+0x62/0x80 [ 547.522528] ? netlink_unicast+0x2fb/0x340 [ 547.522566] ? rtnl_getlink+0x398/0x420 [ 547.522611] ? kmem_cache_alloc_trace+0x17e/0x2a0 [ 547.522657] rtnl_newlink+0x49/0x70 [ 547.522692] rtnetlink_rcv_msg+0x15d/0x400 [ 547.522731] ? rtnl_calcit.isra.0+0x130/0x130 [ 547.524524] netlink_rcv_skb+0x56/0x100 [ 547.526314]
[Kernel-packages] [Bug 2009436] Re: dkms modules are not built anymore for linux-kvm
I created a merge request to push the fix to dkms when ADT_TRIGGERS=linux-meta
only.
I will update the description with details from my previous comment.
** Also affects: dkms (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/2009436
Title:
dkms modules are not built anymore for linux-kvm
Status in autopkgtest package in Ubuntu:
Incomplete
Status in dkms package in Ubuntu:
New
Status in linux-kvm package in Ubuntu:
New
Bug description:
Since 23th of Feb, some adt test for dkms packages (digimend-dkms is an
example) started to pass even though it should fail.
Before, the test would fail during build, because CONFIG_USB=n.
Logs from last time it failed:
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/d/digimend-dkms/20230213_171044_032fa@/log.gz
Logs where test passes.
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/d/digimend-dkms/20230301_110606_17e6d@/log.gz
Could not reproduce it locally, in a vm, a simple sudo apt install
digimend-dkms will fail during build.
```
I: Testing binary package digimend-dkms
I: Trying to build digimend/10 for 5.15.0-1028-kvm
Creating symlink /var/lib/dkms/digimend/10/source -> /usr/src/digimend-10
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
make -j1 KERNELRELEASE=5.15.0-1028-kvm KVERSION=5.15.0-1028-kvm...(bad exit
status: 2)
Error! Bad return status for module build on kernel: 5.15.0-1028-kvm (x86_64)
Consult /var/lib/dkms/digimend/10/build/make.log for more information.
E: digimend/10 failed to build for 5.15.0-1028-kvm
== /var/lib/dkms/digimend/10/build/make.log ==
DKMS make.log for digimend-10 for kernel 5.15.0-1028-kvm (x86_64)
Sat Jan 28 00:05:19 UTC 2023
make -C /lib/modules/5.15.0-1028-kvm/build M=/var/lib/dkms/digimend/10/build
modules
make[1]: Entering directory '/usr/src/linux-headers-5.15.0-1028-kvm'
CC [M] /var/lib/dkms/digimend/10/build/hid-kye.o
CC [M] /var/lib/dkms/digimend/10/build/hid-uclogic-core.o
CC [M] /var/lib/dkms/digimend/10/build/hid-uclogic-rdesc.o
CC [M] /var/lib/dkms/digimend/10/build/hid-uclogic-params.o
/var/lib/dkms/digimend/10/build/hid-uclogic-params.c: In function
‘uclogic_params_init’:
/var/lib/dkms/digimend/10/build/hid-uclogic-params.c:1147:20: warning: this
statement may fall through [-Wimplicit-fallthrough=]
1147 | if (bNumInterfaces != 3) {
|^
/var/lib/dkms/digimend/10/build/hid-uclogic-params.c:1165:9: note: here
1165 | case VID_PID(USB_VENDOR_ID_HUION,
| ^~~~
LD [M] /var/lib/dkms/digimend/10/build/hid-uclogic.o
CC [M] /var/lib/dkms/digimend/10/build/hid-polostar.o
CC [M] /var/lib/dkms/digimend/10/build/hid-viewsonic.o
MODPOST /var/lib/dkms/digimend/10/build/Module.symvers
ERROR: modpost: "usb_string" [/var/lib/dkms/digimend/10/build/hid-uclogic.ko]
undefined!
ERROR: modpost: "usb_control_msg"
[/var/lib/dkms/digimend/10/build/hid-uclogic.ko] undefined!
ERROR: modpost: "usb_hid_driver"
[/var/lib/dkms/digimend/10/build/hid-uclogic.ko] undefined!
make[2]: *** [scripts/Makefile.modpost:133:
/var/lib/dkms/digimend/10/build/Module.symvers] Error 1
make[2]: *** Deleting file '/var/lib/dkms/digimend/10/build/Module.symvers'
make[1]: *** [Makefile:1819: modules] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.15.0-1028-kvm'
make: *** [Makefile:25: modules] Error 2
./digimend/10/build/make.log
autopkgtest [00:05:23]: test dkms-autopkgtest: ---]
dkms-autopkgtest FAIL non-zero exit status 1
autopkgtest [00:05:24]: test dkms-autopkgtest: - - - - - - - - - - results -
- - - - - - - - -
autopkgtest [00:05:24]: summary
dkms-autopkgtest FAIL non-zero exit status 1
```
Test fails with exitcode 1, and autopkgtest return 4 as exitcode.
This happens in multiple modules (oss4, rtl8812au), they are supposed to fail
because a config is not enabled, but now they pass (superficially). This may
affect other derivatives as well that have some config options disabled.
To be investigated.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2009436/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009436] Re: dkms modules are not built anymore for linux-kvm
** Merge proposal linked:
https://code.launchpad.net/~roxanan/ubuntu/+source/dkms/+git/dkms/+merge/438958
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/2009436
Title:
dkms modules are not built anymore for linux-kvm
Status in autopkgtest package in Ubuntu:
Incomplete
Status in dkms package in Ubuntu:
New
Status in linux-kvm package in Ubuntu:
New
Bug description:
Since 23th of Feb, some adt test for dkms packages (digimend-dkms is an
example) started to pass even though it should fail.
Before, the test would fail during build, because CONFIG_USB=n.
Logs from last time it failed:
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/d/digimend-dkms/20230213_171044_032fa@/log.gz
Logs where test passes.
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/d/digimend-dkms/20230301_110606_17e6d@/log.gz
Could not reproduce it locally, in a vm, a simple sudo apt install
digimend-dkms will fail during build.
```
I: Testing binary package digimend-dkms
I: Trying to build digimend/10 for 5.15.0-1028-kvm
Creating symlink /var/lib/dkms/digimend/10/source -> /usr/src/digimend-10
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
make -j1 KERNELRELEASE=5.15.0-1028-kvm KVERSION=5.15.0-1028-kvm...(bad exit
status: 2)
Error! Bad return status for module build on kernel: 5.15.0-1028-kvm (x86_64)
Consult /var/lib/dkms/digimend/10/build/make.log for more information.
E: digimend/10 failed to build for 5.15.0-1028-kvm
== /var/lib/dkms/digimend/10/build/make.log ==
DKMS make.log for digimend-10 for kernel 5.15.0-1028-kvm (x86_64)
Sat Jan 28 00:05:19 UTC 2023
make -C /lib/modules/5.15.0-1028-kvm/build M=/var/lib/dkms/digimend/10/build
modules
make[1]: Entering directory '/usr/src/linux-headers-5.15.0-1028-kvm'
CC [M] /var/lib/dkms/digimend/10/build/hid-kye.o
CC [M] /var/lib/dkms/digimend/10/build/hid-uclogic-core.o
CC [M] /var/lib/dkms/digimend/10/build/hid-uclogic-rdesc.o
CC [M] /var/lib/dkms/digimend/10/build/hid-uclogic-params.o
/var/lib/dkms/digimend/10/build/hid-uclogic-params.c: In function
‘uclogic_params_init’:
/var/lib/dkms/digimend/10/build/hid-uclogic-params.c:1147:20: warning: this
statement may fall through [-Wimplicit-fallthrough=]
1147 | if (bNumInterfaces != 3) {
|^
/var/lib/dkms/digimend/10/build/hid-uclogic-params.c:1165:9: note: here
1165 | case VID_PID(USB_VENDOR_ID_HUION,
| ^~~~
LD [M] /var/lib/dkms/digimend/10/build/hid-uclogic.o
CC [M] /var/lib/dkms/digimend/10/build/hid-polostar.o
CC [M] /var/lib/dkms/digimend/10/build/hid-viewsonic.o
MODPOST /var/lib/dkms/digimend/10/build/Module.symvers
ERROR: modpost: "usb_string" [/var/lib/dkms/digimend/10/build/hid-uclogic.ko]
undefined!
ERROR: modpost: "usb_control_msg"
[/var/lib/dkms/digimend/10/build/hid-uclogic.ko] undefined!
ERROR: modpost: "usb_hid_driver"
[/var/lib/dkms/digimend/10/build/hid-uclogic.ko] undefined!
make[2]: *** [scripts/Makefile.modpost:133:
/var/lib/dkms/digimend/10/build/Module.symvers] Error 1
make[2]: *** Deleting file '/var/lib/dkms/digimend/10/build/Module.symvers'
make[1]: *** [Makefile:1819: modules] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.15.0-1028-kvm'
make: *** [Makefile:25: modules] Error 2
./digimend/10/build/make.log
autopkgtest [00:05:23]: test dkms-autopkgtest: ---]
dkms-autopkgtest FAIL non-zero exit status 1
autopkgtest [00:05:24]: test dkms-autopkgtest: - - - - - - - - - - results -
- - - - - - - - -
autopkgtest [00:05:24]: summary
dkms-autopkgtest FAIL non-zero exit status 1
```
Test fails with exitcode 1, and autopkgtest return 4 as exitcode.
This happens in multiple modules (oss4, rtl8812au), they are supposed to fail
because a config is not enabled, but now they pass (superficially). This may
affect other derivatives as well that have some config options disabled.
To be investigated.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2009436/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011520] Re: Bluetooth: btusb: Add module firmware information for MT7622 and MT7961
** Changed in: linux-intel-iotg (Ubuntu) Status: New => Invalid ** Changed in: linux-intel-iotg (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-intel-iotg (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2011520 Title: Bluetooth: btusb: Add module firmware information for MT7622 and MT7961 Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: In Progress Bug description: [ Impact ] * Export the required module firmware information of MT7622 and M7961 used by modinfo. [ Test Plan ] * execute the following command, you should be able to see the firmware information $ modinfo btusb.ko ... firmware: mediatek/mt7668pr2h.bin firmware: mediatek/mt7663pr2h.bin srcversion: 93D172DBD10743ABF2E68FD ... mediatek/mt7622pr2h.bin and mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin are missing [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2011520/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973098] Re: [i915] Intermittent freezing and LSPCON init failed kernel messages
Same issue here on System-manufacturer : LENOVO System-product-name : 20SUS51107 System-version : ThinkPad P15 Gen 1 Bios-release-date : 12/14/2022 Bios-version : N30ET49W (1.32) with 5.15.0-67-generic #74-22.04.1-Ubuntu and 5.19.0-35-generic #36~22.04.1-Ubuntu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1973098 Title: [i915] Intermittent freezing and LSPCON init failed kernel messages Status in linux package in Ubuntu: Confirmed Status in linux-signed-oem-5.14 package in Ubuntu: Confirmed Bug description: Hardware: Lenovo ThinkPad model 20ST0055AU Boot messages show: [6.397804] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [6.397901] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on minor 0 During normal operation there will intermittently be a freeze for a second or two and then more of these messages display in the kernel logs: [ 505.487006] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 505.487072] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D [ 506.747930] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 506.748018] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D The system will then become operational again. The system is still usable, but it is annoying. I've switched onto this OEM kernel from the generic kernel (5.13), as I had other problems with 5.13 regarding external displays not coming back after idle timeouts. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1036-oem 5.14.0-1036.40 ProcVersionSignature: Ubuntu 5.14.0-1036.40-oem 5.14.21 Uname: Linux 5.14.0-1036-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 12 10:29:31 2022 InstallationDate: Installed on 2021-05-05 (371 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011521] Re: USB: serial: option: add Quectel EM05CN modem
** Changed in: linux-intel-iotg (Ubuntu) Status: New => Invalid ** Changed in: linux-intel-iotg (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-intel-iotg (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2011521 Title: USB: serial: option: add Quectel EM05CN modem Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: In Progress Bug description: [ Impact ] * add Quectel EM05CN modem id [ Test Plan ] * testing on the system with this modem [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2011521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011575] Re: [amdgpu] Cursor used during log in after boot still on screen after log in on desktop
Yes good point. So this can't be the first issue, but it is generally a known recurring issue for amdgpu only. Most recently reported in https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6470 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/2011575 Title: [amdgpu] Cursor used during log in after boot still on screen after log in on desktop Status in linux-oem-5.14 package in Ubuntu: Won't Fix Bug description: After booting up my laptop and logging in, the cursor that is used during the log in phase just freezes on the spot it last was after pressing the enter key to log in and stays there the whole usage time. It only disappears when I restart or shut down the laptop. It doesn't impair the usage of the desktop cursor, but stays on the screen, in front of every open window. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1058.66-oem 5.14.21 Uname: Linux 5.14.0-1058-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 14 13:53:12 2023 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1681] (rev d1) (prog-if 00 [VGA controller]) MachineType: LENOVO 21CKCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1058-oem root=UUID=5579c05a-7872-4f21-8412-a225bea53a66 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2022 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET62W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CKCTO1WW dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.25:svnLENOVO:pn21CKCTO1WW:pvrThinkPadP16sGen1:rvnLENOVO:rn21CKCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CK_BU_Think_FM_ThinkPadP16sGen1: dmi.product.family: ThinkPad P16s Gen 1 dmi.product.name: 21CKCTO1WW dmi.product.sku: LENOVO_MT_21CK_BU_Think_FM_ThinkPad P16s Gen 1 dmi.product.version: ThinkPad P16s Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/2011575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011575] Re: [amdgpu] Cursor used during log in after boot still on screen after log in on desktop
and if the fix landed in 5.9.0, then surely 5.14 has it? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/2011575 Title: [amdgpu] Cursor used during log in after boot still on screen after log in on desktop Status in linux-oem-5.14 package in Ubuntu: Won't Fix Bug description: After booting up my laptop and logging in, the cursor that is used during the log in phase just freezes on the spot it last was after pressing the enter key to log in and stays there the whole usage time. It only disappears when I restart or shut down the laptop. It doesn't impair the usage of the desktop cursor, but stays on the screen, in front of every open window. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1058.66-oem 5.14.21 Uname: Linux 5.14.0-1058-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 14 13:53:12 2023 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1681] (rev d1) (prog-if 00 [VGA controller]) MachineType: LENOVO 21CKCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1058-oem root=UUID=5579c05a-7872-4f21-8412-a225bea53a66 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2022 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET62W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CKCTO1WW dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.25:svnLENOVO:pn21CKCTO1WW:pvrThinkPadP16sGen1:rvnLENOVO:rn21CKCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CK_BU_Think_FM_ThinkPadP16sGen1: dmi.product.family: ThinkPad P16s Gen 1 dmi.product.name: 21CKCTO1WW dmi.product.sku: LENOVO_MT_21CK_BU_Think_FM_ThinkPad P16s Gen 1 dmi.product.version: ThinkPad P16s Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/2011575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011575] Re: [amdgpu] Cursor used during log in after boot still on screen after log in on desktop
it's also a wontfix at this point, as it'll migrate to hwe-5.15 soon ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/2011575 Title: [amdgpu] Cursor used during log in after boot still on screen after log in on desktop Status in linux-oem-5.14 package in Ubuntu: Won't Fix Bug description: After booting up my laptop and logging in, the cursor that is used during the log in phase just freezes on the spot it last was after pressing the enter key to log in and stays there the whole usage time. It only disappears when I restart or shut down the laptop. It doesn't impair the usage of the desktop cursor, but stays on the screen, in front of every open window. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1058.66-oem 5.14.21 Uname: Linux 5.14.0-1058-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 14 13:53:12 2023 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1681] (rev d1) (prog-if 00 [VGA controller]) MachineType: LENOVO 21CKCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1058-oem root=UUID=5579c05a-7872-4f21-8412-a225bea53a66 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2022 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET62W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CKCTO1WW dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.25:svnLENOVO:pn21CKCTO1WW:pvrThinkPadP16sGen1:rvnLENOVO:rn21CKCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CK_BU_Think_FM_ThinkPadP16sGen1: dmi.product.family: ThinkPad P16s Gen 1 dmi.product.name: 21CKCTO1WW dmi.product.sku: LENOVO_MT_21CK_BU_Think_FM_ThinkPad P16s Gen 1 dmi.product.version: ThinkPad P16s Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/2011575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011592] Re: First, WiFi network disconnects automatically, then no WiFi networks are visible in the scanning list. Second, WiFi network connects normally, but there is no inter
[ 281.956392] [ cut here ] [ 281.956396] failed to read DBI register, addr=0x0719 [ 281.956428] WARNING: CPU: 1 PID: 738 at drivers/net/wireless/realtek/rtw88/pci.c:1311 rtw_dbi_read8.constprop.0+0xb4/0xd0 [rtw88_pci] [ 281.956437] Modules linked in: ccm rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) cmac algif_hash algif_skcipher af_alg bnep snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp uvcvideo btusb videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 btrtl snd_sof videobuf2_common btbcm snd_sof_utils btintel snd_hda_codec_hdmi snd_soc_hdac_hda snd_hda_ext_core btmtk videodev bluetooth mc ecdh_generic ecc snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_compress ac97_bus snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_pcm_dmaengine intel_tcc_cooling x86_pkg_temp_thermal intel_powerclamp snd_hda_intel coretemp snd_intel_dspcfg snd_intel_sdw_acpi kvm_intel snd_hda_codec kvm snd_hda_core snd_hwdep snd_pcm intel_rapl_msr crct10dif_pclmul mei_hdcp snd_seq_midi ghash_clmulni_intel mei_pxp snd_seq_midi_event aesni_intel rtw88_8822be crypto_simd snd_rawmidi cryptd [ 281.956505] rtw88_8822b rtw88_pci rapl binfmt_misc joydev rtw88_core intel_cstate i915 snd_seq nls_iso8859_1 mac80211 input_leds serio_raw intel_wmi_thunderbolt wmi_bmof drm_buddy cfg80211 snd_seq_device ttm snd_timer processor_thermal_device_pci_legacy libarc4 snd drm_display_helper processor_thermal_device processor_thermal_rfim cec processor_thermal_mbox processor_thermal_rapl rc_core soundcore drm_kms_helper mei_me i2c_algo_bit fb_sys_fops intel_rapl_common syscopyarea mei sysfillrect intel_soc_dts_iosf intel_pch_thermal sysimgblt hid_multitouch ideapad_laptop sparse_keymap platform_profile int3403_thermal int340x_thermal_zone mac_hid acpi_pad int3400_thermal soc_button_array acpi_thermal_rel sch_fq_codel msr parport_pc ppdev lp parport ramoops pstore_blk reed_solomon drm pstore_zone efi_pstore ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj usbhid hid_generic rtsx_pci_sdmmc crc32_pclmul nvme i2c_i801 i2c_smbus nvme_core ahci libahci intel_lpss_pci i2c_hid_acpi [ 281.956582] intel_lpss i2c_hid rtsx_pci idma64 hid xhci_pci xhci_pci_renesas wmi pinctrl_cannonlake video [ 281.956593] CPU: 1 PID: 738 Comm: wpa_supplicant Tainted: G OE 5.19.0-35-generic #36~22.04.1-Ubuntu [ 281.956597] Hardware name: LENOVO 81N7/LNVNB161216, BIOS ALCN33WW(V2.10) 06/23/2021 [ 281.956599] RIP: 0010:rtw_dbi_read8.constprop.0+0xb4/0xd0 [rtw88_pci] [ 281.956603] Code: 1f 00 5b 41 5c 41 88 45 00 31 c0 41 5d 5d 31 d2 89 d6 89 d7 c3 cc cc cc cc be 19 07 00 00 48 c7 c7 68 94 4a c0 e8 e4 7d fa f0 <0f> 0b b8 fb ff ff ff 5b 41 5c 41 5d 5d 31 d2 89 d6 89 d7 c3 cc cc [ 281.956606] RSP: 0018:ab66809c7760 EFLAGS: 00010246 [ 281.956609] RAX: RBX: RCX: [ 281.956611] RDX: RSI: RDI: [ 281.956613] RBP: ab66809c7778 R08: R09: [ 281.956615] R10: R11: R12: 9255865120e0 [ 281.956616] R13: ab66809c778f R14: R15: [ 281.956618] FS: 7ffb33092800() GS:9259dc68() knlGS: [ 281.956621] CS: 0010 DS: ES: CR0: 80050033 [ 281.956623] CR2: 55ce33a92b14 CR3: 00010916a004 CR4: 003706e0 [ 281.956626] Call Trace: [ 281.956627] [ 281.956631] rtw_pci_link_ps.part.0+0xa7/0xe0 [rtw88_pci] [ 281.956637] rtw_pci_link_ps+0x1b/0x30 [rtw88_pci] [ 281.956641] rtw_leave_lps_core+0x3e/0x180 [rtw88_core] [ 281.956660] rtw_leave_lps+0x4a/0x90 [rtw88_core] [ 281.956674] rtw_core_scan_start+0x21/0xd0 [rtw88_core] [ 281.956687] rtw_ops_sw_scan_start+0x3d/0x60 [rtw88_core] [ 281.956699] __ieee80211_start_scan+0x3c0/0x6f0 [mac80211] [ 281.956754] ieee80211_request_scan+0x30/0x60 [mac80211] [ 281.956798] ieee80211_scan+0x66/0x110 [mac80211] [ 281.956848] rdev_scan+0x2a/0xe0 [cfg80211] [ 281.956897] cfg80211_scan+0x101/0x140 [cfg80211] [ 281.956938] nl80211_trigger_scan+0x42e/0x8d0 [cfg80211] [ 281.956986] genl_family_rcv_msg_doit+0xe4/0x160 [ 281.957018] genl_rcv_msg+0xe2/0x1f0 [ 281.957021] ? nl80211_send_scan_start+0xc0/0xc0 [cfg80211] [ 281.957067] ? genl_get_cmd+0x110/0x110 [ 281.957071] netlink_rcv_skb+0x53/0x110 [ 281.957075] genl_rcv+0x29/0x50 [ 281.957078] netlink_unicast+0x241/0x360 [ 281.957082] netlink_sendmsg+0x25d/0x4f0 [ 281.957086] sock_sendmsg+0x6c/0x80 [ 281.957090] sys_sendmsg+0x264/0x2a0 [ 281.957093] ? import_iovec+0x1b/0x30 [ 281.957096] ? sendmsg_copy_msghdr+0x8d/0xb0 [ 281.957101] ___sys_sendmsg+0x81/0xd0 [ 281.957105] ? sock_getsockopt+0x114/0xe30 [ 281.957110] ? begin_current_label_crit_section+0x2b/0xe0
