[Kernel-packages] [Bug 1993532] Re: [i915] Unable to see second monitor in 5.15.0-52 (but 5.15.0-50 works)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993532 Title: [i915] Unable to see second monitor in 5.15.0-52 (but 5.15.0-50 works) Status in linux package in Ubuntu: Expired Bug description: I have a second monitor plugged into this laptop. Under 5.15.0-52-generic this monitor isn't seen by Ubuntu, whether via a thunderbolt dongle or directly into the HDMI port. When I boot it back into 5.15.0-50-generic it works just fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robin 4304 F pulseaudio /dev/snd/controlC0: robin 4304 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 14:53:25 2022 InstallationDate: Installed on 2022-03-17 (216 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) MachineType: Dell Inc. Latitude 7320 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.2 dmi.board.name: 07MHG4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.2:bd06/15/2022:br1.17:svnDellInc.:pnLatitude7320:pvr:rvnDellInc.:rn07MHG4:rvrA02:cvnDellInc.:ct10:cvr:sku0A34: dmi.product.family: Latitude dmi.product.name: Latitude 7320 dmi.product.sku: 0A34 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002933] Re: [L860R+ Linux][Dell][dell-bto-jammy-jellyfish-arcanine-X56-20221213-16.iso] The test notebook cannot enter into sleep state after clicking the "suspend" and waking
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002933 Title: [L860R+ Linux][Dell][dell-bto-jammy-jellyfish- arcanine-X56-20221213-16.iso] The test notebook cannot enter into sleep state after clicking the "suspend" and waking up soon Status in linux package in Ubuntu: Expired Bug description: We update the dell-bto-jammy-jellyfish-arcanine-X56-20221213-16.iso image to test notebook and use it to test the suspend function. When we click the suspend menu, then the PC screen will goto black, but it will recover quickly by itself and cannot enter into sleep statu. The attachment is the dmesg log. The log shows the issue maybe related with e1000e device. Please help to check this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002933/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011854] Re: cmos_interrupt not getting called
The breaking commit is
f2a7f3238777 ("rtc: rtc-cmos: Do not check ACPI_FADT_LOW_POWER_S0")
Reverting this commit restores the expected AIE and UIE behavior.
** Description changed:
The ubuntu_ltp_kernel_misc rtc01 test case has exposed a possible
regression of the RTC cmos driver on certain Oracle clouds.
This was observed on jammy:linux-oracle-5.15.0-1031.37.
- VM.DenseIO2.8
- VM.Standard2.1
rtc01 0 TINFO : RTC READ TEST:
rtc01 1 TPASS : RTC READ TEST Passed
rtc01 0 TINFO : Current RTC date/time is 16-3-2023, 17:36:04.
rtc01 0 TINFO : RTC ALARM TEST :
rtc01 0 TINFO : Alarm time set to 17:36:09.
rtc01 0 TINFO : Waiting 5 seconds for the alarm...
rtc01 2 TFAIL : rtc01.c:151: Timed out waiting for the alarm
rtc01 0 TINFO : RTC UPDATE INTERRUPTS TEST :
rtc01 0 TINFO : Waiting for 5 update interrupts...
rtc01 3 TFAIL : rtc01.c:208: Timed out waiting for the update
interrupt
rtc01 0 TINFO : RTC Tests Done!
Notice that we successfully enable RTC_AIE_ON, unlike
VM.Standard.A1.Flex-4c.8m which does not support it. I confirmed with
bpftrace on -1029 that we see the cmos interrupt (part of ltp
read_alarm_test)
sudo bpftrace -e 'kprobe:cmos_interrupt { printf("%s\n", probe) }'
Attaching 1 probe...
kprobe:cmos_interrupt
- On -1031 no interrupt is detected. I think this might be caused by
-
- 017314318ad4 ("rtc: cmos: Call cmos_wake_setup() from cmos_do_probe()")
+ On -1031 no interrupt is detected for both the alarm and update tests.
--
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/2011854
Title:
cmos_interrupt not getting called
Status in linux-oracle package in Ubuntu:
New
Bug description:
The ubuntu_ltp_kernel_misc rtc01 test case has exposed a possible
regression of the RTC cmos driver on certain Oracle clouds.
This was observed on jammy:linux-oracle-5.15.0-1031.37.
- VM.DenseIO2.8
- VM.Standard2.1
rtc01 0 TINFO : RTC READ TEST:
rtc01 1 TPASS : RTC READ TEST Passed
rtc01 0 TINFO : Current RTC date/time is 16-3-2023, 17:36:04.
rtc01 0 TINFO : RTC ALARM TEST :
rtc01 0 TINFO : Alarm time set to 17:36:09.
rtc01 0 TINFO : Waiting 5 seconds for the alarm...
rtc01 2 TFAIL : rtc01.c:151: Timed out waiting for the alarm
rtc01 0 TINFO : RTC UPDATE INTERRUPTS TEST :
rtc01 0 TINFO : Waiting for 5 update interrupts...
rtc01 3 TFAIL : rtc01.c:208: Timed out waiting for the update
interrupt
rtc01 0 TINFO : RTC Tests Done!
Notice that we successfully enable RTC_AIE_ON, unlike
VM.Standard.A1.Flex-4c.8m which does not support it. I confirmed with
bpftrace on -1029 that we see the cmos interrupt (part of ltp
read_alarm_test)
sudo bpftrace -e 'kprobe:cmos_interrupt { printf("%s\n", probe) }'
Attaching 1 probe...
kprobe:cmos_interrupt
On -1031 no interrupt is detected for both the alarm and update tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2011854/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006458] Re: Frequent wakeups on HP Pro x360 435 13.3 inch G9 using Qualcomm FastConnect 6900
** Description changed: [Impact] To whom it may concern: I was experiencing frequent wake-ups from s0i3x on a HP Pro 435 G9 convertible [1] using the Qualcomm FastConnect 6900 Soc [2]. The issue is related to FW revision WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9 that comes bundled with Ubuntu 22.10. It appears the SoC increasingly triggering wake-ups after being suspended for approx. 4 hrs. Read the full story at [4]. The solution is to upgrade SoC firmware to rev WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23/ [3] Best regards,Carsten [1] https://support.hp.com/us-en/product/hp-pro-x360-435-13.3-inch-g9-notebook-pc/2101144107/document/ish_6053745-6053789-16 [2] https://www.qualcomm.com/products/technology/wi-fi/fastconnect/fastconnect-6900 [3] https://github.com/kvalo/ath11k-firmware/tree/master/WCN6855/hw2.0/1.1/WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23 [4] https://gitlab.freedesktop.org/drm/amd/-/issues/2377 [Fix] Upgrade firmware, as mentioned above. [Test case] - TBD. + Verify WiFi functionality on WCN6855 works and that unplugging power + cord during suspend doesn't wake system. [Where Problems might occur] It's firmware, what could possibly go wrong? If so, connectivity issues wit ath11k based NICs. ** Changed in: linux-firmware (Ubuntu Kinetic) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2006458 Title: Frequent wakeups on HP Pro x360 435 13.3 inch G9 using Qualcomm FastConnect 6900 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Kinetic: Fix Committed Status in linux-firmware source package in Lunar: Fix Released Bug description: [Impact] To whom it may concern: I was experiencing frequent wake-ups from s0i3x on a HP Pro 435 G9 convertible [1] using the Qualcomm FastConnect 6900 Soc [2]. The issue is related to FW revision WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9 that comes bundled with Ubuntu 22.10. It appears the SoC increasingly triggering wake-ups after being suspended for approx. 4 hrs. Read the full story at [4]. The solution is to upgrade SoC firmware to rev WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23/ [3] Best regards,Carsten [1] https://support.hp.com/us-en/product/hp-pro-x360-435-13.3-inch-g9-notebook-pc/2101144107/document/ish_6053745-6053789-16 [2] https://www.qualcomm.com/products/technology/wi-fi/fastconnect/fastconnect-6900 [3] https://github.com/kvalo/ath11k-firmware/tree/master/WCN6855/hw2.0/1.1/WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23 [4] https://gitlab.freedesktop.org/drm/amd/-/issues/2377 [Fix] Upgrade firmware, as mentioned above. [Test case] Verify WiFi functionality on WCN6855 works and that unplugging power cord during suspend doesn't wake system. [Where Problems might occur] It's firmware, what could possibly go wrong? If so, connectivity issues wit ath11k based NICs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2006458/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009882] Re: Linux 5.4.0-144-generic x86_64 multithread / fork issues
Hi Matthew, yes we do have NFSv3 in our environment and mostly all PHP requests pull files sitting in network storage. However "waiting access" (wa) indicator is close to zero while inspecting "top". In the past when we had had issues with NFS3 most processes slow down while waiting for I/O thus causing a significant spike in the indicator. Doesn't happen this time. Regards, Al -- 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/2009882 Title: Linux 5.4.0-144-generic x86_64 multithread / fork issues Status in linux package in Ubuntu: Confirmed Bug description: We have same servers already running in 5.4.0-122 , 126, 128 and 131 releases with no issues whatsoever and exceptional good performance. They basically have either Apache/2.4.41/mod_php7.4 or Apache/2.4.41/mpm_event with phm7.4-fpm setups, all working perfect. When we load kernel 5.4.0-144 CPU processing go thru the roof, and process kworker/u17:0-xprtiod show at the top. Both setups perform badly with Apache performance going avg 200ms/req in older kernels to over 4,500ms/req in this 144 release. CPU usage from avg 0.4% to over 50% under same traffic and requests rate. We just reloaded old kernels back, via /etc/default/grub, and performance is right back. Same packages, same services, everything the same but the Linux kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-144-generic 5.4.0-144.161 ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229 Uname: Linux 5.4.0-144-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 9 13:21 seq crw-rw 1 root audio 116, 33 Mar 9 13:21 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Thu Mar 9 13:22:31 2023 InstallationDate: Installed on 2021-11-17 (477 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-144-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-144-generic N/A linux-backports-modules-5.4.0-144-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006458] Re: Frequent wakeups on HP Pro x360 435 13.3 inch G9 using Qualcomm FastConnect 6900
I see that this has already been accepted into focal and jammy, but with 'Test case: TBD' this is going to stall out as an SRU. Marking incomplete and holding the kinetic SRU until this is addressed. ** Changed in: linux-firmware (Ubuntu Kinetic) Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2006458 Title: Frequent wakeups on HP Pro x360 435 13.3 inch G9 using Qualcomm FastConnect 6900 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Kinetic: Incomplete Status in linux-firmware source package in Lunar: Fix Released Bug description: [Impact] To whom it may concern: I was experiencing frequent wake-ups from s0i3x on a HP Pro 435 G9 convertible [1] using the Qualcomm FastConnect 6900 Soc [2]. The issue is related to FW revision WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9 that comes bundled with Ubuntu 22.10. It appears the SoC increasingly triggering wake-ups after being suspended for approx. 4 hrs. Read the full story at [4]. The solution is to upgrade SoC firmware to rev WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23/ [3] Best regards,Carsten [1] https://support.hp.com/us-en/product/hp-pro-x360-435-13.3-inch-g9-notebook-pc/2101144107/document/ish_6053745-6053789-16 [2] https://www.qualcomm.com/products/technology/wi-fi/fastconnect/fastconnect-6900 [3] https://github.com/kvalo/ath11k-firmware/tree/master/WCN6855/hw2.0/1.1/WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23 [4] https://gitlab.freedesktop.org/drm/amd/-/issues/2377 [Fix] Upgrade firmware, as mentioned above. [Test case] TBD. [Where Problems might occur] It's firmware, what could possibly go wrong? If so, connectivity issues wit ath11k based NICs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2006458/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
This is also a problem for me with -35 / AMD Radeon pro wx 3200 series. When I rolled back to -32 it worked. -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: In Progress Bug description: CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004262] Re: Intel E810 NICs driver in causing hangs when booting and bonds configured
** Description changed:
+ [Impact]
+ * Intel E810-family NICs cause system hangs when booting with bonding
enabled
+ * This happens due to the driver unplugging auxiliary devices
+ * The unplug event happens under RTNL lock context, which causes a deadlock
where the RDMA driver waits for the RNL lock to complete removal
+
+ [Test Plan]
+ * Users have reported that after setting up bonding on switch and server
side, the system will hang when starting network services
+
+ [Fix]
+ * The upstream patch defers unplugging/re-plugging of the auxiliary device,
so that it's not performed under the RTNL lock context.
+ * Fix was introduced by commit:
+ 248401cb2c46 ice: avoid bonding causing auxiliary plug/unplug under
RTNL lock
+
+ [Regression Potential]
+ * Regressions would manifest in devices that support RDMA functionality and
+ have been added to a bond
+ * We should look out for auxiliary devices that haven't been properly
+ unplugged, or that cause further issues with
+ ice_plug_aux_dev()/ice_unplug_aux_dev()
+
+
+ [Original Description]
jammy 22.04.1
linux-image-generic 5.15.0-58-generic
Intel E810-XXV Dual Port NICs in Dell PowerEdge 650
- 5.15 in jammy -> reproducible
- 5.19 in hwe-edge -> reproducible
- 6.2.rc6 in the mainline build -> works
- Intel's ice driver 1.10.1.2.2 -> works
-
- After beonding is enabled on switch and server side, the system will hang at
initialing ubuntu. The kernel loads but around starting the Network Services
the system can hang for sometimes 5 minutes, and in other cases, indefinitely.
+ After beonding is enabled on switch and server side, the system will
+ hang at initialing ubuntu. The kernel loads but around starting the
+ Network Services the system can hang for sometimes 5 minutes, and in
+ other cases, indefinitely.
The message of:
echo 0 > /proc/sys/kernel/hung_task_timeout_sec” systemd-resolve
blocked for more than 120 seconds
appears, and eventually the Network services just attempts to start and
never does. This is with or without DHCP enabled.
Tried this same setup with the hwe-22.04, hwe-20.04, hwe-22.04-ege and
linux-oem kernels and all exhibit the same failure.
To work around this. installing the Intel 'ice' driver of version
1.10.1.2.2 works. The system doesn't even remotely hang at startup and
all networking functions remain working (ping, DNS, general
accessibility).
The driver can be found at
https://downloadmirror.intel.com/763930/ice-1.10.1.2.2.tar.gz
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jan 31 13:08 seq
crw-rw 1 root audio 116, 33 Jan 31 13:08 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-01-27 (3 days ago)InstallationMedia:
Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Dell Inc. PowerEdge R650
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 mgag200drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic
root=UUID=668aab7c-abe9-434b-a810-acc6eab76cbc ro fsck.mode=skip
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
RelatedPackageVersions:
linux-restricted-modules-5.15.0-58-generic N/A
linux-backports-modules-5.15.0-58-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.9
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'Tags: jammy
uec-images
Uname: Linux 5.15.0-58-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 09/14/2022
dmi.bios.release: 1.8
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.2
dmi.board.name: 0PJ7YJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.8.2:bd09/14/2022:br1.8:svnDellInc.:pnPowerEdgeR650:pvr:rvnDellInc.:rn0PJ7YJ:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=0912;ModelName=PowerEdgeR650:
dmi.product.family: PowerEdge
dmi.product.name: PowerEdge R650
dmi.product.sku: SKU=0912;ModelName=PowerEdge R650
dmi.sys.vendor: Dell Inc.
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: Confirmed
** Changed in: linux (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: linux
[Kernel-packages] [Bug 2002358] Re: Screen turned off after seconds of inactivity, fixed by xset -dpms; bug depending on kernel version?
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.15 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2002358 Title: Screen turned off after seconds of inactivity, fixed by xset -dpms; bug depending on kernel version? Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Bug description: Now and then I have the problem, that the screen turns off after seconds of keyboard or mouse inactivity. I think that it changes with kernel versions but I'm not 100% sure that kernel version is the cause. The annoying bug is present for some time then it's gone, and after a while, the problem is back. Two days ago following packages were installed or updated, since then the problem is there again: Install: linux-hwe-5.15-headers-5.15.0-57:amd64 (5.15.0-57.63~20.04.1, automatic), linux-image-5.15.0-57-generic:amd64 (5.15.0-57.63~20.04.1, automatic), linux-headers-5.15.0-57-generic:amd64 (5.15.0-57.63~20.04.1, automatic), linux-modules-extra-5.15.0-57-generic:amd64 (5.15.0-57.63~20.04.1, automatic), linux-modules-5.15.0-57-generic:amd64 (5.15.0-57.63~20.04.1, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.15.0.56.62~20.04.22, 5.15.0.57.63~20.04.23), update-manager-core:amd64 (1:20.04.10.10, 1:20.04.10.11), linux-libc-dev:amd64 (5.4.0-135.152, 5.4.0-136.153), libcurl4:amd64 (7.68.0-1ubuntu2.14, 7.68.0-1ubuntu2.15), libksba8:amd64 (1.3.5-2ubuntu0.20.04.1, 1.3.5-2ubuntu0.20.04.2), update-manager:amd64 (1:20.04.10.10, 1:20.04.10.11), linux-image-generic-hwe-20.04:amd64 (5.15.0.56.62~20.04.22, 5.15.0.57.63~20.04.23), gir1.2-nautilus-3.0:amd64 (1:3.36.3-0ubuntu1.20.04.1, 1:3.36.3-0ubuntu1.20.04.2), linux-generic-hwe-20.04:amd64 (5.15.0.56.62~20.04.22, 5.15.0.57.63~20.04.23), libfabric1:amd64 (1.6.2-3, 1.6.2-3ubuntu0.1), nautilus:amd64 (1:3.36.3-0ubuntu1.20.04.1, 1:3.36.3-0ubuntu1.20.04.2), libnautilus-extension1a:amd64 (1:3.36.3-0ubuntu1.20.04.1, 1:3.36.3-0ubuntu1.20.04.2), python3-update-manager:amd64 (1:20.04.10.10, 1:20.04.10.11), nautilus-data:amd64 (1:3.36.3-0ubuntu1.20.04.1, 1:3.36.3-0ubuntu1.20.04.2), curl:amd64 (7.68.0-1ubuntu2.14, 7.68.0-1ubuntu2.15), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.14, 7.68.0-1ubuntu2.15) Today I figured out that xset -dpms solves the problem but xset s off does not. In gnome-control-center -> Power I have the following settings: Power Saving: Blank Screen -> 15 minutes ( Selecting Never doesn't change anything.) Suspend & Power Button: Automatic Suspend: On, Delay 15 minutes Power Button Action: Power off I'm using Description: Ubuntu 20.04.5 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-57-generic 5.15.0-57.63~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-57.63~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 9 22:47:36 2023 InstallationDate: Installed on 2022-01-01 (372 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2002358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002358] Re: Screen turned off after seconds of inactivity, fixed by xset -dpms; bug depending on kernel version?
I have the same problem, but with Ubuntu 22. Using xset does resolve the issue, but then the problem is that when my computer does go to sleep, the monitor does not power down -- the screen is just blank but still powered. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2002358 Title: Screen turned off after seconds of inactivity, fixed by xset -dpms; bug depending on kernel version? Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Bug description: Now and then I have the problem, that the screen turns off after seconds of keyboard or mouse inactivity. I think that it changes with kernel versions but I'm not 100% sure that kernel version is the cause. The annoying bug is present for some time then it's gone, and after a while, the problem is back. Two days ago following packages were installed or updated, since then the problem is there again: Install: linux-hwe-5.15-headers-5.15.0-57:amd64 (5.15.0-57.63~20.04.1, automatic), linux-image-5.15.0-57-generic:amd64 (5.15.0-57.63~20.04.1, automatic), linux-headers-5.15.0-57-generic:amd64 (5.15.0-57.63~20.04.1, automatic), linux-modules-extra-5.15.0-57-generic:amd64 (5.15.0-57.63~20.04.1, automatic), linux-modules-5.15.0-57-generic:amd64 (5.15.0-57.63~20.04.1, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.15.0.56.62~20.04.22, 5.15.0.57.63~20.04.23), update-manager-core:amd64 (1:20.04.10.10, 1:20.04.10.11), linux-libc-dev:amd64 (5.4.0-135.152, 5.4.0-136.153), libcurl4:amd64 (7.68.0-1ubuntu2.14, 7.68.0-1ubuntu2.15), libksba8:amd64 (1.3.5-2ubuntu0.20.04.1, 1.3.5-2ubuntu0.20.04.2), update-manager:amd64 (1:20.04.10.10, 1:20.04.10.11), linux-image-generic-hwe-20.04:amd64 (5.15.0.56.62~20.04.22, 5.15.0.57.63~20.04.23), gir1.2-nautilus-3.0:amd64 (1:3.36.3-0ubuntu1.20.04.1, 1:3.36.3-0ubuntu1.20.04.2), linux-generic-hwe-20.04:amd64 (5.15.0.56.62~20.04.22, 5.15.0.57.63~20.04.23), libfabric1:amd64 (1.6.2-3, 1.6.2-3ubuntu0.1), nautilus:amd64 (1:3.36.3-0ubuntu1.20.04.1, 1:3.36.3-0ubuntu1.20.04.2), libnautilus-extension1a:amd64 (1:3.36.3-0ubuntu1.20.04.1, 1:3.36.3-0ubuntu1.20.04.2), python3-update-manager:amd64 (1:20.04.10.10, 1:20.04.10.11), nautilus-data:amd64 (1:3.36.3-0ubuntu1.20.04.1, 1:3.36.3-0ubuntu1.20.04.2), curl:amd64 (7.68.0-1ubuntu2.14, 7.68.0-1ubuntu2.15), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.14, 7.68.0-1ubuntu2.15) Today I figured out that xset -dpms solves the problem but xset s off does not. In gnome-control-center -> Power I have the following settings: Power Saving: Blank Screen -> 15 minutes ( Selecting Never doesn't change anything.) Suspend & Power Button: Automatic Suspend: On, Delay 15 minutes Power Button Action: Power off I'm using Description: Ubuntu 20.04.5 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-57-generic 5.15.0-57.63~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-57.63~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 9 22:47:36 2023 InstallationDate: Installed on 2022-01-01 (372 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2002358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009882] Re: Linux 5.4.0-144-generic x86_64 multithread / fork issues
we have the same issue with this kernel, but also with NFSv4 thanks, Christian -- 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/2009882 Title: Linux 5.4.0-144-generic x86_64 multithread / fork issues Status in linux package in Ubuntu: Confirmed Bug description: We have same servers already running in 5.4.0-122 , 126, 128 and 131 releases with no issues whatsoever and exceptional good performance. They basically have either Apache/2.4.41/mod_php7.4 or Apache/2.4.41/mpm_event with phm7.4-fpm setups, all working perfect. When we load kernel 5.4.0-144 CPU processing go thru the roof, and process kworker/u17:0-xprtiod show at the top. Both setups perform badly with Apache performance going avg 200ms/req in older kernels to over 4,500ms/req in this 144 release. CPU usage from avg 0.4% to over 50% under same traffic and requests rate. We just reloaded old kernels back, via /etc/default/grub, and performance is right back. Same packages, same services, everything the same but the Linux kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-144-generic 5.4.0-144.161 ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229 Uname: Linux 5.4.0-144-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 9 13:21 seq crw-rw 1 root audio 116, 33 Mar 9 13:21 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Thu Mar 9 13:22:31 2023 InstallationDate: Installed on 2021-11-17 (477 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-144-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-144-generic N/A linux-backports-modules-5.4.0-144-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000778] Re: pmtu.sh in net from ubunut_kernel_selftests crash SUT with K-5.19
I could not reproduce this on baltar or kopter-kernel just by running the kernel net selftest suite a few weeks ago, and no one else seems to be experiencing similar problems that I can find. I suspect there is some configuration of the vrfs from previous tests/runs that might be influencing this crash. Still need to do more debugging on it. -- 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/2000778 Title: pmtu.sh in net from ubunut_kernel_selftests crash SUT with K-5.19 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Kinetic: Incomplete Bug description: Issue found with Kinetic 5.19.0-27.28 and 5.19.0-28.29 in this cycle (20221114) on these SUTs * P9 baltar * ARM64 kuzzle * ARM64 howzit-kernel This should not be considered as a regression as the net test cannot be built in 5.19.0-24.25 Test log: ubuntu@baltar:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./pmtu.sh TEST: ipv4: PMTU exceptions [ OK ] TEST: ipv4: PMTU exceptions - nexthop objects [ OK ] TEST: ipv6: PMTU exceptions [ OK ] TEST: ipv6: PMTU exceptions - nexthop objects [ OK ] TEST: ICMPv4 with DSCP and ECN: PMTU exceptions [ OK ] TEST: ICMPv4 with DSCP and ECN: PMTU exceptions - nexthop objects [ OK ] 'socat' command not found; skipping tests TEST: UDPv4 with DSCP and ECN: PMTU exceptions [SKIP] TEST: IPv4 over vxlan4: PMTU exceptions [ OK ] TEST: IPv4 over vxlan4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6 over vxlan4: PMTU exceptions [ OK ] TEST: IPv6 over vxlan4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] TEST: IPv4 over vxlan6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] TEST: IPv6 over vxlan6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4 over geneve4: PMTU exceptions[ OK ] TEST: IPv4 over geneve4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6 over geneve4: PMTU exceptions[ OK ] TEST: IPv6 over geneve4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4 over geneve6: PMTU exceptions[ OK ] TEST: IPv4 over geneve6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6 over geneve6: PMTU exceptions[ OK ] TEST: IPv6 over geneve6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4, bridged vxlan4: PMTU exceptions [ OK ] TEST: IPv4, bridged vxlan4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6, bridged vxlan4: PMTU exceptions [ OK ] TEST: IPv6, bridged vxlan4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4, bridged vxlan6: PMTU exceptions [ OK ] TEST: IPv4, bridged vxlan6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6, bridged vxlan6: PMTU exceptions [ OK ] TEST: IPv6, bridged vxlan6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4, bridged geneve4: PMTU exceptions[ OK ] TEST: IPv4, bridged geneve4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6, bridged geneve4: PMTU exceptions[ OK ] TEST: IPv6, bridged geneve4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4, bridged geneve6: PMTU exceptions[ OK ] TEST: IPv4, bridged geneve6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6, bridged geneve6: PMTU exceptions[ OK ] TEST: IPv6, bridged geneve6: PMTU exceptions - nexthop objects [ OK ] ovs_bridge not supported TEST: IPv4, OVS vxlan4: PMTU exceptions [SKIP] ovs_bridge not supported TEST: IPv6, OVS vxlan4: PMTU exceptions [SKIP] ovs_bridge not supported TEST: IPv4, OVS vxlan6: PMTU exceptions [SKIP] ovs_bridge not supported TEST: IPv6, OVS vxlan6: PMTU exceptions [SKIP] ovs_bridge not supported TEST: IPv4, OVS geneve4: PMTU exceptions[SKIP] ovs_bridge not supported TEST: IPv6, OVS geneve4: PMTU exceptions[SKIP] ovs_bridge not supported TEST: IPv4, OVS geneve6: PMTU exceptions[SKIP] ovs_bridge not supported TEST: IPv6, OVS geneve6: PMTU exceptions
[Kernel-packages] [Bug 1862791] Re: ALC3234 - Popping sounds at the start and at the end of playback
Same on Gigabyte B450 I AORUS PRO WIFI mini-ITX Mainboard (Realtek® ALC1220-VB codec) It does on playback through the 3.5 mm jack output. -- 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/1862791 Title: ALC3234 - Popping sounds at the start and at the end of playback Status in linux package in Ubuntu: Confirmed Bug description: I have bought the Canonical certified DELL Inspiron 15 3585 and i have an issue with audio playback. It only happens when using built-in speakers, it doesn't happen on playback through the 3.5 mm jack output or HDMI output. I already tried disabling power save $ cat /sys/module/snd_hda_intel/parameters/power_save 0 $ cat /sys/module/snd_hda_intel/parameters/power_save_controller N i also tried tsched=0 and using aplay /dev/zero, nothing helped thus far additional info: $ lspci | grep Audio 04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio Controller 04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller $ dmesg | grep -i error [1.065246] tpm_crb: probe of MSFT0101:00 failed with error -16 [1.119343] RAS: Correctable Errors collector initialized. [8.980071] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro [9.769684] pcieport :00:01.7: AER: Multiple Corrected error received: :00:01.0 [9.769697] pcieport :00:01.7: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) [9.769702] pcieport :00:01.7: AER: device [1022:15d3] error status/mask=0040/6000 [ 11.691398] pcieport :00:01.7: AER: Multiple Corrected error received: :00:01.0 [ 11.691419] pcieport :00:01.7: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) [ 11.691425] pcieport :00:01.7: AER: device [1022:15d3] error status/mask=0040/6000 [ 11.727149] pcieport :00:01.7: AER: Corrected error received: :00:01.0 [ 11.727159] pcieport :00:01.7: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) [ 11.727164] pcieport :00:01.7: AER: device [1022:15d3] error status/mask=0040/6000 $ dmesg | grep -i audio [0.565377] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [9.843973] snd_hda_intel :04:00.1: Handle vga_switcheroo audio client [9.855036] input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci:00/:00:08.1/:04:00.1/sound/card0/input16 [9.905946] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC3234: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [9.905950] snd_hda_codec_realtek hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [9.905952] snd_hda_codec_realtek hdaudioC1D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [9.905954] snd_hda_codec_realtek hdaudioC1D0:mono: mono_out=0x0 [9.905955] snd_hda_codec_realtek hdaudioC1D0:inputs: [9.905958] snd_hda_codec_realtek hdaudioC1D0: Headset Mic=0x19 [9.905960] snd_hda_codec_realtek hdaudioC1D0: Headphone Mic=0x1a [9.905961] snd_hda_codec_realtek hdaudioC1D0: Internal Mic=0x12 [9.963314] input: HD-Audio Generic Headphone Mic as /devices/pci:00/:00:08.1/:04:00.6/sound/card1/input18 OS: Kubuntu 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Feb 11 16:49:19 2020 InstallationDate: Installed on 2020-01-17 (24 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=pl PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jan1699 F pulseaudio /dev/snd/controlC0: jan1699 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-17 (31 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 3585 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-40-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A
[Kernel-packages] [Bug 1903288] Re: Power guest secure boot with static keys: kernel portion
Planned new target is 24.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903288 Title: Power guest secure boot with static keys: kernel portion Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Expired Bug description: == Comment: #2 - Daniel John Axtens - 2020-11-05 20:15:10 == This is the kernel side of changes needed for LPAR/guest secure boot. Because Ubuntu keeps its kernels so wonderfully up to date, I don't think there are any extra patches you need to pick up. (I'll double- check against the 21.04 tree once my git pulls finish!) However, we potentially need some configuration changes to make sure kexec-ing into a crashdump kernel still works. Because Lockdown requires that kexec kernels are signed by a key trusted by IMA, the public key for used for signing the kdump kernel needs to be in the IMA keyring or the platform keyring. For host secure boot (and in the UEFI case), it's loaded into the platform keyring. But in the case of guest secure boot with static keys, it's not loaded into the platform keyring so it needs to be loaded into the IMA keyring. This is easy enough to do. Firstly, load the Secure Boot CA into the .primary_trusted_keys keyring via the CONFIG_SYSTEM_TRUSTED_KEYS property. We assume the key used to sign the kernel is signed by this CA. Then, enable IMA_LOAD_X509, which allows certificates signed by a key on the .primary_trusted_keys keyring to be loaded into the IMA keyring. Then set IMA_X509_PATH to provide a path to the signing key on installed file system. (It may also be possible to do this step in userspace, so long as the CA is trusted by the kernel.) Then that key will be loaded into the .ima keyring at boot and be used to appraise the kexec kernel for crashdumps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009085] Re: nvidia-libopencl1-384, nvidia-opencl-icd-384 binaries need dropping on i386
This got done, the i386 binaries got handled via the NBS process. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2009085 Title: nvidia-libopencl1-384, nvidia-opencl-icd-384 binaries need dropping on i386 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: The set of binaries from nvidia-graphics-drivers-390 on i386 has been reduced to: libnvidia-compute-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386 libnvidia-decode-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386 libnvidia-encode-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386 libnvidia-fbc1-390| 390.157-0ubuntu3 | lunar-proposed/restricted | i386 libnvidia-gl-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386 libnvidia-ifr1-390| 390.157-0ubuntu3 | lunar-proposed/restricted | i386 However, the *opencl*384 transitional packages are still being generated: nvidia-libopencl1-384 | 390.157-0ubuntu3 | lunar-proposed/multiverse | i386 nvidia-opencl-icd-384 | 390.157-0ubuntu3 | lunar-proposed/multiverse | i386 And these now become uninstallable because they depend on nvidia- headless-390 that has been dropped on i386. This is the last piece blocking us from having updated nvidia + lrm + kernels in lunar so I have manually deleted the binaries from the archive to allow it to migrate. They also need to be dropped from the source. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2009085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011854] Re: cmos_interrupt not getting called
I confirmed that the kernel -update (-1030) does is able to pass this
test.
--
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/2011854
Title:
cmos_interrupt not getting called
Status in linux-oracle package in Ubuntu:
New
Bug description:
The ubuntu_ltp_kernel_misc rtc01 test case has exposed a possible
regression of the RTC cmos driver on certain Oracle clouds.
This was observed on jammy:linux-oracle-5.15.0-1031.37.
- VM.DenseIO2.8
- VM.Standard2.1
rtc01 0 TINFO : RTC READ TEST:
rtc01 1 TPASS : RTC READ TEST Passed
rtc01 0 TINFO : Current RTC date/time is 16-3-2023, 17:36:04.
rtc01 0 TINFO : RTC ALARM TEST :
rtc01 0 TINFO : Alarm time set to 17:36:09.
rtc01 0 TINFO : Waiting 5 seconds for the alarm...
rtc01 2 TFAIL : rtc01.c:151: Timed out waiting for the alarm
rtc01 0 TINFO : RTC UPDATE INTERRUPTS TEST :
rtc01 0 TINFO : Waiting for 5 update interrupts...
rtc01 3 TFAIL : rtc01.c:208: Timed out waiting for the update
interrupt
rtc01 0 TINFO : RTC Tests Done!
Notice that we successfully enable RTC_AIE_ON, unlike
VM.Standard.A1.Flex-4c.8m which does not support it. I confirmed with
bpftrace on -1029 that we see the cmos interrupt (part of ltp
read_alarm_test)
sudo bpftrace -e 'kprobe:cmos_interrupt { printf("%s\n", probe) }'
Attaching 1 probe...
kprobe:cmos_interrupt
On -1031 no interrupt is detected. I think this might be caused by
017314318ad4 ("rtc: cmos: Call cmos_wake_setup() from
cmos_do_probe()")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2011854/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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-oem-5.17/5.17.0-1029.30)
All autopkgtests for the newly accepted linux-restricted-modules-oem-5.17 (5.17.0-1029.30) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.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/jammy/update_excuses.html#linux-restricted-modules-oem-5.17 [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 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1013.13 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! ** Tags removed: verification-done verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-oem-6.0 verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007331 Title: Fix HFP mSBC support on Realtek Bluetooth USB controller Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in pulseaudio source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in pulseaudio source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in pulseaudio source package in Lunar: Fix Released Bug description: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected device sends response. [Test] Connect different headsets to the said controller, HFP can play and record sounds now. Also verified A2DP profile is unaffected. [Where problems could occur] The kernel part is Realtek specific, so the regression risk is very limited. The pulseaudio side only affects HFP profile, since the codeflow only changes when a mic is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007331/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
This bug is awaiting verification that the linux-oem-5.17/5.17.0-1029.30 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! ** Tags added: kernel-spammed-jammy-linux-oem-5.17 -- 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 1814234] Re: rtcpie in timers from ubuntu_kernel_selftests randomly failing
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1013.13 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! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-oem-6.0 verification-needed-jammy -- 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 2009024] Re: Fail to output sound to external monitor which connects via docking station
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009024 Title: Fail to output sound to external monitor which connects via docking station Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] No sound output from the external monitor which connect via some docking station. It only happens when user boot the system with docking station connected. Re-plug the docking station can fix this issue. Or plug the docking station later won't trigger this problem. [Fix] Turn on the CONFIG_SND_HDA_INTEL_HDMI_SILENT in kernel config. It will start sending an "audio keepalive" to the monitor as soon as it is connected. [Test] Connect the external monitor to the Atomic Type-C Dock (HD22Q) and boot the system with the dock connected. Play sound via HDMI/DP port and check if there's any audio output from the external monitor. [Where problems could occur] It sends the "audio keepalive"(silent stream) to the monitor when connected. Doesn't affect original workflow of the audio system. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009024/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This seems to also affect the 5.19.0 kernel train as well (linux-aws- edge on jammy) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-aws source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux-aws source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux-aws source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-aws source package in Kinetic: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-aws source package in Lunar: Invalid Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic
[Kernel-packages] [Bug 2007601] Re: On Boot after ramdisk loads: ACPI BIOS error (bug) AE_AML_Buffer_Limit, ... is beyond end of object
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007601 Title: On Boot after ramdisk loads: ACPI BIOS error (bug) AE_AML_Buffer_Limit, ... is beyond end of object Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: this tool shows linux-signed-hwe-5.19? But Grub shows 5.19.0-32-generic After regular Software Update to kernel 5.19.0-32-generic on boot after the boot disk is decrypted, and the ramdisk loads: the error message (see attached jpg) shows briefly before continuing to load to the log in screen. No noticeable problems, but I've not tried to suspend (which in the past works, most of the time) with this kernel loaded. Per wiki.ubuntu.com/Kernel/Bugs 1, hardware: see screenshot of Settings/About 2. every boot to this kernel produces the error 3. Does NOT Exist in previous kernels 5.15.0-60-generic and earlier 4. Problem: not sure how to test the latest development Ubuntu kernel version as well as the latest upstream mainline kernel. Towards a solution: This probably is the latest development kernel? (I've looked at https://wiki.ubuntu.com/Kernel/MainlineBuilds?action=show=KernelMainlineBuilds, AND I'm not familiar enough with the language to understand what I'd be doing, so unless I have specific directions on how to test the latest development and upstream mainline kernels, I'm not about to stab in the dark at it. I only get the basic drift that this bug may be fixed in the upcoming kernels, and installing them may or may not work (for other reasons) on the LTS I have running now. this command gives this result $ cat /proc/version_signature Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Not sure if this is a security risk or not, so to be safe I ticked that it is. Smells like it to me, anyway. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 16 10:08:33 2023 InstallationDate: Installed on 2023-01-11 (36 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2007601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI
Still having this issue on my pc -- 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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000778] Re: pmtu.sh in net from ubunut_kernel_selftests crash SUT with K-5.19
kuzzle and scobee are actually failing with 64k generic and 64k lowlatency. The only ARM64 box that can pass with 64k is ARM64 node starmie-kernel. Others like dazzle, kuzzle, helo-kernel, kopter-kernel, scobee-kernel are all failing with 64k. I wonder why we're having this difference. -- 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/2000778 Title: pmtu.sh in net from ubunut_kernel_selftests crash SUT with K-5.19 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Kinetic: Incomplete Bug description: Issue found with Kinetic 5.19.0-27.28 and 5.19.0-28.29 in this cycle (20221114) on these SUTs * P9 baltar * ARM64 kuzzle * ARM64 howzit-kernel This should not be considered as a regression as the net test cannot be built in 5.19.0-24.25 Test log: ubuntu@baltar:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./pmtu.sh TEST: ipv4: PMTU exceptions [ OK ] TEST: ipv4: PMTU exceptions - nexthop objects [ OK ] TEST: ipv6: PMTU exceptions [ OK ] TEST: ipv6: PMTU exceptions - nexthop objects [ OK ] TEST: ICMPv4 with DSCP and ECN: PMTU exceptions [ OK ] TEST: ICMPv4 with DSCP and ECN: PMTU exceptions - nexthop objects [ OK ] 'socat' command not found; skipping tests TEST: UDPv4 with DSCP and ECN: PMTU exceptions [SKIP] TEST: IPv4 over vxlan4: PMTU exceptions [ OK ] TEST: IPv4 over vxlan4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6 over vxlan4: PMTU exceptions [ OK ] TEST: IPv6 over vxlan4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] TEST: IPv4 over vxlan6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] TEST: IPv6 over vxlan6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4 over geneve4: PMTU exceptions[ OK ] TEST: IPv4 over geneve4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6 over geneve4: PMTU exceptions[ OK ] TEST: IPv6 over geneve4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4 over geneve6: PMTU exceptions[ OK ] TEST: IPv4 over geneve6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6 over geneve6: PMTU exceptions[ OK ] TEST: IPv6 over geneve6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4, bridged vxlan4: PMTU exceptions [ OK ] TEST: IPv4, bridged vxlan4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6, bridged vxlan4: PMTU exceptions [ OK ] TEST: IPv6, bridged vxlan4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4, bridged vxlan6: PMTU exceptions [ OK ] TEST: IPv4, bridged vxlan6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6, bridged vxlan6: PMTU exceptions [ OK ] TEST: IPv6, bridged vxlan6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4, bridged geneve4: PMTU exceptions[ OK ] TEST: IPv4, bridged geneve4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6, bridged geneve4: PMTU exceptions[ OK ] TEST: IPv6, bridged geneve4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4, bridged geneve6: PMTU exceptions[ OK ] TEST: IPv4, bridged geneve6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6, bridged geneve6: PMTU exceptions[ OK ] TEST: IPv6, bridged geneve6: PMTU exceptions - nexthop objects [ OK ] ovs_bridge not supported TEST: IPv4, OVS vxlan4: PMTU exceptions [SKIP] ovs_bridge not supported TEST: IPv6, OVS vxlan4: PMTU exceptions [SKIP] ovs_bridge not supported TEST: IPv4, OVS vxlan6: PMTU exceptions [SKIP] ovs_bridge not supported TEST: IPv6, OVS vxlan6: PMTU exceptions [SKIP] ovs_bridge not supported TEST: IPv4, OVS geneve4: PMTU exceptions[SKIP] ovs_bridge not supported TEST: IPv6, OVS geneve4: PMTU exceptions[SKIP] ovs_bridge not supported TEST: IPv4, OVS geneve6: PMTU exceptions[SKIP] ovs_bridge not supported TEST: IPv6, OVS geneve6: PMTU exceptions[SKIP] TEST: IPv4 over fou4:
[Kernel-packages] [Bug 2000667] Re: cmsg_so_mark.sh / cmsg_time.sh / cmsg_ipv6.sh in net from ubuntu_kernel_selftests hang with non-amd64
These are not blocking RISCV64 test to proceed anymore.
** 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/2000667
Title:
cmsg_so_mark.sh / cmsg_time.sh / cmsg_ipv6.sh in net from
ubuntu_kernel_selftests hang with non-amd64
Status in ubuntu-kernel-tests:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux source package in Lunar:
Fix Released
Bug description:
[Impact]
cmsg_* tests in net tests from ubuntu_kernel_selftests will hang on
non-amd64 systems and eventually causing "Incomplete" test results on
RISCV kernels due to the timeout setting.
This is because of an infinity while loop caused by a char variable
used here to take the getopt() return value in cmsg_sender.c, it should
be an int instead.
[Fix]
* 1573c68820 ("selftests: net: fix cmsg_so_mark.sh test hang")
This patch can be cherry-picked into both Kinetic and Lunar, these test
cases are only available in these newer kernels.
[Test]
Compile the patched cmsg_sender.c on a non-amd64 system, and the cmsg_*
tests will no longer hanging.
[Where problems could occur ]
Change limited to testing tools, no actual impact to real functions.
[Original Bug Report]
Issue found with 5.19.0-1010.11, 5.19.0-1011.12
This issue does not exist in 5.19.0-1009.10 because the net test can't
be built by that time.
Test output:
Running 'make run_tests -C net TEST_PROGS=cmsg_so_mark.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=riscv -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_so_mark.sh
Timer expired (5400 sec.), nuking pid 82951
A manual test shows it will stuck with:
$ sudo ./cmsg_so_mark.sh
+ NS=ns
+ IP4=172.16.0.1/24
+ TGT4=172.16.0.2
+ IP6=2001:db8:1::1/64
+ TGT6=2001:db8:1::2
+ MARK=1000
+ trap cleanup EXIT
+ ip netns add ns
+ ip netns exec ns sysctl -w 'net.ipv4.ping_group_range=0 2147483647'
+ ip -netns ns link add type dummy
+ ip -netns ns link set dev dummy0 up
+ ip -netns ns addr add 172.16.0.1/24 dev dummy0
+ ip -netns ns addr add 2001:db8:1::1/64 dev dummy0
+ ip -netns ns rule add fwmark 1000 lookup 300
+ ip -6 -netns ns rule add fwmark 1000 lookup 300
+ ip -netns ns route add prohibit any table 300
+ ip -6 -netns ns route add prohibit any table 300
+ BAD=0
+ TOTAL=0
+ for ovr in setsock cmsg both
+ for i in 4 6
+ '[' 4 == 4 ']'
+ TGT=172.16.0.2
+ for p in u i r
+ '[' u == u ']'
+ prot=UDP
+ '[' u == i ']'
+ '[' u == r ']'
+ '[' setsock == setsock ']'
+ m=-M
+ '[' setsock == cmsg ']'
+ '[' setsock == both ']'
+ ip netns exec ns ./cmsg_sender -4 -p u -M 1001 172.16.0.2 1234
(test stuck here)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000667/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000772] Re: powerpc-build in ubuntu_kernel_selftests failed on P9 with K-5.19
No PowerPC on RISCV kernels. ** 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/2000772 Title: powerpc-build in ubuntu_kernel_selftests failed on P9 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 Released Bug description: [Impact] When trying to build powerpc tests from ubuntu_kernel_selftests, it will fail with: inlined from ‘cycles_with_mmcr2’ at cycles_with_mmcr2_test.c:81:3: /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:86:10: error: ‘actual’ may be used uninitialized [-Werror=maybe-uninitialized] 86 | return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack ()); | ^~~ cycles_with_mmcr2_test.c: In function ‘cycles_with_mmcr2’: cycles_with_mmcr2_test.c:25:36: note: ‘actual’ was declared here 25 | uint64_t val, expected[2], actual; | ^~ cc1: all warnings being treated as errors [Fix] * ff446cd768 "selftests/powerpc: Avoid GCC 12 uninitialised variable warning" This patch can be cherry-picked into Kinetic kernel. [Test] Apply this patch to the kernel tree and build it with: sudo make -C linux/tools/testing/selftests TARGETS=powerpc With this error fixed, test compliation can finish without any issue. [Where problems could occur] Change for test case, no impact to acutal function. [Original Bug Report] Issue found with K-5.19.0-28-generic on P9 node baltar This should not be considered as a regression since ubuntu_kernel_selftests will be blocked by the net test crash before this powerpc tests can be started. This was found by manually running the test. Test build failed with: gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"unknown"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include -m64 -no-pie cycles_with_mmcr2_test.c ../../harness.c ../../utils.c ../event.c ../lib.c ebb.c ebb_handler.S trace.c busy_loop.S -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test In file included from /usr/include/stdio.h:906, from cycles_with_mmcr2_test.c:6: In function ‘printf’, inlined from ‘cycles_with_mmcr2’ at cycles_with_mmcr2_test.c:81:3: /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:86:10: error: ‘actual’ may be used uninitialized [-Werror=maybe-uninitialized] 86 | return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack ()); | ^~~ cycles_with_mmcr2_test.c: In function ‘cycles_with_mmcr2’: cycles_with_mmcr2_test.c:25:36: note: ‘actual’ was declared here 25 | uint64_t val, expected[2], actual; |^~ cc1: all warnings being treated as errors make[3]: *** [../../../lib.mk:173: /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test] Error 1 Please find attachment for the complete build log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
I can confirm unusable NFS Performance on Clients using 5.4.0-144-generic 5.15.0-67-generic had to downgrade kernels an update grub to boot older Versions -- 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 751689] Re: [Lenovo Thinkpad x201s] Overheat due to slow fans when on 'auto'
I know it is long time since this was opened, however herewith I want to declare that this problem still exists nowadays in all Thinkpad line and it is not related to Linux. From all what I have learned so far there is only one conclusion: Lenovo is gapping its fans to keep their products at low noise intentionally with the penalty of lower performance. This problem is getting annoying as more powerful a CPU is as it needs more cooling. No Linux OS is controlling the fans by default and it is obvious it is not Ubuntu or any other fault. It is simply Lenovo is hindering any OS to use higher fan speeds. JFYI in my situation the maximum disengaged fan in a Thinkpad Extreme is about 7800 rpm, however highest auto level is at 4800 rpm. thinkpad_acpi is offering level 7 max which equals to this 4800 rpm. Please note thinkpad_acpi is depending on registers which only offer levels but no fixed speed. For me personally this is a bad design decision and will go into the equation of vendor choice for the next purchase but who cares. PS: As a last there is a pulse setup thinkable which keeps the desired fan rpm at a certain level by alternating between full and highest, but this is a far off topic here. -- 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/751689 Title: [Lenovo Thinkpad x201s] Overheat due to slow fans when on 'auto' Status in linux package in Ubuntu: Fix Released Status in linux source package in Maverick: Won't Fix Status in linux source package in Natty: Won't Fix Status in linux source package in Precise: Won't Fix Status in thinkfan package in Debian: Fix Released Status in linux package in Fedora: Won't Fix Bug description: On my Thinkpad x201s with an i7, if I utilize all of the CPUs/hyperthreads, the machine can be made to overheat very quickly. This is because of the default level setting of 'auto' in /proc/acpi/ibm/fan. On 'auto', the fan only ever goes up to around 4500rpm, while in 'disengaged' mode it can go as high as 6400rpm. At 4500rpm, the CPU continues to climb until the system is forcibly shutdown at 100C. If I reload thinkpad_acpi like so: $ sudo rmmod thinkpad_acpi $ sudo modprobe thinkpad_acpi fan_control=1 Then I can set the fan to disengaged mode manually: echo "level disengaged" > /proc/acpi/ibm/fan With this setting, I can utilize all of the CPUs for an extended time and not surpass 85C, still pretty hot but well under the 100C range. Furthermore, setting to level '7' (the supposed max fan speed) runs the fan at ~5300, well below the maximum fan speed. In maverick this did not seem to be as much of a problem (perhaps because of the lack of the big kernel lock in natty?). Related bugs: https://bugzilla.redhat.com/show_bug.cgi?id=675433 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610722 (against thinkfan package, but demonstrates that other x201 users are having the same problem) ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-7-generic 2.6.38-7.39 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 AcpiTables: Error: command ['gksu', '-D', 'Apport', '--', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 1: GNOME_SUDO_PASS Sorry, try again. sudo: 3 incorrect password attempts AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jamie 2641 F pulseaudio /dev/snd/pcmC0D0p: jamie 2641 F...m pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf252 irq 43' Mixer name : 'Intel IbexPeak HDMI' Components : 'HDA:14f15069,17aa2156,00100302 HDA:80862804,17aa21b5,0010' Controls : 12 Simple ctrls : 6 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 6QHT28WW-1.09' Mixer name : 'ThinkPad EC 6QHT28WW-1.09' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Tue Apr 5 11:56:28 2011 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=58280e6e-d161-43ea-8593-a89fb7b6851a InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1) MachineType: LENOVO 5129CTO ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine:
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-aws (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux-aws (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-aws (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-aws (Ubuntu Kinetic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-aws source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux-aws source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux-aws source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-aws source package in Kinetic: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-aws source package in Lunar: Invalid Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0
[Kernel-packages] [Bug 2012060] [NEW] Crash doesn't open kdumps on Jammy with HWE kernel
Public bug reported:
Hi!
I'm running Ubuntu with HWE kernel 5.19.0-35-generic. The kernel
contains slab struct changes [1] that break crash 8.0.0. The issue has
been fixed [3] in commit 14f8c460473c ("memory: Handle struct slab
changes on Linux 5.17-rc1 and later"). The fix is available in crash
8.0.1 and above.
If you wish I can send a merge request to jammy-devel with this single
patch but for now it seems that Ubuntu's process with regards to this
package is just bump it to the newer version from debian.
Please advice how to proceed. For now I just build the latest version of
crash and I can open kdumps from Jammy with HWE using it.
1. https://lwn.net/Articles/881039/
2. https://bugzilla.redhat.com/show_bug.cgi?id=2041702
3.
https://github.com/crash-utility/crash/commit/14f8c460473c8613553b5defd174ca2af812ddcb
$ lsb_release -rd
Description:Ubuntu 22.04.2 LTS
Release:22.04
$ apt-cache policy crash
crash:
Installed: 8.0.0-1ubuntu1
Candidate: 8.0.0-1ubuntu1
Version table:
*** 8.0.0-1ubuntu1 500
500 http://th.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
** Affects: crash (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/2012060
Title:
Crash doesn't open kdumps on Jammy with HWE kernel
Status in crash package in Ubuntu:
New
Bug description:
Hi!
I'm running Ubuntu with HWE kernel 5.19.0-35-generic. The kernel
contains slab struct changes [1] that break crash 8.0.0. The issue has
been fixed [3] in commit 14f8c460473c ("memory: Handle struct slab
changes on Linux 5.17-rc1 and later"). The fix is available in crash
8.0.1 and above.
If you wish I can send a merge request to jammy-devel with this single
patch but for now it seems that Ubuntu's process with regards to this
package is just bump it to the newer version from debian.
Please advice how to proceed. For now I just build the latest version
of crash and I can open kdumps from Jammy with HWE using it.
1. https://lwn.net/Articles/881039/
2. https://bugzilla.redhat.com/show_bug.cgi?id=2041702
3.
https://github.com/crash-utility/crash/commit/14f8c460473c8613553b5defd174ca2af812ddcb
$ lsb_release -rd
Description:Ubuntu 22.04.2 LTS
Release:22.04
$ apt-cache policy crash
crash:
Installed: 8.0.0-1ubuntu1
Candidate: 8.0.0-1ubuntu1
Version table:
*** 8.0.0-1ubuntu1 500
500 http://th.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2012060/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Kinetic) 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/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: In Progress Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups:
[Kernel-packages] [Bug 2006945] Re: New DG2 workarounds
** 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-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2006945 Title: New DG2 workarounds Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: [Impact] These are hw revision based workarounds from 6.2 that need to be backported for Intel Arc/DG2. [Test case] We don't have known issues that these would fix, but check that things still work normally. [Where things could go wrong] these are limited to a very specific type of hardware, so can't think of what could go wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Re: Fix NVME storage with RAID ON disappeared under Dell factory WINPE environment
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2011768 Title: Fix NVME storage with RAID ON disappeared under Dell factory WINPE environment Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid 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/hwe-next/+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 2012055] [NEW] Jammy update: v6.1.20 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.20 upstream stable release from git://git.kernel.org/ Linux 6.1.20 UML: define RUNTIME_DISCARD_EXIT Revert "bpf, test_run: fix _frame misplacement for LIVE_FRAMES" filelocks: use mount idmapping for setlease permission check drm/amd/display: adjust MALL size available for DCN32 and DCN321 drm/amd/display: Allow subvp on vactive pipes that are 2560x1440@60 media: rc: gpio-ir-recv: add remove function media: ov5640: Fix analogue gain control scripts: handle BrokenPipeError for python scripts PCI: Add SolidRun vendor ID macintosh: windfarm: Use unsigned type for 1-bit bitfields alpha: fix R_ALPHA_LITERAL reloc for large modules powerpc/kcsan: Exclude udelay to prevent recursive instrumentation powerpc/64: Move paca allocation to early_setup() powerpc/64: Fix task_cpu in early boot when booting non-zero cpuid powerpc/bpf/32: Only set a stack frame when necessary clk: renesas: rcar-gen3: Disable R-Car H3 ES1.* powerpc/iommu: fix memory leak with using debugfs_lookup() powerpc/64: Don't recurse irq replay MIPS: Fix a compilation issue tpm/eventlog: Don't abort tpm_read_log on faulty ACPI address watch_queue: fix IOC_WATCH_QUEUE_SET_SIZE alloc error paths drm/msm/adreno: fix runtime PM imbalance at unbind adreno: Shutdown the GPU properly drm/amdgpu/soc21: Add video cap query support for VCN_4_0_4 drm/amdgpu/soc21: don't expose AV1 if VCN0 is harvested ext4: Fix deadlock during directory rename drm/amdgpu: fix return value check in kfd RISC-V: Don't check text_mutex during stop_machine riscv: Use READ_ONCE_NOCHECK in imprecise unwinding stack mode erofs: Revert "erofs: fix kvcalloc() misuse with __GFP_NOFAIL" af_unix: fix struct pid leaks in OOB support net: dsa: mt7530: permit port 5 to work without port 6 on MT7621 SoC SUNRPC: Fix a server shutdown leak octeontx2-af: Unlock contexts in the queue context cache in case of fault detection net/smc: fix fallback failed while sendmsg with fastopen ethernet: ice: avoid gcc-9 integer overflow warning ice: Fix DSCP PFC TLV creation NFSD: Protect against filesystem freezing block: fix wrong mode for blkdev_put() from disk_scan_partitions() platform: x86: MLX_PLATFORM: select REGMAP instead of depending on it platform: mellanox: select REGMAP instead of depending on it netfilter: conntrack: adopt safer max chain length scsi: sd: Fix wrong zone_write_granularity value during revalidate scsi: megaraid_sas: Update max supported LD IDs to 240 net: tls: fix device-offloaded sendpage straddling records net: ethernet: mtk_eth_soc: fix RX data corruption issue net: phy: smsc: fix link up detection in forced irq mode btf: fix resolving BTF_KIND_VAR after ARRAY, STRUCT, UNION, PTR bpf, test_run: fix _frame misplacement for LIVE_FRAMES btrfs: fix extent map logging bit not cleared for split maps after dropping range m68k: mm: Move initrd phys_to_virt handling after paging_init() netfilter: tproxy: fix deadlock due to missing BH disable netfilter: ctnetlink: revert to dumping mark regardless of event type bnxt_en: Avoid order-5 memory allocation for TPA data net: phylib: get rid of unnecessary locking net: stmmac: add to set device wake up flag when stmmac init phy drm/msm/dpu: clear DSPP reservations in rm release drm/msm/dpu: fix clocks settings for msm8998 SSPP blocks drm/msm/dpu: drop DPU_DIM_LAYER from MIXER_MSM8998_MASK drm/msm/dpu: fix len of sc7180 ctl blocks bpf, sockmap: Fix an infinite loop error when len is 0 in tcp_bpf_recvmsg_parser() ice: copy last block omitted in ice_get_module_eeprom() net: caif: Fix use-after-free in cfusbl_device_notify() net: lan78xx: fix accessing the LAN7800's internal phy specific registers from the MAC driver perf stat: Fix counting when initial delay configured net: use indirect calls helpers for sk_exit_memory_pressure() net: tls: fix possible race condition between do_tls_getsockopt_conf() and do_tls_setsockopt_conf() netfilter: nft_quota: copy content when cloning expression netfilter: nft_last: copy content when cloning expression selftests: nft_nat: ensuring the listening side is up before starting the client net: lan966x: Fix port police support using tc-matchall ila: do not generate empty messages in ila_xlat_nl_cmd_get_mapping() drm/msm/dpu: disable features unsupported by QCM2290 tls: rx: fix return value for async crypto powerpc: dts: t1040rdb: fix compatible string for Rev A boards nfc: fdp: add null check of devm_kmalloc_array in fdp_nci_i2c_read_device_properties bgmac: fix *initial* chip reset to support BCM5358
[Kernel-packages] [Bug 2011389] Re: vmd may fail to create sysfs entry while `pci_rescan_bus()` called in some other drivers like wwan
** Changed in: linux-oem-6.1 (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-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: Fix Committed 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 2012019] Re: Fix E-star testing failure with RTK 8852BE
** Changed in: linux-oem-6.1 (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-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2012019 Title: Fix E-star testing failure with RTK 8852BE Status in HWE Next: New Status in linux package in Ubuntu: In Progress 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: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: New Bug description: [Impact] E-star testing failure on machine with RTK 8852BE configuration. [Fix] 1. Enable CLKREQ to reduce power consumption. 2. release RX standby timer of beamformee to save power [Test Case] 1. Prepare one system with RTK 8852BE WLAN/BT. 2. Run E-star testing. 3. The result must meet PASS criteria. [Where problems could occur] Low, may face the performance issue during throughput verification. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2012019/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008951] Re: Ubuntu 22.04 on Lenovo Legion 5 Laptop occasional boot freeze and and unexpected reboots
This one has max number of errors. ** Attachment added: "prevboot4.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2008951/+attachment/5655077/+files/prevboot4.txt -- 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/2008951 Title: Ubuntu 22.04 on Lenovo Legion 5 Laptop occasional boot freeze and and unexpected reboots Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: Problem occurs with "ubuntu-drivers install" beforehand, and in trying to resolve resorted to manual nvidia drivers install approach. Problem recurs anyway. Now not sure is nvidia issue as sometimes bluetooth does not get recognized as now (in this session). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 1 18:33:58 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-11-18 (103 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2008951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008951] Re: Ubuntu 22.04 on Lenovo Legion 5 Laptop occasional boot freeze and and unexpected reboots
My Legion do not freze but quite offten resets unexpectedly. After such reset WiFi is not available. Also number of errors in succesive boots differs: wborkowski@w-borkowski-PC:~$ grep "Error" prevboot0.txt | wc -l 38 wborkowski@w-borkowski-PC:~$ grep "Error" prevboot1.txt | wc -l 42 wborkowski@w-borkowski-PC:~$ grep "Error" prevboot2.txt | wc -l 42 wborkowski@w-borkowski-PC:~$ grep "Error" prevboot3.txt | wc -l 40 wborkowski@w-borkowski-PC:~$ grep "Error" prevboot4.txt | wc -l 43 wborkowski@w-borkowski-PC:~$ grep "Error" prevboot5.txt | wc -l 41 -- 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/2008951 Title: Ubuntu 22.04 on Lenovo Legion 5 Laptop occasional boot freeze and and unexpected reboots Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: Problem occurs with "ubuntu-drivers install" beforehand, and in trying to resolve resorted to manual nvidia drivers install approach. Problem recurs anyway. Now not sure is nvidia issue as sometimes bluetooth does not get recognized as now (in this session). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 1 18:33:58 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-11-18 (103 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2008951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008951] Re: Ubuntu 22.04 on Lenovo Legion 5 Laptop occasional boot freeze and and unexpected reboots
The prevboot0.txt is current, with WiFi working. Some of previous boot is after spontanic reboot. ** Attachment added: "prevboot0.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2008951/+attachment/5655076/+files/prevboot0.txt -- 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/2008951 Title: Ubuntu 22.04 on Lenovo Legion 5 Laptop occasional boot freeze and and unexpected reboots Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: Problem occurs with "ubuntu-drivers install" beforehand, and in trying to resolve resorted to manual nvidia drivers install approach. Problem recurs anyway. Now not sure is nvidia issue as sometimes bluetooth does not get recognized as now (in this session). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 1 18:33:58 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-11-18 (103 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2008951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Re: Fix NVME storage with RAID ON disappeared under Dell factory WINPE environment
** Changed in: linux (Ubuntu Lunar) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2011768 Title: Fix NVME storage with RAID ON disappeared under Dell factory WINPE environment Status in HWE Next: New Status in linux package in Ubuntu: In Progress 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: In Progress Status in linux source package in Lunar: In Progress 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/hwe-next/+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 2012019] Re: Fix E-star testing failure with RTK 8852BE
** Description changed: [Impact] - E-star testing failure on Inspiron RTK 8852BE configuration. + E-star testing failure on machine with RTK 8852BE configuration. [Fix] 1. Enable CLKREQ to reduce power consumption. 2. release RX standby timer of beamformee to save power [Test Case] 1. Prepare one system with RTK 8852BE WLAN/BT. 2. Run E-star testing. 3. The result must meet PASS criteria. [Where problems could occur] Low, may face the performance issue during throughput verification. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2012019 Title: Fix E-star testing failure with RTK 8852BE Status in HWE Next: New Status in linux package in Ubuntu: In Progress 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: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: New Bug description: [Impact] E-star testing failure on machine with RTK 8852BE configuration. [Fix] 1. Enable CLKREQ to reduce power consumption. 2. release RX standby timer of beamformee to save power [Test Case] 1. Prepare one system with RTK 8852BE WLAN/BT. 2. Run E-star testing. 3. The result must meet PASS criteria. [Where problems could occur] Low, may face the performance issue during throughput verification. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2012019/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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: originate-from-1943687 -- 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] netlink_sendmsg+0x24b/0x4c0 [ 547.531505] sock_sendmsg+0x69/0x70 [ 547.533114]
