[Kernel-packages] [Bug 2009676] [NEW] Add support for Raptor Lake S CPUs
Public bug reported: [Impact] * Support thermald on Raptor Lake S CPU. [Test Plan] * Use a machine with a Raptor Lake S cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake S in thermald, which won't impact other hardware. [Other Info] https://github.com/intel/thermal_daemon/commit/e03493dc1e972374c1686492655250f8f48a15ba ** Affects: oem-priority Importance: Undecided Status: New ** Affects: thermald (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-2008667 sutton ** Information type changed from Proprietary to Public ** Also affects: thermald (Ubuntu) Importance: Undecided Status: New ** Tags added: oem-priority originate-from-2008667 sutton -- 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/2009676 Title: Add support for Raptor Lake S CPUs Status in OEM Priority Project: New Status in thermald package in Ubuntu: New Bug description: [Impact] * Support thermald on Raptor Lake S CPU. [Test Plan] * Use a machine with a Raptor Lake S cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake S in thermald, which won't impact other hardware. [Other Info] https://github.com/intel/thermal_daemon/commit/e03493dc1e972374c1686492655250f8f48a15ba To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009542] Re: Can not select HDMI or Displayport as audio output device.
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.19 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009542 Title: Can not select HDMI or Displayport as audio output device. Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After I installed "linux-image-5.19.0-35-generic" package, I can not select HDMI or Displayport as audio output device in gnome setting. When I am using "linux-image-5.19.0-32-generic" package, I can select that. My PC also have S/PDIF as audio output device, I can select it. My environment is follows. Description: Ubuntu 22.04.2 LTS Release: 22.04 Graphics board: Radeon RX6600 Graphics driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998244] Re: kselftest net/fib_nexthop_nongw.sh fails
Test passed on jammy:linux-kvm/5.19.9-1029.34
09:24:21 DEBUG| Running 'make run_tests -C net TEST_PROGS=fib_nexthop_nongw.sh
TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
19349 09:24:21 DEBUG| [stdout] make: Entering
directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
19350 09:24:21 DEBUG| [stdout] make
--no-builtin-rules ARCH=x86 -C ../../../.. headers_install
19351 09:24:21 DEBUG| [stdout] make[1]: Entering
directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
19352 09:24:22 DEBUG| [stdout] INSTALL ./usr/include
19353 09:24:22 DEBUG| [stdout] make[1]: Leaving
directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
19354 09:24:22 DEBUG| [stdout] TAP version 13
19355 09:24:22 DEBUG| [stdout] 1..1
19356 09:24:22 DEBUG| [stdout] # selftests: net:
fib_nexthop_nongw.sh
19357 09:24:22 DEBUG| [stdout] # TEST: nexthop: get
route with nexthop without gw[ OK ]
19358 09:24:22 DEBUG| [stdout] # TEST: nexthop: ping
through nexthop without gw [ OK ]
19359 09:24:22 DEBUG| [stdout] ok 1 selftests: net:
fib_nexthop_nongw.sh
19360 09:24:22 DEBUG| [stdout] make: Leaving
directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
19361 09:24:23 INFO | GOOD
ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh
ubuntu_kernel_selftests.net:fib_nexthop_nongw.shtimestamp=1676021063
localtime=Feb 10 09:24:23completed successfully
19362 09:24:23 INFO | END GOOD
ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh
ubuntu_kernel_selftests.net:fib_nexthop_nongw.shtimestamp=1676021063
localtime=Feb 10 09:24:23
19363 09:24:23 DEBUG| Persistent state
client._record_indent now set to 1
19364 09:24:23 DEBUG| Persistent state
client.unexpected_reboot deleted
** 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-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1998244
Title:
kselftest net/fib_nexthop_nongw.sh fails
Status in linux-kvm package in Ubuntu:
Confirmed
Status in linux-kvm source package in Jammy:
Fix Committed
Status in linux-kvm source package in Kinetic:
Fix Committed
Status in linux-kvm source package in Lunar:
Confirmed
Bug description:
18272 03:33:07 DEBUG| Persistent state client._record_indent
now set to 2
18273 03:33:07 DEBUG| Persistent state
client.unexpected_reboot now set to
('ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh',
'ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh')
18274 03:33:07 DEBUG| Waiting for pid 58525 for 2700 seconds
18275 03:33:07 WARNI| System python is too old, crash
handling disabled
18276 03:33:07 DEBUG| Running 'make run_tests -C net
TEST_PROGS=fib_nexthop_nongw.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
18277 03:33:07 DEBUG| [stdout] make: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
18278 03:33:07 DEBUG| [stdout] make --no-builtin-rules
ARCH=x86 -C ../../../.. headers_install
18279 03:33:07 DEBUG| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
18280 03:33:08 DEBUG| [stdout] INSTALL ./usr/include
18281 03:33:08 DEBUG| [stdout] make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
18282 03:33:08 DEBUG| [stdout] TAP version 13
18283 03:33:08 DEBUG| [stdout] 1..1
18284 03:33:08 DEBUG| [stdout] # selftests: net:
fib_nexthop_nongw.sh
18285 03:33:08 DEBUG| [stdout] # Error: Unknown device type.
18286 03:33:08 DEBUG| [stdout] # Cannot find device "eth0"
18287 03:33:08 DEBUG| [stdout] # Cannot find device "eth0"
18288 03:33:08 DEBUG| [stdout] # TEST: nexthop: get route
with nexthop without gw[ OK ]
18289 03:33:18 DEBUG| [stdout] # TEST: nexthop: ping through
nexthop without gw [FAIL]
18290 03:33:18 DEBUG| [stdout] not ok 1 selftests: net:
fib_nexthop_nongw.sh # exit=1
18291 03:33:18 DEBUG| [stdout] make: Leaving directory
[Kernel-packages] [Bug 2009676] Re: Add support for Raptor Lake S CPUs
Hi koba, I heard you will bump new version of thermald for jammy, may I know your schedule about it? Thanks! -- 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/2009676 Title: Add support for Raptor Lake S CPUs Status in OEM Priority Project: New Status in thermald package in Ubuntu: New Bug description: [Impact] * Support thermald on Raptor Lake S CPU. [Test Plan] * Use a machine with a Raptor Lake S cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake S in thermald, which won't impact other hardware. [Other Info] https://github.com/intel/thermal_daemon/commit/e03493dc1e972374c1686492655250f8f48a15ba To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990750] Re: Boot issue with Ubuntu 22.10 Kinetic Kudu since Kernel 5.19.0.15.15, now hanging with blinking cursor after update to Kernel 5.19.0.21.21
Adding a note here too (as well as the discourse page). I had this bug happen to be via phased updates, exactly as ubfan1 mentioned above. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1990750 Title: Boot issue with Ubuntu 22.10 Kinetic Kudu since Kernel 5.19.0.15.15, now hanging with blinking cursor after update to Kernel 5.19.0.21.21 Status in linux package in Ubuntu: Confirmed Bug description: When starting the PC, the splash screen freezes with the motherboard logo displayed. As my disk is encrypted the decryption field does not appear below the logo. By typing [ALT] + [CTRL] + [DEL] then the splash screen appears again followed by a start-up menu with the following line: *Ubuntu Advanced options for Ubuntu By selecting 'Advanced options for Ubuntu' the following submenu appears: *Ubuntu, with Linux5.19.0-15-generic Ubuntu, with Linux5.19.0-15-generic (recovery mode) Selecting the second option, then the system starts loading with the initial lines of code: Loading Linux 5.19.0-15-generic ... Loading initial ramdisk ... When code has finished loading, the last line at the bottom of the screen is for unlocking the disk: Begin: Mounting root fie system ... Begin Running /script/local-top ... Please unlock disk nvme0n1p3_crypt: Then i type in the code and hit [return] and more code is loading, until a recovery menu with purple background appears, with the title: Recovery Menu (filesystem state: read-only). I select the first menu item: resume Resume normal boot and hit [return]. The menu changes to the notification: You are now going to exit the recovery mode bla bla bla with the [OK] button below it. I hit the [OK] button and then the login screen finally appears. I will post a video of the complete boot sequence later on as I need to install a softaware to edit the video. It is noteworthy that on my previous Ubuntu 22.04 install the same issue with the frozen splash screen occurred when my system was updated with Kernel 5.15.5, but then I did not try out to execute the [ALT] + [CTRL] + [DEL] command. Therefore the bug is probably affecting all kernels from 5.15.5 upwards. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset wl nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Sep 25 08:30:29 2022 InstallationDate: Installed on 2022-09-24 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220920) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/vgubuntu-root ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 (regression from -32)
@kobako the 5.19.9001-34-generic kernel provided in comment 12 is also "bad" (same symptoms, same dmesg lines as seen in the -35 kernel) -- 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 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: In Progress Bug 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 1990750] Re: Boot issue with Ubuntu 22.10 Kinetic Kudu since Kernel 5.19.0.15.15, now hanging with blinking cursor after update to Kernel 5.19.0.21.21
*** This bug is a duplicate of bug 1975650 *** https://bugs.launchpad.net/bugs/1975650 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1975650, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1975650 Nvidia kernel driver stops loading after kernel update (needs manual reinstallation) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1990750 Title: Boot issue with Ubuntu 22.10 Kinetic Kudu since Kernel 5.19.0.15.15, now hanging with blinking cursor after update to Kernel 5.19.0.21.21 Status in linux package in Ubuntu: Confirmed Bug description: When starting the PC, the splash screen freezes with the motherboard logo displayed. As my disk is encrypted the decryption field does not appear below the logo. By typing [ALT] + [CTRL] + [DEL] then the splash screen appears again followed by a start-up menu with the following line: *Ubuntu Advanced options for Ubuntu By selecting 'Advanced options for Ubuntu' the following submenu appears: *Ubuntu, with Linux5.19.0-15-generic Ubuntu, with Linux5.19.0-15-generic (recovery mode) Selecting the second option, then the system starts loading with the initial lines of code: Loading Linux 5.19.0-15-generic ... Loading initial ramdisk ... When code has finished loading, the last line at the bottom of the screen is for unlocking the disk: Begin: Mounting root fie system ... Begin Running /script/local-top ... Please unlock disk nvme0n1p3_crypt: Then i type in the code and hit [return] and more code is loading, until a recovery menu with purple background appears, with the title: Recovery Menu (filesystem state: read-only). I select the first menu item: resume Resume normal boot and hit [return]. The menu changes to the notification: You are now going to exit the recovery mode bla bla bla with the [OK] button below it. I hit the [OK] button and then the login screen finally appears. I will post a video of the complete boot sequence later on as I need to install a softaware to edit the video. It is noteworthy that on my previous Ubuntu 22.04 install the same issue with the frozen splash screen occurred when my system was updated with Kernel 5.15.5, but then I did not try out to execute the [ALT] + [CTRL] + [DEL] command. Therefore the bug is probably affecting all kernels from 5.15.5 upwards. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset wl nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Sep 25 08:30:29 2022 InstallationDate: Installed on 2022-09-24 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220920) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/vgubuntu-root ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990750/+subscriptions -- Mailing l
[Kernel-packages] [Bug 1990750] Re: Boot issue with Ubuntu 22.10 Kinetic Kudu since Kernel 5.19.0.15.15, now hanging with blinking cursor after update to Kernel 5.19.0.21.21
*** This bug is a duplicate of bug 1975650 *** https://bugs.launchpad.net/bugs/1975650 Comments #24-#25 seem to confirm the original issue for the OP was in fact bug 1975650. If anyone is experiencing a different or new issue then please open a new bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1990750 Title: Boot issue with Ubuntu 22.10 Kinetic Kudu since Kernel 5.19.0.15.15, now hanging with blinking cursor after update to Kernel 5.19.0.21.21 Status in linux package in Ubuntu: Confirmed Bug description: When starting the PC, the splash screen freezes with the motherboard logo displayed. As my disk is encrypted the decryption field does not appear below the logo. By typing [ALT] + [CTRL] + [DEL] then the splash screen appears again followed by a start-up menu with the following line: *Ubuntu Advanced options for Ubuntu By selecting 'Advanced options for Ubuntu' the following submenu appears: *Ubuntu, with Linux5.19.0-15-generic Ubuntu, with Linux5.19.0-15-generic (recovery mode) Selecting the second option, then the system starts loading with the initial lines of code: Loading Linux 5.19.0-15-generic ... Loading initial ramdisk ... When code has finished loading, the last line at the bottom of the screen is for unlocking the disk: Begin: Mounting root fie system ... Begin Running /script/local-top ... Please unlock disk nvme0n1p3_crypt: Then i type in the code and hit [return] and more code is loading, until a recovery menu with purple background appears, with the title: Recovery Menu (filesystem state: read-only). I select the first menu item: resume Resume normal boot and hit [return]. The menu changes to the notification: You are now going to exit the recovery mode bla bla bla with the [OK] button below it. I hit the [OK] button and then the login screen finally appears. I will post a video of the complete boot sequence later on as I need to install a softaware to edit the video. It is noteworthy that on my previous Ubuntu 22.04 install the same issue with the frozen splash screen occurred when my system was updated with Kernel 5.15.5, but then I did not try out to execute the [ALT] + [CTRL] + [DEL] command. Therefore the bug is probably affecting all kernels from 5.15.5 upwards. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset wl nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Sep 25 08:30:29 2022 InstallationDate: Installed on 2022-09-24 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220920) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/vgubuntu-root ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009685] [NEW] iwlwifi hard system crash when collecting data
Public bug reported: After a random amount of time the system crashes and everytime it has something to do with iwlwifi, always at the same line: WRT: Collecting data: ini trigger 4 fired (delay=0ms). This seems to be jumpstarted by an Error sending logs. Two examples: - Mar 2 15:57:26 ironwarrior kernel: [25087.967111] iwlwifi :00:14.3: Error sending SCAN_CFG_CMD: time out after 2000ms. - Mar 8 08:57:43 ironwarrior kernel: [ 155.033518] iwlwifi :00:14.3: Error sending STATISTICS_CMD: time out after 2000ms. When system hangs I am forced to do a hardware reset. Is there any short fix I can do to avoid this while it's being looked at? Assuming this is the right place to report this bug. Thank you lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 - lspci -nnk | grep 0280 -A3 00:14.3 Network controller [0280]: Intel Corporation Tiger Lake PCH CNVi WiFi [8086:43f0] (rev 11) DeviceName: Onboard - Ethernet Subsystem: Intel Corporation Wi-Fi 6 AX201 160MHz [8086:0074] Kernel driver in use: iwlwifi - apt-cache policy linux-firmware linux-firmware: Installed: 20220329.git681281e4-0ubuntu3.10 Candidate: 20220329.git681281e4-0ubuntu3.10 Version table: *** 20220329.git681281e4-0ubuntu3.10 500 500 http://pt.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://pt.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 20220329.git681281e4-0ubuntu3.9 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 20220329.git681281e4-0ubuntu1 500 500 http://pt.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://pt.archive.ubuntu.com/ubuntu jammy/main i386 Packages Random output text of /var/log/syslog Mar 8 08:57:43 ironwarrior kernel: [ 155.033518] iwlwifi :00:14.3: Error sending STATISTICS_CMD: time out after 2000ms. Mar 8 08:57:43 ironwarrior kernel: [ 155.033524] iwlwifi :00:14.3: Current CMD queue read_ptr 135 write_ptr 136 Mar 8 08:57:43 ironwarrior kernel: [ 155.035160] iwlwifi :00:14.3: Start IWL Error Log Dump: Mar 8 08:57:43 ironwarrior kernel: [ 155.035161] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 Mar 8 08:57:43 ironwarrior kernel: [ 155.035162] iwlwifi :00:14.3: Loaded firmware version: 72.daa05125.0 QuZ-a0-hr-b0-72.ucode Mar 8 08:57:43 ironwarrior kernel: [ 155.035163] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN Mar 8 08:57:43 ironwarrior kernel: [ 155.035164] iwlwifi :00:14.3: 0x22F0 | trm_hw_status0 Mar 8 08:57:43 ironwarrior kernel: [ 155.035165] iwlwifi :00:14.3: 0x | trm_hw_status1 Mar 8 08:57:43 ironwarrior kernel: [ 155.035166] iwlwifi :00:14.3: 0x004CC13E | branchlink2 Mar 8 08:57:43 ironwarrior kernel: [ 155.035167] iwlwifi :00:14.3: 0x00019940 | interruptlink1 Mar 8 08:57:43 ironwarrior kernel: [ 155.035168] iwlwifi :00:14.3: 0x00019940 | interruptlink2 Mar 8 08:57:43 ironwarrior kernel: [ 155.035168] iwlwifi :00:14.3: 0x004C3F84 | data1 Mar 8 08:57:43 ironwarrior kernel: [ 155.035169] iwlwifi :00:14.3: 0x0100 | data2 Mar 8 08:57:43 ironwarrior kernel: [ 155.035170] iwlwifi :00:14.3: 0x | data3 Mar 8 08:57:43 ironwarrior kernel: [ 155.035171] iwlwifi :00:14.3: 0x65C10249 | beacon time Mar 8 08:57:43 ironwarrior kernel: [ 155.035171] iwlwifi :00:14.3: 0xF0EBFDC9 | tsf low Mar 8 08:57:43 ironwarrior kernel: [ 155.035172] iwlwifi :00:14.3: 0x0076 | tsf hi Mar 8 08:57:43 ironwarrior kernel: [ 155.035173] iwlwifi :00:14.3: 0x | time gp1 Mar 8 08:57:43 ironwarrior kernel: [ 155.035173] iwlwifi :00:14.3: 0x08F462FA | time gp2 Mar 8 08:57:43 ironwarrior kernel: [ 155.035174] iwlwifi :00:14.3: 0x0001 | uCode revision type Mar 8 08:57:43 ironwarrior kernel: [ 155.035175] iwlwifi :00:14.3: 0x0048 | uCode version major Mar 8 08:57:43 ironwarrior kernel: [ 155.035176] iwlwifi :00:14.3: 0xDAA05125 | uCode version minor Mar 8 08:57:43 ironwarrior kernel: [ 155.035176] iwlwifi :00:14.3: 0x0351 | hw version Mar 8 08:57:43 ironwarrior kernel: [ 155.035177] iwlwifi :00:14.3: 0x00C89001 | board version Mar 8 08:57:43 ironwarrior kernel: [ 155.035178] iwlwifi :00:14.3: 0x80F4F400 | hcmd Mar 8 08:57:43 ironwarrior kernel: [ 155.035179] iwlwifi :00:14.3: 0x0002 | isr0 Mar 8 08:57:43 ironwarrior kernel: [ 155.035179] iwlwifi :00:14.3: 0x | isr1 Mar 8 08:57:43 ironwarrior kernel: [ 155.035180] iwlwifi :00:14.3: 0x08F04002 | isr2 Mar 8 08:57:43 ironwarrior kernel: [ 155.035181] iwlwifi :00:14.3: 0x00C1028C | isr3 Mar 8 08:57:43 ironwarrior kernel: [ 155.035181] iwlwifi :00:14.3: 0x
[Kernel-packages] [Bug 2009687] [NEW] [lunar] Nvidia GPU offloaded but still powered
Public bug reported: Hi, Lenovo Legion 5 16" i7 12700H RTX 3070 Ti Nvidia 525 proprietary driver (official Ubuntu packages) Nvidia on-demand mode Ubuntu Wayland or Xorg sessions Ubuntu Lunar up to date I noticed a high power usage using powertop (or simply remaining time in g-c-c...). Nvidia driver seems offloaded but gpu power usage still shows ~ 9W -> 23W, random. uname -a Linux ** 6.1.0-16-generic #16-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 24 14:37:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux nvidia-smi Wed Mar 8 10:59:21 2023 +-+ | NVIDIA-SMI 525.85.05Driver Version: 525.85.05CUDA Version: 12.0 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 NVIDIA GeForce ... Off | :01:00.0 Off | N/A | | N/A 34CP8 9W / 50W | 4MiB / 8192MiB | 0% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 5445 G /usr/bin/gnome-shell3MiB | +-+ glxinfo -B name of display: :1 display: :1 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel (0x8086) Device: Mesa Intel(R) Graphics (ADL GT2) (0x46a6) Version: 22.3.6 Accelerated: yes Video memory: 31821MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2) OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.3.6 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.3.6 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.3.6 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 lspci 00:00.0 Host bridge: Intel Corporation 12th Gen Core Processor Host Bridge/DRAM Registers (rev 02) 00:01.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x16 Controller #1 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c) 00:04.0 Signal processing controller: Intel Corporation Alder Lake Innovation Platform Framework Processor Participant (rev 02) 00:06.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #0 (rev 02) 00:06.2 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #2 (rev 02) 00:07.0 PCI bridge: Intel Corporation Alder Lake-P Thunderbolt 4 PCI Express Root Port #0 (rev 02) 00:0a.0 Signal processing controller: Intel Corporation Platform Monitoring Technology (rev 01) 00:0d.0 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 USB Controller (rev 02) 00:0d.2 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 NHI #0 (rev 02) 00:14.0 USB controller: Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller (rev 01) 00:14.2 RAM memory: Intel Corporation Alder Lake PCH Shared SRAM (rev 01) 00:14.3 Network controller: Intel Corporation Alder Lake-P PCH CNVi WiFi (rev 01) 00:15.0 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #0 (rev 01) 00:15.1 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #1 (rev 01) 00:16.0 Communication controller: Intel Corporation Alder Lake PCH HECI Controller (rev 01) 00:1d.0 PCI bridge: Intel Corporation Device 51b0 (rev 01) 00:1d.1 PCI bridge: Intel Corporation Alder Lake PCI Express x1 Root Port #10 (rev 01) 00:1f.0 ISA bridge: Intel Corporation Alder Lake PCH eSPI Controller (rev 01) 00:1f.3 Audio device: Intel Corpora
[Kernel-packages] [Bug 2009014] Re: Some QHD panels fail to refresh when PSR2 enabled
** Changed in: linux (Ubuntu Kinetic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009014 Title: Some QHD panels fail to refresh when PSR2 enabled Status in HWE Next: New Status in linux package in Ubuntu: Confirmed 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: Fix Committed Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: [Impact] Some QHD (2560x1440) panels which support PSR2 refresh the display abnormally. The display frequently stop responding for few seconds on all user interactions, ex. mouse movement, TTY and any APP GUI. There's no problem on the external monitor. After disabling PSR, the problem will be gone. [Fix] Intel release a fix to calculate the wake up line count and configure them into PSR2_CTL accordingly. [Test] Verified on the problematic panels to check if the display responds smoothly to mouse movement. [Where problems could occur] Only affects the panels on some particular panels which supports PSR2 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009014/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990750] Re: Boot issue with Ubuntu 22.10 Kinetic Kudu since Kernel 5.19.0.15.15, now hanging with blinking cursor after update to Kernel 5.19.0.21.21
*** This bug is a duplicate of bug 1975650 *** https://bugs.launchpad.net/bugs/1975650 @alextcranglesim This bug is not necessarily a duplicate of the referred bug https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1975650 It just happened to also arise in some cases with Kernel updates but this is just the last instance of it happening. The black screen with blinking cursor happened to me many times in the past when during a fresh install not installing proprietary drivers and later on installing nVidia drivers downloaded from nVidia. You can search the internet for 'black screen', 'ubuntu', 'blinking cursor', 'nVidia'... and will find plenty of issues reported but none of the solutions ever worked for me. The point is that I previously never knew how to handle this situation and resorted to a fresh install as I though my system was definitely broken. This is until I realized that it is still possible to access the system with some keyboard commands as explained above in order to start up Ubuntu and to restore its proper startup behaviour by subsequently updating the driver to the proprietary tested version, which was by the way only the last step in solving the black screen issue. The other bug report only provides the code to restore the drivers but not what to do when the system is hanging with the black screen. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1990750 Title: Boot issue with Ubuntu 22.10 Kinetic Kudu since Kernel 5.19.0.15.15, now hanging with blinking cursor after update to Kernel 5.19.0.21.21 Status in linux package in Ubuntu: Confirmed Bug description: When starting the PC, the splash screen freezes with the motherboard logo displayed. As my disk is encrypted the decryption field does not appear below the logo. By typing [ALT] + [CTRL] + [DEL] then the splash screen appears again followed by a start-up menu with the following line: *Ubuntu Advanced options for Ubuntu By selecting 'Advanced options for Ubuntu' the following submenu appears: *Ubuntu, with Linux5.19.0-15-generic Ubuntu, with Linux5.19.0-15-generic (recovery mode) Selecting the second option, then the system starts loading with the initial lines of code: Loading Linux 5.19.0-15-generic ... Loading initial ramdisk ... When code has finished loading, the last line at the bottom of the screen is for unlocking the disk: Begin: Mounting root fie system ... Begin Running /script/local-top ... Please unlock disk nvme0n1p3_crypt: Then i type in the code and hit [return] and more code is loading, until a recovery menu with purple background appears, with the title: Recovery Menu (filesystem state: read-only). I select the first menu item: resume Resume normal boot and hit [return]. The menu changes to the notification: You are now going to exit the recovery mode bla bla bla with the [OK] button below it. I hit the [OK] button and then the login screen finally appears. I will post a video of the complete boot sequence later on as I need to install a softaware to edit the video. It is noteworthy that on my previous Ubuntu 22.04 install the same issue with the frozen splash screen occurred when my system was updated with Kernel 5.15.5, but then I did not try out to execute the [ALT] + [CTRL] + [DEL] command. Therefore the bug is probably affecting all kernels from 5.15.5 upwards. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset wl nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Sep 25 08:30:29 2022 InstallationDate: Installed on 2022-09-24 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220920) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/vgubuntu-root ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chas
[Kernel-packages] [Bug 2009676] Re: Add support for Raptor Lake S CPUs
I've applied the patch for Jammy and uploaded a new version ready for SRU. thermald (2.4.9-1ubuntu0.2) jammy; urgency=medium * Add support for Raptor Lake S CPUs. (LP: #2009676) Date: Wed, 8 Mar 2023 11:28:31 + Changed-By: Colin Ian King Maintainer: Ubuntu Developers https://launchpad.net/ubuntu/+source/thermald/2.4.9-1ubuntu0.2 == OK: thermald_2.4.9.orig.tar.xz OK: thermald_2.4.9-1ubuntu0.2.debian.tar.xz OK: thermald_2.4.9-1ubuntu0.2.dsc -> Component: main Section: misc Upload Warnings: Redirecting ubuntu jammy to ubuntu jammy-proposed. This upload awaits approval by a distro manager Announcing to jammy-chan...@lists.ubuntu.com Thank you for your contribution to Ubuntu. ** Changed in: thermald (Ubuntu) Milestone: None => jammy-updates -- 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/2009676 Title: Add support for Raptor Lake S CPUs Status in OEM Priority Project: New Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: New Bug description: [Impact] * Support thermald on Raptor Lake S CPU. [Test Plan] * Use a machine with a Raptor Lake S cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake S in thermald, which won't impact other hardware. [Other Info] https://github.com/intel/thermal_daemon/commit/e03493dc1e972374c1686492655250f8f48a15ba To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009685] Re: iwlwifi hard system crash when collecting data
Forgot to take a look at the timestamps which seems to show the "problem" is more likely a consequence of hitting hardware restart. Closing this and trying to take an extra look at the problem again, then posting it on askubuntu ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2009685 Title: iwlwifi hard system crash when collecting data Status in linux-firmware package in Ubuntu: Invalid Bug description: After a random amount of time the system crashes and everytime it has something to do with iwlwifi, always at the same line: WRT: Collecting data: ini trigger 4 fired (delay=0ms). This seems to be jumpstarted by an Error sending logs. Two examples: - Mar 2 15:57:26 ironwarrior kernel: [25087.967111] iwlwifi :00:14.3: Error sending SCAN_CFG_CMD: time out after 2000ms. - Mar 8 08:57:43 ironwarrior kernel: [ 155.033518] iwlwifi :00:14.3: Error sending STATISTICS_CMD: time out after 2000ms. When system hangs I am forced to do a hardware reset. Is there any short fix I can do to avoid this while it's being looked at? Assuming this is the right place to report this bug. Thank you lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 - lspci -nnk | grep 0280 -A3 00:14.3 Network controller [0280]: Intel Corporation Tiger Lake PCH CNVi WiFi [8086:43f0] (rev 11) DeviceName: Onboard - Ethernet Subsystem: Intel Corporation Wi-Fi 6 AX201 160MHz [8086:0074] Kernel driver in use: iwlwifi - apt-cache policy linux-firmware linux-firmware: Installed: 20220329.git681281e4-0ubuntu3.10 Candidate: 20220329.git681281e4-0ubuntu3.10 Version table: *** 20220329.git681281e4-0ubuntu3.10 500 500 http://pt.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://pt.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 20220329.git681281e4-0ubuntu3.9 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 20220329.git681281e4-0ubuntu1 500 500 http://pt.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://pt.archive.ubuntu.com/ubuntu jammy/main i386 Packages Random output text of /var/log/syslog Mar 8 08:57:43 ironwarrior kernel: [ 155.033518] iwlwifi :00:14.3: Error sending STATISTICS_CMD: time out after 2000ms. Mar 8 08:57:43 ironwarrior kernel: [ 155.033524] iwlwifi :00:14.3: Current CMD queue read_ptr 135 write_ptr 136 Mar 8 08:57:43 ironwarrior kernel: [ 155.035160] iwlwifi :00:14.3: Start IWL Error Log Dump: Mar 8 08:57:43 ironwarrior kernel: [ 155.035161] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 Mar 8 08:57:43 ironwarrior kernel: [ 155.035162] iwlwifi :00:14.3: Loaded firmware version: 72.daa05125.0 QuZ-a0-hr-b0-72.ucode Mar 8 08:57:43 ironwarrior kernel: [ 155.035163] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN Mar 8 08:57:43 ironwarrior kernel: [ 155.035164] iwlwifi :00:14.3: 0x22F0 | trm_hw_status0 Mar 8 08:57:43 ironwarrior kernel: [ 155.035165] iwlwifi :00:14.3: 0x | trm_hw_status1 Mar 8 08:57:43 ironwarrior kernel: [ 155.035166] iwlwifi :00:14.3: 0x004CC13E | branchlink2 Mar 8 08:57:43 ironwarrior kernel: [ 155.035167] iwlwifi :00:14.3: 0x00019940 | interruptlink1 Mar 8 08:57:43 ironwarrior kernel: [ 155.035168] iwlwifi :00:14.3: 0x00019940 | interruptlink2 Mar 8 08:57:43 ironwarrior kernel: [ 155.035168] iwlwifi :00:14.3: 0x004C3F84 | data1 Mar 8 08:57:43 ironwarrior kernel: [ 155.035169] iwlwifi :00:14.3: 0x0100 | data2 Mar 8 08:57:43 ironwarrior kernel: [ 155.035170] iwlwifi :00:14.3: 0x | data3 Mar 8 08:57:43 ironwarrior kernel: [ 155.035171] iwlwifi :00:14.3: 0x65C10249 | beacon time Mar 8 08:57:43 ironwarrior kernel: [ 155.035171] iwlwifi :00:14.3: 0xF0EBFDC9 | tsf low Mar 8 08:57:43 ironwarrior kernel: [ 155.035172] iwlwifi :00:14.3: 0x0076 | tsf hi Mar 8 08:57:43 ironwarrior kernel: [ 155.035173] iwlwifi :00:14.3: 0x | time gp1 Mar 8 08:57:43 ironwarrior kernel: [ 155.035173] iwlwifi :00:14.3: 0x08F462FA | time gp2 Mar 8 08:57:43 ironwarrior kernel: [ 155.035174] iwlwifi :00:14.3: 0x0001 | uCode revision type Mar 8 08:57:43 ironwarrior kernel: [ 155.035175] iwlwifi :00:14.3: 0x0048 | uCode version major Mar 8 08:57:43 ironwarrior kernel: [ 155.035176] iwlwifi :00:14.3: 0xDAA05125 | uCode version minor Mar 8 08:57:43 ironwarrior
[Kernel-packages] [Bug 2009676] Re: Add support for Raptor Lake S CPUs
Hello Bin, or anyone else affected, Accepted thermald into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/thermald/2.4.9-1ubuntu0.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: thermald (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: thermald (Ubuntu) Status: New => Fix Released ** Changed in: thermald (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/2009676 Title: Add support for Raptor Lake S CPUs Status in OEM Priority Project: New Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Bug description: [Impact] * Support thermald on Raptor Lake S CPU. [Test Plan] * Use a machine with a Raptor Lake S cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake S in thermald, which won't impact other hardware. [Other Info] https://github.com/intel/thermal_daemon/commit/e03493dc1e972374c1686492655250f8f48a15ba To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009676] Re: Add support for Raptor Lake S CPUs
I don't think we have kernel support for RPL in focal though? -- 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/2009676 Title: Add support for Raptor Lake S CPUs Status in OEM Priority Project: New Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Bug description: [Impact] * Support thermald on Raptor Lake S CPU. [Test Plan] * Use a machine with a Raptor Lake S cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake S in thermald, which won't impact other hardware. [Other Info] https://github.com/intel/thermal_daemon/commit/e03493dc1e972374c1686492655250f8f48a15ba To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009355] Re: linux-libc-dev is no longer multi-arch safe
** Tags added: update-excuse -- 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/2009355 Title: linux-libc-dev is no longer multi-arch safe Status in linux package in Ubuntu: Confirmed Bug description: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/i386/b/binutils/20230305_112702_eba45@/log.gz dpkg: error processing archive /tmp/apt-dpkg-install-9IkDRS/098-linux-libc-dev_6.1.0-16.16_i386.deb (--unpack): trying to overwrite shared '/arch/x86/include/generated/asm/.syscalls_32.h.cmd', which is different from other instances of package linux-libc-dev:i386 I'm not sure why linux-libc-dev_6.1.0-16.16 has files in /arch /install /scripts. But these files are different on different arch (or different build, since it embeds build path) ==> amd64/arch/x86/include/generated/asm/.syscalls_32.h.cmd <== cmd_arch/x86/include/generated/asm/syscalls_32.h := sh /build/linux-1t584m/linux-6.1.0/scripts/syscalltbl.sh --abis i386 /build/linux-1t584m/linux-6.1.0/arch/x86/entry/syscalls/syscall_32.tbl arch/x86/include/generated/asm/syscalls_32.h ==> i386/arch/x86/include/generated/asm/.syscalls_32.h.cmd <== cmd_arch/x86/include/generated/asm/syscalls_32.h := sh /build/linux-f194dh/linux-6.1.0/scripts/syscalltbl.sh --abis i386 /build/linux-f194dh/linux-6.1.0/arch/x86/entry/syscalls/syscall_32.tbl arch/x86/include/generated/asm/syscalls_32.h To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009355/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
I have sent a patch to fix the upstream error (https://lkml.org/lkml/2023/3/8/107), which is intended to resolve the issue of a massive increase in ACCESS operations. I have also prepared a test kernel that includes this patch and would appreciate it if you could use it for testing. To install the test kernel, please follow these steps: 1. Run the following command: sudo add-apt-repository ppa:chengendu/jammy-nfs-patch 2. Update the packages: sudo apt update 3. Install the kernel packages: sudo apt install linux-headers-5.15.0-67-generic linux-image-unsigned-5.15.0-67-generic linux-modules-5.15.0-67-generic linux-modules-extra-5.15.0-67-generic 4. Reboot your system. 5. To check the installed kernel version, run the command 'uname -rv', which should output '5.15.0-67-generic #74+test20230308b0h1a13a615ee32-Ubuntu SMP Wed Mar 8 09:24:49 UT'. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firm
[Kernel-packages] [Bug 2002601] Re: Wireless: Enable RTL8852BE wifi driver
@Koba I’m using Jammy. At least that’s what shows when I’m running >sudo apt-get update and >sudo apt-get install upgrade. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2002601 Title: Wireless: Enable RTL8852BE wifi driver Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Justification] Enable Realtek RLT8852BE WIFI. [Test] 1. put rtw8852b_fw.bin in /lib/firmware/rtw89/ 2. boot-up with kernel enabled RTL8852be. 3. Connect to WIFI-AP and test with ping. * ping -I wlp2s0 8.8.8.8 ~~~ PING 8.8.8.8 (8.8.8.8) from 10.102.137.55 wlp2s0: 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=5.86 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=6.21 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=18.9 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=6.09 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=6.13 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=5.77 ms ~~~ * Connected to AP ~~~ u@ubuntu:~$ nmcli dev DEVICE TYPE STATE CONNECTION enp3s0 ethernet connected Wired connection 1 wlp2s0 wifi connected Canonical p2p-dev-wlp2s0 wifi-p2p disconnected -- lo loopback unmanaged -- ~~~ * lsmod | grep 8852 ~~~ lsmod | grep 8852 rtw89_8852be 16384 0 rtw89_8852b 368640 1 rtw89_8852be rtw89_pci 61440 1 rtw89_8852be rtw89_core 442368 2 rtw89_8852b,rtw89_pci cfg80211 1081344 3 rtw89_8852b,rtw89_core,mac80211 ~~~ 4. cbd's built result, Lunar, ~~~ remote: Resolving deltas: 100% (391/391), completed with 118 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'u_lMstrNxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-lunar-0e58018b43c1-ioeM remote: * 96/480 cores busy (1/5 hosts), 0 builds queued remote: 2023-01-12 03:16:35 kobako-lunar-0e58018b43c1-ioeM/amd64/BUILD-OK remote: 2023-01-12 03:17:47 kobako-lunar-0e58018b43c1-ioeM/arm64/BUILD-OK remote: 2023-01-12 03:11:36 kobako-lunar-0e58018b43c1-ioeM/armhf/BUILD-OK remote: 2023-01-12 03:16:30 kobako-lunar-0e58018b43c1-ioeM/ppc64el/BUILD-OK remote: 2023-01-12 03:10:24 kobako-lunar-0e58018b43c1-ioeM/s390x/BUILD-OK remote: To cbd:lunar.git ~~~ OEM-6.1, remote: Resolving deltas: 100% (399/399), completed with 121 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'oem-6.1-next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-c1002f30ccc3-m65z remote: * 0/192 cores busy (0/2 hosts), 0 builds queued remote: 2023-01-12 05:25:23 kobako-jammy-c1002f30ccc3-m65z/amd64/BUILD-OK remote: To cbd:jammy.git [Where problems could occur] Medium, a new driver so the current driver may have some edge cases didn't consider. [Misc] * For generic Jammy, need more patches to enable RTL8852be so only SRU for OEM-6.1. * firmware, dae5d4603b07) rtw89: 8852b: update fw to v0.27.32.1 has landed on Lunar, so only SRU for Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
Hello ChengEn, Du , Thank you for the quick response and fix . We have quickly tried the test kernel ( 5.15.0-67-generic #74+test20230307b2h2cbb6062f8eb-Ubuntu ) on a test webserver (ubuntu 22.04.2 lts ) with an impacted configuration with nfs and db. The test kernel seems for us to fix the problem, as we have returned to a normal behavior as the previous kernel (5.15.0-60-generic). Best regards, -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporatio
[Kernel-packages] [Bug 2009676] Re: Add support for Raptor Lake S CPUs
I believe it's useful to have RPL focal support in thermald if users use newer HWE kernels. Plus the change is basically adding in some CPU id's so it's a small delta for useful potential support. -- 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/2009676 Title: Add support for Raptor Lake S CPUs Status in OEM Priority Project: New Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Bug description: [Impact] * Support thermald on Raptor Lake S CPU. [Test Plan] * Use a machine with a Raptor Lake S cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake S in thermald, which won't impact other hardware. [Other Info] https://github.com/intel/thermal_daemon/commit/e03493dc1e972374c1686492655250f8f48a15ba To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009676] Re: Add support for Raptor Lake S CPUs
@Colin, @Timo, i could help to verify this on RPL-S. -- 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/2009676 Title: Add support for Raptor Lake S CPUs Status in OEM Priority Project: New Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Bug description: [Impact] * Support thermald on Raptor Lake S CPU. [Test Plan] * Use a machine with a Raptor Lake S cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake S in thermald, which won't impact other hardware. [Other Info] https://github.com/intel/thermal_daemon/commit/e03493dc1e972374c1686492655250f8f48a15ba To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008833] Re: mlxbf-gige: Fix intermittent no ip issue
** Changed in: linux-bluefield (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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2008833 Title: mlxbf-gige: Fix intermittent no ip issue Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Although the link is up, and the PHY interrupt is cleared, there is no ip assigned. Nothing is being transmitted, and nothing is received. The RX error count keeps on increasing (check ifconfig oob_net0). After several minutes, the RX error count stagnates and the oob finally gets an ip and is pingable. [Fix] The issue is in the mlxbf_gige_rx_init function. As soon as the RX DMA is enabled, the RX CI reaches the max 128, it becomes equal to RX PI. And RX CI doesn't decrease since the code hasn't ran phy_start yet. The solution is to move the rx init after phy_start. This fix applies to both 5.4 and 5.15. [Test Case] * Check if the gige driver is loaded * Check that the oob_net0 interface is up and pingable from an external host * Do at ~1000 resets and powercycles and check the oon_net0 interface again [Regression Potential] * No known regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2008833/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007875] Re: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently
To the best of my knowledge, I followed the steps you outlined cloning both repos and installing/cp'ing the files. I've double checked the firmware files exist. When I run "update-grub" just to check, I see Found linux image: /boot/vmlinuz-6.0.0-1012-oem Found initrd image: /boot/initrd.img-6.0.0-1012-oem Found linux image: /boot/vmlinuz-5.19.0-35-generic Found initrd image: /boot/initrd.img-5.19.0-35-generic Found linux image: /boot/vmlinuz-5.19.0-32-generic Found initrd image: /boot/initrd.img-5.19.0-32-generic Found linux image: /boot/vmlinuz-5.15.0-67-generic Found initrd image: /boot/initrd.img-5.15.0-67-generic When I boot, I pick 5.19.0-32-generic. That is what I should pick, right? I'm not familiar with how drivers are selected for each kernel nor how exactly the backport-iwlwifi make and make install actually work, but it looked successful. Before running the commands, it appeared that kernel 5.19.0-32-generic would have the wifi error once a day or so. After I ran the commands and rebooted, I had no internet at all. That also made it difficult for me to look up any commands necessary to provide more information. I can try other things if that is desired. This is my primary computer and I need to use kernel 5.15 to get work done, so it may take me a day or so to respond. This is the only device that has failed. My Android phone and other family Ubuntu computers do not have a problem with the same wifi router. I wonder if it only fails when it happens to use the 6Gz frequency? Is it expected to see that when running iw dev wlp0s20f3 info? Does center1: 5775 MHz mean what a lay person would call "5Ghz" and the MHz would be above 6000MHz if it was using "6Gz"? Once the wifi crashes, I don't know what frequency it was recently using. Another perhaps less common thing about the Nest Wifi Pro is that it's a Mesh network with two access points. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2007875 Title: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently Status in linux-firmware package in Ubuntu: Fix Released Status in oem-somerville-tentacool-meta package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Committed Status in oem-somerville-tentacool-meta source package in Jammy: New Status in linux-firmware source package in Kinetic: Fix Released Status in oem-somerville-tentacool-meta source package in Kinetic: Invalid Status in linux-firmware source package in Lunar: Fix Released Status in oem-somerville-tentacool-meta source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] backport-iwlwifi-dkms/kinetic is being built into hwe-5.19 kernel, and -73 firmware are supported bug missing. On one user reported issue, this fixes WiFi stability on 5G band. [Fix] New upstreamed firmware revision fixes this issue. [Test Case] 1. Boot hwe-5.19 kernel 2. iwlwifi-so-a0-gf-a0-73.ucode firmware should be loaded 3. Browse the web, usually takes between 1 and 5 minutes 4. Networking will cut out [Where problems could occur] This affects only users need both backport-iwlwifi-dkms and hwe-5.19 kernel on WiFi stability. [Other Info] While Kinetic and above have them all, only Jammy is nominated. == original bug report == I'm using the stock Dell Ubuntu 22.04 image on my XPS 13 Plus (9320). Recently I received some kernel updates, the 5.19 kernel used in 22.10 and a 6.0 oem kernel. Both updates break wifi. It seems to only do so on newer 5.7 GHz access points. 1. Boot latest 6.0 oem kernel 2. Browse the web, usually takes between 1 and 5 minutes. 3. Networking will cut out. Disabling networking and starting again will fix it until it happens again in a few minutes. This will repeat indefinitely, essentially making wireless useless. The attached dmesg log reliably shows up when it fails, showing iwlwifi failing and a (network?) hardware reset request. It witnessed this happen months ago on 22.10, which led me to using the Dell stock 22.04 image. But it seems even the newer OEM kernel is affected. A workaround is to select the older 5.15 kernel in grub. I find on this laptop, one must hit escape precisely 1 second after seeing the Dell logo on boot. Alternatively one could edit /etc/grub/default and set a longer timeout. Let me know if this bug report would be better to go to Dell as a support request instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2007875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002601] Re: Wireless: Enable RTL8852BE wifi driver
@Devon, would you like to use oem kernel(6.1-oem)? ~~~ #sudo apt install linux-oem-22.-4c ~~~ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2002601 Title: Wireless: Enable RTL8852BE wifi driver Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Justification] Enable Realtek RLT8852BE WIFI. [Test] 1. put rtw8852b_fw.bin in /lib/firmware/rtw89/ 2. boot-up with kernel enabled RTL8852be. 3. Connect to WIFI-AP and test with ping. * ping -I wlp2s0 8.8.8.8 ~~~ PING 8.8.8.8 (8.8.8.8) from 10.102.137.55 wlp2s0: 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=5.86 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=6.21 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=18.9 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=6.09 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=6.13 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=5.77 ms ~~~ * Connected to AP ~~~ u@ubuntu:~$ nmcli dev DEVICE TYPE STATE CONNECTION enp3s0 ethernet connected Wired connection 1 wlp2s0 wifi connected Canonical p2p-dev-wlp2s0 wifi-p2p disconnected -- lo loopback unmanaged -- ~~~ * lsmod | grep 8852 ~~~ lsmod | grep 8852 rtw89_8852be 16384 0 rtw89_8852b 368640 1 rtw89_8852be rtw89_pci 61440 1 rtw89_8852be rtw89_core 442368 2 rtw89_8852b,rtw89_pci cfg80211 1081344 3 rtw89_8852b,rtw89_core,mac80211 ~~~ 4. cbd's built result, Lunar, ~~~ remote: Resolving deltas: 100% (391/391), completed with 118 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'u_lMstrNxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-lunar-0e58018b43c1-ioeM remote: * 96/480 cores busy (1/5 hosts), 0 builds queued remote: 2023-01-12 03:16:35 kobako-lunar-0e58018b43c1-ioeM/amd64/BUILD-OK remote: 2023-01-12 03:17:47 kobako-lunar-0e58018b43c1-ioeM/arm64/BUILD-OK remote: 2023-01-12 03:11:36 kobako-lunar-0e58018b43c1-ioeM/armhf/BUILD-OK remote: 2023-01-12 03:16:30 kobako-lunar-0e58018b43c1-ioeM/ppc64el/BUILD-OK remote: 2023-01-12 03:10:24 kobako-lunar-0e58018b43c1-ioeM/s390x/BUILD-OK remote: To cbd:lunar.git ~~~ OEM-6.1, remote: Resolving deltas: 100% (399/399), completed with 121 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'oem-6.1-next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-c1002f30ccc3-m65z remote: * 0/192 cores busy (0/2 hosts), 0 builds queued remote: 2023-01-12 05:25:23 kobako-jammy-c1002f30ccc3-m65z/amd64/BUILD-OK remote: To cbd:jammy.git [Where problems could occur] Medium, a new driver so the current driver may have some edge cases didn't consider. [Misc] * For generic Jammy, need more patches to enable RTL8852be so only SRU for OEM-6.1. * firmware, dae5d4603b07) rtw89: 8852b: update fw to v0.27.32.1 has landed on Lunar, so only SRU for Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 (regression from -32)
@Dave, appreciate, I would like to check from first patch in amd driver first. thanks https://drive.google.com/drive/folders/1bWeHxyBYhukZLic8CmRowDfr0zSjGs-N?usp=share_link -- 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 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: In Progress Bug 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 2002601] Re: Wireless: Enable RTL8852BE wifi driver
@Koba, pardon what’s probably are silly questions, but does 6.1-oem have the RTL8852BE driver included in the kernel? Also will linux-oem-22.-4c work in Mint? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2002601 Title: Wireless: Enable RTL8852BE wifi driver Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Justification] Enable Realtek RLT8852BE WIFI. [Test] 1. put rtw8852b_fw.bin in /lib/firmware/rtw89/ 2. boot-up with kernel enabled RTL8852be. 3. Connect to WIFI-AP and test with ping. * ping -I wlp2s0 8.8.8.8 ~~~ PING 8.8.8.8 (8.8.8.8) from 10.102.137.55 wlp2s0: 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=5.86 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=6.21 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=18.9 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=6.09 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=6.13 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=5.77 ms ~~~ * Connected to AP ~~~ u@ubuntu:~$ nmcli dev DEVICE TYPE STATE CONNECTION enp3s0 ethernet connected Wired connection 1 wlp2s0 wifi connected Canonical p2p-dev-wlp2s0 wifi-p2p disconnected -- lo loopback unmanaged -- ~~~ * lsmod | grep 8852 ~~~ lsmod | grep 8852 rtw89_8852be 16384 0 rtw89_8852b 368640 1 rtw89_8852be rtw89_pci 61440 1 rtw89_8852be rtw89_core 442368 2 rtw89_8852b,rtw89_pci cfg80211 1081344 3 rtw89_8852b,rtw89_core,mac80211 ~~~ 4. cbd's built result, Lunar, ~~~ remote: Resolving deltas: 100% (391/391), completed with 118 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'u_lMstrNxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-lunar-0e58018b43c1-ioeM remote: * 96/480 cores busy (1/5 hosts), 0 builds queued remote: 2023-01-12 03:16:35 kobako-lunar-0e58018b43c1-ioeM/amd64/BUILD-OK remote: 2023-01-12 03:17:47 kobako-lunar-0e58018b43c1-ioeM/arm64/BUILD-OK remote: 2023-01-12 03:11:36 kobako-lunar-0e58018b43c1-ioeM/armhf/BUILD-OK remote: 2023-01-12 03:16:30 kobako-lunar-0e58018b43c1-ioeM/ppc64el/BUILD-OK remote: 2023-01-12 03:10:24 kobako-lunar-0e58018b43c1-ioeM/s390x/BUILD-OK remote: To cbd:lunar.git ~~~ OEM-6.1, remote: Resolving deltas: 100% (399/399), completed with 121 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'oem-6.1-next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-c1002f30ccc3-m65z remote: * 0/192 cores busy (0/2 hosts), 0 builds queued remote: 2023-01-12 05:25:23 kobako-jammy-c1002f30ccc3-m65z/amd64/BUILD-OK remote: To cbd:jammy.git [Where problems could occur] Medium, a new driver so the current driver may have some edge cases didn't consider. [Misc] * For generic Jammy, need more patches to enable RTL8852be so only SRU for OEM-6.1. * firmware, dae5d4603b07) rtw89: 8852b: update fw to v0.27.32.1 has landed on Lunar, so only SRU for Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002601] Re: Wireless: Enable RTL8852BE wifi driver
rtl8852be has been enabled in 6.1-oem. Could you find the linux-oem-22.04c in Mint? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2002601 Title: Wireless: Enable RTL8852BE wifi driver Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Justification] Enable Realtek RLT8852BE WIFI. [Test] 1. put rtw8852b_fw.bin in /lib/firmware/rtw89/ 2. boot-up with kernel enabled RTL8852be. 3. Connect to WIFI-AP and test with ping. * ping -I wlp2s0 8.8.8.8 ~~~ PING 8.8.8.8 (8.8.8.8) from 10.102.137.55 wlp2s0: 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=5.86 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=6.21 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=18.9 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=6.09 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=6.13 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=5.77 ms ~~~ * Connected to AP ~~~ u@ubuntu:~$ nmcli dev DEVICE TYPE STATE CONNECTION enp3s0 ethernet connected Wired connection 1 wlp2s0 wifi connected Canonical p2p-dev-wlp2s0 wifi-p2p disconnected -- lo loopback unmanaged -- ~~~ * lsmod | grep 8852 ~~~ lsmod | grep 8852 rtw89_8852be 16384 0 rtw89_8852b 368640 1 rtw89_8852be rtw89_pci 61440 1 rtw89_8852be rtw89_core 442368 2 rtw89_8852b,rtw89_pci cfg80211 1081344 3 rtw89_8852b,rtw89_core,mac80211 ~~~ 4. cbd's built result, Lunar, ~~~ remote: Resolving deltas: 100% (391/391), completed with 118 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'u_lMstrNxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-lunar-0e58018b43c1-ioeM remote: * 96/480 cores busy (1/5 hosts), 0 builds queued remote: 2023-01-12 03:16:35 kobako-lunar-0e58018b43c1-ioeM/amd64/BUILD-OK remote: 2023-01-12 03:17:47 kobako-lunar-0e58018b43c1-ioeM/arm64/BUILD-OK remote: 2023-01-12 03:11:36 kobako-lunar-0e58018b43c1-ioeM/armhf/BUILD-OK remote: 2023-01-12 03:16:30 kobako-lunar-0e58018b43c1-ioeM/ppc64el/BUILD-OK remote: 2023-01-12 03:10:24 kobako-lunar-0e58018b43c1-ioeM/s390x/BUILD-OK remote: To cbd:lunar.git ~~~ OEM-6.1, remote: Resolving deltas: 100% (399/399), completed with 121 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'oem-6.1-next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-c1002f30ccc3-m65z remote: * 0/192 cores busy (0/2 hosts), 0 builds queued remote: 2023-01-12 05:25:23 kobako-jammy-c1002f30ccc3-m65z/amd64/BUILD-OK remote: To cbd:jammy.git [Where problems could occur] Medium, a new driver so the current driver may have some edge cases didn't consider. [Misc] * For generic Jammy, need more patches to enable RTL8852be so only SRU for OEM-6.1. * firmware, dae5d4603b07) rtw89: 8852b: update fw to v0.27.32.1 has landed on Lunar, so only SRU for Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002601] Re: Wireless: Enable RTL8852BE wifi driver
@Koba I was able to find the oem-22.-4c using the sudo command you provided in Mint. It installed successfully and when I restarted the wifi card still works and I’m showing kernel 6.1.0-1007-oem. Crossing my fingers the driver is retained with the next upgrade. Thanks so much for your help, it’s greatly appreciated. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2002601 Title: Wireless: Enable RTL8852BE wifi driver Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Justification] Enable Realtek RLT8852BE WIFI. [Test] 1. put rtw8852b_fw.bin in /lib/firmware/rtw89/ 2. boot-up with kernel enabled RTL8852be. 3. Connect to WIFI-AP and test with ping. * ping -I wlp2s0 8.8.8.8 ~~~ PING 8.8.8.8 (8.8.8.8) from 10.102.137.55 wlp2s0: 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=5.86 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=6.21 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=18.9 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=6.09 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=6.13 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=5.77 ms ~~~ * Connected to AP ~~~ u@ubuntu:~$ nmcli dev DEVICE TYPE STATE CONNECTION enp3s0 ethernet connected Wired connection 1 wlp2s0 wifi connected Canonical p2p-dev-wlp2s0 wifi-p2p disconnected -- lo loopback unmanaged -- ~~~ * lsmod | grep 8852 ~~~ lsmod | grep 8852 rtw89_8852be 16384 0 rtw89_8852b 368640 1 rtw89_8852be rtw89_pci 61440 1 rtw89_8852be rtw89_core 442368 2 rtw89_8852b,rtw89_pci cfg80211 1081344 3 rtw89_8852b,rtw89_core,mac80211 ~~~ 4. cbd's built result, Lunar, ~~~ remote: Resolving deltas: 100% (391/391), completed with 118 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'u_lMstrNxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-lunar-0e58018b43c1-ioeM remote: * 96/480 cores busy (1/5 hosts), 0 builds queued remote: 2023-01-12 03:16:35 kobako-lunar-0e58018b43c1-ioeM/amd64/BUILD-OK remote: 2023-01-12 03:17:47 kobako-lunar-0e58018b43c1-ioeM/arm64/BUILD-OK remote: 2023-01-12 03:11:36 kobako-lunar-0e58018b43c1-ioeM/armhf/BUILD-OK remote: 2023-01-12 03:16:30 kobako-lunar-0e58018b43c1-ioeM/ppc64el/BUILD-OK remote: 2023-01-12 03:10:24 kobako-lunar-0e58018b43c1-ioeM/s390x/BUILD-OK remote: To cbd:lunar.git ~~~ OEM-6.1, remote: Resolving deltas: 100% (399/399), completed with 121 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'oem-6.1-next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-c1002f30ccc3-m65z remote: * 0/192 cores busy (0/2 hosts), 0 builds queued remote: 2023-01-12 05:25:23 kobako-jammy-c1002f30ccc3-m65z/amd64/BUILD-OK remote: To cbd:jammy.git [Where problems could occur] Medium, a new driver so the current driver may have some edge cases didn't consider. [Misc] * For generic Jammy, need more patches to enable RTL8852be so only SRU for OEM-6.1. * firmware, dae5d4603b07) rtw89: 8852b: update fw to v0.27.32.1 has landed on Lunar, so only SRU for Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967593] Re: kernel modules going missing after reboot
** Changed in: cloud-initramfs-tools (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/1967593 Title: kernel modules going missing after reboot Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. EDIT2: it turns out this is caused by the cloud-initramfs-copymods package mounting over modules locations. Removed it and reinstalled kernel modules package (extras didnt seem necessary, but probably prudent too). This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Dr
[Kernel-packages] [Bug 2009676] Re: Add support for Raptor Lake S CPUs
** 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 thermald in Ubuntu. https://bugs.launchpad.net/bugs/2009676 Title: Add support for Raptor Lake S CPUs Status in OEM Priority Project: New Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Bug description: [Impact] * Support thermald on Raptor Lake S CPU. [Test Plan] * Use a machine with a Raptor Lake S cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake S in thermald, which won't impact other hardware. [Other Info] https://github.com/intel/thermal_daemon/commit/e03493dc1e972374c1686492655250f8f48a15ba To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009676] Re: Add support for Raptor Lake S CPUs
@koba, can you test the focal version too? -- 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/2009676 Title: Add support for Raptor Lake S CPUs Status in OEM Priority Project: New Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Bug description: [Impact] * Support thermald on Raptor Lake S CPU. [Test Plan] * Use a machine with a Raptor Lake S cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake S in thermald, which won't impact other hardware. [Other Info] https://github.com/intel/thermal_daemon/commit/e03493dc1e972374c1686492655250f8f48a15ba To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009594] Re: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)
This does indeed appear to be a serious issue, but it is unfortunately not a charm issue. It appears to me to be an issue with the mlx5 driver in the kernel which is visible in this specific environment for yet to be uncovered reasons. ** Changed in: charm-ovn-chassis 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/2009594 Title: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE) Status in charm-ovn-chassis: Invalid Status in linux package in Ubuntu: Confirmed Bug description: This is seen on particular with : * Charmed Openstack with Jammy Yoga * 5.19.0-35-generic (linux-generic-hwe-22.04/jammy-updates) * Mellanox Connectx-6 card with mlx5_core module being used * SR-IOV is being used with VF-LAG for the use of OVN hardware offloading The servers enter into very high load (around 75~100) quickly during the boot with all process relying on network communication with the Mellanox network card being stuck or extremely slow. Kernel logs are being displayed about kworkers being blocked for more than 120 seconds The number of SR-IOV devices configured both from the firmware and the kernel seems to have a serious correlation with the likeliness of this bug to occur. Having enabled more VF seems to hugely increase the risk for this bug to arise. This does not happen systematically at every boot, but with 32 VFs on each PF, it occurs about 40% of the time. To recover the server, a cold reboot is required. Look at a quick sample of the trace, this seems to involve directly the mlx5 driver within the kernel : Mar 07 05:24:56 nova-1 kernel: INFO: task kworker/0:1:19 blocked for more than 120 seconds. Mar 07 05:24:56 nova-1 kernel: Tainted: P OE 5.19.0-35-generic #36~22.04.1-Ubuntu Mar 07 05:24:56 nova-1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 07 05:24:56 nova-1 kernel: task:kworker/0:1 state:D stack:0 pid: 19 ppid: 2 flags:0x4000 Mar 07 05:24:56 nova-1 kernel: Workqueue: events work_for_cpu_fn Mar 07 05:24:56 nova-1 kernel: Call Trace: Mar 07 05:24:56 nova-1 kernel: Mar 07 05:24:56 nova-1 kernel: __schedule+0x257/0x5d0 Mar 07 05:24:56 nova-1 kernel: schedule+0x68/0x110 Mar 07 05:24:56 nova-1 kernel: schedule_preempt_disabled+0x15/0x30 Mar 07 05:24:56 nova-1 kernel: __mutex_lock.constprop.0+0x4f1/0x750 Mar 07 05:24:56 nova-1 kernel: __mutex_lock_slowpath+0x13/0x20 Mar 07 05:24:56 nova-1 kernel: mutex_lock+0x3e/0x50 Mar 07 05:24:56 nova-1 kernel: mlx5_register_device+0x1c/0xb0 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: mlx5_init_one+0xe4/0x110 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: probe_one+0xcb/0x120 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: local_pci_probe+0x4b/0x90 Mar 07 05:24:56 nova-1 kernel: work_for_cpu_fn+0x1a/0x30 Mar 07 05:24:56 nova-1 kernel: process_one_work+0x21f/0x400 Mar 07 05:24:56 nova-1 kernel: worker_thread+0x200/0x3f0 Mar 07 05:24:56 nova-1 kernel: ? rescuer_thread+0x3a0/0x3a0 Mar 07 05:24:56 nova-1 kernel: kthread+0xee/0x120 Mar 07 05:24:56 nova-1 kernel: ? kthread_complete_and_exit+0x20/0x20 Mar 07 05:24:56 nova-1 kernel: ret_from_fork+0x22/0x30 Mar 07 05:24:56 nova-1 kernel: To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ovn-chassis/+bug/2009594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007487] Re: package linux-headers-5.19.0-32-generic 5.19.0-32.33~22.04.1 failed to install/upgrade: installed linux-headers-5.19.0-32-generic package post-installation script s
** 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-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007487 Title: package linux-headers-5.19.0-32-generic 5.19.0-32.33~22.04.1 failed to install/upgrade: installed linux-headers-5.19.0-32-generic package post-installation script subprocess returned error exit status 1 Status in linux-hwe-5.19 package in Ubuntu: New Bug description: not sure what this is about but it's been happening for weeks now. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-headers-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 16 01:03:16 2023 ErrorMessage: installed linux-headers-5.19.0-32-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-10-07 (131 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: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-hwe-5.19 Title: package linux-headers-5.19.0-32-generic 5.19.0-32.33~22.04.1 failed to install/upgrade: installed linux-headers-5.19.0-32-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007487/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007487] Re: package linux-headers-5.19.0-32-generic 5.19.0-32.33~22.04.1 failed to install/upgrade: installed linux-headers-5.19.0-32-generic package post-installation script s
** Tags removed: need-duplicate-check -- 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/2007487 Title: package linux-headers-5.19.0-32-generic 5.19.0-32.33~22.04.1 failed to install/upgrade: installed linux-headers-5.19.0-32-generic package post-installation script subprocess returned error exit status 1 Status in linux-hwe-5.19 package in Ubuntu: New Bug description: not sure what this is about but it's been happening for weeks now. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-headers-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 16 01:03:16 2023 ErrorMessage: installed linux-headers-5.19.0-32-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-10-07 (131 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: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-hwe-5.19 Title: package linux-headers-5.19.0-32-generic 5.19.0-32.33~22.04.1 failed to install/upgrade: installed linux-headers-5.19.0-32-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007487/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006744] Re: libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict
This bug was fixed in the package mesa - 22.3.6-1ubuntu2 --- mesa (22.3.6-1ubuntu2) lunar; urgency=medium * control: Add replaces/breaks to -dri for amber. (LP: #2006744) -- Timo Aaltonen Tue, 07 Mar 2023 10:24:33 +0200 ** Changed in: mesa (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to mesa-amber in Ubuntu. https://bugs.launchpad.net/bugs/2006744 Title: libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict Status in mesa package in Ubuntu: Fix Released Status in mesa-amber package in Ubuntu: Fix Released Bug description: I enabled lunar-proposed today (with APT::Default-Release "lunar- proposed";) and got the error below during update: Preparing to unpack .../39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ... Unpacking libgl1-mesa-dri:amd64 (22.3.4-1ubuntu1) over (22.2.5-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-AkyzpG/39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Then it will be broken: root@deleteme-lunar:~# apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libgl1-mesa-dri : Depends: libglapi-mesa (= 22.2.5-0ubuntu1) but 22.3.4-1ubuntu1 is installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). root@deleteme-lunar:~# apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: libicu71 libpython3.10-minimal libpython3.10-stdlib python3.10 python3.10-minimal Use 'apt autoremove' to remove them. The following additional packages will be installed: libgl1-mesa-dri The following packages will be upgraded: libgl1-mesa-dri 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 62 not fully installed or removed. Need to get 0 B/7806 kB of archives. After this operation, 809 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 81205 files and directories currently installed.) Preparing to unpack .../libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ... Unpacking libgl1-mesa-dri:amd64 (22.3.4-1ubuntu1) over (22.2.5-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Errors were encountered while processing: /var/cache/apt/archives/libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) How to reproduce: 1. Spin up a Lunar VM 2. Enable -proposed 3. Install libgl1-mesa-dri and libgl1-amber-dri 4. Add APT::Default-Release "lunar-proposed"; to /etc/apt/apt.conf.d/somefile 5. Try to upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2006744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998244] Re: kselftest net/fib_nexthop_nongw.sh fails
This bug was fixed in the package linux-kvm - 5.15.0-1029.34 --- linux-kvm (5.15.0-1029.34) jammy; urgency=medium * jammy/linux-kvm: 5.15.0-1029.34 -proposed tracker (LP: #2004333) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.01.30) * Jammy update: v5.15.81 upstream stable release (LP: #2003130) - [Config] kvm: updateconfigs for CC_HAS_ASM_GOTO_TIED_OUTPUT - [Config] kvm: updateconfigs for INET_TABLE_PERTURB_ORDER * kselftest net/fib_nexthop_nongw.sh fails (LP: #1998244) - [Config] kvm: Add support for dummy net driver [ Ubuntu: 5.15.0-66.73 ] * jammy/linux: 5.15.0-66.73 -proposed tracker (LP: #2004636) * CVE-2023-0461 - SAUCE: Fix inet_csk_listen_start after CVE-2023-0461 [ Ubuntu: 5.15.0-65.72 ] * jammy/linux: 5.15.0-65.72 -proposed tracker (LP: #2004344) * Packaging resync (LP: #1786013) - [Packaging] update variants - debian/dkms-versions -- update from kernel-versions (main/2023.01.30) * NFS: client permission error after adding user to permissible group (LP: #2003053) - NFS: Clear the file access cache upon login - NFS: Judge the file access cache's timestamp in rcu path - NFS: Fix up a sparse warning * Fix W6400 hang after resume of S3 stress (LP: #2000299) - drm/amd/display: Manually adjust strobe for DCN303 * Rear Audio port sometimes has no audio output after reboot(Cirrus Logic) (LP: #1998905) - ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock. * CVE-2022-20369 - NFSD: fix use-after-free in __nfs42_ssc_open() * CVE-2023-0461 - net/ulp: prevent ULP without clone op from entering the LISTEN status - net/ulp: use consistent error code when blocking ULP * CVE-2023-0179 - netfilter: nft_payload: incorrect arithmetics when fetching VLAN header bits * Jammy update: v5.15.85 upstream stable release (LP: #2003139) - udf: Discard preallocation before extending file with a hole - udf: Fix preallocation discarding at indirect extent boundary - udf: Do not bother looking for prealloc extents if i_lenExtents matches i_size - udf: Fix extending file within last block - usb: gadget: uvc: Prevent buffer overflow in setup handler - USB: serial: option: add Quectel EM05-G modem - USB: serial: cp210x: add Kamstrup RF sniffer PIDs - USB: serial: f81232: fix division by zero on line-speed change - USB: serial: f81534: fix division by zero on line-speed change - xhci: Apply XHCI_RESET_TO_DEFAULT quirk to ADL-N - igb: Initialize mailbox message for VF reset - usb: dwc3: pci: Update PCIe device ID for USB3 controller on CPU sub-system for Raptor Lake - HID: uclogic: Add HID_QUIRK_HIDINPUT_FORCE quirk - selftests: net: Use "grep -E" instead of "egrep" - net: loopback: use NET_NAME_PREDICTABLE for name_assign_type - Linux 5.15.85 * Jammy update: v5.15.84 upstream stable release (LP: #2003137) - x86/vdso: Conditionally export __vdso_sgx_enter_enclave() - vfs: fix copy_file_range() averts filesystem freeze protection - ASoC: fsl_micfil: explicitly clear software reset bit - ASoC: fsl_micfil: explicitly clear CHnF flags - ASoC: ops: Check bounds for second channel in snd_soc_put_volsw_sx() - libbpf: Use page size as max_entries when probing ring buffer map - pinctrl: meditatek: Startup with the IRQs disabled - can: sja1000: fix size of OCR_MODE_MASK define - can: mcba_usb: Fix termination command argument - net: fec: don't reset irq coalesce settings to defaults on "ip link up" - ASoC: cs42l51: Correct PGA Volume minimum value - perf: Fix perf_pending_task() UaF - nvme-pci: clear the prp2 field when not used - ASoC: ops: Correct bounds check for second channel on SX controls - net: fec: properly guard irq coalesce setup - Linux 5.15.84 * Jammy update: v5.15.83 upstream stable release (LP: #2003134) - clk: generalize devm_clk_get() a bit - clk: Provide new devm_clk helpers for prepared and enabled clocks - mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse() - arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4 series - arm: dts: rockchip: fix node name for hym8563 rtc - arm: dts: rockchip: remove clock-frequency from rtc - ARM: dts: rockchip: fix ir-receiver node names - arm64: dts: rockchip: fix ir-receiver node names - ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name - fs: use acquire ordering in __fget_light() - ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels - ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation - ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register - spi: mediatek: Fix DEVAPC Violation at KO Remove - ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188 - ASoC: rt711-sdca: fix the latency time of c
[Kernel-packages] [Bug 1814234] Re: rtcpie in timers from ubuntu_kernel_selftests randomly failing
** Changed in: linux (Ubuntu Xenial) 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/1814234 Title: rtcpie in timers from ubuntu_kernel_selftests randomly failing Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: Node: Standard_D11_v2 Kernel: 4.18.0-1008.8~18.04.1 selftests: timers: rtcpie Periodic IRQ rate is 1024Hz. Counting 20 interrupts at: 2Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 4Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 8Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 16Hz:1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 32Hz:1 2 3 4 5 6 7 PIE delta error: 0.034667 should be close to 0.031250 181. 01/30 20:08:46 DEBUG| utils:0153| [stdout] not ok 1..9 selftests: timers: rtcpie [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1814234/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009286] Re: linux-image-unsigned-6.2.0-060200-generic/now doesn't load GUI
I didn't think about being the kernel mainline it should not covered by distribution support. I am closing my bud report ** Changed in: linux (Ubuntu) Status: Incomplete => 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/2009286 Title: linux-image-unsigned-6.2.0-060200-generic/now doesn't load GUI Status in linux package in Ubuntu: Invalid Bug description: Description:Ubuntu 22.04.2 LTS Release:22.04 I am running linux-image-unsigned-6.1.15-060115-generic/now successfully. If I try to run any 6.2.x image, after the boot screen I get a filesystem check, then the boot screen again which just hangs. The Ubuntu GUI never loads. Very happy to provide any further information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 (regression from -32)
@kobako the 5.19.9002-34-generic kernel in comment 14 is also "bad" -- 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 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: In Progress Bug 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 2009759] [NEW] Change default of CONFIG_EISA_VLB_PRIMING
Public bug reported: Currently the Ubuntu kernels ship with CONFIG_EISA_VLB_PRIMING=y. This doesn't match the upstream default (n) and this is the help text: Activate this option if your system contains a Vesa Local Bus (VLB) card that identify itself as an EISA card (such as the Adaptec AHA-284x). When in doubt, say N. I noticed this actually changes the kernel behavior such that it forces the probing code to probe EISA slots even when it cannot find an EISA compliant mainboard. This manifests in a collection of warnings on every boot. [0.985127] platform eisa.0: EISA: Cannot allocate resource for mainboard [0.985845] platform eisa.0: Cannot allocate resource for EISA slot 1 [0.986526] platform eisa.0: Cannot allocate resource for EISA slot 2 [0.987213] platform eisa.0: Cannot allocate resource for EISA slot 3 [0.987899] platform eisa.0: Cannot allocate resource for EISA slot 4 [0.988586] platform eisa.0: Cannot allocate resource for EISA slot 5 [0.989273] platform eisa.0: Cannot allocate resource for EISA slot 6 [0.989961] platform eisa.0: Cannot allocate resource for EISA slot 7 [0.990646] platform eisa.0: Cannot allocate resource for EISA slot 8 I think this config option should be changed to match upstream default for Ubuntu kernels. ** Affects: linux (Ubuntu) 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/2009759 Title: Change default of CONFIG_EISA_VLB_PRIMING Status in linux package in Ubuntu: New Bug description: Currently the Ubuntu kernels ship with CONFIG_EISA_VLB_PRIMING=y. This doesn't match the upstream default (n) and this is the help text: Activate this option if your system contains a Vesa Local Bus (VLB) card that identify itself as an EISA card (such as the Adaptec AHA-284x). When in doubt, say N. I noticed this actually changes the kernel behavior such that it forces the probing code to probe EISA slots even when it cannot find an EISA compliant mainboard. This manifests in a collection of warnings on every boot. [0.985127] platform eisa.0: EISA: Cannot allocate resource for mainboard [0.985845] platform eisa.0: Cannot allocate resource for EISA slot 1 [0.986526] platform eisa.0: Cannot allocate resource for EISA slot 2 [0.987213] platform eisa.0: Cannot allocate resource for EISA slot 3 [0.987899] platform eisa.0: Cannot allocate resource for EISA slot 4 [0.988586] platform eisa.0: Cannot allocate resource for EISA slot 5 [0.989273] platform eisa.0: Cannot allocate resource for EISA slot 6 [0.989961] platform eisa.0: Cannot allocate resource for EISA slot 7 [0.990646] platform eisa.0: Cannot allocate resource for EISA slot 8 I think this config option should be changed to match upstream default for Ubuntu kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007798] Re: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
This bug is awaiting verification that the linux-kvm/5.15.0-1030.35 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-kvm -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007798 Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: == SRU Justification == [Impact] Audio playback becomes silent on some Intel SoF systems. [Fix] Revert offending commit. [Test] The speaker can always play sound after the commit gets reverted. [Where problems could occur] Audio on linux 5.15 has been working fine without the patch for a long time, so this only restore it to where it was. == Original Bug Report == [Summary] During the kernel SRU testing on focal-hwe, I found the audio output of some machines are broken. I've tested some of machine on Jammy using same kernel(5.15.0-66-generic) and haven't seen this happened. The volume bars in settings react to what sound is played correctly and device is detected as well. [Reproduce steps] 1. install focal 2. enable -proposed 3. run apt dist-upgrade. 4. reboot. 5. press fn keys to volume up then volume down or play a short youtube video. 6. after a while can't hear any sound from the speaker. [Failure rate] 10/10 [Additional info] If I run "sudo alsa force-reload" can make audio work again, but after a while it breaks again. These are machines that impacted by this bug: https://certification.canonical.com/hardware/202007-28045/ https://certification.canonical.com/hardware/201906-27109/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/202007-28047/ https://certification.canonical.com/hardware/202007-28055/ https://certification.canonical.com/hardware/202005-27899/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-66.73~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1303 F pulseaudio CasperMD5CheckResult: skip Date: Sun Feb 19 21:24:59 2023 InstallationDate: Installed on 2020-08-03 (930 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Feb 19 20:53:23 dell-inspiron-7591-nebula-n15a-c2-201903-26881 dbus-daemon[985]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1303 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd11/06/2019:br1.5:svnDellInc.:pnInspiron7590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0922: dmi.product.family: Inspiron dmi.product.name: Inspiron 7590 dmi.product.sku: 0922 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007798/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009759] 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 2009759 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/2009759 Title: Change default of CONFIG_EISA_VLB_PRIMING Status in linux package in Ubuntu: Incomplete Bug description: Currently the Ubuntu kernels ship with CONFIG_EISA_VLB_PRIMING=y. This doesn't match the upstream default (n) and this is the help text: Activate this option if your system contains a Vesa Local Bus (VLB) card that identify itself as an EISA card (such as the Adaptec AHA-284x). When in doubt, say N. I noticed this actually changes the kernel behavior such that it forces the probing code to probe EISA slots even when it cannot find an EISA compliant mainboard. This manifests in a collection of warnings on every boot. [0.985127] platform eisa.0: EISA: Cannot allocate resource for mainboard [0.985845] platform eisa.0: Cannot allocate resource for EISA slot 1 [0.986526] platform eisa.0: Cannot allocate resource for EISA slot 2 [0.987213] platform eisa.0: Cannot allocate resource for EISA slot 3 [0.987899] platform eisa.0: Cannot allocate resource for EISA slot 4 [0.988586] platform eisa.0: Cannot allocate resource for EISA slot 5 [0.989273] platform eisa.0: Cannot allocate resource for EISA slot 6 [0.989961] platform eisa.0: Cannot allocate resource for EISA slot 7 [0.990646] platform eisa.0: Cannot allocate resource for EISA slot 8 I think this config option should be changed to match upstream default for Ubuntu kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980831] Re: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!
Since upgrading to 6.1.0-16-generic on lunar, I hit nearly the exact same error again, minus the "fences timed out" log: [728875.081136] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=263052, emitted seq=263054 [728875.081681] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process spotify pid 626324 thread spotify:cs0 pid 626354 [728875.082223] amdgpu :1f:00.0: amdgpu: GPU reset begin! [728875.674379] amdgpu: [powerplay] Failed message: 0x24, input parameter: 0x0, error code: 0x [728875.674390] amdgpu: [powerplay] Failed message: 0x9, input parameter: 0xf4, error code: 0x [728875.674395] amdgpu: [powerplay] Failed message: 0xa, input parameter: 0x103000, error code: 0x [728875.674399] amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x0, error code: 0x [728875.674403] amdgpu: [powerplay] Failed message: 0x42, input parameter: 0x1, error code: 0x [728875.674407] amdgpu: [powerplay] Failed message: 0x24, input parameter: 0x0, error code: 0x [728875.707103] [drm] REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:936 [728895.793037] [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 20secs aborting [728895.793200] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing E18E (len 824, WS 0, PS 0) @ 0xE30E [728895.793351] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing E048 (len 326, WS 0, PS 0) @ 0xE138 [728895.793501] [drm:dce110_link_encoder_disable_output [amdgpu]] *ERROR* dce110_link_encoder_disable_output: Failed to execute VBIOS command table! [728915.796976] [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 20secs aborting [728915.797146] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing C30A (len 62, WS 0, PS 0) @ 0xC326 [728935.800920] [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 20secs aborting [728935.801087] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing E18E (len 824, WS 0, PS 0) @ 0xE30E [728935.801238] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing E048 (len 326, WS 0, PS 0) @ 0xE138 [728935.801388] [drm:dce110_link_encoder_disable_output [amdgpu]] *ERROR* dce110_link_encoder_disable_output: Failed to execute VBIOS command table! [728955.804861] [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 20secs aborting [728955.805022] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing C30A (len 62, WS 0, PS 0) @ 0xC326 [728975.808802] [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 20secs aborting [728975.808971] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing B802 (len 1359, WS 12, PS 8) @ 0xBB17 -- 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/1980831 Title: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: When working normally, random freezes happen. Everything freezes, except the mouse cursor. I tried from keyboard to: switch to another window, start a terminal, run a command to restart gnome, enabled ctrl+alt+backspace and tried it to restart X windows, ctrl+alt+delete, switch to another session with ctrl+alt+F1-F9 - nothing works. If I'm listening to something, the sound goes on for a while; sometimes it stops by itself, other times it keeps going. The only way to recover that I've found is to stop the laptop from the power button. For a while I thought it was due to firefox; I installed the deb version and then switched to chrome - same behavior. It didn't happen when I was playing Hollow Knight in Steam, or when I've used the terminal and nothing else. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 6 14:27:36 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-06-16 (19 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1980831/+subscriptions -- Maili
[Kernel-packages] [Bug 2007875] Re: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently
Actually, the $ sudo make install for backport-iwlwifi will only be installed into the kernel you build it, it will not install itself to all the kernel version. To fix your firmware issue we usually try the latest firmware but it needs to update the driver to bump the ABI for loading the new firmware. If it is okay, would you please try to build it on 5.19.0-35-generic and boot into 5.19.0-35-generic kernel. Of course, please do it when you are available, don't bother to do it immediately since you already have a stable 5.15 kernel for your daily work. The reason that I suggest you to try it is because I can't reproduce it with my Netgear Nighthawk AP. Thanks for your understanding, -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2007875 Title: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently Status in linux-firmware package in Ubuntu: Fix Released Status in oem-somerville-tentacool-meta package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Committed Status in oem-somerville-tentacool-meta source package in Jammy: New Status in linux-firmware source package in Kinetic: Fix Released Status in oem-somerville-tentacool-meta source package in Kinetic: Invalid Status in linux-firmware source package in Lunar: Fix Released Status in oem-somerville-tentacool-meta source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] backport-iwlwifi-dkms/kinetic is being built into hwe-5.19 kernel, and -73 firmware are supported bug missing. On one user reported issue, this fixes WiFi stability on 5G band. [Fix] New upstreamed firmware revision fixes this issue. [Test Case] 1. Boot hwe-5.19 kernel 2. iwlwifi-so-a0-gf-a0-73.ucode firmware should be loaded 3. Browse the web, usually takes between 1 and 5 minutes 4. Networking will cut out [Where problems could occur] This affects only users need both backport-iwlwifi-dkms and hwe-5.19 kernel on WiFi stability. [Other Info] While Kinetic and above have them all, only Jammy is nominated. == original bug report == I'm using the stock Dell Ubuntu 22.04 image on my XPS 13 Plus (9320). Recently I received some kernel updates, the 5.19 kernel used in 22.10 and a 6.0 oem kernel. Both updates break wifi. It seems to only do so on newer 5.7 GHz access points. 1. Boot latest 6.0 oem kernel 2. Browse the web, usually takes between 1 and 5 minutes. 3. Networking will cut out. Disabling networking and starting again will fix it until it happens again in a few minutes. This will repeat indefinitely, essentially making wireless useless. The attached dmesg log reliably shows up when it fails, showing iwlwifi failing and a (network?) hardware reset request. It witnessed this happen months ago on 22.10, which led me to using the Dell stock 22.04 image. But it seems even the newer OEM kernel is affected. A workaround is to select the older 5.15 kernel in grub. I find on this laptop, one must hit escape precisely 1 second after seeing the Dell logo on boot. Alternatively one could edit /etc/grub/default and set a longer timeout. Let me know if this bug report would be better to go to Dell as a support request instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2007875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009759] Re: Change default of CONFIG_EISA_VLB_PRIMING
Hi Mario, What if Adaptec AHA-284x is really used by the system? Maybe tune down the log level instead? -- 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/2009759 Title: Change default of CONFIG_EISA_VLB_PRIMING Status in linux package in Ubuntu: Incomplete Bug description: Currently the Ubuntu kernels ship with CONFIG_EISA_VLB_PRIMING=y. This doesn't match the upstream default (n) and this is the help text: Activate this option if your system contains a Vesa Local Bus (VLB) card that identify itself as an EISA card (such as the Adaptec AHA-284x). When in doubt, say N. I noticed this actually changes the kernel behavior such that it forces the probing code to probe EISA slots even when it cannot find an EISA compliant mainboard. This manifests in a collection of warnings on every boot. [0.985127] platform eisa.0: EISA: Cannot allocate resource for mainboard [0.985845] platform eisa.0: Cannot allocate resource for EISA slot 1 [0.986526] platform eisa.0: Cannot allocate resource for EISA slot 2 [0.987213] platform eisa.0: Cannot allocate resource for EISA slot 3 [0.987899] platform eisa.0: Cannot allocate resource for EISA slot 4 [0.988586] platform eisa.0: Cannot allocate resource for EISA slot 5 [0.989273] platform eisa.0: Cannot allocate resource for EISA slot 6 [0.989961] platform eisa.0: Cannot allocate resource for EISA slot 7 [0.990646] platform eisa.0: Cannot allocate resource for EISA slot 8 I think this config option should be changed to match upstream default for Ubuntu kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980831] Re: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!
Brett, That's a different bug so please open a new one by running: ubuntu-bug linux -- 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/1980831 Title: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: When working normally, random freezes happen. Everything freezes, except the mouse cursor. I tried from keyboard to: switch to another window, start a terminal, run a command to restart gnome, enabled ctrl+alt+backspace and tried it to restart X windows, ctrl+alt+delete, switch to another session with ctrl+alt+F1-F9 - nothing works. If I'm listening to something, the sound goes on for a while; sometimes it stops by itself, other times it keeps going. The only way to recover that I've found is to stop the laptop from the power button. For a while I thought it was due to firefox; I installed the deb version and then switched to chrome - same behavior. It didn't happen when I was playing Hollow Knight in Steam, or when I've used the terminal and nothing else. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 6 14:27:36 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-06-16 (19 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1980831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.15.0.1030.26)
All autopkgtests for the newly accepted linux-meta-kvm (5.15.0.1030.26) for jammy have finished running. The following regressions have been reported in tests triggered by the package: oss4/4.2-build2010-5ubuntu9.1 (amd64) rtl8821ce/5.5.2.1-0ubuntu11~0.22.04.1 (amd64) backport-iwlwifi-dkms/9858-0ubuntu3.2 (amd64) digimend-dkms/10-4 (amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu17~22.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-kvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
The first test kernel (5.15.0-67-generic #74+test20230307b2h2cbb6062f8eb-Ubuntu) merely reverts file access cache-related commits. However, the second test kernel (5.15.0-67-generic #74+test20230308b0h1a13a615ee32-Ubuntu) truly identifies and resolves the problem. The file access cache, which belongs to the user, will be cleared once the user logs out and logs in again. After that, all behavior will be the same as usual. We would appreciate it if you could use the second test kernel for testing and confirm that it has resolved the performance issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/20
[Kernel-packages] [Bug 2009759] Re: Change default of CONFIG_EISA_VLB_PRIMING
It's ancient EISA card, does anything modern still use EISA? -- 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/2009759 Title: Change default of CONFIG_EISA_VLB_PRIMING Status in linux package in Ubuntu: Incomplete Bug description: Currently the Ubuntu kernels ship with CONFIG_EISA_VLB_PRIMING=y. This doesn't match the upstream default (n) and this is the help text: Activate this option if your system contains a Vesa Local Bus (VLB) card that identify itself as an EISA card (such as the Adaptec AHA-284x). When in doubt, say N. I noticed this actually changes the kernel behavior such that it forces the probing code to probe EISA slots even when it cannot find an EISA compliant mainboard. This manifests in a collection of warnings on every boot. [0.985127] platform eisa.0: EISA: Cannot allocate resource for mainboard [0.985845] platform eisa.0: Cannot allocate resource for EISA slot 1 [0.986526] platform eisa.0: Cannot allocate resource for EISA slot 2 [0.987213] platform eisa.0: Cannot allocate resource for EISA slot 3 [0.987899] platform eisa.0: Cannot allocate resource for EISA slot 4 [0.988586] platform eisa.0: Cannot allocate resource for EISA slot 5 [0.989273] platform eisa.0: Cannot allocate resource for EISA slot 6 [0.989961] platform eisa.0: Cannot allocate resource for EISA slot 7 [0.990646] platform eisa.0: Cannot allocate resource for EISA slot 8 I think this config option should be changed to match upstream default for Ubuntu kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009759] Re: Change default of CONFIG_EISA_VLB_PRIMING
Just for reference in a quick Google search on my profile for "Adaptec AHA-284x" my top hit was an OS/2 driver.. -- 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/2009759 Title: Change default of CONFIG_EISA_VLB_PRIMING Status in linux package in Ubuntu: Incomplete Bug description: Currently the Ubuntu kernels ship with CONFIG_EISA_VLB_PRIMING=y. This doesn't match the upstream default (n) and this is the help text: Activate this option if your system contains a Vesa Local Bus (VLB) card that identify itself as an EISA card (such as the Adaptec AHA-284x). When in doubt, say N. I noticed this actually changes the kernel behavior such that it forces the probing code to probe EISA slots even when it cannot find an EISA compliant mainboard. This manifests in a collection of warnings on every boot. [0.985127] platform eisa.0: EISA: Cannot allocate resource for mainboard [0.985845] platform eisa.0: Cannot allocate resource for EISA slot 1 [0.986526] platform eisa.0: Cannot allocate resource for EISA slot 2 [0.987213] platform eisa.0: Cannot allocate resource for EISA slot 3 [0.987899] platform eisa.0: Cannot allocate resource for EISA slot 4 [0.988586] platform eisa.0: Cannot allocate resource for EISA slot 5 [0.989273] platform eisa.0: Cannot allocate resource for EISA slot 6 [0.989961] platform eisa.0: Cannot allocate resource for EISA slot 7 [0.990646] platform eisa.0: Cannot allocate resource for EISA slot 8 I think this config option should be changed to match upstream default for Ubuntu kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009676] Re: Add support for Raptor Lake S CPUs
@Colin, but we don't have kernel support RPL-s in focal, how could I verify it? -- 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/2009676 Title: Add support for Raptor Lake S CPUs Status in OEM Priority Project: New Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Bug description: [Impact] * Support thermald on Raptor Lake S CPU. [Test Plan] * Use a machine with a Raptor Lake S cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake S in thermald, which won't impact other hardware. [Other Info] https://github.com/intel/thermal_daemon/commit/e03493dc1e972374c1686492655250f8f48a15ba To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 (regression from -32)
@Dave, thanks your effort. here's another kernel, reverted this patch. ~~~ fdcc4c22b7ab) ALSA: hda/hdmi - enable runtime pm for more AMD display audio ~~~ https://drive.google.com/drive/folders/1Ky7Xw6Yt8HVU0YLDbFRJX0ROuJ9O0iVU?usp=share_link -- 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 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: In Progress Bug 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 2002601] Re: Wireless: Enable RTL8852BE wifi driver
@Devon, thanks and enjoy your wireless. because Jammy needs lots of patches to backport, it's high risky. Lunar will have rtl8852be enablement. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2002601 Title: Wireless: Enable RTL8852BE wifi driver Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Justification] Enable Realtek RLT8852BE WIFI. [Test] 1. put rtw8852b_fw.bin in /lib/firmware/rtw89/ 2. boot-up with kernel enabled RTL8852be. 3. Connect to WIFI-AP and test with ping. * ping -I wlp2s0 8.8.8.8 ~~~ PING 8.8.8.8 (8.8.8.8) from 10.102.137.55 wlp2s0: 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=5.86 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=6.21 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=18.9 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=6.09 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=6.13 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=5.77 ms ~~~ * Connected to AP ~~~ u@ubuntu:~$ nmcli dev DEVICE TYPE STATE CONNECTION enp3s0 ethernet connected Wired connection 1 wlp2s0 wifi connected Canonical p2p-dev-wlp2s0 wifi-p2p disconnected -- lo loopback unmanaged -- ~~~ * lsmod | grep 8852 ~~~ lsmod | grep 8852 rtw89_8852be 16384 0 rtw89_8852b 368640 1 rtw89_8852be rtw89_pci 61440 1 rtw89_8852be rtw89_core 442368 2 rtw89_8852b,rtw89_pci cfg80211 1081344 3 rtw89_8852b,rtw89_core,mac80211 ~~~ 4. cbd's built result, Lunar, ~~~ remote: Resolving deltas: 100% (391/391), completed with 118 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'u_lMstrNxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-lunar-0e58018b43c1-ioeM remote: * 96/480 cores busy (1/5 hosts), 0 builds queued remote: 2023-01-12 03:16:35 kobako-lunar-0e58018b43c1-ioeM/amd64/BUILD-OK remote: 2023-01-12 03:17:47 kobako-lunar-0e58018b43c1-ioeM/arm64/BUILD-OK remote: 2023-01-12 03:11:36 kobako-lunar-0e58018b43c1-ioeM/armhf/BUILD-OK remote: 2023-01-12 03:16:30 kobako-lunar-0e58018b43c1-ioeM/ppc64el/BUILD-OK remote: 2023-01-12 03:10:24 kobako-lunar-0e58018b43c1-ioeM/s390x/BUILD-OK remote: To cbd:lunar.git ~~~ OEM-6.1, remote: Resolving deltas: 100% (399/399), completed with 121 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'oem-6.1-next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-c1002f30ccc3-m65z remote: * 0/192 cores busy (0/2 hosts), 0 builds queued remote: 2023-01-12 05:25:23 kobako-jammy-c1002f30ccc3-m65z/amd64/BUILD-OK remote: To cbd:jammy.git [Where problems could occur] Medium, a new driver so the current driver may have some edge cases didn't consider. [Misc] * For generic Jammy, need more patches to enable RTL8852be so only SRU for OEM-6.1. * firmware, dae5d4603b07) rtw89: 8852b: update fw to v0.27.32.1 has landed on Lunar, so only SRU for Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000785] Re: package linux-intel-iotg-tools-common 5.15.0-1018.23 failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-intel-iotg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2000785 Title: package linux-intel-iotg-tools-common 5.15.0-1018.23 failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 Status in linux-intel-iotg package in Ubuntu: Confirmed Bug description: Does not let me upgrade with sudo apt upgrade says there is an error even though I have not changed anything in the system files. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-intel-iotg-tools-common 5.15.0-1018.23 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 AptOrdering: linux-intel-iotg-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Dec 30 13:50:37 2022 DpkgTerminalLog: Preparing to unpack .../linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb ... Unpacking linux-intel-iotg-tools-common (5.15.0-1021.26) over (5.15.0-1018.23) ... dpkg: error processing archive /var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 DuplicateSignature: package:linux-intel-iotg-tools-common:5.15.0-1018.23 Unpacking linux-intel-iotg-tools-common (5.15.0-1021.26) over (5.15.0-1018.23) ... dpkg: error processing archive /var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 InstallationDate: Installed on 2022-10-06 (84 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-intel-iotg Title: package linux-intel-iotg-tools-common 5.15.0-1018.23 failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2000785/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
** Changed in: linux (Ubuntu) Assignee: (unassigned) => ChengEn, Du (chengendu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rv
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
Hello ChengEn, Du , Thanks for the test Kernel. I can no longer find a problem with this Kernel and NFS client. I also think that the kernel has fixed the problem. Best regards, -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMwa
[Kernel-packages] [Bug 2002601] Re: Wireless: Enable RTL8852BE wifi driver
@Koba, are you saying I should upgrade to Lunar Lobster? If so how do I do that (apart from installing off a fresh ISO)? Whenever I run >sudo apt-get install upgrade it says there aren’t any upgrades to install. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2002601 Title: Wireless: Enable RTL8852BE wifi driver Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Justification] Enable Realtek RLT8852BE WIFI. [Test] 1. put rtw8852b_fw.bin in /lib/firmware/rtw89/ 2. boot-up with kernel enabled RTL8852be. 3. Connect to WIFI-AP and test with ping. * ping -I wlp2s0 8.8.8.8 ~~~ PING 8.8.8.8 (8.8.8.8) from 10.102.137.55 wlp2s0: 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=5.86 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=6.21 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=18.9 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=6.09 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=6.13 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=5.77 ms ~~~ * Connected to AP ~~~ u@ubuntu:~$ nmcli dev DEVICE TYPE STATE CONNECTION enp3s0 ethernet connected Wired connection 1 wlp2s0 wifi connected Canonical p2p-dev-wlp2s0 wifi-p2p disconnected -- lo loopback unmanaged -- ~~~ * lsmod | grep 8852 ~~~ lsmod | grep 8852 rtw89_8852be 16384 0 rtw89_8852b 368640 1 rtw89_8852be rtw89_pci 61440 1 rtw89_8852be rtw89_core 442368 2 rtw89_8852b,rtw89_pci cfg80211 1081344 3 rtw89_8852b,rtw89_core,mac80211 ~~~ 4. cbd's built result, Lunar, ~~~ remote: Resolving deltas: 100% (391/391), completed with 118 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'u_lMstrNxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-lunar-0e58018b43c1-ioeM remote: * 96/480 cores busy (1/5 hosts), 0 builds queued remote: 2023-01-12 03:16:35 kobako-lunar-0e58018b43c1-ioeM/amd64/BUILD-OK remote: 2023-01-12 03:17:47 kobako-lunar-0e58018b43c1-ioeM/arm64/BUILD-OK remote: 2023-01-12 03:11:36 kobako-lunar-0e58018b43c1-ioeM/armhf/BUILD-OK remote: 2023-01-12 03:16:30 kobako-lunar-0e58018b43c1-ioeM/ppc64el/BUILD-OK remote: 2023-01-12 03:10:24 kobako-lunar-0e58018b43c1-ioeM/s390x/BUILD-OK remote: To cbd:lunar.git ~~~ OEM-6.1, remote: Resolving deltas: 100% (399/399), completed with 121 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'oem-6.1-next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-c1002f30ccc3-m65z remote: * 0/192 cores busy (0/2 hosts), 0 builds queued remote: 2023-01-12 05:25:23 kobako-jammy-c1002f30ccc3-m65z/amd64/BUILD-OK remote: To cbd:jammy.git [Where problems could occur] Medium, a new driver so the current driver may have some edge cases didn't consider. [Misc] * For generic Jammy, need more patches to enable RTL8852be so only SRU for OEM-6.1. * firmware, dae5d4603b07) rtw89: 8852b: update fw to v0.27.32.1 has landed on Lunar, so only SRU for Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002601] Re: Wireless: Enable RTL8852BE wifi driver
@Devon, you could always use 6.1-oem kernel and that would keep upgrading to last. if you want use the generic kernel, lunar may be a option but rtl8852be is still working on for Lunar. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2002601 Title: Wireless: Enable RTL8852BE wifi driver Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Justification] Enable Realtek RLT8852BE WIFI. [Test] 1. put rtw8852b_fw.bin in /lib/firmware/rtw89/ 2. boot-up with kernel enabled RTL8852be. 3. Connect to WIFI-AP and test with ping. * ping -I wlp2s0 8.8.8.8 ~~~ PING 8.8.8.8 (8.8.8.8) from 10.102.137.55 wlp2s0: 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=5.86 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=6.21 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=18.9 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=6.09 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=6.13 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=5.77 ms ~~~ * Connected to AP ~~~ u@ubuntu:~$ nmcli dev DEVICE TYPE STATE CONNECTION enp3s0 ethernet connected Wired connection 1 wlp2s0 wifi connected Canonical p2p-dev-wlp2s0 wifi-p2p disconnected -- lo loopback unmanaged -- ~~~ * lsmod | grep 8852 ~~~ lsmod | grep 8852 rtw89_8852be 16384 0 rtw89_8852b 368640 1 rtw89_8852be rtw89_pci 61440 1 rtw89_8852be rtw89_core 442368 2 rtw89_8852b,rtw89_pci cfg80211 1081344 3 rtw89_8852b,rtw89_core,mac80211 ~~~ 4. cbd's built result, Lunar, ~~~ remote: Resolving deltas: 100% (391/391), completed with 118 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'u_lMstrNxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-lunar-0e58018b43c1-ioeM remote: * 96/480 cores busy (1/5 hosts), 0 builds queued remote: 2023-01-12 03:16:35 kobako-lunar-0e58018b43c1-ioeM/amd64/BUILD-OK remote: 2023-01-12 03:17:47 kobako-lunar-0e58018b43c1-ioeM/arm64/BUILD-OK remote: 2023-01-12 03:11:36 kobako-lunar-0e58018b43c1-ioeM/armhf/BUILD-OK remote: 2023-01-12 03:16:30 kobako-lunar-0e58018b43c1-ioeM/ppc64el/BUILD-OK remote: 2023-01-12 03:10:24 kobako-lunar-0e58018b43c1-ioeM/s390x/BUILD-OK remote: To cbd:lunar.git ~~~ OEM-6.1, remote: Resolving deltas: 100% (399/399), completed with 121 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'oem-6.1-next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-c1002f30ccc3-m65z remote: * 0/192 cores busy (0/2 hosts), 0 builds queued remote: 2023-01-12 05:25:23 kobako-jammy-c1002f30ccc3-m65z/amd64/BUILD-OK remote: To cbd:jammy.git [Where problems could occur] Medium, a new driver so the current driver may have some edge cases didn't consider. [Misc] * For generic Jammy, need more patches to enable RTL8852be so only SRU for OEM-6.1. * firmware, dae5d4603b07) rtw89: 8852b: update fw to v0.27.32.1 has landed on Lunar, so only SRU for Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009785] [NEW] [RTL8821CE] WLAN functionality cannot be controlled any more
You have been subscribed to a public bug: After the latest upgrade and a reboot, the WLAN connectivity features have disappeared from the menu on the upper right hand side menu, and the system does not connect to the local WLAN at my home; in short: WLAN DOES NOT WORK ANY MORE (Luckily, Ethernet connectivity is still available so I can send this using USB tethering.) New, however is Bluetooth connectivity control. Turning this off, turns on airplane mode; turning airplane mode off returns the Bluetooth control menu entry. $ lspci -nnk -d::0280 02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter [10ec:c821] DeviceName: WLAN Subsystem: Hewlett-Packard Company RTL8821CE 802.11ac PCIe Wireless Network Adapter [103c:831a] Kernel modules: rtw88_8821ce THIS DOES NOT REPORT A KERNEL DRIVER IN USE. Thank you Wolfgang ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 9 05:12:28 2023 DistUpgraded: 2022-11-14 12:08:39,894 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl8821ce/5.5.2.1, 5.15.0-67-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G1 (Ice Lake) [103c:86c1] InstallationDate: Installed on 2020-12-19 (809 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP 250 G7 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=ac8de2b3-079a-406a-af37-4891044b3642 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-11-14 (114 days ago) dmi.bios.date: 07/31/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 86C1 dmi.board.vendor: HP dmi.board.version: 89.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 89.35 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/31/2020:br15.33:efr89.35:svnHP:pnHP250G7NotebookPC:pvrType1ProductConfigId:rvnHP:rn86C1:rvr89.35:cvnHP:ct10:cvrChassisVersion:sku1B7K9ES#ABD: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 250 G7 Notebook PC dmi.product.sku: 1B7K9ES#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- [RTL8821CE] WLAN functionality cannot be controlled any more https://bugs.launchpad.net/bugs/2009785 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009785] Re: [RTL8821CE] WLAN functionality cannot be controlled any more
Thanks for the bug report. If the built-in driver 'rtw88_8821ce' isn't working then please try the add-on driver: sudo apt update sudo apt full-upgrade sudo apt install rtl8821ce-dkms and then reboot. ** Summary changed: - WLAN functionality cannot be controlled any more + [RTL8821CE] WLAN functionality cannot be controlled any more ** Package changed: xorg (Ubuntu) => linux-hwe-5.19 (Ubuntu) -- 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/2009785 Title: [RTL8821CE] WLAN functionality cannot be controlled any more Status in linux-hwe-5.19 package in Ubuntu: New Bug description: After the latest upgrade and a reboot, the WLAN connectivity features have disappeared from the menu on the upper right hand side menu, and the system does not connect to the local WLAN at my home; in short: WLAN DOES NOT WORK ANY MORE (Luckily, Ethernet connectivity is still available so I can send this using USB tethering.) New, however is Bluetooth connectivity control. Turning this off, turns on airplane mode; turning airplane mode off returns the Bluetooth control menu entry. $ lspci -nnk -d::0280 02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter [10ec:c821] DeviceName: WLAN Subsystem: Hewlett-Packard Company RTL8821CE 802.11ac PCIe Wireless Network Adapter [103c:831a] Kernel modules: rtw88_8821ce THIS DOES NOT REPORT A KERNEL DRIVER IN USE. Thank you Wolfgang ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 9 05:12:28 2023 DistUpgraded: 2022-11-14 12:08:39,894 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl8821ce/5.5.2.1, 5.15.0-67-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G1 (Ice Lake) [103c:86c1] InstallationDate: Installed on 2020-12-19 (809 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP 250 G7 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=ac8de2b3-079a-406a-af37-4891044b3642 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-11-14 (114 days ago) dmi.bios.date: 07/31/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 86C1 dmi.board.vendor: HP dmi.board.version: 89.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 89.35 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/31/2020:br15.33:efr89.35:svnHP:pnHP250G7NotebookPC:pvrType1ProductConfigId:rvnHP:rn86C1:rvr89.35:cvnHP:ct10:cvrChassisVersion:sku1B7K9ES#ABD: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 250 G7 Notebook PC dmi.product.sku: 1B7K9ES#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009785/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990750] Re: Boot issue with Ubuntu 22.10 Kinetic Kudu since Kernel 5.19.0.15.15, now hanging with blinking cursor after update to Kernel 5.19.0.21.21
*** This bug is a duplicate of bug 1975650 *** https://bugs.launchpad.net/bugs/1975650 'black screen', 'ubuntu', 'blinking cursor', 'nVidia' do not describe a bug, but instead are common characteristics of many thousands of different bugs. Although bug 1975650 doesn't seem to describe a black screen problem, if you find that reinstalling the driver fixed the issue (comment #25) then we should keep this as a duplicate of bug 1975650. One possible reason for a black screen is that Nvidia systems are known to sometimes boot to the wrong VT, or even log into the wrong VT. The workaround for that is to use Ctrl+Alt+F1-FN to find the correct screen. Like in bug 1960868 and bug 1878838. If your black screen problem persists after reinstalling the Nvidia driver, or if you would like to continue debugging that issue, then please use 'journalctl -b-1' or similar to collect a full system log from when the black screen was occurring. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1990750 Title: Boot issue with Ubuntu 22.10 Kinetic Kudu since Kernel 5.19.0.15.15, now hanging with blinking cursor after update to Kernel 5.19.0.21.21 Status in linux package in Ubuntu: Confirmed Bug description: When starting the PC, the splash screen freezes with the motherboard logo displayed. As my disk is encrypted the decryption field does not appear below the logo. By typing [ALT] + [CTRL] + [DEL] then the splash screen appears again followed by a start-up menu with the following line: *Ubuntu Advanced options for Ubuntu By selecting 'Advanced options for Ubuntu' the following submenu appears: *Ubuntu, with Linux5.19.0-15-generic Ubuntu, with Linux5.19.0-15-generic (recovery mode) Selecting the second option, then the system starts loading with the initial lines of code: Loading Linux 5.19.0-15-generic ... Loading initial ramdisk ... When code has finished loading, the last line at the bottom of the screen is for unlocking the disk: Begin: Mounting root fie system ... Begin Running /script/local-top ... Please unlock disk nvme0n1p3_crypt: Then i type in the code and hit [return] and more code is loading, until a recovery menu with purple background appears, with the title: Recovery Menu (filesystem state: read-only). I select the first menu item: resume Resume normal boot and hit [return]. The menu changes to the notification: You are now going to exit the recovery mode bla bla bla with the [OK] button below it. I hit the [OK] button and then the login screen finally appears. I will post a video of the complete boot sequence later on as I need to install a softaware to edit the video. It is noteworthy that on my previous Ubuntu 22.04 install the same issue with the frozen splash screen occurred when my system was updated with Kernel 5.15.5, but then I did not try out to execute the [ALT] + [CTRL] + [DEL] command. Therefore the bug is probably affecting all kernels from 5.15.5 upwards. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset wl nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Sep 25 08:30:29 2022 InstallationDate: Installed on 2022-09-24 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220920) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/vgubuntu-root ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.sku: To be filled by O.E.M. dmi.product.version
[Kernel-packages] [Bug 2009642] Re: mt7921: add support of MTFG table
** Tags added: kern-6013 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2009642 Title: mt7921: add support of MTFG table Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware 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-firmware source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Add ACPI MTFG table support of Mediatek MT7922 Wi-Fi driver to enable 6G power enhance feature. [Fix] Add MTFG table in driver and update firmware to support it. Lunar already got the firmware, so SRU for Jammy only. Kernel commit is a new feature and it requests more than 10 unrelated commits when backport to 5.15 and 5.19, so SRU for 6.0+ kernel version. [Test] Verified WiFi on 2.4/5GHz only because of no 6G environment. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009642/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009685] Re: iwlwifi hard system crash when collecting data
** Tags added: kern-6014 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2009685 Title: iwlwifi hard system crash when collecting data Status in linux-firmware package in Ubuntu: Invalid Bug description: After a random amount of time the system crashes and everytime it has something to do with iwlwifi, always at the same line: WRT: Collecting data: ini trigger 4 fired (delay=0ms). This seems to be jumpstarted by an Error sending logs. Two examples: - Mar 2 15:57:26 ironwarrior kernel: [25087.967111] iwlwifi :00:14.3: Error sending SCAN_CFG_CMD: time out after 2000ms. - Mar 8 08:57:43 ironwarrior kernel: [ 155.033518] iwlwifi :00:14.3: Error sending STATISTICS_CMD: time out after 2000ms. When system hangs I am forced to do a hardware reset. Is there any short fix I can do to avoid this while it's being looked at? Assuming this is the right place to report this bug. Thank you lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 - lspci -nnk | grep 0280 -A3 00:14.3 Network controller [0280]: Intel Corporation Tiger Lake PCH CNVi WiFi [8086:43f0] (rev 11) DeviceName: Onboard - Ethernet Subsystem: Intel Corporation Wi-Fi 6 AX201 160MHz [8086:0074] Kernel driver in use: iwlwifi - apt-cache policy linux-firmware linux-firmware: Installed: 20220329.git681281e4-0ubuntu3.10 Candidate: 20220329.git681281e4-0ubuntu3.10 Version table: *** 20220329.git681281e4-0ubuntu3.10 500 500 http://pt.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://pt.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 20220329.git681281e4-0ubuntu3.9 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 20220329.git681281e4-0ubuntu1 500 500 http://pt.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://pt.archive.ubuntu.com/ubuntu jammy/main i386 Packages Random output text of /var/log/syslog Mar 8 08:57:43 ironwarrior kernel: [ 155.033518] iwlwifi :00:14.3: Error sending STATISTICS_CMD: time out after 2000ms. Mar 8 08:57:43 ironwarrior kernel: [ 155.033524] iwlwifi :00:14.3: Current CMD queue read_ptr 135 write_ptr 136 Mar 8 08:57:43 ironwarrior kernel: [ 155.035160] iwlwifi :00:14.3: Start IWL Error Log Dump: Mar 8 08:57:43 ironwarrior kernel: [ 155.035161] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 Mar 8 08:57:43 ironwarrior kernel: [ 155.035162] iwlwifi :00:14.3: Loaded firmware version: 72.daa05125.0 QuZ-a0-hr-b0-72.ucode Mar 8 08:57:43 ironwarrior kernel: [ 155.035163] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN Mar 8 08:57:43 ironwarrior kernel: [ 155.035164] iwlwifi :00:14.3: 0x22F0 | trm_hw_status0 Mar 8 08:57:43 ironwarrior kernel: [ 155.035165] iwlwifi :00:14.3: 0x | trm_hw_status1 Mar 8 08:57:43 ironwarrior kernel: [ 155.035166] iwlwifi :00:14.3: 0x004CC13E | branchlink2 Mar 8 08:57:43 ironwarrior kernel: [ 155.035167] iwlwifi :00:14.3: 0x00019940 | interruptlink1 Mar 8 08:57:43 ironwarrior kernel: [ 155.035168] iwlwifi :00:14.3: 0x00019940 | interruptlink2 Mar 8 08:57:43 ironwarrior kernel: [ 155.035168] iwlwifi :00:14.3: 0x004C3F84 | data1 Mar 8 08:57:43 ironwarrior kernel: [ 155.035169] iwlwifi :00:14.3: 0x0100 | data2 Mar 8 08:57:43 ironwarrior kernel: [ 155.035170] iwlwifi :00:14.3: 0x | data3 Mar 8 08:57:43 ironwarrior kernel: [ 155.035171] iwlwifi :00:14.3: 0x65C10249 | beacon time Mar 8 08:57:43 ironwarrior kernel: [ 155.035171] iwlwifi :00:14.3: 0xF0EBFDC9 | tsf low Mar 8 08:57:43 ironwarrior kernel: [ 155.035172] iwlwifi :00:14.3: 0x0076 | tsf hi Mar 8 08:57:43 ironwarrior kernel: [ 155.035173] iwlwifi :00:14.3: 0x | time gp1 Mar 8 08:57:43 ironwarrior kernel: [ 155.035173] iwlwifi :00:14.3: 0x08F462FA | time gp2 Mar 8 08:57:43 ironwarrior kernel: [ 155.035174] iwlwifi :00:14.3: 0x0001 | uCode revision type Mar 8 08:57:43 ironwarrior kernel: [ 155.035175] iwlwifi :00:14.3: 0x0048 | uCode version major Mar 8 08:57:43 ironwarrior kernel: [ 155.035176] iwlwifi :00:14.3: 0xDAA05125 | uCode version minor Mar 8 08:57:43 ironwarrior kernel: [ 155.035176] iwlwifi :00:14.3: 0x0351 | hw version Mar 8 08:57:43 ironwarrior kernel: [ 155.035177] iwlwifi :00:14.3: 0x00C89001 | board version Mar 8 08:57:43 ironwarrior kernel: [ 155.035178] iwlwifi :00:14.3: 0x80F4F400 | hcmd Mar
[Kernel-packages] [Bug 2009676] Re: Add support for Raptor Lake S CPUs
The support plan for RPL-S is Focal - will not support RPL-S. Jammy - will support with the patch thermald 2.5.2 in this SRU and linux-oem 6.1+ -- 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/2009676 Title: Add support for Raptor Lake S CPUs Status in OEM Priority Project: New Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Bug description: [Impact] * Support thermald on Raptor Lake S CPU. [Test Plan] * Use a machine with a Raptor Lake S cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake S in thermald, which won't impact other hardware. [Other Info] https://github.com/intel/thermal_daemon/commit/e03493dc1e972374c1686492655250f8f48a15ba To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999375] Re: Update dg2_dmc to 2.08
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1999375 Title: Update dg2_dmc to 2.08 Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Invalid Status in linux-firmware source package in Kinetic: Fix Released Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: [Impact] i915/dg2 needs this new firmware version to fix some undisclosed bugs The kernel commit is in 6.2 and up, so lunar should eventually be covered once it moves to it. [Test case] Boot a system with the new firmware and a kernel that uses it, and check that the correct version is loaded. [Where things could go wrong] If the kernel is updated before the firmware is available, then loading i915 fails as it can't find the firmware it requires. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999375/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006453] Re: Fix selftests/ftracetests/Meta-selftests
I've cherry-picked a fix for oem-6.1, thanks ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2006453 Title: Fix selftests/ftracetests/Meta-selftests Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux-oem-6.1 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Committed 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 2009014] Re: Some QHD panels fail to refresh when PSR2 enabled
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009014 Title: Some QHD panels fail to refresh when PSR2 enabled Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: [Impact] Some QHD (2560x1440) panels which support PSR2 refresh the display abnormally. The display frequently stop responding for few seconds on all user interactions, ex. mouse movement, TTY and any APP GUI. There's no problem on the external monitor. After disabling PSR, the problem will be gone. [Fix] Intel release a fix to calculate the wake up line count and configure them into PSR2_CTL accordingly. [Test] Verified on the problematic panels to check if the display responds smoothly to mouse movement. [Where problems could occur] Only affects the panels on some particular panels which supports PSR2 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009014/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007823] Re: Mute/mic LEDs no function on a HP platfrom
You need to always add 'linux' to bugs targeted for linux-oem-NN, that's the only way to track if a fix has landed in the devel series or not. Lunar is getting 6.2, does that contain this fix? ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux (Ubuntu Lunar) Status: New => Incomplete ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007823 Title: Mute/mic LEDs no function on a HP platfrom Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed 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: Incomplete Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on a HP platform. [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. Applied on oem-6.1 and it works fine. [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/2007823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007823] Re: Mute/mic LEDs no function on a HP platfrom
fix committed via 6.1.13 (bug 2008707) -- 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/2007823 Title: Mute/mic LEDs no function on a HP platfrom Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed 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: Incomplete Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on a HP platform. [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. Applied on oem-6.1 and it works fine. [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/2007823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006945] Re: New DG2 workarounds
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2006945 Title: New DG2 workarounds Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: [Impact] These are hw revision based workarounds from 6.2 that need to be backported for Intel Arc/DG2. [Test case] We don't have known issues that these would fix, but check that things still work normally. [Where things could go wrong] these are limited to a very specific type of hardware, so can't think of what could go wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009164] Re: Fix screen that remains blank forever after it gets locked
Does it work with earlier kernels, meaning is this bug a regression in itself? Backporting 41 commits to an LTS kernel might cause issues in the future.. -- 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/2009164 Title: Fix screen that remains blank forever after it gets locked Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Bug description: [Impact] Once screen is locked under gnome-shell, the screen never wakes up and remains in blank forever. [Fix] "drm/i915: Create resized LUTs for ivb+ split gamma mode" makes gamma LUT operations in atomic context, so userspace can no longer misuse libdrm. "drm/i915: Rework legacy LUT handling" starts to use the reworked gamma LUT. Pull the whole series and series they depends upon to properly support gamma LUT. [Test] The easier way to reproduce the issue is to 1) Login under Wayland 2) Logout and login under X 3) Go back to wayland 4) Super + L to screenlock With the LUT reworked series applied, screen can always come back alive. [Where problems could occur] Regression can happen on refactoring patches with "no functional change intended", let alone overhauls like this one. So only OEM-6.1 and Unstable are targeted to contain the potential regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007824] Re: Mute/mic LEDs and speaker no function on some HP platfroms
is this in 6.2? ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux (Ubuntu Lunar) Status: New => Incomplete ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007824 Title: Mute/mic LEDs and speaker no function on some HP platfroms Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed 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: Incomplete Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The mic mute/audio mute LEDS and speaker are not work on some HP platforms. [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs and speaker are working good. Applied on oem-6.1 and it works fine. [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/2007824/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007824] Re: Mute/mic LEDs and speaker no function on some HP platfroms
fixed in 6.1.13 -- 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/2007824 Title: Mute/mic LEDs and speaker no function on some HP platfroms Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed 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: Incomplete Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The mic mute/audio mute LEDS and speaker are not work on some HP platforms. [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs and speaker are working good. Applied on oem-6.1 and it works fine. [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/2007824/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007585] Re: Jammy update: v6.1.12 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007585 Title: Jammy update: v6.1.12 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.12 upstream stable release from git://git.kernel.org/ Linux 6.1.12 Documentation/hw-vuln: Add documentation for Cross-Thread Return Predictions KVM: x86: Mitigate the cross-thread return address predictions bug x86/speculation: Identify processors vulnerable to SMT RSB predictions drm/i915: Fix VBT DSI DVO port handling drm/i915: Initialize the obj flags for shmem objects drm/i915: Move fd_install after last use of fence drm/amd/display: fix cursor offset on rotation 180 drm/amd/display: properly handling AGP aperture in vm setup drm/amdgpu/smu: skip pptable init under sriov drm/amdgpu/fence: Fix oops due to non-matching drm_sched init/fini drm/amd/pm: bump SMU 13.0.7 driver_if header version drm/amdgpu: Add unique_id support for GC 11.0.1/2 drm/amd/pm: bump SMU 13.0.0 driver_if header version arm64: efi: Force the use of SetVirtualAddressMap() on eMAG and Altra Max machines Fix page corruption caused by racy check in __free_pages arm64: dts: meson-axg: Make mmc host controller interrupts level-sensitive arm64: dts: meson-g12-common: Make mmc host controller interrupts level-sensitive arm64: dts: meson-gx: Make mmc host controller interrupts level-sensitive rtmutex: Ensure that the top waiter is always woken up tracing: Fix TASK_COMM_LEN in trace event format file drm/amdgpu: Use the TGID for trace_amdgpu_vm_update_ptes powerpc/64s/interrupt: Fix interrupt exit race with security mitigation switch riscv: kprobe: Fixup misaligned load text riscv: Fixup race condition on PG_dcache_clean in flush_icache_pte nvdimm: Support sizeof(struct page) > MAX_STRUCT_PAGE_SIZE ceph: flush cap releases when the session is flushed drm/amd/pm: add SMU 13.0.7 missing GetPptLimit message mapping pinctrl: qcom: sm8450-lpass-lpi: correct swr_rx_data group clk: ingenic: jz4760: Update M/N/OD calculation algorithm cxl/region: Fix passthrough-decoder detection cxl/region: Fix null pointer dereference for resetting decoder usb: typec: altmodes/displayport: Fix probe pin assign check usb: core: add quirk for Alcor Link AK9563 smartcard reader btrfs: free device in btrfs_close_devices for a single device filesystem btrfs: simplify update of last_dir_index_offset when logging a directory selftests: mptcp: stop tests earlier selftests: mptcp: allow more slack for slow test-case mptcp: be careful on subflow status propagation on errors mptcp: do not wait for bare sockets' timeout net: USB: Fix wrong-direction WARNING in plusb.c cifs: Fix use-after-free in rdata->read_into_pages() pinctrl: intel: Restore the pins that used to be in Direct IRQ mode pinctrl: aspeed: Revert "Force to disable the function's signal" spi: dw: Fix wrong FIFO level setting for long xfers pinctrl: single: fix potential NULL dereference pinctrl: aspeed: Fix confusing types in return value pinctrl: mediatek: Fix the drive register definition of some Pins clk: microchip: mpfs-ccc: Use devm_kasprintf() for allocating formatted strings ASoC: topology: Return -ENOMEM on memory allocation failure ASoC: fsl_sai: fix getting version from VERID ASoC: tas5805m: add missing page switch. ASoC: tas5805m: rework to avoid scheduling while atomic. arm64: dts: mediatek: mt8195: Fix vdosys* compatible strings riscv: stacktrace: Fix missing the first frame ALSA: pci: lx6464es: fix a debug loop arm64: dts: rockchip: set sdmmc0 speed to sd-uhs-sdr50 on rock-3a arm64: dts: rockchip: fix input enable pinconf on rk3399 selftests: forwarding: lib: quote the sysctl values net: mscc: ocelot: fix all IPv6 getting trapped to CPU when PTP timestamping is used rds: rds_rm_zerocopy_callback() use list_first_entry() selftests: Fix failing VXLAN VNI filtering test txhash: fix sk->sk_txrehash default net: ethernet: mtk_eth_soc: fix wrong parameters order in __xdp_rxq_info_reg() igc: Add ndo_tx_timeout support net/mlx5: Serialize module cleanup with reload and remove net/mlx5: fw_tracer, Zero consumer index when reloading
[Kernel-packages] [Bug 2007584] Re: Jammy update: v6.1.11 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2007584
Title:
Jammy update: v6.1.11 upstream stable release
Status in OEM Priority Project:
New
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v6.1.11 upstream stable release
from git://git.kernel.org/
Linux 6.1.11
bpf: Skip invalid kfunc call in backtrack_insn
gfs2: Always check inode size of inline inodes
gfs2: Cosmetic gfs2_dinode_{in,out} cleanup
wifi: brcmfmac: Check the count value of channel spec to prevent
out-of-bounds reads
f2fs: fix to do sanity check on i_extra_isize in is_alive()
fbdev: smscufx: fix error handling code in ufx_usb_probe
f2fs: initialize locks earlier in f2fs_fill_super()
ovl: Use "buf" flexible array for memcpy() destination
fs/ntfs3: Validate attribute data and valid sizes
powerpc/imc-pmu: Revert nest_init_lock to being a mutex
powerpc/64s: Fix local irq disable when PMIs are disabled
powerpc/64s/radix: Fix crash with unaligned relocated kernel
iio:adc:twl6030: Enable measurement of VAC
ASoC: SOF: sof-audio: prepare_widgets: Check swidget for NULL on sink failure
platform/x86/amd: pmc: add CONFIG_SERIO dependency
serial: 8250_dma: Fix DMA Rx rearm race
serial: 8250_dma: Fix DMA Rx completion race
phy: qcom-qmp-combo: fix runtime suspend
nvmem: core: fix return value
nvmem: core: fix cell removal on error
nvmem: core: fix device node refcounting
nvmem: core: fix registration vs use race
nvmem: core: fix cleanup after dev_set_name()
nvmem: core: remove nvmem_config wp_gpio
nvmem: core: initialise nvmem->id early
drm/amdgpu: update wave data type to 3 for gfx11
drm/amd/pm: drop unneeded dpm features disablement for SMU 13.0.4/11
drm/amd: Fix initialization for nbio 4.3.0
drm/i915: Fix potential bit_17 double-free
drm/i915: Avoid potential vm use-after-free
serial: stm32: Merge hard IRQ and threaded IRQ handling into single IRQ
handler
dma-buf: actually set signaling bit for private stub fences
migrate: hugetlb: check for hugetlb shared PMD in node migration
maple_tree: fix mas_empty_area_rev() lower bound validation
Squashfs: fix handling and sanity checking of xattr_ids count
ia64: fix build error due to switch case label appearing next to declaration
highmem: round down the address passed to kunmap_flush_on_unmap()
mm/MADV_COLLAPSE: catch !none !huge !bad pmd lookups
mm, mremap: fix mremap() expanding for vma's with vm_ops->close()
mm/khugepaged: fix ->anon_vma race
mm/swapfile: add cond_resched() in get_swap_pages()
mm/uffd: fix pte marker when fork() without fork event
fpga: stratix10-soc: Fix return value check in s10_ops_write_init()
fpga: m10bmc-sec: Fix probe rollback
x86/debug: Fix stack recursion caused by wrongly ordered DR7 accesses
HV: hv_balloon: fix memory leak with using debugfs_lookup()
kernel/irq/irqdomain.c: fix memory leak with using debugfs_lookup()
usb: gadget: udc: do not clear gadget driver.bus
usb: typec: ucsi: Don't attempt to resume the ports before they exist
usb: gadget: f_uac2: Fix incorrect increment of bNumEndpoints
mm: memcg: fix NULL pointer in mem_cgroup_track_foreign_dirty_slowpath()
mm: hugetlb: proc: check for hugetlb shared PMD in /proc/PID/smaps
mm: multi-gen LRU: fix crash during cgroup migration
Revert "mm: kmemleak: alloc gray object for reserved region with direct map"
riscv: disable generation of unwind tables
parisc: Wire up PTRACE_GETREGS/PTRACE_SETREGS for compat case
parisc: Replace hardcoded value with PRIV_USER constant in ptrace.c
parisc: Fix return code of pdc_iodc_print()
nvmem: qcom-spmi-sdam: fix module autoloading
nvmem: sunxi_sid: Always use 32-bit MMIO reads
nvmem: brcm_nvram: Add check for kzalloc
iio: imu: fxos8700: fix MAGN sensor scale and unit
iio: imu: fxos8700: remove definition FXOS8700_CTRL_ODR_MIN
iio: imu: fxos8700: fix failed initialization ODR mode assignment
iio: imu: fxos8700: fix incorrect ODR mode readback
iio: imu: fxos8700: fix swapped ACCEL and MAGN channels readback
iio: imu: fxos8700: fix map label of channel type to MAGN sensor
iio: imu: fxos8700: fix IMU data bits returned to user space
iio: imu: fxos8700: fix incomplete ACC
[Kernel-packages] [Bug 2007516] Re: screen flicker after PSR2 enabled
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007516 Title: screen flicker after PSR2 enabled Status in HWE Next: New Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed 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: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: The screen flicker after ubuntu jammy upgrade kernel to 5.19. The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in 5.19 kernel. I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config can omit the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007583] Re: Jammy update: v6.1.10 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007583 Title: Jammy update: v6.1.10 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.10 upstream stable release from git://git.kernel.org/ Linux 6.1.10 net: mctp: purge receive queues on sk destruction rust: print: avoid evaluating arguments in `pr_*` macros in `unsafe` blocks net: fix NULL pointer in skb_segment_list gpiolib-acpi: Don't set GPIOs for wakeup in S3 mode gpiolib: acpi: Add a ignore wakeup quirk for Clevo NL5xRU nvme-apple: only reset the controller when RTKit is running cifs: fix return of uninitialized rc in dfs_cache_update_tgthint() gpiolib: acpi: Allow ignoring wake capability on pins that aren't in _AEI dmaengine: imx-sdma: Fix a possible memory leak in sdma_transfer_init HID: playstation: sanity check DualSense calibration data. HID: uclogic: Add support for XP-PEN Deco 01 V2 s390: workaround invalid gcc-11 out of bounds read warning block: fix hctx checks for batch allocation ACPI: video: Add backlight=native DMI quirk for Acer Aspire 4810T LoongArch: Get frame info in unwind_start() when regs is not available blk-cgroup: fix missing pd_online_fn() while activating policy erofs: clean up parsing of fscache related options kselftest: Fix error message for unconfigured LLVM builds ARM: omap1: fix building gpio15xx arm64: dts: msm8994-angler: fix the memory map mac80211: Fix MLO address translation for multiple bss case erofs/zmap.c: Fix incorrect offset calculation bpf: Skip task with pid=1 in send_signal_common() firmware: arm_scmi: Clear stale xfer->hdr.status arm64: dts: imx8mq-thor96: fix no-mmc property for SDHCI arm64: dts: freescale: Fix pca954x i2c-mux node names ARM: dts: vf610: Fix pca9548 i2c-mux node names ARM: dts: imx: Fix pca9547 i2c-mux node name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2007583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007578] Re: Jammy update: v6.1.9 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007578 Title: Jammy update: v6.1.9 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.9 upstream stable release from git://git.kernel.org/ Linux 6.1.9 amdgpu: fix build on non-DCN platforms. perf/x86/amd: fix potential integer overflow on shift of a int netfilter: conntrack: unify established states for SCTP paths dt-bindings: i2c: renesas,rzv2m: Fix SoC specific string x86/i8259: Mark legacy PIC interrupts with IRQ_LEVEL dt-bindings: riscv: fix single letter canonical order dt-bindings: riscv: fix underscore requirement for multi-letter extensions acpi: Fix suspend with Xen PV x86/sev: Add SEV-SNP guest feature negotiation support Input: i8042 - add Clevo PCX0DX to i8042 quirk table Revert "Input: synaptics - switch touchpad on HP Laptop 15-da3001TU to RMI mode" Revert "mm/compaction: fix set skip in fast_find_migrateblock" Fix up more non-executable files marked executable tools: gpio: fix -c option of gpio-event-mon treewide: fix up files incorrectly marked executable block: ublk: move ublk_chr_class destroying after devices are removed Partially revert "perf/arm-cmn: Optimise DTC counter accesses" net: mdio-mux-meson-g12a: force internal PHY off on mux switch tsnep: Fix TX queue stop/wake for multiple queues net/tg3: resolve deadlock in tg3_reset_task() during EEH riscv: Move call to init_cpu_topology() to later initialization stage thermal: intel: int340x: Add locking to int340x_thermal_get_trip_type() net: mctp: mark socks as dead on unhash, prevent re-add net: mctp: hold key reference when looking up a general key net: mctp: move expiry timer delete to unhash net: mctp: add an explicit reference from a mctp_sk_key to sock net: ravb: Fix possible hang if RIS2_QFF1 happen net: ravb: Fix lack of register setting after system resumed for Gen3 gpio: ep93xx: Fix port F hwirq numbers in handler gpio: mxc: Unlock on error path in mxc_flip_edge() nvme: fix passthrough csi check riscv/kprobe: Fix instruction simulation of JALR sctp: fail if no bound addresses can be used for a given scope net/sched: sch_taprio: do not schedule in taprio_reset() tracing/osnoise: Use built-in RCU list checking ACPI: video: Fix apple gmux detection platform/x86: apple-gmux: Add apple_gmux_detect() helper platform/x86: apple-gmux: Move port defines to apple-gmux.h platform/x86: asus-wmi: Fix kbd_dock_devid tablet-switch reporting netrom: Fix use-after-free of a listening socket. netfilter: conntrack: fix vtag checks for ABORT/SHUTDOWN_COMPLETE net: ethernet: adi: adin1110: Fix multicast offloading net: dsa: microchip: fix probe of I2C-connected KSZ8563 ipv4: prevent potential spectre v1 gadget in fib_metrics_match() ipv4: prevent potential spectre v1 gadget in ip_metrics_convert() netlink: annotate data races around sk_state netlink: annotate data races around dst_portid and dst_group netlink: annotate data races around nlk->portid netfilter: nft_set_rbtree: skip elements in transaction from garbage collection netfilter: nft_set_rbtree: Switch to node list walk for overlap detection ACPI: video: Add backlight=native DMI quirk for Asus U46E ACPI: video: Add backlight=native DMI quirk for HP EliteBook 8460p ACPI: video: Add backlight=native DMI quirk for HP Pavilion g6-1d80nr drm/i915/selftest: fix intel_selftest_modify_policy argument types nvme-fc: fix initialization order nvme: consolidate setting the tagset flags nvme: simplify transport specific device attribute handling net: fec: Use page_pool_put_full_page when freeing rx buffers net: fix UaF in netns ops registration error path netlink: prevent potential spectre v1 gadgets iavf: schedule watchdog immediately when changing primary MAC iavf: fix temporary deadlock and failure to set MAC address drm/i915: Fix a memory leak with reused mmap_offset drm/drm_vma_manager: Add drm_vma_node_allow_once() i2c: designware: Fix unbalanced suspended flag i2c: designware: use casting of u64 in clock multiplication to avoid overflow io_uring: always prep_async for drain requests net: mana: Fix IR
[Kernel-packages] [Bug 2007668] Re: Intel 12th gen: Noisy screen corruption during some cursor movement in 5.19 kernels
** Also affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-5.19 (Ubuntu) Status: New => Confirmed ** Changed in: linux-hwe-5.19 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007668 Title: Intel 12th gen: Noisy screen corruption during some cursor movement in 5.19 kernels Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: This always happens when the cursor sweeps over a height range (approximately 960px ~ 990px from the top). Even when watching a video, the top of the screen sometimes glitches. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 17 16:24:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:46aa] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b14] InstallationDate: Installed on 2022-08-13 (187 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=3ba28059-7aea-46a5-bf4e-44dd0203b83d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 02GGG1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn02GGG1:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007668/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
Just encountered this bug - my computer was flat out spamming the console with this error caused by VLC borking after resume Ubuntu 22.04.2 LTS using nvidia 515 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: New Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Bug description: To replicate: 1. Start a video playing, for example in vlc. 'avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 418.56 Fri Mar 15 12:31:51 CDT 2019 for hardware decoding' 2. Optionally pause it. 3. Switch to another user. The original user's ~/.xsession-errors will rapidly fill up with errors along the lines of "vdpau_chroma filter error". At the same time, errors are put in /var/log/syslog as well: [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. (repeat ad nauseum) At least one of the two will rapidly fill up its partition and problems will arise. With AMD video hardware and driver, the video continues playing - you can hear the sound despite being in the other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
