[Kernel-packages] [Bug 2042902] Re: ucm2: soundwire: add rt713 SDCA device
For Lunar ** Patch added: "alsa-ucm-conf_1.2.6.3-1ubuntu9.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+attachment/5717628/+files/alsa-ucm-conf_1.2.6.3-1ubuntu9.3.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in alsa-ucm-conf package in Ubuntu: New Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042902] Re: ucm2: soundwire: add rt713 SDCA device
For Mantic ** Patch added: "alsa-ucm-conf_1.2.9-1ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+attachment/5717676/+files/alsa-ucm-conf_1.2.9-1ubuntu4.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in alsa-ucm-conf package in Ubuntu: New Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042902] Re: ucm2: soundwire: add rt713 SDCA device
for Jammy ** Patch added: "alsa-ucm-conf_1.2.6.3-1ubuntu1.9.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+attachment/5717627/+files/alsa-ucm-conf_1.2.6.3-1ubuntu1.9.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in alsa-ucm-conf package in Ubuntu: New Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042902] Re: ucm2: soundwire: add rt713 SDCA device
The attachment "alsa-ucm-conf_1.2.6.3-1ubuntu1.9.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in alsa-ucm-conf package in Ubuntu: New Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042902] Re: ucm2: soundwire: add rt713 SDCA device
For Noble ** Patch added: "alsa-ucm-conf_1.2.9-1ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+attachment/5717724/+files/alsa-ucm-conf_1.2.9-1ubuntu4.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in alsa-ucm-conf package in Ubuntu: New Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038263] Re: Add SoF topology support on Intel RaptorLake DELL SKU 0C11
2.2.6-1ubuntu1.1 works well on Intel RaptorLake DELL SKU 0C11 as 23.10 ** Attachment added: "721293778.446208.mp4" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038263/+attachment/5717731/+files/721293778.446208.mp4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2038263 Title: Add SoF topology support on Intel RaptorLake DELL SKU 0C11 Status in HWE Next: New Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: New Status in linux source package in Jammy: New Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in firmware-sof source package in Lunar: Won't Fix Status in linux source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in firmware-sof source package in Mantic: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: SRU Jusitification for firmware-sof [Impact] To support audio functions on RPL Dell SKU 0C11, it requires the topology file from sof-tplg-v2.2.7 [Fix] Pull the sof-rpl-rt711-l0-rt1316-l12.tplg from https://github.com/thesofproject/sof-bin/releases/tag/v2023.09 [Test Case] Install the fixes on the target platform(RPL Dell SKU 0C11) and verify the audio function. 1. Install the firmware-sof on platform(RPL) Dell SKU 0C11 2. Make sure the audio output/input devices are not dummy in audio settings. [Where problems could occur] New firmware is only for the RPL platforms which requires the specific topology file. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2023.09 [Impact] Audio play/capture are not functional on specific Dell machines of Intel RPL platforms [Fix] Backport the fix from Intel in https://github.com/thesofproject/linux [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy` shown on the Audio output/input option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2038263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038263] Re: Add SoF topology support on Intel RaptorLake DELL SKU 0C11
** Tags removed: verification-needed-mantic ** Tags added: verification-done-mantic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2038263 Title: Add SoF topology support on Intel RaptorLake DELL SKU 0C11 Status in HWE Next: New Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: New Status in linux source package in Jammy: New Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in firmware-sof source package in Lunar: Won't Fix Status in linux source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in firmware-sof source package in Mantic: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: SRU Jusitification for firmware-sof [Impact] To support audio functions on RPL Dell SKU 0C11, it requires the topology file from sof-tplg-v2.2.7 [Fix] Pull the sof-rpl-rt711-l0-rt1316-l12.tplg from https://github.com/thesofproject/sof-bin/releases/tag/v2023.09 [Test Case] Install the fixes on the target platform(RPL Dell SKU 0C11) and verify the audio function. 1. Install the firmware-sof on platform(RPL) Dell SKU 0C11 2. Make sure the audio output/input devices are not dummy in audio settings. [Where problems could occur] New firmware is only for the RPL platforms which requires the specific topology file. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2023.09 [Impact] Audio play/capture are not functional on specific Dell machines of Intel RPL platforms [Fix] Backport the fix from Intel in https://github.com/thesofproject/linux [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy` shown on the Audio output/input option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2038263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2041668] Re: Memory leak in 23.10 kernel (6.5.0-10)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2041668 Title: Memory leak in 23.10 kernel (6.5.0-10) Status in linux package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: Confirmed Bug description: There appears to be a memory 'leak' in the kernel of the latest Ubuntu release (Mantic Minotaur, kernel version 6.5.0-10). I put 'leak' in quotes because this memory appears to be allocated but never used. The kernel's memory over-commit mechanism seems to prevent this leak from manifesting in OOM killer triggers or other failures. The primary symptom is a steady increase in the value reported as 'Committed_AS' in '/proc/meminfo'. The other memory stats reported there remain reasonable, though. I've observed this problem on a fairly diverse set of machines (both VMs and physical machines) with a variety of workloads. Busier machines seem to have a faster leak rate. I've tried to narrow down the issue by rebooting into single user mode, killing all userspace processes (except the systemd processes) and removing as many kernel models as possible. The problem continues in that state. I didn't see any obvious culprits in /proc/slabinfo nor /proc/vmallocinfo. So far, the only way I've been able to remediate this issue is to reboot back into the Lunar Lobster kernel (6.2.0-35). I think this fact alone rules out any triggers that may be part of the 23.10 userspace environment. I've attached the generic debug info requested by this component's bug template from an example machine. Please let me know if there is any more information I can provide. It seems to be pretty trivial to reproduce though, and I'm guessing it has not been reported yet because the leak doesn't actually manifest in an out-of-memory situation. At least, I haven't observed that yet. The worst case I've observed was 150 GB of memory committed on a machine with 16 GB of physical RAM after about 24 hours. Moving back to the previous kernel version, the committed memory statistic holds fairly steady around 7 GB on that machine and workload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041668/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035181] Re: Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1025.29 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-linux-xilinx-zynqmp'
to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp'
to 'verification-failed-jammy-linux-xilinx-zynqmp'.
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-xilinx-zynqmp-v2
verification-needed-jammy-linux-xilinx-zynqmp
--
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/2035181
Title:
Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Fix Released
Bug description:
[Impact]
Commit bdeeed3498c7 ("libbpf: fix offsetof() and container_of() to work
with CO-RE") from stable update breaks the ubuntu_bpf test build and
cause net:udpgro_bench.sh, net:udpgro.sh, net:veth.sh in
ubuntu_kernel_selftests stopped working, as they require bpf selftest
to be built first.
The following is extracted from the commit message:
The problem is the new offsetof() does not play nice with static asserts.
Given that the context is a static assert (and CO-RE relocation is not
needed at compile time), offsetof() usage can be replaced by restoring
the original offsetof() definition as __builtin_offsetof().
[Test Plan]
Build bpf selftest in tools/testing/selftests with the following command:
make headers; make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS= \
clean all KDIR=/usr/src/linux-headers-5.15.0-85-generic/
The build can finish successfully with patched kernel source code.
[Where problems could occur]
Fix limited to testing tool, if this fix is incorrect the bpf selftest
build will remain broken.
== Original bug report ==
Issue found with Jammy 5.15.0-85.95 in cycle 2023.09.04
This issue does not exist with 5.15.0-83.92 in cycle 2023.08.07 (-84
is a security cycle, in which the ubuntu_bpf test was not triggered
there)
Test build failed with:
CLNG-BPF [test_maps] test_btf_map_in_map.o
CLNG-BPF [test_maps] test_btf_newkv.o
CLNG-BPF [test_maps] test_btf_nokv.o
CLNG-BPF [test_maps] test_btf_skc_cls_ingress.o
CLNG-BPF [test_maps] test_cgroup_link.o
CLNG-BPF [test_maps] test_check_mtu.o
CLNG-BPF [test_maps] test_cls_redirect.o
make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
stderr:
Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from
latest version at 'include/uapi/linux/bpf.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs
from latest version at 'include/uapi/linux/netlink.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs
from latest version at 'include/uapi/linux/if_link.h'
progs/test_cls_redirect.c:90:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:91:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv4.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33:
note: expanded from macro 'offsetof'
#define offsetof(type, member) ((unsigned long)&((type *)0)->member)
^
progs/test_cls_redirect.c:95:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:96:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv6.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
[Kernel-packages] [Bug 2035163] Re: Avoid address overwrite in kernel_connect
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1025.29 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-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'. 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-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2035163 Title: Avoid address overwrite in kernel_connect Status in linux package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gke package in Ubuntu: Invalid Status in linux-gkeop package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux-gcp source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in linux-gke source package in Jammy: Fix Released Status in linux-gkeop source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-gcp source package in Lunar: Fix Released Status in linux-gcp source package in Mantic: Fix Released Bug description: This fix is requested to resolve an issue with NFS-backed mounts when used with BPF-load-balancing: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=0bdf399342c5 Testing: - GCP has confirmed the fix works before proposing it upstream. I have verified basic network sanity with fix applied. Regression potenial: - The fix modifies kernel_connect() which can have an effect on all kinds of network connections. The change itself is very minor though and simply converts a pass-by-reference to a pass-by-value - so the risk is considered minimal. More information at: https://canonical.lightning.force.com/lightning/r/Case/5008e0HNldDAAT/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035166] Re: NULL Pointer Dereference During KVM MMU Page Invalidation
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1025.29 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-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'. 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-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp -- 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/2035166 Title: NULL Pointer Dereference During KVM MMU Page Invalidation Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Bug description: [Impact] During VM live migration, there is a potential risk of dereferencing a NULL pointer, which can lead to memory access issues and result in an unstable environment. [Fix] The call trace is as follows: kernel: BUG: kernel NULL pointer dereference, address: 0008 kernel: #PF: supervisor write access in kernel mode kernel: #PF: error_code(0x0002) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: 0002 [#1] SMP NOPTI kernel: CPU: 29 PID: 4063601 Comm: CPU 0/KVM Tainted: G IOE 5.15.0-53-generic #59~20.04.1-Ubuntu kernel: Hardware name: Dell Inc. PowerEdge R640/0H28RR, BIOS 2.12.2 07/09/2021 kernel: RIP: 0010:__handle_changed_spte+0x3a9/0x620 [kvm] kernel: Code: 48 8b 58 28 44 0f b6 63 24 48 8b 43 28 41 83 e4 0f 48 89 45 a0 0f 1f 44 00 00 45 84 d2 0f 85 06 02 00 00 48 8b 43 08 48 8b 13 <48> 89 42 08 48 89 10 44 0f b6 6b 23 48 b8 00 01 00 00 00 00 ad de kernel: RSP: 0018:b580320278a8 EFLAGS: 00010246 kernel: RAX: RBX: a0fe29e94c38 RCX: 0027 kernel: RDX: RSI: 0004 RDI: b5801e24ba58 kernel: RBP: b58032027930 R08: R09: 0004 kernel: R10: 0001 R11: R12: 0003 kernel: R13: 0004 R14: R15: b5801e235000 kernel: FS: 7f1553fff700() GS:a20eff78() knlGS: kernel: CS: 0010 DS: ES: CR0: 80050033 kernel: CR2: 0008 CR3: 00e7f7544004 CR4: 007726e0 kernel: PKRU: 5554 kernel: Call Trace: kernel: kernel: ? __switch_to_xtra+0x109/0x510 kernel: zap_gfn_range+0x218/0x360 [kvm] kernel: ? __smp_call_single_queue+0x59/0x90 kernel: ? alloc_cpumask_var_node+0x1/0x30 kernel: ? kvm_make_vcpus_request_mask+0x150/0x1d0 [kvm] kernel: kvm_tdp_mmu_zap_invalidated_roots+0x5b/0xb0 [kvm] kernel: kvm_mmu_zap_all_fast+0x19a/0x1d0 [kvm] -- kernel: RAX: ffda RBX: 4020ae46 RCX: 7f15aa26e3ab kernel: RDX: 7f1553ffe050 RSI: 4020ae46 RDI: 002f kernel: RBP: 5602a885a410 R08: 5602a82ad000 R09: 7f154c087470 kernel: R10: R11: 0246 R12: 7f1553ffe050 kernel: R13: 7f1553ffe160 R14: R15: 0080 kernel: The error occurred randomly in different production environments of the customer, all with the same call trace. Therefore, the likelihood of other processes contaminating memory is low. After analyzing the call trace with the help of debug symbols, we can pinpoint the source of the error. root@focal:~/ddeb# eu-addr2line -ifae ./usr/lib/debug/lib/modules/5.15.0-53-generic/kernel/arch/x86/kvm/kvm.ko __handle_changed_spte+0x3a9 0x00068109 __list_del inlined at /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:135:2 in __handle_changed_spte /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:112:13 __list_del_entry /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:135:2 list_del /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:146:2 tdp_mmu_unlink_page /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:305:2 handle_removed_tdp_mmu_page /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:340:2 __handle_changed_spte /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:491:3 The error occurred when the kernel attempted to delete an entry from a list. This issue may potentially be related to timing and has proven challenging to reproduce consistently, making it difficult for us to pinpoint the
[Kernel-packages] [Bug 2035116] Re: allow io_uring to be disabled in runtime
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1025.29 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-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'. 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-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp -- 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/2035116 Title: allow io_uring to be disabled in runtime Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] io_uring has been an important attack vector in the recent years in local privilege escalation attacks. Allowing admins that don't use io_uring to disable it in their systems allows them to reduce their attack surface. [Test case] sysctl -w kernel.io_uring_disabled=1 then try to use io_uring from an unprivileged user, then try it with privileges (CAP_SYS_ADMIN) Actually also tried setting kernel.io_uring_disabled=2 and checking that neither (privileged or unprivileged worked). Then testing setting it back to 0. Then tested with io_uring_disabled set to 1 and io_uring_group=1000 and that it worked for group 1000, then set it to 1001 and verified that it didn't work anymore for group 1000. [Potential regression] Uses can be denied from using io_uring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037403] Re: PCI BARs larger than 128GB are disabled
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1025.29 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-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'. 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-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2037403 Title: PCI BARs larger than 128GB are disabled Status in linux package in Ubuntu: Incomplete Status in linux-bluefield package in Ubuntu: New Status in linux source package in Jammy: Fix Released Status in linux-bluefield source package in Jammy: Fix Committed Bug description: [SRU Justification] [Impact] Current linux-bluefield kernel reports that PCI BARs larger than 128GB are disabled. Increase the maximum PCI BAR size from 128GB to 8TB for future expansion. [Test Plan] Use updated kernel with PCI device with PCI BARs larger than 128GB. [Where problems could occur] No potential problems are expected. [Other Info] Testing has been provided by the customer. This patch is a cherry-pick from the upstream 5.18 kernel. It is intended for linux-bluefield kernel re-spin but it may be also suitable for the generic kernel (separate submission). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037077] Re: Fix unstable audio at low levels on Thinkpad P1G4
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1025.29 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-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'. 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-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp -- 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/2037077 Title: Fix unstable audio at low levels on Thinkpad P1G4 Status in HWE Next: In Progress 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 Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The audio at low levels is not stable with fluctuating levels. [Fix] Forcibly assign NID 0x03 to HP while NID 0x02 to SPK. [Test] Tested on hardware, the audio output is OK at all levels. [Where problems could occur] It may break audio output on Thinkpad P1G4/5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036675] Re: 5.15.0-85 live migration regression
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1025.29 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-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'. 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-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp -- 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/2036675 Title: 5.15.0-85 live migration regression Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Fix Released Bug description: Fixes added for LP 2032164 [0] to resolve an issue in live migration have unfortunately introduced a regression, causing a previously working live migration pattern to fail when tested with the 5.15.0-85 kernel from -proposed. Specifically, live migration from a PKRU-enabled host running a kernel older than 5.15.0-85 to a host running the 5.15.0-85 kernel will fail. The destination can be either with or without PKRU; both cases fail, although in different ways (one hangs, the other fails due to a PCID flag issue). The commits in question are commit fa9225d64f215e8109de10f6b6c7a08f033d0ec0 Author: Dr. David Alan Gilbert Date: Mon Aug 21 14:47:28 2023 +0800 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES commit 27a189b881278c8ad9c16b0ee05668d724352733 Author: Leonardo Bras Date: Mon Aug 21 14:47:27 2023 +0800 x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0 [0] https://bugs.launchpad.net/bugs/2032164 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
I can confirm too, i'm just waiting for the latest kernels to show up in mainline, so i can install them and have them signed. So that virtualbox will finally worrk too. It's been an honor to test along you people!! Happy patching. :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: New Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Status in Fedora: New Bug description: [Impact] Keyboard and touchpad doesn't work on some recent systems, and also s2idle is broken. [Fix] Two upstream commits. 128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility 3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops [Test case] boot a fixed kernel and test that input and s2idle works. [Where problems could occur] A buggy bios could maybe advertise a system being PCAT compatible when it's not, though in such a case it might have been already caught before. -- Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919154] Re: Enable CONFIG_NO_HZ_FULL on supported architectures
** Changed in: linux-lowlatency (Ubuntu Hirsute) Status: New => Won't Fix ** Changed in: linux-lowlatency (Ubuntu Groovy) Status: New => Won't Fix ** Changed in: linux-lowlatency (Ubuntu Focal) Status: New => Won't Fix -- 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/1919154 Title: Enable CONFIG_NO_HZ_FULL on supported architectures Status in linux package in Ubuntu: In Progress Status in linux-lowlatency package in Ubuntu: Fix Released Status in linux source package in Focal: Won't Fix Status in linux-lowlatency source package in Focal: Won't Fix Status in linux source package in Groovy: Won't Fix Status in linux-lowlatency source package in Groovy: Won't Fix Status in linux source package in Hirsute: Won't Fix Status in linux-lowlatency source package in Hirsute: Won't Fix Status in linux source package in Jammy: Won't Fix Status in linux-lowlatency source package in Jammy: Won't Fix Status in linux source package in Lunar: Won't Fix Status in linux-lowlatency source package in Lunar: Won't Fix Status in linux source package in Mantic: Won't Fix Status in linux-lowlatency source package in Mantic: Fix Released Bug description: [Impact] The CONFIG_NO_HZ_FULL=y Kconfig option causes the kernel to avoid sending scheduling-clock interrupts to CPUs with a single runnable task, and such CPUs are said to be "adaptive-ticks CPUs". This is important for applications with aggressive real-time response constraints because it allows them to improve their worst-case response times by the maximum duration of a scheduling-clock interrupt. It is also important for computationally intensive short-iteration workloads: If any CPU is delayed during a given iteration, all the other CPUs will be forced to wait idle while the delayed CPU finishes. Thus, the delay is multiplied by one less than the number of CPUs. In these situations, there is again strong motivation to avoid sending scheduling-clock interrupts. [Test Plan] In order to verify the change will not cause performance issues in context switch we should compare the results for: ./stress-ng --seq 0 --metrics-brief -t 15 Running on a dedicated machine and with the following services disabled: smartd.service, iscsid.service, apport.service, cron.service, anacron.timer, apt-daily.timer, apt-daily-upgrade.timer, fstrim.timer, logrotate.timer, motd-news.timer, man-db.timer. The results didn't show any performance regression: https://kernel.ubuntu.com/~mhcerri/lp1919154/ [Where problems could occur] Performance degradation might happen for workloads with intensive context switching. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2041668] Re: Memory leak in 23.10 kernel (6.5.0-10)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2041668 Title: Memory leak in 23.10 kernel (6.5.0-10) Status in linux package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: Confirmed Bug description: There appears to be a memory 'leak' in the kernel of the latest Ubuntu release (Mantic Minotaur, kernel version 6.5.0-10). I put 'leak' in quotes because this memory appears to be allocated but never used. The kernel's memory over-commit mechanism seems to prevent this leak from manifesting in OOM killer triggers or other failures. The primary symptom is a steady increase in the value reported as 'Committed_AS' in '/proc/meminfo'. The other memory stats reported there remain reasonable, though. I've observed this problem on a fairly diverse set of machines (both VMs and physical machines) with a variety of workloads. Busier machines seem to have a faster leak rate. I've tried to narrow down the issue by rebooting into single user mode, killing all userspace processes (except the systemd processes) and removing as many kernel models as possible. The problem continues in that state. I didn't see any obvious culprits in /proc/slabinfo nor /proc/vmallocinfo. So far, the only way I've been able to remediate this issue is to reboot back into the Lunar Lobster kernel (6.2.0-35). I think this fact alone rules out any triggers that may be part of the 23.10 userspace environment. I've attached the generic debug info requested by this component's bug template from an example machine. Please let me know if there is any more information I can provide. It seems to be pretty trivial to reproduce though, and I'm guessing it has not been reported yet because the leak doesn't actually manifest in an out-of-memory situation. At least, I haven't observed that yet. The worst case I've observed was 150 GB of memory committed on a machine with 16 GB of physical RAM after about 24 hours. Moving back to the previous kernel version, the committed memory statistic holds fairly steady around 7 GB on that machine and workload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041668/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043079] [NEW] [PCE-5033] suspend/1_xrandr_screens_after_suspend.tar.gz_auto
Public bug reported: aster: Ubuntu desktop 20.04.6 Device: Advantech ARK-3534 Kernel: 5.15.0-67-generic x86_6 Steps to repro: 1. Execute Checkbox 2. View the Suspend Test Failure symptom: Attachments suspend/1_xrandr_screens_after_suspend.tar.gz_auto Failure rate: 100% Note: When using PCE-5133 to test, there is no such test item ** Affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: New ** Attachment added: "submission_2023-11-08T08.27.39.763127.zip" https://bugs.launchpad.net/bugs/2043079/+attachment/5717462/+files/submission_2023-11-08T08.27.39.763127.zip -- 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/2043079 Title: [PCE-5033] suspend/1_xrandr_screens_after_suspend.tar.gz_auto Status in linux-intel-iotg package in Ubuntu: New Bug description: aster: Ubuntu desktop 20.04.6 Device: Advantech ARK-3534 Kernel: 5.15.0-67-generic x86_6 Steps to repro: 1. Execute Checkbox 2. View the Suspend Test Failure symptom: Attachments suspend/1_xrandr_screens_after_suspend.tar.gz_auto Failure rate: 100% Note: When using PCE-5133 to test, there is no such test item To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2043079/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040354] Re: Add K24 device tree
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1025.29 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-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'. 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-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2040354 Title: Add K24 device tree Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed Bug description: [ Impact ] * This ports the K24 device trees from the Xilinx 6.1 kernel (xlnx_rebase_v6.1_LTS_2023.1_update) * This will allow the same image.its file and thus flash-kernel package to be used for the K24 development images and the stable release. [ Test Plan ] * The k24 platform does not need to be tested since it is not a certified platform. The normal regression testing on K26 and ZCU platforms is sufficient. [ Where problems could occur ] * A bug in the device tree could cause a build error in the kernel. The device tree is not used by any certified images. [ Other Info ] The change squashes together the following changes from Xilinx xlnx_rebase_v6.1_LTS_2023.1_update branch. Patches that modified device tree other than: arch/arm64/boot/dts/xilinx/zynqmp-sck-kd-g-revA.dts arch/arm64/boot/dts/xilinx/zynqmp-sm-k24-revA.dts arch/arm64/boot/dts/xilinx/zynqmp-smk-k24-revA.dts were modified to remove the other changes. a89bdb9e6f1f arm64: zynqmp: Add/Update/Sync DTs for xilinx platforms f1fe53d988d8 arm64: zynqmp: Update ADI PHY properties for KD240 f660fc7bba89 arm64: zynqmp: Use MIO 77 for ADI PHY reset on KD240 41a6b53e0691 arm64: zynqmp: Fill model name for SOM CCs 958f20d8445e arm64: zynqmp: Fix memory size on k24 c3cc27055c19 arm64: zynqmp: Wire can0 on kd240-revA 9da2d3e73b17 arm64: zynqmp: Configure gem1 rx pins on kd240 board 646a2dfaaaf8 arm64: zynqmp: Cover K24/KD240 revB/1 boards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2040354/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1025.29 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-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'. 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-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp -- 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/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux package in Ubuntu: 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 Lunar: Fix Released Bug description: SRU Justification [Impact] In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. [Test Plan] User test results pending, but its a fix commit so should likely be applied regardless. [Regression Potential] SGX could continue to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034479] Re: Fix suspend hang on Lenovo workstation
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1025.29 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-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'. 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-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp -- 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/2034479 Title: Fix suspend hang on Lenovo workstation Status in HWE Next: In Progress 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: Fix Released Status in linux-oem-6.1 source package in Jammy: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The system hang after resume from S3. Error logs: kernel: igb :02:00.0: disabling already-disabled device kernel: WARNING: CPU: 0 PID: 277 at drivers/pci/pci.c:2248 pci_disable_device+0xc4/0xf0 kernel: RIP: 0010:pci_disable_device+0xc4/0xf0 kernel: Call Trace: kernel: kernel: igb_io_error_detected+0x3e/0x60 kernel: report_error_detected+0xd6/0x1c0 kernel: ? __pfx_report_normal_detected+0x10/0x10 kernel: report_normal_detected+0x16/0x30 kernel: pci_walk_bus+0x74/0xa0 kernel: pcie_do_recovery+0xb9/0x340 kernel: ? __pfx_aer_root_reset+0x10/0x10 kernel: aer_process_err_devices+0x168/0x220 kernel: aer_isr+0x1b5/0x1e0 kernel: ? __pfx_irq_thread_fn+0x10/0x10 kernel: irq_thread_fn+0x21/0x70 kernel: irq_thread+0xf8/0x1c0 kernel: ? __pfx_irq_thread_dtor+0x10/0x10 kernel: ? __pfx_irq_thread+0x10/0x10 kernel: kthread+0xef/0x120 kernel: ? __pfx_kthread+0x10/0x10 kernel: ret_from_fork+0x29/0x50 kernel: kernel: ---[ end trace ]--- [Fix] The pci io error detected ops is called before the driver resumed. Avoid this race condition to fix the issue. [Test] Tested on hardware, the system suspend/resume OK. [Where problems could occur] It may break igb driver. The commit is included in 6.5-rc1 and merged by stable update in oem-6.1, SRU for Jammy and Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033122] Re: Request backport of xen timekeeping performance improvements
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1025.29 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-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'. 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-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp -- 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/2033122 Title: Request backport of xen timekeeping performance improvements Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Bug description: Users, especially those on EC2, are encouraged to select tsc as their default clocksource. However, this requires manual tuning of the operating system. Kvm can determine if it safe to use the tsc, and will default to that instead of its pvclock when appropriate. This requests a backport of patch does the same for Xen instances. If appropriate, it's fine if this is applied to only the linux-aws branches. Not all Xen EC2 instances advertise explicit nomigrate support, however, on those that do we'll select tsc by default. On the subset of hosts where this is advertised, users will safely default to the more performant clocksource. [Impact] Xen instances default to the xen clocksource which has been documented to be slower. This is required for instances where the tsc is not safe to use, or the guest is subject to migration. On some platforms the performance impact can be high, and users are encouraged to select the tsc when appropriate. Instead of leaving up to users to figure this out by reading a variety of different documents, pick the fast clocksource when it can be determined to be safe to do so. [Backport] Clean cherry pick. No conflicts applying to 5.15 or 6.2. [Test] Booted EC2 xen instances with and without this patch and validated that on those that properly advertised the required criteria via cpuid, that the clocksource defaulted to tsc instead of xen. [Potential Regression] Potential is low, since only absurd configurations could lead to a problem. If this is considered risky, it can be applied to only linux-aws where the documented guidance is for users to enable tsc as the clocksource on Xen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034447] Re: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1025.29 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-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'. 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-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp -- 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/2034447 Title: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: Seeing a panic on hidon (an Nvidia H100) after booting the 5.15.0-85-generic kernel: [ 58.935877] [ cut here ] [ 58.935893] refcount_t: underflow; use-after-free. [ 58.935920] WARNING: CPU: 207 PID: 2985 at lib/refcount.c:28 refcount_warn_saturate+0xf7/0x150 [ 58.935943] Modules linked in: x86_pkg_temp_thermal(+) intel_powerclamp coretemp nls_iso8859_1 rapl irdma(+) i40e qat_4xxx(+) isst_if_mbox_pci intel_qat pmt_telemetry pmt_crashlog idxd(+) isst_if_mmio pmt_class isst_if_common authenc idxd_bus intel_th_gth mei_me intel_th_pci intel_th mei switchtec ipmi_ssif acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 multipath linear mlx5_ib ib_uverbs ib_core ast i2c_algo_bit drm_vram_helper drm_ttm_helper ttm drm_kms_helper raid0 mlx5_core syscopyarea sysfillrect sysimgblt crct10dif_pclmul fb_sys_fops crc32_pclmul ixgbe cec mlxfw ghash_clmulni_intel aesni_intel psample crypto_simd xfrm_algo ice rc_core cryptd tls nvme i2c_i801 dca xhci_pci intel_pmt drm [ 58.936077] pci_hyperv_intf i2c_ismt i2c_smbus [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936083] mdio [ 58.936096] xhci_pci_renesas nvme_core wmi pinctrl_emmitsburg [ 58.936106] CPU: 207 PID: 2985 Comm: systemd-udevd Not tainted 5.15.0-85-generic #95-Ubuntu [ 58.936115] Hardware name: NVIDIA DGXH100/DGXH100, BIOS 1.0.7 05/08/2023 [ 58.936119] RIP: 0010:refcount_warn_saturate+0xf7/0x150 [ 58.936130] Code: eb 9e 0f b6 1d 5e e6 b9 01 80 fb 01 0f 87 f4 63 6f 00 83 e3 01 75 89 48 c7 c7 88 c3 23 9e c6 05 42 e6 b9 01 01 e8 d8 e4 6b 00 <0f> 0b e9 6f ff ff ff 0f b6 1d 2d e6 b9 01 80 fb 01 0f 87 b1 63 6f [ 58.936135] RSP: 0018:ff4d5d94b2c7fa28 EFLAGS: 00010282 [ 58.936142] RAX: RBX: RCX: 0027 [ 58.936146] RDX: ff314dbbbf9e0588 RSI: 0001 RDI: ff314dbbbf9e0580 [ 58.936149] RBP: ff4d5d94b2c7fa30 R08: 0026 R09: ff4d5d94b2c7f9c0 [ 58.936153] R10: 0028 R11: 0001 R12: [ 58.936156] R13: ff314cbfdbcb6900 R14: ff314cbfdbcb67b8 R15: ff314cbfd24b4000 [ 58.936159] FS: 7fadd2f6c8c0() GS:ff314dbbbf9c() knlGS: [ 58.936163] CS: 0010 DS: ES: CR0: 80050033 [ 58.936167] CR2: 7fadd243b584 CR3: 00012972c006 CR4: 00771ee0 [ 58.936171] DR0: DR1: DR2: [ 58.936174] DR3: DR6: fffe07f0 DR7: 0400 [ 58.936177] PKRU: 5554 [ 58.936179] Call Trace: [ 58.936184] [ 58.936188] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936204] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936212] ? crypto_mod_put+0x6b/0x80 [ 58.936225] ? show_regs.part.0+0x23/0x29 [ 58.936232] ? show_regs.cold+0x8/0xd [ 58.936239] ? refcount_warn_saturate+0xf7/0x150 [ 58.936246] ? __warn+0x8c/0x100 [ 58.936255] ? refcount_warn_saturate+0xf7/0x150 [ 58.936263] ? report_bug+0xa4/0xd0 [ 58.936274] ? down_trylock+0x2e/0x40 [ 58.936285] ? handle_bug+0x39/0x90 [ 58.936296] ? exc_invalid_op+0x19/0x70 [ 58.936301] ?
[Kernel-packages] [Bug 2031333] Re: Need to get fine-grained control for FAN(TFN) Participant.
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1025.29 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-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'. 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-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp -- 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/2031333 Title: Need to get fine-grained control for FAN(TFN) Participant. Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: This is a public version of the following bugs: https://bugs.launchpad.net/bugs/1987597 https://bugs.launchpad.net/bugs/2027754 [Feature Description] We need Fine-grained Control of TFN participant for enabling active 2 policy in Linux/chrome. Currently, The kernel has provided __FPS table and cur__state to adjust the fan level as per _FPS table . But there is no option to read *_FIF (Fan Information) and _FST (Fan Status).* Once the fine-grained control is enabled, we should be able to the set the control value from 0-100 through Arg0 of _FSL (Fan Set Level). *_FST (Fan Status)* should report current running RPM and control value of the FAN(TFN). please refer ACPI spec for more detail. [https://uefi.org/specs/ACPI/6.4/11_Thermal_Management/fan- device.html] [HW/SW Information] Hardware: Alder Lake Target Release: 22.04 Target Kernel: 5.15 Merged for 5.18-rc1 f1197343f077 ACPI: fan: Add additional attributes for fine grain control bea2d9868ef5 ACPI: fan: Properly handle fine grain control d445571fa369 ACPI: fan: Optimize struct acpi_fan_fif 00ae053a0533 ACPI: fan: Separate file for attributes creation Platform-independent [Business Justification] Function enabling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042998] Re: After upgrading to 23.10 the system does not resume after suspend
** Description changed:
+ It seems to suspend fine (when closing lid), but when opening lid it
+ tries to startup... LEDs are blinking (as the HDD is activated), after
+ some time it is working hard because the fan starts running faster and
+ faster. No reaction on any keys. Tried the power button, CTRL+ALT+F1-F8,
+ but no reaction. Only option is to restart by holding power button down
+ for 4 seconds.
+
This problem occurs when using nvidia proprietary binary driver. A
different problem occurs when I run the system without the nvidia
proprietary binary driver. See Bug #2042996
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: jarl 5102 F wireplumber
- /dev/snd/controlC1: jarl 5102 F wireplumber
- /dev/snd/seq:jarl 5099 F pipewire
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: jarl 5102 F wireplumber
+ /dev/snd/controlC1: jarl 5102 F wireplumber
+ /dev/snd/seq:jarl 5099 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Nov 8 08:19:03 2023
HibernationDevice: RESUME=UUID=62c8a911-b76d-4691-9ffe-019c5aef1c88
InstallationDate: Installed on 2016-01-08 (2861 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
- Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
- Bus 001 Device 004: ID 5986:066d Bison Electronics Inc. BisonCam, NB Pro
- Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
- Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. ES603 Swipe
Fingerprint Sensor
- Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+ Bus 001 Device 004: ID 5986:066d Bison Electronics Inc. BisonCam, NB Pro
+ Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
+ Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. ES603 Swipe
Fingerprint Sensor
+ Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=77b926b9-e936-4d48-a883-a4690b36dac0 ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
- linux-restricted-modules-6.5.0-10-generic N/A
- linux-backports-modules-6.5.0-10-generic N/A
- linux-firmware20230919.git3672ccab-0ubuntu2.1
+ linux-restricted-modules-6.5.0-10-generic N/A
+ linux-backports-modules-6.5.0-10-generic N/A
+ linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-04 (4 days ago)
dmi.bios.date: 02/02/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.13RSA1
dmi.board.asset.tag: Tag 12345
dmi.board.name: Oryx Pro
dmi.board.vendor: System76, Inc.
dmi.board.version: orxp1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1.05.13RSA1:bd02/02/2016:br5.11:svnSystem76,Inc.:pnOryxPro:pvrorxp1:rvnSystem76,Inc.:rnOryxPro:rvrorxp1:cvnSystem76,Inc.:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: Oryx Pro
dmi.product.sku: Not Applicable
dmi.product.version: orxp1
dmi.sys.vendor: System76, Inc.
--
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/2042998
Title:
After upgrading to 23.10 the system does not resume after suspend
Status in linux package in Ubuntu:
New
Bug description:
It seems to suspend fine (when closing lid), but when opening lid it
tries to startup... LEDs are blinking (as the HDD is activated), after
some time it is working hard because the fan starts running faster and
faster. No reaction on any keys. Tried the power button,
CTRL+ALT+F1-F8, but no reaction. Only option is to restart by holding
power button down for 4 seconds.
This problem occurs when using nvidia proprietary binary driver. A
different problem occurs when I run the system without the nvidia
proprietary binary driver. See Bug #2042996
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
[Kernel-packages] [Bug 2040120] Re: Kernel configs deviate from generic kernel
This bug was fixed in the package linux-gke - 5.15.0-1046.51 --- linux-gke (5.15.0-1046.51) jammy; urgency=medium * jammy/linux-gke: 5.15.0-1046.51 -proposed tracker (LP: #2038024) * Kernel configs deviate from generic kernel (LP: #2040120) - [Configs] Revert configs to match pre-annotation configs * Use new annotations model (LP: #2019000) - [Config] migrate all configs into annotations * Jammy update: v5.15.126 upstream stable release (LP: #2037593) - [Config] updateconfigs for ARM64_ERRATUM_ and ARM64_WORKAROUND_TSB_FLUSH_FAILURE [ Ubuntu: 5.15.0-88.98 ] * jammy/linux: 5.15.0-88.98 -proposed tracker (LP: #2038055) * CVE-2023-4244 - netfilter: nf_tables: don't skip expired elements during walk - netfilter: nf_tables: adapt set backend to use GC transaction API - netfilter: nft_set_hash: mark set element as dead when deleting from packet path - netfilter: nf_tables: GC transaction API to avoid race with control plane - netfilter: nf_tables: remove busy mark and gc batch API - netfilter: nf_tables: don't fail inserts if duplicate has expired - netfilter: nf_tables: fix kdoc warnings after gc rework - netfilter: nf_tables: fix GC transaction races with netns and netlink event exit path - netfilter: nf_tables: GC transaction race with netns dismantle - netfilter: nf_tables: GC transaction race with abort path - netfilter: nf_tables: use correct lock to protect gc_list - netfilter: nf_tables: defer gc run if previous batch is still pending - netfilter: nft_dynset: disallow object maps - netfilter: nft_set_rbtree: skip sync GC for new elements in this transaction * CVE-2023-42756 - netfilter: ipset: Fix race between IPSET_CMD_CREATE and IPSET_CMD_SWAP * CVE-2023-4623 - net/sched: sch_hfsc: Ensure inner classes have fsc curve * PCI BARs larger than 128GB are disabled (LP: #2037403) - PCI: Support BAR sizes up to 8TB * Fix unstable audio at low levels on Thinkpad P1G4 (LP: #2037077) - ALSA: hda/realtek - ALC287 I2S speaker platform support * Check for changes relevant for security certifications (LP: #1945989) - [Packaging] Add a new fips-checks script * Jammy update: v5.15.126 upstream stable release (LP: #2037593) - io_uring: gate iowait schedule on having pending requests - perf: Fix function pointer case - net/mlx5: Free irqs only on shutdown callback - arm64: errata: Add workaround for TSB flush failures - arm64: errata: Add detection for TRBE write to out-of-range - [Config] updateconfigs for ARM64_ERRATUM_ and ARM64_WORKAROUND_TSB_FLUSH_FAILURE - iommu/arm-smmu-v3: Work around MMU-600 erratum 1076982 - iommu/arm-smmu-v3: Document MMU-700 erratum 2812531 - iommu/arm-smmu-v3: Add explicit feature for nesting - iommu/arm-smmu-v3: Document nesting-related errata - arm64: dts: imx8mn-var-som: add missing pull-up for onboard PHY reset pinmux - word-at-a-time: use the same return type for has_zero regardless of endianness - KVM: s390: fix sthyi error handling - wifi: cfg80211: Fix return value in scan logic - net/mlx5: DR, fix memory leak in mlx5dr_cmd_create_reformat_ctx - net/mlx5e: fix return value check in mlx5e_ipsec_remove_trailer() - bpf: Add length check for SK_DIAG_BPF_STORAGE_REQ_MAP_FD parsing - rtnetlink: let rtnl_bridge_setlink checks IFLA_BRIDGE_MODE length - net: dsa: fix value check in bcm_sf2_sw_probe() - perf test uprobe_from_different_cu: Skip if there is no gcc - net: sched: cls_u32: Fix match key mis-addressing - mISDN: hfcpci: Fix potential deadlock on >lock - qed: Fix kernel-doc warnings - qed: Fix scheduling in a tasklet while getting stats - net: annotate data-races around sk->sk_max_pacing_rate - net: add missing READ_ONCE(sk->sk_rcvlowat) annotation - net: add missing READ_ONCE(sk->sk_sndbuf) annotation - net: add missing READ_ONCE(sk->sk_rcvbuf) annotation - net: add missing data-race annotations around sk->sk_peek_off - net: add missing data-race annotation for sk_ll_usec - net/sched: taprio: Limit TCA_TAPRIO_ATTR_SCHED_CYCLE_TIME to INT_MAX. - bpf, cpumap: Handle skb as well when clean up ptr_ring - bpf: sockmap: Remove preempt_disable in sock_map_sk_acquire - net: ll_temac: Switch to use dev_err_probe() helper - net: ll_temac: fix error checking of irq_of_parse_and_map() - net: korina: handle clk prepare error in korina_probe() - net: netsec: Ignore 'phy-mode' on SynQuacer in DT mode - net: dcb: choose correct policy to parse DCB_ATTR_BCN - s390/qeth: Don't call dev_close/dev_open (DOWN/UP) - ip6mr: Fix skb_under_panic in ip6mr_cache_report() - vxlan: Fix nexthop hash size - net/mlx5: fs_core: Make find_closest_ft more generic - net/mlx5: fs_core: Skip the FTs in the same FS_TYPE_PRIO_CHAINS fs_prio - prestera: fix fallback to previous version
[Kernel-packages] [Bug 2030924] Re: [SRU][Ubuntu 22.04.1] Unable to interpret the frequency values in cpuinfo_min_freq and cpuino_max_freq sysfs files.
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1025.29 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-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'. 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-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp -- 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/2030924 Title: [SRU][Ubuntu 22.04.1] Unable to interpret the frequency values in cpuinfo_min_freq and cpuino_max_freq sysfs files. Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [Impact] On DELL EMC PowerEdge system when Ubuntu 22.04.1 OS is Installed, Unable to Interpret the values in cpuinfo_max_freq and cpuinfo_min_freq sysfs files as per the Intel specs document. Steps to Reproduce: 1. Install one CPU that supports DBS "Demand-Based Power Management". 2. Install Ubuntu 22.04.1 OS. 2. Enable "Logical Processor" under CPU Information menu from F2 setup. 3. Save changes and reboot to Ubuntu 22.04.1 OS. 4. Right click on "Computer" and select "File system" and check for the following CPU directories. /sys/devices/system/cpu/cpu0/cpufreq/cpu0 /sys/devices/system/cpu/cpu0/cpufreq/cpu1 5. View the Max Frequency and Min Frequency under CPU0 and CPU1 directory. 6. The Max and Min Frequency did not match as per the Intel specs datasheet. Actual results: /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_max_freq -> 680 /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_min_freq -> 80 /sys/devices/system/cpu/cpu0/cpufreq/cpu0/base_frequency -> 390 Expected results: As per Intel datasheet specification. /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_max_freq -> 5300 MHz /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_min_freq -> 800 MHz /sys/devices/system/cpu/cpu0/cpufreq/cpu0/base_frequency -> 3000 MHz [Fix] cpufreq: intel_pstate: Fix scaling for hybrid-capable systems with disabled E-cores https://github.com/torvalds/linux/commit/0fcfc9e51990246a9813475716746ff5eb98c6aa [github.com] [Test Plan] Same as steps to reproduce [ Where problems could occur ] This issue is seen on Intel based system under development which supports DBS "Demand-Based Power Management", then install Ubuntu-22.04 and boot into OS then check for the frequency values under /sys/devices/system/cpu/cpu0/cpufreq/cpu0 Regression risk = Low to medium [ Other Info ] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/cpuinfo_freq lunar https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/cpuinfo_freq_lunar_2 Mantic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/cpuinfo_freq_mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2022361] Re: Please enable Renesas RZ platform serial installer
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1025.29 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-linux-xilinx-zynqmp'
to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp'
to 'verification-failed-jammy-linux-xilinx-zynqmp'.
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-xilinx-zynqmp-v2
verification-needed-jammy-linux-xilinx-zynqmp
--
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/2022361
Title:
Please enable Renesas RZ platform serial installer
Status in linux package in Ubuntu:
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 Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[Impact]
The ubuntu installer does not work via serial ports for Renesas boards like
RZ/G2M-HiHope
(https://www.renesas.com/us/en/products/microcontrollers-microprocessors/rz-mpus/rzg2m-hihope-rzg2m-reference-board,
RZ/G2L, RZ/G2LC, RZ/G2UL SMARC Board
(https://renesas.info/wiki/RZ-G/RZ-G2L_SMARC).
The installation can be done using HDMI ports, but it would be nice to
support installation via serial port as well.
[Test case]
Try to install Ubuntu on a Renesas board.
[Fix]
Statically build SuperH SCI(F) serial port support (with
earlyconsole).
[Regression potential]
Statically building an additional driver in the kernel can make the
kernel image bigger, potentially causing boot issues in small (arm64 /
armhf) platforms.
[Original bug report]
Package: linux
Version: Ubuntu-6.2.0-21.21
Severity: normal
File: /mantic/debian.master/config/annotations
Dear Maintainer,
The ubuntu kernel is missing a few configuration options for Renesas
RZ/G2M MPU as below:
#Modify the following config from m to y.
CONFIG_SERIAL_SH_SCI=y
#add below configuration
CONFIG_SERIAL_SH_SCI_CONSOLE=y
CONFIG_SERIAL_SH_SCI_EARLYCON=y
The above changes are required in annotations file:
"/mantic/debian.master/config/annotations"
code location:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/mantic/tree/debian.master/config/annotations#n11372
#Modify the following line (change 'm' to 'y')
CONFIG_SERIAL_SH_SCI policy<{'arm64': 'y', 'armhf': 'y'}>
#Add the following lines:
CONFIG_SERIAL_SH_SCI_CONSOLE policy<{'arm64': 'y', 'armhf': 'y'}>
CONFIG_SERIAL_SH_SCI_EARLYCON policy<{'arm64': 'y', 'armhf': 'y'}>
Could you please add those configuration options to the Ubuntu kernel?
Best Regards
John
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022361/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019880] Re: ubuntu_kernel_selftests:net:vrf-xfrm-tests.sh: 8 failed test cases on jammy/fips
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1025.29 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-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'. 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-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp -- 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/2019880 Title: ubuntu_kernel_selftests:net:vrf-xfrm-tests.sh: 8 failed test cases on jammy/fips Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: These failures happen on all supported architectures, when fips=1. When fips=0, all test cases pass. Results are shown below: make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/src/linux' TAP version 13 1..1 # selftests: net: vrf-xfrm-tests.sh # # No qdisc on VRF device # TEST: IPv4 no xfrm policy [ OK ] # TEST: IPv6 no xfrm policy [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy with VRF in selector [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy with xfrm device [FAIL] # TEST: IPv6 xfrm policy with xfrm device [FAIL] # # netem qdisc on VRF device # TEST: IPv4 no xfrm policy [ OK ] # TEST: IPv6 no xfrm policy [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy with VRF in selector [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy with xfrm device [FAIL] # TEST: IPv6 xfrm policy with xfrm device [FAIL] # # Tests passed: 6 # Tests failed: 8 not ok 1 selftests: net: vrf-xfrm-tests.sh # exit=1 make: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests/net' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2019880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945989] Re: Check for changes relevant for security certifications
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1025.29 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-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'. 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-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp -- 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/1945989 Title: Check for changes relevant for security certifications Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [Impact] When producing a new version of some kernels, we need to check for changes that might affect FIPS or other certs and justify why a commit was kept or removed. To simplify this process we can add an automated check that will abort the kernel preparation and build when such changes exist without a justification. [Test Plan] Check if the kernel preparation fails (cranky close) when one of a security certification changes is added. [Where problems could occur] No kernels should be affected until we enable this check on each one. Even when enabled, that only affects the kernel preparation and not the resulting kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033007] Re: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1025.29 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-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'. 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-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp -- 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/2033007 Title: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [Impact] The kdump service operates by utilizing the kexec_file_load system call, which loads a new kernel image intended for subsequent execution. However, this process encounters a hindrance if the CONFIG_KEXEC_IMAGE_VERIFY_SIG option isn't enabled to facilitate signature verification. In addition, a noteworthy point is that if the kernel image is signed with a MOK, it will face rejection due to ARM64's reliance solely on the .builtin_trusted_keys for verification purposes. To enhance flexibility, it's suggested that we align the behavior on x86 platforms. This alignment could potentially involve expanding the scope to encompass more keyrings, such as .secondary_trusted_keys and platform keyrings, thereby broadening the options available for verification mechanisms. [Fix] Enabling the CONFIG_KEXEC_IMAGE_VERIFY_SIG option is necessary, along with the incorporation of two specific commits, in order to enhance the capabilities of the kexec_file_load system call on ARM64. The commits that need to be applied are as follows: c903dae8941d kexec, KEYS: make the code in bzImage64_verify_sig generic 0d519cadf751 arm64: kexec_file: use more system keyrings to verify kernel image signature [Test Plan] 1. Set up a VM with UEFI secure boot and enabled kernel lockdown on ARM64 2. Install 'kdump-tools' sudo apt install linux-crashdump 3. Reboot and verify kdump status with 'kdump-config show' root@ubuntu:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_COREDIR:/var/crash crashkernel addr: 0xde00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-78-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-78-generic current state:Not ready to kdump kexec command: /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-79-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz 4. Check the log using 'systemctl status kdump-tools' Aug 24 06:08:39 ubuntu systemd[1]: Starting Kernel crash dump capture service... Aug 24 06:08:39 ubuntu kdump-tools[1750]: Starting kdump-tools: Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/vmlinuz Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/initrd.img Aug 24 06:08:39 ubuntu kdump-tools[1755]: * /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-78-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz Aug 24 06:08:41 ubuntu kernel: [ 403.301008] Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7 Aug 24 06:08:41 ubuntu kdump-tools[1755]: * failed to load kdump kernel Aug 24 06:08:41 ubuntu kdump-tools: failed to load kdump kernel Aug 24 06:08:41 ubuntu systemd[1]: Finished Kernel crash dump capture service. [Where problems could occur] The problem is specific to kexec image signature verification on ARM64. This change allows additional keyrings and impacts only the ARM64 kexec_file_load system call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 2019868] Re: ubuntu_kernel_selftests:net:tls: 88 failed test cases on jammy/fips
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1025.29 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-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'. 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-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp -- 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/2019868 Title: ubuntu_kernel_selftests:net:tls: 88 failed test cases on jammy/fips Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: These failures happen on all supported architectures, when fips=1. When fips=0, all test cases pass. The results are shown below: make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/src/linux' TAP version 13 1..1 # selftests: net: tls # TAP version 13 # 1..179 # # Starting 179 tests from 6 test cases. # # RUN global.non_established ... # #OK global.non_established # ok 1 global.non_established # # RUN global.keysizes ... # #OK global.keysizes # ok 2 global.keysizes # # RUN tls_basic.base_base ... # #OK tls_basic.base_base # ok 3 tls_basic.base_base # # RUN tls.12_gcm.sendfile ... # #OK tls.12_gcm.sendfile # ok 4 tls.12_gcm.sendfile # # RUN tls.12_gcm.send_then_sendfile ... # #OK tls.12_gcm.send_then_sendfile # ok 5 tls.12_gcm.send_then_sendfile # # RUN tls.12_gcm.recv_max ... # #OK tls.12_gcm.recv_max # ok 6 tls.12_gcm.recv_max # # RUN tls.12_gcm.recv_small ... # #OK tls.12_gcm.recv_small # ok 7 tls.12_gcm.recv_small # # RUN tls.12_gcm.msg_more ... # #OK tls.12_gcm.msg_more # ok 8 tls.12_gcm.msg_more # # RUN tls.12_gcm.msg_more_unsent ... # #OK tls.12_gcm.msg_more_unsent # ok 9 tls.12_gcm.msg_more_unsent # # RUN tls.12_gcm.sendmsg_single ... # #OK tls.12_gcm.sendmsg_single # ok 10 tls.12_gcm.sendmsg_single # # RUN tls.12_gcm.sendmsg_fragmented ... # #OK tls.12_gcm.sendmsg_fragmented # ok 11 tls.12_gcm.sendmsg_fragmented # # RUN tls.12_gcm.sendmsg_large ... # #OK tls.12_gcm.sendmsg_large # ok 12 tls.12_gcm.sendmsg_large # # RUN tls.12_gcm.sendmsg_multiple ... # #OK tls.12_gcm.sendmsg_multiple # ok 13 tls.12_gcm.sendmsg_multiple # # RUN tls.12_gcm.sendmsg_multiple_stress ... # #OK tls.12_gcm.sendmsg_multiple_stress # ok 14 tls.12_gcm.sendmsg_multiple_stress # # RUN tls.12_gcm.splice_from_pipe ... # #OK tls.12_gcm.splice_from_pipe # ok 15 tls.12_gcm.splice_from_pipe # # RUN tls.12_gcm.splice_from_pipe2 ... # #OK tls.12_gcm.splice_from_pipe2 # ok 16 tls.12_gcm.splice_from_pipe2 # # RUN tls.12_gcm.send_and_splice ... # #OK tls.12_gcm.send_and_splice # ok 17 tls.12_gcm.send_and_splice # # RUN tls.12_gcm.splice_to_pipe ... # #OK tls.12_gcm.splice_to_pipe # ok 18 tls.12_gcm.splice_to_pipe # # RUN tls.12_gcm.recvmsg_single ... # #OK tls.12_gcm.recvmsg_single # ok 19 tls.12_gcm.recvmsg_single # # RUN tls.12_gcm.recvmsg_single_max ... # #OK tls.12_gcm.recvmsg_single_max # ok 20 tls.12_gcm.recvmsg_single_max # # RUN tls.12_gcm.recvmsg_multiple ... # #OK tls.12_gcm.recvmsg_multiple # ok 21 tls.12_gcm.recvmsg_multiple # # RUN tls.12_gcm.single_send_multiple_recv ... # #OK tls.12_gcm.single_send_multiple_recv # ok 22 tls.12_gcm.single_send_multiple_recv # # RUN tls.12_gcm.multiple_send_single_recv ... # #OK tls.12_gcm.multiple_send_single_recv # ok 23 tls.12_gcm.multiple_send_single_recv # # RUN tls.12_gcm.single_send_multiple_recv_non_align ... # #OK
[Kernel-packages] [Bug 2032176] Re: Crashing with CPU soft lock on GA kernel 5.15.0.79.76 and HWE kernel 5.19.0-46.47-22.04.1
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1025.29 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-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'. 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-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp -- 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/2032176 Title: Crashing with CPU soft lock on GA kernel 5.15.0.79.76 and HWE kernel 5.19.0-46.47-22.04.1 Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: Impact: We had reports of VM setups which would show intermediate crashes and after that locking up completely. This could be reproduced with large memory setups. The problem seems to be that fixes to performance regressions caused more problems in 5.15 kernels and the full fixes are too intrusive to be backported. Fix: The following patch was recently sent to the upstream stable mailing list and looks to be making its way into linux-5.15.y. This changes the default value of kvm.tdp_mmu to off (if anyone is willing to take the risks, this can be changed back in config). Regression potential: VM hosts with many large memory tennants might see a performance impact which the TDP MMU approach tried to solve. If those did not see other problems they might turn this on again. Testcase: Large openstack instance (64GB memory, AMD CPU (using SVM)) with a large second level guest (32GB memory). Repeatedly starting and stopping the 2nd level guest. --- original description --- The crash occurred on a juju machine, and the juju agent was lost. The juju machine is on an openstack instance provision by juju. The openstack console log indicts the it is related to spin_lock and KVM MMU: [418200.348830] ? _raw_spin_lock+0x22/0x30 [418200.349588] _raw_write_lock+0x20/0x30 [418200.350196] kvm_tdp_mmu_map+0x2b1/0x490 [kvm] [418200.351014] kvm_mmu_notifier_invalidate_range_start+0x1ad/0x300 [kvm] [418200.351796] direct_page_fault+0x206/0x310 [kvm] [418200.352667] __mmu_notifier_invalidate_range_start+0x91/0x1b0 [418200.353624] kvm_tdp_page_fault+0x72/0x90 [kvm] [418200.354496] try_to_migrate_one+0x691/0x730 [418200.355436] kvm_mmu_page_fault+0x73/0x1c0 [kvm] openstack console log: https://pastebin.canonical.com/p/spmH8r3crQ/ syslog: https://pastebin.canonical.com/p/wFPsFD8G9n/ The syslog was rotated after the crash occurred, so the syslog at the time of the initial crash was lost. Other juju machine with 5.15.0.79.76 kernel seems to have the same issues. We previously have a similar issue with 5.15.0-73. The juju machine crashed with raw_spin_lock and kvm mmu in the logs as well: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026229 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack CloudPlatform: openstack CloudSubPlatform: metadata (http://169.254.169.254) Date: Mon Aug 21 08:59:46 2023 Ec2AMI: ami-0c61 Ec2AMIManifest: FIXME Ec2AvailabilityZone: availability-zone-1 Ec2InstanceType: builder-cpu4-ram72-disk20 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 23 03:23 seq crw-rw 1 root audio 116, 33 Aug 23 03:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 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 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack
[Kernel-packages] [Bug 2028122] Re: Fix unreliable ethernet cable detection on I219 NIC
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1025.29 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-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'. 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-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp -- 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/2028122 Title: Fix unreliable ethernet cable detection on I219 NIC Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] Hotplugging RJ45 ethernet cable only works for one time because ACPI GPE wake doesn't working properly anymore. [Fix] Always use PME poll to read PCI PME to know if there's wake event. [Test] With the patch applied, ethernet cable can always be detected. [Where problems could occur] PME poll mechanism periodically reads the PMCTRL register, so the power consumption can be slightly higher. The increase will be very low, probably won't be noticeable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2028122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform
Add debdiff for ivsc-driver/mantic since it's landed in Noble already. This is identical to that in ivsc-driver/noble except for the version string. It's a version bump, as we need this for linux-oem-6.5 builds that tracks ivsc-driver/mantic. ** Patch added: "ivsc-driver_0~git202212210258.94ecb88b-0ubuntu0.23.10.3~ppa.2.debdiff" https://bugs.launchpad.net/ubuntu/mantic/+source/ivsc-driver/+bug/2031412/+attachment/5717465/+files/ivsc-driver_0~git202212210258.94ecb88b-0ubuntu0.23.10.3~ppa.2.debdiff ** Changed in: ipu6-drivers (Ubuntu Mantic) Status: Triaged => In Progress ** Changed in: ivsc-driver (Ubuntu Mantic) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2031412 Title: Support mipi camera on Intel Meteor Lake platform Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: Fix Released Status in ivsc-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ipu6-drivers source package in Jammy: Won't Fix Status in ivsc-driver source package in Jammy: Won't Fix Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in ipu6-drivers source package in Mantic: In Progress Status in ivsc-driver source package in Mantic: In Progress Status in linux source package in Mantic: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in ipu6-drivers source package in Noble: Fix Released Status in ivsc-driver source package in Noble: Fix Released Status in linux source package in Noble: Triaged Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justification] == ipu6-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Based on upstream tag https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019, and an additional patch to enable/fix compilation of additional sensor modules. [Test Case] This is verified on MTL Lattice and VSC platforms, as well as previous generations e.g. TGL and ADL. To actually verify the camera framework: ``` $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel $ sudo apt install linux-oem-22.04d-exp $ sudo apt install linux-modules-ipu6-oem-22.04d-exp $ sudo apt install linux-modules-ivsc-oem-22.04d-exp $ sudo apt install linux-modules-usbio-oem-22.04d-exp $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` And then browse https://webcamtests.com/ for testing. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == ivsc-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] 4 commits from the latest trunk branch on upstream repository https://github.com/intel/ivsc-driver. [Test Case] With all other changes in position, Intel VSC driver modules are to be loaded as a soft dependency of some selected camera sensor modules. LJCA modules should be loaded automatically on MTL platforms as well. To actually verify the camera framework: ``` $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel $ sudo apt install linux-oem-22.04d-exp $ sudo apt install linux-modules-ipu6-oem-22.04d-exp $ sudo apt install linux-modules-ivsc-oem-22.04d-exp $ sudo apt install linux-modules-usbio-oem-22.04d-exp $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` And then browse https://webcamtests.com/ for testing. [Where problems could occur] While it changes how LJCA modules match from ACPI ID, it's also tested and verified on previous generations using IVSC, e.g. TGL, ADL. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == linux/linux-oem-6.5 == [Impact] Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on MTL. [Fix] Two fixes in need. One, we need IOMMU passthrough for
[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform
Add debdiff for ipu6-drivers/mantic since it's landed in Noble already. This is identical to that in ipu6-drivers/noble except for the version string. It's a version bump, as we need this for linux-oem-6.5 builds that tracks ipu6-drivers/mantic. ** Patch added: "SRU ipu6-drivers/mantic" https://bugs.launchpad.net/ubuntu/mantic/+source/ivsc-driver/+bug/2031412/+attachment/5717464/+files/ipu6-drivers_0~git202310180730.3f813580-0ubuntu0.23.10.1~exp.1.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2031412 Title: Support mipi camera on Intel Meteor Lake platform Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: Fix Released Status in ivsc-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ipu6-drivers source package in Jammy: Won't Fix Status in ivsc-driver source package in Jammy: Won't Fix Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in ipu6-drivers source package in Mantic: In Progress Status in ivsc-driver source package in Mantic: In Progress Status in linux source package in Mantic: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in ipu6-drivers source package in Noble: Fix Released Status in ivsc-driver source package in Noble: Fix Released Status in linux source package in Noble: Triaged Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justification] == ipu6-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Based on upstream tag https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019, and an additional patch to enable/fix compilation of additional sensor modules. [Test Case] This is verified on MTL Lattice and VSC platforms, as well as previous generations e.g. TGL and ADL. To actually verify the camera framework: ``` $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel $ sudo apt install linux-oem-22.04d-exp $ sudo apt install linux-modules-ipu6-oem-22.04d-exp $ sudo apt install linux-modules-ivsc-oem-22.04d-exp $ sudo apt install linux-modules-usbio-oem-22.04d-exp $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` And then browse https://webcamtests.com/ for testing. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == ivsc-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] 4 commits from the latest trunk branch on upstream repository https://github.com/intel/ivsc-driver. [Test Case] With all other changes in position, Intel VSC driver modules are to be loaded as a soft dependency of some selected camera sensor modules. LJCA modules should be loaded automatically on MTL platforms as well. To actually verify the camera framework: ``` $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel $ sudo apt install linux-oem-22.04d-exp $ sudo apt install linux-modules-ipu6-oem-22.04d-exp $ sudo apt install linux-modules-ivsc-oem-22.04d-exp $ sudo apt install linux-modules-usbio-oem-22.04d-exp $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` And then browse https://webcamtests.com/ for testing. [Where problems could occur] While it changes how LJCA modules match from ACPI ID, it's also tested and verified on previous generations using IVSC, e.g. TGL, ADL. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == linux/linux-oem-6.5 == [Impact] Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on MTL. [Fix] Two fixes in need. One, we need IOMMU passthrough for MTL platform. The other, fix is for handshake pin support for Lattice MIPI aggregator. The Intel IPU6 camera drivers are not yet all upstreamed yet. So far Intel VSC, LJCA (the previous MIPI
[Kernel-packages] [Bug 2042999] Re: BT/WiFi coex stability issue on RTL8851BE/RTL8852BE
** Tags added: kern-8499
--
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/2042999
Title:
BT/WiFi coex stability issue on RTL8851BE/RTL8852BE
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
New
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Lunar:
In Progress
Status in linux-firmware source package in Mantic:
In Progress
Bug description:
[SRU Justifcation]
[Impact]
On platforms with RTL8851BE/RTL8852BE, bluetooth mouse/keyboard may not work
smoothly with WiFi connection activated.
[Fix]
Proposed firmware upstreamed as:
* 2afd1423e476 ("rtw89: 8852b: update fw to v0.29.29.5")
* 7a916315fb28 ("rtw89: 8852b: update fw to v0.29.29.4")
* 02df6e4f03c0 ("rtw89: 8851b: update fw to v0.29.41.3")
[Test Case]
1. Install Ubuntu 22.04 on SUT with RTL8851BE / 8852BE Wlan card
2. Connected BT KB/MS, and then connected WIFI, select an AP to connect
3. Check BT mouse/keyboard, mouse movement, keyboard key pressing not respond
smoothly.
[Where problems could occur]
This updates opaque firmware blobs, so anything could happen. With
verifications
from multiparties, it improves the stability and no other problem found so
far.
[Other Info]
On Lunar, we don't have RTL8851BE enabled, so the related commits are omitted.
On Mantic and oem-6.5/jammy, we have both.
== original bug report ==
1.Install Ubuntu 22.04 on SUT with RTL8851BE / 8852BE Wlan card
2.Connected BT KB/MS,and then connected WIFI, select an AP to connect
3.Check BT mouse/keyboard, mouse movement, keyboard key pressing not respond
smoothly.
Proposed firmware upstreamed as:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2afd1423e4765eb691711ea5e78a19853cb2f6eb
("rtw89: 8852b: update fw to v0.29.29.5")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=7a916315fb2889aa4b89a71b4eb0b18e5d6153a9
("rtw89: 8852b: update fw to v0.29.29.4")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=02df6e4f03c08fe95c8967a69b86d2c1165400d6
("rtw89: 8851b: update fw to v0.29.41.3")
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042999/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477]
I've tried install Fedora 39 from bootable ISO and there are not working mouse and keyboard in installation area. Lenovo V15 G4 AMN -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: New Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Status in Fedora: New Bug description: [Impact] Keyboard and touchpad doesn't work on some recent systems, and also s2idle is broken. [Fix] Two upstream commits. 128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility 3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops [Test case] boot a fixed kernel and test that input and s2idle works. [Where problems could occur] A buggy bios could maybe advertise a system being PCAT compatible when it's not, though in such a case it might have been already caught before. -- Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042853] Re: [UBUNTU 23.04] Kernel config option missing for s390 PCI passthrough
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: linux (Ubuntu Noble)
Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned)
--
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/2042853
Title:
[UBUNTU 23.04] Kernel config option missing for s390 PCI passthrough
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Lunar:
New
Status in linux source package in Mantic:
New
Status in linux source package in Noble:
New
Bug description:
=== Description by mjros...@us.ibm.com ===
LP#1853306 / IBM bug 182254 backported the necessary kernel pieces to
enable enhanced interpretation of PCI passthrough on s390. It also
included a kernel config update for CONFIG_VFIO_PCI_ZDEV_KVM=y which
is necessary to activate this kernel feature.
For lunar and mantic, the kernel code did not require backporting due
to the base kernel version already containing it, but the kernel
config option still needs to be enabled. Comparison from
git.launchpad.net:
Jammy:
cat debian.master/config/annotations | grep CONFIG_VFIO_PCI_ZDEV_KVM
CONFIG_VFIO_PCI_ZDEV_KVMpolicy<{'s390x': 'y'}>
CONFIG_VFIO_PCI_ZDEV_KVMnote<'LP#1853306 Enable VFIO
zPCI pass-through for s390x'>
Lunar:
cat debian.master/config/annotations | grep CONFIG_VFIO_PCI_ZDEV_KVM
CONFIG_VFIO_PCI_ZDEV_KVMpolicy<{'s390x': 'n'}>
Mantic:
cat debian.master/config/annotations | grep CONFIG_VFIO_PCI_ZDEV_KVM
CONFIG_VFIO_PCI_ZDEV_KVMpolicy<{'s390x': 'n'}>
This setting is supposed to default y when S390 && KVM via Kconfig.
Can this be enabled for lunar, mantic, and future releases?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2042853/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477]
> I've tried install Fedora 39 from bootable ISO and there are not working > mouse and keyboard in installation area. Lenovo V15 G4 AMN This is expected, F39's images use 6.5.6 as kernel and the fixes for this are only available in 6.5.10 and later. So you need to either install 6.5.10 for your current distribution (most distributions have some mainline kernel repository somewhere) or install Fedora 39 using an usb keyboard + mouse and then install all updates and after that things should work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: New Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Status in Fedora: New Bug description: [Impact] Keyboard and touchpad doesn't work on some recent systems, and also s2idle is broken. [Fix] Two upstream commits. 128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility 3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops [Test case] boot a fixed kernel and test that input and s2idle works. [Where problems could occur] A buggy bios could maybe advertise a system being PCAT compatible when it's not, though in such a case it might have been already caught before. -- Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477]
yeah, after update kernel everything okay. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: New Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Status in Fedora: New Bug description: [Impact] Keyboard and touchpad doesn't work on some recent systems, and also s2idle is broken. [Fix] Two upstream commits. 128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility 3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops [Test case] boot a fixed kernel and test that input and s2idle works. [Where problems could occur] A buggy bios could maybe advertise a system being PCAT compatible when it's not, though in such a case it might have been already caught before. -- Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform
Need sponsors for Mantic SRU. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2031412 Title: Support mipi camera on Intel Meteor Lake platform Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: Fix Released Status in ivsc-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ipu6-drivers source package in Jammy: Won't Fix Status in ivsc-driver source package in Jammy: Won't Fix Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in ipu6-drivers source package in Mantic: In Progress Status in ivsc-driver source package in Mantic: In Progress Status in linux source package in Mantic: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in ipu6-drivers source package in Noble: Fix Released Status in ivsc-driver source package in Noble: Fix Released Status in linux source package in Noble: Triaged Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justification] == ipu6-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Based on upstream tag https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019, and an additional patch to enable/fix compilation of additional sensor modules. [Test Case] This is verified on MTL Lattice and VSC platforms, as well as previous generations e.g. TGL and ADL. To actually verify the camera framework: ``` $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel $ sudo apt install linux-oem-22.04d-exp $ sudo apt install linux-modules-ipu6-oem-22.04d-exp $ sudo apt install linux-modules-ivsc-oem-22.04d-exp $ sudo apt install linux-modules-usbio-oem-22.04d-exp $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` And then browse https://webcamtests.com/ for testing. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == ivsc-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] 4 commits from the latest trunk branch on upstream repository https://github.com/intel/ivsc-driver. [Test Case] With all other changes in position, Intel VSC driver modules are to be loaded as a soft dependency of some selected camera sensor modules. LJCA modules should be loaded automatically on MTL platforms as well. To actually verify the camera framework: ``` $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel $ sudo apt install linux-oem-22.04d-exp $ sudo apt install linux-modules-ipu6-oem-22.04d-exp $ sudo apt install linux-modules-ivsc-oem-22.04d-exp $ sudo apt install linux-modules-usbio-oem-22.04d-exp $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` And then browse https://webcamtests.com/ for testing. [Where problems could occur] While it changes how LJCA modules match from ACPI ID, it's also tested and verified on previous generations using IVSC, e.g. TGL, ADL. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == linux/linux-oem-6.5 == [Impact] Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on MTL. [Fix] Two fixes in need. One, we need IOMMU passthrough for MTL platform. The other, fix is for handshake pin support for Lattice MIPI aggregator. The Intel IPU6 camera drivers are not yet all upstreamed yet. So far Intel VSC, LJCA (the previous MIPI aggregator for ADL/RPL platforms) are in v6.6 already, and IPU6 ISYS is under upstream review. More components to come according to Intel. These two fixes are therefore for related components for not-yet fully upstreamed IPU6 as needed for out-of-tree dkms drivers. [Test Case] ``` $ sudo dmesg | grep "Passthrough IOMMU for integrated Intel IPU" $ sudo dmesg | grep int3472 # should have no "int3472-discrete INT3472:0c:
[Kernel-packages] [Bug 2025054] Re: snap-kernel-uc22 lacks atheros firmware
** Also affects: canonical-kernel-snaps/jammy Importance: Undecided Status: New ** Changed in: canonical-kernel-snaps/jammy Status: New => Fix Committed ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Invalid ** Changed in: canonical-kernel-snaps Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2025054 Title: snap-kernel-uc22 lacks atheros firmware Status in canonical-kernel-snaps: Confirmed Status in canonical-kernel-snaps uc22 series: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Bug description: [Summary] The Atheros firmware files aren't available in the snap-kernel-uc22 snap, used in Ubuntu Core Desktop, so the Bluetooth module in Asus Zenbook UX21-e (and probably in a lot more devices) doesn't work. [Steps to reproduce] Boot, from a power-down state, a device with an Atheros-based Bluetooth module, into Ubuntu Core Desktop, open a root terminal and type bluetoothctl devices It returns the error 'No default controller available', because the Bluetooth module firmware wasn't loaded. Now, from a power-down state, boot into an Ubuntu live session (for example, from an USB pendrive), and when the desktop appears, reboot the computer (without powering it down) into Ubuntu Core Desktop and type again in a root terminal bluetoothctl devices This time there is no error, because the Bluetooth device firmware was already loaded in the Ubuntu live session. [Expected result] The call to `bluetoothctl devices` should not return any error. [Actual result] The call to `bluetoothctl devices` returns the 'No default controller available' error. [Failure rate] 3/3 [Stage] Patch available to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-kernel-snaps/+bug/2025054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023201 Title: Add support of Smart Amplifier IC ALC1319D on Intel platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in firmware-sof source package in Lunar: Fix Committed Status in linux source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in firmware-sof source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: SRU Justification for firmware-sof [Impact] To support Smart Amplifier IC ALC1319D, it requires sof-bin v2.2.6 [Fix] Pull sof-bin v2.2.6 and for the completeness pull in v2.2.5, too [Test Case] Install the fixes on the target platform(RPL Dell SKU 0BDA) and verify the audio function. 1. Install the firmware-sof on platform(RPL) with Audio Smart AMP IC ALC1319D 2. Make sure the audio works 3. Also try above steps on other platforms(ADL/TGL) to make sure the audio keep working. [Where problems could occur] New firmware may affect ADL, RPL, and TGL platforms, we need to verify it on not only the target platform, but other existing platforms. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2.2.5 https://github.com/thesofproject/sof-bin/releases/tag/v2.2.6 [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040140] Re: Add soundwire support on Intel MTL platform
*** This bug is a duplicate of bug 2029281 *** https://bugs.launchpad.net/bugs/2029281 While the required kernel commits for ALC713 has been in oem-6.5 kernel, there is no more work to do except firmware-sof SRU that is also a part of 2029281. Mark as duplicate and move private bug binding there. ** This bug has been marked a duplicate of bug 2029281 Soundwire support for Dell SKU0C87 devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2040140 Title: Add soundwire support on Intel MTL platform Status in HWE Next: New Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.5 package in Ubuntu: New Status in firmware-sof source package in Jammy: New Status in linux source package in Jammy: Incomplete Status in linux-oem-6.5 source package in Jammy: In Progress Status in firmware-sof source package in Mantic: New Status in linux source package in Mantic: Incomplete Status in linux-oem-6.5 source package in Mantic: New Bug description: SRU Jusitification for firmware-sof [Impact] Since Intel MTL platform introduces ALC713 codec, remove ALC 714. DMIC is connected to ALC 713, the audio functions fail to work by the change. [Fix] Pull sof-bin v2.7 [Test Case] Install the fixes on the target platform(MTL) and verify the audio function. 1. Install the firmware-sof on platform(MTL) of following codec combination ALC713+ALC1308. ALC713+ALC1308. ALC714+ALC1318 2. Make sure the all audio functions work, include audio play and capture [Where problems could occur] New firmware may affect MTL platforms, we need to verify it only on the target platform. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2023.09 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2040140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029281] Re: Soundwire support for Dell SKU0C87 devices
** Tags added: originate-from-2012814 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2029281 Title: Soundwire support for Dell SKU0C87 devices Status in HWE Next: New Status in firmware-sof package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Triaged Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in firmware-sof source package in Mantic: Triaged Status in linux source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2029281 [Impact] Missing soundwire support for Dell SKU0C87 deivces. [Fix] * bin: https://github.com/thesofproject/sof/pull/7911 * kernel: https://github.com/thesofproject/linux/pull/4468 [Test Case] Test audio functions on Tributo MTL platforms. [Where problems could occur] New devices, may need further polishments. [Other Info] This is for Intel MTL based platforms, so only OEM-6.5, Mantic, and Unstable are nominated for fix. == original bug description == kernel: sof-audio-pci-intel-mtl :00:1f.3: hda codecs found, mask 4 kernel: sof-audio-pci-intel-mtl :00:1f.3: Direct firmware load for intel/sof-ipc4/mtl/sof-mtl.ri failed with error -2 kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof firmware file is missing, you might need to kernel: sof-audio-pci-intel-mtl :00:1f.3: download it from https://github.com/thesofproject/sof-bin/ kernel: sof-audio-pci-intel-mtl :00:1f.3: error: failed to load DSP firmware -2 kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof_probe_work failed err: -2 kernel: kauditd_printk_skb: 33 callbacks suppressed Required fixes: * bin: https://github.com/thesofproject/sof/pull/7911 * kernel: https://github.com/thesofproject/linux/pull/4468 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2029281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029281] Re: Soundwire support for Dell SKU0C87 devices
Attach proposed debdiff for Noble. Note while this change actually contains two binary patches that cannot be renederred correctly by debdiff, it's also pushed to https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2029281 for further inspection. Need sponsor for uploading. ** Patch added: "firmware-sof_2.2.6-1ubuntu2~ppa.1.noble.debdiff" https://bugs.launchpad.net/ubuntu/mantic/+source/firmware-sof/+bug/2029281/+attachment/5717482/+files/firmware-sof_2.2.6-1ubuntu2~ppa.1.noble.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2029281 Title: Soundwire support for Dell SKU0C87 devices Status in HWE Next: New Status in firmware-sof package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Triaged Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in firmware-sof source package in Mantic: Triaged Status in linux source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2029281 [Impact] Missing soundwire support for Dell SKU0C87 deivces. [Fix] * bin: https://github.com/thesofproject/sof/pull/7911 * kernel: https://github.com/thesofproject/linux/pull/4468 [Test Case] Test audio functions on Tributo MTL platforms. [Where problems could occur] New devices, may need further polishments. [Other Info] This is for Intel MTL based platforms, so only OEM-6.5, Mantic, and Unstable are nominated for fix. == original bug description == kernel: sof-audio-pci-intel-mtl :00:1f.3: hda codecs found, mask 4 kernel: sof-audio-pci-intel-mtl :00:1f.3: Direct firmware load for intel/sof-ipc4/mtl/sof-mtl.ri failed with error -2 kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof firmware file is missing, you might need to kernel: sof-audio-pci-intel-mtl :00:1f.3: download it from https://github.com/thesofproject/sof-bin/ kernel: sof-audio-pci-intel-mtl :00:1f.3: error: failed to load DSP firmware -2 kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof_probe_work failed err: -2 kernel: kauditd_printk_skb: 33 callbacks suppressed Required fixes: * bin: https://github.com/thesofproject/sof/pull/7911 * kernel: https://github.com/thesofproject/linux/pull/4468 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2029281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029281] Re: Soundwire support for Dell SKU0C87 devices
** Description changed:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2029281
+
+ == firmware-sof ==
+
+ [Impact]
+
+ Missing soundwire firmware support for Intel MTL deivces.
+
+ [Fix]
+
+ Depends on sof-bin v2.7.1 release from
https://github.com/thesofproject/sof-bin/tree/v2023.09.1. Two commits
specifically:
+ *
https://github.com/thesofproject/sof-bin/commit/ad8dfcc182d3e0a5ce06a7fe9ed7717a04cad06b
("Add sof-v2.7 for Intel Meteor Lake hardware")
+ *
https://github.com/thesofproject/sof-bin/commit/5f010669084d64df29d77a436b6ffa0095565668
("Add more sof-v2.7.1 Intel MTL binaries")
+
+ [Test Case]
+
+ Test audio functions on Tributo MTL platforms.
+
+ [Where problems could occur]
+
+ New devices, may need further polishments.
+
+ [Other Info]
+
+ This is for Intel MTL based platforms, so oem-6.5/jammy is the target
+ series, and Mantic for best effort MTL support. Noble is also nominated
+ of course.
+
+ == linux ==
[Impact]
Missing soundwire support for Dell SKU0C87 deivces.
[Fix]
* bin: https://github.com/thesofproject/sof/pull/7911
* kernel: https://github.com/thesofproject/linux/pull/4468
[Test Case]
Test audio functions on Tributo MTL platforms.
[Where problems could occur]
New devices, may need further polishments.
[Other Info]
This is for Intel MTL based platforms, so only OEM-6.5, Mantic, and
Unstable are nominated for fix.
== original bug description ==
kernel: sof-audio-pci-intel-mtl :00:1f.3: hda codecs found, mask 4
kernel: sof-audio-pci-intel-mtl :00:1f.3: Direct firmware load for
intel/sof-ipc4/mtl/sof-mtl.ri failed with error -2
kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof firmware file is
missing, you might need to
kernel: sof-audio-pci-intel-mtl :00:1f.3: download it from
https://github.com/thesofproject/sof-bin/
kernel: sof-audio-pci-intel-mtl :00:1f.3: error: failed to load DSP
firmware -2
kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof_probe_work failed
err: -2
kernel: kauditd_printk_skb: 33 callbacks suppressed
Required fixes:
* bin: https://github.com/thesofproject/sof/pull/7911
* kernel: https://github.com/thesofproject/linux/pull/4468
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2029281
Title:
Soundwire support for Dell SKU0C87 devices
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Triaged
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in firmware-sof source package in Mantic:
Triaged
Status in linux source package in Mantic:
Fix Released
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2029281
== firmware-sof ==
[Impact]
Missing soundwire firmware support for Intel MTL deivces.
[Fix]
Depends on sof-bin v2.7.1 release from
https://github.com/thesofproject/sof-bin/tree/v2023.09.1. Two commits
specifically:
*
https://github.com/thesofproject/sof-bin/commit/ad8dfcc182d3e0a5ce06a7fe9ed7717a04cad06b
("Add sof-v2.7 for Intel Meteor Lake hardware")
*
https://github.com/thesofproject/sof-bin/commit/5f010669084d64df29d77a436b6ffa0095565668
("Add more sof-v2.7.1 Intel MTL binaries")
[Test Case]
Test audio functions on Tributo MTL platforms.
[Where problems could occur]
New devices, may need further polishments.
[Other Info]
This is for Intel MTL based platforms, so oem-6.5/jammy is the target
series, and Mantic for best effort MTL support. Noble is also
nominated of course.
== linux ==
[Impact]
Missing soundwire support for Dell SKU0C87 deivces.
[Fix]
* bin: https://github.com/thesofproject/sof/pull/7911
* kernel: https://github.com/thesofproject/linux/pull/4468
[Test Case]
Test audio functions on Tributo MTL platforms.
[Where problems could occur]
New devices, may need further polishments.
[Other Info]
This is for Intel MTL based platforms, so only OEM-6.5, Mantic, and
Unstable are nominated for fix.
== original bug description ==
kernel: sof-audio-pci-intel-mtl :00:1f.3: hda codecs found, mask 4
kernel: sof-audio-pci-intel-mtl :00:1f.3: Direct firmware load for
intel/sof-ipc4/mtl/sof-mtl.ri failed with error -2
kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof firmware file is
missing, you might need to
kernel: sof-audio-pci-intel-mtl :00:1f.3: download it from
https://github.com/thesofproject/sof-bin/
kernel: sof-audio-pci-intel-mtl
[Kernel-packages] [Bug 2029281] Re: Soundwire support for Dell SKU0C87 devices
Turn Mantic/Jammy to TRIAGED as there are already revisions in -proposed pocket. To SRU for Noble first. ** Changed in: firmware-sof (Ubuntu) Status: Incomplete => In Progress ** Changed in: firmware-sof (Ubuntu Jammy) Status: Incomplete => Triaged ** Changed in: firmware-sof (Ubuntu Mantic) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2029281 Title: Soundwire support for Dell SKU0C87 devices Status in HWE Next: New Status in firmware-sof package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Triaged Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in firmware-sof source package in Mantic: Triaged Status in linux source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2029281 [Impact] Missing soundwire support for Dell SKU0C87 deivces. [Fix] * bin: https://github.com/thesofproject/sof/pull/7911 * kernel: https://github.com/thesofproject/linux/pull/4468 [Test Case] Test audio functions on Tributo MTL platforms. [Where problems could occur] New devices, may need further polishments. [Other Info] This is for Intel MTL based platforms, so only OEM-6.5, Mantic, and Unstable are nominated for fix. == original bug description == kernel: sof-audio-pci-intel-mtl :00:1f.3: hda codecs found, mask 4 kernel: sof-audio-pci-intel-mtl :00:1f.3: Direct firmware load for intel/sof-ipc4/mtl/sof-mtl.ri failed with error -2 kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof firmware file is missing, you might need to kernel: sof-audio-pci-intel-mtl :00:1f.3: download it from https://github.com/thesofproject/sof-bin/ kernel: sof-audio-pci-intel-mtl :00:1f.3: error: failed to load DSP firmware -2 kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof_probe_work failed err: -2 kernel: kauditd_printk_skb: 33 callbacks suppressed Required fixes: * bin: https://github.com/thesofproject/sof/pull/7911 * kernel: https://github.com/thesofproject/linux/pull/4468 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2029281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040337] Re: Incorrect argument from SEV live-migration fix
This bug is awaiting verification that the linux-gcp/5.4.0-1118.127 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-gcp' to 'verification-done-focal- linux-gcp'. If the problem still exists, change the tag 'verification- needed-focal-linux-gcp' to 'verification-failed-focal-linux-gcp'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-gcp-v2 verification-needed-focal-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2040337 Title: Incorrect argument from SEV live-migration fix Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: Fix Committed Status in linux-gcp source package in Jammy: Fix Committed Bug description: [Impact] * Google requested fix to notify_range_enc_status_changed() passing incorrect argument. [Fix] * Upstream ac3f9c9f1b37 introduced change to notify_range_enc_status_changed() to accept page size instead of number of pages, but function was not updated. Updating to send correct argument. Upstream implementation changed with TDX support, and is unaffected, so no plans to upstream. [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00367134 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2040337/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039732] Re: No graphic desktop environment on Google GCP instances
This bug is awaiting verification that the linux-gcp/6.5.0-1009.9 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-mantic-linux-gcp' to 'verification-done-mantic- linux-gcp'. If the problem still exists, change the tag 'verification- needed-mantic-linux-gcp' to 'verification-failed-mantic-linux-gcp'. 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-mantic-linux-gcp-v2 verification-needed-mantic-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2039732 Title: No graphic desktop environment on Google GCP instances Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Google reports not being able to display graphic desktop environment. [Fix] * CONFIG_SYSFB_SIMPLEFB was initially enabled in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next=0bf2a2472f71a3001a8a9a0849b6bed7e7069a7b. It was subsequently disabled for amd64 in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next=40b0ce0833309133453c3dbc19753f62084c0a7a. This was not reflected in the GCP kernel config. [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression. Simple config change that was not taken from generic. [Other Info] * SF #00366439 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039732/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028999] Re: Slow download speed kubuntu 23.04 starting from kernel 6.2.0-25
installing r8168-dkms seems to better the result, but not completely solve it. Suggested here: https://askubuntu.com/q/1488178 Afterwards download is 920 mbit and upload 400 mbit, should be 980/980 mbit. -- 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/2028999 Title: Slow download speed kubuntu 23.04 starting from kernel 6.2.0-25 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading kernel to linux-image-6.2.0-25-generic (or -26), I experience slow download speed (20-30Mbps instead of the expected 500Mbps-1Gbps). This happens with firefox, chrome, chromium and wget. Upload speeds are ok. Downloads in LAN seems not to be affected. Only from the Internet (i.e.: speedtest.net with firefox/chrome/chromium or some big ISO files downloads). When booting with older kernel, i.e. 6.2.0-24, the problem disappear. My network card is a Realtek, see attached lspci output, and is using r8169 module. PC is a Dell Optiplex 3080 /proc/version_signature: Ubuntu 6.2.0-26.26-generic 6.2.13 lspci output is attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!
I don't use ceph but I'm seeing this spammed across my Ubuntu 23.10
machines. Is it a false alarm then?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2037214
Title:
evict_inodes inode xxx, i_count = 1, was skipped!
Status in linux package in Ubuntu:
Confirmed
Status in linux-oem-6.5 package in Ubuntu:
Confirmed
Bug description:
Hi,
during boot the kernel logs the following messages:
# dmesg | grep evict_inodes
[ 12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
[ 12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
[ 12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
[ 12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
[ 12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!
Those messages are not displayed when I boot my system with a mainline Linux
kernel.
Moreover, in the mainline Linux source code, I do not find the lines where
such a message could be printed.
Therefore, those messages are probably caused by an Ubuntu patch.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-5-generic 6.5.0-5.5
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bonnaudl 4827 F wireplumber
/dev/snd/seq:bonnaudl 4808 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 14:39:10 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901266] Re: system sluggish, thermal keep frequency at 400MHz
This bug report has not seen any further follow-up for 2+ years. Closing it. If it is still not fixed please re-open this issue. ** Changed in: thermald (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1901266 Title: system sluggish, thermal keep frequency at 400MHz Status in thermald package in Ubuntu: Fix Released Bug description: This morning I upgraded to 20.10 from 20.04 The system was quite slow although I have a fast machine. My virtual windows 10 on virtualbox became unusable. When I tried to have the virtual machine open, I could not participate properly in a zoom call (I could still hear the people but they said that my voice was very choppy) On 20.04 I was super-happy with the speed and I could have as many apps running as I want. Based on google I started looking at % journalctl --follow and this shows quite a few errors but not repeating often enough to explain it. Then I googled some more and found that /boot/efi was writing and reading. Then I googled some more and thought I had trouble with gnome. So I reset it to default % dconf reset -f /org/gnome/ and disabled the extensions. This made things slightly better but by far not acceptable. After lots of searching I checked the frequency of the CPUs and it was at the minimum 400Hz (as shown by i7z and also other tools). I tried setting the governor with cpufreqctl and similar methods but this did not change anything. I then found an old bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769236 and tried % sudo systemctl stop thermald this seems to work. After a few seconds the frequency shown in i7z goes to ~4500 MHz and the virtual machine seems to work fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: thermald 2.3-4 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 24 01:39:40 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+merion+X66 InstallationDate: Installed on 2019-09-27 (392 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: thermald UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago) mtime.conffile..etc.thermald.thermal-conf.xml: 2020-10-24T01:35:59.781865 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1901266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738534] Re: Processor turbo disabled/throttled after suspend
** Summary changed: - Processor turbo dsiabled/throttled after suspend + Processor turbo disabled/throttled after suspend -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1738534 Title: Processor turbo disabled/throttled after suspend Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: New Bug description: After suspending/resuming my laptop on battery power, I noticed choppy video playback. I've narrowed it down to the CPU being locked to lower frequencies after suspend/resume (only on battery). Plugging the laptop back in does not restore the normal performance, nor does suspend/resume after plugging it back in. The performance doesn't drop until after the suspend/resume, I'm not sure if it is _supposed_ to throttle when on battery, but either way the behaviour is wrong. Doing a full shutdown and restart restores the performance to normal. Prior to a suspend/resume cycle, cpupower reports: $ sudo cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 3.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 3.00 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 1.26 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes 2800 MHz max turbo 4 active cores 2800 MHz max turbo 3 active cores 2800 MHz max turbo 2 active cores 3000 MHz max turbo 1 active cores Afterwards, the frequency is clamped (cpufreq-set -r --max=3.0GHz has no effect) and turbo is disabled: $ sudo cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 3.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 1.80 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 950 MHz (asserted by call to kernel) boost state support: Supported: no Active: no 2800 MHz max turbo 4 active cores 2800 MHz max turbo 3 active cores 2800 MHz max turbo 2 active cores 3000 MHz max turbo 1 active cores Trying to re-enable turbo mode by setting the no_turbo intel_pstate /sys/ entry back to 0 is rejected: $ echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo 0 tee: /sys/devices/system/cpu/intel_pstate/no_turbo: Operation not permitted However, these two commands *do* work around the problem, forcing turbo mode back on and then restoring the normal frequency range: sudo x86_energy_perf_policy --turbo-enable 1 sudo cpufreq-set -r --min=0.8GHz --max=3.0GHz I also see this error in dmesg after some resumes (but the above problem sometimes happens without this error message): Dec 16 11:36:25 shauns-laptop kernel: intel_pstate: Turbo disabled by BIOS or unavailable on processor ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-19-generic 4.13.0-19.22 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaun 1194 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 16 11:18:12 2017 InstallationDate: Installed on 2017-12-14 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 001 Device 004: ID 2232:1024 Silicon Motion Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-19-generic root=UUID=7352de8c-0017-44e1-81fb-0145ad9c1185 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A
[Kernel-packages] [Bug 2043136] [NEW] Bluetooth prpblem
Public bug reported: It is always disconnected, I tried with Shell and Blueman, but both are not good. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 9 22:42:12 2023 InstallationDate: Installed on 2023-08-10 (90 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2043136 Title: Bluetooth prpblem Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: It is always disconnected, I tried with Shell and Blueman, but both are not good. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 9 22:42:12 2023 InstallationDate: Installed on 2023-08-10 (90 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.2 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-6.2/+bug/2043136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
This bug was fixed in the package mutter - 45.0-3ubuntu3.1 --- mutter (45.0-3ubuntu3.1) mantic; urgency=medium * Cherry pick 4 commits to fix SIGKILL on lockscreen. (LP: #2034619) * Drop kms-impl-device-Inhibit-deadline-timer-on-amdgpu.patch -- Mario Limonciello Thu, 26 Oct 2023 10:27:44 -0500 ** Changed in: mutter (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042564] Re: Performance regression in the 5.15 Ubuntu 20.04 kernel compared to 5.4 Ubuntu 20.04 kernel
I have identified the cause of the fio/glusterfs crash and the EXT4-fs errors: The test procedure runs fio write tests on /dev/sda (which is in fact the rootfs itself). I modified Phil's launch script to create a smaller 10GB boot disk for the rootfs but also create a 50GB "junk" disk (/dev/sdb) to use for the fio test: https://paste.ubuntu.com/p/9Gp7rqR2yG/ (modified launch script) Then, run the fio test like so: # NOTE: /dev/sdb instead of /dev/sda sudo fio --ioengine=libaio --blocksize=4k --readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sdb This yields a clean test run (no crash, no EXT4 corruption errors) with either kernel version, however I still see the same performance degradation with 5.15-generic vs 5.4-kvm running on the focal cloudimg. For the record, I also tested updating glusterfs and libaio to the most modern versions, with no effect (but again, the "glusterfs crash" was a red herring). -- 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/2042564 Title: Performance regression in the 5.15 Ubuntu 20.04 kernel compared to 5.4 Ubuntu 20.04 kernel Status in linux package in Ubuntu: New Status in linux source package in Focal: New Bug description: We in the Canonical Public Cloud team have received report from our colleagues in Google regarding a potential performance regression with the 5.15 kernel vs the 5.4 kernel on ubuntu 20.04. Their test were performed using the linux-gkeop and linux-gkeop-5.15 kernels. I have verified with the generic Ubuntu 20.04 5.4 linux-generic and the Ubuntu 20.04 5.15 linux-generic-hwe-20.04 kernels. The tests were run using `fio` fio commands: * 4k initwrite: `fio --ioengine=libaio --blocksize=4k --readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sdc` * 4k overwrite: `fio --ioengine=libaio --blocksize=4k --readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sdc` My reproducer was to launch an Ubuntu 20.04 cloud image locally with qemu the results are below: Using 5.4 kernel ``` ubuntu@cloudimg:~$ uname --kernel-release 5.4.0-164-generic ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k --readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sda fiojob1: (g=0): rw=write, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=128 ... fio-3.16 Starting 8 processes Jobs: 8 (f=8): [W(8)][99.6%][w=925MiB/s][w=237k IOPS][eta 00m:01s] fiojob1: (groupid=0, jobs=8): err= 0: pid=2443: Thu Nov 2 09:15:22 2023 write: IOPS=317k, BW=1237MiB/s (1297MB/s)(320GiB/264837msec); 0 zone resets slat (nsec): min=628, max=37820k, avg=7207.71, stdev=101058.61 clat (nsec): min=457, max=56099k, avg=340.45, stdev=1707823.38 lat (usec): min=23, max=56100, avg=3229.78, stdev=1705.80 clat percentiles (usec): | 1.00th=[ 775], 5.00th=[ 1352], 10.00th=[ 1647], 20.00th=[ 2024], | 30.00th=[ 2343], 40.00th=[ 2638], 50.00th=[ 2933], 60.00th=[ 3261], | 70.00th=[ 3654], 80.00th=[ 4146], 90.00th=[ 5014], 95.00th=[ 5932], | 99.00th=[ 8979], 99.50th=[10945], 99.90th=[18220], 99.95th=[22676], | 99.99th=[32113] bw ( MiB/s): min= 524, max= 1665, per=100.00%, avg=1237.72, stdev=20.42, samples=4232 iops: min=134308, max=426326, avg=316855.16, stdev=5227.36, samples=4232 lat (nsec) : 500=0.01%, 750=0.01%, 1000=0.01% lat (usec) : 4=0.01%, 10=0.01%, 20=0.01%, 50=0.01%, 100=0.01% lat (usec) : 250=0.05%, 500=0.54%, 750=0.37%, 1000=0.93% lat (msec) : 2=17.40%, 4=58.02%, 10=22.01%, 20=0.60%, 50=0.07% lat (msec) : 100=0.01% cpu : usr=3.29%, sys=7.45%, ctx=1262621, majf=0, minf=103 IO depths: 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0% submit: 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0% complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.1% issued rwts: total=0,83886080,0,8 short=0,0,0,0 dropped=0,0,0,0 latency : target=0, window=0, percentile=100.00%, depth=128 Run status group 0 (all jobs): WRITE: bw=1237MiB/s (1297MB/s), 1237MiB/s-1237MiB/s (1297MB/s-1297MB/s), io=320GiB (344GB), run=264837-264837msec Disk stats (read/write): sda: ios=36/32868891, merge=0/50979424, ticks=5/27498602, in_queue=1183124, util=100.00% ``` After upgrading to linux-generic-hwe-20.04 kernel and rebooting ``` ubuntu@cloudimg:~$ uname --kernel-release 5.15.0-88-generic ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k
[Kernel-packages] [Bug 2039151] Re: Support speaker mute hotkey for Cirrus CS35L41 HDA codec
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1007.7 --- linux-oem-6.5 (6.5.0-1007.7) jammy; urgency=medium * jammy/linux-oem-6.5: 6.5.0-1007.7 -proposed tracker (LP: #2041654) * Support speaker mute hotkey for Cirrus CS35L41 HDA codec (LP: #2039151) - ALSA: hda: cs35l41: Support systems with missing _DSD properties - ALSA: hda: cs35l41: Fix the loop check in cs35l41_add_dsd_properties - ALSA: hda: cs35l41: Add notification support into component binding - ALSA: hda/realtek: Support ACPI Notification framework via component binding - ALSA: hda: cs35l41: Support mute notifications for CS35L41 HDA - ALSA: hda: cs35l41: Add read-only ALSA control for forced mute * Unable to power off the system with MTL CPU (LP: #2039405) - Revert "x86/smp: Put CPUs into INIT on shutdown if possible" * Support mipi camera on Intel Meteor Lake platform (LP: #2031412) - SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs on Meteor Lake - SAUCE: platform/x86: int3472: Add handshake GPIO function * Miscellaneous upstream changes - Revert "UBUNTU: SAUCE: modpost: support arbitrary symbol length in modversion" - Revert "UBUNTU: [Packaging] ZSTD compress modules" [ Ubuntu: 6.5.0-10.10 ] * mantic/linux: 6.5.0-10.10 -proposed tracker (LP: #2039204) * CVE-2023-4921 - net: sched: sch_qfq: Fix UAF in qfq_dequeue() * CVE-2023-42756 - netfilter: ipset: Fix race between IPSET_CMD_CREATE and IPSET_CMD_SWAP * CVE-2023-4881 - netfilter: nftables: exthdr: fix 4-byte stack OOB write * CVE-2023-5197 - netfilter: nf_tables: disallow rule removal from chain binding -- Timo Aaltonen Fri, 27 Oct 2023 15:50:55 +0300 ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-42756 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4881 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4921 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5197 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2039151 Title: Support speaker mute hotkey for Cirrus CS35L41 HDA codec Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Incomplete Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Some systems use a special hotkey to mute speaker audio. On systems using CS35L41 HDA which have this hotkey, add a mechanism which uses ACPI notifications to detect whether the hotkey is triggered to switch the mute state. [Fix] Backport the fix from Cirrus on linux-next https://lore.kernel.org/alsa-devel/87fs36egnv.wl-ti...@suse.de/T/#t. [Test Case] 1. Power on the machine with CS35L41 HDA and the speaker mute hotkey. 2. Verify the audio functions 3. Verify if the speaker can be mute/unmute by the hotkey. [Where problems could occur] Only affect specific laptops with the CS35L41 HDA and the speaker mute hotkey on keyboard. The impact is restricted. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2039151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039405] Re: Unable to power off the system with MTL CPU
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1007.7 --- linux-oem-6.5 (6.5.0-1007.7) jammy; urgency=medium * jammy/linux-oem-6.5: 6.5.0-1007.7 -proposed tracker (LP: #2041654) * Support speaker mute hotkey for Cirrus CS35L41 HDA codec (LP: #2039151) - ALSA: hda: cs35l41: Support systems with missing _DSD properties - ALSA: hda: cs35l41: Fix the loop check in cs35l41_add_dsd_properties - ALSA: hda: cs35l41: Add notification support into component binding - ALSA: hda/realtek: Support ACPI Notification framework via component binding - ALSA: hda: cs35l41: Support mute notifications for CS35L41 HDA - ALSA: hda: cs35l41: Add read-only ALSA control for forced mute * Unable to power off the system with MTL CPU (LP: #2039405) - Revert "x86/smp: Put CPUs into INIT on shutdown if possible" * Support mipi camera on Intel Meteor Lake platform (LP: #2031412) - SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs on Meteor Lake - SAUCE: platform/x86: int3472: Add handshake GPIO function * Miscellaneous upstream changes - Revert "UBUNTU: SAUCE: modpost: support arbitrary symbol length in modversion" - Revert "UBUNTU: [Packaging] ZSTD compress modules" [ Ubuntu: 6.5.0-10.10 ] * mantic/linux: 6.5.0-10.10 -proposed tracker (LP: #2039204) * CVE-2023-4921 - net: sched: sch_qfq: Fix UAF in qfq_dequeue() * CVE-2023-42756 - netfilter: ipset: Fix race between IPSET_CMD_CREATE and IPSET_CMD_SWAP * CVE-2023-4881 - netfilter: nftables: exthdr: fix 4-byte stack OOB write * CVE-2023-5197 - netfilter: nf_tables: disallow rule removal from chain binding -- Timo Aaltonen Fri, 27 Oct 2023 15:50:55 +0300 ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-42756 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4881 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4921 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5197 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2039405 Title: Unable to power off the system with MTL CPU Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] The commit introduced from v6.4 leads to the power off issue 45e34c8af58f x86/smp: Put CPUs into INIT on shutdown if possible [Fix] The problematic commit has been reverted since v6.6 fbe1bf1e5ff1 Revert "x86/smp: Put CPUs into INIT on shutdown if possible" [Test case] 1. Power up the MTL system 2. Power off the system and make sure it shutdown correctly [Where problems could occur] From the origin commit log, revert the commit may have a protential security issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2039405/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1007.7 --- linux-oem-6.5 (6.5.0-1007.7) jammy; urgency=medium * jammy/linux-oem-6.5: 6.5.0-1007.7 -proposed tracker (LP: #2041654) * Support speaker mute hotkey for Cirrus CS35L41 HDA codec (LP: #2039151) - ALSA: hda: cs35l41: Support systems with missing _DSD properties - ALSA: hda: cs35l41: Fix the loop check in cs35l41_add_dsd_properties - ALSA: hda: cs35l41: Add notification support into component binding - ALSA: hda/realtek: Support ACPI Notification framework via component binding - ALSA: hda: cs35l41: Support mute notifications for CS35L41 HDA - ALSA: hda: cs35l41: Add read-only ALSA control for forced mute * Unable to power off the system with MTL CPU (LP: #2039405) - Revert "x86/smp: Put CPUs into INIT on shutdown if possible" * Support mipi camera on Intel Meteor Lake platform (LP: #2031412) - SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs on Meteor Lake - SAUCE: platform/x86: int3472: Add handshake GPIO function * Miscellaneous upstream changes - Revert "UBUNTU: SAUCE: modpost: support arbitrary symbol length in modversion" - Revert "UBUNTU: [Packaging] ZSTD compress modules" [ Ubuntu: 6.5.0-10.10 ] * mantic/linux: 6.5.0-10.10 -proposed tracker (LP: #2039204) * CVE-2023-4921 - net: sched: sch_qfq: Fix UAF in qfq_dequeue() * CVE-2023-42756 - netfilter: ipset: Fix race between IPSET_CMD_CREATE and IPSET_CMD_SWAP * CVE-2023-4881 - netfilter: nftables: exthdr: fix 4-byte stack OOB write * CVE-2023-5197 - netfilter: nf_tables: disallow rule removal from chain binding -- Timo Aaltonen Fri, 27 Oct 2023 15:50:55 +0300 ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-42756 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4881 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4921 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5197 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2031412 Title: Support mipi camera on Intel Meteor Lake platform Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: Fix Released Status in ivsc-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ipu6-drivers source package in Jammy: Won't Fix Status in ivsc-driver source package in Jammy: Won't Fix Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in ipu6-drivers source package in Mantic: In Progress Status in ivsc-driver source package in Mantic: In Progress Status in linux source package in Mantic: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in ipu6-drivers source package in Noble: Fix Released Status in ivsc-driver source package in Noble: Fix Released Status in linux source package in Noble: Triaged Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justification] == ipu6-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Based on upstream tag https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019, and an additional patch to enable/fix compilation of additional sensor modules. [Test Case] This is verified on MTL Lattice and VSC platforms, as well as previous generations e.g. TGL and ADL. To actually verify the camera framework: ``` $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel $ sudo apt install linux-oem-22.04d-exp $ sudo apt install linux-modules-ipu6-oem-22.04d-exp $ sudo apt install linux-modules-ivsc-oem-22.04d-exp $ sudo apt install linux-modules-usbio-oem-22.04d-exp $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` And then browse https://webcamtests.com/ for testing. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == ivsc-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform.
[Kernel-packages] [Bug 2042092] Re: CIFS module is not included in 6.2.0-1016
Related But.. and fixed in this https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042546 -- 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/2042092 Title: CIFS module is not included in 6.2.0-1016 Status in linux-azure package in Ubuntu: Confirmed Bug description: Between 6.2.0-1015 and 6.2.0-1016, the CIFS module was moved from fs/cifs/* to fs/smb/client/*, fs/smb/common/* and fs/smb/server/*. The inclusion list (root/debian.azure-6.2/control.d/azure.inclusion-list) was not updated for this change, so the module is not included in the linux-modules-6.2.0-1026-azure package. WORKAROUND: cifs.ko is provided in the linux-modules-extra-azure (as noted in comment #7); a 'sudo apt install linux-modules-extra-azure' will add it in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2042092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043118] [NEW] Regression CIFS mounted DFS
Public bug reported: On Ubuntu 22.04.3 LTS (jammy jellyfish) we mount a DFS file service using CIFS with kerberos authentication. After the kernel upgrade from 5.15.0-86-generic to 5.15.0-88-generic (exact version: 5.15.0-88.98) this stopped working. The mount seems to have worked, but files and directories are inaccessible. A non-DFS CIFS share mounted on the same client machine is not affected. In our case the filesystem is mounted using autofs with the following mapping: /dfs-share -fstype=cifs,sec=krb5,vers=3,multiuser,noserverino ://example.com/share Kernel log messages: CIFS: Attempting to mount \\example.com\share CIFS: VFS: BAD_NETWORK_NAME: \\example.com\share CIFS: VFS: Verify user has a krb5 ticket and keyutils is installed CIFS: VFS: \\CLx-Ny.EXAMPLE.COM Send error in SessSetup = -126 We confirmed that kernel version 5.15.0-88 causes this by booting different kernel versions repeatedly. When booting 5.15.0-86 everything worked properly as before. Though not familiar with kernel coding, we found changes in the source code that seem to confirm that some code dealing with DFS has changed, moved, or removed. After: git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy This: git diff Ubuntu-5.15.0-86.96 Ubuntu-5.15.0-88.98 -- fs/cifs/cifs_dfs_ref.c This suggests the function cifs_dfs_do_mount() has been (re)moved. ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2043118 Title: Regression CIFS mounted DFS Status in linux-signed package in Ubuntu: New Bug description: On Ubuntu 22.04.3 LTS (jammy jellyfish) we mount a DFS file service using CIFS with kerberos authentication. After the kernel upgrade from 5.15.0-86-generic to 5.15.0-88-generic (exact version: 5.15.0-88.98) this stopped working. The mount seems to have worked, but files and directories are inaccessible. A non-DFS CIFS share mounted on the same client machine is not affected. In our case the filesystem is mounted using autofs with the following mapping: /dfs-share -fstype=cifs,sec=krb5,vers=3,multiuser,noserverino ://example.com/share Kernel log messages: CIFS: Attempting to mount \\example.com\share CIFS: VFS: BAD_NETWORK_NAME: \\example.com\share CIFS: VFS: Verify user has a krb5 ticket and keyutils is installed CIFS: VFS: \\CLx-Ny.EXAMPLE.COM Send error in SessSetup = -126 We confirmed that kernel version 5.15.0-88 causes this by booting different kernel versions repeatedly. When booting 5.15.0-86 everything worked properly as before. Though not familiar with kernel coding, we found changes in the source code that seem to confirm that some code dealing with DFS has changed, moved, or removed. After: git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy This: git diff Ubuntu-5.15.0-86.96 Ubuntu-5.15.0-88.98 -- fs/cifs/cifs_dfs_ref.c This suggests the function cifs_dfs_do_mount() has been (re)moved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2043118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
I have switched to Debian and downloaded the latest kernel from kernel.org. As the current kernel on Debian was 6.1.0-13, I have selected the 6.1.62 kernel source. I have followed the steps and Quinten written earlier, except the patching steps as it is not needed anymore and after installing the compiled kernel, it works perfectly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: New Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Status in Fedora: New Bug description: [Impact] Keyboard and touchpad doesn't work on some recent systems, and also s2idle is broken. [Fix] Two upstream commits. 128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility 3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops [Test case] boot a fixed kernel and test that input and s2idle works. [Where problems could occur] A buggy bios could maybe advertise a system being PCAT compatible when it's not, though in such a case it might have been already caught before. -- Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
Same issue here with Thinkpad P13s Gen 2 (AMD) with 23.10 installed just moments ago I'm also unable to install the fixes on a fresh installation: sudo apt install -t mantic-proposed mutter Reading package lists... Done E: The value 'mantic-proposed' is invalid for APT::Default-Release as such a release is not available in the sources sudo apt install mutter/mantic-proposed Reading package lists... Done Building dependency tree... Done Reading state information... Done Package mutter is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: mutter-common-bin E: Release 'mantic-proposed' for 'mutter' was not found Did I miss something? => mutter-common-bin is already the newest version (45.0-3ubuntu3). -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043125] [NEW] Updating to Linux 5.15.0-90-generic breaks r8152 ethernet on thunderbolt
Public bug reported: Updating from Linux 5.15.0-88-generic to 5.15.0-90-generic breaks ethernet support. In my setup, the ethernet port is inside a Thunderbolt Dell WD19TB docking station. On 5.15.0-88 the ethernet device works and is shown with ip and on dmesg logs : $ sudo dmesg ... 27 [2.260869] r8152 4-1.4:1.0 eth0: v1.12.13 28 [2.268290] r8152 4-1.4:1.0 enxcc483ac3b5f5: renamed from eth0 29 [2.268290] r8152 4-1.4:1.0 enxcc483ac3b5f5: renamed from eth0 30 [7.308677] r8152 4-1.4:1.0 enxcc483ac3b5f5: carrier on 31 [7.523473] IPv6: ADDRCONF(NETDEV_CHANGE): enxcc483ac3b5f5: link becomes ready ... $ ip a [...] 2: enxcc483ac3b5f5: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether cc:48:3a:c3:b5:f5 brd ff:ff:ff:ff:ff:ff inet 192.168.133.178/24 brd 192.168.133.255 scope global dynamic noprefixroute enxcc483ac3b5f5 valid_lft 1760sec preferred_lft 1760sec inet6 fe80::887f:293c:8126:cb43/64 scope link noprefixroute valid_lft forever preferred_lft forever On 5.15.0-90 the device cannot be found. Thanks for looking into this regression. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-90-generic 5.15.0-90.100 ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131 Uname: Linux 5.15.0-90-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: poliveira 1905 F pulseaudio /dev/snd/controlC0: poliveira 1905 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 9 16:58:05 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X79 InstallationDate: Installed on 2020-10-29 (1106 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 IwConfig: lono wireless extensions. wlp59s0 no wireless extensions. MachineType: Dell Inc. Precision 5540 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic root=UUID=52eafe9e-33dc-415d-9dec-5c74761fa536 ro nvidia-drm.modeset=1 mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-90-generic N/A linux-backports-modules-5.15.0-90-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.22 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2023 dmi.bios.release: 1.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.23.0 dmi.board.name: 03G9D9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.23.0:bd07/18/2023:br1.23:svnDellInc.:pnPrecision5540:pvr:rvnDellInc.:rn03G9D9:rvrA00:cvnDellInc.:ct10:cvr:sku0906: dmi.product.family: Precision dmi.product.name: Precision 5540 dmi.product.sku: 0906 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy package-from-proposed ** Summary changed: - Updating to Dell WD19TB breaks r8152 ethernet on thunderbolt + Updating to Linux 5.15.0-90-generic breaks r8152 ethernet on thunderbolt -- 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/2043125 Title: Updating to Linux 5.15.0-90-generic breaks r8152 ethernet on thunderbolt Status in linux package in Ubuntu: New Bug description: Updating from Linux 5.15.0-88-generic to 5.15.0-90-generic breaks ethernet support. In my setup, the ethernet port is inside a Thunderbolt Dell WD19TB docking station. On 5.15.0-88 the ethernet device works and is shown with ip and on dmesg logs : $ sudo dmesg ... 27 [2.260869] r8152 4-1.4:1.0 eth0: v1.12.13 28 [2.268290] r8152 4-1.4:1.0 enxcc483ac3b5f5: renamed from eth0 29 [2.268290] r8152 4-1.4:1.0 enxcc483ac3b5f5: renamed from eth0 30 [7.308677] r8152 4-1.4:1.0 enxcc483ac3b5f5: carrier on 31 [7.523473] IPv6: ADDRCONF(NETDEV_CHANGE): enxcc483ac3b5f5: link becomes ready ... $ ip a [...] 2: enxcc483ac3b5f5: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether cc:48:3a:c3:b5:f5 brd ff:ff:ff:ff:ff:ff inet 192.168.133.178/24 brd 192.168.133.255 scope global dynamic noprefixroute enxcc483ac3b5f5 valid_lft 1760sec preferred_lft 1760sec inet6 fe80::887f:293c:8126:cb43/64 scope link noprefixroute valid_lft forever preferred_lft forever On 5.15.0-90 the device cannot be found. Thanks for looking into this regression. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package:
[Kernel-packages] [Bug 2043132] [NEW] Pull request to enable GDS optimization in the Grace enablement kernel
Public bug reported: These are the same patches that have been applied to the 5.19 and 6.2 kernels to enable GDS. NVIDIA is requesting they be applied to the 6.5 kernel which is used for Grace enablement. ** Affects: linux-nvidia-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2043132 Title: Pull request to enable GDS optimization in the Grace enablement kernel Status in linux-nvidia-6.5 package in Ubuntu: New Bug description: These are the same patches that have been applied to the 5.19 and 6.2 kernels to enable GDS. NVIDIA is requesting they be applied to the 6.5 kernel which is used for Grace enablement. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2043132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
