Re: [Kernel-packages] [Bug 1936678] [NEW] Samsung Laptop support module doesn't load
-- 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/1936678 Title: Samsung Laptop support module doesn't load Status in linux package in Ubuntu: Won't Fix Bug description: This is identical to bug # 1170885, which was filed 2013-04-20. The last comment on that bug was by Kai-Heng Feng (kaihengfeng), who requested a new bug report. This is a Samsung laptop NP730QCJ. $ sudo modprobe samsung-laptop modprobe: ERROR: could not insert 'samsung_laptop': No such device About my system: $ sudo dmidecode | grep -A 2 -i 'base board' Base Board Information Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: NP730QCJ-K01US $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS" $ cat /proc/version_signature Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 $ file /sys/firmware/efi/ /sys/firmware/efi/: directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059951] [NEW] mlxbf_gige: stop interface during shutdown
Public bug reported: SRU Justification: [Impact] The mlxbf_gige driver shutdown() is invoked during reboot processing, but the stop() logic is not guaranteed to execute on all distros. If stop() does not execute NAPI remains enabled during system shutdown and can cause an exception if NAPI is scheduled when interface is shutdown but not stopped. [Fix] The networking interface managed by the mlxbf_gige driver must be stopped during reboot processing so that it is put into a clean state and driver callbacks won't be called. [Test Case] * Put BF platform into a reboot loop * Ensure that BF platform brings up "oob_net0" interface each reboot, and that no mlxbf_gige driver exceptions occur [Regression Potential] There is low potential for regression as this brings in upstream content. [Other] None ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2059951 Title: mlxbf_gige: stop interface during shutdown Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] The mlxbf_gige driver shutdown() is invoked during reboot processing, but the stop() logic is not guaranteed to execute on all distros. If stop() does not execute NAPI remains enabled during system shutdown and can cause an exception if NAPI is scheduled when interface is shutdown but not stopped. [Fix] The networking interface managed by the mlxbf_gige driver must be stopped during reboot processing so that it is put into a clean state and driver callbacks won't be called. [Test Case] * Put BF platform into a reboot loop * Ensure that BF platform brings up "oob_net0" interface each reboot, and that no mlxbf_gige driver exceptions occur [Regression Potential] There is low potential for regression as this brings in upstream content. [Other] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2059951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059310] [NEW] mlxbf_gige: call request_irq() after NAPI initialized
Public bug reported: SRU Justification: [Impact] The mlxbf_gige driver encounters a NULL pointer exception in mlxbf_gige_open() when kdump is enabled. The exception happens because there is a pending RX interrupt before the call to request_irq(RX IRQ) executes. Then, the RX IRQ handler fires immediately after this request_irq() completes. The RX IRQ handler runs "napi_schedule()" before NAPI is fully initialized via "netif_napi_add()" and "napi_enable()", both which happen later in the open() logic. [Fix] The logic in mlxbf_gige_open() must fully initialize NAPI before any calls to request_irq() execute. [Test Case] * Boot BF platform and bring up "oob_net0" interface * Enable kdump completely * Trigger kdump via "echo c > /proc/sysrq-trigger" * There should be no exceptions from mlxbf_gige driver [Regression Potential] There is low potential for regression as this brings in upstream content. [Other] None ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2059310 Title: mlxbf_gige: call request_irq() after NAPI initialized Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] The mlxbf_gige driver encounters a NULL pointer exception in mlxbf_gige_open() when kdump is enabled. The exception happens because there is a pending RX interrupt before the call to request_irq(RX IRQ) executes. Then, the RX IRQ handler fires immediately after this request_irq() completes. The RX IRQ handler runs "napi_schedule()" before NAPI is fully initialized via "netif_napi_add()" and "napi_enable()", both which happen later in the open() logic. [Fix] The logic in mlxbf_gige_open() must fully initialize NAPI before any calls to request_irq() execute. [Test Case] * Boot BF platform and bring up "oob_net0" interface * Enable kdump completely * Trigger kdump via "echo c > /proc/sysrq-trigger" * There should be no exceptions from mlxbf_gige driver [Regression Potential] There is low potential for regression as this brings in upstream content. [Other] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2059310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059279] [NEW] mlxbf_gige: replace SAUCE patch for pause frame counters
Public bug reported: SRU Justification: [Impact] The support for mlxbf_gige pause frame counters was added to Jammy via a SAUCE patch. After upstream review, a small issue was fixed that makes the SAUCE patch different from the upstream commit. [Fix] The fix is to replace the SAUCE patch in the Jammy repo with the upstream equivalent. [Test Case] * Boot BF platform and bring up "oob_net0" interface * Execute the command "ethtool -I -a oob_net0" to get baseline stats * Send heavy traffic into "oob_net0" interface * Re-run the above ethtool command, noting the pause frame counters [Regression Potential] There is low potential for regression as this brings in upstream content. [Other] None ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2059279 Title: mlxbf_gige: replace SAUCE patch for pause frame counters Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] The support for mlxbf_gige pause frame counters was added to Jammy via a SAUCE patch. After upstream review, a small issue was fixed that makes the SAUCE patch different from the upstream commit. [Fix] The fix is to replace the SAUCE patch in the Jammy repo with the upstream equivalent. [Test Case] * Boot BF platform and bring up "oob_net0" interface * Execute the command "ethtool -I -a oob_net0" to get baseline stats * Send heavy traffic into "oob_net0" interface * Re-run the above ethtool command, noting the pause frame counters [Regression Potential] There is low potential for regression as this brings in upstream content. [Other] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2059279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055086] [NEW] mlxbf_gige: add support for pause frame counters
Public bug reported: SRU Justification: [Impact] The BlueField-2 and BlueField-3 silicon designs include a provision for reporting pause frame counters, but the driver (mlxbf_gige) does not have software support yet. [Fix] The fix is to update the mlxbf_gige driver to support the "get_pause_stats()" callback, which enables display of pause frame counters via "ethtool -I -a ooob_net0". The support of this callback was added to Linux kernel 5.9.0 [Test Case] * Reboot BF platform, and configure oob_net0 interface * Issue command "ethtool -I -a oob_net0" to display pause frame counters * Send in multiple streams of traffic to oob_net0 interface, e.g. from two or three simultaneous SCP operations * Re-issue "ethtool -I -a oob_net0" and note difference in output [Regression Potential] The changed logic extends the ethtool support, so low risk for any problem. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2055086 Title: mlxbf_gige: add support for pause frame counters Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] The BlueField-2 and BlueField-3 silicon designs include a provision for reporting pause frame counters, but the driver (mlxbf_gige) does not have software support yet. [Fix] The fix is to update the mlxbf_gige driver to support the "get_pause_stats()" callback, which enables display of pause frame counters via "ethtool -I -a ooob_net0". The support of this callback was added to Linux kernel 5.9.0 [Test Case] * Reboot BF platform, and configure oob_net0 interface * Issue command "ethtool -I -a oob_net0" to display pause frame counters * Send in multiple streams of traffic to oob_net0 interface, e.g. from two or three simultaneous SCP operations * Re-issue "ethtool -I -a oob_net0" and note difference in output [Regression Potential] The changed logic extends the ethtool support, so low risk for any problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2055086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054899] [NEW] package linux-headers-6.5.0-21-generic 6.5.0-21.21 failed to install/upgrade: installed linux-headers-6.5.0-21-generic package post-installation script subprocess
Public bug reported:
This occurred installing updates.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-21-generic 6.5.0-21.21
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 2455 F wireplumber
/dev/snd/controlC1: david 2455 F wireplumber
/dev/snd/seq:david 2438 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sat Feb 24 16:31:10 2024
ErrorMessage: installed linux-headers-6.5.0-21-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2022-07-10 (594 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic
root=UUID=7992ce64-176b-4fba-8425-28f856008200 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: /usr/bin/python3.11, Python 3.11.6, python-is-python3, 3.11.4-1
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
SourcePackage: linux
Title: package linux-headers-6.5.0-21-generic 6.5.0-21.21 failed to
install/upgrade: installed linux-headers-6.5.0-21-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/09/2023
dmi.bios.release: 1.31
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.31.3
dmi.board.name: 0VK0WN
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.31.3:bd03/09/2023:br1.31:svnDellInc.:pnPrecision7710:pvr:rvnDellInc.:rn0VK0WN:rvrA01:cvnDellInc.:ct9:cvr:sku06DA:
dmi.product.family: Precision
dmi.product.name: Precision 7710
dmi.product.sku: 06DA
dmi.sys.vendor: Dell Inc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-package mantic
--
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/2054899
Title:
package linux-headers-6.5.0-21-generic 6.5.0-21.21 failed to
install/upgrade: installed linux-headers-6.5.0-21-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
New
Bug description:
This occurred installing updates.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-21-generic 6.5.0-21.21
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 2455 F wireplumber
/dev/snd/controlC1: david 2455 F wireplumber
/dev/snd/seq: david 2438 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sat Feb 24 16:31:10 2024
ErrorMessage: installed linux-headers-6.5.0-21-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2022-07-10 (594 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic
root=UUID=7992ce64-176b-4fba-8425-28f856008200 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: /usr/bin/python3.11, Python 3.11.6, python-is-python3, 3.11.4-1
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
SourcePackage: linux
Title: package linux-headers-6.5.0-21-generic 6.5.0-21.21 failed to
install/upgrade: installed linux-headers-6.5.0-21-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/09/2023
dmi.bios.release: 1.31
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.31.3
dmi.board.name: 0VK0WN
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.31.3:bd03/09/2023:br1.31:svnDellInc.:pnPrecision7710:pvr:rvnDellInc.:rn0VK0WN:rvrA01:cvnDellInc.:ct9:cvr:sku06DA:
dmi.product.family: Precision
dmi.product.name: Precision 7710
dmi.product.sku: 06DA
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054899/+subscriptions
--
Mailing list: https://launchpad.net/~
[Kernel-packages] [Bug 2049938] Re: Bang & Olufsen Cisco 980 loses connection on 6.5 generic kernel
Dmesg log from OEM kernel ** Attachment added: "dmesg_out" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049938/+attachment/5748485/+files/dmesg_out -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049938 Title: Bang & Olufsen Cisco 980 loses connection on 6.5 generic kernel Status in linux package in Ubuntu: New Bug description: When you connect the headset which is based on Bluetooth LE it connects and then almost immediately disconnects. This does not happen when using the 6.5.0-1009-oem kernel Can you poirt whatever changes to bluetooth from the oem kernel to the generic as the cutomer will not use the oem kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049938] Re: Bang & Olufsen Cisco 980 loses connection on 6.5 generic kernel
lsusb output ** Attachment added: "lsusb_out" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049938/+attachment/5748486/+files/lsusb_out -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049938 Title: Bang & Olufsen Cisco 980 loses connection on 6.5 generic kernel Status in linux package in Ubuntu: New Bug description: When you connect the headset which is based on Bluetooth LE it connects and then almost immediately disconnects. This does not happen when using the 6.5.0-1009-oem kernel Can you poirt whatever changes to bluetooth from the oem kernel to the generic as the cutomer will not use the oem kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049938] [NEW] Bang & Olufsen Cisco 980 loses connection on 6.5 generic kernel
Public bug reported: When you connect the headset which is based on Bluetooth LE it connects and then almost immediately disconnects. This does not happen when using the 6.5.0-1009-oem kernel Can you poirt whatever changes to bluetooth from the oem kernel to the generic as the cutomer will not use the oem 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/2049938 Title: Bang & Olufsen Cisco 980 loses connection on 6.5 generic kernel Status in linux package in Ubuntu: New Bug description: When you connect the headset which is based on Bluetooth LE it connects and then almost immediately disconnects. This does not happen when using the 6.5.0-1009-oem kernel Can you poirt whatever changes to bluetooth from the oem kernel to the generic as the cutomer will not use the oem kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049930] [NEW] mlxbf_gige: disable RX_DMA during NAPI poll
Public bug reported: SRU Justification: [Impact] A regression has been introduced in the latest 22.04 kernel by including the following two commits: revert "UBUNTU: SAUCE: Fix OOB handling RX packets in heavy traffic" addition of upstream "mlxbf_gige: fix receive packet race condition" The regression will manifest as connectivity problems on "oob_net0" interface [Fix] Modify the GIGE driver to include the RX_DMA disable logic in its NAPI poll routine This logic was part of "UBUNTU: SAUCE: Fix OOB handling RX packets in heavy traffic" but not part of upstream "mlxbf_gige: fix receive packet race condition" [Test Case] Boot BF3 platform and ensure oob_net0 interface is up and has IP address Bring up many IP interfaces, including oob_net0, and make sure OOB interface is continually accessible (e.g. via ping) [Regression Potential] Low risk change, adding back in prior logic. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2049930 Title: mlxbf_gige: disable RX_DMA during NAPI poll Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] A regression has been introduced in the latest 22.04 kernel by including the following two commits: revert "UBUNTU: SAUCE: Fix OOB handling RX packets in heavy traffic" addition of upstream "mlxbf_gige: fix receive packet race condition" The regression will manifest as connectivity problems on "oob_net0" interface [Fix] Modify the GIGE driver to include the RX_DMA disable logic in its NAPI poll routine This logic was part of "UBUNTU: SAUCE: Fix OOB handling RX packets in heavy traffic" but not part of upstream "mlxbf_gige: fix receive packet race condition" [Test Case] Boot BF3 platform and ensure oob_net0 interface is up and has IP address Bring up many IP interfaces, including oob_net0, and make sure OOB interface is continually accessible (e.g. via ping) [Regression Potential] Low risk change, adding back in prior logic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2049930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047853] [NEW] mlxbf_gige: replace SAUCE patch for RX race condition
Public bug reported: SRU Justification: [Impact] There is a SAUCE patch that addresses a mlxbf-gige RX race condition "UBUNTU: SAUCE: Fix OOB handling RX packets in heavy traffic" This SAUCE patch should be reverted and replaced with upstream content. [Fix] Bring in the following upstream commit from linux-next: "mlxbf_gige: fix receive packet race condition" [Test Case] Boot BF3 platform and ensure oob_net0 interface is up and has IP address Send heavy level of traffic into the BF3 oob_net0 and make sure no stalls occur [Regression Potential] Low risk change, cherry pick of upstream approved commit ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2047853 Title: mlxbf_gige: replace SAUCE patch for RX race condition Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] There is a SAUCE patch that addresses a mlxbf-gige RX race condition "UBUNTU: SAUCE: Fix OOB handling RX packets in heavy traffic" This SAUCE patch should be reverted and replaced with upstream content. [Fix] Bring in the following upstream commit from linux-next: "mlxbf_gige: fix receive packet race condition" [Test Case] Boot BF3 platform and ensure oob_net0 interface is up and has IP address Send heavy level of traffic into the BF3 oob_net0 and make sure no stalls occur [Regression Potential] Low risk change, cherry pick of upstream approved commit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2047853/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045919] [NEW] mlxbf-bootctl: fails to report info about cards using dev keys
Public bug reported: SRU Justification: [Impact] There is a gap in the mlxbf-bootctl driver logic, resulting in failure to report when a secure boot enabled card is using development keys. The program will instead report lifecycle state as "GA Secured" which is misleading. [Fix] Bring in the following upstream commit from linux-next: "mlxbf-bootctl: correctly identify secure boot with development keys" [Test Case] Enable secure boot on a BF3 card that is using development keys Login as root on BF3 Run the command "mlxbf-bootctl" Verify that the "lifecycle state" row shows "Secured (development)" [Regression Potential] Low risk change, cherry pick of upstream approved commit ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2045919 Title: mlxbf-bootctl: fails to report info about cards using dev keys Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] There is a gap in the mlxbf-bootctl driver logic, resulting in failure to report when a secure boot enabled card is using development keys. The program will instead report lifecycle state as "GA Secured" which is misleading. [Fix] Bring in the following upstream commit from linux-next: "mlxbf-bootctl: correctly identify secure boot with development keys" [Test Case] Enable secure boot on a BF3 card that is using development keys Login as root on BF3 Run the command "mlxbf-bootctl" Verify that the "lifecycle state" row shows "Secured (development)" [Regression Potential] Low risk change, cherry pick of upstream approved commit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2045919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042075] Re: Black screen at login after updating to this kernel
I assume you mean to run this journalctl -k > journal_good.txt from the working journal? -- 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/2042075 Title: Black screen at login after updating to this kernel Status in linux package in Ubuntu: Incomplete Bug description: Dell Inspiron AMD A10 Laptop Linux Mint Mate O/S After updating the kernel I restarted the laptop. After entering my password and logging in the screen goes black with occasional flashes of, I guess i'd call it static. The same thing happened with the previous kernel I installed, ending .87, when I was running Zorin OS. After un-installing the system returns to opening as usual. System: Kernel: 5.15.0-76-generic x86_64 bits (This is the kernel that is working correctly): 64 compiler: gcc v: 11.3.0 Desktop: MATE 1.26.0 wm: marco dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy Machine: Type: Portable System: Dell product: Inspiron v: A12 serial: Chassis: type: 8 v: A12 serial: Mobo: Dell model: 0CX84K v: A00 serial: UEFI: Dell v: A12 date: 08/30/2016 CPU: Info: quad core model: AMD A10-8700P Radeon R6 10 Compute Cores 4C+6G bits: 64 type: MT MCP arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB Speed (MHz): avg: 2776 high: 3053 min/max: 1300/1800 boost: enabled cores: 1: 2673 2: 2680 3: 3053 4: 2700 bogomips: 14374 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Dell driver: amdgpu v: kernel ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:9874 Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 M430 Radeon 520 Mobile] vendor: Dell driver: radeon v: kernel pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 03:00.0 chip-ID: 1002:6660 Device-3: Microdia Integrated Webcam HD type: USB driver: uvcvideo bus-ID: 2-4:3 chip-ID: 0c45:6712 Display: x11 server: X.Org v: 1.21.1.4 compositor: marco v: 1.26.0 driver: X: loaded: ati,radeon unloaded: amdgpu,fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 1366x768 s-dpi: 96 Monitor-1: eDP res: 1366x768 dpi: 112 diag: 354mm (13.9") OpenGL: renderer: AMD Radeon R6 Graphics (carrizo LLVM 15.0.7 DRM 3.42 5.15.0-76-generic) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes I don't have a lot of experience with reporting errors so I hope this helps! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042075] Re: Black screen at login after updating to this kernel
** Attachment added: "journal_good.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042075/+attachment/5716723/+files/journal_good.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042075 Title: Black screen at login after updating to this kernel Status in linux package in Ubuntu: Incomplete Bug description: Dell Inspiron AMD A10 Laptop Linux Mint Mate O/S After updating the kernel I restarted the laptop. After entering my password and logging in the screen goes black with occasional flashes of, I guess i'd call it static. The same thing happened with the previous kernel I installed, ending .87, when I was running Zorin OS. After un-installing the system returns to opening as usual. System: Kernel: 5.15.0-76-generic x86_64 bits (This is the kernel that is working correctly): 64 compiler: gcc v: 11.3.0 Desktop: MATE 1.26.0 wm: marco dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy Machine: Type: Portable System: Dell product: Inspiron v: A12 serial: Chassis: type: 8 v: A12 serial: Mobo: Dell model: 0CX84K v: A00 serial: UEFI: Dell v: A12 date: 08/30/2016 CPU: Info: quad core model: AMD A10-8700P Radeon R6 10 Compute Cores 4C+6G bits: 64 type: MT MCP arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB Speed (MHz): avg: 2776 high: 3053 min/max: 1300/1800 boost: enabled cores: 1: 2673 2: 2680 3: 3053 4: 2700 bogomips: 14374 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Dell driver: amdgpu v: kernel ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:9874 Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 M430 Radeon 520 Mobile] vendor: Dell driver: radeon v: kernel pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 03:00.0 chip-ID: 1002:6660 Device-3: Microdia Integrated Webcam HD type: USB driver: uvcvideo bus-ID: 2-4:3 chip-ID: 0c45:6712 Display: x11 server: X.Org v: 1.21.1.4 compositor: marco v: 1.26.0 driver: X: loaded: ati,radeon unloaded: amdgpu,fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 1366x768 s-dpi: 96 Monitor-1: eDP res: 1366x768 dpi: 112 diag: 354mm (13.9") OpenGL: renderer: AMD Radeon R6 Graphics (carrizo LLVM 15.0.7 DRM 3.42 5.15.0-76-generic) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes I don't have a lot of experience with reporting errors so I hope this helps! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042075] Re: Black screen at login after updating to this kernel
Hope these help! ** Attachment added: "journal_good.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042075/+attachment/5716137/+files/journal_good.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042075 Title: Black screen at login after updating to this kernel Status in linux package in Ubuntu: Incomplete Bug description: Dell Inspiron AMD A10 Laptop Linux Mint Mate O/S After updating the kernel I restarted the laptop. After entering my password and logging in the screen goes black with occasional flashes of, I guess i'd call it static. The same thing happened with the previous kernel I installed, ending .87, when I was running Zorin OS. After un-installing the system returns to opening as usual. System: Kernel: 5.15.0-76-generic x86_64 bits (This is the kernel that is working correctly): 64 compiler: gcc v: 11.3.0 Desktop: MATE 1.26.0 wm: marco dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy Machine: Type: Portable System: Dell product: Inspiron v: A12 serial: Chassis: type: 8 v: A12 serial: Mobo: Dell model: 0CX84K v: A00 serial: UEFI: Dell v: A12 date: 08/30/2016 CPU: Info: quad core model: AMD A10-8700P Radeon R6 10 Compute Cores 4C+6G bits: 64 type: MT MCP arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB Speed (MHz): avg: 2776 high: 3053 min/max: 1300/1800 boost: enabled cores: 1: 2673 2: 2680 3: 3053 4: 2700 bogomips: 14374 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Dell driver: amdgpu v: kernel ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:9874 Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 M430 Radeon 520 Mobile] vendor: Dell driver: radeon v: kernel pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 03:00.0 chip-ID: 1002:6660 Device-3: Microdia Integrated Webcam HD type: USB driver: uvcvideo bus-ID: 2-4:3 chip-ID: 0c45:6712 Display: x11 server: X.Org v: 1.21.1.4 compositor: marco v: 1.26.0 driver: X: loaded: ati,radeon unloaded: amdgpu,fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 1366x768 s-dpi: 96 Monitor-1: eDP res: 1366x768 dpi: 112 diag: 354mm (13.9") OpenGL: renderer: AMD Radeon R6 Graphics (carrizo LLVM 15.0.7 DRM 3.42 5.15.0-76-generic) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes I don't have a lot of experience with reporting errors so I hope this helps! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042075] Re: Black screen at login after updating to this kernel
** Attachment added: "journal_bad.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042075/+attachment/5716136/+files/journal_bad.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042075 Title: Black screen at login after updating to this kernel Status in linux package in Ubuntu: Incomplete Bug description: Dell Inspiron AMD A10 Laptop Linux Mint Mate O/S After updating the kernel I restarted the laptop. After entering my password and logging in the screen goes black with occasional flashes of, I guess i'd call it static. The same thing happened with the previous kernel I installed, ending .87, when I was running Zorin OS. After un-installing the system returns to opening as usual. System: Kernel: 5.15.0-76-generic x86_64 bits (This is the kernel that is working correctly): 64 compiler: gcc v: 11.3.0 Desktop: MATE 1.26.0 wm: marco dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy Machine: Type: Portable System: Dell product: Inspiron v: A12 serial: Chassis: type: 8 v: A12 serial: Mobo: Dell model: 0CX84K v: A00 serial: UEFI: Dell v: A12 date: 08/30/2016 CPU: Info: quad core model: AMD A10-8700P Radeon R6 10 Compute Cores 4C+6G bits: 64 type: MT MCP arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB Speed (MHz): avg: 2776 high: 3053 min/max: 1300/1800 boost: enabled cores: 1: 2673 2: 2680 3: 3053 4: 2700 bogomips: 14374 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Dell driver: amdgpu v: kernel ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:9874 Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 M430 Radeon 520 Mobile] vendor: Dell driver: radeon v: kernel pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 03:00.0 chip-ID: 1002:6660 Device-3: Microdia Integrated Webcam HD type: USB driver: uvcvideo bus-ID: 2-4:3 chip-ID: 0c45:6712 Display: x11 server: X.Org v: 1.21.1.4 compositor: marco v: 1.26.0 driver: X: loaded: ati,radeon unloaded: amdgpu,fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 1366x768 s-dpi: 96 Monitor-1: eDP res: 1366x768 dpi: 112 diag: 354mm (13.9") OpenGL: renderer: AMD Radeon R6 Graphics (carrizo LLVM 15.0.7 DRM 3.42 5.15.0-76-generic) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes I don't have a lot of experience with reporting errors so I hope this helps! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042075] [NEW] Black screen at login after updating to this kernel
Public bug reported: Dell Inspiron AMD A10 Laptop Linux Mint Mate O/S After updating the kernel I restarted the laptop. After entering my password and logging in the screen goes black with occasional flashes of, I guess i'd call it static. The same thing happened with the previous kernel I installed, ending .87, when I was running Zorin OS. After un-installing the system returns to opening as usual. System: Kernel: 5.15.0-76-generic x86_64 bits (This is the kernel that is working correctly): 64 compiler: gcc v: 11.3.0 Desktop: MATE 1.26.0 wm: marco dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy Machine: Type: Portable System: Dell product: Inspiron v: A12 serial: Chassis: type: 8 v: A12 serial: Mobo: Dell model: 0CX84K v: A00 serial: UEFI: Dell v: A12 date: 08/30/2016 CPU: Info: quad core model: AMD A10-8700P Radeon R6 10 Compute Cores 4C+6G bits: 64 type: MT MCP arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB Speed (MHz): avg: 2776 high: 3053 min/max: 1300/1800 boost: enabled cores: 1: 2673 2: 2680 3: 3053 4: 2700 bogomips: 14374 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Dell driver: amdgpu v: kernel ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:9874 Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 M430 Radeon 520 Mobile] vendor: Dell driver: radeon v: kernel pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 03:00.0 chip-ID: 1002:6660 Device-3: Microdia Integrated Webcam HD type: USB driver: uvcvideo bus-ID: 2-4:3 chip-ID: 0c45:6712 Display: x11 server: X.Org v: 1.21.1.4 compositor: marco v: 1.26.0 driver: X: loaded: ati,radeon unloaded: amdgpu,fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 1366x768 s-dpi: 96 Monitor-1: eDP res: 1366x768 dpi: 112 diag: 354mm (13.9") OpenGL: renderer: AMD Radeon R6 Graphics (carrizo LLVM 15.0.7 DRM 3.42 5.15.0-76-generic) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes I don't have a lot of experience with reporting errors so I hope this helps! ** 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/2042075 Title: Black screen at login after updating to this kernel Status in linux package in Ubuntu: New Bug description: Dell Inspiron AMD A10 Laptop Linux Mint Mate O/S After updating the kernel I restarted the laptop. After entering my password and logging in the screen goes black with occasional flashes of, I guess i'd call it static. The same thing happened with the previous kernel I installed, ending .87, when I was running Zorin OS. After un-installing the system returns to opening as usual. System: Kernel: 5.15.0-76-generic x86_64 bits (This is the kernel that is working correctly): 64 compiler: gcc v: 11.3.0 Desktop: MATE 1.26.0 wm: marco dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy Machine: Type: Portable System: Dell product: Inspiron v: A12 serial: Chassis: type: 8 v: A12 serial: Mobo: Dell model: 0CX84K v: A00 serial: UEFI: Dell v: A12 date: 08/30/2016 CPU: Info: quad core model: AMD A10-8700P Radeon R6 10 Compute Cores 4C+6G bits: 64 type: MT MCP arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB Speed (MHz): avg: 2776 high: 3053 min/max: 1300/1800 boost: enabled cores: 1: 2673 2: 2680 3: 3053 4: 2700 bogomips: 14374 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Dell driver: amdgpu v: kernel ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:9874 Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 M430 Radeon 520 Mobile] vendor: Dell driver: radeon v: kernel pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 03:00.0 chip-ID: 1002:6660 Device-3: Microdia Integrated Webcam HD type: USB driver: uvcvideo bus-ID: 2-4:3 chip-ID: 0c45:6712 Display: x11 server: X.Org v: 1.21.1.4 compositor: marco v: 1.26.0 driver: X: loaded: ati,radeon unloaded: amdgpu,fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 1366x768 s-dpi: 96 Monitor-1: eDP res: 1366x768 dpi: 112 diag: 354mm (13.9") OpenGL: renderer: AMD Radeon R6 Graphics (carrizo LLVM 15.0.7 DRM 3.42 5.15.0-76-generic) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes I don't have a lot of experience with reporting errors so I hope this helps! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 2042075] Re: Black screen at login after updating to this kernel
Just in case I should add the kernels that caused the problem for my laptop are Linux kernel 5.15.0-88.98, and 5.15.0-87 -- 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/2042075 Title: Black screen at login after updating to this kernel Status in linux package in Ubuntu: New Bug description: Dell Inspiron AMD A10 Laptop Linux Mint Mate O/S After updating the kernel I restarted the laptop. After entering my password and logging in the screen goes black with occasional flashes of, I guess i'd call it static. The same thing happened with the previous kernel I installed, ending .87, when I was running Zorin OS. After un-installing the system returns to opening as usual. System: Kernel: 5.15.0-76-generic x86_64 bits (This is the kernel that is working correctly): 64 compiler: gcc v: 11.3.0 Desktop: MATE 1.26.0 wm: marco dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy Machine: Type: Portable System: Dell product: Inspiron v: A12 serial: Chassis: type: 8 v: A12 serial: Mobo: Dell model: 0CX84K v: A00 serial: UEFI: Dell v: A12 date: 08/30/2016 CPU: Info: quad core model: AMD A10-8700P Radeon R6 10 Compute Cores 4C+6G bits: 64 type: MT MCP arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB Speed (MHz): avg: 2776 high: 3053 min/max: 1300/1800 boost: enabled cores: 1: 2673 2: 2680 3: 3053 4: 2700 bogomips: 14374 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Dell driver: amdgpu v: kernel ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:9874 Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 M430 Radeon 520 Mobile] vendor: Dell driver: radeon v: kernel pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 03:00.0 chip-ID: 1002:6660 Device-3: Microdia Integrated Webcam HD type: USB driver: uvcvideo bus-ID: 2-4:3 chip-ID: 0c45:6712 Display: x11 server: X.Org v: 1.21.1.4 compositor: marco v: 1.26.0 driver: X: loaded: ati,radeon unloaded: amdgpu,fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 1366x768 s-dpi: 96 Monitor-1: eDP res: 1366x768 dpi: 112 diag: 354mm (13.9") OpenGL: renderer: AMD Radeon R6 Graphics (carrizo LLVM 15.0.7 DRM 3.42 5.15.0-76-generic) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes I don't have a lot of experience with reporting errors so I hope this helps! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland
I'm experiencing the same issue as well.
I'm using an Asus TUF A15 with an RTX 4050.
Gnome crashes when using multiple screens with Firefox and the file
explorer.
One tip is to debug 'the frozen screen' by changing the screen order in
Settings > Display.
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/2038998
Title:
[amdgpu] Screen artifacts/UI oddities on Wayland
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM
Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.
Wayland
Kernel 6.5.0-9-generic
* * * * *
Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.
Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
compatible titles.
Screen corruption (white and grey streaks) present in-game when GNOME
UI elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.
Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.
Artifacts only appeared in Wayland session; not X11/Xorg.
I previously had been running the same games on Ubuntu 22.04 LTS
(GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
computer without issue (kernel 6.2).
* * * * *
Please see subsequent posts for video/images.
Happy to provide any other information as needed. Thanks!
* * * * *
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:509b]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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/2038998/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035135] Re: Oracle Cloud systems not getting Jammy kernel updates
** Changed in: linux-meta-oracle (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2035135 Title: Oracle Cloud systems not getting Jammy kernel updates Status in linux-meta-oracle package in Ubuntu: Fix Released Bug description: (Please forgive my ignorance of the kernel release process, maybe I've gotten this all wrong.) There have been several kernel releases for Jammy lately but the two systems I have on Oracle Cloud (one amd64 and one arm64) have not been receiving updates since kernel 5.15.0-1040. It looks like the linux- oracle package is no longer getting updated? Were we supposed to change to a new package called linux-oracle-lts-22.04? lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 apt-cache policy linux-oracle linux-oracle: Installed: 5.15.0.1040.35 Candidate: 5.15.0.1040.35 Version table: *** 5.15.0.1040.35 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.1002.2 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy/main amd64 Packages apt-cache policy linux-oracle-lts-22.04 linux-oracle-lts-22.04: Installed: (none) Candidate: 5.15.0.1042.37 Version table: 5.15.0.1042.37 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oracle/+bug/2035135/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035135] Re: Oracle Cloud systems not getting Jammy kernel updates
This appears to have been resolved as of 5.15.0.1044.39: apt-cache policy linux-oracle linux-oracle: Installed: 5.15.0.1044.39 Candidate: 5.15.0.1044.39 Version table: *** 5.15.0.1044.39 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.1040.35 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 5.15.0.1002.2 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy/main amd64 Packages Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2035135 Title: Oracle Cloud systems not getting Jammy kernel updates Status in linux-meta-oracle package in Ubuntu: Confirmed Bug description: (Please forgive my ignorance of the kernel release process, maybe I've gotten this all wrong.) There have been several kernel releases for Jammy lately but the two systems I have on Oracle Cloud (one amd64 and one arm64) have not been receiving updates since kernel 5.15.0-1040. It looks like the linux- oracle package is no longer getting updated? Were we supposed to change to a new package called linux-oracle-lts-22.04? lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 apt-cache policy linux-oracle linux-oracle: Installed: 5.15.0.1040.35 Candidate: 5.15.0.1040.35 Version table: *** 5.15.0.1040.35 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.1002.2 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy/main amd64 Packages apt-cache policy linux-oracle-lts-22.04 linux-oracle-lts-22.04: Installed: (none) Candidate: 5.15.0.1042.37 Version table: 5.15.0.1042.37 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oracle/+bug/2035135/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035374] [NEW] pwr-mlxbf: update Kconfig with upstream changes
Public bug reported: SRU Justification: [Impact] The Mellanox BlueField power driver (pwr-mlxbf) has a dependency on either the BlueField-2 or BlueField-3 GPIO driver. The current Kconfig does not have the BlueField-3 dependency. [Fix] There is an upstream commit that extends the Kconfig to include the GPIO_MLXBF3 dependency. [Test Case] Build the power driver with and without GPIO_MLXBF2 and GPIO_MLXBF3 present in the kernel configuration. Verify power driver is built. [Regression Potential] * none [Other] * none ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2035374 Title: pwr-mlxbf: update Kconfig with upstream changes Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] The Mellanox BlueField power driver (pwr-mlxbf) has a dependency on either the BlueField-2 or BlueField-3 GPIO driver. The current Kconfig does not have the BlueField-3 dependency. [Fix] There is an upstream commit that extends the Kconfig to include the GPIO_MLXBF3 dependency. [Test Case] Build the power driver with and without GPIO_MLXBF2 and GPIO_MLXBF3 present in the kernel configuration. Verify power driver is built. [Regression Potential] * none [Other] * none To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2035374/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035135] [NEW] Oracle Cloud systems not getting Jammy kernel updates
Public bug reported: (Please forgive my ignorance of the kernel release process, maybe I've gotten this all wrong.) There have been several kernel releases for Jammy lately but the two systems I have on Oracle Cloud (one amd64 and one arm64) have not been receiving updates since kernel 5.15.0-1040. It looks like the linux- oracle package is no longer getting updated? Were we supposed to change to a new package called linux-oracle-lts-22.04? lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 apt-cache policy linux-oracle linux-oracle: Installed: 5.15.0.1040.35 Candidate: 5.15.0.1040.35 Version table: *** 5.15.0.1040.35 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.1002.2 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy/main amd64 Packages apt-cache policy linux-oracle-lts-22.04 linux-oracle-lts-22.04: Installed: (none) Candidate: 5.15.0.1042.37 Version table: 5.15.0.1042.37 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages Thanks! ** Affects: linux-meta-oracle (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2035135 Title: Oracle Cloud systems not getting Jammy kernel updates Status in linux-meta-oracle package in Ubuntu: New Bug description: (Please forgive my ignorance of the kernel release process, maybe I've gotten this all wrong.) There have been several kernel releases for Jammy lately but the two systems I have on Oracle Cloud (one amd64 and one arm64) have not been receiving updates since kernel 5.15.0-1040. It looks like the linux- oracle package is no longer getting updated? Were we supposed to change to a new package called linux-oracle-lts-22.04? lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 apt-cache policy linux-oracle linux-oracle: Installed: 5.15.0.1040.35 Candidate: 5.15.0.1040.35 Version table: *** 5.15.0.1040.35 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.1002.2 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy/main amd64 Packages apt-cache policy linux-oracle-lts-22.04 linux-oracle-lts-22.04: Installed: (none) Candidate: 5.15.0.1042.37 Version table: 5.15.0.1042.37 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oracle/+bug/2035135/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035123] [NEW] scripts/pahole-flags.sh needs upstream fix
Public bug reported: When doing a kernel make in our Jammy repo we notice the follow error being emitted: ./scripts/pahole-flags.sh: line 7: return: can only `return' from a function or sourced script It appears that while the Jammy baseline is 5.15.99 (as per the top-level Makefile) the file scripts/pahole-flags.sh is out of date with upstream 5.15.99 The upstream 5.15.99 version of scripts/pahole-flags.sh fixes this issue by making this change: 7c7 < return --- > exit 0 This seems like a simple fix, but not sure who should be fixing this. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2035123 Title: scripts/pahole-flags.sh needs upstream fix Status in linux-bluefield package in Ubuntu: New Bug description: When doing a kernel make in our Jammy repo we notice the follow error being emitted: ./scripts/pahole-flags.sh: line 7: return: can only `return' from a function or sourced script It appears that while the Jammy baseline is 5.15.99 (as per the top-level Makefile) the file scripts/pahole-flags.sh is out of date with upstream 5.15.99 The upstream 5.15.99 version of scripts/pahole-flags.sh fixes this issue by making this change: 7c7 < return --- > exit 0 This seems like a simple fix, but not sure who should be fixing this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2035123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033551] [NEW] mlxbf_bootctl: replace SAUCE patches with upstream
Public bug reported: SRU Justification: [Impact] The mlxbf_bootctl BlueField platform driver in the Jammy repo consists of some SAUCE patches. These need to be replaced. [Fix] The fix is to revert the four SAUCE patches, replacing them with upstream commits for the same functionality. One patch for the mlxbf_bootctl driver is not yet upstreamed, so that patch will remain as SAUCE patch for now. [Test Case] * Boot BF2/BF3 platform, verify no new errors * Program MFG fields via "bfcfg" tool: 1) With current image, use 'bfcfg -d' to display current values 2) Reboot, stopping at UEFI menu, trigger 'Reset MFG Info' 3) With new image, use 'bfcfg' to push new or same MFG fields 4) Verify that the MFG fields are programmed properly via 'bfcfg -d' 5) Repeat process to replace proper MFG fields * Display BlueField boot log 1) cd /sys/bus/platform/devices/MLNXBF04:00 2) cat rsh_log 3) Should see boot log entries relevant to last boot [Regression Potential] The upstream commits are not exactly the same as the SAUCE patches, so technically there is a chance of regression, but its been well-tested and the functionality is the same. [Other] n/a ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2033551 Title: mlxbf_bootctl: replace SAUCE patches with upstream Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] The mlxbf_bootctl BlueField platform driver in the Jammy repo consists of some SAUCE patches. These need to be replaced. [Fix] The fix is to revert the four SAUCE patches, replacing them with upstream commits for the same functionality. One patch for the mlxbf_bootctl driver is not yet upstreamed, so that patch will remain as SAUCE patch for now. [Test Case] * Boot BF2/BF3 platform, verify no new errors * Program MFG fields via "bfcfg" tool: 1) With current image, use 'bfcfg -d' to display current values 2) Reboot, stopping at UEFI menu, trigger 'Reset MFG Info' 3) With new image, use 'bfcfg' to push new or same MFG fields 4) Verify that the MFG fields are programmed properly via 'bfcfg -d' 5) Repeat process to replace proper MFG fields * Display BlueField boot log 1) cd /sys/bus/platform/devices/MLNXBF04:00 2) cat rsh_log 3) Should see boot log entries relevant to last boot [Regression Potential] The upstream commits are not exactly the same as the SAUCE patches, so technically there is a chance of regression, but its been well-tested and the functionality is the same. [Other] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2033551/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026229] Re: Crashing issue with 5.15 kernel
@kleber-souza do you have any reference for which kind of bugs were resolved between 5.15.0-73-generic and 5.15.0-76.83 that might have addressed this? Our testing indicates that the newer kernel version is stable. It would be good to know what specifically caused this 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/2026229 Title: Crashing issue with 5.15 kernel Status in linux package in Ubuntu: New Bug description: We have been working on making self-hosted GitHub actions runners available in Canonical and have encountered an issue which seems to be with the kernel. The github-runner charm is a machine charm that runs on virtual machines. The charm creates a LXD virtual machine inside the juju unit/machine and runs the GitHub self-hosted runner application. The self-hosted runner can be used on GitHub to run GitHub Actions. The deployment of github-runner charm consists of about 15 units/machines (one unit per machine). In the past, we would see about one machine going into “down” state about every 1-3 days. From the openstack hosting the machine, it seems the machine has crashed. The syslog includes the following entry: Jun 8 21:15:58 juju-e4d256-prod-github-runner-66 kernel: [27199.579882] BUG: kernel NULL pointer dereference, address: 0008 The syslog: https://pastebin.canonical.com/p/gYy3Z9XGkN/ Log on openstack: https://pastebin.canonical.com/p/fbGcmQv9JW/ The deployment of the charm was on the jammy series (22.04). This series uses the Linux kernel 5.15. For the last week, the team has been experimenting with upgrading the kernel to the HWE version which is 5.19. Since then we have not encountered crashes in the virtual machine hosting the juju machine. This mattermost thread includes our team’s discussion of this issue and the reason we decide to upgrade the kernel: https://chat.canonical.com/canonical/pl/h8wrrmcnh3d17dtjmg56zf5pwy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027634] [NEW] package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Public bug reported: Not sure what caused this bug. The reporting dialog was on my screen when I unlocked the PC. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 4017 F wireplumber /dev/snd/controlC1: david 4017 F wireplumber /dev/snd/seq:david 4013 F pipewire CRDA: N/A CasperMD5CheckResult: unknown Date: Thu Jul 13 06:32:45 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2021-06-16 (756 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20VK001CAU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=6c94f9a7-6ba0-496d-abcc-72b4e2c82feb ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: dkms Title: package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: Upgraded to lunar on 2023-04-30 (73 days ago) dmi.bios.date: 04/26/2023 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: R1FET52W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20VK001CAU dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrR1FET52W(1.26):bd04/26/2023:br1.26:efr1.17:svnLENOVO:pn20VK001CAU:pvrThinkPadL13YogaGen2:rvnLENOVO:rn20VK001CAU:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20VK_BU_Think_FM_ThinkPadL13YogaGen2: dmi.product.family: ThinkPad L13 Yoga Gen 2 dmi.product.name: 20VK001CAU dmi.product.sku: LENOVO_MT_20VK_BU_Think_FM_ThinkPad L13 Yoga Gen 2 dmi.product.version: ThinkPad L13 Yoga Gen 2 dmi.sys.vendor: LENOVO ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2027634 Title: package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: New Bug description: Not sure what caused this bug. The reporting dialog was on my screen when I unlocked the PC. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 4017 F wireplumber /dev/snd/controlC1: david 4017 F wireplumber /dev/snd/seq: david 4013 F pipewire CRDA: N/A CasperMD5CheckResult: unknown Date: Thu Jul 13 06:32:45 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2021-06-16 (756 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20VK001CAU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=6c94f9a7-6ba0-496d-abcc-72b4e2c82feb ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: dkms Title: package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: Upgraded to lunar on 2023-04-30 (73 days ago) dmi.bios.date: 04/26/2023 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: R1FET52W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20VK001CAU dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrR1FET52W(1.26):bd04/26
[Kernel-packages] [Bug 2026229] Re: Crashing issue with 5.15 kernel
Thanks, we are trying out the jammy kernel to confirm it resolves the issue. Will report back -- 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/2026229 Title: Crashing issue with 5.15 kernel Status in linux package in Ubuntu: New Bug description: We have been working on making self-hosted GitHub actions runners available in Canonical and have encountered an issue which seems to be with the kernel. The github-runner charm is a machine charm that runs on virtual machines. The charm creates a LXD virtual machine inside the juju unit/machine and runs the GitHub self-hosted runner application. The self-hosted runner can be used on GitHub to run GitHub Actions. The deployment of github-runner charm consists of about 15 units/machines (one unit per machine). In the past, we would see about one machine going into “down” state about every 1-3 days. From the openstack hosting the machine, it seems the machine has crashed. The syslog includes the following entry: Jun 8 21:15:58 juju-e4d256-prod-github-runner-66 kernel: [27199.579882] BUG: kernel NULL pointer dereference, address: 0008 The syslog: https://pastebin.canonical.com/p/gYy3Z9XGkN/ Log on openstack: https://pastebin.canonical.com/p/fbGcmQv9JW/ The deployment of the charm was on the jammy series (22.04). This series uses the Linux kernel 5.15. For the last week, the team has been experimenting with upgrading the kernel to the HWE version which is 5.19. Since then we have not encountered crashes in the virtual machine hosting the juju machine. This mattermost thread includes our team’s discussion of this issue and the reason we decide to upgrade the kernel: https://chat.canonical.com/canonical/pl/h8wrrmcnh3d17dtjmg56zf5pwy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026229] Re: Crashing issue with 5.15 kernel
** Description changed: We have been working on making self-hosted GitHub actions runners available in Canonical and have encountered an issue which seems to be - with the kernel. This is a doc with more details: - https://docs.google.com/document/d/1E00rlT12Cu-h99do80Qge- - MKyQARFDY6hxSjhFFfPvA/edit?usp=sharing + with the kernel. + + The github-runner charm is a machine charm that runs on virtual + machines. The charm creates a LXD virtual machine inside the juju + unit/machine and runs the GitHub self-hosted runner application. The + self-hosted runner can be used on GitHub to run GitHub Actions. + + The deployment of github-runner charm consists of about 15 units/machines (one unit per machine). In the past, we would see about one machine going into “down” state about every 1-3 days. From the openstack hosting the machine, it seems the machine has crashed. The syslog includes the following entry: + Jun 8 21:15:58 juju-e4d256-prod-github-runner-66 kernel: [27199.579882] BUG: kernel NULL pointer dereference, address: 0008 + The syslog: https://pastebin.canonical.com/p/gYy3Z9XGkN/ + Log on openstack: https://pastebin.canonical.com/p/fbGcmQv9JW/ + The deployment of the charm was on the jammy series (22.04). This series uses the Linux kernel 5.15. + + For the last week, the team has been experimenting with upgrading the + kernel to the HWE version which is 5.19. Since then we have not + encountered crashes in the virtual machine hosting the juju machine. + + This mattermost thread includes our team’s discussion of this issue and the reason we decide to upgrade the kernel: + https://chat.canonical.com/canonical/pl/h8wrrmcnh3d17dtjmg56zf5pwy -- 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/2026229 Title: Crashing issue with 5.15 kernel Status in linux package in Ubuntu: New Bug description: We have been working on making self-hosted GitHub actions runners available in Canonical and have encountered an issue which seems to be with the kernel. The github-runner charm is a machine charm that runs on virtual machines. The charm creates a LXD virtual machine inside the juju unit/machine and runs the GitHub self-hosted runner application. The self-hosted runner can be used on GitHub to run GitHub Actions. The deployment of github-runner charm consists of about 15 units/machines (one unit per machine). In the past, we would see about one machine going into “down” state about every 1-3 days. From the openstack hosting the machine, it seems the machine has crashed. The syslog includes the following entry: Jun 8 21:15:58 juju-e4d256-prod-github-runner-66 kernel: [27199.579882] BUG: kernel NULL pointer dereference, address: 0008 The syslog: https://pastebin.canonical.com/p/gYy3Z9XGkN/ Log on openstack: https://pastebin.canonical.com/p/fbGcmQv9JW/ The deployment of the charm was on the jammy series (22.04). This series uses the Linux kernel 5.15. For the last week, the team has been experimenting with upgrading the kernel to the HWE version which is 5.19. Since then we have not encountered crashes in the virtual machine hosting the juju machine. This mattermost thread includes our team’s discussion of this issue and the reason we decide to upgrade the kernel: https://chat.canonical.com/canonical/pl/h8wrrmcnh3d17dtjmg56zf5pwy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026229] [NEW] Crashing issue with 5.15 kernel
Public bug reported: We have been working on making self-hosted GitHub actions runners available in Canonical and have encountered an issue which seems to be with the kernel. This is a doc with more details: https://docs.google.com/document/d/1E00rlT12Cu-h99do80Qge- MKyQARFDY6hxSjhFFfPvA/edit?usp=sharing ** 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/2026229 Title: Crashing issue with 5.15 kernel Status in linux package in Ubuntu: New Bug description: We have been working on making self-hosted GitHub actions runners available in Canonical and have encountered an issue which seems to be with the kernel. This is a doc with more details: https://docs.google.com/document/d/1E00rlT12Cu-h99do80Qge- MKyQARFDY6hxSjhFFfPvA/edit?usp=sharing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@Samer Attrah (samerattrah) I had exactly the same problem that you have, I solved it by disabling secure boot from bios. (to have permission to disable secure boot I also had to set a supervisory password from bios as well). -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 04/20/2022 dmi.bios.release: 1.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag
[Kernel-packages] [Bug 2023636] [NEW] package linux-libc-dev 5.15.0-72.79 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted
Public bug reported: Got a popup with a generic error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-libc-dev 5.15.0-72.79 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 4450 F pulseaudio CasperMD5CheckResult: unknown Date: Tue Jun 13 09:45:54 2023 Dependencies: DuplicateSignature: package:linux-libc-dev:5.15.0-72.79 Unpacking perl-modules-5.34 (5.34.0-3ubuntu1.2) over (5.34.0-3ubuntu1.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Aax279/00-perl-modules-5.34_5.34.0-3ubuntu1.2_all.deb (--unpack): unable to open '/usr/share/perl/5.34.0/warnings/register.pm.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=df64ea1a-ec08-4ea7-b373-695e3e12b5f2 InstallationDate: Installed on 2018-09-20 (1726 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist LTD N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1 SourcePackage: linux Title: package linux-libc-dev 5.15.0-72.79 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to jammy on 2022-10-17 (238 days ago) dmi.bios.date: 06/11/2018 dmi.bios.release: 7.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 5.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.11:bd06/11/2018:br7.11:efr5.9:svnPCSpecialistLTD:pnN7x0WU:pvrNotApplicable:rvnCLEVO:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2023636 Title: package linux-libc-dev 5.15.0-72.79 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted Status in linux package in Ubuntu: New Bug description: Got a popup with a generic error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-libc-dev 5.15.0-72.79 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 4450 F pulseaudio CasperMD5CheckResult: unknown Date: Tue Jun 13 09:45:54 2023 Dependencies: DuplicateSignature: package:linux-libc-dev:5.15.0-72.79 Unpacking perl-modules-5.34 (5.34.0-3ubuntu1.2) over (5.34.0-3ubuntu1.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Aax279/00-perl-modules-5.34_5.34.0-3ubuntu1.2_all.deb (--unpack): unable to open '/usr/share/perl/5.34.0/warnings/register.pm.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=df64ea1a-ec08-4ea7-b373-695e3e12b5f2 InstallationDate: Installed on 2018-09-20 (1726 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC S
[Kernel-packages] [Bug 1993532] Re: [i915] Unable to see second monitor in 5.15.0-52 (but 5.15.0-50 works)
I am experiencing a similar issue, but I'm not sure if it's the same or not. What I experience is that *if I boot with the second monitor attached*, once I unplug it, it will never be detected again. However, if I boot with the second monitor unattached, and then plug it in, I can consistently unplug and replug it and it is always detected. This is using a USB-C cable for the second monitor. If I instead use an HDMI cable, it always works correctly. Robin, can you confirm whether this is the behaviour you're seeing as well? Or if your issue has been resolved? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993532 Title: [i915] Unable to see second monitor in 5.15.0-52 (but 5.15.0-50 works) Status in linux package in Ubuntu: Expired Bug description: I have a second monitor plugged into this laptop. Under 5.15.0-52-generic this monitor isn't seen by Ubuntu, whether via a thunderbolt dongle or directly into the HDMI port. When I boot it back into 5.15.0-50-generic it works just fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robin 4304 F pulseaudio /dev/snd/controlC0: robin 4304 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 14:53:25 2022 InstallationDate: Installed on 2022-03-17 (216 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) MachineType: Dell Inc. Latitude 7320 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.2 dmi.board.name: 07MHG4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.2:bd06/15/2022:br1.17:svnDellInc.:pnLatitude7320:pvr:rvnDellInc.:rn07MHG4:rvrA02:cvnDellInc.:ct10:cvr:sku0A34: dmi.product.family: Latitude dmi.product.name: Latitude 7320 dmi.product.sku: 0A34 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021369] [NEW] package libnvidia-gl-390 (not installed) failed to install/upgrade: new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit statu
Public bug reported: Found after updating from 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libnvidia-gl-390 (not installed) ProcVersionSignature: Ubuntu 5.15.0-72.79-generic 5.15.98 Uname: Linux 5.15.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat May 27 11:23:03 2023 ErrorMessage: new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2023-05-01 (26 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) 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.2 apt 2.4.9 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-gl-390 (not installed) failed to install/upgrade: new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to jammy on 2023-05-27 (0 days ago) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2021369 Title: package libnvidia-gl-390 (not installed) failed to install/upgrade: new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit status 2 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Found after updating from 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libnvidia-gl-390 (not installed) ProcVersionSignature: Ubuntu 5.15.0-72.79-generic 5.15.98 Uname: Linux 5.15.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat May 27 11:23:03 2023 ErrorMessage: new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2023-05-01 (26 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) 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.2 apt 2.4.9 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-gl-390 (not installed) failed to install/upgrade: new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to jammy on 2023-05-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2021369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924298] Re: accept returns duplicate endpoints under load
In Tomcat versions 9.0.56 to 9.0.58, this message was sometimes emitted
in error; this was fixed in 9.0.59. Since 9.0.63, the log message also
explicitly recommends to use Kernel 5.10 or later, but I am not seeing
that in any of the logs reported here, so these Tomcat versions must be
older than 9.0.63.
For those of you who have recently reported seeing this on up to date
focal and jammy versions with Kernel 5.15, please update Tomcat to a
recent version (at least 9.0.59) and report back.
--
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/1924298
Title:
accept returns duplicate endpoints under load
Status in Linux:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
When accepting client connections under load, duplicate endpoints may
be returned. These endpoints will have different (usually sequential)
file descriptors but will refer to the same connection (same server
IP, same server port, same client IP, same client port). Both copies
of the endpoint appear to be functional.
Reproduction requires:
- compilation of the attached server.c program
- wrk (https://github.com/wg/wrk) to generate load
The steps to reproduce are:
- run 'server' application in one console window
- run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency
--timeout 1s http://localhost:/post; done' in a second console window
- run the same command in a third window to generate concurrent load
You may need to run additional instance of the wrk command in multiple
windows to trigger the issue.
When the problem occurs the server executable will exit and print some
debugging info. e.g.:
accerror = 1950892, counter = 10683, port = 59892, clientfd = 233, lastClient
= 232
This indicates that the sockets with file descriptors 233 and 232 are
duplicates.
The issue has been reproduced on fully patched versions of Ubuntu
20.04 and 18.04. Other versions have not been tested.
This issue was originally observed in Java and was reported against the
Spring Framework:
https://github.com/spring-projects/spring-framework/issues/26434
Investigation from the Spring team and the Apache Tomcat team identified that
it appeared to be a JDK issue:
https://bugs.openjdk.java.net/browse/JDK-8263243
Further research from the JDK team determined that the issue was at
the OS level. Hence this report.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-71-generic 5.4.0-71.79
ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
Uname: Linux 5.4.0-71-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 15 12:52:53 2021
HibernationDevice: RESUME=UUID=f5a46e09-d99b-4475-8ab6-2cd70da8418d
InstallationDate: Installed on 2017-02-02 (1532 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig:
lono wireless extensions.
docker0 no wireless extensions.
eno1 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. Default string
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic
root=/dev/mapper/ubuntu--vg-root ro text
RelatedPackageVersions:
linux-restricted-modules-5.4.0-71-generic N/A
linux-backports-modules-5.4.0-71-generic N/A
linux-firmware1.187.10
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-09-07 (219 days ago)
dmi.bios.date: 06/13/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F22
dmi.board.asset.tag: Default string
dmi.board.name: X99-SLI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF22:bd06/13/2016:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Default string
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1924298/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958523] Re: [amdgpu] Static-noise-like effect
I am seeing this same issue (static screen) on a fully updated Jammy system. It is a Beelink Renoir system and I have two external monitors plugged in via HDMI. It seems to happen fairly randomly, but most often after the monitors go to sleep and then are woken up. It resolves itself eventually and doesn't seem to reoccur as long as I'm active on the system. Only one of the screens will go into static when it happens. Manually cycling power on a monitor can help bring it back. Currently on kernel 5.19.0-41-generic. Any workarounds or fixes? Currently using Xorg display, haven't tried Wayland yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958523 Title: [amdgpu] Static-noise-like effect Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: Hello, I have encountered a bug in Ubuntu. When I turn on my laptop and log in (I can see the login screen) I see static-noise-like effect. I was able to make a screenshot and it depicts my desktop as if the problem didn't exist. Switching to stable (non-HWE) kernel solves the issue. My desktop environment is GNOME. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958523/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924298] Re: accept returns duplicate endpoints under load
FWIW, the fix mentioned earlier is indeed in Kernel 5.10-RC6 and later:
https://github.com/torvalds/linux/commit/01770a166165738a6e05c3d911fb4609cc4eb416
But if people are hitting it with e.g. a 5.15 Kernel, then... that fix
didn't fix it ;)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1924298
Title:
accept returns duplicate endpoints under load
Status in Linux:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
When accepting client connections under load, duplicate endpoints may
be returned. These endpoints will have different (usually sequential)
file descriptors but will refer to the same connection (same server
IP, same server port, same client IP, same client port). Both copies
of the endpoint appear to be functional.
Reproduction requires:
- compilation of the attached server.c program
- wrk (https://github.com/wg/wrk) to generate load
The steps to reproduce are:
- run 'server' application in one console window
- run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency
--timeout 1s http://localhost:/post; done' in a second console window
- run the same command in a third window to generate concurrent load
You may need to run additional instance of the wrk command in multiple
windows to trigger the issue.
When the problem occurs the server executable will exit and print some
debugging info. e.g.:
accerror = 1950892, counter = 10683, port = 59892, clientfd = 233, lastClient
= 232
This indicates that the sockets with file descriptors 233 and 232 are
duplicates.
The issue has been reproduced on fully patched versions of Ubuntu
20.04 and 18.04. Other versions have not been tested.
This issue was originally observed in Java and was reported against the
Spring Framework:
https://github.com/spring-projects/spring-framework/issues/26434
Investigation from the Spring team and the Apache Tomcat team identified that
it appeared to be a JDK issue:
https://bugs.openjdk.java.net/browse/JDK-8263243
Further research from the JDK team determined that the issue was at
the OS level. Hence this report.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-71-generic 5.4.0-71.79
ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
Uname: Linux 5.4.0-71-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 15 12:52:53 2021
HibernationDevice: RESUME=UUID=f5a46e09-d99b-4475-8ab6-2cd70da8418d
InstallationDate: Installed on 2017-02-02 (1532 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig:
lono wireless extensions.
docker0 no wireless extensions.
eno1 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. Default string
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic
root=/dev/mapper/ubuntu--vg-root ro text
RelatedPackageVersions:
linux-restricted-modules-5.4.0-71-generic N/A
linux-backports-modules-5.4.0-71-generic N/A
linux-firmware1.187.10
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-09-07 (219 days ago)
dmi.bios.date: 06/13/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F22
dmi.board.asset.tag: Default string
dmi.board.name: X99-SLI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF22:bd06/13/2016:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Default string
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1924298/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017579] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess r
I believe I fixed this in my case by installing the latest DispayLink drivers from https://www.synaptics.com/products/displaylink- graphics/downloads/ubuntu. You may also find choosing the not-latest kernel in the boot menu will help. -- 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/2017579 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: During upgrade to 23.04 from 22.10 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: norbert1451 F wireplumber /dev/snd/controlC1: norbert1451 F wireplumber /dev/snd/seq:norbert1448 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Mon Apr 24 17:54:16 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-03-07 (48 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Dell Inc. XPS 13 9300 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-04-24 (0 days ago) dmi.bios.date: 03/13/2023 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 077Y9N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.0:bd03/13/2023:br1.17:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:sku096D: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017579/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018186] [NEW] package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess
Public bug reported: Error occured during upgrade to Ubuntu 2023.04. Asked me to submit a bug report. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 3982 F wireplumber /dev/snd/controlC1: david 3982 F wireplumber /dev/snd/seq:david 3979 F pipewire CRDA: N/A CasperMD5CheckResult: unknown Date: Sat Apr 29 12:29:36 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-06-16 (683 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20VK001CAU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=6c94f9a7-6ba0-496d-abcc-72b4e2c82feb ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-04-30 (0 days ago) dmi.bios.date: 02/07/2023 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: R1FET50W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20VK001CAU dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrR1FET50W(1.24):bd02/07/2023:br1.24:efr1.16:svnLENOVO:pn20VK001CAU:pvrThinkPadL13YogaGen2:rvnLENOVO:rn20VK001CAU:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20VK_BU_Think_FM_ThinkPadL13YogaGen2: dmi.product.family: ThinkPad L13 Yoga Gen 2 dmi.product.name: 20VK001CAU dmi.product.sku: LENOVO_MT_20VK_BU_Think_FM_ThinkPad L13 Yoga Gen 2 dmi.product.version: ThinkPad L13 Yoga Gen 2 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- 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/2018186 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: Error occured during upgrade to Ubuntu 2023.04. Asked me to submit a bug report. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 3982 F wireplumber /dev/snd/controlC1: david 3982 F wireplumber /dev/snd/seq: david 3979 F pipewire CRDA: N/A CasperMD5CheckResult: unknown Date: Sat Apr 29 12:29:36 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-06-16 (683 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20VK001CAU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=6c94f9a7-6ba0-496d-abcc-72b4e2c82feb ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-04-30 (0 days ago) dmi.bios.date: 02/07/2023 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: R1FET50W (1.24 ) dmi.board.asset.tag: Not Availa
[Kernel-packages] [Bug 2017790] Re: Intel Wi-Fi 6 AX201 failing in 23.04
Windows was installed but it’s removed now. I have seen suggestions to create a bootable usb to disable the WiFi adapter but I’m not sure if that would work -- 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/2017790 Title: Intel Wi-Fi 6 AX201 failing in 23.04 Status in linux-lowlatency package in Ubuntu: Confirmed Bug description: After upgrading from 22.04 to 23.04 the intel wifi driver is not loading, I am seeing the following in dmesg: [ 215.024382] Loading of unsigned module is rejected [ 262.051998] [ cut here ] [ 262.052001] WARNING: CPU: 2 PID: 6946 at net/netlink/genetlink.c:570 genl_validate_ops+0x1cc/0x270 [ 262.052007] Modules linked in: cfg80211(O+) rfcomm xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables libcrc32c nfnetlink br_netfilter bridge stp llc vmw_vsock_vmci_transport vsock vmw_vmci snd_seq_dummy snd_hrtimer overlay cmac algif_hash algif_skcipher af_alg bnep dell_rbu typec_displayport snd_hda_codec_hdmi snd_ctl_led binfmt_misc snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel hid_logitech_hidpp soundwire_generic_allocation nls_iso8859_1 soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_compress ac97_bus x86_pkg_temp_thermal r8153_ecm snd_pcm_dmaengine intel_powerclamp cdc_ether coretemp snd_hda_intel usbnet snd_usb_audio kvm_intel snd_intel_dspcfg r8152 snd_intel_sdw_acpi [ 262.052038] mii hid_plantronics hid_logitech_dj snd_usbmidi_lib snd_hda_codec kvm snd_hda_core snd_hwdep irqbypass mei_hdcp mei_pxp intel_rapl_msr dell_laptop snd_pcm crct10dif_pclmul i915 polyval_clmulni snd_seq_midi polyval_generic snd_seq_midi_event ghash_clmulni_intel sha512_ssse3 snd_rawmidi uvcvideo btusb videobuf2_vmalloc hid_sensor_custom_intel_hinge aesni_intel hid_sensor_gyro_3d hid_sensor_accel_3d dell_wmi videobuf2_memops snd_seq crypto_simd hid_sensor_trigger btrtl drm_buddy snd_seq_device btbcm videobuf2_v4l2 btintel processor_thermal_device_pci_legacy cryptd cmdlinepart industrialio_triggered_buffer dell_smbios rapl dcdbas snd_timer ttm dell_wmi_sysman btmtk videodev kfifo_buf spi_nor processor_thermal_device hid_sensor_iio_common processor_thermal_rfim intel_cstate firmware_attributes_class ledtrig_audio drm_display_helper dell_wmi_descriptor wmi_bmof industrialio mei_me mtd bluetooth snd videobuf2_common mc cec processor_thermal_mbox soundcore rc_core mei ecdh_generic [ 262.052068] processor_thermal_rapl iwlwifi_compat(O) drm_kms_helper ecc ucsi_acpi joydev i2c_algo_bit intel_rapl_common typec_ucsi syscopyarea intel_soc_dts_iosf sysfillrect typec sysimgblt igen6_edac int3403_thermal soc_button_array int340x_thermal_zone int3400_thermal intel_hid acpi_thermal_rel acpi_pad acpi_tad sparse_keymap hid_multitouch input_leds mac_hid serio_raw msr parport_pc ppdev drm lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 usbhid hid_sensor_custom hid_sensor_hub intel_ishtp_hid hid_generic nvme nvme_core intel_ish_ipc i2c_hid_acpi spi_intel_pci rtsx_pci_sdmmc crc32_pclmul video i2c_i801 i2c_hid intel_lpss_pci xhci_pci spi_intel intel_ishtp nvme_common thunderbolt psmouse i2c_smbus intel_lpss rtsx_pci idma64 xhci_pci_renesas hid wmi pinctrl_tigerlake [ 262.052097] CPU: 2 PID: 6946 Comm: modprobe Tainted: GW O 6.2.0-1003-lowlatency #3-Ubuntu [ 262.052098] Hardware name: Dell Inc. Latitude 7420/07MHG4, BIOS 1.24.2 02/24/2023 [ 262.052099] RIP: 0010:genl_validate_ops+0x1cc/0x270 [ 262.052102] Code: 81 c4 d8 00 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d 31 d2 31 c9 31 ff c3 cc cc cc cc 49 83 7d 50 00 0f 85 b9 fe ff ff 0f 0b eb bd <0f> 0b eb b9 0f 0b eb b5 0f 0b eb b1 45 84 ff 75 04 31 c0 eb ad 4d [ 262.052103] RSP: 0018:a91bc7103a88 EFLAGS: 00010206 [ 262.052105] RAX: 0003 RBX: a91bc7103af0 RCX: [ 262.052106] RDX: RSI: RDI: [ 262.052106] RBP: a91bc7103b88 R08: R09: [ 262.052107] R10: R11: R12: 0001 [ 262.052107] R13: c1824780 R14: a91bc7103a88 R15: [ 262.052108] FS: 7fd67c380040() GS:8fcc7f68() knlGS: [ 262.052109] CS: 0010 DS: ES: CR0: 80050033 [ 262.052110] CR2: 7fff38c0e848 CR3: 00010a938006 CR4: 00770ee0 [ 262.052111] PKRU: 5554 [ 262.052112] Call Trace: [ 262.052113] [ 262.052115] ? __pfx_nl80211_pre_doit+0x10/0x10 [cfg80211] [ 262.052146]
[Kernel-packages] [Bug 2017790] Re: Intel Wi-Fi 6 AX201 failing in 23.04
@Matthew No luck i'm afraid I removed the module and I'm still getting the same issue. @Jeremy is there any other steps I can try ? -- 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/2017790 Title: Intel Wi-Fi 6 AX201 failing in 23.04 Status in linux-lowlatency package in Ubuntu: Confirmed Bug description: After upgrading from 22.04 to 23.04 the intel wifi driver is not loading, I am seeing the following in dmesg: [ 215.024382] Loading of unsigned module is rejected [ 262.051998] [ cut here ] [ 262.052001] WARNING: CPU: 2 PID: 6946 at net/netlink/genetlink.c:570 genl_validate_ops+0x1cc/0x270 [ 262.052007] Modules linked in: cfg80211(O+) rfcomm xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables libcrc32c nfnetlink br_netfilter bridge stp llc vmw_vsock_vmci_transport vsock vmw_vmci snd_seq_dummy snd_hrtimer overlay cmac algif_hash algif_skcipher af_alg bnep dell_rbu typec_displayport snd_hda_codec_hdmi snd_ctl_led binfmt_misc snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel hid_logitech_hidpp soundwire_generic_allocation nls_iso8859_1 soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_compress ac97_bus x86_pkg_temp_thermal r8153_ecm snd_pcm_dmaengine intel_powerclamp cdc_ether coretemp snd_hda_intel usbnet snd_usb_audio kvm_intel snd_intel_dspcfg r8152 snd_intel_ sdw_acpi [ 262.052038] mii hid_plantronics hid_logitech_dj snd_usbmidi_lib snd_hda_codec kvm snd_hda_core snd_hwdep irqbypass mei_hdcp mei_pxp intel_rapl_msr dell_laptop snd_pcm crct10dif_pclmul i915 polyval_clmulni snd_seq_midi polyval_generic snd_seq_midi_event ghash_clmulni_intel sha512_ssse3 snd_rawmidi uvcvideo btusb videobuf2_vmalloc hid_sensor_custom_intel_hinge aesni_intel hid_sensor_gyro_3d hid_sensor_accel_3d dell_wmi videobuf2_memops snd_seq crypto_simd hid_sensor_trigger btrtl drm_buddy snd_seq_device btbcm videobuf2_v4l2 btintel processor_thermal_device_pci_legacy cryptd cmdlinepart industrialio_triggered_buffer dell_smbios rapl dcdbas snd_timer ttm dell_wmi_sysman btmtk videodev kfifo_buf spi_nor processor_thermal_device hid_sensor_iio_common processor_thermal_rfim intel_cstate firmware_attributes_class ledtrig_audio drm_display_helper dell_wmi_descriptor wmi_bmof industrialio mei_me mtd bluetooth snd videobuf2_common mc cec processor_thermal_mbox soundcore rc_core mei ecdh_ generic [ 262.052068] processor_thermal_rapl iwlwifi_compat(O) drm_kms_helper ecc ucsi_acpi joydev i2c_algo_bit intel_rapl_common typec_ucsi syscopyarea intel_soc_dts_iosf sysfillrect typec sysimgblt igen6_edac int3403_thermal soc_button_array int340x_thermal_zone int3400_thermal intel_hid acpi_thermal_rel acpi_pad acpi_tad sparse_keymap hid_multitouch input_leds mac_hid serio_raw msr parport_pc ppdev drm lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 usbhid hid_sensor_custom hid_sensor_hub intel_ishtp_hid hid_generic nvme nvme_core intel_ish_ipc i2c_hid_acpi spi_intel_pci rtsx_pci_sdmmc crc32_pclmul video i2c_i801 i2c_hid intel_lpss_pci xhci_pci spi_intel intel_ishtp nvme_common thunderbolt psmouse i2c_smbus intel_lpss rtsx_pci idma64 xhci_pci_renesas hid wmi pinctrl_tigerlake [ 262.052097] CPU: 2 PID: 6946 Comm: modprobe Tainted: GW O 6.2.0-1003-lowlatency #3-Ubuntu [ 262.052098] Hardware name: Dell Inc. Latitude 7420/07MHG4, BIOS 1.24.2 02/24/2023 [ 262.052099] RIP: 0010:genl_validate_ops+0x1cc/0x270 [ 262.052102] Code: 81 c4 d8 00 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d 31 d2 31 c9 31 ff c3 cc cc cc cc 49 83 7d 50 00 0f 85 b9 fe ff ff 0f 0b eb bd <0f> 0b eb b9 0f 0b eb b5 0f 0b eb b1 45 84 ff 75 04 31 c0 eb ad 4d [ 262.052103] RSP: 0018:a91bc7103a88 EFLAGS: 00010206 [ 262.052105] RAX: 0003 RBX: a91bc7103af0 RCX: [ 262.052106] RDX: RSI: RDI: [ 262.052106] RBP: a91bc7103b88 R08: R09: [ 262.052107] R10: R11: R12: 0001 [ 262.052107] R13: c1824780 R14: a91bc7103a88 R15: [ 262.052108] FS: 7fd67c380040() GS:8fcc7f68() knlGS: [ 262.052109] CS: 0010 DS: ES: CR0: 80050033 [ 262.052110] CR2: 7fff38c0e848 CR3: 00010a938006 CR4: 00770ee0 [ 262.052111] PKRU: 5554 [ 262.052112] Call Trace: [ 262.052113] [ 262.052115] ? __pfx_nl80211_pre_doit+0x10/0x10 [cfg80211] [ 262.052146] ?
[Kernel-packages] [Bug 2017790] Re: Intel Wi-Fi 6 AX201 failing in 23.04
I have removed the backports and now i'm getting this: sudo dmesg |grep -i wifi [3.412202] Intel(R) Wireless WiFi driver for Linux [3.412300] iwlwifi :00:14.3: enabling device ( -> 0002) [3.525445] iwlwifi :00:14.3: CSR_RESET = 0x10 [3.525473] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x0 [3.525525] iwlwifi :00:14.3: value [iter 0]: 0x [3.525577] iwlwifi :00:14.3: value [iter 1]: 0x [3.525627] iwlwifi :00:14.3: value [iter 2]: 0x [3.525667] iwlwifi :00:14.3: value [iter 3]: 0x [3.525700] iwlwifi :00:14.3: value [iter 4]: 0x [3.525751] iwlwifi :00:14.3: value [iter 5]: 0x [3.525796] iwlwifi :00:14.3: value [iter 6]: 0x [3.525838] iwlwifi :00:14.3: value [iter 7]: 0x [3.525870] iwlwifi :00:14.3: value [iter 8]: 0x [3.525919] iwlwifi :00:14.3: value [iter 9]: 0x [3.525985] iwlwifi :00:14.3: value [iter 10]: 0x [3.526037] iwlwifi :00:14.3: value [iter 11]: 0x [3.526075] iwlwifi :00:14.3: value [iter 12]: 0x [3.526131] iwlwifi :00:14.3: value [iter 13]: 0x [3.526201] iwlwifi :00:14.3: value [iter 14]: 0x [3.526225] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x1 [3.526284] iwlwifi :00:14.3: value [iter 0]: 0x [3.526340] iwlwifi :00:14.3: value [iter 1]: 0x [3.526381] iwlwifi :00:14.3: value [iter 2]: 0x [3.526434] iwlwifi :00:14.3: value [iter 3]: 0x [3.526494] iwlwifi :00:14.3: value [iter 4]: 0x [3.526543] iwlwifi :00:14.3: value [iter 5]: 0x [3.526585] iwlwifi :00:14.3: value [iter 6]: 0x [3.526651] iwlwifi :00:14.3: value [iter 7]: 0x [3.526702] iwlwifi :00:14.3: value [iter 8]: 0x [3.526763] iwlwifi :00:14.3: value [iter 9]: 0x [3.526822] iwlwifi :00:14.3: value [iter 10]: 0x [3.526875] iwlwifi :00:14.3: value [iter 11]: 0x [3.526936] iwlwifi :00:14.3: value [iter 12]: 0x [3.526995] iwlwifi :00:14.3: value [iter 13]: 0x [3.527041] iwlwifi :00:14.3: value [iter 14]: 0x [3.527065] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x6 [3.527113] iwlwifi :00:14.3: value [iter 0]: 0x [3.527151] iwlwifi :00:14.3: value [iter 1]: 0x [3.527190] iwlwifi :00:14.3: value [iter 2]: 0x [3.527230] iwlwifi :00:14.3: value [iter 3]: 0x [3.527270] iwlwifi :00:14.3: value [iter 4]: 0x [3.527338] iwlwifi :00:14.3: value [iter 5]: 0x [3.527369] iwlwifi :00:14.3: value [iter 6]: 0x [3.527405] iwlwifi :00:14.3: value [iter 7]: 0x [3.527439] iwlwifi :00:14.3: value [iter 8]: 0x [3.527472] iwlwifi :00:14.3: value [iter 9]: 0x [3.527513] iwlwifi :00:14.3: value [iter 10]: 0x [3.527561] iwlwifi :00:14.3: value [iter 11]: 0x [3.527602] iwlwifi :00:14.3: value [iter 12]: 0x [3.527636] iwlwifi :00:14.3: value [iter 13]: 0x [3.527698] iwlwifi :00:14.3: value [iter 14]: 0x [3.527718] iwlwifi :00:14.3: Host monitor block 0x22 vector 0x0 [3.527774] iwlwifi :00:14.3: value [iter 0]: 0x [3.527820] iwlwifi: probe of :00:14.3 failed with error -110 -- 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/2017790 Title: Intel Wi-Fi 6 AX201 failing in 23.04 Status in linux-lowlatency package in Ubuntu: Confirmed Bug description: After upgrading from 22.04 to 23.04 the intel wifi driver is not loading, I am seeing the following in dmesg: [ 215.024382] Loading of unsigned module is rejected [ 262.051998] [ cut here ] [ 262.052001] WARNING: CPU: 2 PID: 6946 at net/netlink/genetlink.c:570 genl_validate_ops+0x1cc/0x270 [ 262.052007] Modules linked in: cfg80211(O+) rfcomm xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables libcrc32c nfnetlink br_netfilter bridge stp llc vmw_vsock_vmci_transport vsock vmw_vmci snd_seq_dummy snd_hrtimer overlay cmac algif_hash algif_skcipher af_alg bnep dell_rbu typec_displayport snd_hda_codec_hdmi snd_ctl_led binfmt_misc snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel hid_logitech_hidpp
[Kernel-packages] [Bug 2017790] Re: Intel Wi-Fi 6 AX201 failing in 23.04
Alos seeing this: [2.691388] iwlwifi_compat: loading out-of-tree module taints kernel. [2.698204] Loading modules backported from iwlwifi [2.698208] iwlwifi-stack-public:master:9904:0e80336f -- 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/2017790 Title: Intel Wi-Fi 6 AX201 failing in 23.04 Status in linux-lowlatency package in Ubuntu: New Bug description: After upgrading from 22.04 to 23.04 the intel wifi driver is not loading, I am seeing the following in dmesg: [ 215.024382] Loading of unsigned module is rejected [ 262.051998] [ cut here ] [ 262.052001] WARNING: CPU: 2 PID: 6946 at net/netlink/genetlink.c:570 genl_validate_ops+0x1cc/0x270 [ 262.052007] Modules linked in: cfg80211(O+) rfcomm xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables libcrc32c nfnetlink br_netfilter bridge stp llc vmw_vsock_vmci_transport vsock vmw_vmci snd_seq_dummy snd_hrtimer overlay cmac algif_hash algif_skcipher af_alg bnep dell_rbu typec_displayport snd_hda_codec_hdmi snd_ctl_led binfmt_misc snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel hid_logitech_hidpp soundwire_generic_allocation nls_iso8859_1 soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_compress ac97_bus x86_pkg_temp_thermal r8153_ecm snd_pcm_dmaengine intel_powerclamp cdc_ether coretemp snd_hda_intel usbnet snd_usb_audio kvm_intel snd_intel_dspcfg r8152 snd_intel_ sdw_acpi [ 262.052038] mii hid_plantronics hid_logitech_dj snd_usbmidi_lib snd_hda_codec kvm snd_hda_core snd_hwdep irqbypass mei_hdcp mei_pxp intel_rapl_msr dell_laptop snd_pcm crct10dif_pclmul i915 polyval_clmulni snd_seq_midi polyval_generic snd_seq_midi_event ghash_clmulni_intel sha512_ssse3 snd_rawmidi uvcvideo btusb videobuf2_vmalloc hid_sensor_custom_intel_hinge aesni_intel hid_sensor_gyro_3d hid_sensor_accel_3d dell_wmi videobuf2_memops snd_seq crypto_simd hid_sensor_trigger btrtl drm_buddy snd_seq_device btbcm videobuf2_v4l2 btintel processor_thermal_device_pci_legacy cryptd cmdlinepart industrialio_triggered_buffer dell_smbios rapl dcdbas snd_timer ttm dell_wmi_sysman btmtk videodev kfifo_buf spi_nor processor_thermal_device hid_sensor_iio_common processor_thermal_rfim intel_cstate firmware_attributes_class ledtrig_audio drm_display_helper dell_wmi_descriptor wmi_bmof industrialio mei_me mtd bluetooth snd videobuf2_common mc cec processor_thermal_mbox soundcore rc_core mei ecdh_ generic [ 262.052068] processor_thermal_rapl iwlwifi_compat(O) drm_kms_helper ecc ucsi_acpi joydev i2c_algo_bit intel_rapl_common typec_ucsi syscopyarea intel_soc_dts_iosf sysfillrect typec sysimgblt igen6_edac int3403_thermal soc_button_array int340x_thermal_zone int3400_thermal intel_hid acpi_thermal_rel acpi_pad acpi_tad sparse_keymap hid_multitouch input_leds mac_hid serio_raw msr parport_pc ppdev drm lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 usbhid hid_sensor_custom hid_sensor_hub intel_ishtp_hid hid_generic nvme nvme_core intel_ish_ipc i2c_hid_acpi spi_intel_pci rtsx_pci_sdmmc crc32_pclmul video i2c_i801 i2c_hid intel_lpss_pci xhci_pci spi_intel intel_ishtp nvme_common thunderbolt psmouse i2c_smbus intel_lpss rtsx_pci idma64 xhci_pci_renesas hid wmi pinctrl_tigerlake [ 262.052097] CPU: 2 PID: 6946 Comm: modprobe Tainted: GW O 6.2.0-1003-lowlatency #3-Ubuntu [ 262.052098] Hardware name: Dell Inc. Latitude 7420/07MHG4, BIOS 1.24.2 02/24/2023 [ 262.052099] RIP: 0010:genl_validate_ops+0x1cc/0x270 [ 262.052102] Code: 81 c4 d8 00 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d 31 d2 31 c9 31 ff c3 cc cc cc cc 49 83 7d 50 00 0f 85 b9 fe ff ff 0f 0b eb bd <0f> 0b eb b9 0f 0b eb b5 0f 0b eb b1 45 84 ff 75 04 31 c0 eb ad 4d [ 262.052103] RSP: 0018:a91bc7103a88 EFLAGS: 00010206 [ 262.052105] RAX: 0003 RBX: a91bc7103af0 RCX: [ 262.052106] RDX: RSI: RDI: [ 262.052106] RBP: a91bc7103b88 R08: R09: [ 262.052107] R10: R11: R12: 0001 [ 262.052107] R13: c1824780 R14: a91bc7103a88 R15: [ 262.052108] FS: 7fd67c380040() GS:8fcc7f68() knlGS: [ 262.052109] CS: 0010 DS: ES: CR0: 80050033 [ 262.052110] CR2: 7fff38c0e848 CR3: 00010a938006 CR4: 00770ee0 [ 262.052111] PKRU: 5554 [ 262.052112] Call Trace: [ 262.052113] [ 262.052115] ?
[Kernel-packages] [Bug 2017790] [NEW] Intel Wi-Fi 6 AX201 failing in 23.04
Public bug reported: After upgrading from 22.04 to 23.04 the intel wifi driver is not loading, I am seeing the following in dmesg: [ 215.024382] Loading of unsigned module is rejected [ 262.051998] [ cut here ] [ 262.052001] WARNING: CPU: 2 PID: 6946 at net/netlink/genetlink.c:570 genl_validate_ops+0x1cc/0x270 [ 262.052007] Modules linked in: cfg80211(O+) rfcomm xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables libcrc32c nfnetlink br_netfilter bridge stp llc vmw_vsock_vmci_transport vsock vmw_vmci snd_seq_dummy snd_hrtimer overlay cmac algif_hash algif_skcipher af_alg bnep dell_rbu typec_displayport snd_hda_codec_hdmi snd_ctl_led binfmt_misc snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel hid_logitech_hidpp soundwire_generic_allocation nls_iso8859_1 soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_compress ac97_bus x86_pkg_temp_thermal r8153_ecm snd_pcm_dmaengine intel_powerclamp cdc_ether coretemp snd_hda_intel usbnet snd_usb_audio kvm_intel snd_intel_dspcfg r8152 snd_intel_sd w_acpi [ 262.052038] mii hid_plantronics hid_logitech_dj snd_usbmidi_lib snd_hda_codec kvm snd_hda_core snd_hwdep irqbypass mei_hdcp mei_pxp intel_rapl_msr dell_laptop snd_pcm crct10dif_pclmul i915 polyval_clmulni snd_seq_midi polyval_generic snd_seq_midi_event ghash_clmulni_intel sha512_ssse3 snd_rawmidi uvcvideo btusb videobuf2_vmalloc hid_sensor_custom_intel_hinge aesni_intel hid_sensor_gyro_3d hid_sensor_accel_3d dell_wmi videobuf2_memops snd_seq crypto_simd hid_sensor_trigger btrtl drm_buddy snd_seq_device btbcm videobuf2_v4l2 btintel processor_thermal_device_pci_legacy cryptd cmdlinepart industrialio_triggered_buffer dell_smbios rapl dcdbas snd_timer ttm dell_wmi_sysman btmtk videodev kfifo_buf spi_nor processor_thermal_device hid_sensor_iio_common processor_thermal_rfim intel_cstate firmware_attributes_class ledtrig_audio drm_display_helper dell_wmi_descriptor wmi_bmof industrialio mei_me mtd bluetooth snd videobuf2_common mc cec processor_thermal_mbox soundcore rc_core mei ecdh_ge neric [ 262.052068] processor_thermal_rapl iwlwifi_compat(O) drm_kms_helper ecc ucsi_acpi joydev i2c_algo_bit intel_rapl_common typec_ucsi syscopyarea intel_soc_dts_iosf sysfillrect typec sysimgblt igen6_edac int3403_thermal soc_button_array int340x_thermal_zone int3400_thermal intel_hid acpi_thermal_rel acpi_pad acpi_tad sparse_keymap hid_multitouch input_leds mac_hid serio_raw msr parport_pc ppdev drm lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 usbhid hid_sensor_custom hid_sensor_hub intel_ishtp_hid hid_generic nvme nvme_core intel_ish_ipc i2c_hid_acpi spi_intel_pci rtsx_pci_sdmmc crc32_pclmul video i2c_i801 i2c_hid intel_lpss_pci xhci_pci spi_intel intel_ishtp nvme_common thunderbolt psmouse i2c_smbus intel_lpss rtsx_pci idma64 xhci_pci_renesas hid wmi pinctrl_tigerlake [ 262.052097] CPU: 2 PID: 6946 Comm: modprobe Tainted: GW O 6.2.0-1003-lowlatency #3-Ubuntu [ 262.052098] Hardware name: Dell Inc. Latitude 7420/07MHG4, BIOS 1.24.2 02/24/2023 [ 262.052099] RIP: 0010:genl_validate_ops+0x1cc/0x270 [ 262.052102] Code: 81 c4 d8 00 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d 31 d2 31 c9 31 ff c3 cc cc cc cc 49 83 7d 50 00 0f 85 b9 fe ff ff 0f 0b eb bd <0f> 0b eb b9 0f 0b eb b5 0f 0b eb b1 45 84 ff 75 04 31 c0 eb ad 4d [ 262.052103] RSP: 0018:a91bc7103a88 EFLAGS: 00010206 [ 262.052105] RAX: 0003 RBX: a91bc7103af0 RCX: [ 262.052106] RDX: RSI: RDI: [ 262.052106] RBP: a91bc7103b88 R08: R09: [ 262.052107] R10: R11: R12: 0001 [ 262.052107] R13: c1824780 R14: a91bc7103a88 R15: [ 262.052108] FS: 7fd67c380040() GS:8fcc7f68() knlGS: [ 262.052109] CS: 0010 DS: ES: CR0: 80050033 [ 262.052110] CR2: 7fff38c0e848 CR3: 00010a938006 CR4: 00770ee0 [ 262.052111] PKRU: 5554 [ 262.052112] Call Trace: [ 262.052113] [ 262.052115] ? __pfx_nl80211_pre_doit+0x10/0x10 [cfg80211] [ 262.052146] ? __pfx_nl80211_get_wiphy+0x10/0x10 [cfg80211] [ 262.052171] ? __pfx_nl80211_post_doit+0x10/0x10 [cfg80211] [ 262.052195] ? __pfx_nl80211_dump_wiphy+0x10/0x10 [cfg80211] [ 262.052217] ? __pfx_nl80211_dump_wiphy_done+0x10/0x10 [cfg80211] [ 262.052238] genl_register_family+0x29/0x200 [ 262.052240] ? rtnl_unlock+0xe/0x20 [ 262.052244] nl80211_init+0x16/0xc50 [cfg80211] [ 262.052267] __init_backport+0x78/0xf0 [cfg80211] [ 262.052288] ? __pfx_init_module+0x10/0x10
Re: [Kernel-packages] [Bug 1969457] Re: /dev/zvol links not created for encrypted zvols, zfs-volume-wait Timed out waiting on zvol links
In my case, they did not. On Tue, Apr 25, 2023 at 4:01 AM homerlinux <1969...@bugs.launchpad.net> wrote: > May be, by any chance, that your zvols contain LVMs? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1969457 > > Title: > /dev/zvol links not created for encrypted zvols, zfs-volume-wait Timed > out waiting on zvol links > > Status in zfs-linux package in Ubuntu: > Confirmed > > Bug description: > Fresh installation of 20.04.4 with installer created zfs native > encrypted root > zfsutils-linux: 0.8.3-1ubuntu12.13 > > On reboot, zvol /dev/zvol entries are not being created. This seems to > effect different zvols each reboot. > > Example logs: > ``` > -- A start job for unit zsys-gc.service has finished successfully. > -- > -- The job identifier is 3139. > Apr 19 06:43:49 monolith zvol_wait[74768]: cannot open > 'rpool/export/vault/block': dataset does not exist > Apr 19 06:43:50 monolith zvol_wait[74786]: cannot open > 'rpool/export/vault/block': dataset does not exist > Apr 19 06:43:51 monolith zvol_wait[74805]: cannot open > 'rpool/export/vault/block': dataset does not exist > Apr 19 06:43:52 monolith zvol_wait[74823]: cannot open > 'rpool/export/vault/block': dataset does not exist > Apr 19 06:43:53 monolith zvol_wait[74932]: cannot open > 'rpool/export/vault/block': dataset does not exist > Apr 19 06:43:54 monolith zvol_wait[74950]: cannot open > 'rpool/export/vault/block': dataset does not exist > Apr 19 06:43:55 monolith zvol_wait[74969]: cannot open > 'rpool/export/vault/block': dataset does not exist > Apr 19 06:43:56 monolith zvol_wait[74987]: cannot open > 'rpool/export/vault/block': dataset does not exist > Apr 19 06:43:57 monolith zvol_wait[75006]: cannot open > 'rpool/export/vault/block': dataset does not exist > Apr 19 06:43:58 monolith zvol_wait[4440]: Still waiting on 1 zvol links > ... > Apr 19 06:43:58 monolith zvol_wait[4440]: No progress since last loop. > Apr 19 06:43:58 monolith zvol_wait[4440]: Checking if any zvols were > deleted. > Apr 19 06:43:58 monolith zvol_wait[4440]: Remaining zvols: > Apr 19 06:43:58 monolith zvol_wait[4440]: > rpool/libvirt_zvols/kube-04-disk0 > Apr 19 06:43:58 monolith zvol_wait[4440]: Timed out waiting on zvol links > Apr 19 06:43:58 monolith systemd[1]: zfs-volume-wait.service: Main > process exited, code=exited, status=1/FAILURE > -- Subject: Unit process exited > -- Defined-By: systemd > -- Support: http://www.ubuntu.com/support > -- > -- An ExecStart= process belonging to unit zfs-volume-wait.service has > exited. > -- > -- The process' exit code is 'exited' and its exit status is 1. > Apr 19 06:43:58 monolith systemd[1]: zfs-volume-wait.service: Failed > with result 'exit-code'. > -- Subject: Unit failed > -- Defined-By: systemd > -- Support: http://www.ubuntu.com/support > -- > -- The unit zfs-volume-wait.service has entered the 'failed' state with > result 'exit-code'. > Apr 19 06:43:58 monolith systemd[1]: Failed to start Wait for ZFS Volume > (zvol) links in /dev. > -- Subject: A start job for unit zfs-volume-wait.service has failed > -- Defined-By: systemd > -- Support: http://www.ubuntu.com/support > -- > -- A start job for unit zfs-volume-wait.service has finished with a > failure. > -- > -- The job identifier is 226 and the job result is failed. > Apr 19 06:43:58 monolith systemd[1]: Dependency failed for ZFS volumes > are ready. > -- Subject: A start job for unit zfs-volumes.target has failed > -- Defined-By: systemd > -- Support: http://www.ubuntu.com/support > -- > -- A start job for unit zfs-volumes.target has finished with a failure. > ``` > I believe this is related to changes made here: > https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1888405 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969457/+subscriptions > > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1969457 Title: /dev/zvol links not created for encrypted zvols, zfs-volume-wait Timed out waiting on zvol links Status in zfs-linux package in Ubuntu: Confirmed Bug description: Fresh installation of 20.04.4 with installer created zfs native encrypted root zfsutils-linux: 0.8.3-1ubuntu12.13 On reboot, zvol /dev/zvol entries are not being created. This seems to effect different zvols each reboot. Example logs: ``` -- A start job for unit zsys-gc.service has finished successfully. -- -- The job identifier is 3139. Apr 19 06:43:49 monolith zvol_wait[74768]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:50 monolith zvol_wait[74786]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:51 monolith
[Kernel-packages] [Bug 2013086] Re: regression: max number of loop devices
Users of our software (singularity) were affected by this issue. https://github.com/sylabs/singularity/issues/1499 For historic reasons (old kernels without /dev/loop-control), we have been creating /dev/loopXX devices directly via mknod, if needed, before using them. After the backport of https://lkml.org/lkml/2022/12/8/904 it was possible to mknod additional loop devices, in addition to those present on boot, but they could not then be used successfully. We found that switching to creating devices via LOOP_CTL_ADD ioctl against /dev/loop-control avoids the issue. >8 devices are created and are usable. While there will be a workaround for people who can upgrade to a new version of our software, the change in the Ubuntu kernel causes a regression for users of existing versions of singularity, who must set max_loop in the kernel cmdline to work around the problem. ** Bug watch added: github.com/sylabs/singularity/issues #1499 https://github.com/sylabs/singularity/issues/1499 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2013086 Title: regression: max number of loop devices Status in linux-hwe-5.15 package in Ubuntu: Confirmed Bug description: Since the patch in https://lkml.org/lkml/2022/12/8/904 got backported to linux-hwe-5.15 (apparently in 5.15.0-68) the kernel effectively boots with max_loop=CONFIG_BLK_DEV_LOOP_MIN_COUNT as a parameter. In /boot/config-... we find CONFIG_BLK_DEV_LOOP_MIN_COUNT=8, which means no more than 8 loop devices are supported. This is a regression. At least one other distro solves this by compiling with CONFIG_BLK_DEV_LOOP_MIN_COUNT=0 [1]; maybe Ubuntu could start doing that as well. We currently workaround this by setting max_loop=0 on the kernel cmdline but would rather not have to. [1] https://github.com/archlinux/svntogit- packages/blob/62b8243b1d485493d3e8b10b05281efa20fe7918/trunk/config#L2517 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2013086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014227] [NEW] package linux-headers-6.2.0-18-generic 6.2.0-18.18 failed to install/upgrade: installed linux-headers-6.2.0-18-generic package post-installation script subprocess
Public bug reported: This is when running do-release-upgrade. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-18-generic 6.2.0-18.18 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.26.0-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david-noble 1659 F wireplumber /dev/snd/seq:david-noble 1656 F pipewire CasperMD5CheckResult: pass Date: Fri Mar 31 14:47:08 2023 ErrorMessage: installed linux-headers-6.2.0-18-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-03-13 (748 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release arm64 (20210201.2) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci-vt: -[:00]-+-01.0 Intel Corporation 82801I (ICH9 Family) HD Audio Controller +-02.0 Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller +-03.0 NEC Corporation uPD720200 USB 3.0 Host Controller +-09.0 Parallels, Inc. Virtual Machine Communication Interface \-0a.0 Red Hat, Inc. Virtio GPU MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=732910d6-ddae-4a95-ab9e-9f5c9edc555a ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-headers-6.2.0-18-generic 6.2.0-18.18 failed to install/upgrade: installed linux-headers-6.2.0-18-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-03-31 (0 days ago) acpidump: dmi.bios.date: Fri, 10 Feb 2023 10:16:42 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 18.2.0 (53488) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr18.2.0(53488):bdFri,10Feb2023101642:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr:skuParallels_ARM_VM: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-package arm64 lunar -- 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/2014227 Title: package linux-headers-6.2.0-18-generic 6.2.0-18.18 failed to install/upgrade: installed linux-headers-6.2.0-18-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: This is when running do-release-upgrade. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-18-generic 6.2.0-18.18 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.26.0-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david-noble 1659 F wireplumber /dev/snd/seq: david-noble 1656 F pipewire CasperMD5CheckResult: pass Date: Fri Mar 31 14:47:08 2023 ErrorMessage: installed linux-headers-6.2.0-18-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-03-13 (748 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release arm64 (20210201.2) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci-vt: -[:00]-+-01.0 Intel Corporation 82801I (ICH9 Family) HD Audio Controller +-02.0 Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller +-03.0 NEC Corporation uPD720200 USB 3.0 Host Controller +-09.0 Parallels, Inc. Virtual Machine Communication Interface \-0a.0 Red Hat, Inc. Virtio GPU Ma
[Kernel-packages] [Bug 1874241] Re: iwlwifi intel ax201 crashing on intel nuc10i7fnh
I'm on the latest kernel for 22.04 and I still can't get the wifi driver to load I keep seeing the following: [ 3.837973] audit: type=1400 audit(1677506792.544:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_gr off" pid=522 comm="apparmor_parser" [ 3.960935] iwlwifi :00:14.3: CSR_RESET = 0x10 [ 3.960965] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x0 [ 3.961034] iwlwifi :00:14.3: value [iter 0]: 0x [ 3.961098] iwlwifi :00:14.3: value [iter 1]: 0x [ 3.961162] iwlwifi :00:14.3: value [iter 2]: 0x [ 3.961222] iwlwifi :00:14.3: value [iter 3]: 0x [ 3.961291] iwlwifi :00:14.3: value [iter 4]: 0x [ 3.961354] iwlwifi :00:14.3: value [iter 5]: 0x [ 3.961412] iwlwifi :00:14.3: value [iter 6]: 0x [ 3.961468] iwlwifi :00:14.3: value [iter 7]: 0x [ 3.961533] iwlwifi :00:14.3: value [iter 8]: 0x [ 3.961584] iwlwifi :00:14.3: value [iter 9]: 0x [ 3.961633] iwlwifi :00:14.3: value [iter 10]: 0x [ 3.961683] iwlwifi :00:14.3: value [iter 11]: 0x [ 3.961741] iwlwifi :00:14.3: value [iter 12]: 0x [ 3.961790] iwlwifi :00:14.3: value [iter 13]: 0x [ 3.961859] iwlwifi :00:14.3: value [iter 14]: 0x [ 3.961879] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x1 [ 3.961949] iwlwifi :00:14.3: value [iter 0]: 0x [ 3.962012] iwlwifi :00:14.3: value [iter 1]: 0x [ 3.962073] iwlwifi :00:14.3: value [iter 2]: 0x [ 3.962133] iwlwifi :00:14.3: value [iter 3]: 0x [ 3.962213] iwlwifi :00:14.3: value [iter 4]: 0x [ 3.962279] iwlwifi :00:14.3: value [iter 5]: 0x [ 3.962339] iwlwifi :00:14.3: value [iter 6]: 0x [ 3.962399] iwlwifi :00:14.3: value [iter 7]: 0x [ 3.962466] iwlwifi :00:14.3: value [iter 8]: 0x [ 3.962528] iwlwifi :00:14.3: value [iter 9]: 0x [ 3.962590] iwlwifi :00:14.3: value [iter 10]: 0x [ 3.962655] iwlwifi :00:14.3: value [iter 11]: 0x [ 3.962723] iwlwifi :00:14.3: value [iter 12]: 0x [ 3.962786] iwlwifi :00:14.3: value [iter 13]: 0x [ 3.962842] iwlwifi :00:14.3: value [iter 14]: 0x [ 3.962853] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x6 [ 3.962906] iwlwifi :00:14.3: value [iter 0]: 0x [ 3.962971] iwlwifi :00:14.3: value [iter 1]: 0x [ 3.963028] iwlwifi :00:14.3: value [iter 2]: 0x [ 3.963074] iwlwifi :00:14.3: value [iter 3]: 0x [ 3.963488] iwlwifi :00:14.3: value [iter 4]: 0x [ 3.963546] iwlwifi :00:14.3: value [iter 5]: 0x [ 3.963595] iwlwifi :00:14.3: value [iter 6]: 0x [ 3.963643] iwlwifi :00:14.3: value [iter 7]: 0x [ 3.963695] iwlwifi :00:14.3: value [iter 8]: 0x [ 3.963771] iwlwifi :00:14.3: value [iter 9]: 0x [ 3.963829] iwlwifi :00:14.3: value [iter 10]: 0x [ 3.963891] iwlwifi :00:14.3: value [iter 11]: 0x [ 3.963951] iwlwifi :00:14.3: value [iter 12]: 0x [ 3.964019] iwlwifi :00:14.3: value [iter 13]: 0x [ 3.964089] iwlwifi :00:14.3: value [iter 14]: 0x [ 3.964118] iwlwifi :00:14.3: Host monitor block 0x22 vector 0x0 [ 3.964186] iwlwifi :00:14.3: value [iter 0]: 0x [ 3.964237] iwlwifi: probe of :00:14.3 failed with error -110 [ 3.974367] AVX2 version of gcm_enc/dec engaged. [ 3.974401] AES CTR mode by8 optimization enabled -- 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/1874241 Title: iwlwifi intel ax201 crashing on intel nuc10i7fnh Status in linux-firmware package in Ubuntu: Incomplete Bug description: The intel iwlwifi firmware will crash when you insert a device into the thunderbolt3 port, and this will be trigger probabilistically. wifi card model:Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x354 Firmware version: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17 Linux-firmware version: 1.187 thunderbolt3 chip model: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06) dmesg output: [ 103.777908] pcieport :00:1c.0: PME: Spurious native interrupt! [ 103.777918] pcieport :00:1c.0: PME: Spurious native interrupt! [ 104.118148] usb 4-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 104.147184] usb 4-1: New USB device found, idVendor=05e3, idProduct=0749, bcdDevice=15.32 [ 104.147190] usb 4-1: New USB device strings: Mfr=3, Product=4, SerialNumber=2 [ 104.147194] usb 4-1: Product: USB3.0 Card Reader [ 104.147197] usb 4-1: Manufacturer: Generic [ 104.147199] usb 4-1: SerialNumber: 1532 [ 104.183374] usb-storage 4-1:1.0: USB Mass Storage device detected [ 104.183952] scsi host3: usb-storage
[Kernel-packages] [Bug 2013108] [NEW] Bluetooth HP810-160 Not Activated
Public bug reported: sudo cat /sys/kernel/debug/usb/devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 2 B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev= 5.19 S: Manufacturer=Linux 5.19.0-38-generic ehci_hcd S: Product=EHCI Host Controller S: SerialNumber=:00:1a.0 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 6 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=8087 ProdID=8008 Rev= 0.05 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=256ms T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 2 B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev= 5.19 S: Manufacturer=Linux 5.19.0-38-generic ehci_hcd S: Product=EHCI Host Controller S: SerialNumber=:00:1d.0 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 8 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=8087 ProdID=8000 Rev= 0.05 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=14 B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev= 5.19 S: Manufacturer=Linux 5.19.0-38-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=17ef ProdID=602d Rev= 1.30 S: Manufacturer=Lenovo S: Product=Lenovo Black Silk USB Keyboard C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=100mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbhid E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms I:* If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid E: Ad=82(I) Atr=03(Int.) MxPS= 5 Ivl=10ms T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=17ef ProdID=602e Rev= 1.00 S: Manufacturer=PixArt S: Product=USB Optical Mouse C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=10ms T: Bus=03 Lev=01 Prnt=01 Port=08 Cnt=03 Dev#= 4 Spd=480 MxCh= 3 D: Ver= 2.10 Cls=09(hub ) Sub=00 Prot=02 MxPS=64 #Cfgs= 1 P: Vendor=0bc2 ProdID=ab44 Rev=48.85 S: Manufacturer=Seagate S: Product=Backup+ Hub S: SerialNumber=01CB0293B3EN C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=01 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=256ms I:* If#= 0 Alt= 1 #EPs= 1 Cls=09(hub ) Sub=00 Prot=02 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=256ms T: Bus=03 Lev=01 Prnt=01 Port=09 Cnt=04 Dev#= 5 Spd=480 MxCh= 3 D: Ver= 2.10 Cls=09(hub ) Sub=00 Prot=02 MxPS=64 #Cfgs= 1 P: Vendor=0bc2 ProdID=ab44 Rev=48.85 S: Manufacturer=Seagate S: Product=Backup+ Hub S: SerialNumber=01CB0247B2DB C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=01 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=256ms I:* If#= 0 Alt= 1 #EPs= 1 Cls=09(hub ) Sub=00 Prot=02 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=256ms T: Bus=03 Lev=01 Prnt=01 Port=10 Cnt=05 Dev#= 6 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=0184 Rev=84.13 S: Manufacturer=Generic S: Product=USB2.0-CRW S: SerialNumber=2010081884130 C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=ums-realtek E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms T: Bus=03 Lev=01 Prnt=01 Port=11 Cnt=06 Dev#= 7 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0a5c ProdID=21fb Rev= 1.12 S: Manufacturer=Broadcom Corp S: Product=BCM20702A0 S: SerialNumber=54271EF47473 C:* #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms I:* If#= 1 Alt= 0 #EPs= 2
[Kernel-packages] [Bug 2012649] [NEW] mlxbf_gige: need to replace SAUCE patches with upstream commits
Public bug reported:
SRU Justification:
[Impact]
The GIGE driver ("mlxbf_gige") in the Jammy repo contains SAUCE
patches that enable BlueField-3 support. This same functionality
is contained in upstream commits and Jammy repo should utilize them.
[Fix]
The BlueField-3 support will be provided in the form of a set
of upstream patches, to be sent in as a pull request.
[Test Case]
Should test on both BlueField-2 & BlueField-3:
Boot platform and bring up "oob_net0" interface properly
Test that network traffic works properly
[Regression Potential]
The upstream commits have been reviewed and tested well,
so there should be low risk of regression.
[Other]
n/a
** Affects: linux-bluefield (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2012649
Title:
mlxbf_gige: need to replace SAUCE patches with upstream commits
Status in linux-bluefield package in Ubuntu:
New
Bug description:
SRU Justification:
[Impact]
The GIGE driver ("mlxbf_gige") in the Jammy repo contains SAUCE
patches that enable BlueField-3 support. This same functionality
is contained in upstream commits and Jammy repo should utilize them.
[Fix]
The BlueField-3 support will be provided in the form of a set
of upstream patches, to be sent in as a pull request.
[Test Case]
Should test on both BlueField-2 & BlueField-3:
Boot platform and bring up "oob_net0" interface properly
Test that network traffic works properly
[Regression Potential]
The upstream commits have been reviewed and tested well,
so there should be low risk of regression.
[Other]
n/a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2012649/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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
Thanks, I think I'm now using 5.19.0-35 with the new driver. I'll monitor for crashes. Is there anything in particular I should look for in "journalctl -k -b"? -- 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 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 2007875] Re: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently
I attempted this and booted into kernel 5.19.0-32-generic however I then had no wifi at all. The option to connect no longer existed in the top right corner. Prior to this, it failed in the same way, with Microcode SW error detected, a second time today. It does seems like it happened less often but it's hard to prove that. I switched back to 5.15 for now so as to have a usable computer. -- 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 2007759] Re: Spotify freezes my entire system
I see the exact same issue with spotify, Ubuntu 22.04 and kernel: Linux atomic 5.19.0-35-generic #36~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 17 15:17:25 UTC 2 x86_64 x86_64 x86_64 GNU/Linux and I have a Lenovo P14s and CPU model name: AMD Ryzen 7 PRO 5850U with Radeon Graphics -- 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/2007759 Title: Spotify freezes my entire system Status in linux package in Ubuntu: Confirmed Bug description: When I open spotify and have it open for a while my system freezes and I need to hard reset afterwards. ubuntu 22.10 spotify version 1.1.84.716.gc5f8b819 The main error that I always get aren't included in any txt files but here is the one error I copy paste from askubuntu: retry page fault (src_id:0 ring:0 vmid:1 pasid:32776, for process spotify pid 13673 thread spotify:cs0 pid 13735) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800106a2 from IH client 0x12 (VMC) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140051 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: RW: 0x1 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32776, for process spotify pid 13673 thread spotify:cs0 pid 13735) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800106a2 from IH client 0x12 (VMC) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140051 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: RW: 0x1 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32776, for process spotify pid 13673 thread spotify:cs0 pid 13735) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800106a2 from IH client 0x12 (VMC) -- ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1576 F wireplumber /dev/snd/controlC0: adrian 1576 F wireplumber /dev/snd/seq:adrian 1573 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 18 20:11:39 2023 InstallationDate: Installed on 2023-01-27 (21 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 81W1 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=683321d2-f902-45fc-86c5-b0d4410e061a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2023-01-27 (21 days ago) dmi.bios.date: 04/18/2022 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: E8CN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ADA05 dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrE8CN34WW:bd04/18/2022:br1.34:efr1.34:svnLENOVO:pn81W1:pvrIdeaPad315ADA05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad315ADA05:skuLENOVO_MT_81W1_BU_idea_FM_IdeaPad315ADA05:
[Kernel-packages] [Bug 2009580] [NEW] Problems with Docker images with NFS/CIFS mounts into containers in linux-azure-5.4.0-1104
Public bug reported: Hi, As of linux-azure-5.4.0.1104 in Ubuntu Bionic (Azure) we are seeing Docker images fail to start / hang. These images mount NFS and CIFS shares into them as volumes, which I suspect might be related. I see many NFS-related changes in this new kernel version's changelog. These same containers work fine in linux-azure-5.4.0-1103. Upgrading to 1104 reproduces the behaviour. It would seem this kernel version has introduced either a bug or an incompatibility with our version of Docker. Docker version output: Server: Engine: Version: 20.10.12 API version: 1.41 (minimum version 1.12) Go version: go1.16.2 Git commit: 20.10.12-0ubuntu2~18.04.1 Built:Mon Apr 4 20:53:56 2022 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.5.9-0ubuntu1~18.04.2 GitCommit: runc: Version: 1.1.0-0ubuntu1~18.04.1 GitCommit: docker-init: Version: 0.19.0 GitCommit: I'm willing to help troubleshoot the issue if needed. Thanks ** Affects: linux-meta-azure-5.4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-azure-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/2009580 Title: Problems with Docker images with NFS/CIFS mounts into containers in linux-azure-5.4.0-1104 Status in linux-meta-azure-5.4 package in Ubuntu: New Bug description: Hi, As of linux-azure-5.4.0.1104 in Ubuntu Bionic (Azure) we are seeing Docker images fail to start / hang. These images mount NFS and CIFS shares into them as volumes, which I suspect might be related. I see many NFS-related changes in this new kernel version's changelog. These same containers work fine in linux-azure-5.4.0-1103. Upgrading to 1104 reproduces the behaviour. It would seem this kernel version has introduced either a bug or an incompatibility with our version of Docker. Docker version output: Server: Engine: Version: 20.10.12 API version: 1.41 (minimum version 1.12) Go version: go1.16.2 Git commit: 20.10.12-0ubuntu2~18.04.1 Built:Mon Apr 4 20:53:56 2022 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.5.9-0ubuntu1~18.04.2 GitCommit: runc: Version: 1.1.0-0ubuntu1~18.04.1 GitCommit: docker-init: Version: 0.19.0 GitCommit: I'm willing to help troubleshoot the issue if needed. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-azure-5.4/+bug/2009580/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
ing kernel.perf_event_max_sample_rate to 62500 $ uname -a Linux david-XPS-9320 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 x86_64 x86_64 x86_64 GNU/Linux -- 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 1874241] Re: iwlwifi intel ax201 crashing on intel nuc10i7fnh
Can we get a confirmation if this issue will be fixed at some point or can we get a workaround ? -- 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/1874241 Title: iwlwifi intel ax201 crashing on intel nuc10i7fnh Status in linux-firmware package in Ubuntu: Confirmed Bug description: The intel iwlwifi firmware will crash when you insert a device into the thunderbolt3 port, and this will be trigger probabilistically. wifi card model:Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x354 Firmware version: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17 Linux-firmware version: 1.187 thunderbolt3 chip model: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06) dmesg output: [ 103.777908] pcieport :00:1c.0: PME: Spurious native interrupt! [ 103.777918] pcieport :00:1c.0: PME: Spurious native interrupt! [ 104.118148] usb 4-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 104.147184] usb 4-1: New USB device found, idVendor=05e3, idProduct=0749, bcdDevice=15.32 [ 104.147190] usb 4-1: New USB device strings: Mfr=3, Product=4, SerialNumber=2 [ 104.147194] usb 4-1: Product: USB3.0 Card Reader [ 104.147197] usb 4-1: Manufacturer: Generic [ 104.147199] usb 4-1: SerialNumber: 1532 [ 104.183374] usb-storage 4-1:1.0: USB Mass Storage device detected [ 104.183952] scsi host3: usb-storage 4-1:1.0 [ 104.184172] usbcore: registered new interface driver usb-storage [ 104.187897] usbcore: registered new interface driver uas [ 105.217035] scsi 3:0:0:0: Direct-Access Generic STORAGE DEVICE 1532 PQ: 0 ANSI: 6 [ 105.217792] sd 3:0:0:0: Attached scsi generic sg1 type 0 [ 105.233978] sd 3:0:0:0: [sdb] Attached SCSI removable disk [ 109.998995] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 109.999102] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 109.999111] iwlwifi :00:14.3: Status: 0x0040, count: 6 [ 109.999119] iwlwifi :00:14.3: Loaded firmware version: 48.4fa0041f.0 [ 109.999128] iwlwifi :00:14.3: 0x4435 | ADVANCED_SYSASSERT [ 109.999135] iwlwifi :00:14.3: 0x008026F4 | trm_hw_status0 [ 109.999142] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 109.999148] iwlwifi :00:14.3: 0x004CA228 | branchlink2 [ 109.999154] iwlwifi :00:14.3: 0x0E26 | interruptlink1 [ 109.999161] iwlwifi :00:14.3: 0x0E26 | interruptlink2 [ 109.999168] iwlwifi :00:14.3: 0x000161A0 | data1 [ 109.999174] iwlwifi :00:14.3: 0xDEADBEEF | data2 [ 109.999180] iwlwifi :00:14.3: 0xDEADBEEF | data3 [ 109.999186] iwlwifi :00:14.3: 0xF90167B5 | beacon time [ 109.999192] iwlwifi :00:14.3: 0x51938809 | tsf low [ 109.999199] iwlwifi :00:14.3: 0x0010 | tsf hi [ 109.999205] iwlwifi :00:14.3: 0x | time gp1 [ 109.999211] iwlwifi :00:14.3: 0x064A1430 | time gp2 [ 109.999217] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 109.999224] iwlwifi :00:14.3: 0x0030 | uCode version major [ 109.999231] iwlwifi :00:14.3: 0x4FA0041F | uCode version minor [ 109.999239] iwlwifi :00:14.3: 0x0351 | hw version [ 109.999245] iwlwifi :00:14.3: 0x00C89004 | board version [ 109.999252] iwlwifi :00:14.3: 0x069E001C | hcmd [ 109.999259] iwlwifi :00:14.3: 0x8002 | isr0 [ 109.999265] iwlwifi :00:14.3: 0x0100 | isr1 [ 109.999271] iwlwifi :00:14.3: 0x08F2 | isr2 [ 109.999278] iwlwifi :00:14.3: 0x04C1FFCC | isr3 [ 109.999284] iwlwifi :00:14.3: 0x | isr4 [ 109.999290] iwlwifi :00:14.3: 0x069D001C | last cmd Id [ 109.999297] iwlwifi :00:14.3: 0x8B70 | wait_event [ 109.999304] iwlwifi :00:14.3: 0x4208 | l2p_control [ 109.999310] iwlwifi :00:14.3: 0x2020 | l2p_duration [ 109.999317] iwlwifi :00:14.3: 0x033F | l2p_mhvalid [ 109.999324] iwlwifi :00:14.3: 0x00E6 | l2p_addr_match [ 109.999331] iwlwifi :00:14.3: 0x0009 | lmpm_pmg_sel [ 109.999337] iwlwifi :00:14.3: 0x | timestamp [ 109.999344] iwlwifi :00:14.3: 0xB8DC | flow_handler [ 109.999391] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 109.999398] iwlwifi :00:14.3: Status: 0x0040, count: 7 [ 109.999406] iwlwifi :00:14.3: 0x2070 | NMI_INTERRUPT_LMAC_FATAL [ 109.999413] iwlwifi :00:14.3: 0x | umac branchlink1 [ 109.999420] iwlwifi :00:14.3: 0xC008D49C | umac branchlink2 [ 109.999427] iwlwifi :00:14.3: 0x8048DBD2 | umac interruptlink1 [ 109.999434] iwlwifi :00:14.3: 0x8048DBD2 | umac interruptlink2 [ 109.999441] iwlwifi :00:14.3: 0x0400 | umac data1 [ 109.999447] iwlwifi :00:14.3: 0x8048DBD2 | umac data2 [ 109.999454] iwlwifi :00:14.3: 0x | umac data3 [
[Kernel-packages] [Bug 2008706] Re: Intel Wi-Fi 6 AX201 failing in 22.04.2 LTS
This has been going on for a while but since the last linux firmware update the ax201 card is not working at all. -- 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/2008706 Title: Intel Wi-Fi 6 AX201 failing in 22.04.2 LTS Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: [3.837973] audit: type=1400 audit(1677506792.544:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_gr off" pid=522 comm="apparmor_parser" [3.960935] iwlwifi :00:14.3: CSR_RESET = 0x10 [3.960965] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x0 [3.961034] iwlwifi :00:14.3: value [iter 0]: 0x [3.961098] iwlwifi :00:14.3: value [iter 1]: 0x [3.961162] iwlwifi :00:14.3: value [iter 2]: 0x [3.961222] iwlwifi :00:14.3: value [iter 3]: 0x [3.961291] iwlwifi :00:14.3: value [iter 4]: 0x [3.961354] iwlwifi :00:14.3: value [iter 5]: 0x [3.961412] iwlwifi :00:14.3: value [iter 6]: 0x [3.961468] iwlwifi :00:14.3: value [iter 7]: 0x [3.961533] iwlwifi :00:14.3: value [iter 8]: 0x [3.961584] iwlwifi :00:14.3: value [iter 9]: 0x [3.961633] iwlwifi :00:14.3: value [iter 10]: 0x [3.961683] iwlwifi :00:14.3: value [iter 11]: 0x [3.961741] iwlwifi :00:14.3: value [iter 12]: 0x [3.961790] iwlwifi :00:14.3: value [iter 13]: 0x [3.961859] iwlwifi :00:14.3: value [iter 14]: 0x [3.961879] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x1 [3.961949] iwlwifi :00:14.3: value [iter 0]: 0x [3.962012] iwlwifi :00:14.3: value [iter 1]: 0x [3.962073] iwlwifi :00:14.3: value [iter 2]: 0x [3.962133] iwlwifi :00:14.3: value [iter 3]: 0x [3.962213] iwlwifi :00:14.3: value [iter 4]: 0x [3.962279] iwlwifi :00:14.3: value [iter 5]: 0x [3.962339] iwlwifi :00:14.3: value [iter 6]: 0x [3.962399] iwlwifi :00:14.3: value [iter 7]: 0x [3.962466] iwlwifi :00:14.3: value [iter 8]: 0x [3.962528] iwlwifi :00:14.3: value [iter 9]: 0x [3.962590] iwlwifi :00:14.3: value [iter 10]: 0x [3.962655] iwlwifi :00:14.3: value [iter 11]: 0x [3.962723] iwlwifi :00:14.3: value [iter 12]: 0x [3.962786] iwlwifi :00:14.3: value [iter 13]: 0x [3.962842] iwlwifi :00:14.3: value [iter 14]: 0x [3.962853] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x6 [3.962906] iwlwifi :00:14.3: value [iter 0]: 0x [3.962971] iwlwifi :00:14.3: value [iter 1]: 0x [3.963028] iwlwifi :00:14.3: value [iter 2]: 0x [3.963074] iwlwifi :00:14.3: value [iter 3]: 0x [3.963488] iwlwifi :00:14.3: value [iter 4]: 0x [3.963546] iwlwifi :00:14.3: value [iter 5]: 0x [3.963595] iwlwifi :00:14.3: value [iter 6]: 0x [3.963643] iwlwifi :00:14.3: value [iter 7]: 0x [3.963695] iwlwifi :00:14.3: value [iter 8]: 0x [3.963771] iwlwifi :00:14.3: value [iter 9]: 0x [3.963829] iwlwifi :00:14.3: value [iter 10]: 0x [3.963891] iwlwifi :00:14.3: value [iter 11]: 0x [3.963951] iwlwifi :00:14.3: value [iter 12]: 0x [3.964019] iwlwifi :00:14.3: value [iter 13]: 0x [3.964089] iwlwifi :00:14.3: value [iter 14]: 0x [3.964118] iwlwifi :00:14.3: Host monitor block 0x22 vector 0x0 [3.964186] iwlwifi :00:14.3: value [iter 0]: 0x [3.964237] iwlwifi: probe of :00:14.3 failed with error -110 [3.974367] AVX2 version of gcm_enc/dec engaged. [3.974401] AES CTR mode by8 optimization enabled ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 27 14:11:18 2023 InstallationDate: Installed on 2022-06-01 (271 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage
[Kernel-packages] [Bug 2008706] [NEW] Intel Wi-Fi 6 AX201 failing in 22.04.2 LTS
Public bug reported: [3.837973] audit: type=1400 audit(1677506792.544:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_gr off" pid=522 comm="apparmor_parser" [3.960935] iwlwifi :00:14.3: CSR_RESET = 0x10 [3.960965] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x0 [3.961034] iwlwifi :00:14.3: value [iter 0]: 0x [3.961098] iwlwifi :00:14.3: value [iter 1]: 0x [3.961162] iwlwifi :00:14.3: value [iter 2]: 0x [3.961222] iwlwifi :00:14.3: value [iter 3]: 0x [3.961291] iwlwifi :00:14.3: value [iter 4]: 0x [3.961354] iwlwifi :00:14.3: value [iter 5]: 0x [3.961412] iwlwifi :00:14.3: value [iter 6]: 0x [3.961468] iwlwifi :00:14.3: value [iter 7]: 0x [3.961533] iwlwifi :00:14.3: value [iter 8]: 0x [3.961584] iwlwifi :00:14.3: value [iter 9]: 0x [3.961633] iwlwifi :00:14.3: value [iter 10]: 0x [3.961683] iwlwifi :00:14.3: value [iter 11]: 0x [3.961741] iwlwifi :00:14.3: value [iter 12]: 0x [3.961790] iwlwifi :00:14.3: value [iter 13]: 0x [3.961859] iwlwifi :00:14.3: value [iter 14]: 0x [3.961879] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x1 [3.961949] iwlwifi :00:14.3: value [iter 0]: 0x [3.962012] iwlwifi :00:14.3: value [iter 1]: 0x [3.962073] iwlwifi :00:14.3: value [iter 2]: 0x [3.962133] iwlwifi :00:14.3: value [iter 3]: 0x [3.962213] iwlwifi :00:14.3: value [iter 4]: 0x [3.962279] iwlwifi :00:14.3: value [iter 5]: 0x [3.962339] iwlwifi :00:14.3: value [iter 6]: 0x [3.962399] iwlwifi :00:14.3: value [iter 7]: 0x [3.962466] iwlwifi :00:14.3: value [iter 8]: 0x [3.962528] iwlwifi :00:14.3: value [iter 9]: 0x [3.962590] iwlwifi :00:14.3: value [iter 10]: 0x [3.962655] iwlwifi :00:14.3: value [iter 11]: 0x [3.962723] iwlwifi :00:14.3: value [iter 12]: 0x [3.962786] iwlwifi :00:14.3: value [iter 13]: 0x [3.962842] iwlwifi :00:14.3: value [iter 14]: 0x [3.962853] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x6 [3.962906] iwlwifi :00:14.3: value [iter 0]: 0x [3.962971] iwlwifi :00:14.3: value [iter 1]: 0x [3.963028] iwlwifi :00:14.3: value [iter 2]: 0x [3.963074] iwlwifi :00:14.3: value [iter 3]: 0x [3.963488] iwlwifi :00:14.3: value [iter 4]: 0x [3.963546] iwlwifi :00:14.3: value [iter 5]: 0x [3.963595] iwlwifi :00:14.3: value [iter 6]: 0x [3.963643] iwlwifi :00:14.3: value [iter 7]: 0x [3.963695] iwlwifi :00:14.3: value [iter 8]: 0x [3.963771] iwlwifi :00:14.3: value [iter 9]: 0x [3.963829] iwlwifi :00:14.3: value [iter 10]: 0x [3.963891] iwlwifi :00:14.3: value [iter 11]: 0x [3.963951] iwlwifi :00:14.3: value [iter 12]: 0x [3.964019] iwlwifi :00:14.3: value [iter 13]: 0x [3.964089] iwlwifi :00:14.3: value [iter 14]: 0x [3.964118] iwlwifi :00:14.3: Host monitor block 0x22 vector 0x0 [3.964186] iwlwifi :00:14.3: value [iter 0]: 0x [3.964237] iwlwifi: probe of :00:14.3 failed with error -110 [3.974367] AVX2 version of gcm_enc/dec engaged. [3.974401] AES CTR mode by8 optimization enabled ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 27 14:11:18 2023 InstallationDate: Installed on 2022-06-01 (271 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2008706 Title: Intel Wi-Fi 6 AX201 failing in 22.04.2 LTS Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: [3.837973] audit: type=1400 audit(1677506792.544:10): apparmor="STATUS" operation="profile_load"
[Kernel-packages] [Bug 1485246] Re: Backlight issue - Samsung Chronos 7 (model - NP770Z5E)
@Erwin (erwin-gaubitzer-6) Spot on - thank you. -- 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/1485246 Title: Backlight issue - Samsung Chronos 7 (model - NP770Z5E) Status in linux package in Ubuntu: Confirmed Bug description: Control of screen backlight is broken with a default clean install of Ubuntu 15.04 on my Samsung Series 7 Laptop (NP770Z5E). Setting kernel parameter 'acpi_backlight=vendor' fixes the issue after two reboots. Debugging information attached as per - https://wiki.ubuntu.com/Kernel/Debugging/Backlight ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1699 F pulseaudio Date: Sat Aug 15 21:36:20 2015 HibernationDevice: RESUME=UUID=c4899b44-3e19-4e62-921d-cf0a1cef97ec InstallationDate: Installed on 2015-08-12 (3 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: SAMSUNG ELECTRONICS CO., LTD. 770Z5E/780Z5E ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=5a02817b-1f9b-4abc-93a3-b10d5d9278ed ro quiet splash acpi_backlight=vendor vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P05ABU.142.130905.SK dmi.board.asset.tag: No Asset Tag dmi.board.name: NP770Z5E-S02UK dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ABU.142.130905.SK:bd09/05/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn770Z5E/780Z5E:pvrP05ABU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP770Z5E-S02UK:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 770Z5E/780Z5E dmi.product.version: P05ABU dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485246/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007853] Re: Intel video driver i915 - Repeated GPU HANG's - Xorg use a lot of CPU
ng else. Nothing in xorg log. It surprising me to keep the problem in grub menu so I think is more an hardware problem triggered or a driver error. Anyone have an idea of what it could be ? Thanks in advance Have a good day. David To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007853/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007853] Re: Intel video driver i915 - Repeated GPU HANG's - Xorg use a lot of CPU
slog nothing else. Nothing in xorg log. It surprising me to keep the problem in grub menu so I think is more an hardware problem triggered or a driver error. Anyone have an idea of what it could be ? Thanks in advance Have a good day. David To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007853/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007853] Re: Intel video driver i915 - Repeated GPU HANG's - Xorg use a lot of CPU
It arrive to Direct 3D 7 or 8 or 9 the problem start. Before this, all is ok, fluid. (DXDiag 7, 8 or 9 are never are fluid, but I'm not sure VMWare work well with this old version) I think it normal at a moment to saturate the CPU or GPU, here it seem to be the case, the YouTube video and vlc video skip frame and freeze and jerk. But when the test is finish, it will go back at a normally state few time after, I think. Now the system is not fluid, ALT+TAB lag, jerk, changing tab on firefox it very long, system monitor is very long. All graphical software is very long. Video are not fluid. Xorg start taking a lot of CPU even if nothing is done. If I suspend system and resume it, it is better but not fluid. If I hibernate (suspend to disk) with an hardware reset it is very fluid. Sometime it seem to be totally normal. Before do anything I see with cat /proc/interrupts a lot of interrupts on IR-PCI-MSI 327680-edge xhci_hcd. For example : 325180. After an hibernation I have "only" 102178 for xhci_hcd. When I restart before any suspend, I can have the bios screen very long to appear and the grub menu not fluid, very slow. I thinks I'm keep the bug some time after reset. On forum people deal with lost of video sync. I think it can be anything that. With a power off it work normally, so the hardware reset have an impact. In dmesg I only have : (when the problem start) [ 5546.086667] x86/split lock detection: #AC: main-svga/14494 took a split_lock trap at address: 0x559ce0ea2e3d [ 5546.291794] x86/split lock detection: #AC: vmx-svga/14491 took a split_lock trap at address: 0x563fc34febb7 [ 5546.310412] x86/split lock detection: #AC: main-mks/14493 took a split_lock trap at address: 0x559ce0ea30a7 nothing else. VLC have this error : [h264 @ 0x7fa854c9e300] get_buffer() failed [h264 @ 0x7fa854c9e300] thread_get_buffer() failed [h264 @ 0x7fa854c9e300] decode_slice_header error [h264 @ 0x7fa854c9e300] no frame! [h264 @ 0x7fa854d8f3c0] get_buffer() failed [h264 @ 0x7fa854d8f3c0] thread_get_buffer() failed [h264 @ 0x7fa854d8f3c0] decode_slice_header error [h264 @ 0x7fa854d8f3c0] no frame! [5560d6746a70] vlcpulse audio output error: digital pass-through stream connection failure: Non pris en charge [5560d6746a70] main audio output error: module not functional [7fa854cebd50] main decoder error: failed to create audio output [5560d6746a70] vlcpulse audio output error: digital pass-through stream connection failure: Non pris en charge [5560d6746a70] main audio output error: module not functional [7fa854cebd50] main decoder error: failed to create audio output [5560d6746a70] main audio output error: cannot add user visualization "any" (skipped) [7fa854c19430] avcodec decoder: Using Intel iHD driver for Intel(R) Gen Graphics - 22.3.1 () for hardware decoding I can see it on syslog nothing else. Nothing in xorg log. It surprising me to keep the problem in grub menu so I think is more an hardware problem triggered or a driver error. Anyone have an idea of what it could be ? Thanks in advance Have a good day. David To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007853/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007853] Re: Intel video driver i915 - Repeated GPU HANG's - Xorg use a lot of CPU
iver error. Anyone have an idea of what it could be ? Thanks in advance Have a good day. David To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007853/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007853] Re: Intel video driver i915 - Repeated GPU HANG's - Xorg use a lot of CPU
hanks in advance
Have a good day.
David
--
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/2007853
Title:
Intel video driver i915 - Repeated GPU HANG's - Xorg use a lot of CPU
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hello,
I think my problem is link to firmware package or make hardware error.
Lot of people have problem with the i915. I have take lot of time to
configure it correctly.
Today my configuration is ok with 5.19.0-32-generic, it seem the same with
5.15.0-60.
I'm on Ubuntu 22.04 LTS ("The Jammy Jellyfish")
I'm not sure when the problem have really started, but I propose you to
firstly see the problem in the global way.
I'm not sure It wan really depend on a kernel or a configuration. My
BIOS is up to date and all the system .
So today my i915 integrated card work well with my 11th Gen Intel® Core™ i5.
I have configure it, all drivers seem to be ok. VMWare work with accelerate
3D graphics, VLC work with OpenGL Output and hardware VDPAU or VD-API. Mesa
seem to be ok, Firefox work with hardware video acceleration. glmark2 and
glxgears is ok to. Xorg use very few CPU.
ALT+TAB is very speed to change between applications. TAB changing on Firefox
is very speed to.
Videos are fluid and use few CPU.
Intel_GPU_top show that vlc use hardware.
But at an aleatory time or with using a lot of CPU/GPU a problem
arrive !
My test process is VLC with a 1080p movie with a good encoding 5Go for an 1
hours.
Firefox with a 720p or 1080 video on YouTube in incrustation
VMWare with a Windows XP VM testing Dxdiag.
The 3 is visible partially at the same time on my screen.
I'm launching the 3, and I launch dxdiag video test on the VM. When It arrive
to Direct 3D 7 or 8 or 9 the problem start.
Before this, all is ok, fluid. (DXDiag 7, 8 or 9 are never are fluid, but I'm
not sure VMWare work well with this old version)
I think it normal at a moment to saturate the CPU or GPU, here it seem to be
the case, the YouTube video and vlc video skip frame and freeze and jerk.
But when the test is finish, it will go back at a normally state few time
after, I think.
Now the system is not fluid, ALT+TAB lag, jerk, changing tab on firefox it
very long, system monitor is very long. All graphical software is very long.
Video are not fluid.
Xorg start taking a lot of CPU even if nothing is done.
If I suspend system and resume it, it is better but not fluid.
If I hibernate (suspend to disk) with an hardware reset it is very fluid.
Sometime it seem to be totally normal.
Before do anything I see with cat /proc/interrupts a lot of interrupts on
IR-PCI-MSI 327680-edge xhci_hcd. For example : 325180.
After an hibernation I have "only" 102178 for xhci_hcd.
When I restart before any suspend, I can have the bios screen very long to
appear and the grub menu not fluid, very slow. I thinks I'm keep the bug some
time after reset.
On forum people deal with lost of video sync. I think it can be anything that.
With a power off it work normally, so the hardware reset have an impact.
In dmesg I only have : (when the problem start)
[ 5546.086667] x86/split lock detection: #AC: main-svga/14494 took a
split_lock trap at address: 0x559ce0ea2e3d
[ 5546.291794] x86/split lock detection: #AC: vmx-svga/14491 took a
split_lock trap at address: 0x563fc34febb7
[ 5546.310412] x86/split lock detection: #AC: main-mks/14493 took a
split_lock trap at address: 0x559ce0ea30a7
nothing else.
VLC have this error :
[h264 @ 0x7fa854c9e300] get_buffer() failed
[h264 @ 0x7fa854c9e300] thread_get_buffer() failed
[h264 @ 0x7fa854c9e300] decode_slice_header error
[h264 @ 0x7fa854c9e300] no frame!
[h264 @ 0x7fa854d8f3c0] get_buffer() failed
[h264 @ 0x7fa854d8f3c0] thread_get_buffer() failed
[h264 @ 0x7fa854d8f3c0] decode_slice_header error
[h264 @ 0x7fa854d8f3c0] no frame!
[5560d6746a70] vlcpulse audio output error: digital pass-through stream
connection failure: Non pris en charge
[5560d6746a70] main audio output error: module not functional
[7fa854cebd50] main decoder error: failed to create audio output
[5560d6746a70] vlcpulse audio output error: digital pass-through stream
connection failure: Non pris en charge
[5560d6746a70] main audio output error: module not functional
[7fa854cebd50] main decoder error: failed to create audio output
[5560d6746a70] main audio output error: cannot add user visualization
"any" (skipped)
[7fa854c19430] avcodec decoder: Using Intel iHD driver for Intel(R) Gen
Graphics - 22.3.1 () for hardware decoding
I can see it on syslog nothing else.
Nothing in xorg log.
It surprising me to keep the problem in grub menu so I think is more an
hardware problem triggered or a driver error.
Anyone have an idea
[Kernel-packages] [Bug 2007853] [NEW] Intel video driver i915 - Repeated GPU HANG's - Xorg use a lot of CPU
Public bug reported: Hello, I think my problem is link to firmware package or make hardware error. Lot of people have problem with the i915. I have take lot of time to configure it correctly. Today my configuration is ok with 5.19.0-32-generic, it seem the same with 5.15.0-60. I'm not sure when the problem have really started, but I propose you to firstly see the problem in the global way. I'm not sure It wan really depend on a kernel or a configuration. My BIOS is up to date and all the system . So today my i915 integrated card work well with my 11th Gen Intel® Core™ i5. I have configure it, all drivers seem to be ok. VMWare work with accelerate 3D graphics, VLC work with OpenGL Output and hardware VDPAU or VD-API. Mesa seem to be ok, Firefox work with hardware video acceleration. glmark2 and glxgears is ok to. Xorg use very few CPU. ALT+TAB is very speed to change between applications. TAB changing on Firefox is very speed to. Videos are fluid and use few CPU. Intel_GPU_top show that vlc use hardware. But at an aleatory time or with using a lot of CPU/GPU a problem arrive ! My test process is VLC with a 1080p movie with a good encoding 5Go for an 1 hours. Firefox with a 720p or 1080 video on YouTube in incrustation VMWare with a Windows XP VM testing Dxdiag. The 3 is visible partially at the same time on my screen. I'm launching the 3, and I launch dxdiag video test on the VM. When It arrive to Direct 3D 7 or 8 or 9 the problem start. Before this, all is ok, fluid. (DXDiag 7, 8 or 9 are never are fluid, but I'm not sure VMWare work well with this old version) I think it normal at a moment to saturate the CPU or GPU, here it seem to be the case, the YouTube video and vlc video skip frame and freeze and jerk. But when the test is finish, it will go back at a normally state few time after, I think. Now the system is not fluid, ALT+TAB lag, jerk, changing tab on firefox it very long, system monitor is very long. All graphical software is very long. Video are not fluid. Xorg start taking a lot of CPU even if nothing is done. If I suspend system and resume it, it is better but not fluid. If I hibernate (suspend to disk) with an hardware reset it is very fluid. Sometime it seem to be totally normal. Before do anything I see with cat /proc/interrupts a lot of interrupts on IR-PCI-MSI 327680-edge xhci_hcd. For example : 325180. After an hibernation I have "only" 102178 for xhci_hcd. When I restart before any suspend, I can have the bios screen very long to appear and the grub menu not fluid, very slow. I thinks I'm keep the bug some time after reset. On forum people deal with lost of video sync. I think it can be anything that. With a power off it work normally, so the hardware reset have an impact. In dmesg I only have : (when the problem start) [ 5546.086667] x86/split lock detection: #AC: main-svga/14494 took a split_lock trap at address: 0x559ce0ea2e3d [ 5546.291794] x86/split lock detection: #AC: vmx-svga/14491 took a split_lock trap at address: 0x563fc34febb7 [ 5546.310412] x86/split lock detection: #AC: main-mks/14493 took a split_lock trap at address: 0x559ce0ea30a7 nothing else. VLC have this error : [h264 @ 0x7fa854c9e300] get_buffer() failed [h264 @ 0x7fa854c9e300] thread_get_buffer() failed [h264 @ 0x7fa854c9e300] decode_slice_header error [h264 @ 0x7fa854c9e300] no frame! [h264 @ 0x7fa854d8f3c0] get_buffer() failed [h264 @ 0x7fa854d8f3c0] thread_get_buffer() failed [h264 @ 0x7fa854d8f3c0] decode_slice_header error [h264 @ 0x7fa854d8f3c0] no frame! [5560d6746a70] vlcpulse audio output error: digital pass-through stream connection failure: Non pris en charge [5560d6746a70] main audio output error: module not functional [7fa854cebd50] main decoder error: failed to create audio output [5560d6746a70] vlcpulse audio output error: digital pass-through stream connection failure: Non pris en charge [5560d6746a70] main audio output error: module not functional [7fa854cebd50] main decoder error: failed to create audio output [5560d6746a70] main audio output error: cannot add user visualization "any" (skipped) [7fa854c19430] avcodec decoder: Using Intel iHD driver for Intel(R) Gen Graphics - 22.3.1 () for hardware decoding I can see it on syslog nothing else. Nothing in xorg log. It surprising me to keep the problem in grub menu so I think is more an hardware problem triggered or a driver error. Anyone have an idea of what it could be ? Thanks in advance Have a good day. David ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: i915 xorg -- 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/2007853 Title: Intel video driver i915 - Repeated GPU HANG's - Xorg use a lot of CPU Status in linux package in Ubuntu: New Bug description: Hello, I think my problem is link
[Kernel-packages] [Bug 1962485] Re: Kernel Crash [general protection fault: 0000 [#1] SMP NOPTI]
Maybe the same as https://lore.kernel.org/lkml/CANn89iJxiV_-g6n60aeA=mO=DYwGV9VdJswHP4pc- vwq_ug...@mail.gmail.com/T/ ? -- 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/1962485 Title: Kernel Crash [general protection fault: [#1] SMP NOPTI] Status in linux package in Ubuntu: Confirmed Bug description: Hi, I am running openstack xena release on ubuntu focal. Today my compute node running ubuntu focal crashed with due to kernel and dump has been generated in /var/crash/. Below is the kernel trace in crash dump. [455151.890114] general protection fault: [#1] SMP NOPTI [455151.890285] CPU: 43 PID: 83232 Comm: qemu-system-x86 Kdump: loaded Tainted: G OE 5.4.0-88-generic #99-Ubuntu [455151.890612] Hardware name: Dell Inc. PowerEdge R6525/X, BIOS 2.5.6 10/06/2021 [455151.890842] RIP: 0010:count_subheaders.part.0+0x26/0x60 [455151.890998] Code: 00 00 00 90 0f 1f 44 00 00 48 83 3f 00 74 4d 55 48 89 e5 41 55 45 31 ed 41 54 45 31 e4 53 48 89 fb 48 8b 7b 18 48 85 ff 74 23 <48> 83 3f 00 74 25 e8 cf ff ff ff 41 01 c5 48 83 c3 40 48 83 3b 00 [455151.891552] RSP: 0018:a6b477487b88 EFLAGS: 00010202 [455151.891707] RAX: RBX: 9387c594f280 RCX: [455151.891918] RDX: 0060 RSI: 9390702a72c0 RDI: 0314a8c0f1b16f3e [455151.892130] RBP: a6b477487ba0 R08: R09: bc6ed7f0 [455151.892341] R10: a6b477487cd0 R11: 0001 R12: [455151.892552] R13: R14: 9391e5684000 R15: bd5f9880 [455151.892767] FS: 7f69950c75c0() GS:9391feac() knlGS: [455151.893016] CS: 0010 DS: ES: CR0: 80050033 [455151.893207] CR2: 7f61e9e45000 CR3: 017c54afa000 CR4: 00340ee0 [455151.893434] Call Trace: [455151.893514] count_subheaders.part.0+0x31/0x60 [455151.893646] unregister_sysctl_table+0x30/0x90 [455151.893781] unregister_net_sysctl_table+0xe/0x10 [455151.893922] __devinet_sysctl_unregister.isra.0+0x2c/0x60 [455151.894082] devinet_sysctl_unregister+0x29/0x40 [455151.894220] inetdev_event+0x1e8/0x560 [455151.894334] ? skb_dequeue+0x5f/0x70 [455151.89] notifier_call_chain+0x55/0x80 [455151.894565] ? notifier_call_chain+0x55/0x80 [455151.894693] raw_notifier_call_chain+0x16/0x20 [455151.894829] call_netdevice_notifiers_info+0x2e/0x60 [455151.894983] ? tun_show_owner+0x60/0x60 [455151.895098] rollback_registered_many+0x36e/0x520 [455151.895239] unregister_netdevice_queue+0x94/0x120 [455151.895383] __tun_detach+0x421/0x430 [455151.895495] tun_chr_close+0x3a/0x70 [455151.895605] __fput+0xcc/0x260 [455151.895698] fput+0xe/0x10 [455151.895792] task_work_run+0x8f/0xb0 [455151.895903] exit_to_usermode_loop+0x131/0x160 [455151.896036] do_syscall_64+0x163/0x190 [455151.896150] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [455151.896302] RIP: 0033:0x7f69965ba3fb [455151.896410] Code: 03 00 00 00 0f 05 48 3d 00 f0 ff ff 77 41 c3 48 83 ec 18 89 7c 24 0c e8 f3 fb ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2f 44 89 c7 89 44 24 0c e8 31 fc ff ff 8b 44 [455151.896975] RSP: 002b:7ffdff14b350 EFLAGS: 0293 ORIG_RAX: 0003 [455151.897201] RAX: RBX: 557fe0875e50 RCX: 7f69965ba3fb [455151.897412] RDX: 557fe0748f40 RSI: 0001 RDI: 002b [455151.897637] RBP: 557fe0887460 R08: R09: [455151.904390] R10: 0032 R11: 0293 R12: 557fe0875e50 [455151.911165] R13: 0001 R14: 557fe09efc10 R15: 557fe0747900 I didn't find any documented details on kernel 5.4 for this bug. I have uploaded the logs via ubuntu-bug linux command. # uname -a Linux kvm03-a1-r01-khi04.rapid.pk 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 17:29:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 5.4.0-88.99-generic 5.4.140 I am using Dell R6525 with EPYC 7532 CPUs. Let me know if there is there are more information needed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-88-generic 5.4.0-88.99 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 28 17:38 seq crw-rw 1 root audio 116, 33 Feb 28 17:38 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Mon Feb 28
[Kernel-packages] [Bug 1999731] Re: disk stress test failing with code 7
The log was attached ** Attachment added: "stress-ng_0.15.04-1~j_amd64_log.txt" https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1999731/+attachment/5647719/+files/stress-ng_0.15.04-1~j_amd64_log.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1999731 Title: disk stress test failing with code 7 Status in Stress-ng: In Progress Status in linux package in Ubuntu: In Progress Status in stress-ng package in Ubuntu: In Progress Bug description: Since mid of November we see lots of disk stress test failing with multiple Ubuntu kernel e.g. bionic-hwe, focal, focal-hwe. Most of them are with lockofd stressor and system are still alive after stress test. 05 Nov 08:51: Running stress-ng lockofd stressor for 240 seconds... ** stress-ng exited with code 7 To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1999731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999731] Re: disk stress test failing with code 7
Test with stress-ng_0.15.04-1~j_amd64 + ubunut 22.04(5.15.0-58-generic) + Micron_7450_MTFDKCB3T8TFR -> Passed -- 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/1999731 Title: disk stress test failing with code 7 Status in Stress-ng: In Progress Status in linux package in Ubuntu: In Progress Status in stress-ng package in Ubuntu: In Progress Bug description: Since mid of November we see lots of disk stress test failing with multiple Ubuntu kernel e.g. bionic-hwe, focal, focal-hwe. Most of them are with lockofd stressor and system are still alive after stress test. 05 Nov 08:51: Running stress-ng lockofd stressor for 240 seconds... ** stress-ng exited with code 7 To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1999731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
I've tested the patch on kernel 5.15.0-57.63 and it solves the issue for me. Aleksandr - Andrea asked you in your kernel-team thread to rebase the patch on master-next, hopefully if you can do this it'll be accepted. Keen to see this issue fixed in jammy as it's breaking Docker+Sysbox containers too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1990849 Title: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54 Status in linux package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in zfs-linux source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Status in zfs-linux source package in Kinetic: Confirmed Bug description: Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS are broken. Reproducer steps: ``` sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo lxd init --auto lxc storage create zfs zfs lxc launch images:ubuntu/jammy c1 -s zfs lxc exec c1 -- touch /root/foo touch: cannot touch '/root/foo': Value too large for defined data type ``` Expected result can be achieved by disabling shiftfs: ``` sudo snap set lxd shiftfs.enable=false sudo systemctl reload snap.lxd.daemon lxc launch images:ubuntu/jammy c2 -s zfs lxc exec c2 -- touch /root/foo lxc exec c2 -- ls -la /root/foo -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo ``` Kernel 5.15.0-47-generic does not exhibit this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2240 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 14:55:52 2022 InstallationDate: Installed on 2022-03-04 (205 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) MachineType: LENOVO 20R1000RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET40W(1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrN2QET40W(1.34):bd04/15/2021:br1.34:efr1.15:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002513] [NEW] Since kernel 4.15.0-201, ls prints an error message for every btrfs read-only file system
Public bug reported: Since installing the latest kernel update on bionic (4.15.0-201), ls prints an error message for every btrfs read-only file system in the target directory. How to reproduce: On a btrfs file system in any directory, run: - sudo btrfs su cr testsubvol - sudo btrfs su sn -r testsubvol testsubvol2 - ls -l Output of "ls -l" is: ls: testsubvol2: Read-only file system total 0 drwxr-xr-x 1 root root 0 Jan 11 11:37 testsubvol drwxr-xr-x 1 root root 0 Jan 11 11:37 testsubvol2 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "report.tar" https://bugs.launchpad.net/bugs/2002513/+attachment/5640641/+files/report.tar -- 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/2002513 Title: Since kernel 4.15.0-201, ls prints an error message for every btrfs read-only file system Status in linux package in Ubuntu: New Bug description: Since installing the latest kernel update on bionic (4.15.0-201), ls prints an error message for every btrfs read-only file system in the target directory. How to reproduce: On a btrfs file system in any directory, run: - sudo btrfs su cr testsubvol - sudo btrfs su sn -r testsubvol testsubvol2 - ls -l Output of "ls -l" is: ls: testsubvol2: Read-only file system total 0 drwxr-xr-x 1 root root 0 Jan 11 11:37 testsubvol drwxr-xr-x 1 root root 0 Jan 11 11:37 testsubvol2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002513/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999731] Re: disk stress test failing with code 7
Test with stress-ng_0.13.12-2ubuntu1_amd64.deb -> Passed 27 Dec 03:53: Running stress-ng locka stressor for 240 seconds... stress-ng: info: [3300189] setting to a 240 second (4 mins, 0.00 secs) run per stressor stress-ng: info: [3300189] dispatching hogs: 176 locka stress-ng: info: [3300189] successful run completed in 240.09s (4 mins, 0.09 secs) 27 Dec 03:57: Running stress-ng lockf stressor for 240 seconds... stress-ng: info: [3300551] setting to a 240 second (4 mins, 0.00 secs) run per stressor stress-ng: info: [3300551] dispatching hogs: 176 lockf stress-ng: info: [3300551] successful run completed in 240.10s (4 mins, 0.10 secs) 27 Dec 04:01: Running stress-ng lockofd stressor for 240 seconds... stress-ng: info: [3300914] setting to a 240 second (4 mins, 0.00 secs) run per stressor stress-ng: info: [3300914] dispatching hogs: 176 lockofd stress-ng: info: [3300914] successful run completed in 240.09s (4 mins, 0.09 secs) -- 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/1999731 Title: disk stress test failing with code 7 Status in Stress-ng: In Progress Status in linux package in Ubuntu: In Progress Status in stress-ng package in Ubuntu: In Progress Bug description: Since mid of November we see lots of disk stress test failing with multiple Ubuntu kernel e.g. bionic-hwe, focal, focal-hwe. Most of them are with lockofd stressor and system are still alive after stress test. 05 Nov 08:51: Running stress-ng lockofd stressor for 240 seconds... ** stress-ng exited with code 7 To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1999731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981590] Re: Kernel 5.15 hangs at "Loading initial ramdisk"
FWIW I'm now running Ubuntu 22.04 in Legacy mode and finding the workaround satisfactory. ls -lh /boot/initrd* lrwxrwxrwx 1 root root 28 Dec 1 13:56 /boot/initrd.img -> initrd.img-5.15.0-56-generic -rw-r--r-- 1 root root 107M Nov 30 11:46 /boot/initrd.img-5.15.0-53-generic -rw-r--r-- 1 root root 107M Dec 1 13:56 /boot/initrd.img-5.15.0-56-generic lrwxrwxrwx 1 root root 28 Dec 1 13:56 /boot/initrd.img.old -> initrd.img-5.15.0-53-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1981590 Title: Kernel 5.15 hangs at "Loading initial ramdisk" Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Bug description: Updated from kernel 5.13 to 5.15 today. After rebooting the system hangs at "Loading ramdisk". I reverted to 5.13 and it started properly. More detail on the way. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 13 14:48:42 2022 InstallationDate: Installed on 2021-01-06 (553 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1981590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)
I have this issue after suspend/resume on Ubuntu 20.04 LTS, kernel 5.15.0, Dell Precision 5540 with an Intel Core i9-9980HK processor. lsusb shows the device: Bus 001 Device 025: ID 8087:0029 Intel Corp Which is an Intel AX200 Bluetooth wireless chip. Suspending and resuming my laptop once more fixes the issue. No need to cold reboot. Here is the Bluetooth dmesg output from this morning's suspend/resume cycles: [58674.253723] Bluetooth: hci0: command 0xfc05 tx timeout [58674.253724] Bluetooth: hci0: Reading Intel version command failed (-110) [58795.067813] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017 [58795.068737] Bluetooth: hci0: Device revision is 1 [58795.068739] Bluetooth: hci0: Secure boot is enabled [58795.068740] Bluetooth: hci0: OTP lock is enabled [58795.068741] Bluetooth: hci0: API lock is enabled [58795.068741] Bluetooth: hci0: Debug lock is disabled [58795.068742] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [58795.068952] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi [58796.844050] Bluetooth: hci0: Waiting for firmware download to complete [58796.844645] Bluetooth: hci0: Firmware loaded in 1734054 usecs [58796.844836] Bluetooth: hci0: Waiting for device to boot [58796.859635] Bluetooth: hci0: Device booted in 14567 usecs [58796.859721] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc [58796.861740] Bluetooth: hci0: Applying Intel DDC parameters completed [58796.864875] Bluetooth: hci0: Firmware revision 0.0 build 121 week 36 2020 [58796.924662] Bluetooth: hci0: MSFT filter_enable is already on -- 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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995956] Re: amdgpu no-retry page fault in Kinetic Kudu
Similarly, I was in a video call (via Chromium snap), tried to switch to slack to check messages that just came in, and GUI locked up (but audio continued for several minutes). journald had a ton of these messages: Nov 18 10:41:11 tippin kernel: amdgpu :05:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:1 pasid:32778, for process slack pid 11822 thread slack:cs0 pid 11863) Nov 18 10:41:11 tippin kernel: amdgpu :05:00.0: amdgpu: in page starting at address 0x800103a3 from IH client 0x12 (VMC) Nov 18 10:41:11 tippin kernel: amdgpu :05:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140050 Nov 18 10:41:11 tippin kernel: amdgpu :05:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 18 10:41:11 tippin kernel: amdgpu :05:00.0: amdgpu: MORE_FAULTS: 0x0 Nov 18 10:41:11 tippin kernel: amdgpu :05:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 18 10:41:11 tippin kernel: amdgpu :05:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Nov 18 10:41:11 tippin kernel: amdgpu :05:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 18 10:41:11 tippin kernel: amdgpu :05:00.0: amdgpu: RW: 0x1 I believe this is tracked upstream in https://gitlab.freedesktop.org/drm/amd/-/issues/2113 . ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2113 https://gitlab.freedesktop.org/drm/amd/-/issues/2113 ** Also affects: linux via https://gitlab.freedesktop.org/drm/amd/-/issues/2113 Importance: Unknown Status: Unknown -- 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/1995956 Title: amdgpu no-retry page fault in Kinetic Kudu Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Kinetic: Triaged Bug description: When using Skype in snap, amdgpu crashed, resulting in black screen and unresponsive system. Happened on Kinetic Kudu 5.19.0-23-generic with or without latest amdgpu firmware. Affected laptop is T14 with Ryzen 5850U. Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142c000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00540051 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142d000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142c000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00540051 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
Running "Ubuntu 22.04.1". After updating today, was unable to fully boot. Screen goes black, unable to get to a terminal. Booted into 5.15.0-52 to report/confirm issue. Please instruct. -- 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995148] [NEW] mlxbf_gige: need to add BlueField-3 support
Public bug reported:
SRU Justification:
[Impact]
The GIGE driver ("mlxbf_gige") in the Jammy repo does not yet
support the BlueField-3 SoC. The "mlxbf_gige" driver which
supports BlueField-2 SoC currently will be extended to include
the BlueField-3 support.
[Fix]
The BlueField-3 support will be provided in the form of a set
of 4 patches, to be sent in as a pull request.
[Test Case]
BlueField-2: Boot platform and bring up "oob_net0" interface properly
Test that network traffic works properly
BlueField-3: Tested in simulator platforms and early silicon
[Regression Potential]
Since this is initial support there is chance of regression
on BlueField-2 platforms, but it's been tested there.
[Other]
n/a
** Affects: linux-bluefield (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/1995148
Title:
mlxbf_gige: need to add BlueField-3 support
Status in linux-bluefield package in Ubuntu:
New
Bug description:
SRU Justification:
[Impact]
The GIGE driver ("mlxbf_gige") in the Jammy repo does not yet
support the BlueField-3 SoC. The "mlxbf_gige" driver which
supports BlueField-2 SoC currently will be extended to include
the BlueField-3 support.
[Fix]
The BlueField-3 support will be provided in the form of a set
of 4 patches, to be sent in as a pull request.
[Test Case]
BlueField-2: Boot platform and bring up "oob_net0" interface properly
Test that network traffic works properly
BlueField-3: Tested in simulator platforms and early silicon
[Regression Potential]
Since this is initial support there is chance of regression
on BlueField-2 platforms, but it's been tested there.
[Other]
n/a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1995148/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973676] Re: flickering and black screen after grub after 22.04 upgrade
It seems only 5.15 was the problem. I can confirm it to work on most of the next major versions: I tried the latest of each series, 5.17.x, 5.18.x, 5.19.x and finally 6.0.0 and 6.0.1 and it works on all of them. -- 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/1973676 Title: flickering and black screen after grub after 22.04 upgrade Status in linux package in Ubuntu: Incomplete Bug description: On an HP x360 Spectre (i7-8565U WhiskeyLake-U GT2 [UHD Graphics 620]), after upgrading from 21.10 to 22.04, at boot time just after grub, the kernel displays some errors messages then goes to black. I configure my machine with an encrypted filesystem and before it was going to the splash screen and asking for the partition password. If I type in the password, it seems to boot but the screen stays black forever. It seems the bug started with the 5.15.x series. I have been able, using "mainline" to update up to 5.14.21. After this version the problem appears. Before it's fine. I found the following errors in the logs: * i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=43426 end=43427) time 300 us, min 2146, max 2159, scanline start 2131, end 2171 * i915 :00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) * i915 :00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it * i915 :00:02.0: [drm] [ENCODER:113:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it * i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun So the problem is > 5.13.x series It might be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1979352] Re: system frozen after sleep
Maybe related to this https://github.com/mate-desktop/mate- desktop/issues/519 ** Bug watch added: github.com/mate-desktop/mate-desktop/issues #519 https://github.com/mate-desktop/mate-desktop/issues/519 -- 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/1979352 Title: system frozen after sleep Status in Ubuntu MATE: Confirmed Status in acpid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: Linux V330 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This is a bug that I reported with Ubuntu Mate 20.04 if I remember correctly but, at that time it was only apparent when I was using video ripping software on separate laptops and only when the machines became idle once the ripping program had finished. I don't think this bug was ever fixed and so I'm returning to it because I left my laptop in sleep mode over meal time to come back to a frozen system. I was not using the video ripping program this time, just surfing the Net. No other program was open. I run a Lenovo i7 V330-151KB and a Lenovo i5 Z50 but, the bug has happened when using an old Dell 1530 laptop. I do not believe I am unique in having this bug as someone has a similar bug when they have minimised Google Chrome and their system had went to sleep. I was also using Chrome this time but, as I have already said I was having this happen using another program and not using Chrome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1979352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973676] Re: flickering and black screen from boot time, no more display after 22.04 upgrade
** Description changed: - On an HP x360 Spectre (i7-8565U WhiskeyLake-U GT2 [UHD Graphics 620]), - after upgrading to 22.04 from 21.10, the display goes to some flickering - lines in black and grey or colors (remember the artifacts on Amstrad CPC - or C64 when loading from a tape? Same here...). + On an HP x360 Spectre (i7-8565U WhiskeyLake-U GT2 [UHD Graphics 620]), after upgrading from 21.10 to 22.04, at boot time just after grub, the kernel displays some errors messages then goes to black. + I configure my machine with an encrypted filesystem and before it was going to the splash screen and asking for the partition password. + If I type in the password, it seems to boot but the screen stays black forever. - After the initial grub menu, the kernel loads and boots. There are a few - lines of log when the screen is in text mode. As soon as the plymouth - screen comes in, the screen starts flickering massively. Nothing - appeared on the screen except horizontal lines. I have an encrypted - partition, so I type in the password and then the screen goes to - flickering lines in color when Wayland starts. - - I tried different kernels: - - 5.17.8: failed - - 5.15.x: all failed (from Ubuntu 22.04) - - 5.13.19: works and back to normal + It seems the bug started with the 5.15.x series. I have been able, using + "mainline" to update up to 5.14.21. After this version the problem appears. Before it's fine. I found the following errors in the logs: * i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=43426 end=43427) time 300 us, min 2146, max 2159, scanline start 2131, end 2171 * i915 :00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) * i915 :00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it * i915 :00:02.0: [drm] [ENCODER:113:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it * i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun So the problem is > 5.13.x series - I temporarily solved it by downgrading to 5.13.19 from ubuntu mainline - on a newly updated ubuntu 22.04! But it seems the bug affects all the - kernels. - It might be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 - - Info: - Description: Ubuntu 22.04 LTS - Release: 22.04 - - linux-image-5.15.0-30-generic: - Installed: 5.15.0-30.31 - Candidate: 5.15.0-30.31 - Version table: - *** 5.15.0-30.31 500 - 500 http://au.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages - 100 /var/lib/dpkg/status ** Changed in: linux (Ubuntu) Status: Fix Released => New ** Summary changed: - flickering and black screen from boot time, no more display after 22.04 upgrade + flickering and black screen after grub after 22.04 upgrade -- 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/1973676 Title: flickering and black screen after grub after 22.04 upgrade Status in linux package in Ubuntu: New Bug description: On an HP x360 Spectre (i7-8565U WhiskeyLake-U GT2 [UHD Graphics 620]), after upgrading from 21.10 to 22.04, at boot time just after grub, the kernel displays some errors messages then goes to black. I configure my machine with an encrypted filesystem and before it was going to the splash screen and asking for the partition password. If I type in the password, it seems to boot but the screen stays black forever. It seems the bug started with the 5.15.x series. I have been able, using "mainline" to update up to 5.14.21. After this version the problem appears. Before it's fine. I found the following errors in the logs: * i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=43426 end=43427) time 300 us, min 2146, max 2159, scanline start 2131, end 2171 * i915 :00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) * i915 :00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it * i915 :00:02.0: [drm] [ENCODER:113:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it * i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun So the problem is > 5.13.x series It might be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991403] [NEW] mlxbf_gige: fix devm_ioremap error handling
Public bug reported: SRU Justification: [Impact] The following upstream commit was recently added to Jammy: 3a1a274e933f mlxbf_gige: compute MDIO period based on i1clk This patch added driver logic that includes a "devm_ioremap" call, but the error handling logic pertaining to this call is incorrect. [Fix] The "devm_ioremap" function returns NULL on error, it doesn't return error pointers. The error handling logic has been fixed accordingly. [Test Case] Boot platform and bring up "oob_net0" interface properly Test that network traffic works properly [Regression Potential] Low, as the patch was reviewed upstream [Other] None ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1991403 Title: mlxbf_gige: fix devm_ioremap error handling Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] The following upstream commit was recently added to Jammy: 3a1a274e933f mlxbf_gige: compute MDIO period based on i1clk This patch added driver logic that includes a "devm_ioremap" call, but the error handling logic pertaining to this call is incorrect. [Fix] The "devm_ioremap" function returns NULL on error, it doesn't return error pointers. The error handling logic has been fixed accordingly. [Test Case] Boot platform and bring up "oob_net0" interface properly Test that network traffic works properly [Regression Potential] Low, as the patch was reviewed upstream [Other] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1991403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991151] Re: mlxbf_gige: need to revert SAUCE patch for "clear MDIO gateway lock"
Sorry as this has become confusing. This bug does still apply to Jammy linux-bluefield, and the fix is contained in a patch series that I sent in yesterday: v3--cover-letter.patch v3-0001-UBUNTU-SAUCE-Revert-UBUNTU-SAUCE-mlxbf_gige-clear.patch v3-0002-mlxbf_gige-clear-MDIO-gateway-lock-after-read.patch Please let me know if indeed this bug is being closed and I need to create another LP bug for the v3 patch series. -- 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/1991151 Title: mlxbf_gige: need to revert SAUCE patch for "clear MDIO gateway lock" Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: In Progress Bug description: SRU Justification: [Impact] The Jammy repo contains the following SAUCE patch: UBUNTU: SAUCE: mlxbf_gige: clear MDIO gateway lock after read This patch is now in mainline Linux kernel, so the SAUCE patch can be reverted and replaced with the upstream commit SHA. [Fix] The fix requires two parts, the first of which is addressed by this bug. A second bug will be created to add the upstream commit to the repo. The fix to this bug is a revert of the SAUCE patch 8d2dbbd437a1 UBUNTU: SAUCE: mlxbf_gige: clear MDIO gateway lock after read [Test Case] Boot platform and bring up "oob_net0" interface properly Test that network traffic works properly [Regression Potential] Low, as this logic is well tested. [Other] Will add a note to this bug with the second bug's number, after the second bug is created. The second bug is for adding the upstream commit to the Jammy repo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1991151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991151] Re: mlxbf_gige: need to revert SAUCE patch for "clear MDIO gateway lock"
This bug is within the Jammy repo of the BlueField project (22.04). I sent in the patch with a subject line containing this prefix: "[SRU][F:linux-bluefield]" Is that relevant for 22.04 patches, or should the "F" be replaced with something to signify Jammy? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1991151 Title: mlxbf_gige: need to revert SAUCE patch for "clear MDIO gateway lock" Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] The Jammy repo contains the following SAUCE patch: UBUNTU: SAUCE: mlxbf_gige: clear MDIO gateway lock after read This patch is now in mainline Linux kernel, so the SAUCE patch can be reverted and replaced with the upstream commit SHA. [Fix] The fix requires two parts, the first of which is addressed by this bug. A second bug will be created to add the upstream commit to the repo. The fix to this bug is a revert of the SAUCE patch 8d2dbbd437a1 UBUNTU: SAUCE: mlxbf_gige: clear MDIO gateway lock after read [Test Case] Boot platform and bring up "oob_net0" interface properly Test that network traffic works properly [Regression Potential] Low, as this logic is well tested. [Other] Will add a note to this bug with the second bug's number, after the second bug is created. The second bug is for adding the upstream commit to the Jammy repo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1991151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991151] [NEW] mlxbf_gige: need to revert SAUCE patch for "clear MDIO gateway lock"
Public bug reported: SRU Justification: [Impact] The Jammy repo contains the following SAUCE patch: UBUNTU: SAUCE: mlxbf_gige: clear MDIO gateway lock after read This patch is now in mainline Linux kernel, so the SAUCE patch can be reverted and replaced with the upstream commit SHA. [Fix] The fix requires two parts, the first of which is addressed by this bug. A second bug will be created to add the upstream commit to the repo. The fix to this bug is a revert of the SAUCE patch 8d2dbbd437a1 UBUNTU: SAUCE: mlxbf_gige: clear MDIO gateway lock after read [Test Case] Boot platform and bring up "oob_net0" interface properly Test that network traffic works properly [Regression Potential] Low, as this logic is well tested. [Other] Will add a note to this bug with the second bug's number, after the second bug is created. The second bug is for adding the upstream commit to the Jammy repo. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1991151 Title: mlxbf_gige: need to revert SAUCE patch for "clear MDIO gateway lock" Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] The Jammy repo contains the following SAUCE patch: UBUNTU: SAUCE: mlxbf_gige: clear MDIO gateway lock after read This patch is now in mainline Linux kernel, so the SAUCE patch can be reverted and replaced with the upstream commit SHA. [Fix] The fix requires two parts, the first of which is addressed by this bug. A second bug will be created to add the upstream commit to the repo. The fix to this bug is a revert of the SAUCE patch 8d2dbbd437a1 UBUNTU: SAUCE: mlxbf_gige: clear MDIO gateway lock after read [Test Case] Boot platform and bring up "oob_net0" interface properly Test that network traffic works properly [Regression Potential] Low, as this logic is well tested. [Other] Will add a note to this bug with the second bug's number, after the second bug is created. The second bug is for adding the upstream commit to the Jammy repo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1991151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989495] [NEW] mlxbf_gige: need to clear MDIO gateway lock after read
Public bug reported: SRU Justification: [Impact] The BlueField-2 GIGE logic accesses the MDIO device via reads/writes to a gateway (GW) register. The MDIO GW lock is set after read. Make sure to always clear to indicate that the GW register is not being used. If the lock is mistakenly interpreted as ACTIVE, then subsequent MDIO accesses will be blocked and PHY device will be inaccessible. [Fix] For each MDIO read and write transaction, the last step should be to clear the MDIO GW lock. [Test Case] Boot the BlueField-2 platform Bring up the "oob_net0" interface via DHCP or static IP Ping and file transfer over "oob_net0" should work properly Bounce the "oob_net0" interface a few times and repeat tests [Regression Potential] * Low risk for causing a regression, tested well in our lab. [Other] * None ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1989495 Title: mlxbf_gige: need to clear MDIO gateway lock after read Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] The BlueField-2 GIGE logic accesses the MDIO device via reads/writes to a gateway (GW) register. The MDIO GW lock is set after read. Make sure to always clear to indicate that the GW register is not being used. If the lock is mistakenly interpreted as ACTIVE, then subsequent MDIO accesses will be blocked and PHY device will be inaccessible. [Fix] For each MDIO read and write transaction, the last step should be to clear the MDIO GW lock. [Test Case] Boot the BlueField-2 platform Bring up the "oob_net0" interface via DHCP or static IP Ping and file transfer over "oob_net0" should work properly Bounce the "oob_net0" interface a few times and repeat tests [Regression Potential] * Low risk for causing a regression, tested well in our lab. [Other] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989495/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987996] Re: boot is failing shows error ACPI BIOS error (bug): could not resolve symbol [\_SB.PR00._CPC] I tried reinstalling ubuntu and erase the current files however the ins
Unfortunately I'm unable to access terminal at this point when I boot I can only access the GNU GRUB menu is there any other way I can get those files? ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987996 Title: boot is failing shows error ACPI BIOS error (bug): could not resolve symbol [\_SB.PR00._CPC] I tried reinstalling ubuntu and erase the current files however the installer crashed. Status in linux package in Ubuntu: Confirmed Bug description: I have read this is a kernel issue, however I don't know how to resolve it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.15 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 17:17:31 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987996/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987223] Re: Touchpad and Touchscreen not showing up in devices on Dell after Kubuntu 22.04 upgrade
Following this: https://www.dell.com/support/kbdoc/fr- ch/000150104/precision-xps-ubuntu-general-touchpad-mouse-issue- fix?lang=en I ran the following and rebooted: sudo apt install --install-recommends linux-generic-hwe-22.04 xserver-xorg-hwe-18.04 Now the devices exist, see devices2 attachment ** Attachment added: "devices2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987223/+attachment/5610586/+files/devices2 -- 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/1987223 Title: Touchpad and Touchscreen not showing up in devices on Dell after Kubuntu 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: The touchpad and touch screen worked ok on 20.04. After installing 22.04 they no longer work. Investigation shows no devices, output from below attached in "devices": cat /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: david 1396 F pulseaudio /dev/snd/controlC1: david 1396 F pulseaudio /dev/snd/pcmC1D0p: david 1396 F...m pulseaudio /dev/snd/controlC0: david 1396 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Aug 21 22:24:24 2022 InstallationDate: Installed on 2022-04-20 (123 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: Dell Inc. Inspiron 7786 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=9c986618-4ee9-4eb8-bc36-dbdfc9a61cd1 ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/28/2022 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0C6KN0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd03/28/2022:br1.14:svnDellInc.:pnInspiron7786:pvr:rvnDellInc.:rn0C6KN0:rvrA00:cvnDellInc.:ct31:cvr:sku0896: dmi.product.family: Inspiron dmi.product.name: Inspiron 7786 dmi.product.sku: 0896 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987223] [NEW] Touchpad and Touchscreen not showing up in devices on Dell after Kubuntu 22.04 upgrade
Public bug reported: The touchpad and touch screen worked ok on 20.04. After installing 22.04 they no longer work. Investigation shows no devices, output from below attached in "devices": cat /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: david 1396 F pulseaudio /dev/snd/controlC1: david 1396 F pulseaudio /dev/snd/pcmC1D0p: david 1396 F...m pulseaudio /dev/snd/controlC0: david 1396 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Aug 21 22:24:24 2022 InstallationDate: Installed on 2022-04-20 (123 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: Dell Inc. Inspiron 7786 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=9c986618-4ee9-4eb8-bc36-dbdfc9a61cd1 ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/28/2022 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0C6KN0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd03/28/2022:br1.14:svnDellInc.:pnInspiron7786:pvr:rvnDellInc.:rn0C6KN0:rvrA00:cvnDellInc.:ct31:cvr:sku0896: dmi.product.family: Inspiron dmi.product.name: Inspiron 7786 dmi.product.sku: 0896 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "cat /proc/bus/input/devices" https://bugs.launchpad.net/bugs/1987223/+attachment/5610550/+files/devices ** Summary changed: - radeTouchpad and Touchscreen not showing up in devices on Dell after Kubuntu 22.04 upg + Touchpad and Touchscreen not showing up in devices on Dell after Kubuntu 22.04 upgrade -- 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/1987223 Title: Touchpad and Touchscreen not showing up in devices on Dell after Kubuntu 22.04 upgrade Status in linux package in Ubuntu: New Bug description: The touchpad and touch screen worked ok on 20.04. After installing 22.04 they no longer work. Investigation shows no devices, output from below attached in "devices": cat /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: david 1396 F pulseaudio /dev/snd/controlC1: david 1396 F pulseaudio /dev/snd/pcmC1D0p: david 1396 F...m pulseaudio /dev/snd/controlC0: david 1396 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Aug 21 22:24:24 2022 InstallationDate: Installed on 2022-04-20 (123 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: Dell Inc. Inspiron 7786 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=9c986618-4ee9-4eb8-bc36-dbdfc9a61cd1 ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/28/2022 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0C6KN0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd03/28/2022:br1.14:svnDellInc.:pnInspiron7786:pvr:rvnDellInc.:rn0C6KN0:rvrA00:cvnDellInc.:ct31:cvr:sku0896: dmi.product.family: Inspiron dmi.product.name: Inspiron 7786 dmi.product.sku: 0896 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/19
[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
I upgraded via do-release-upgrade -d With 5.15.0-41-generic the webcam works! At least in Chrome/Firefox. However wifi becomes unreliable and disconnects after some time. I will confirm that this is reproducible later. For now, it doesn't look like a viable solution for me. I had installed the 22.04 oem kernel, assuming it would be better, as the oem 20.04 install was using an oem kernel. Is there any advantage of using 5.14.0-10XX-oem instead of 5.15 generic? How would I install it? Let me know if more logs would be helpful. ** Attachment added: "dpkg -l" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1955383/+attachment/5604577/+files/dpkg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.23+staging.38 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-2013-oem N/A linux-backports-modules-5.14.0-2013-oem N/A linux-firmware 1.187.23+staging.38 Tags: third-party-packages focal Uname: Linux
[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
The XPS 13 Plus 9320 webcam does not work for me since upgrading to 22.04 from the original 20.04 OEM installation. BIOS: 1.4.0 Kernel:5.17.0-1013-oem libcamhal-ipu6ep0 is installed from the mentioned PPA v4l2-ctl --list-devices Intel MIPI Camera (platform:v4l2loopback-000): /dev/video0 Neither chrome nor Firefox show video. Similar to the issue described here https://askubuntu.com/questions/1414767/dell-xps-plus-9320-webcam- not-detected-in-ubuntu-22-04?atw=1#comment2465343_1417193 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.23+staging.38 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-2013-oem N/A linux-backports-modules-5.14.0-2013-oem N/A linux-firmware 1.187.23+staging.38 Tags: third-party-packages focal Uname: Linux 5.14.0-2013-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present
[Kernel-packages] [Bug 1981590] Re: Kernel 5.15 hangs at "Loading initial ramdisk"
Independent confirmation from me, with the same symptoms: updated from kernel 5.13 to 5.15 today. After rebooting the system hangs at "Loading ramdisk". I reverted to 5.13 and it started properly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1981590 Title: Kernel 5.15 hangs at "Loading initial ramdisk" Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Bug description: Updated from kernel 5.13 to 5.15 today. After rebooting the system hangs at "Loading ramdisk". I reverted to 5.13 and it started properly. More detail on the way. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 13 14:48:42 2022 InstallationDate: Installed on 2021-01-06 (553 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1981590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959030] Re: [SOF - sof-bytcht rt5651, playback] No sound at all
Apologies in advance if I don't use the right syntax or formatting here; I'm pretty new to Linux and this bug reporting process. I believe I am seeing the same symptoms running 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux on Lubuntu 22.04. The sound card seems to be recognized: $ aplay -l List of PLAYBACK Hardware Devices card 0: Audio [Intel HDMI/DP LPE Audio], device 0: HdmiLpeAudio [Intel HDMI/DP LPE Audi] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Audio [Intel HDMI/DP LPE Audio], device 1: HdmiLpeAudio [Intel HDMI/DP LPE Audi] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Audio [Intel HDMI/DP LPE Audio], device 2: HdmiLpeAudio [Intel HDMI/DP LPE Audi] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: rt5651 [sof-bytcht rt5651], device 0: PCM (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: rt5651 [sof-bytcht rt5651], device 1: PCM Deep Buffer (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 I used to get sound when I ran $ speaker-test -D plughw:CARD=rt5651,DEV=0 but not anymore. pavucontrol-qt only shows a Dummy output. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959030 Title: [SOF - sof-bytcht rt5651, playback] No sound at all Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: After last update sound stopped to work ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ttrolka1260 F pulseaudio /dev/snd/pcmC1D0p: ttrolka1260 F...m pulseaudio /dev/snd/controlC0: ttrolka1260 F pulseaudio /dev/snd/timer: ttrolka1260 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 25 20:29:29 2022 InstallationDate: Installed on 2021-09-04 (143 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:rt5651 failed Symptom_Card: Built-in Audio - sof-bytcht rt5651 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ttrolka1260 F pulseaudio /dev/snd/pcmC1D0p: ttrolka1260 F...m pulseaudio /dev/snd/controlC0: ttrolka1260 F pulseaudio /dev/snd/timer: ttrolka1260 f pulseaudio Symptom_Type: No sound at all Title: [SOF - sof-bytcht rt5651, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Digma12x.WJ3142.NFNKRCN01 dmi.board.asset.tag: Default string dmi.board.name: CITI E401 ET4007EW dmi.board.vendor: Digma dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrDigma12x.WJ3142.NFNKRCN01:bd07/03/2018:br5.11:svnDigma:pnCITIE401ET4007EW:pvrDefaultstring:rvnDigma:rnCITIE401ET4007EW:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:sku1806078: dmi.product.family: CHT dmi.product.name: CITI E401 ET4007EW dmi.product.sku: 1806078 dmi.product.version: Default string dmi.sys.vendor: Digma To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1959030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981590] Re: Kernel 5.15 hangs at "Loading initial ramdisk"
** Also affects: linux-signed-hwe-5.15 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1981590 Title: Kernel 5.15 hangs at "Loading initial ramdisk" Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: Updated from kernel 5.13 to 5.15 today. After rebooting the system hangs at "Loading ramdisk". I reverted to 5.13 and it started properly. More detail on the way. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 13 14:48:42 2022 InstallationDate: Installed on 2021-01-06 (553 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1981590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981590] Re: Kernel 5.15 hangs at "Loading initial ramdisk"
While experimenting with FreeDOS and Windows PE, I discovered that disabling UEFI mode (switching to Legacy mode) means I can now boot into kernel 5.15. Certainly not a solution, but at least a workaround. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1981590 Title: Kernel 5.15 hangs at "Loading initial ramdisk" Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Updated from kernel 5.13 to 5.15 today. After rebooting the system hangs at "Loading ramdisk". I reverted to 5.13 and it started properly. More detail on the way. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 13 14:48:42 2022 InstallationDate: Installed on 2021-01-06 (553 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1981590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981590] Re: Kernel 5.15 hangs at "Loading initial ramdisk"
Independent confirmation from me, with the same symptoms: updated from kernel 5.13 to 5.15 today. After rebooting the system hangs at "Loading ramdisk". I reverted to 5.13 and it started properly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1981590 Title: Kernel 5.15 hangs at "Loading initial ramdisk" Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Updated from kernel 5.13 to 5.15 today. After rebooting the system hangs at "Loading ramdisk". I reverted to 5.13 and it started properly. More detail on the way. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 13 14:48:42 2022 InstallationDate: Installed on 2021-01-06 (553 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1981590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981590] Re: Kernel 5.15 hangs at "Loading initial ramdisk"
$ ls -lh /boot/initrd* lrwxrwxrwx 1 root root 28 Jul 13 07:55 /boot/initrd.img -> initrd.img-5.15.0-41-generic -rw-r--r-- 1 root root 108M Jul 13 07:54 /boot/initrd.img-5.13.0-52-generic -rw-r--r-- 1 root root 117M Jul 13 07:55 /boot/initrd.img-5.15.0-41-generic lrwxrwxrwx 1 root root 28 Jul 13 07:55 /boot/initrd.img.old -> initrd.img-5.13.0-52-generic $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/nvme0n1p2 705M 267M 387M 41% /boot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1981590 Title: Kernel 5.15 hangs at "Loading initial ramdisk" Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: Updated from kernel 5.13 to 5.15 today. After rebooting the system hangs at "Loading ramdisk". I reverted to 5.13 and it started properly. More detail on the way. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 13 14:48:42 2022 InstallationDate: Installed on 2021-01-06 (553 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1981590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981590] Re: Kernel 5.15 hangs at "Loading initial ramdisk"
Tried removing modifying /etc/default/grub by setting GRUB_CMDLINE_LINUX_DEFAULT to "" (was "quiet splash") Results: - 5.13: spews lots of logs, no splash screen when prompted for disk encryption passphrase - 5.15: still hangs at the same place, no logs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1981590 Title: Kernel 5.15 hangs at "Loading initial ramdisk" Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: Updated from kernel 5.13 to 5.15 today. After rebooting the system hangs at "Loading ramdisk". I reverted to 5.13 and it started properly. More detail on the way. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 13 14:48:42 2022 InstallationDate: Installed on 2021-01-06 (553 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1981590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981590] Re: Kernel 5.15 hangs at "Loading initial ramdisk"
** Summary changed: - Computer hangs at boot + Kernel 5.15 hangs at "Loading initial ramdisk" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1981590 Title: Kernel 5.15 hangs at "Loading initial ramdisk" Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: Updated from kernel 5.13 to 5.15 today. After rebooting the system hangs at "Loading ramdisk". I reverted to 5.13 and it started properly. More detail on the way. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 13 14:48:42 2022 InstallationDate: Installed on 2021-01-06 (553 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1981590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981590] Re: Computer hangs at boot
No extra info available, once I get the following message, no keys respond (e.g. NumLock cannot switch state). The same happens for the "recovery mode" option. Loading Linux 5.15.0-41-generic ... Loading initial ramdisk ... _ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1981590 Title: Kernel 5.15 hangs at "Loading initial ramdisk" Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: Updated from kernel 5.13 to 5.15 today. After rebooting the system hangs at "Loading ramdisk". I reverted to 5.13 and it started properly. More detail on the way. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 13 14:48:42 2022 InstallationDate: Installed on 2021-01-06 (553 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1981590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981590] Re: Computer hangs at boot
Result of dpkg -l | grep '^ii linux': ``` ii linux-base 4.5ubuntu3.7 all Linux image base package ii linux-firmware 1.187.32 all Firmware for Linux kernel drivers ii linux-generic-hwe-20.04 5.15.0.41.44~20.04.13 amd64 Complete Generic Linux kernel and headers ii linux-headers-5.13.0-52-generic 5.13.0-52.59~20.04.1amd64Linux kernel headers for version 5.13.0 on 64 bit x86 SMP ii linux-headers-5.15.0-41-generic 5.15.0-41.44~20.04.1amd64Linux kernel headers for version 5.15.0 on 64 bit x86 SMP ii linux-headers-generic-hwe-20.04 5.15.0.41.44~20.04.13 amd64 Generic Linux kernel headers ii linux-hwe-5.13-headers-5.13.0-52 5.13.0-52.59~20.04.1all Header files related to Linux kernel version 5.13.0 ii linux-hwe-5.15-headers-5.15.0-41 5.15.0-41.44~20.04.1all Header files related to Linux kernel version 5.15.0 ii linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1amd64Signed kernel image generic ii linux-image-5.15.0-41-generic 5.15.0-41.44~20.04.1amd64Signed kernel image generic ii linux-image-generic-hwe-20.04 5.15.0.41.44~20.04.13 amd64 Generic Linux kernel image ii linux-libc-dev:amd645.4.0-122.138 amd64Linux Kernel Headers for development ii linux-modules-5.13.0-52-generic 5.13.0-52.59~20.04.1amd64Linux kernel extra modules for version 5.13.0 on 64 bit x86 SMP ii linux-modules-5.15.0-41-generic 5.15.0-41.44~20.04.1amd64Linux kernel extra modules for version 5.15.0 on 64 bit x86 SMP ii linux-modules-extra-5.13.0-52-generic 5.13.0-52.59~20.04.1amd64Linux kernel extra modules for version 5.13.0 on 64 bit x86 SMP ii linux-modules-extra-5.15.0-41-generic 5.15.0-41.44~20.04.1amd64Linux kernel extra modules for version 5.15.0 on 64 bit x86 SMP ii linux-sound-base 1.0.25+dfsg-0ubuntu5all base package for ALSA and OSS sound systems ``` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1981590 Title: Computer hangs at boot Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: Updated from kernel 5.13 to 5.15 today. After rebooting the system hangs at "Loading ramdisk". I reverted to 5.13 and it started properly. More detail on the way. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 13 14:48:42 2022 InstallationDate: Installed on 2021-01-06 (553 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1981590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
