[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
Hi Guys, would you please enable proposed and install the target kernel(5.19.0-41.42) to verify? thanks a lot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937133] Re: devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute (KeyError: 'flavour')
This bug is awaiting verification that the linux/5.19.0-41.42 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937133 Title: devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute (KeyError: 'flavour') Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Released Bug description: [Impact] On s390x LPAR instances, this test will fail with: # File "linux/tools/testing/selftests/net/devlink_port_split.py", line 64, in get_if_names # if ports[port]['flavour'] == 'physical': # KeyError: 'flavour' not ok 1 selftests: net: devlink_port_split.py # exit=1 This is because the mlx4 driver in use on this instance does not set attributes, therefore `devlink -j port show` command output does not contain this "flavour" key. [Fix] * 3de66d08d3 selftests: net: devlink_port_split.py: skip test if no suitable device available This patch can be cherry-picked into our J/K/L kernels. [Test] Run the patched devlink_port_split.py on s390x LPAR, and it won't fail with # KeyError: 'flavour' but marked as SKIP instead. [Where problems could occur] If this change is incorrect, it may affect the test result, however it's limited to testing tools, no actual impact to kernel functions. [Original Bug Report] Failing on hirsute/linux 5.11.0-26.28 host s2lp4 Not a regression as this is also failing on 5.11.0-24.25 17:16:32 DEBUG| [stdout] # selftests: net: devlink_port_split.py 17:16:32 DEBUG| [stdout] # Traceback (most recent call last): 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 283, in 17:16:32 DEBUG| [stdout] # main() 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 256, in main 17:16:32 DEBUG| [stdout] # ports = devlink_ports(dev) 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 70, in __init__ 17:16:32 DEBUG| [stdout] # self.if_names = devlink_ports.get_if_names(dev) 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 64, in get_if_names 17:16:32 DEBUG| [stdout] # if ports[port]['flavour'] == 'physical': 17:16:32 DEBUG| [stdout] # KeyError: 'flavour' 17:16:32 DEBUG| [stdout] not ok 44 selftests: net: devlink_port_split.py # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1937133/+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 1988346] Re: cm32181 module error blocking suspend
This bug is awaiting verification that the linux/5.19.0-41.42 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process ex
[Kernel-packages] [Bug 2004262] Re: Intel E810 NICs driver in causing hangs when booting and bonds configured
This bug is awaiting verification that the linux/5.19.0-41.42 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-kinetic' to 'verification-done-kinetic'. If the
problem still exists, change the tag 'verification-needed-kinetic' to
'verification-failed-kinetic'.
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-kinetic-linux verification-needed-kinetic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2004262
Title:
Intel E810 NICs driver in causing hangs when booting and bonds
configured
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Status in linux source package in Lunar:
Confirmed
Bug description:
[Impact]
* Intel E810-family NICs cause system hangs when booting with bonding
enabled
* This happens due to the driver unplugging auxiliary devices
* The unplug event happens under RTNL lock context, which causes a deadlock
where the RDMA driver waits for the RNL lock to complete removal
[Test Plan]
* Users have reported that after setting up bonding on switch and server
side, the system will hang when starting network services
[Fix]
* The upstream patch defers unplugging/re-plugging of the auxiliary device,
so that it's not performed under the RTNL lock context.
* Fix was introduced by commit:
248401cb2c46 ice: avoid bonding causing auxiliary plug/unplug under
RTNL lock
[Regression Potential]
* Regressions would manifest in devices that support RDMA functionality and
have been added to a bond
* We should look out for auxiliary devices that haven't been properly
unplugged, or that cause further issues with
ice_plug_aux_dev()/ice_unplug_aux_dev()
[Original Description]
jammy 22.04.1
linux-image-generic 5.15.0-58-generic
Intel E810-XXV Dual Port NICs in Dell PowerEdge 650
- 5.15 in jammy -> reproducible
- 5.19 in hwe-edge -> reproducible
- 6.2.rc6 in the mainline build -> works
- Intel's ice driver 1.10.1.2.2 -> works
After beonding is enabled on switch and server side, the system will
hang at initialing ubuntu. The kernel loads but around starting the
Network Services the system can hang for sometimes 5 minutes, and in
other cases, indefinitely.
The message of:
echo 0 > /proc/sys/kernel/hung_task_timeout_sec” systemd-resolve
blocked for more than 120 seconds
appears, and eventually the Network services just attempts to start
and never does. This is with or without DHCP enabled.
Tried this same setup with the hwe-22.04, hwe-20.04, hwe-22.04-ege and
linux-oem kernels and all exhibit the same failure.
To work around this. installing the Intel 'ice' driver of version
1.10.1.2.2 works. The system doesn't even remotely hang at startup
and all networking functions remain working (ping, DNS, general
accessibility).
The driver can be found at
https://downloadmirror.intel.com/763930/ice-1.10.1.2.2.tar.gz
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jan 31 13:08 seq
crw-rw 1 root audio 116, 33 Jan 31 13:08 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-01-27 (3 days ago)InstallationMedia:
Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Dell Inc. PowerEdge R650
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 mgag200drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic
root=UUID=668aab7c-abe9-434b-a810-acc6eab76cbc ro fsck.mode=skip
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
RelatedPackageVersions:
linux-restricted-modules-5.15.0-58-generic N/A
linux-backports-modules-5.15.0-58-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.9
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'Tags: jammy
uec-images
Uname: Linux 5.15.0-58-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 09/14/2022
dm
[Kernel-packages] [Bug 2006453] Re: Fix selftests/ftracetests/Meta-selftests
This bug is awaiting verification that the linux/5.19.0-41.42 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-kinetic -- 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/2006453 Title: Fix selftests/ftracetests/Meta-selftests Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-6.1 source package in Bionic: 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 Kinetic: Fix Committed Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [SRU Justification] == Impact == This subtest checks for bashisms in the test scripts of ftracetests. A recent stable change added such a case. This is harmless but causes the Meta-selftests to fail. The offending commit is "selftests/ftrace: event_triggers: wait longer for test_event_enable" which adds: + if [ "$e" == $val ]; then == Fix == Replace the test with + if [ "$e" = $val ]; then == Testcase == Running the kernel selftests/ftracetest (done in ADT and RT) should no longer show "Meta-selftests" as FAILed. == Regression Potential == This affects only the selftest suite and only ftrace subtests. Any change would only be observable there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
This bug is awaiting verification that the linux/5.19.0-41.42 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011616] Re: Connection timeout due to conntrack limits
This bug is awaiting verification that the linux/5.19.0-41.42 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-kinetic -- 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/2011616 Title: Connection timeout due to conntrack limits Status in linux package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Status in linux-gcp source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-gcp source package in Kinetic: New Status in linux source package in Lunar: In Progress Status in linux-gcp source package in Lunar: New Bug description: Customers of GKE 1.25 and 1.26 are affected by the conntrack performance issue that causes random connection timeouts. The fix has been committed to to the upstream's net git repo and to prodkernel and needs to be backported to Ubuntu versions with kernel 5.15. https://partnerissuetracker.corp.google.com/issues/272090522 Fix: https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git/commit/?id=c77737b736ceb50fdf150434347dbd81ec76dbb1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011616/+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 2015498] Re: Debian autoreconstruct Fix restoration of execute permissions
This bug is awaiting verification that the linux/5.19.0-41.42 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015498 Title: Debian autoreconstruct Fix restoration of execute permissions Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Confirmed Bug description: SRU justification [Impact] Debian source package diffs cannot represent that a file should be executable. gen-auto-reconstruct detects when a commit adds a script that is supposed to be invoked during the build and restores the execute permissions in the reconstruct script by adding `chmod +x $file`. But, if a file removes its execute permission, this will change it back. This happened in the last jammy release (version 5.15.0-70.77) where a commit from upstream removed the execute permission for a header file but then our scripts brought it back. [Fix] Andy proposed the following fix https://dpaste.com/6SJ8YR3BM Basically it checks if the permission was added or removed and uses either +x or -x. [Test plan] Easily tested with jammy-kvm, latest release where a rebase picked this commit "treewide: fix up files incorrectly marked executable" where `drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h` changed its permission from 755 to 644 (removed execute). When debian packages are prepared, you'll notice the file has changed its permission back to 755. With the fix, it should be the same. [Regression potential] Low, it is a small fix. Scripts will still have execute permission. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015498/+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 2013209] Re: expoline.o is packaged unconditionally for s390x
This bug is awaiting verification that the linux/5.19.0-41.42 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2013209 Title: expoline.o is packaged unconditionally for s390x Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.15 package in Ubuntu: New Status in linux-hwe-5.15 source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Released Bug description: https://bugs.launchpad.net/bugs/1639924 enabled CONFIG_EXPOLINE_EXTERN for s390x in Jammy. While this works as expected on Jammy, it won't work on some derivatives of it: for example focal:hwe-5.15. On Focal, this config can't be enabled due to the GCC version it comes with. CONFIG_EXPOLINE_EXTERN requires >= 110200 while Focal comes with 90400. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013209/+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 2013088] Re: kernel: fix __clear_user() inline assembly constraints
This bug is awaiting verification that the linux/5.19.0-41.42 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013088 Title: kernel: fix __clear_user() inline assembly constraints Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Released Bug description: SRU Justification: == [ Impact ] * In case clear_user() crosses two pages and faults on the second page the kernel may write lowcore contents to the first page, instead of clearing it. * The __clear_user() inline assembly misses earlyclobber constraint modifiers. Depending on compiler and compiler options this may lead to incorrect code which copies kernel lowcore contents to user space instead of clearing memory, in case clear_user() faults. [Fix] * For Kinetic and Jammy cherrypick of 89aba4c26fae 89aba4c26fae4e459f755a18912845c348ee48f3 "s390/uaccess: add missing earlyclobber annotations to __clear_user()" * For Focal and Bionic a backport of the above commit is needed: https://launchpadlibrarian.net/659551648/s390-uaccess.patch [ Test Plan ] * A test program in C is needed and used for testing. * The test will be done by IBM. [ Where problems could occur ] * The modification is limited to function 'long __clear_user'. * And there, just to one inline assembly constraints line. * This is usually difficult to trace. * A erroneous modification may lead to a wrong behavior in 'long __clear_user', * and maybe returning a wrong size (in uaccess.c). [ Other Info ] * This affects all Ubuntu releases in service, down to 18.04. * Since we are close to 23.04 kernel freeze, I submit a patch request for 23.04 separately, and submit the SRU request for the all other Ubuntu releases later. __ Description: kernel: fix __clear_user() inline assembly constraints Symptom: In case clear_user() crosses two pages and faults on the second page the kernel may write lowcore contents to the first page, instead of clearing it. Problem: The __clear_user() inline assembly misses earlyclobber constraint modifiers. Depending on compiler and compiler options this may lead to incorrect code which copies kernel lowcore contents to user space instead of clearing memory, in case clear_user() faults. Solution: Add missing earlyclobber constraint modifiers. Preventive:yes Upstream-ID: 89aba4c26fae4e459f755a18912845c348ee48f3 Affected Releases: 18.04 20.04 22.04 22.10 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2013088/+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 2015956] Re: selftest: fib_tests: Always cleanup before exit
This bug is awaiting verification that the linux/5.19.0-41.42 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2015956 Title: selftest: fib_tests: Always cleanup before exit Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux-oem-6.0 source package in Focal: Invalid Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Copied from the commit message: Usage of `set -e` before executing a command causes immediate exit on failure, without cleanup up the resources allocated at setup. This can affect the next tests that use the same resources, leading to a chain of failures. A simple fix is to always call cleanup function when the script exists. This approach is already used by other existing tests. [Fix] * b60417a9f2 selftest: fib_tests: Always cleanup before exit This patch can be cherry-picked into affected kernels. [Test] Run the patched fib_tests.sh on KVM kernels, which is expected to fail due to bug 2007458. Check with `ip netns`, the ns1 added during setup() should be removed. [Where problems could occur] Test robustness improvement, this should not break things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2015956/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003053] Re: NFS: client permission error after adding user to permissible group
** Bug watch added: Linux Kernel Bug Tracker #217165 https://bugzilla.kernel.org/show_bug.cgi?id=217165 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003053 Title: NFS: client permission error after adding user to permissible group Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: [Impact] The NFS client's access cache becomes stale due to the user's group membership changing on the server after the user has already logged in on the client. The access cache only expires if either NFS_INO_INVALID_ACCESS flag is on or timeout (without delegation). Adding a user to a group in the NFS server will not cause any file attributes to change. The client will encounter permission errors until other file attributes are changed or the memory cache is dropped. [Fix] The access cache shall be cleared once the user logs out and logs back in again. 0eb43812c0270ee3d005ff32f91f7d0a6c4943af NFS: Clear the file access cache upon login 029085b8949f5d269ae2bbd14915407dd0c7f902 NFS: Judge the file access cache's timestamp in rcu path 5e9a7b9c2ea18551759833146a181b14835bfe39 NFS: Fix up a sparse warning [Test Plan] 1.[client side] testuser is not part of testgroup testuser@kinetic:~$ ls -ld /mnt/private/ drwxrwx--- 2 root testgroup 4096 Nov 24 08:23 /mnt/private/ testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied 2.[server side] add testuser into testgroup, which has access to folder root@kinetic:~$ usermod -aG testgroup testuser && echo `date +'%s'` > /proc/net/rpc/auth.unix.gid/flush 3.[client side] create a file again but still fail testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied [Where problems could occur] The fix will apply upstream commits, so the regression can be considered as low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
I'm having the same problem with a Toshiba laptop using an A8-4500 APU (HD 7640G integrated graphics). Still booting 5.19.0-32 so my HDMI audio works. Like others have said, 5.19.0-40 (Ubuntu 22.04) didn't fix it. Hopefully the next one will have the 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007001] Re: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display
Hi everyone, I have submitted the revert to the Kernel Team for SRU: Cover letter: https://lists.ubuntu.com/archives/kernel-team/2023-April/138908.html Patch: https://lists.ubuntu.com/archives/kernel-team/2023-April/138909.html The next step is for the kernel team to review the patch, and for two senior Kernel Team members to ack the patch. At that stage, it will be accepted into the next SRU cycle. You can track the dates for the 2023.05.15 SRU cycle on https://kernel.ubuntu.com/ I will write back once have have two acks from the Kernel Team. Thanks, Matthew -- 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/2007001 Title: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/2007001 [Impact] Numerous VMWare users have reported that vmwgfx cannot reserve the memory region for the graphics framebuffer, leading their VMs to have blank screens. They see the following in dmesg: [ 11.135360] vmwgfx :00:0f.0: BAR 2: can't reserve [mem 0x7000-0x77ff 64bit pref] [ 11.135366] vmwgfx: probe of :00:0f.0 failed with error -16 And a cat /proc/iomem shows this: 5000-7fff : PCI Bus :00 7000-77ff : :00:0f.0 7000-702f : BOOTFB The kernel has failed to release this memory region for vmwgfx to occupy. Most affected users are on aarch64, with the host being Apple silicon systems. [Fix] The regression was introduced by the below commit in 5.19.0-30-generic: commit 5e01376124309b4dbd30d413f43c0d9c2f60edea Author: Thomas Zimmermann Date: Mon Jul 18 09:23:18 2022 +0200 Subject: video/aperture: Disable and unregister sysfb devices via aperture helpers Link: https://github.com/torvalds/linux/commit/5e01376124309b4dbd30d413f43c0d9c2f60edea This commit was part of a larger refactoring of the video subsystem, and requires the entire series to function correctly. You can review the whole series below: https://patchwork.freedesktop.org/series/106040/ The patch series also requires quite a few additional fixups to fix bugs introduced by the series, making the size about 15 commits in total. The contents of the series don't really fix any bugs, and their purpose is to refactor the code for future changes to the fbdev subsystem, and really aren't appropriate to be backported to a stable kernel series. "video/aperture: Disable and unregister sysfb devices via aperture helpers" seems to have been selected for -stable by mistake by its fixes: tag, and was pulled into upstream stable by a robot with little human review. The best course of action is to revert. No action needed for Lunar, as the entire series is present in that release. [Testcase] This bug affects users running Ubuntu in VMWare VMs, notably on aarch64 devices, like modern Apple computers. Start a Kinetic or Jammy-HWE Server or Desktop VM in VMWare Fusion on Apple silicon, and see if the display comes up or not. Affected users will see a blank screen. There is a test kernel available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2007001-test If you install the test kernel and reboot, you will be able to see the screen on your VM like normal. [Where problems could occur] This commit changes when the sysfb is disabled and memory region for the graphics framebuffer is released to the proper device driver. If a regression were to occur, then graphics drivers may fail to reserve the framebuffer memory, and fail to start, leaving users with a blank screen. There are no workarounds, other than booting a previous kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007001/+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 2007001] Re: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display
** Summary changed: - Blank console display with aarch64 kernel 5.19.0-31 + vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display ** Description changed: - Upgraded the kernel on 22.10 aarch64 (running in a VM on VMware Fusion - 13.0.1 on Apple Silicon_ from 5.19.0-29 to 5.19.0-31. After the upgrade - and after rebooting the VM no text or graphical console appears on the - VM. + BugLink: https://bugs.launchpad.net/bugs/2007001 - The VM is running and can be accessed through SSH. + [Impact] - Rebooting the VM with kernel 5.19.0-29 - everything is working as - expected. Text and graphical consoles now display properly. + Numerous VMWare users have reported that vmwgfx cannot reserve the + memory region for the graphics framebuffer, leading their VMs to have + blank screens. - ProblemType: Bug - DistroRelease: Ubuntu 22.10 - Package: linux-image-5.19.0-31-generic 5.19.0-31.32 - ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 - Uname: Linux 5.19.0-31-generic aarch64 - ApportVersion: 2.23.1-0ubuntu3 - Architecture: arm64 - AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: - CRDA: N/A - CasperMD5CheckResult: pass - Date: Sat Feb 11 13:04:22 2023 - InstallationDate: Installed on 2022-09-11 (153 days ago) - InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha arm64 (20220911) - IwConfig: - lono wireless extensions. - - ens160no wireless extensions. - MachineType: VMware, Inc. VMware20,1 - ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash - ProcFB: - - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=5e9795ee-63e3-4df1-93e9-c36cd88c726c ro quiet splash vt.handoff=7 - RelatedPackageVersions: - linux-restricted-modules-5.19.0-31-generic N/A - linux-backports-modules-5.19.0-31-generic N/A - linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 - RfKill: - - SourcePackage: linux - UpgradeStatus: No upgrade log present (probably fresh install) - dmi.bios.date: 12/05/2022 - dmi.bios.vendor: VMware, Inc. - dmi.bios.version: VMW201.00V.20904234.BA64.2212051119 - dmi.board.name: VBSA - dmi.board.vendor: VMware, Inc. - dmi.board.version: 1 - dmi.chassis.type: 1 - dmi.chassis.vendor: VMware, Inc. - dmi.chassis.version: VMware20,1 - dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW201.00V.20904234.BA64.2212051119:bd12/05/2022:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001: - dmi.product.family: VMware - dmi.product.name: VMware20,1 - dmi.product.sku: 0001 - dmi.product.version: 1 - dmi.sys.vendor: VMware, Inc. + They see the following in dmesg: + + [ 11.135360] vmwgfx :00:0f.0: BAR 2: can't reserve [mem 0x7000-0x77ff 64bit pref] + [ 11.135366] vmwgfx: probe of :00:0f.0 failed with error -16 + + And a cat /proc/iomem shows this: + + 5000-7fff : PCI Bus :00 + 7000-77ff : :00:0f.0 + 7000-702f : BOOTFB + + The kernel has failed to release this memory region for vmwgfx to + occupy. + + Most affected users are on aarch64, with the host being Apple silicon + systems. + + [Fix] + + The regression was introduced by the below commit in 5.19.0-30-generic: + + commit 5e01376124309b4dbd30d413f43c0d9c2f60edea + Author: Thomas Zimmermann + Date: Mon Jul 18 09:23:18 2022 +0200 + Subject: video/aperture: Disable and unregister sysfb devices via aperture helpers + Link: https://github.com/torvalds/linux/commit/5e01376124309b4dbd30d413f43c0d9c2f60edea + + This commit was part of a larger refactoring of the video subsystem, and + requires the entire series to function correctly. You can review the + whole series below: + + https://patchwork.freedesktop.org/series/106040/ + + The patch series also requires quite a few additional fixups to fix bugs + introduced by the series, making the size about 15 commits in total. The + contents of the series don't really fix any bugs, and their purpose is + to refactor the code for future changes to the fbdev subsystem, and + really aren't appropriate to be backported to a stable kernel series. + + "video/aperture: Disable and unregister sysfb devices via aperture + helpers" seems to have been selected for -stable by mistake by its + fixes: tag, and was pulled into upstream stable by a robot with little + human review. + + The best course of action is to revert. No action needed for Lunar, as + the entire series is present in that release. + + [Testcase] + + This bug affects users running Ubuntu in VMWare VMs, notably on aarch64 + devices, like modern Apple computers. + + Start a Kinetic or Jammy-HWE Server or Desktop VM in VMWare Fusion on + Apple silicon, and see if the display comes up or not. + + Affected users will see a blank screen. + + There is a test kernel available in the following ppa: + + https://launchpad.net/~m
[Kernel-packages] [Bug 2017013] Re: net: sched: Fix use after free in red_enqueue()
** Also affects: linux-oem (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-oem (Ubuntu Xenial)
** Changed in: linux-oem (Ubuntu)
Status: New => In Progress
** Changed in: linux-oem (Ubuntu)
Importance: Undecided => High
** Changed in: linux-oem (Ubuntu)
Assignee: (unassigned) => Cengiz Can (cengizcan)
** Package changed: linux-oem (Ubuntu) => linux-oem-5.17 (Ubuntu)
** Also affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.14 (Ubuntu)
Status: New => In Progress
** Changed in: linux-oem-5.14 (Ubuntu)
Importance: Undecided => High
** Changed in: linux-oem-5.14 (Ubuntu)
Assignee: (unassigned) => Cengiz Can (cengizcan)
--
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/2017013
Title:
net: sched: Fix use after free in red_enqueue()
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-5.14 package in Ubuntu:
In Progress
Status in linux-oem-5.17 package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
[Impact]
We can't use "skb" again after passing it to qdisc_enqueue(). This is
basically identical to commit 2f09707 ("sch_sfb: Also store skb
len before calling child enqueue").
Fixes: d7f4f33 ("sch_red: update backlog as well")
[Fix]
Cherry picked from upstream.
[Test case]
Compile, boot and basic network functionality tested using ntop.
[Potential regression]
Low. This has been in multiple trees for a while now.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017013/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
The "problem" is inside of kernel-modules. Probably there is some conflict between the snd modules (snd-hda-intel?) and hardware. This is a historical problem of all linux distributions that has been repeating cyclically for many years. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011738] Re: Add ATX related reporting nodes in mlxbf-ptm debugfs driver
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2011738 Title: Add ATX related reporting nodes in mlxbf-ptm debugfs driver Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] mlxbf-ptm is a kernel driver that provides debufgs interface for system software to monitor Bluefield devices' power and thermal management parameters. [Fix] * This change adds additional debugfs nodes that provide ATX status and power profile data. Replaces S_IRUGO with 0444 inline with checkpatch expectation. [Test Case] * After installing the kernel module, debugfs entry at /sys/kernel/debug/mlxbf-ptm will be created * monitors/status folder contains read-only parameters reported from the Bluefield device [Regression Potential] * Minimal - as these are read-only parameters that report Bluefield device information. [Other] * This code is likely to change depending on feedback we received from maintainers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2011738/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
@SiggiTron can confirm, I also still have the same bug. 5.19.0-40 on KDE Neon with RX590 and still no audio. It really sucks at this point - more than a month with shitty audio from 11 years old motherboard. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009271] Re: Too many BDL entries regression
I am also seeing them triggered at random times when pausing and unpausing youtube videos that are playing in Firefox. Even muting and unmuting a video can trigger a flood of the messages and associated audio hangs. In case I didn't mention it, I am currently running 5.19.0-38-generic #39~22.04.1-Ubuntu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009271 Title: Too many BDL entries regression Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: Hello, Thanks for your hard work :) I got this error after kernel update to 5.19.0-35 as explained here : https://askubuntu.com/questions/1457367/snd-hda-intel-001f-3-too-many-bdl-entries-messages-in-system-log and here : https://lore.kernel.org/stable/cab1lbmv1ky+kuubwvxroe+mbqbjtjofvzb8smmbcuy2mdvg...@mail.gmail.com/T/#u A load of syslog "Too many BDL entries" appears. Have a nice week-end, best regards, Laurent Lyaudet ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-35-generic 5.19.0-35.36 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent5004 F wireplumber /dev/snd/controlC1: laurent5004 F wireplumber /dev/snd/seq:laurent5000 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 16:47:55 2023 InstallationDate: Installed on 2020-07-01 (976 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. GL73 8SD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-21 (134 days ago) dmi.bios.date: 03/29/2019 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C7IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-17C7 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1: dmi.product.family: GL dmi.product.name: GL73 8SD dmi.product.sku: 17C7.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017013] Re: net: sched: Fix use after free in red_enqueue()
** Description changed:
+ [Impact]
We can't use "skb" again after passing it to qdisc_enqueue(). This is
basically identical to commit 2f09707 ("sch_sfb: Also store skb
len before calling child enqueue").
Fixes: d7f4f33 ("sch_red: update backlog as well")
+
+ [Fix]
+ Cherry picked from upstream.
+
+ [Test case]
+ Compile, boot and basic network functionality tested using ntop.
+
+ [Potential regression]
+ Low. This has been in multiple trees for a while now.
--
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/2017013
Title:
net: sched: Fix use after free in red_enqueue()
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
In Progress
Bug description:
[Impact]
We can't use "skb" again after passing it to qdisc_enqueue(). This is
basically identical to commit 2f09707 ("sch_sfb: Also store skb
len before calling child enqueue").
Fixes: d7f4f33 ("sch_red: update backlog as well")
[Fix]
Cherry picked from upstream.
[Test case]
Compile, boot and basic network functionality tested using ntop.
[Potential regression]
Low. This has been in multiple trees for a while now.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017013/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
@Nolt, sorry, it's typo. (i mean 5.19-40) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
.sdev_attrs...
That will work.
Great job. This is due to the following patch not applied.
patch "(64fc9015fbeb scsi: smartpqi: Switch to attribute groups)"
2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs
Also due to a contextual difference because of
patch "(64fc9015fbeb scsi: smartpqi: Switch to attribute groups)"
I'll bet it's because of this HUNK:
@@ -7137,6 +7247,7 @@ static struct attribute *pqi_sdev_attrs[] = {
&dev_attr_ssd_smart_path_enabled.attr,
&dev_attr_raid_level.attr,
&dev_attr_raid_bypass_cnt.attr,
+ &dev_attr_sas_ncq_prio_enable.attr,
NULL
};
The structure definition also was changed in this HUNK
-static struct device_attribute *pqi_sdev_attrs[] = {
- &dev_attr_lunid,
- &dev_attr_unique_id,
- &dev_attr_path_info,
- &dev_attr_sas_address,
- &dev_attr_ssd_smart_path_enabled,
- &dev_attr_raid_level,
- &dev_attr_raid_bypass_cnt,
+static struct attribute *pqi_sdev_attrs[] = {
+ &dev_attr_lunid.attr,
+ &dev_attr_unique_id.attr,
+ &dev_attr_path_info.attr,
+ &dev_attr_sas_address.attr,
+ &dev_attr_ssd_smart_path_enabled.attr,
+ &dev_attr_raid_level.attr,
+ &dev_attr_raid_bypass_cnt.attr,
NULL
};
So, needs to be
static struct device_attribute *pqi_sdev_attrs[] = {
and remove all of the .attr suffixes.
c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer
Also due to this HUNK
@@ -7262,6 +7271,7 @@ static struct scsi_host_template pqi_driver_template = {
.map_queues = pqi_map_queues,
.sdev_groups = pqi_sdev_groups,
.shost_groups = pqi_shost_groups,
+ .cmd_size = sizeof(struct pqi_cmd_priv),
};
The context without
patch "(64fc9015fbeb scsi: smartpqi: Switch to attribute groups)"
would be
.shost_attrs = pqi_shost_attrs,
.shost_attrs = pqi_shost_attrs,
The HUNK that changed this is below:
@@ -7153,8 +7157,8 @@ static struct scsi_host_template pqi_driver_template = {
.slave_alloc = pqi_slave_alloc,
.slave_configure = pqi_slave_configure,
.map_queues = pqi_map_queues,
- .sdev_attrs = pqi_sdev_attrs,
- .shost_attrs = pqi_shost_attrs,
+ .sdev_groups = pqi_sdev_groups,
+ .shost_groups = pqi_shost_groups,
};
Hope this helps.
--
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/1998643
Title:
smartpqi: Update 22.04 driver to include recent bug fixes and support
current generation devices
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
Incomplete
Bug description:
[Impact]
These patches provide bug fixes and add support for the latest generation of
OEM PCI devices to ensure customers are able to use Jammy on the recent
generations of server hardware. This will bring us in line with the other major
linux distros.
[Fix]
There are some outstanding patches already in Linus's tree that can be
applied to 22.04.
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
The following patches apply to
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy
f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045
e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year
6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter
2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs
cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints
6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition
69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests
85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures
2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers
44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i
331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang
904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices
297bdc540f0e scsi: smartpqi: Close write read holes
dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers
1d393227fc76 scsi: smartpqi: Add controller fw version to console log
4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal
8946ea283808 scsi: smartpqi: Fix typo in comment
c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer
31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang
62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035
291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses
c66e078ad89e scsi: smartpqi: Fix hibernate and suspend
5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements
c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init
00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives
5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads
27655e9db479 scsi: smartpqi: Update volume size after expansion
b7335
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
@koba you mean that in 5.19-49 this issue is resolved? It's a really annoying bug which is present well through few kernel updates already. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856871] Re: i/o error if next unused loop device is queried
This bug is awaiting verification that the linux/5.4.0-149.166 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856871 Title: i/o error if next unused loop device is queried Status in linux package in Ubuntu: Fix Released Status in parted package in Ubuntu: Invalid Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in udev package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: [Impact] * There's an I/O error on fsync() in a detached loop device if it has been previously attached. The issue is that write cache is enabled in the attach path in loop_configure() but it isn't disabled in the detach path; thus it remains enabled in the block device regardless of whether it is attached or not. * fsync() on detached loop devices can be called by partition tools and commands run by sosreport, so the unexpected kernel error message might surprise users or even distract from the actual issue being investigatedr. It might also trigger alerts in logging/monitoring/alerting stacks [Fix] * Disable write cache in the detach path [Test Plan] * Attach and detach an image to a loop device and test fsync return value aterwards # DEV=/dev/loop7 # IMG=/tmp/image # truncate --size 1M $IMG # losetup $DEV $IMG # losetup -d $DEV Before: # strace -e fsync parted -s $DEV print 2>&1 | grep fsync fsync(3)= -1 EIO (Input/output error) Warning: Error fsyncing/closing /dev/loop7: Input/output error [ 982.529929] blk_update_request: I/O error, dev loop7, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 After: # strace -e fsync parted -s $DEV print 2>&1 | grep fsync fsync(3)= 0 [Where problems could occur] * The detach path for block devices is modified. Worst case scenario would be an error when detaching loop devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856871/+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 2013088] Re: kernel: fix __clear_user() inline assembly constraints
This bug is awaiting verification that the linux/5.4.0-149.166 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013088 Title: kernel: fix __clear_user() inline assembly constraints Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Released Bug description: SRU Justification: == [ Impact ] * In case clear_user() crosses two pages and faults on the second page the kernel may write lowcore contents to the first page, instead of clearing it. * The __clear_user() inline assembly misses earlyclobber constraint modifiers. Depending on compiler and compiler options this may lead to incorrect code which copies kernel lowcore contents to user space instead of clearing memory, in case clear_user() faults. [Fix] * For Kinetic and Jammy cherrypick of 89aba4c26fae 89aba4c26fae4e459f755a18912845c348ee48f3 "s390/uaccess: add missing earlyclobber annotations to __clear_user()" * For Focal and Bionic a backport of the above commit is needed: https://launchpadlibrarian.net/659551648/s390-uaccess.patch [ Test Plan ] * A test program in C is needed and used for testing. * The test will be done by IBM. [ Where problems could occur ] * The modification is limited to function 'long __clear_user'. * And there, just to one inline assembly constraints line. * This is usually difficult to trace. * A erroneous modification may lead to a wrong behavior in 'long __clear_user', * and maybe returning a wrong size (in uaccess.c). [ Other Info ] * This affects all Ubuntu releases in service, down to 18.04. * Since we are close to 23.04 kernel freeze, I submit a patch request for 23.04 separately, and submit the SRU request for the all other Ubuntu releases later. __ Description: kernel: fix __clear_user() inline assembly constraints Symptom: In case clear_user() crosses two pages and faults on the second page the kernel may write lowcore contents to the first page, instead of clearing it. Problem: The __clear_user() inline assembly misses earlyclobber constraint modifiers. Depending on compiler and compiler options this may lead to incorrect code which copies kernel lowcore contents to user space instead of clearing memory, in case clear_user() faults. Solution: Add missing earlyclobber constraint modifiers. Preventive:yes Upstream-ID: 89aba4c26fae4e459f755a18912845c348ee48f3 Affected Releases: 18.04 20.04 22.04 22.10 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2013088/+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 2015440] Re: fib_tests.sh in ubuntu_kernel_selftests was skipped silently on Focal
This bug is awaiting verification that the linux/5.4.0-149.166 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-focal' to 'verification-done-focal'. If the problem
still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-focal-linux verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2015440
Title:
fib_tests.sh in ubuntu_kernel_selftests was skipped silently on Focal
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Bug description:
[Impact]
When applying the following commit via stable update (bug 2011625):
Revert "ipv4: Fix incorrect route flushing when source address is
deleted"
The executable bit of this script was dropped. And this test will be
skipped on 5.4:
# selftests: net: fib_tests.sh
# Warning: file fib_tests.sh is missing!
not ok 1 selftests: net: fib_tests.sh
[Fix]
* f0c95f229a ("selftests: Fix the executable permissions for fib_tests.sh")
This can be cherry-picked to Focal from linux-5.4.y of the stable
tree.
[Test]
Run the test with the patched kernel. This test will not be skipped.
[Where problems could occur]
This change just allow the script to get tested, however we will see
failures reported from this test.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2015440/+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 2015498] Re: Debian autoreconstruct Fix restoration of execute permissions
This bug is awaiting verification that the linux/5.4.0-149.166 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015498 Title: Debian autoreconstruct Fix restoration of execute permissions Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Confirmed Bug description: SRU justification [Impact] Debian source package diffs cannot represent that a file should be executable. gen-auto-reconstruct detects when a commit adds a script that is supposed to be invoked during the build and restores the execute permissions in the reconstruct script by adding `chmod +x $file`. But, if a file removes its execute permission, this will change it back. This happened in the last jammy release (version 5.15.0-70.77) where a commit from upstream removed the execute permission for a header file but then our scripts brought it back. [Fix] Andy proposed the following fix https://dpaste.com/6SJ8YR3BM Basically it checks if the permission was added or removed and uses either +x or -x. [Test plan] Easily tested with jammy-kvm, latest release where a rebase picked this commit "treewide: fix up files incorrectly marked executable" where `drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h` changed its permission from 755 to 644 (removed execute). When debian packages are prepared, you'll notice the file has changed its permission back to 755. With the fix, it should be the same. [Regression potential] Low, it is a small fix. Scripts will still have execute permission. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015498/+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 2015956] Re: selftest: fib_tests: Always cleanup before exit
This bug is awaiting verification that the linux/5.4.0-149.166 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2015956 Title: selftest: fib_tests: Always cleanup before exit Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux-oem-6.0 source package in Focal: Invalid Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Copied from the commit message: Usage of `set -e` before executing a command causes immediate exit on failure, without cleanup up the resources allocated at setup. This can affect the next tests that use the same resources, leading to a chain of failures. A simple fix is to always call cleanup function when the script exists. This approach is already used by other existing tests. [Fix] * b60417a9f2 selftest: fib_tests: Always cleanup before exit This patch can be cherry-picked into affected kernels. [Test] Run the patched fib_tests.sh on KVM kernels, which is expected to fail due to bug 2007458. Check with `ip netns`, the ns1 added during setup() should be removed. [Where problems could occur] Test robustness improvement, this should not break things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2015956/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
Answers below.
From: nore...@launchpad.net on behalf of Michael Reed
<1998...@bugs.launchpad.net>
Sent: Wednesday, April 19, 2023 12:21 PM
To: Don Brace - C33706
Subject: [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug
fixes and support current generation devices
EXTERNAL EMAIL: Do not click links or open attachments unless you know
the content is safe
Hi Don,
Here are the changes I made to the second patch
c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer
drivers/scsi/smartpqi/smartpqi_init.c
@@ -7256,8 +7265,9 @@ static struct scsi_host_template pqi_driver_template = {
.slave_alloc = pqi_slave_alloc,
.slave_configure = pqi_slave_configure,
.map_queues = pqi_map_queues,
- .sdev_attrs = pqi_sdev_attrs,
- .shost_attrs = pqi_shost_attrs,
+ .sdev_groups = pqi_sdev_groups,
+ .shost_groups = pqi_shost_groups,
+ .cmd_size = sizeof(struct pqi_cmd_priv),
};
The issue here is that the added lines cause the build to break. If I didn't
add
+ .sdev_groups = pqi_sdev_groups,
+ .shost_groups = pqi_shost_groups,
and keep
- .sdev_attrs = pqi_sdev_attrs,
- .shost_attrs = pqi_shost_attrs,
My guess is that it will build. I haven't tried it yet but wanted some
guidance.
DON
That will work.
Great job. This is due to the following patch not applied.
patch "(64fc9015fbeb scsi: smartpqi: Switch to attribute groups)"
--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1998643
Title:
smartpqi: Update 22.04 driver to include recent bug fixes and support
current generation devices
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
Incomplete
Bug description:
[Impact]
These patches provide bug fixes and add support for the latest generation of
OEM PCI devices to ensure customers are able to use Jammy on the recent
generations of server hardware. This will bring us in line with the other major
linux distros.
[Fix]
There are some outstanding patches already in Linus's tree that can be
applied to 22.04.
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
The following patches apply to
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy
f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045
e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year
6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter
2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs
cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints
6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition
69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests
85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures
2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers
44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i
331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang
904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices
297bdc540f0e scsi: smartpqi: Close write read holes
dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers
1d393227fc76 scsi: smartpqi: Add controller fw version to console log
4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal
8946ea283808 scsi: smartpqi: Fix typo in comment
c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer
31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang
62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035
291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses
c66e078ad89e scsi: smartpqi: Fix hibernate and suspend
5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements
c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init
00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives
5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads
27655e9db479 scsi: smartpqi: Update volume size after expansion
b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend
42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value
9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io()
b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code
94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer
70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot
2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs
c57ee4ccb358 scsi: smartpqi: Add PCI IDs
c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace
64fc9015fbeb scsi: smartpqi: Switch to attribute groups
0ca190805784 scsi: smartpqi: Call scsi_done() directly
I added the above SHA1 IDs to a file called:
backport_linus_6.1_into_22.04
git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04
git am -s /tmp/patche
[Kernel-packages] [Bug 2016827] Status changed to Confirmed
This change was made by a bot. ** 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/2016827 Title: screen breaks and freezing Status in linux package in Ubuntu: Confirmed Bug description: Just started having issues with the graphics breaking and having boot information when booting both tuning on and shutting down. Now both my web browsers are randomly freezing my pc completely up and having to just turn it off and back on without shutting it down. My fan will run really loud on boot up and for about the next 3 to 4 min after boot, the power consumption has been reduce really bad as well. Thanks for your time hope that I can get this resolved. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-69-generic 5.15.0-69.76 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mjm2086 F pulseaudio /dev/snd/controlC0: mjm2086 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Apr 17 20:19:10 2023 MachineType: HP HP 255 G8 Notebook PC ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=ac398bb2-9ae5-4a95-8511-6f6f88344f20 ro quiet splash loglevel=3 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 15.32 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 87D2 dmi.board.vendor: HP dmi.board.version: 38.25 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 38.25 dmi.modalias: dmi:bvnInsyde:bvrF.32:bd08/02/2022:br15.32:efr38.25:svnHP:pnHP255G8NotebookPC:pvrType1ProductConfigId:rvnHP:rn87D2:rvr38.25:cvnHP:ct10:cvrChassisVersion:sku5U073UT#ABA: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 255 G8 Notebook PC dmi.product.sku: 5U073UT#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016827/+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 2017016] Status changed to Confirmed
This change was made by a bot. ** 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/2017016 Title: package linux-image-5.15.0-69-generic 5.15.0-69.76 failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in linux package in Ubuntu: Confirmed Bug description: no idea ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-69-generic 5.15.0-69.76 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: libxml2:i386: Install libxml2:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lester 2445 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown Date: Wed Apr 19 12:41:02 2023 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2022-02-05 (437 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 80TV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=UUID=94800299-c94b-4ce0-a2b4-a97599c8aeac ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1 SourcePackage: linux Title: package linux-image-5.15.0-69-generic 5.15.0-69.76 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: Upgraded to jammy on 2022-08-23 (238 days ago) dmi.bios.date: 09/23/2016 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: 3JCN21WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Torronto 5C2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-15IKB dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvr3JCN21WW:bd09/23/2016:br1.21:efr1.21:svnLENOVO:pn80TV:pvrLenovoideapad310-15IKB:rvnLENOVO:rnTorronto5C2:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad310-15IKB:skuLENOVO_MT_80TV_BU_idea_FM_Lenovoideapad310-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80TV dmi.product.sku: LENOVO_MT_80TV_BU_idea_FM_Lenovo ideapad 310-15IKB dmi.product.version: Lenovo ideapad 310-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017016/+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 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
Hi Don,
Here are the changes I made to the second patch
c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer
drivers/scsi/smartpqi/smartpqi_init.c
@@ -7256,8 +7265,9 @@ static struct scsi_host_template pqi_driver_template = {
.slave_alloc = pqi_slave_alloc,
.slave_configure = pqi_slave_configure,
.map_queues = pqi_map_queues,
- .sdev_attrs = pqi_sdev_attrs,
- .shost_attrs = pqi_shost_attrs,
+ .sdev_groups = pqi_sdev_groups,
+ .shost_groups = pqi_shost_groups,
+ .cmd_size = sizeof(struct pqi_cmd_priv),
};
The issue here is that the added lines cause the build to break. If I didn't
add
+ .sdev_groups = pqi_sdev_groups,
+ .shost_groups = pqi_shost_groups,
and keep
- .sdev_attrs = pqi_sdev_attrs,
- .shost_attrs = pqi_shost_attrs,
My guess is that it will build. I haven't tried it yet but wanted some
guidance.
--
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/1998643
Title:
smartpqi: Update 22.04 driver to include recent bug fixes and support
current generation devices
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
Incomplete
Bug description:
[Impact]
These patches provide bug fixes and add support for the latest generation of
OEM PCI devices to ensure customers are able to use Jammy on the recent
generations of server hardware. This will bring us in line with the other major
linux distros.
[Fix]
There are some outstanding patches already in Linus's tree that can be
applied to 22.04.
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
The following patches apply to
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy
f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045
e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year
6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter
2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs
cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints
6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition
69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests
85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures
2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers
44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i
331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang
904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices
297bdc540f0e scsi: smartpqi: Close write read holes
dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers
1d393227fc76 scsi: smartpqi: Add controller fw version to console log
4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal
8946ea283808 scsi: smartpqi: Fix typo in comment
c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer
31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang
62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035
291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses
c66e078ad89e scsi: smartpqi: Fix hibernate and suspend
5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements
c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init
00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives
5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads
27655e9db479 scsi: smartpqi: Update volume size after expansion
b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend
42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value
9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io()
b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code
94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer
70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot
2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs
c57ee4ccb358 scsi: smartpqi: Add PCI IDs
c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace
64fc9015fbeb scsi: smartpqi: Switch to attribute groups
0ca190805784 scsi: smartpqi: Call scsi_done() directly
I added the above SHA1 IDs to a file called:
backport_linus_6.1_into_22.04
git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04
git am -s /tmp/patches/*.diff
All patches applied without any conflicts.
[Test Plan]
The upstream driver has undergone extensive testing by Microchip's test team
before submitting those patches to the upstream kernel. All patches are tested
and accepted in the upstream kernel at this time.
One should be able to load the smartpqi driver and verify the version
is at 2.1.18-045
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions
--
Mailing list: https://la
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
Hi Don,
Here are the changes I made to adjust/backport the first patch. Is this
correct?
2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs
drivers/scsi/smartpqi/smartpqi_init.c
@@ -7126,15 +7234,18 @@ static DEVICE_ATTR(sas_address, 0444,
pqi_sas_address_show, NULL);
static DEVICE_ATTR(ssd_smart_path_enabled, 0444,
pqi_ssd_smart_path_enabled_show, NULL);
static DEVICE_ATTR(raid_level, 0444, pqi_raid_level_show, NULL);
static DEVICE_ATTR(raid_bypass_cnt, 0444, pqi_raid_bypass_cnt_show, NULL);
-
-static struct device_attribute *pqi_sdev_attrs[] = {
- &dev_attr_lunid,
- &dev_attr_unique_id,
- &dev_attr_path_info,
- &dev_attr_sas_address,
- &dev_attr_ssd_smart_path_enabled,
- &dev_attr_raid_level,
- &dev_attr_raid_bypass_cnt,
+static DEVICE_ATTR(sas_ncq_prio_enable, 0644,
+ pqi_sas_ncq_prio_enable_show, pqi_sas_ncq_prio_enable_store);
+
+static struct attribute *pqi_sdev_attrs[] = {
+ &dev_attr_lunid.attr,
+ &dev_attr_unique_id.attr,
+ &dev_attr_path_info.attr,
+ &dev_attr_sas_address.attr,
+ &dev_attr_ssd_smart_path_enabled.attr,
+ &dev_attr_raid_level.attr,
+ &dev_attr_raid_bypass_cnt.attr,
+ &dev_attr_sas_ncq_prio_enable.attr,
NULL
};
--
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/1998643
Title:
smartpqi: Update 22.04 driver to include recent bug fixes and support
current generation devices
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
Incomplete
Bug description:
[Impact]
These patches provide bug fixes and add support for the latest generation of
OEM PCI devices to ensure customers are able to use Jammy on the recent
generations of server hardware. This will bring us in line with the other major
linux distros.
[Fix]
There are some outstanding patches already in Linus's tree that can be
applied to 22.04.
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
The following patches apply to
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy
f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045
e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year
6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter
2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs
cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints
6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition
69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests
85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures
2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers
44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i
331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang
904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices
297bdc540f0e scsi: smartpqi: Close write read holes
dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers
1d393227fc76 scsi: smartpqi: Add controller fw version to console log
4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal
8946ea283808 scsi: smartpqi: Fix typo in comment
c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer
31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang
62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035
291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses
c66e078ad89e scsi: smartpqi: Fix hibernate and suspend
5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements
c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init
00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives
5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads
27655e9db479 scsi: smartpqi: Update volume size after expansion
b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend
42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value
9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io()
b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code
94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer
70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot
2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs
c57ee4ccb358 scsi: smartpqi: Add PCI IDs
c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace
64fc9015fbeb scsi: smartpqi: Switch to attribute groups
0ca190805784 scsi: smartpqi: Call scsi_done() directly
I added the above SHA1 IDs to a file called:
backport_linus_6.1_into_22.04
git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04
git am -s /tmp/patches/*.diff
All patches applied without any conflicts.
[Test Plan]
The upstream driver has undergone extensive testing by Microchip's test team
bef
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
Hi Don, I have 2 patches that do not cherry-pick cleanly to the jammy kernel based on master-next tags. git describe --tags Ubuntu-5.15.0-72.79-43-gc85205fa6c05 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer -- 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/1998643 Title: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Incomplete Bug description: [Impact] These patches provide bug fixes and add support for the latest generation of OEM PCI devices to ensure customers are able to use Jammy on the recent generations of server hardware. This will bring us in line with the other major linux distros. [Fix] There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. [Test Plan] The upstream driver has undergone extensive testing by Microchip's test team before submitting those patches to the upstream kernel. All patches are tested and accepted in the upstream kernel at this time. One should be able to load the smartpqi driver and verify the version is at 2.1.18-045 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+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 2017016] Re: package linux-image-5.15.0-69-generic 5.15.0-69.76 failed to install/upgrade: problemas de dependencias - se deja sin configurar
** Tags removed: need-duplicate-check -- 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/2017016 Title: package linux-image-5.15.0-69-generic 5.15.0-69.76 failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in linux package in Ubuntu: New Bug description: no idea ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-69-generic 5.15.0-69.76 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: libxml2:i386: Install libxml2:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lester 2445 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown Date: Wed Apr 19 12:41:02 2023 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2022-02-05 (437 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 80TV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=UUID=94800299-c94b-4ce0-a2b4-a97599c8aeac ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1 SourcePackage: linux Title: package linux-image-5.15.0-69-generic 5.15.0-69.76 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: Upgraded to jammy on 2022-08-23 (238 days ago) dmi.bios.date: 09/23/2016 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: 3JCN21WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Torronto 5C2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-15IKB dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvr3JCN21WW:bd09/23/2016:br1.21:efr1.21:svnLENOVO:pn80TV:pvrLenovoideapad310-15IKB:rvnLENOVO:rnTorronto5C2:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad310-15IKB:skuLENOVO_MT_80TV_BU_idea_FM_Lenovoideapad310-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80TV dmi.product.sku: LENOVO_MT_80TV_BU_idea_FM_Lenovo ideapad 310-15IKB dmi.product.version: Lenovo ideapad 310-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017016/+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 2017016] [NEW] package linux-image-5.15.0-69-generic 5.15.0-69.76 failed to install/upgrade: problemas de dependencias - se deja sin configurar
Public bug reported: no idea ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-69-generic 5.15.0-69.76 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: libxml2:i386: Install libxml2:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lester 2445 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown Date: Wed Apr 19 12:41:02 2023 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2022-02-05 (437 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 80TV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=UUID=94800299-c94b-4ce0-a2b4-a97599c8aeac ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1 SourcePackage: linux Title: package linux-image-5.15.0-69-generic 5.15.0-69.76 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: Upgraded to jammy on 2022-08-23 (238 days ago) dmi.bios.date: 09/23/2016 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: 3JCN21WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Torronto 5C2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-15IKB dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvr3JCN21WW:bd09/23/2016:br1.21:efr1.21:svnLENOVO:pn80TV:pvrLenovoideapad310-15IKB:rvnLENOVO:rnTorronto5C2:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad310-15IKB:skuLENOVO_MT_80TV_BU_idea_FM_Lenovoideapad310-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80TV dmi.product.sku: LENOVO_MT_80TV_BU_idea_FM_Lenovo ideapad 310-15IKB dmi.product.version: Lenovo ideapad 310-15IKB dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017016 Title: package linux-image-5.15.0-69-generic 5.15.0-69.76 failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in linux package in Ubuntu: New Bug description: no idea ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-69-generic 5.15.0-69.76 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: libxml2:i386: Install libxml2:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lester 2445 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown Date: Wed Apr 19 12:41:02 2023 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2022-02-05 (437 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 80TV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=UUID=94800299-c94b-4ce0-a2b4-a97599c8aeac ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1 SourcePackage: linux Title: package linux-image-5.15.0-69-generic 5.15.0-69.76 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: Upgraded to jammy on 2022-08-23 (238 days ago) dmi.bios.date: 09/23/2016 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: 3JCN21WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Torronto 5C2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-15IKB dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvr3JCN21WW:bd09/23/2016:br1.21:efr1.21:svnLENOVO:pn80TV:pvrLenovoideapad310-15IKB:rvnLENOVO:rnTorronto5C2:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad310-15IKB:skuLENOVO_MT_80TV_BU_idea_FM_Lenovoideapad310-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80TV dmi.product.sku: LENOVO_MT_80TV_BU_idea_FM_Lenovo ideapad 310-15IKB dm
[Kernel-packages] [Bug 2009271] Re: Too many BDL entries regression
Nothing to do with any screen saver. Just boot the system, hit Ctl-Alt-F2 (to get to a console) and login. There they are. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009271 Title: Too many BDL entries regression Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: Hello, Thanks for your hard work :) I got this error after kernel update to 5.19.0-35 as explained here : https://askubuntu.com/questions/1457367/snd-hda-intel-001f-3-too-many-bdl-entries-messages-in-system-log and here : https://lore.kernel.org/stable/cab1lbmv1ky+kuubwvxroe+mbqbjtjofvzb8smmbcuy2mdvg...@mail.gmail.com/T/#u A load of syslog "Too many BDL entries" appears. Have a nice week-end, best regards, Laurent Lyaudet ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-35-generic 5.19.0-35.36 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent5004 F wireplumber /dev/snd/controlC1: laurent5004 F wireplumber /dev/snd/seq:laurent5000 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 16:47:55 2023 InstallationDate: Installed on 2020-07-01 (976 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. GL73 8SD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-21 (134 days ago) dmi.bios.date: 03/29/2019 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C7IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-17C7 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1: dmi.product.family: GL dmi.product.name: GL73 8SD dmi.product.sku: 17C7.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016827] Re: screen breaks and freezing
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2016827 Title: screen breaks and freezing Status in linux package in Ubuntu: New Bug description: Just started having issues with the graphics breaking and having boot information when booting both tuning on and shutting down. Now both my web browsers are randomly freezing my pc completely up and having to just turn it off and back on without shutting it down. My fan will run really loud on boot up and for about the next 3 to 4 min after boot, the power consumption has been reduce really bad as well. Thanks for your time hope that I can get this resolved. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-69-generic 5.15.0-69.76 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mjm2086 F pulseaudio /dev/snd/controlC0: mjm2086 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Apr 17 20:19:10 2023 MachineType: HP HP 255 G8 Notebook PC ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=ac398bb2-9ae5-4a95-8511-6f6f88344f20 ro quiet splash loglevel=3 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 15.32 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 87D2 dmi.board.vendor: HP dmi.board.version: 38.25 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 38.25 dmi.modalias: dmi:bvnInsyde:bvrF.32:bd08/02/2022:br15.32:efr38.25:svnHP:pnHP255G8NotebookPC:pvrType1ProductConfigId:rvnHP:rn87D2:rvr38.25:cvnHP:ct10:cvrChassisVersion:sku5U073UT#ABA: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 255 G8 Notebook PC dmi.product.sku: 5U073UT#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016827/+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 2017013] Re: net: sched: Fix use after free in red_enqueue()
** Changed in: linux (Ubuntu)
Assignee: Cengiz Can (cengizcan) => (unassigned)
** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-3586
--
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/2017013
Title:
net: sched: Fix use after free in red_enqueue()
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
In Progress
Bug description:
We can't use "skb" again after passing it to qdisc_enqueue(). This is
basically identical to commit 2f09707 ("sch_sfb: Also store skb
len before calling child enqueue").
Fixes: d7f4f33 ("sch_red: update backlog as well")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017013/+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 2017013] [NEW] net: sched: Fix use after free in red_enqueue()
Public bug reported:
We can't use "skb" again after passing it to qdisc_enqueue(). This is
basically identical to commit 2f09707 ("sch_sfb: Also store skb
len before calling child enqueue").
Fixes: d7f4f33 ("sch_red: update backlog as well")
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Affects: linux (Ubuntu Xenial)
Importance: High
Assignee: Cengiz Can (cengizcan)
Status: In Progress
** Package changed: linux-azure (Ubuntu) => linux (Ubuntu)
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Cengiz Can (cengizcan)
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-3586
--
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/2017013
Title:
net: sched: Fix use after free in red_enqueue()
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
In Progress
Bug description:
We can't use "skb" again after passing it to qdisc_enqueue(). This is
basically identical to commit 2f09707 ("sch_sfb: Also store skb
len before calling child enqueue").
Fixes: d7f4f33 ("sch_red: update backlog as well")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017013/+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 2017013] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 2017013
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017013
Title:
net: sched: Fix use after free in red_enqueue()
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
In Progress
Bug description:
We can't use "skb" again after passing it to qdisc_enqueue(). This is
basically identical to commit 2f09707 ("sch_sfb: Also store skb
len before calling child enqueue").
Fixes: d7f4f33 ("sch_red: update backlog as well")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017013/+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 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)
The attachment "thermald_Jammy_2.4.9-1ubuntu0.3.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 thermald in Ubuntu. https://bugs.launchpad.net/bugs/1995606 Title: Upgrade thermald to 2.5.1 for Jammy (22.04) Status in OEM Priority Project: New Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: Incomplete Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] since the PL1 min/max is introduced, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU. this may cause machines run like the old behavior that doesn't have PL1 min/max. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1995606/+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 2016898] Re: Azure: Enable MANA Jumbo Frame Support
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Kinetic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2016898 Title: Azure: Enable MANA Jumbo Frame Support Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] The MANA driver does not support jumbo frames [Fix] net: mana: Add support for jumbo frame https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/microsoft/mana?id=80f6215b450eb8e92d8b1f117abf5ecf867f963e net: mana: Enable RX path to handle various MTU sizes https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/microsoft/mana?id=2fbbd712baf1c60996554326728bbdbef5616e12 net: mana: Refactor RX buffer allocation code to prepare for various MTU https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/microsoft/mana?id=a2917b23497e4205db32271e4e06e142a9f8a6aa net: mana: Use napi_build_skb in RX path https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/microsoft/mana?id=ce518bc3e9ca342309995c9270c3ec4892963695 [Test Plan] Microsoft tested [Regression Potential] Regular frames could be discarded. [Other Info] SF: #00358566 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016898/+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 2016995] Re: Azure: Build-in TDX guest driver
** Changed in: linux-azure (Ubuntu Kinetic) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Lunar) Status: In Progress => Fix Committed ** Changed in: linux-azure-5.19 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2016995 Title: Azure: Build-in TDX guest driver Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure-5.19 package in Ubuntu: Invalid Status in linux-azure source package in Jammy: Invalid Status in linux-azure-5.19 source package in Jammy: Fix Committed Status in linux-azure source package in Kinetic: Fix Committed Status in linux-azure-5.19 source package in Kinetic: Invalid Status in linux-azure source package in Lunar: Fix Committed Status in linux-azure-5.19 source package in Lunar: Invalid Bug description: SRU Justification [Impact] The TDX guest driver is currently packaged in linux-modules-extra. This is a non-optimal experience for users of the Azure image that is focused on TDX encryption and security. [Fix] Build in the TDX guest driver [Test Plan] Check that the TDX guest driver no longer appears in linux-modules-extra Microsoft tested as well. [Regression potential] There should be no regression potential. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2016995/+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 2016920] Re: [UBUNTU 22.04] Standalone dump does not work on NVMe device
** Also affects: s390-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: s390-tools (Ubuntu Jammy) Importance: Undecided => High ** Changed in: s390-tools (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: s390-tools (Ubuntu Lunar) Importance: Undecided => High -- 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/2016920 Title: [UBUNTU 22.04] Standalone dump does not work on NVMe device Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in s390-tools package in Ubuntu: New Status in linux source package in Jammy: New Status in s390-tools source package in Jammy: New Status in linux source package in Kinetic: New Status in s390-tools source package in Kinetic: New Status in linux source package in Lunar: New Status in s390-tools source package in Lunar: New Bug description: Problem Description: I installed Ubuntu 22.04.1. and created a dump partition on an NVMe disk. However, this dump partition is not able to capture a dump: [414340.280553] kdump-tools[15167]: * unloaded kdump kernel [414376.146205] sysrq: Trigger a crash [414376.146215] Kernel panic - not syncing: sysrq triggered crash [414376.146218] CPU: 13 PID: 16009 Comm: bash Not tainted 5.15.0-69-generic #76-Ubuntu [414376.146222] Hardware name: IBM 3931 A01 704 (LPAR) [414376.146224] Call Trace: [414376.146225] [<000176c3e31a>] dump_stack_lvl+0x62/0x80 [414376.146233] [<000176c3913a>] panic+0x152/0x340 [414376.146237] [<0001768d5cfe>] sysrq_handle_crash+0x2e/0x30 [414376.146242] [<0001768d6952>] __handle_sysrq+0xf2/0x280 [414376.146245] [<0001768d7244>] write_sysrq_trigger+0x54/0x70 [414376.146248] [<000176597faa>] proc_reg_write+0x9a/0xf0 [414376.146252] [<0001764e64dc>] vfs_write+0xbc/0x280 [414376.146255] [<0001764e8a18>] ksys_write+0x68/0x100 [414376.146258] [<000176c4288c>] __do_syscall+0x1bc/0x1f0 [414376.146261] [<000176c4fc98>] system_call+0x78/0xa0 System version 9. Watchdog enabled. Running 'ZBootLoader' version '3.1.5' level 'D51C.D51C_328.13'. OK Success [2.131284] zdump: The dump process started for a 64-bit operating system Linux System Dumper starting Version 3.0 (64 bit) Linux version 5.15.27 (buildd@bos02-s390x-003) (gcc (Ubuntu 11.2.0-18ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP Mon Mar 21 16:33:41 UTC 2022 ERROR: open /sys/firmware/ipl/device failed No such file or directory ERROR: Could not enable dump device Dump failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2016920/+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 1995956] Re: amdgpu no-retry page fault resulting in black screen and unresponsive system
very much waiting for the fix to be ported to 5.19 for ubuntu 22.04 keeping 5.15 for now -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/1995956 Title: amdgpu no-retry page fault resulting in black screen and unresponsive system Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Triaged Status in linux-oem-6.1 package in Ubuntu: Fix Released Status in linux source package in Kinetic: Triaged Bug description: When using Skype in snap, amdgpu crashed, resulting in black screen and unresponsive system. Happened on Kinetic Kudu 5.19.0-23-generic with or without latest amdgpu firmware. Affected laptop is T14 with Ryzen 5850U. Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142c000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00540051 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142d000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142c000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00540051 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142d000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x0 This happens in a loop and eventually leads to GPU reset, which fails. Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=211509, emitted seq=211512 Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process skypeforlinux pid 154554 thread skypeforli:cs0 pid 154558 Nov 03 16:35:55 laptop kernel: amdgpu :07:00.0: amdgpu:
[Kernel-packages] [Bug 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)
@Raof, i have modified the patches, only picked the necessary and drop the part of refactoring. * drop these two commits, ~~~ * Dropped, Remove /dev/cpu/*/msr access for TCC * part of refactoring and keep the required, Separate Adaptive engine and GDDV ~~~ Would you please review it first. thanks ** Patch added: "thermald_Jammy_2.4.9-1ubuntu0.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1995606/+attachment/5665259/+files/thermald_Jammy_2.4.9-1ubuntu0.3.debdiff -- 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/1995606 Title: Upgrade thermald to 2.5.1 for Jammy (22.04) Status in OEM Priority Project: New Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: Incomplete Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] since the PL1 min/max is introduced, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU. this may cause machines run like the old behavior that doesn't have PL1 min/max. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1995606/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009271] Re: Too many BDL entries regression
Same here - I cannot be certain, but for me it seems to be triggered after screensaver is unlocked. I will return to the desktop, unlock the screensaver, and notice that pulseaudio is taking 100% and audio is no longer working. Sometimes pulseaudio -k will restart/fix it. But other times it will not. See tons of [242505.848196] snd_hda_intel :00:1f.3: Too many BDL entries: buffer=4194300, period=135300 in the syslog. /var/log/syslog also filled my hard drive due to this message. This problem started happening in the past month or so for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009271 Title: Too many BDL entries regression Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: Hello, Thanks for your hard work :) I got this error after kernel update to 5.19.0-35 as explained here : https://askubuntu.com/questions/1457367/snd-hda-intel-001f-3-too-many-bdl-entries-messages-in-system-log and here : https://lore.kernel.org/stable/cab1lbmv1ky+kuubwvxroe+mbqbjtjofvzb8smmbcuy2mdvg...@mail.gmail.com/T/#u A load of syslog "Too many BDL entries" appears. Have a nice week-end, best regards, Laurent Lyaudet ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-35-generic 5.19.0-35.36 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent5004 F wireplumber /dev/snd/controlC1: laurent5004 F wireplumber /dev/snd/seq:laurent5000 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 16:47:55 2023 InstallationDate: Installed on 2020-07-01 (976 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. GL73 8SD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-21 (134 days ago) dmi.bios.date: 03/29/2019 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C7IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-17C7 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1: dmi.product.family: GL dmi.product.name: GL73 8SD dmi.product.sku: 17C7.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
@Siggitron, i checked 5.19-49 is released on March 31 so the next version may have the solution. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017002] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2017002/+attachment/5665236/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => New ** 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/2017002 Title: My secondary screen stay in sleep mode Status in linux package in Ubuntu: Confirmed Bug description: My secondary screen connected via DisplayPort through a USB Type-C dock does not turn back on after going into sleep mode. My laptop is Lenovo ThinkPad-X13 on ubuntu 23.04 This issue occurred when my laptop is on 6.2.0-20-generic kernel No problem on 5.19.0-38-generic #39-Ubuntu kernel --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2021-02-19 (788 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UGS11Q00 Package: linux (not installed) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=eb166940-c818-4253-9f98-fedce08626f5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: lunar Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-14 (4 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 12/09/2022 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET73W(1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UGS11Q00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrR1CET73W(1.42):bd12/09/2022:br1.42:efr1.42:svnLENOVO:pn20UGS11Q00:pvrThinkPadX13Gen1:rvnLENOVO:rn20UGS11Q00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UG_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UGS11Q00 dmi.product.sku: LENOVO_MT_20UG_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017002/+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 2017002] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2017002/+attachment/5665235/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017002 Title: My secondary screen stay in sleep mode Status in linux package in Ubuntu: Confirmed Bug description: My secondary screen connected via DisplayPort through a USB Type-C dock does not turn back on after going into sleep mode. My laptop is Lenovo ThinkPad-X13 on ubuntu 23.04 This issue occurred when my laptop is on 6.2.0-20-generic kernel No problem on 5.19.0-38-generic #39-Ubuntu kernel --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2021-02-19 (788 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UGS11Q00 Package: linux (not installed) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=eb166940-c818-4253-9f98-fedce08626f5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: lunar Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-14 (4 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 12/09/2022 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET73W(1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UGS11Q00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrR1CET73W(1.42):bd12/09/2022:br1.42:efr1.42:svnLENOVO:pn20UGS11Q00:pvrThinkPadX13Gen1:rvnLENOVO:rn20UGS11Q00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UG_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UGS11Q00 dmi.product.sku: LENOVO_MT_20UG_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017002/+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 2017002] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2017002/+attachment/5665233/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017002 Title: My secondary screen stay in sleep mode Status in linux package in Ubuntu: Confirmed Bug description: My secondary screen connected via DisplayPort through a USB Type-C dock does not turn back on after going into sleep mode. My laptop is Lenovo ThinkPad-X13 on ubuntu 23.04 This issue occurred when my laptop is on 6.2.0-20-generic kernel No problem on 5.19.0-38-generic #39-Ubuntu kernel --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2021-02-19 (788 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UGS11Q00 Package: linux (not installed) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=eb166940-c818-4253-9f98-fedce08626f5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: lunar Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-14 (4 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 12/09/2022 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET73W(1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UGS11Q00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrR1CET73W(1.42):bd12/09/2022:br1.42:efr1.42:svnLENOVO:pn20UGS11Q00:pvrThinkPadX13Gen1:rvnLENOVO:rn20UGS11Q00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UG_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UGS11Q00 dmi.product.sku: LENOVO_MT_20UG_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017002/+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 2017002] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2017002/+attachment/5665234/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017002 Title: My secondary screen stay in sleep mode Status in linux package in Ubuntu: Confirmed Bug description: My secondary screen connected via DisplayPort through a USB Type-C dock does not turn back on after going into sleep mode. My laptop is Lenovo ThinkPad-X13 on ubuntu 23.04 This issue occurred when my laptop is on 6.2.0-20-generic kernel No problem on 5.19.0-38-generic #39-Ubuntu kernel --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2021-02-19 (788 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UGS11Q00 Package: linux (not installed) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=eb166940-c818-4253-9f98-fedce08626f5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: lunar Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-14 (4 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 12/09/2022 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET73W(1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UGS11Q00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrR1CET73W(1.42):bd12/09/2022:br1.42:efr1.42:svnLENOVO:pn20UGS11Q00:pvrThinkPadX13Gen1:rvnLENOVO:rn20UGS11Q00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UG_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UGS11Q00 dmi.product.sku: LENOVO_MT_20UG_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017002/+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 2017002] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2017002/+attachment/5665232/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017002 Title: My secondary screen stay in sleep mode Status in linux package in Ubuntu: Confirmed Bug description: My secondary screen connected via DisplayPort through a USB Type-C dock does not turn back on after going into sleep mode. My laptop is Lenovo ThinkPad-X13 on ubuntu 23.04 This issue occurred when my laptop is on 6.2.0-20-generic kernel No problem on 5.19.0-38-generic #39-Ubuntu kernel --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2021-02-19 (788 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UGS11Q00 Package: linux (not installed) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=eb166940-c818-4253-9f98-fedce08626f5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: lunar Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-14 (4 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 12/09/2022 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET73W(1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UGS11Q00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrR1CET73W(1.42):bd12/09/2022:br1.42:efr1.42:svnLENOVO:pn20UGS11Q00:pvrThinkPadX13Gen1:rvnLENOVO:rn20UGS11Q00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UG_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UGS11Q00 dmi.product.sku: LENOVO_MT_20UG_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017002/+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 2017002] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2017002/+attachment/5665231/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017002 Title: My secondary screen stay in sleep mode Status in linux package in Ubuntu: Confirmed Bug description: My secondary screen connected via DisplayPort through a USB Type-C dock does not turn back on after going into sleep mode. My laptop is Lenovo ThinkPad-X13 on ubuntu 23.04 This issue occurred when my laptop is on 6.2.0-20-generic kernel No problem on 5.19.0-38-generic #39-Ubuntu kernel --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2021-02-19 (788 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UGS11Q00 Package: linux (not installed) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=eb166940-c818-4253-9f98-fedce08626f5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: lunar Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-14 (4 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 12/09/2022 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET73W(1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UGS11Q00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrR1CET73W(1.42):bd12/09/2022:br1.42:efr1.42:svnLENOVO:pn20UGS11Q00:pvrThinkPadX13Gen1:rvnLENOVO:rn20UGS11Q00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UG_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UGS11Q00 dmi.product.sku: LENOVO_MT_20UG_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017002/+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 2017002] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2017002/+attachment/5665230/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017002 Title: My secondary screen stay in sleep mode Status in linux package in Ubuntu: Confirmed Bug description: My secondary screen connected via DisplayPort through a USB Type-C dock does not turn back on after going into sleep mode. My laptop is Lenovo ThinkPad-X13 on ubuntu 23.04 This issue occurred when my laptop is on 6.2.0-20-generic kernel No problem on 5.19.0-38-generic #39-Ubuntu kernel --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2021-02-19 (788 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UGS11Q00 Package: linux (not installed) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=eb166940-c818-4253-9f98-fedce08626f5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: lunar Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-14 (4 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 12/09/2022 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET73W(1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UGS11Q00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrR1CET73W(1.42):bd12/09/2022:br1.42:efr1.42:svnLENOVO:pn20UGS11Q00:pvrThinkPadX13Gen1:rvnLENOVO:rn20UGS11Q00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UG_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UGS11Q00 dmi.product.sku: LENOVO_MT_20UG_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017002/+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 2017002] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2017002/+attachment/5665229/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017002 Title: My secondary screen stay in sleep mode Status in linux package in Ubuntu: Confirmed Bug description: My secondary screen connected via DisplayPort through a USB Type-C dock does not turn back on after going into sleep mode. My laptop is Lenovo ThinkPad-X13 on ubuntu 23.04 This issue occurred when my laptop is on 6.2.0-20-generic kernel No problem on 5.19.0-38-generic #39-Ubuntu kernel --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2021-02-19 (788 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UGS11Q00 Package: linux (not installed) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=eb166940-c818-4253-9f98-fedce08626f5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: lunar Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-14 (4 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 12/09/2022 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET73W(1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UGS11Q00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrR1CET73W(1.42):bd12/09/2022:br1.42:efr1.42:svnLENOVO:pn20UGS11Q00:pvrThinkPadX13Gen1:rvnLENOVO:rn20UGS11Q00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UG_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UGS11Q00 dmi.product.sku: LENOVO_MT_20UG_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017002/+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 2017002] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2017002/+attachment/5665228/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017002 Title: My secondary screen stay in sleep mode Status in linux package in Ubuntu: Confirmed Bug description: My secondary screen connected via DisplayPort through a USB Type-C dock does not turn back on after going into sleep mode. My laptop is Lenovo ThinkPad-X13 on ubuntu 23.04 This issue occurred when my laptop is on 6.2.0-20-generic kernel No problem on 5.19.0-38-generic #39-Ubuntu kernel --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2021-02-19 (788 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UGS11Q00 Package: linux (not installed) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=eb166940-c818-4253-9f98-fedce08626f5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: lunar Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-14 (4 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 12/09/2022 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET73W(1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UGS11Q00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrR1CET73W(1.42):bd12/09/2022:br1.42:efr1.42:svnLENOVO:pn20UGS11Q00:pvrThinkPadX13Gen1:rvnLENOVO:rn20UGS11Q00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UG_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UGS11Q00 dmi.product.sku: LENOVO_MT_20UG_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017002/+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 2017002] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2017002/+attachment/5665227/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017002 Title: My secondary screen stay in sleep mode Status in linux package in Ubuntu: Confirmed Bug description: My secondary screen connected via DisplayPort through a USB Type-C dock does not turn back on after going into sleep mode. My laptop is Lenovo ThinkPad-X13 on ubuntu 23.04 This issue occurred when my laptop is on 6.2.0-20-generic kernel No problem on 5.19.0-38-generic #39-Ubuntu kernel --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2021-02-19 (788 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UGS11Q00 Package: linux (not installed) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=eb166940-c818-4253-9f98-fedce08626f5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: lunar Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-14 (4 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 12/09/2022 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET73W(1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UGS11Q00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrR1CET73W(1.42):bd12/09/2022:br1.42:efr1.42:svnLENOVO:pn20UGS11Q00:pvrThinkPadX13Gen1:rvnLENOVO:rn20UGS11Q00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UG_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UGS11Q00 dmi.product.sku: LENOVO_MT_20UG_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017002/+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 2017002] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2017002/+attachment/5665226/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017002 Title: My secondary screen stay in sleep mode Status in linux package in Ubuntu: Confirmed Bug description: My secondary screen connected via DisplayPort through a USB Type-C dock does not turn back on after going into sleep mode. My laptop is Lenovo ThinkPad-X13 on ubuntu 23.04 This issue occurred when my laptop is on 6.2.0-20-generic kernel No problem on 5.19.0-38-generic #39-Ubuntu kernel --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2021-02-19 (788 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UGS11Q00 Package: linux (not installed) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=eb166940-c818-4253-9f98-fedce08626f5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: lunar Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-14 (4 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 12/09/2022 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET73W(1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UGS11Q00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrR1CET73W(1.42):bd12/09/2022:br1.42:efr1.42:svnLENOVO:pn20UGS11Q00:pvrThinkPadX13Gen1:rvnLENOVO:rn20UGS11Q00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UG_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UGS11Q00 dmi.product.sku: LENOVO_MT_20UG_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017002/+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 2017002] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2017002/+attachment/5665225/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017002 Title: My secondary screen stay in sleep mode Status in linux package in Ubuntu: Confirmed Bug description: My secondary screen connected via DisplayPort through a USB Type-C dock does not turn back on after going into sleep mode. My laptop is Lenovo ThinkPad-X13 on ubuntu 23.04 This issue occurred when my laptop is on 6.2.0-20-generic kernel No problem on 5.19.0-38-generic #39-Ubuntu kernel --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2021-02-19 (788 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UGS11Q00 Package: linux (not installed) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=eb166940-c818-4253-9f98-fedce08626f5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: lunar Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-14 (4 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 12/09/2022 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET73W(1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UGS11Q00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrR1CET73W(1.42):bd12/09/2022:br1.42:efr1.42:svnLENOVO:pn20UGS11Q00:pvrThinkPadX13Gen1:rvnLENOVO:rn20UGS11Q00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UG_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UGS11Q00 dmi.product.sku: LENOVO_MT_20UG_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017002/+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 2017002] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2017002/+attachment/5665224/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017002 Title: My secondary screen stay in sleep mode Status in linux package in Ubuntu: Confirmed Bug description: My secondary screen connected via DisplayPort through a USB Type-C dock does not turn back on after going into sleep mode. My laptop is Lenovo ThinkPad-X13 on ubuntu 23.04 This issue occurred when my laptop is on 6.2.0-20-generic kernel No problem on 5.19.0-38-generic #39-Ubuntu kernel --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2021-02-19 (788 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UGS11Q00 Package: linux (not installed) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=eb166940-c818-4253-9f98-fedce08626f5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: lunar Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-14 (4 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 12/09/2022 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET73W(1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UGS11Q00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrR1CET73W(1.42):bd12/09/2022:br1.42:efr1.42:svnLENOVO:pn20UGS11Q00:pvrThinkPadX13Gen1:rvnLENOVO:rn20UGS11Q00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UG_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UGS11Q00 dmi.product.sku: LENOVO_MT_20UG_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017002/+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 2017002] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/2017002/+attachment/5665221/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017002 Title: My secondary screen stay in sleep mode Status in linux package in Ubuntu: Confirmed Bug description: My secondary screen connected via DisplayPort through a USB Type-C dock does not turn back on after going into sleep mode. My laptop is Lenovo ThinkPad-X13 on ubuntu 23.04 This issue occurred when my laptop is on 6.2.0-20-generic kernel No problem on 5.19.0-38-generic #39-Ubuntu kernel --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2021-02-19 (788 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UGS11Q00 Package: linux (not installed) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=eb166940-c818-4253-9f98-fedce08626f5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: lunar Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-14 (4 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 12/09/2022 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET73W(1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UGS11Q00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrR1CET73W(1.42):bd12/09/2022:br1.42:efr1.42:svnLENOVO:pn20UGS11Q00:pvrThinkPadX13Gen1:rvnLENOVO:rn20UGS11Q00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UG_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UGS11Q00 dmi.product.sku: LENOVO_MT_20UG_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017002/+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 2017002] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2017002/+attachment/5665223/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017002 Title: My secondary screen stay in sleep mode Status in linux package in Ubuntu: Confirmed Bug description: My secondary screen connected via DisplayPort through a USB Type-C dock does not turn back on after going into sleep mode. My laptop is Lenovo ThinkPad-X13 on ubuntu 23.04 This issue occurred when my laptop is on 6.2.0-20-generic kernel No problem on 5.19.0-38-generic #39-Ubuntu kernel --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2021-02-19 (788 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UGS11Q00 Package: linux (not installed) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=eb166940-c818-4253-9f98-fedce08626f5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: lunar Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-14 (4 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 12/09/2022 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET73W(1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UGS11Q00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrR1CET73W(1.42):bd12/09/2022:br1.42:efr1.42:svnLENOVO:pn20UGS11Q00:pvrThinkPadX13Gen1:rvnLENOVO:rn20UGS11Q00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UG_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UGS11Q00 dmi.product.sku: LENOVO_MT_20UG_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017002/+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 2017002] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2017002/+attachment/5665222/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017002 Title: My secondary screen stay in sleep mode Status in linux package in Ubuntu: Confirmed Bug description: My secondary screen connected via DisplayPort through a USB Type-C dock does not turn back on after going into sleep mode. My laptop is Lenovo ThinkPad-X13 on ubuntu 23.04 This issue occurred when my laptop is on 6.2.0-20-generic kernel No problem on 5.19.0-38-generic #39-Ubuntu kernel --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2021-02-19 (788 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UGS11Q00 Package: linux (not installed) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=eb166940-c818-4253-9f98-fedce08626f5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: lunar Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-14 (4 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 12/09/2022 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET73W(1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UGS11Q00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrR1CET73W(1.42):bd12/09/2022:br1.42:efr1.42:svnLENOVO:pn20UGS11Q00:pvrThinkPadX13Gen1:rvnLENOVO:rn20UGS11Q00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UG_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UGS11Q00 dmi.product.sku: LENOVO_MT_20UG_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017002/+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 2017002] Re: My secondary screen stay in sleep mode
apport information ** Tags added: apport-collected lunar ** Description changed: My secondary screen connected via DisplayPort through a USB Type-C dock does not turn back on after going into sleep mode. My laptop is Lenovo ThinkPad-X13 on ubuntu 23.04 This issue occurred when my laptop is on 6.2.0-20-generic kernel No problem on 5.19.0-38-generic #39-Ubuntu kernel + --- + ProblemType: Bug + ApportVersion: 2.26.1-0ubuntu2 + Architecture: amd64 + CRDA: N/A + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 23.04 + InstallationDate: Installed on 2021-02-19 (788 days ago) + InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) + MachineType: LENOVO 20UGS11Q00 + Package: linux (not installed) + ProcEnviron: + LANG=fr_FR.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm + XDG_RUNTIME_DIR= + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=eb166940-c818-4253-9f98-fedce08626f5 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 + RelatedPackageVersions: + linux-restricted-modules-5.19.0-38-generic N/A + linux-backports-modules-5.19.0-38-generic N/A + linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 + Tags: lunar + Uname: Linux 5.19.0-38-generic x86_64 + UpgradeStatus: Upgraded to lunar on 2023-04-14 (4 days ago) + UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark + _MarkForUpload: True + dmi.bios.date: 12/09/2022 + dmi.bios.release: 1.42 + dmi.bios.vendor: LENOVO + dmi.bios.version: R1CET73W(1.42 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20UGS11Q00 + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40697 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.ec.firmware.release: 1.42 + dmi.modalias: dmi:bvnLENOVO:bvrR1CET73W(1.42):bd12/09/2022:br1.42:efr1.42:svnLENOVO:pn20UGS11Q00:pvrThinkPadX13Gen1:rvnLENOVO:rn20UGS11Q00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UG_BU_Think_FM_ThinkPadX13Gen1: + dmi.product.family: ThinkPad X13 Gen 1 + dmi.product.name: 20UGS11Q00 + dmi.product.sku: LENOVO_MT_20UG_BU_Think_FM_ThinkPad X13 Gen 1 + dmi.product.version: ThinkPad X13 Gen 1 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2017002/+attachment/5665220/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017002 Title: My secondary screen stay in sleep mode Status in linux package in Ubuntu: Confirmed Bug description: My secondary screen connected via DisplayPort through a USB Type-C dock does not turn back on after going into sleep mode. My laptop is Lenovo ThinkPad-X13 on ubuntu 23.04 This issue occurred when my laptop is on 6.2.0-20-generic kernel No problem on 5.19.0-38-generic #39-Ubuntu kernel --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2021-02-19 (788 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UGS11Q00 Package: linux (not installed) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=eb166940-c818-4253-9f98-fedce08626f5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: lunar Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-14 (4 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 12/09/2022 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET73W(1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UGS11Q00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrR1CET73W(1.42):bd12/09/2022:br1.42:efr1.42:svnLENOVO:pn20UGS11Q00:pvrThinkPadX13Gen1:rvnLENOVO:rn20UGS11Q00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UG_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UGS11Q00 dmi.product.sku: LENOVO_MT_20UG_BU_Think_FM_
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
Still same problem with kernel 5.19.0.40--generic like with kernel 5.19.0.38 only with 5.19.0-32-generic is working properly hdmi sound with Radeon X570. Micro-Star International Co., Ltd. MS-7B79 Radeon RX 570 Series Ubuntu 22.04.2 LTS -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017002] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2017002 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017002 Title: My secondary screen stay in sleep mode Status in linux package in Ubuntu: Incomplete Bug description: My secondary screen connected via DisplayPort through a USB Type-C dock does not turn back on after going into sleep mode. My laptop is Lenovo ThinkPad-X13 on ubuntu 23.04 This issue occurred when my laptop is on 6.2.0-20-generic kernel No problem on 5.19.0-38-generic #39-Ubuntu kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017002/+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 2017002] [NEW] My secondary screen stay in sleep mode
Public bug reported: My secondary screen connected via DisplayPort through a USB Type-C dock does not turn back on after going into sleep mode. My laptop is Lenovo ThinkPad-X13 on ubuntu 23.04 This issue occurred when my laptop is on 6.2.0-20-generic kernel No problem on 5.19.0-38-generic #39-Ubuntu kernel ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: kernel-bug ** Tags added: kernel-bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017002 Title: My secondary screen stay in sleep mode Status in linux package in Ubuntu: Incomplete Bug description: My secondary screen connected via DisplayPort through a USB Type-C dock does not turn back on after going into sleep mode. My laptop is Lenovo ThinkPad-X13 on ubuntu 23.04 This issue occurred when my laptop is on 6.2.0-20-generic kernel No problem on 5.19.0-38-generic #39-Ubuntu kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017002/+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 2016410] Re: macbook not waking from suspend
Attached report from apport and status changed to Confirmed. ** Attachment added: "apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016410/+attachment/5665219/+files/apport.linux.8jjxkq2i.apport ** Changed in: linux (Ubuntu) Status: Incomplete => 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/2016410 Title: macbook not waking from suspend Status in linux package in Ubuntu: Confirmed Bug description: macbook air 2017 is not waking from suspend. Happens less when wifi is on but almost all times if wifi is off [may wake for one or two times if lucky]. Pressing any key including power button does nothing, only option is hard reboot. Things are normal if wifi driver is not installed. wifi driver [for BCM4360] is mentioned in the attachment. OS: Xubuntu 22.04.2 LTS x86_64 Host: MacBookAir7,2 1.0 Kernel: 5.19.0-32-generic CPU: Intel i5-5350U (4) @ 2.900GHz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016410/+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 2016398] Re: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?)
** Attachment added: "Fixed script that replicates the issue" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016398/+attachment/5665218/+files/overlayfsscript -- 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/2016398 Title: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?) Status in linux package in Ubuntu: Confirmed Bug description: Hi BACKGROUND: --- I have a set of scripts that debootstraps and builds vanilla Debian installs, where the only modifications are what packages are installed. Then that becomes the lower directory of an overlayfs mount, a tmpfs becomes the upperdir, and then that becomes the chroot where config changes are made with more scripts. This overlayfs is mounted in its own mount namespace as the script is unshare'd Within these scripts, I make packages with a fork of checkinstall I made which uses the / as the lowerdir, as overlayfs allows that, a tmpfs as the upperdir, the install command is run with chroot, and then the contents are copied. THE ISSUE: -- I noticed that it appears that my ramdisks are remaining in memory, I have isolated it out to the overlayfs mounts with the overlayfs as the lowerdir where chroot is being called on it. I tried entering the namespace myself and umounting it, and notice I get the error "Target is busy" With the "Target Is Busy" issue, I tried to `lsof` and `fuser` and `lsfd` as much as I could, but every user mode tool shows absolutely NO files open at all I was using Kubuntu 18.04, it was an old install and 32 bit, so I had no upgrade path to be using more recent versions. Now I am on 23.04, but I also think this is happening on a 22.10 laptop DIAGNOSIS: -- I am able to isolate it out, and get this to replicate in the smallest script that I could that is now attached. the chroot is important. I am able to unmount the second overlayfs if chroot is never called. Nothing ever has to run IN the chroot, trying to call a binary that does not exist, and then trying to unmount it results in "target is busy" with no open files reportable by user mode tools FURTHER TESTING: Trying to find out the version of Linux this was introduced, I made a script that builds a very minimal ext4 file for a VM with a small debootstrapped system, builds a kernel, and runs the kernel with QEMU.. but when I started, after all that, I can't replicate it at all with a vanilla 6.2.0 kernel. I used the same config out of my /boot to the .config, only tweaking a few options like SYSTEM_TRUSTED_KEYS. Trying to unmount the second filesystem actually results in success I then built a Kubuntu Lunar VM, and was able to replicate it on not just my system. When I built and install the vanilla kernel with bindeb-pkg, and then I boot the vanilla kernel, I can't replicate it, the second filesystem unmounts. When I reboot the VM, and start the default distribution kernel, I am able to replicate the issue, the second filesystem being unable to unmount, with "target is busy" with no files open according to standard usermode tools, when chroot is called on it I tried to look at patches in git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/lunar and git log --oneline --grep="sauce" but none of them really look relevant. I could be VERY wrong in this matter though SUMMARY: Long story short, (I am VERY sorry about the length:) I make an overlayfs, I make a second overlayfs with the first overlayfs as the second one's lowerdir, I chroot into the second overlayfs, and then later I can't unmount the second one as it says "Target is busy", but the user mode tools don't show any files open at all. If I mount the second overlayfs, and then unmount it without ever chroot-ing into it I AM able to unmount it The attached script should replicate the issue This doesn't seem to happen on the vanilla Linux kernel, with the same as close as possible config that Ubuntu uses Thanks ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nerdopolis 3007 F wireplumber /dev/snd/controlC0: nerdopolis 3007 F wireplumber /dev/snd/seq:nerdopolis 3003 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Apr 15 19:08:48 2023 InstallationDate: Installed on 2023-04-09 (6 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230408) MachineType: ASRock B650M PG Riptide ProcFB:
[Kernel-packages] [Bug 2016995] Re: Azure: Build-in TDX guest driver
** Description changed: SRU Justification [Impact] The TDX guest driver is currently packaged in linux-modules-extra. This is a non-optimal experience for users of the Azure image that is focused on TDX encryption and security. [Fix] - Build in the TDX guest driver, + Build in the TDX guest driver + + [Test Plan] + + Check that the TDX guest driver no longer appears in linux-modules-extra + Microsoft tested as well. [Regression potential] There should be no regression potential. -- 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/2016995 Title: Azure: Build-in TDX guest driver Status in linux-azure package in Ubuntu: In Progress Status in linux-azure-5.19 package in Ubuntu: Invalid Status in linux-azure source package in Jammy: Invalid Status in linux-azure-5.19 source package in Jammy: In Progress Status in linux-azure source package in Kinetic: In Progress Status in linux-azure-5.19 source package in Kinetic: Invalid Status in linux-azure source package in Lunar: In Progress Status in linux-azure-5.19 source package in Lunar: Invalid Bug description: SRU Justification [Impact] The TDX guest driver is currently packaged in linux-modules-extra. This is a non-optimal experience for users of the Azure image that is focused on TDX encryption and security. [Fix] Build in the TDX guest driver [Test Plan] Check that the TDX guest driver no longer appears in linux-modules-extra Microsoft tested as well. [Regression potential] There should be no regression potential. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2016995/+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 2015857] Re: Repeatedly unusable truncated crash files (on log-out)
Added package version to the description (apport-collect does not allow me to collect the data since I am not the original reporter). ** Description changed: Repeatedly unusable truncated crash files: Bug 2012974, bug 2015842, bug 2015140, bug 2012075 Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete. If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell). Running `apport-retrace -g $crash` on the .crash files will fail with "/tmp/apport_core_[...] is not a core dump: file format not recognized" Steps to reproduce == 1. Use Ubuntu 23.04 (lunar) desktop with GNOME shell 2. Downgrade gjs and libgjs0g to 1.76.0-1 (for triggering bug 1974293) 3. Remove all crashes: `sudo rm -f /var/crash/*` 4. Interact with the desktop, icon grid and calendar for 30 seconds. 5. Log out. 6. Crash files written. To test the core file, either use `apport-unpack` on the /var/crash/*.crash file to extract the CoreDump file or use `apport- retrace -g` on the .crash file. It will fail to print the backtrace: ``` $ apport-retrace -g /var/crash/_usr_bin_gnome-shell.1000.crash [...] Warnung: Error reading shared library list entry at 0x646c7472 Failed to read a valid object file image from memory. Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGSEGV, Segmentation fault. Warnung: Section `.reg-xstate/10527' in core file too small. (gdb) bt #0 0x7fe1c8090ffb in ?? () Backtrace stopped: Cannot access memory at address 0x7ffd59a40fe0 ``` You can use the 0001-apport-Write-coredump-at-beginning-and-quit.patch on apport to only write the coredump and adjust the slowdown to 100% reproduce the behavior on log-out. + + ApportVersion: 2.26.1-0ubuntu2 + Architecture: amd64 + DistroRelease: Ubuntu 23.04 + Package: linux-image-6.2.0-20-generic 6.2.0-20.20 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=6278216c-6f7c-4a94-8eab-e9c43da65227 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 ** Changed in: linux (Ubuntu) Status: Incomplete => 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/2015857 Title: Repeatedly unusable truncated crash files (on log-out) Status in apport package in Ubuntu: Triaged Status in linux package in Ubuntu: Confirmed Bug description: Repeatedly unusable truncated crash files: Bug 2012974, bug 2015842, bug 2015140, bug 2012075 Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete. If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell). Running `apport-retrace -g $crash` on the .crash files will fail with "/tmp/apport_core_[...] is not a core dump: file format not recognized" Steps to reproduce == 1. Use Ubuntu 23.04 (lunar) desktop with GNOME shell 2. Downgrade gjs and libgjs0g to 1.76.0-1 (for triggering bug 1974293) 3. Remove all crashes: `sudo rm -f /var/crash/*` 4. Interact with the desktop, icon grid and calendar for 30 seconds. 5. Log out. 6. Crash files written. To test the core file, either use `apport-unpack` on the /var/crash/*.crash file to extract the CoreDump file or use `apport- retrace -g` on the .crash file. It will fail to print the backtrace: ``` $ apport-retrace -g /var/crash/_usr_bin_gnome-shell.1000.crash [...] Warnung: Error reading shared library list entry at 0x646c7472 Failed to read a valid object file image from memory. Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGSEGV, Segmentation fault. Warnung: Section `.reg-xstate/10527' in core file too small. (gdb) bt #0 0x7fe1c8090ffb in ?? () Backtrace stopped: Cannot access memory at address 0x7ffd59a40fe0 ``` You can use the 0001-apport-Write-coredump-at-beginning-and-quit.patch on apport to only write the coredump and adjust the slowdown to 100% reproduce the behavior on log-out. ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=6278216c-6f7c-4a94-8eab-e9c43da65227 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 To manage notifications about
[Kernel-packages] [Bug 2016920] Re: [UBUNTU 22.04] Standalone dump does not work on NVMe device
** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: linux (Ubuntu Lunar) Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned) ** Changed in: ubuntu-z-systems Status: New => Incomplete ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => High ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: ubuntu-z-systems Importance: Undecided => High -- 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/2016920 Title: [UBUNTU 22.04] Standalone dump does not work on NVMe device Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Status in linux source package in Kinetic: New Status in linux source package in Lunar: New Bug description: Problem Description: I installed Ubuntu 22.04.1. and created a dump partition on an NVMe disk. However, this dump partition is not able to capture a dump: [414340.280553] kdump-tools[15167]: * unloaded kdump kernel [414376.146205] sysrq: Trigger a crash [414376.146215] Kernel panic - not syncing: sysrq triggered crash [414376.146218] CPU: 13 PID: 16009 Comm: bash Not tainted 5.15.0-69-generic #76-Ubuntu [414376.146222] Hardware name: IBM 3931 A01 704 (LPAR) [414376.146224] Call Trace: [414376.146225] [<000176c3e31a>] dump_stack_lvl+0x62/0x80 [414376.146233] [<000176c3913a>] panic+0x152/0x340 [414376.146237] [<0001768d5cfe>] sysrq_handle_crash+0x2e/0x30 [414376.146242] [<0001768d6952>] __handle_sysrq+0xf2/0x280 [414376.146245] [<0001768d7244>] write_sysrq_trigger+0x54/0x70 [414376.146248] [<000176597faa>] proc_reg_write+0x9a/0xf0 [414376.146252] [<0001764e64dc>] vfs_write+0xbc/0x280 [414376.146255] [<0001764e8a18>] ksys_write+0x68/0x100 [414376.146258] [<000176c4288c>] __do_syscall+0x1bc/0x1f0 [414376.146261] [<000176c4fc98>] system_call+0x78/0xa0 System version 9. Watchdog enabled. Running 'ZBootLoader' version '3.1.5' level 'D51C.D51C_328.13'. OK Success [2.131284] zdump: The dump process started for a 64-bit operating system Linux System Dumper starting Version 3.0 (64 bit) Linux version 5.15.27 (buildd@bos02-s390x-003) (gcc (Ubuntu 11.2.0-18ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP Mon Mar 21 16:33:41 UTC 2022 ERROR: open /sys/firmware/ipl/device failed No such file or directory ERROR: Could not enable dump device Dump failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2016920/+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 2016995] [NEW] Azure: Build-in TDX guest driver
Public bug reported: SRU Justification [Impact] The TDX guest driver is currently packaged in linux-modules-extra. This is a non-optimal experience for users of the Azure image that is focused on TDX encryption and security. [Fix] Build in the TDX guest driver, [Regression potential] There should be no regression potential. ** Affects: linux-azure (Ubuntu) Importance: High Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure-5.19 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-azure-5.19 (Ubuntu Jammy) Importance: High Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Kinetic) Importance: High Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure-5.19 (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Lunar) Importance: High Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure-5.19 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) ** Changed in: linux-azure (Ubuntu) Importance: Undecided => High ** Changed in: linux-azure (Ubuntu) Status: New => In Progress ** Changed in: linux-azure (Ubuntu) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Also affects: linux-azure (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Lunar) Importance: High Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Description changed: SRU Justification [Impact] The TDX guest driver is currently packaged in linux-modules-extra. This - is a non-optimal experience for user of the Azure image that is focused + is a non-optimal experience for users of the Azure image that is focused on TDX encryption and security. [Fix] Build in the TDX guest driver, [Regression potential] There should be no regression potential. ** Changed in: linux-azure (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: linux-azure (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Kinetic) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Also affects: linux-azure-5.19 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-azure-5.19 (Ubuntu Kinetic) Status: New => Invalid ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-azure-5.19 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-azure-5.19 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-azure-5.19 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure-5.19 (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-azure-5.19 (Ubuntu Lunar) Status: New => Invalid -- 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/2016995 Title: Azure: Build-in TDX guest driver Status in linux-azure package in Ubuntu: In Progress Status in linux-azure-5.19 package in Ubuntu: Invalid Status in linux-azure source package in Jammy: Invalid Status in linux-azure-5.19 source package in Jammy: In Progress Status in linux-azure source package in Kinetic: In Progress Status in linux-azure-5.19 source package in Kinetic: Invalid Status in linux-azure source package in Lunar: In Progress Status in linux-azure-5.19 source package in Lunar: Invalid Bug description: SRU Justification [Impact] The TDX guest driver is currently packaged in linux-modules-extra. This is a non-optimal experience for users of the Azure image that is focused on TDX encryption and security. [Fix] Build in the TDX guest driver, [Regression potential] There should be no regression potential. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2016995/+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 2015857] Re: Repeatedly unusable truncated crash files (on log-out)
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015857 Title: Repeatedly unusable truncated crash files (on log-out) Status in apport package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Repeatedly unusable truncated crash files: Bug 2012974, bug 2015842, bug 2015140, bug 2012075 Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete. If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell). Running `apport-retrace -g $crash` on the .crash files will fail with "/tmp/apport_core_[...] is not a core dump: file format not recognized" Steps to reproduce == 1. Use Ubuntu 23.04 (lunar) desktop with GNOME shell 2. Downgrade gjs and libgjs0g to 1.76.0-1 (for triggering bug 1974293) 3. Remove all crashes: `sudo rm -f /var/crash/*` 4. Interact with the desktop, icon grid and calendar for 30 seconds. 5. Log out. 6. Crash files written. To test the core file, either use `apport-unpack` on the /var/crash/*.crash file to extract the CoreDump file or use `apport- retrace -g` on the .crash file. It will fail to print the backtrace: ``` $ apport-retrace -g /var/crash/_usr_bin_gnome-shell.1000.crash [...] Warnung: Error reading shared library list entry at 0x646c7472 Failed to read a valid object file image from memory. Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGSEGV, Segmentation fault. Warnung: Section `.reg-xstate/10527' in core file too small. (gdb) bt #0 0x7fe1c8090ffb in ?? () Backtrace stopped: Cannot access memory at address 0x7ffd59a40fe0 ``` You can use the 0001-apport-Write-coredump-at-beginning-and-quit.patch on apport to only write the coredump and adjust the slowdown to 100% reproduce the behavior on log-out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2015857/+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 2016920] Re: [UBUNTU 22.04] Standalone dump does not work on NVMe device
Thanks for raising this - ok, I'm waiting for the commit. I guess it affects all releases that are never than jammy (incl. jammy itself). But please use 22.04.2 instead of 22.04.1 (since .2 superseded .1). ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: ubuntu-z-systems Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2016920 Title: [UBUNTU 22.04] Standalone dump does not work on NVMe device Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Status in linux source package in Kinetic: New Status in linux source package in Lunar: New Bug description: Problem Description: I installed Ubuntu 22.04.1. and created a dump partition on an NVMe disk. However, this dump partition is not able to capture a dump: [414340.280553] kdump-tools[15167]: * unloaded kdump kernel [414376.146205] sysrq: Trigger a crash [414376.146215] Kernel panic - not syncing: sysrq triggered crash [414376.146218] CPU: 13 PID: 16009 Comm: bash Not tainted 5.15.0-69-generic #76-Ubuntu [414376.146222] Hardware name: IBM 3931 A01 704 (LPAR) [414376.146224] Call Trace: [414376.146225] [<000176c3e31a>] dump_stack_lvl+0x62/0x80 [414376.146233] [<000176c3913a>] panic+0x152/0x340 [414376.146237] [<0001768d5cfe>] sysrq_handle_crash+0x2e/0x30 [414376.146242] [<0001768d6952>] __handle_sysrq+0xf2/0x280 [414376.146245] [<0001768d7244>] write_sysrq_trigger+0x54/0x70 [414376.146248] [<000176597faa>] proc_reg_write+0x9a/0xf0 [414376.146252] [<0001764e64dc>] vfs_write+0xbc/0x280 [414376.146255] [<0001764e8a18>] ksys_write+0x68/0x100 [414376.146258] [<000176c4288c>] __do_syscall+0x1bc/0x1f0 [414376.146261] [<000176c4fc98>] system_call+0x78/0xa0 System version 9. Watchdog enabled. Running 'ZBootLoader' version '3.1.5' level 'D51C.D51C_328.13'. OK Success [2.131284] zdump: The dump process started for a 64-bit operating system Linux System Dumper starting Version 3.0 (64 bit) Linux version 5.15.27 (buildd@bos02-s390x-003) (gcc (Ubuntu 11.2.0-18ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP Mon Mar 21 16:33:41 UTC 2022 ERROR: open /sys/firmware/ipl/device failed No such file or directory ERROR: Could not enable dump device Dump failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2016920/+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 2015857] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2015857 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015857 Title: Repeatedly unusable truncated crash files (on log-out) Status in apport package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Repeatedly unusable truncated crash files: Bug 2012974, bug 2015842, bug 2015140, bug 2012075 Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete. If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell). Running `apport-retrace -g $crash` on the .crash files will fail with "/tmp/apport_core_[...] is not a core dump: file format not recognized" Steps to reproduce == 1. Use Ubuntu 23.04 (lunar) desktop with GNOME shell 2. Downgrade gjs and libgjs0g to 1.76.0-1 (for triggering bug 1974293) 3. Remove all crashes: `sudo rm -f /var/crash/*` 4. Interact with the desktop, icon grid and calendar for 30 seconds. 5. Log out. 6. Crash files written. To test the core file, either use `apport-unpack` on the /var/crash/*.crash file to extract the CoreDump file or use `apport- retrace -g` on the .crash file. It will fail to print the backtrace: ``` $ apport-retrace -g /var/crash/_usr_bin_gnome-shell.1000.crash [...] Warnung: Error reading shared library list entry at 0x646c7472 Failed to read a valid object file image from memory. Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGSEGV, Segmentation fault. Warnung: Section `.reg-xstate/10527' in core file too small. (gdb) bt #0 0x7fe1c8090ffb in ?? () Backtrace stopped: Cannot access memory at address 0x7ffd59a40fe0 ``` You can use the 0001-apport-Write-coredump-at-beginning-and-quit.patch on apport to only write the coredump and adjust the slowdown to 100% reproduce the behavior on log-out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2015857/+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 2015857] Re: Repeatedly unusable truncated crash files (on log-out)
This behavior is only noticeable on log-out. Killing gnome-shell works. I am using the 0001-apport-Write-coredump-at-beginning-and-quit.patch with a delay of 0.005s: ``` $ killall -11 gnome-shell $ tail /var/log/apport.log ERROR: apport (pid 15107) 2023-04-19 13:53:03,089: called for pid 14206, signal 11, core limit 0, dump mode 1 WARNING: apport (pid 15107) 2023-04-19 13:53:57,167: Wrote 639,475,712 bytes of core to /var/lib/apport/coredump/core._usr_bin_gnome-shell.1000.af6fdb2c-b9ba-4eeb-8727-683ac2247576.14206.5881189 $ gdb /usr/bin/gnome-shell /var/lib/apport/coredump/core._usr_bin_gnome-shell.1000.* ``` The 639 MB were successful written and that took 54 seconds. -- 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/2015857 Title: Repeatedly unusable truncated crash files (on log-out) Status in apport package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Repeatedly unusable truncated crash files: Bug 2012974, bug 2015842, bug 2015140, bug 2012075 Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete. If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell). Running `apport-retrace -g $crash` on the .crash files will fail with "/tmp/apport_core_[...] is not a core dump: file format not recognized" Steps to reproduce == 1. Use Ubuntu 23.04 (lunar) desktop with GNOME shell 2. Downgrade gjs and libgjs0g to 1.76.0-1 (for triggering bug 1974293) 3. Remove all crashes: `sudo rm -f /var/crash/*` 4. Interact with the desktop, icon grid and calendar for 30 seconds. 5. Log out. 6. Crash files written. To test the core file, either use `apport-unpack` on the /var/crash/*.crash file to extract the CoreDump file or use `apport- retrace -g` on the .crash file. It will fail to print the backtrace: ``` $ apport-retrace -g /var/crash/_usr_bin_gnome-shell.1000.crash [...] Warnung: Error reading shared library list entry at 0x646c7472 Failed to read a valid object file image from memory. Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGSEGV, Segmentation fault. Warnung: Section `.reg-xstate/10527' in core file too small. (gdb) bt #0 0x7fe1c8090ffb in ?? () Backtrace stopped: Cannot access memory at address 0x7ffd59a40fe0 ``` You can use the 0001-apport-Write-coredump-at-beginning-and-quit.patch on apport to only write the coredump and adjust the slowdown to 100% reproduce the behavior on log-out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2015857/+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 2016991] Re: Regression in ena NIC - /sys/class/net/eth0/device/msi_irqs/ is empty
Instance type used - i3.4xlarge -- 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/2016991 Title: Regression in ena NIC - /sys/class/net/eth0/device/msi_irqs/ is empty Status in linux package in Ubuntu: Incomplete Bug description: It worked on kernel 5.15, and it doesn't on 5.19. Running on AWS instance, with the following: driver: ena version: 5.19.0-1022-aws firmware-version: expansion-rom-version: bus-info: :00:03.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no Linux ip-10-0-1-194 5.19.0-1022-aws #23~22.04.1-Ubuntu SMP Fri Mar 17 15:38:24 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux dmesg: [5.485138] ena :00:03.0: ENA device version: 0.10 [5.485146] ena :00:03.0: ENA controller version: 0.0.1 implementation version 1 [5.487074] ena :00:03.0: LLQ is not supported Fallback to host mode policy. ... [5.533589] ena :00:03.0: Elastic Network Adapter (ENA) found at mem 8300, mac addr 02:08:84:31:35:a9 Interrupt mapping: 210: 35669 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 xen-pirq -msi-x ena-mgmnt@pci::00:03.0 211: 1079105381 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 xen-pirq -msi-x eth0-Tx-Rx-0 212: 0 1047885215 0 0 0 0 0 0 0 0 0 0 0 0 0 0 xen-pirq -msi-x eth0-Tx-Rx-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016991/+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 2015857] Re: Repeatedly unusable truncated crash files
Note: Apport triggers this behavior, because it compresses the core dump and base64 encodes the compressed result. That increases the time to read the coredump file. In addition apport also takes some time to collect the crash information. ** Summary changed: - Repeatedly unusable truncated crash files + Repeatedly unusable truncated crash files (on log-out) -- 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/2015857 Title: Repeatedly unusable truncated crash files (on log-out) Status in apport package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Repeatedly unusable truncated crash files: Bug 2012974, bug 2015842, bug 2015140, bug 2012075 Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete. If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell). Running `apport-retrace -g $crash` on the .crash files will fail with "/tmp/apport_core_[...] is not a core dump: file format not recognized" Steps to reproduce == 1. Use Ubuntu 23.04 (lunar) desktop with GNOME shell 2. Downgrade gjs and libgjs0g to 1.76.0-1 (for triggering bug 1974293) 3. Remove all crashes: `sudo rm -f /var/crash/*` 4. Interact with the desktop, icon grid and calendar for 30 seconds. 5. Log out. 6. Crash files written. To test the core file, either use `apport-unpack` on the /var/crash/*.crash file to extract the CoreDump file or use `apport- retrace -g` on the .crash file. It will fail to print the backtrace: ``` $ apport-retrace -g /var/crash/_usr_bin_gnome-shell.1000.crash [...] Warnung: Error reading shared library list entry at 0x646c7472 Failed to read a valid object file image from memory. Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGSEGV, Segmentation fault. Warnung: Section `.reg-xstate/10527' in core file too small. (gdb) bt #0 0x7fe1c8090ffb in ?? () Backtrace stopped: Cannot access memory at address 0x7ffd59a40fe0 ``` You can use the 0001-apport-Write-coredump-at-beginning-and-quit.patch on apport to only write the coredump and adjust the slowdown to 100% reproduce the behavior on log-out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2015857/+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 2015857] Re: Repeatedly unusable truncated crash files
One day of debugging gave more insight. Apport is not directly the culprit. If reading from stdin takes too long, the input will be truncated. Attached a patch for apport to write the coredump at the beginning and quit. It can be slowed down by sleeping between the 1 MB blocks. The longer the sleep, the smaller the files get. For my VM: sleeping for 0.001s truncates the file slightly to ~400 MB; sleeping 0.005s truncates it to 42 MB. I verified that /proc/ is still there afterwards. So I would say that the kernel team should have a look next. ** Patch added: "0001-apport-Write-coredump-at-beginning-and-quit.patch" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2015857/+attachment/5665206/+files/0001-apport-Write-coredump-at-beginning-and-quit.patch ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: Repeatedly unusable truncated crash files: Bug 2012974, bug 2015842, bug 2015140, bug 2012075 Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete. If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell). Running `apport-retrace -g $crash` on the .crash files will fail with "/tmp/apport_core_[...] is not a core dump: file format not recognized" + + Steps to reproduce + == + + 1. Use Ubuntu 23.04 (lunar) desktop with GNOME shell + + 2. Downgrade gjs and libgjs0g to 1.76.0-1 (for triggering bug 1974293) + + 3. Remove all crashes: `sudo rm -f /var/crash/*` + + 4. Interact with the desktop, icon grid and calendar for 30 seconds. + + 5. Log out. + + 6. Crash files written. + + To test the core file, either use `apport-unpack` on the + /var/crash/*.crash file to extract the CoreDump file or use `apport- + retrace -g` on the .crash file. It will fail to print the backtrace: + + ``` + $ apport-retrace -g /var/crash/_usr_bin_gnome-shell.1000.crash + [...] + Warnung: Error reading shared library list entry at 0x646c7472 + Failed to read a valid object file image from memory. + Core was generated by `/usr/bin/gnome-shell'. + Program terminated with signal SIGSEGV, Segmentation fault. + Warnung: Section `.reg-xstate/10527' in core file too small. + (gdb) bt + #0 0x7fe1c8090ffb in ?? () + Backtrace stopped: Cannot access memory at address 0x7ffd59a40fe0 + ``` ** Description changed: Repeatedly unusable truncated crash files: Bug 2012974, bug 2015842, bug 2015140, bug 2012075 Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete. If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell). Running `apport-retrace -g $crash` on the .crash files will fail with "/tmp/apport_core_[...] is not a core dump: file format not recognized" Steps to reproduce == 1. Use Ubuntu 23.04 (lunar) desktop with GNOME shell 2. Downgrade gjs and libgjs0g to 1.76.0-1 (for triggering bug 1974293) 3. Remove all crashes: `sudo rm -f /var/crash/*` 4. Interact with the desktop, icon grid and calendar for 30 seconds. 5. Log out. 6. Crash files written. To test the core file, either use `apport-unpack` on the /var/crash/*.crash file to extract the CoreDump file or use `apport- retrace -g` on the .crash file. It will fail to print the backtrace: ``` $ apport-retrace -g /var/crash/_usr_bin_gnome-shell.1000.crash [...] Warnung: Error reading shared library list entry at 0x646c7472 Failed to read a valid object file image from memory. Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGSEGV, Segmentation fault. Warnung: Section `.reg-xstate/10527' in core file too small. (gdb) bt #0 0x7fe1c8090ffb in ?? () Backtrace stopped: Cannot access memory at address 0x7ffd59a40fe0 ``` + + You can use the 0001-apport-Write-coredump-at-beginning-and-quit.patch + on apport to only write the coredump and adjust the slowdown to 100% + reproduce the behavior on log-out. -- 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/2015857 Title: Repeatedly unusable truncated crash files (on log-out) Status in apport package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Repeatedly unusable truncated crash files: Bug 2012974, bug 2015842, bug 2015140, bug 2012075 Based on my own testing, the problems seems to happen if multiple binaries crash simu
[Kernel-packages] [Bug 2016991] Re: Regression in ena NIC - /sys/class/net/eth0/device/msi_irqs/ is empty
I can't provide all logs, but I hope this will be sufficient. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016991/+attachment/5665207/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2016991 Title: Regression in ena NIC - /sys/class/net/eth0/device/msi_irqs/ is empty Status in linux package in Ubuntu: Incomplete Bug description: It worked on kernel 5.15, and it doesn't on 5.19. Running on AWS instance, with the following: driver: ena version: 5.19.0-1022-aws firmware-version: expansion-rom-version: bus-info: :00:03.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no Linux ip-10-0-1-194 5.19.0-1022-aws #23~22.04.1-Ubuntu SMP Fri Mar 17 15:38:24 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux dmesg: [5.485138] ena :00:03.0: ENA device version: 0.10 [5.485146] ena :00:03.0: ENA controller version: 0.0.1 implementation version 1 [5.487074] ena :00:03.0: LLQ is not supported Fallback to host mode policy. ... [5.533589] ena :00:03.0: Elastic Network Adapter (ENA) found at mem 8300, mac addr 02:08:84:31:35:a9 Interrupt mapping: 210: 35669 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 xen-pirq -msi-x ena-mgmnt@pci::00:03.0 211: 1079105381 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 xen-pirq -msi-x eth0-Tx-Rx-0 212: 0 1047885215 0 0 0 0 0 0 0 0 0 0 0 0 0 0 xen-pirq -msi-x eth0-Tx-Rx-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016991/+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 2001914] Re: [i915] [drm] GPU HANG: ecode 12:0:00000000
On my machine (Framework 13, 12th Gen Intel), this started when I upgraded 22.10 from 5.19.0-38-generic to 5.19.0-40-generic. After downgrade, it hasn't returned for now. I wonder if others also have this line about "fence" before each hang like I do: Apr 18 18:22:20 kernel: Asynchronous wait on fence :00:02.0:gnome-shell[2578]:47f4 timed out (hint:intel_atomic_commit_ready [i915]) Apr 18 18:22:22 kernel: i915 :00:02.0: [drm] GPU HANG: ecode 12:0: Apr 18 18:22:22 kernel: i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Apr 18 18:22:22 kernel: i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin version 70.1 Apr 18 18:22:22 kernel: i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 Apr 18 18:22:22 kernel: i915 :00:02.0: [drm] HuC authenticated Apr 18 18:22:22 kernel: i915 :00:02.0: [drm] GuC submission enabled Apr 18 18:22:22 kernel: i915 :00:02.0: [drm] GuC SLPC enabled The only other difference I notice compared to -38 is a new error/warning at each boot on -40: Apr 19 00:35:20 kernel: i915 :00:02.0: [drm] Selective fetch area calculation failed in pipe A Do we have this patch applied (as mentioned on the freedesktop.org issue? https://patchwork.freedesktop.org/series/114080/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2001914 Title: [i915] [drm] GPU HANG: ecode 12:0: Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.17 package in Ubuntu: Confirmed Bug description: When I open the terminal or just browsing, gnom sometimes freezes for a second, but sometimes restart the machine is necessary. The log is: Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm]i915 :00:02.0: [drm] GPU HANG: ecode 12:0: Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_62.0.3.bin version 62.0 submission:enabled Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC SLPC: enabled Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 authenticated:yes Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: last_user_time (2748010) is greater than comparison timestamp (2743419). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: 0xc0003c appears to be one of the offending windows with a timestamp of 2748010. Working around... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg ./boot/grub/loopback.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Jan 5 12:25:49 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-02 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2001914/+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 2016991] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2016991 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2016991 Title: Regression in ena NIC - /sys/class/net/eth0/device/msi_irqs/ is empty Status in linux package in Ubuntu: Incomplete Bug description: It worked on kernel 5.15, and it doesn't on 5.19. Running on AWS instance, with the following: driver: ena version: 5.19.0-1022-aws firmware-version: expansion-rom-version: bus-info: :00:03.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no Linux ip-10-0-1-194 5.19.0-1022-aws #23~22.04.1-Ubuntu SMP Fri Mar 17 15:38:24 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux dmesg: [5.485138] ena :00:03.0: ENA device version: 0.10 [5.485146] ena :00:03.0: ENA controller version: 0.0.1 implementation version 1 [5.487074] ena :00:03.0: LLQ is not supported Fallback to host mode policy. ... [5.533589] ena :00:03.0: Elastic Network Adapter (ENA) found at mem 8300, mac addr 02:08:84:31:35:a9 Interrupt mapping: 210: 35669 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 xen-pirq -msi-x ena-mgmnt@pci::00:03.0 211: 1079105381 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 xen-pirq -msi-x eth0-Tx-Rx-0 212: 0 1047885215 0 0 0 0 0 0 0 0 0 0 0 0 0 0 xen-pirq -msi-x eth0-Tx-Rx-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016991/+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 2016991] [NEW] Regression in ena NIC - /sys/class/net/eth0/device/msi_irqs/ is empty
Public bug reported: It worked on kernel 5.15, and it doesn't on 5.19. Running on AWS instance, with the following: driver: ena version: 5.19.0-1022-aws firmware-version: expansion-rom-version: bus-info: :00:03.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no Linux ip-10-0-1-194 5.19.0-1022-aws #23~22.04.1-Ubuntu SMP Fri Mar 17 15:38:24 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux dmesg: [5.485138] ena :00:03.0: ENA device version: 0.10 [5.485146] ena :00:03.0: ENA controller version: 0.0.1 implementation version 1 [5.487074] ena :00:03.0: LLQ is not supported Fallback to host mode policy. ... [5.533589] ena :00:03.0: Elastic Network Adapter (ENA) found at mem 8300, mac addr 02:08:84:31:35:a9 Interrupt mapping: 210: 35669 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 xen-pirq -msi-x ena-mgmnt@pci::00:03.0 211: 1079105381 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 xen-pirq -msi-x eth0-Tx-Rx-0 212: 0 1047885215 0 0 0 0 0 0 0 0 0 0 0 0 0 0 xen-pirq -msi-x eth0-Tx-Rx-1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2016991 Title: Regression in ena NIC - /sys/class/net/eth0/device/msi_irqs/ is empty Status in linux package in Ubuntu: Incomplete Bug description: It worked on kernel 5.15, and it doesn't on 5.19. Running on AWS instance, with the following: driver: ena version: 5.19.0-1022-aws firmware-version: expansion-rom-version: bus-info: :00:03.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no Linux ip-10-0-1-194 5.19.0-1022-aws #23~22.04.1-Ubuntu SMP Fri Mar 17 15:38:24 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux dmesg: [5.485138] ena :00:03.0: ENA device version: 0.10 [5.485146] ena :00:03.0: ENA controller version: 0.0.1 implementation version 1 [5.487074] ena :00:03.0: LLQ is not supported Fallback to host mode policy. ... [5.533589] ena :00:03.0: Elastic Network Adapter (ENA) found at mem 8300, mac addr 02:08:84:31:35:a9 Interrupt mapping: 210: 35669 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 xen-pirq -msi-x ena-mgmnt@pci::00:03.0 211: 1079105381 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 xen-pirq -msi-x eth0-Tx-Rx-0 212: 0 1047885215 0 0 0 0 0 0 0 0 0 0 0 0 0 0 xen-pirq -msi-x eth0-Tx-Rx-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016991/+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 2015531] Re: Mute/mic LEDs no function on a HP platfrom
This patch was in stable queue. So it's in 6.1.0-1009-oem. I'll set to invalid. Thanks. ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2015531 Title: Mute/mic LEDs no function on a HP platfrom Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Invalid Status in linux source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ProBook Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] Apply this patch on OEM-6.1, and after applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2015531/+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 2015531] Re: Mute/mic LEDs no function on a HP platfrom
I don't see a patch on the list for this? -- 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/2015531 Title: Mute/mic LEDs no function on a HP platfrom Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ProBook Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] Apply this patch on OEM-6.1, and after applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2015531/+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 2013088] Re: kernel: fix __clear_user() inline assembly constraints
Due to: https://lists.ubuntu.com/archives/kernel-team/2023-April/138879.html "Already applied as part of upstream stable v6.2.10." I'll update the lunar entry status to Fix Released. ** Changed in: linux (Ubuntu Lunar) Status: In Progress => 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/2013088 Title: kernel: fix __clear_user() inline assembly constraints Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Released Bug description: SRU Justification: == [ Impact ] * In case clear_user() crosses two pages and faults on the second page the kernel may write lowcore contents to the first page, instead of clearing it. * The __clear_user() inline assembly misses earlyclobber constraint modifiers. Depending on compiler and compiler options this may lead to incorrect code which copies kernel lowcore contents to user space instead of clearing memory, in case clear_user() faults. [Fix] * For Kinetic and Jammy cherrypick of 89aba4c26fae 89aba4c26fae4e459f755a18912845c348ee48f3 "s390/uaccess: add missing earlyclobber annotations to __clear_user()" * For Focal and Bionic a backport of the above commit is needed: https://launchpadlibrarian.net/659551648/s390-uaccess.patch [ Test Plan ] * A test program in C is needed and used for testing. * The test will be done by IBM. [ Where problems could occur ] * The modification is limited to function 'long __clear_user'. * And there, just to one inline assembly constraints line. * This is usually difficult to trace. * A erroneous modification may lead to a wrong behavior in 'long __clear_user', * and maybe returning a wrong size (in uaccess.c). [ Other Info ] * This affects all Ubuntu releases in service, down to 18.04. * Since we are close to 23.04 kernel freeze, I submit a patch request for 23.04 separately, and submit the SRU request for the all other Ubuntu releases later. __ Description: kernel: fix __clear_user() inline assembly constraints Symptom: In case clear_user() crosses two pages and faults on the second page the kernel may write lowcore contents to the first page, instead of clearing it. Problem: The __clear_user() inline assembly misses earlyclobber constraint modifiers. Depending on compiler and compiler options this may lead to incorrect code which copies kernel lowcore contents to user space instead of clearing memory, in case clear_user() faults. Solution: Add missing earlyclobber constraint modifiers. Preventive:yes Upstream-ID: 89aba4c26fae4e459f755a18912845c348ee48f3 Affected Releases: 18.04 20.04 22.04 22.10 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2013088/+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 2011817] Re: Intel Alder Lake GPU performance much lower in 6.1/6.2 compared to 5.19
** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/2011817 Title: Intel Alder Lake GPU performance much lower in 6.1/6.2 compared to 5.19 Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Bug description: Intel Alder Lake GPU performance is much lower in 6.1 compared to 5.19. For example, benchmarking gnome-shell main running on Xorg: 6.1.0-16-generic 30.02 FPS, average: 15.5ms, peak: 16.4ms intel_gpu_top says 211/208 MHz despite gt_min_freq_mhz==300 5.19.0-21-generic 60.00 FPS, average: 8.3ms, peak: 8.7ms intel_gpu_top says 542/560 MHz The issue is so severe in 6.1.0-16-generic that even triple buffering can't fix it for Xorg sessions. It does for Wayland though. I can work around it with `cp gt_max_freq_mhz gt_min_freq_mhz` but probably shouldn't need to. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.1.0-16-generic 6.1.0-16.16 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan1730 F wireplumber /dev/snd/seq:dan1727 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Mar 16 19:31:50 2023 InstallationDate: Installed on 2022-11-28 (108 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) MachineType: Intel(R) Client Systems NUC12DCMi7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=3a6db1e7-0341-452a-80e1-2895838feeac ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-16-generic N/A linux-backports-modules-6.1.0-16-generic N/A linux-firmware20230302.git60971a64-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: dmi.product.family: DC dmi.product.name: NUC12DCMi7 dmi.product.sku: RNUC12DCMi7 dmi.product.version: M30143-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2011817/+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 2007001] Re: Blank console display with aarch64 kernel 5.19.0-31
Hi Matthew, Thanks for your test kernel (and thanks for upload the jammy hwe version of it too) I can confirm this kernels gives me video output in VMware Fusion 13.0.1 No error on vmwgfx startup: [0.00] Linux version 5.19.0-38-generic (buildd@bos02-arm64-003) (aarch64-linux-gnu-gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #39~22.04.1+TEST2007001v20230418b1-Ubuntu SMP PREEMPT_DYNAMIC Tu (Ubuntu 5.19.0-38.39~22.04.1+TEST2007001v20230418b1-generic 5.19.17) [...] [1.284460] vmwgfx :00:0f.0: [drm] Register MMIO at 0x0x3d00 size is 4096 kiB [1.285181] vmwgfx :00:0f.0: [drm] VRAM at 0x7000 size is 131072 kiB [1.285193] vmwgfx :00:0f.0: [drm] Running on SVGA version 3. [1.285196] vmwgfx :00:0f.0: [drm] Capabilities: cursor, cursor bypass, alpha cursor, 3D, pitchlock, irq mask, traces, command buffers, command buffers 2, gbobject, dx, hp cmd queue, no bb restriction, cap2 register, [1.285201] vmwgfx :00:0f.0: [drm] Capabilities2: grow otable, intra surface copy, dx2, gb memsize 2, screendma reg, otable ptdepth2, non ms to ms stretchblt, cursor mob, mshint, cb max size 4mb, dx3, frame type, trace full fb, extra regs, lo staging, [1.285204] vmwgfx :00:0f.0: [drm] DMA map mode: Caching DMA mappings. [1.285243] vmwgfx :00:0f.0: [drm] Legacy memory limits: VRAM = 4096 kB, FIFO = 256 kB, surface = 524288 kB [1.285259] vmwgfx :00:0f.0: [drm] MOB limits: max mob size = 1048576 kB, max mob pages = 524288 [1.285261] vmwgfx :00:0f.0: [drm] Maximum display memory size is 262144 kiB [1.289628] vmwgfx :00:0f.0: [drm] No GMR memory available. Graphics memory resources are very limited. [1.289794] vmwgfx :00:0f.0: [drm] Screen Target display unit initialized [1.290031] vmwgfx :00:0f.0: [drm] Using command buffers with DMA pool. [1.290037] vmwgfx :00:0f.0: [drm] Available shader model: SM_5_1X. [1.290439] Console: switching to colour frame buffer device 128x48 [1.291782] [drm] Initialized vmwgfx 2.20.0 20211206 for :00:0f.0 on minor 0 To double check, I reinstalled the latest 5.19 HWE kernel for 22.04 and double-checked I could reproduce the issue in the archive: [0.00] Linux version 5.19.0-40-generic (buildd@bos02-arm64-021) (aarch64-linux-gnu-gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #41~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 31 16:02:33 UTC 2 (Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17) [...] [0.739889] vmwgfx :00:0f.0: BAR 2: can't reserve [mem 0x7000-0x77ff 64bit pref] [0.739893] vmwgfx: probe of :00:0f.0 failed with error -16 Thanks a lot for the fix and looking forward to seeing it in jammy- updates :-) -- 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/2007001 Title: Blank console display with aarch64 kernel 5.19.0-31 Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: In Progress Bug description: Upgraded the kernel on 22.10 aarch64 (running in a VM on VMware Fusion 13.0.1 on Apple Silicon_ from 5.19.0-29 to 5.19.0-31. After the upgrade and after rebooting the VM no text or graphical console appears on the VM. The VM is running and can be accessed through SSH. Rebooting the VM with kernel 5.19.0-29 - everything is working as expected. Text and graphical consoles now display properly. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Sat Feb 11 13:04:22 2023 InstallationDate: Installed on 2022-09-11 (153 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha arm64 (20220911) IwConfig: lono wireless extensions. ens160no wireless extensions. MachineType: VMware, Inc. VMware20,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=5e9795ee-63e3-4df1-93e9-c36cd88c726c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2022 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW201.00V.20904234.BA64.2212051119 dmi.
[Kernel-packages] [Bug 2016979] [NEW] Nvidia daemon doesn't terminate properly
Public bug reported: Every reboot or shutdown, the nvidia daemon doesn't terminate properly: Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: State 'stop-sigterm' timed out. Killing. Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Killing process 1832 (nvidia-persiste) with signal SIGKILL. Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Main process exited, code=killed, status=9/KILL Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Failed with result 'timeout'. Apr 19 01:00:31 ZB systemd[1]: Stopped NVIDIA Persistence Daemon. ** Affects: nvidia-graphics-drivers-530 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-530 in Ubuntu. https://bugs.launchpad.net/bugs/2016979 Title: Nvidia daemon doesn't terminate properly Status in nvidia-graphics-drivers-530 package in Ubuntu: New Bug description: Every reboot or shutdown, the nvidia daemon doesn't terminate properly: Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: State 'stop-sigterm' timed out. Killing. Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Killing process 1832 (nvidia-persiste) with signal SIGKILL. Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Main process exited, code=killed, status=9/KILL Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Failed with result 'timeout'. Apr 19 01:00:31 ZB systemd[1]: Stopped NVIDIA Persistence Daemon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-530/+bug/2016979/+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 1998711] Re: Control key not working in Ubuntu 22.04.1
it also affect me and already tried with this link to troubleshoot https://wiki.ubuntu.com/Hotkeys/Troubleshooting and it looks like the ctrl, alt, super key recognized as shift key -- 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/1998711 Title: Control key not working in Ubuntu 22.04.1 Status in linux package in Ubuntu: Confirmed Bug description: Upon research into several posted solutions the issue remains. 1.Ubuntu 22.04.1 LTS and GNOME tweaks 42.5 installed 2. Using apt-cache policy pkgname does not work in terminal 3. Left and right control (ctrl) buttons are not working on my Thinkpad t580 for anything (copy, paste, quit, etc) 4. Nothing, when trying to paste with 'ctrl+v' it simple input a 'v' Went through several iterations of clearing shortcuts, local pointers, reset keyboard language layouts, and iBus/None in language. Nothing has worked up to this point so reporting a bug as a last attempt to fix the issue. Only option not done yet is reinstalling Ubuntu but won't do that until school semester is over (final exams complete). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: craiga71746 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-15 (143 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20L9CTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=eaad8663-e31b-44fd-99a0-8818cbb4a61a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: wayland-session jammy Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: N27ET45W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L9CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrN27ET45W(1.31):bd12/14/2021:br1.31:efr1.15:svnLENOVO:pn20L9CTO1WW:pvrThinkPadT580:rvnLENOVO:rn20L9CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L9_BU_Think_FM_ThinkPadT580: dmi.product.family: ThinkPad T580 dmi.product.name: 20L9CTO1WW dmi.product.sku: LENOVO_MT_20L9_BU_Think_FM_ThinkPad T580 dmi.product.version: ThinkPad T580 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998711/+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 2016976] Re: package linux-modules-nvidia-525-5.19.0-40-generic 5.19.0-40.41~22.04.1+1 failed to install/upgrade: installed linux-modules-nvidia-525-5.19.0-40-generic package po
** Package changed: ubuntu => linux-restricted-modules-hwe-5.19 (Ubuntu) ** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2016976 Title: package linux-modules-nvidia-525-5.19.0-40-generic 5.19.0-40.41~22.04.1+1 failed to install/upgrade: installed linux- modules-nvidia-525-5.19.0-40-generic package post-installation script subprocess returned error exit status 127 Status in linux-restricted-modules-hwe-5.19 package in Ubuntu: New Bug description: while iam booting ubuntu the first things is coming error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-nvidia-525-5.19.0-40-generic 5.19.0-40.41~22.04.1+1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 19 14:37:12 2023 DuplicateSignature: package:linux-modules-nvidia-525-5.19.0-40-generic:5.19.0-40.41~22.04.1+1 Setting up linux-modules-nvidia-525-5.19.0-40-generic (5.19.0-40.41~22.04.1+1) ... /var/lib/dpkg/info/linux-modules-nvidia-525-5.19.0-40-generic.config: 6: /etc/default/linux-modules-nvidia: linux-modules-nvidia-525-open-generic-hwe-22.04: not found dpkg: error processing package linux-modules-nvidia-525-5.19.0-40-generic (--configure): installed linux-modules-nvidia-525-5.19.0-40-generic package post-installation script subprocess returned error exit status 127 ErrorMessage: installed linux-modules-nvidia-525-5.19.0-40-generic package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2023-01-31 (77 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-restricted-modules-hwe-5.19 Title: package linux-modules-nvidia-525-5.19.0-40-generic 5.19.0-40.41~22.04.1+1 failed to install/upgrade: installed linux-modules-nvidia-525-5.19.0-40-generic package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.19/+bug/2016976/+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 1960309] Re: kselftest ftrace inter-event histogram trigger snapshot action failure
Check with hinted kernels, this issue does not exist anymore. ** Changed in: linux (Ubuntu) Status: Expired => 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/1960309 Title: kselftest ftrace inter-event histogram trigger snapshot action failure Status in linux package in Ubuntu: Fix Released Bug description: This ftrace sub-test is failing on focal with the latest hwe-5.15: [stdout] # [67] event trigger - test inter-event histogram trigger snapshot action[FAIL] We have not seen this failure before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960309/+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
