[Kernel-packages] [Bug 1997505] Re: Unattended-Upgrade will upgrade 1020-oem kernel without nvidia-driver
Thanks all, the workaround works fine. ** No longer affects: nvidia-graphics-drivers-515 (Ubuntu) ** Changed in: oem-priority Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1997505 Title: Unattended-Upgrade will upgrade 1020-oem kernel without nvidia-driver Status in OEM Priority Project: Fix Released Status in linux-meta-oem-5.17 package in Ubuntu: Fix Released Bug description: If the GMed image used earlier kernel than 5.17.0-1020-oem, then you would like meet this issue. 1020-oem is in security channel. In jammy the unattende-upgrade will install security fixes by default. For the I+N platforms, the nvidia driver couldn't be installed for 1020-oem kernel, then user will meet a black screen cause of nvidia modules couldn't be loaded. Unattended-Upgrade::Allowed-Origins { "${distro_id}:${distro_codename}"; "${distro_id}:${distro_codename}-security"; // Extended Security Maintenance; doesn't necessarily exist for // every release and this system may not have it installed, but if // available, the policy for updates is such that unattended-upgrades // should also install from here by default. "${distro_id}ESMApps:${distro_codename}-apps-security"; "${distro_id}ESM:${distro_codename}-infra-security"; To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1997505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998194] Re: Please add support for Qualcomm IPC Router in 5.4 focal kernel
** Tags added: oem-priority -- 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/1998194 Title: Please add support for Qualcomm IPC Router in 5.4 focal kernel Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: The modemmanager debian package in focal was recently upgraded to 1.18 (the jammy version was backported - see LP: #1965901). This version has broken some Qualcomm modems as it start to require the Qualcomm IPC Router for them, which drivers are not enabled in Ubuntu kernel 5.4. To fix this we need these options enabled in the focal kernel: CONFIG_QRTR=m CONFIG_QRTR_SMD=m CONFIG_QRTR_TUN=m CONFIG_QRTR_MHI=m The options are already enabled in more modern Ubuntu kernel, i.e. 5.17. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998194] Re: Please add support for Qualcomm IPC Router in 5.4 focal kernel
** Also affects: oem-priority 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/1998194 Title: Please add support for Qualcomm IPC Router in 5.4 focal kernel Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: The modemmanager debian package in focal was recently upgraded to 1.18 (the jammy version was backported - see LP: #1965901). This version has broken some Qualcomm modems as it start to require the Qualcomm IPC Router for them, which drivers are not enabled in Ubuntu kernel 5.4. To fix this we need these options enabled in the focal kernel: CONFIG_QRTR=m CONFIG_QRTR_SMD=m CONFIG_QRTR_TUN=m CONFIG_QRTR_MHI=m The options are already enabled in more modern Ubuntu kernel, i.e. 5.17. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998656] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998656 Title: iwlwifi is crashing Status in linux package in Ubuntu: Confirmed Bug description: Hello, My wifi adapter is regularly crashing with the latest kernel. The workaround appears to be the same as outlined in: https://bugzilla.kernel.org/show_bug.cgi?id=208425 which is setting the router to use 20MHz channel widths. This appears to be fixed in kernel 5.18.6 as described here: https://bugzilla.kernel.org/show_bug.cgi?id=215635#c18 However, Ubuntu 22.04 does not have kernel 5.18.6. This is occurring in linux-source-5.15.0-53.59. Thank you, Ted ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.15.64-caticorn-22.11.16 x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shofutex 2321 F pulseaudio /dev/snd/controlC0: shofutex 2321 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Dec 2 18:34:41 2022 InstallationDate: Installed on 2019-09-23 (1166 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H WIFI ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.64-hostname-22.11.16 root=/dev/mapper/ubuntu--vg-root ro quiet splash amd_iommu=on iommu=pt kvm_amd.npt=1 vfio-pci.ids=1002:67df,1002:aaf0,1022:15e0,1022:15e1 pcie_acs_override=id:1022:15e0,id:1022:15e1 amdgpu.gttsize=8192 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.64-caticorn-22.11.16 N/A linux-backports-modules-5.15.64-caticorn-22.11.16 N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-02 (214 days ago) dmi.bios.date: 07/22/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F41 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF41:bd07/22/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3HWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3HWIFI-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H WIFI 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/ubuntu/+source/linux/+bug/1998656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998656] [NEW] iwlwifi is crashing
Public bug reported: Hello, My wifi adapter is regularly crashing with the latest kernel. The workaround appears to be the same as outlined in: https://bugzilla.kernel.org/show_bug.cgi?id=208425 which is setting the router to use 20MHz channel widths. This appears to be fixed in kernel 5.18.6 as described here: https://bugzilla.kernel.org/show_bug.cgi?id=215635#c18 However, Ubuntu 22.04 does not have kernel 5.18.6. This is occurring in linux-source-5.15.0-53.59. Thank you, Ted ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.15.64-caticorn-22.11.16 x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shofutex 2321 F pulseaudio /dev/snd/controlC0: shofutex 2321 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Dec 2 18:34:41 2022 InstallationDate: Installed on 2019-09-23 (1166 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H WIFI ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.64-hostname-22.11.16 root=/dev/mapper/ubuntu--vg-root ro quiet splash amd_iommu=on iommu=pt kvm_amd.npt=1 vfio-pci.ids=1002:67df,1002:aaf0,1022:15e0,1022:15e1 pcie_acs_override=id:1022:15e0,id:1022:15e1 amdgpu.gttsize=8192 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.64-caticorn-22.11.16 N/A linux-backports-modules-5.15.64-caticorn-22.11.16 N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-02 (214 days ago) dmi.bios.date: 07/22/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F41 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF41:bd07/22/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3HWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3HWIFI-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1998656 Title: iwlwifi is crashing Status in linux package in Ubuntu: New Bug description: Hello, My wifi adapter is regularly crashing with the latest kernel. The workaround appears to be the same as outlined in: https://bugzilla.kernel.org/show_bug.cgi?id=208425 which is setting the router to use 20MHz channel widths. This appears to be fixed in kernel 5.18.6 as described here: https://bugzilla.kernel.org/show_bug.cgi?id=215635#c18 However, Ubuntu 22.04 does not have kernel 5.18.6. This is occurring in linux-source-5.15.0-53.59. Thank you, Ted ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.15.64-caticorn-22.11.16 x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shofutex 2321 F pulseaudio /dev/snd/controlC0: shofutex 2321 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Dec 2 18:34:41 2022 InstallationDate: Installed on 2019-09-23 (1166 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H WIFI ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.64-hostname-22.11.16 root=/dev/mapper/ubuntu--vg-root ro quiet splash amd_iommu=on iommu=pt kvm_amd.npt=1 vfio-pci.ids=1002:67df,1002:aaf0,1022:15e0,1022:15e1 pcie_acs_override=id:1022:15e0,id:1022:15e1 amdgpu.gttsize=8192 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.64-caticorn-22.11.16 N/A linux-backports-modules-5.15.64-caticorn-22.11.16 N/A linux-firmware 2022
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to latest kernel.org
The compile test was successful. There are some more outstanding patches from Martin Petersen's tree: git remote add mkp_6.20-scsi-queue https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git -t 6.2/scsi-queue git fetch mkp_6.20-scsi-queue cat backport_mkp_6.2-scsi-queue_into_22.04 2ae45329a956 scsi: smartpqi: Change version to 2.1.20-035 921800a1deea scsi: smartpqi: Initialize feature section info 14063fb625c4 scsi: smartpqi: Add controller cache flush during rmmod cc9befcbbb5e scsi: smartpqi: Correct device removal for multi-actuator devices cbe42ac15698 scsi: smartpqi: Change sysfs raid_level attribute to N/A for controllers 7c56850637ea scsi: smartpqi: Correct max LUN number 0b93cf2a9097 scsi: smartpqi: Add new controller PCI IDs b27ac2faa2fc scsi: smartpqi: Convert to host_tagset git-backport --sort -d /tmp/patches_mkp ../backport_mkp_6.2-scsi-queue_into_22.04 git am -s /tmp/patches_mkp/*.diff These also compile. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998643 Title: smartpqi: Update 22.04 driver to latest kernel.org Status in linux package in Ubuntu: Incomplete Bug description: There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. ~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997140] Re: No video output with Kernel 5.15.0-53-lowlatency
Issue solved here with 5.15.0-56-lowlatency. -- 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/1997140 Title: No video output with Kernel 5.15.0-53-lowlatency Status in linux package in Ubuntu: Confirmed Bug description: Since kernel update to 5.15.0-53-lowlatency, I get no output at all anymore on the monitor. The monitor says 'No Signal'. Also when trying to change to a console with CTRL-ALT-F1 no output. When booting to the still installed previous version 5.15.0-52-lowlatency, all works as expected, and equally so when booting to a self compiled kernel 5.15.73-rt52. System is Xubuntu 22.04 LTS. The debug output is from booting with kernel -52. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998351] Re: Azure: MANA New Feature MANA XDP_Redirect Action
** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Kinetic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1998351 Title: Azure: MANA New Feature MANA XDP_Redirect Action Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] XDP Redirection is not implemented in 5.15 Azure tuned kernels. Microsoft has requested the addition of this feature: commit 7a8938cd024d383c12bb1e08025db6ea3d551103 ("net: mana: Add support of XDP_REDIRECT action") [Test Plan] Microsoft tested with positive results. [Where things could go wrong] Network skb routing could go awry. [Other info] SF: #00340222 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1998351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998643] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1998643 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998643 Title: smartpqi: Update 22.04 driver to latest kernel.org Status in linux package in Ubuntu: Incomplete Bug description: There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. ~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to latest kernel.org
I want do to a build also to ensure that all patches will compile. I believe that they will. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998643 Title: smartpqi: Update 22.04 driver to latest kernel.org Status in linux package in Ubuntu: New Bug description: There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. ~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998643] [NEW] smartpqi: Update 22.04 driver to latest kernel.org
Public bug reported: There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. ~ ** 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/1998643 Title: smartpqi: Update 22.04 driver to latest kernel.org Status in linux package in Ubuntu: New Bug description: There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statemen
[Kernel-packages] [Bug 1997505] Re: Unattended-Upgrade will upgrade 1020-oem kernel without nvidia-driver
** Also affects: linux-meta-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-meta-oem-5.17 (Ubuntu) Importance: Undecided => Critical ** Changed in: linux-meta-oem-5.17 (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: linux-meta-oem-5.17 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1997505 Title: Unattended-Upgrade will upgrade 1020-oem kernel without nvidia-driver Status in OEM Priority Project: Triaged Status in linux-meta-oem-5.17 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: If the GMed image used earlier kernel than 5.17.0-1020-oem, then you would like meet this issue. 1020-oem is in security channel. In jammy the unattende-upgrade will install security fixes by default. For the I+N platforms, the nvidia driver couldn't be installed for 1020-oem kernel, then user will meet a black screen cause of nvidia modules couldn't be loaded. Unattended-Upgrade::Allowed-Origins { "${distro_id}:${distro_codename}"; "${distro_id}:${distro_codename}-security"; // Extended Security Maintenance; doesn't necessarily exist for // every release and this system may not have it installed, but if // available, the policy for updates is such that unattended-upgrades // should also install from here by default. "${distro_id}ESMApps:${distro_codename}-apps-security"; "${distro_id}ESM:${distro_codename}-infra-security"; To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1997505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998472] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1998472 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998472 Title: Sound on Chromebook crashes to buzzing Status in linux package in Ubuntu: Incomplete Bug description: Running Xubuntu 22.04.1 LTS on Acer Chromebook CB3-111. Sound works fine for about 6 minutes and then crashes to a loud buzzing noise. Same problem in both YouTube and Spotify. After closing the application and restarting it the sound is ok until it crashes again. This bug does not seem to be unique to my Chromebook. I have seen a couple of other users with different Chromebooks reporting the same problem online. See: https://www.reddit.com/r/Ubuntu/comments/x0y19l/sound_buzzing_with_22041_on_chromebook/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998472] Re: Sound on Chromebook crashes to buzzing
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998472 Title: Sound on Chromebook crashes to buzzing Status in linux package in Ubuntu: New Bug description: Running Xubuntu 22.04.1 LTS on Acer Chromebook CB3-111. Sound works fine for about 6 minutes and then crashes to a loud buzzing noise. Same problem in both YouTube and Spotify. After closing the application and restarting it the sound is ok until it crashes again. This bug does not seem to be unique to my Chromebook. I have seen a couple of other users with different Chromebooks reporting the same problem online. See: https://www.reddit.com/r/Ubuntu/comments/x0y19l/sound_buzzing_with_22041_on_chromebook/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998472] [NEW] Sound on Chromebook crashes to buzzing
You have been subscribed to a public bug: Running Xubuntu 22.04.1 LTS on Acer Chromebook CB3-111. Sound works fine for about 6 minutes and then crashes to a loud buzzing noise. Same problem in both YouTube and Spotify. After closing the application and restarting it the sound is ok until it crashes again. This bug does not seem to be unique to my Chromebook. I have seen a couple of other users with different Chromebooks reporting the same problem online. See: https://www.reddit.com/r/Ubuntu/comments/x0y19l/sound_buzzing_with_22041_on_chromebook/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Sound on Chromebook crashes to buzzing https://bugs.launchpad.net/bugs/1998472 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997201] Re: BlueZ 5.66 release
This bug was fixed in the package bluez - 5.66-0ubuntu1 --- bluez (5.66-0ubuntu1) lunar; urgency=medium * New upstream release 5.66 (LP: #1997201): - Fix issue with A2DP and transport connection collisions. - Fix issue with allowing application specific error codes. - Fix issue with not setting initiator flag correctly. - Fix issue with HoG Report MAP size handling. - Add initial support for Basic Audio Profile. - Add initial support for Volume Control Profile. * Refreshed patches: - raspi-bcm43xx-load-firmware.patch -- Daniel van Vugt Wed, 30 Nov 2022 16:31:09 +0800 ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1997201 Title: BlueZ 5.66 release Status in bluez package in Ubuntu: Fix Released Bug description: Release to Lunar: http://www.bluez.org/release-of-bluez-5-66/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1997201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998588] Re: package linux-intel-iotg-tools-common 5.15.0-1017.22 [modified: usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-archive.1.gz usr/share/man/man1/perf-b
Same/Related bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996539 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/1998588 Title: package linux-intel-iotg-tools-common 5.15.0-1017.22 [modified: usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf- archive.1.gz usr/share/man/man1/perf-bench.1.gz usr/share/man/man1/perf-buildid-cache.1.gz usr/share/man/man1/perf- buildid-list.1.gz usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz usr/share/man/man1/perf- daemon.1.gz usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf- diff.1.gz usr/share/man/man1/perf-dlfilter.1.gz usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf- ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf- inject.1.gz usr/share/man/man1/perf-intel-pt.1.gz usr/share/man/man1/perf-iostat.1.gz usr/share/man/man1/perf- kallsyms.1.gz usr/share/man/man1/perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1/perf-list.1.gz usr/share/man/man1/perf-lock.1.gz usr/share/man/man1/perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz usr/share/man/man1/perf-record.1.gz usr/share/man/man1/perf-report.1.gz usr/share/man/man1/perf-sched.1.gz usr/share/man/man1/perf-script-perl.1.gz usr/share/man/man1/perf- script-python.1.gz usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf-stat.1.gz usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf-timechart.1.gz usr/share/man/man1/perf- top.1.gz usr/share/man/man1/perf-trace.1.gz usr/share/man/man1/perf- version.1.gz usr/share/man/man1/perf.1.gz] failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-53.59 Status in linux-intel-iotg package in Ubuntu: Confirmed Bug description: 1w ProblemType: Package DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: linux-intel-iotg-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Dec 2 12:34:33 2022 DpkgTerminalLog: Preparing to unpack .../linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb ... Unpacking linux-intel-iotg-tools-common (5.15.0-1021.26) over (5.15.0-1017.22) ... dpkg: error processing archive /var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-53.59 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-53.59 InstallationDate: Installed on 2022-10-09 (54 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-intel-iotg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/1998588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998588] Re: package linux-intel-iotg-tools-common 5.15.0-1017.22 [modified: usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-archive.1.gz usr/share/man/man1/perf-b
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-intel-iotg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/1998588 Title: package linux-intel-iotg-tools-common 5.15.0-1017.22 [modified: usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf- archive.1.gz usr/share/man/man1/perf-bench.1.gz usr/share/man/man1/perf-buildid-cache.1.gz usr/share/man/man1/perf- buildid-list.1.gz usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz usr/share/man/man1/perf- daemon.1.gz usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf- diff.1.gz usr/share/man/man1/perf-dlfilter.1.gz usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf- ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf- inject.1.gz usr/share/man/man1/perf-intel-pt.1.gz usr/share/man/man1/perf-iostat.1.gz usr/share/man/man1/perf- kallsyms.1.gz usr/share/man/man1/perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1/perf-list.1.gz usr/share/man/man1/perf-lock.1.gz usr/share/man/man1/perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz usr/share/man/man1/perf-record.1.gz usr/share/man/man1/perf-report.1.gz usr/share/man/man1/perf-sched.1.gz usr/share/man/man1/perf-script-perl.1.gz usr/share/man/man1/perf- script-python.1.gz usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf-stat.1.gz usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf-timechart.1.gz usr/share/man/man1/perf- top.1.gz usr/share/man/man1/perf-trace.1.gz usr/share/man/man1/perf- version.1.gz usr/share/man/man1/perf.1.gz] failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-53.59 Status in linux-intel-iotg package in Ubuntu: Confirmed Bug description: 1w ProblemType: Package DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: linux-intel-iotg-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Dec 2 12:34:33 2022 DpkgTerminalLog: Preparing to unpack .../linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb ... Unpacking linux-intel-iotg-tools-common (5.15.0-1021.26) over (5.15.0-1017.22) ... dpkg: error processing archive /var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-53.59 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-53.59 InstallationDate: Installed on 2022-10-09 (54 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-intel-iotg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/1998588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998602] Re: overlay writing user.* xattrs on symlinks
> I had thought I should be able to reproduce it by mounting (in an unprivileged user+mountns) an overlayfs where the underlay has, say, "/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable dnsmasq is doing), but that did not work for me. Fwiw, I think you need index=on enabled for origin xattrs to be set. -- 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/1998602 Title: overlay writing user.* xattrs on symlinks Status in linux package in Ubuntu: Incomplete Bug description: This was reported (and worked around) in https://github.com/project- stacker/stacker/pull/333. The kernel does not allow user.* xattrs on a symlink. However, on 5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu mainline build (6.1.0-060100rc5-generic), an unprivileged program can cause such xattrs to be created. Once they're there, userspace (i.e. setfattr) cannot remove them since the kernel says they can't exist - but listxattr shows them. I've failed so far in setting up a simpler reproducer, so I'll begin by reporting the full reproducer. Download 'stacker' from https://github.com/project- stacker/stacker/releases/download/v0.22.1/stacker . Create a stacker.yaml config file: cat > stacker.yaml << EOF pxe-server-base: from: type: docker url: docker://ubuntu:jammy run: | apt-get update apt-get -y install dnsmasq systemd sb-pxe-server: from: type: built tag: pxe-server-base run: | systemctl disable dnsmasq EOF and run 'stacker build'. It will end with: Executing: /lib/systemd/systemd-sysv-install disable dnsmasq Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service. error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: failed to remove attr user.overlay.origin: xattr.LRemove /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq user.overlay.origin: operation not permitted error: exit status 1 You'll subsequently see that ./roots/sb-pxe- server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with user.overlay.origin xattr (per llistxatr), though you can't read the contents or delete it. I had thought I should be able to reproduce it by mounting (in an unprivileged user+mountns) an overlayfs where the underlay has, say, "/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable dnsmasq is doing), but that did not work for me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860284]
Thanks for those! It's a little overwhelming, but I don't see any issues related to the comment #62 patch. It seems to work as I expect on your system. There are definitely dock hotplug issues and the performance issue, but those are problems for different reports. -- 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/1860284 Title: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1860284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860284]
Since your laptop does match d341838d776a, I don't think the comment #62 patch will make much difference. It will likely change MMCONFIG messages from "reserved in E820" to "reserved in ACPI motherboard resources", but won't change the behavior. No need to repeat with v6.1-rc7. A single .tgz or even just the single dmesg log would be great. I don't think lsmod/lspci/etc are relevant for this bug, but no harm in including 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/1860284 Title: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1860284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860284]
Yes, it is overwhelming, isn't it. The only thing that seems to stick out for me is when I sdiff pairs of lsmod and lsusb files where it seems like the states of the devices should return to the initial states after plugging or unplugging the TBT4 Dock. For example, when I sdiff these two files, there are just a few diffs in the TBT-related Flags: test-f-without-tbt4-on-at-boot-thunderbolt-debug/lspci-vv-boot-without-tbt4-on.txt test-f-without-tbt4-on-at-boot-thunderbolt-debug/lspci-vv-boot-without-tbt4-on-unplugged.txt It seems that these two files should show the TBT PCI Devices in the same state ? But it's been almost 40 years since I messed with any low level PeeCee firmware programming and I am just a tad behind the times :) Anyhow, thanks for what you ( and all the Kernel Devs ) do ! I appreciate you !! -- kjh -- 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/1860284 Title: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1860284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~
[Kernel-packages] [Bug 1860284]
p.s. Yes Bjorn, your patch from commentt #62 worked perfectly, even after I removed the Clevo Entry from the pci_crs_quirks[] array. -- 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/1860284 Title: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1860284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860284]
Created attachment 303339 6.0.10 Logs Bjorn -- Attached anker-tests-e..f-tar.gz Manifest is below. I went ahead and included all the logs I had already gathered yesterday after reading this thread. Notable: 1. The Patches I applied are in kernel_config_debug/linux-6.0.10.kjh_dp.patch 2. Test(e) - Boot with Thunderbolt Attached ... Read Performance dropped from ~800 MB/sec to 39 MB/sec hdparm after unplugging then replugging the TBT This did not happen when I booted with TBT unplugged ... Thank You ! -- kjh Manifest of anker-tests-e..f-tar.gz in temporal order: kernel_config_debug/ .config linux-6.0.10.kjh_dp.patch test-e-with-tbt4-on-at-boot-thunderbolt-debug/ dmesg-boot-with-tbt4-on.txt lsusb-vv-boot-with-tbt4-on.txt lsmod-boot-with-tbt4-on.txt lspci-vv-boot-with-tbt4-on.txt hdparm--direct-t_sda3-boot-with-tbt4-on.txt dmesg-boot-with-tbt4-on-unplugged.txt lsusb-vv-boot-with-tbt4-on-unplugged.txt lspci-vv-boot-with-tbt4-on-unplugged.txt lsmod-boot-with-tbt4-on-unplugged.txt dmesg-boot-with-tbt4-on-replugged.txt lsmod-boot-with-tbt4-on-replugged.txt lspci-vv-boot-with-tbt4-on-replugged.txt hdparm--direct-t_sda3-boot-with-tbt4-on-replugged.txt lsmod-boot-with-tbt4-on-replugged-after-hdparm.txt test-f-without-tbt4-on-at-boot-thunderbolt-debug/ dmesg-boot-without-tbt4-on.txt lspci-vv-boot-without-tbt4-on.txt lsusb-vv-boot-without-tbt4-on.txt lsmod-boot-without-tbt4-on.txt dmesg-boot-without-tbt4-on-plugged.txt lsmod-boot-without-tbt4-on-plugged.txt lspci-vv-boot-without-tbt4-on-plugged.txt lsusb-vv-boot-without-tbt4-on-plugged.txt hdparm--direct-t_sda3-boot-without-tbt4-on-plugged.txt dmesg-boot-without-tbt4-on-unplugged.txt lsmod-boot-without-tbt4-on-unplugged.txt lspci-vv-boot-without-tbt4-on-unplugged.txt lsusb-vv-boot-without-tbt4-on-unplugged.txt dmesg-boot-without-tbt4-on-replugged.txt lsmod-boot-without-tbt4-on-replugged.txt lspci-vv-boot-without-tbt4-on-replugged.txt lsusb-vv-boot-without-tbt4-on-replugged.txt hdparm--direct-t_sda3-boot-without-tbt4-on-replugged.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/1860284 Title: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-gener
[Kernel-packages] [Bug 1860284]
Bjorn -- My Laptop does match d341838d776a # dmesg -t |grep DMI: DMI: Notebook X170KM-G/X170KM-G, BIOS 1.07.08LS1 01/11/2020 I've already built 6.0.10 with your patches and I booted yesterday afternoon with these CommandLine Args: ro nvidia-drm.modeset=1 thunderbolt.dyndbg=+p efi=debug loglevel=3 udev.log_level=3 Note that Mika gave me the thunderbolt.dyndbg=+p Arg and it does print some 'interesting but mysterious' info :) I've already gatherred the two sets of logs, so ... Q1: Would you prefer a single .tgz file with the logs in sub- directories or do you prefer multiple attachments in this thread ? Q2: Would you prefer logs for linux 6.1-rc7 ? I can build that one and gather logs for 6.1-rc7 instead of 6.0.y if you prefer. Thanks again Bjorn ! -- kjh -- 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/1860284 Title: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1860284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/L
[Kernel-packages] [Bug 1860284]
Bjorn -- Not to butt in, but ... If you want it, I've built 6.0.10 with your Patches and I ran the same tests. I've got a Sager NP9672M Laptop which is a rebranded Clevo X1170KM-G I've been working with Mika on Bug 214259 - Discrete Thunderbolt Controller 8086:1137 throws DMAR and XHCI errors and is only partially functional -- kjh -- 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/1860284 Title: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1860284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860284]
Hi Konrad, you're not butting in at all! Things got a little tangled up here. I think bug 214259 describes two issues: 1) Hot-added devices, e.g., an ethernet NIC in a dock, don't work. This should be helped by https://git.kernel.org/linus/d341838d776a, which appeared in v5.19, but only for the machines specifically listed in that patch. 2) I/O page faults related to IOMMU and USB. I think this one is still unresolved, and I don't think the comment #62 patch will help. Your laptop is a rebranded Clevo. Does it match the d341838d776a list? You can tell by looking for "PCI: %s detected: not clipping E820 regions from _CRS" in your dmesg log. If your laptop does not match the list, hot-added devices probably will not work with v6.0. If the comment #62 patch makes them work better, that information would be extremely valuable. A dmesg log from a boot with "pci=use_e820 efi=debug" would be very helpful. -- 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/1860284 Title: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1860284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1998601] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998601 Title: Performance issues with QEMU-KVM in Windows Guests Status in linux package in Ubuntu: Confirmed Bug description: Hi to all, i'm detecting huge performance problems in a Windows 11 VM in a QEMU-KVM environment hosted by Ubuntu 22.10. I have a 12700H intel cpu and Ubuntu is running the stock kernel (5.19.0.26.27). Normally the virtual machine works without any issues. Anyway when i do some complex operations that involves the use of all the cores simultaneously (such a Windows update operation or a compilation of huge c++ project) the guest starts to lag (even the mouse can't be moved for several seconds). I can reproduce always the issue by compiling a specific huge c++ project inside Visual Studio 2022. At specific point, where visual studio collects all the data and starts to compile, the guest freezes and lags for several seconds and then returns to operate normally. I've tried to update to the newest 6.0.9 kernel but the problem still persists. Anyway reverting to the older 5.18.19 there is no such problem even compiling the huge c++ project, So i think that there is something that has changed starting from kernel 5.19. Any clue for this? Thanks for your attention ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-26-generic 5.19.0-26.27 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcoroccagli 2113 F wireplumber /dev/snd/seq:marcoroccagli 2110 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 2 14:32:58 2022 InstallationDate: Installed on 2022-11-29 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 82RB ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=45b01693-19c0-4fc0-b7f2-99912bf9fe6d ro quiet splash intel_iommu=on vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2022 dmi.bios.release: 1.46 dmi.bios.vendor: LENOVO dmi.bios.version: J2CN46WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 5 15IAH7H dmi.ec.firmware.release: 1.46 dmi.modalias: dmi:bvnLENOVO:bvrJ2CN46WW:bd09/28/2022:br1.46:efr1.46:svnLENOVO:pn82RB:pvrLegion515IAH7H:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion515IAH7H:skuLENOVO_MT_82RB_BU_idea_FM_Legion515IAH7H: dmi.product.family: Legion 5 15IAH7H dmi.product.name: 82RB dmi.product.sku: LENOVO_MT_82RB_BU_idea_FM_Legion 5 15IAH7H dmi.product.version: Legion 5 15IAH7H dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998602] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1998602 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998602 Title: overlay writing user.* xattrs on symlinks Status in linux package in Ubuntu: Incomplete Bug description: This was reported (and worked around) in https://github.com/project- stacker/stacker/pull/333. The kernel does not allow user.* xattrs on a symlink. However, on 5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu mainline build (6.1.0-060100rc5-generic), an unprivileged program can cause such xattrs to be created. Once they're there, userspace (i.e. setfattr) cannot remove them since the kernel says they can't exist - but listxattr shows them. I've failed so far in setting up a simpler reproducer, so I'll begin by reporting the full reproducer. Download 'stacker' from https://github.com/project- stacker/stacker/releases/download/v0.22.1/stacker . Create a stacker.yaml config file: cat > stacker.yaml << EOF pxe-server-base: from: type: docker url: docker://ubuntu:jammy run: | apt-get update apt-get -y install dnsmasq systemd sb-pxe-server: from: type: built tag: pxe-server-base run: | systemctl disable dnsmasq EOF and run 'stacker build'. It will end with: Executing: /lib/systemd/systemd-sysv-install disable dnsmasq Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service. error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: failed to remove attr user.overlay.origin: xattr.LRemove /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq user.overlay.origin: operation not permitted error: exit status 1 You'll subsequently see that ./roots/sb-pxe- server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with user.overlay.origin xattr (per llistxatr), though you can't read the contents or delete it. I had thought I should be able to reproduce it by mounting (in an unprivileged user+mountns) an overlayfs where the underlay has, say, "/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable dnsmasq is doing), but that did not work for me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998194] Re: Please add support for Qualcomm IPC Router in 5.4 focal kernel
** Description changed: The modemmanager debian package in focal was recently upgraded to 1.18 - (apparently the jammy version was backported). This version has broken - some Qualcomm modems as it start to require the Qualcomm IPC Router for - them, which drivers are not enabled in Ubuntu kernel 5.4. To fix this we - need these options enabled in the focal kernel: + (the jammy version was backported - see LP: #1965901). This version has + broken some Qualcomm modems as it start to require the Qualcomm IPC + Router for them, which drivers are not enabled in Ubuntu kernel 5.4. To + fix this we need these options enabled in the focal kernel: CONFIG_QRTR=m CONFIG_QRTR_SMD=m CONFIG_QRTR_TUN=m CONFIG_QRTR_MHI=m The options are already enabled in more modern Ubuntu kernel, i.e. 5.17. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998194 Title: Please add support for Qualcomm IPC Router in 5.4 focal kernel Status in linux package in Ubuntu: Confirmed Bug description: The modemmanager debian package in focal was recently upgraded to 1.18 (the jammy version was backported - see LP: #1965901). This version has broken some Qualcomm modems as it start to require the Qualcomm IPC Router for them, which drivers are not enabled in Ubuntu kernel 5.4. To fix this we need these options enabled in the focal kernel: CONFIG_QRTR=m CONFIG_QRTR_SMD=m CONFIG_QRTR_TUN=m CONFIG_QRTR_MHI=m The options are already enabled in more modern Ubuntu kernel, i.e. 5.17. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998602] [NEW] overlay writing user.* xattrs on symlinks
Public bug reported: This was reported (and worked around) in https://github.com/project- stacker/stacker/pull/333. The kernel does not allow user.* xattrs on a symlink. However, on 5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu mainline build (6.1.0-060100rc5-generic), an unprivileged program can cause such xattrs to be created. Once they're there, userspace (i.e. setfattr) cannot remove them since the kernel says they can't exist - but listxattr shows them. I've failed so far in setting up a simpler reproducer, so I'll begin by reporting the full reproducer. Download 'stacker' from https://github.com/project- stacker/stacker/releases/download/v0.22.1/stacker . Create a stacker.yaml config file: cat > stacker.yaml << EOF pxe-server-base: from: type: docker url: docker://ubuntu:jammy run: | apt-get update apt-get -y install dnsmasq systemd sb-pxe-server: from: type: built tag: pxe-server-base run: | systemctl disable dnsmasq EOF and run 'stacker build'. It will end with: Executing: /lib/systemd/systemd-sysv-install disable dnsmasq Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service. error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: failed to remove attr user.overlay.origin: xattr.LRemove /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq user.overlay.origin: operation not permitted error: exit status 1 You'll subsequently see that ./roots/sb-pxe- server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with user.overlay.origin xattr (per llistxatr), though you can't read the contents or delete it. I had thought I should be able to reproduce it by mounting (in an unprivileged user+mountns) an overlayfs where the underlay has, say, "/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable dnsmasq is doing), but that did not work for me. ** 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/1998602 Title: overlay writing user.* xattrs on symlinks Status in linux package in Ubuntu: New Bug description: This was reported (and worked around) in https://github.com/project- stacker/stacker/pull/333. The kernel does not allow user.* xattrs on a symlink. However, on 5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu mainline build (6.1.0-060100rc5-generic), an unprivileged program can cause such xattrs to be created. Once they're there, userspace (i.e. setfattr) cannot remove them since the kernel says they can't exist - but listxattr shows them. I've failed so far in setting up a simpler reproducer, so I'll begin by reporting the full reproducer. Download 'stacker' from https://github.com/project- stacker/stacker/releases/download/v0.22.1/stacker . Create a stacker.yaml config file: cat > stacker.yaml << EOF pxe-server-base: from: type: docker url: docker://ubuntu:jammy run: | apt-get update apt-get -y install dnsmasq systemd sb-pxe-server: from: type: built tag: pxe-server-base run: | systemctl disable dnsmasq EOF and run 'stacker build'. It will end with: Executing: /lib/systemd/systemd-sysv-install disable dnsmasq Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service. error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: failed to remove attr user.overlay.origin: xattr.LRemove /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq user.overlay.origin: operation not permitted error: exit status 1 You'll subsequently see that ./roots/sb-pxe- server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with user.overlay.origin xattr (per llistxatr), though you can't read the contents or delete it. I had thought I should be able to reproduce it by mounting (in an unprivileged user+mountns) an overlayfs where the underlay has, say, "/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable dnsmasq is doing), but that did not work for me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998601] [NEW] Performance issues with QEMU-KVM in Windows Guests
Public bug reported: Hi to all, i'm detecting huge performance problems in a Windows 11 VM in a QEMU-KVM environment hosted by Ubuntu 22.10. I have a 12700H intel cpu and Ubuntu is running the stock kernel (5.19.0.26.27). Normally the virtual machine works without any issues. Anyway when i do some complex operations that involves the use of all the cores simultaneously (such a Windows update operation or a compilation of huge c++ project) the guest starts to lag (even the mouse can't be moved for several seconds). I can reproduce always the issue by compiling a specific huge c++ project inside Visual Studio 2022. At specific point, where visual studio collects all the data and starts to compile, the guest freezes and lags for several seconds and then returns to operate normally. I've tried to update to the newest 6.0.9 kernel but the problem still persists. Anyway reverting to the older 5.18.19 there is no such problem even compiling the huge c++ project, So i think that there is something that has changed starting from kernel 5.19. Any clue for this? Thanks for your attention ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-26-generic 5.19.0-26.27 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcoroccagli 2113 F wireplumber /dev/snd/seq:marcoroccagli 2110 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 2 14:32:58 2022 InstallationDate: Installed on 2022-11-29 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 82RB ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=45b01693-19c0-4fc0-b7f2-99912bf9fe6d ro quiet splash intel_iommu=on vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2022 dmi.bios.release: 1.46 dmi.bios.vendor: LENOVO dmi.bios.version: J2CN46WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 5 15IAH7H dmi.ec.firmware.release: 1.46 dmi.modalias: dmi:bvnLENOVO:bvrJ2CN46WW:bd09/28/2022:br1.46:efr1.46:svnLENOVO:pn82RB:pvrLegion515IAH7H:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion515IAH7H:skuLENOVO_MT_82RB_BU_idea_FM_Legion515IAH7H: dmi.product.family: Legion 5 15IAH7H dmi.product.name: 82RB dmi.product.sku: LENOVO_MT_82RB_BU_idea_FM_Legion 5 15IAH7H dmi.product.version: Legion 5 15IAH7H dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 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/1998601 Title: Performance issues with QEMU-KVM in Windows Guests Status in linux package in Ubuntu: New Bug description: Hi to all, i'm detecting huge performance problems in a Windows 11 VM in a QEMU-KVM environment hosted by Ubuntu 22.10. I have a 12700H intel cpu and Ubuntu is running the stock kernel (5.19.0.26.27). Normally the virtual machine works without any issues. Anyway when i do some complex operations that involves the use of all the cores simultaneously (such a Windows update operation or a compilation of huge c++ project) the guest starts to lag (even the mouse can't be moved for several seconds). I can reproduce always the issue by compiling a specific huge c++ project inside Visual Studio 2022. At specific point, where visual studio collects all the data and starts to compile, the guest freezes and lags for several seconds and then returns to operate normally. I've tried to update to the newest 6.0.9 kernel but the problem still persists. Anyway reverting to the older 5.18.19 there is no such problem even compiling the huge c++ project, So i think that there is something that has changed starting from kernel 5.19. Any clue for this? Thanks for your attention ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-26-generic 5.19.0-26.27 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcoroccagli 2113 F wireplumber /dev/snd/seq:marcoroccagli 2110 F pipewire CRDA: N/A CasperMD5CheckResult: pass
[Kernel-packages] [Bug 1990876] Re: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module
The problem seems to have, finally, gone with linux-image-5.15.0.53: 5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:53:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This bug report can now be closed. -- 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/1990876 Title: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module Status in linux package in Ubuntu: Incomplete Bug description: Using Ubuntu 22.04, as of yesterday night upon rebooting the framework laptop (which had not been rebooted for several weeks), the fans come on strong and I see, with top, a kworker process at nearly 100% CPU utilization, which makes the laptop unusable. I have an early Framework laptop with an 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz. I removed all USB-c expansion cards except for one with an USB-c pass through, to no avail. With perf I have been able to determine that the xhci_hub_control and perhaps xhci_bus_suspend are at fault. As a matter of fact, the laptop cannot suspend any more, when it was working flawlessly until the reboot. $ sudo apt install linux-tools-common linux-tools-$(uname -r) $ sudo -i # echo -1 > /proc/sys/kernel/perf_event_paranoid # perf record control-c # perf report Samples: 125K of event 'cycles', Event count (approx.): 142991820424 Overhead Command Shared Object Symbol 54.11% kworker/5:2+usb [kernel.kallsyms] [k] xhci_hub_control ◆ 7.94% kworker/5:2+usb [kernel.kallsyms] [k] xhci_bus_suspend ▒ 0.98% kworker/5:2+usb [kernel.kallsyms] [k] kfree ▒ 0.86% kworker/5:2+usb [kernel.kallsyms] [k] _raw_spin_lock_irqsave ... What can be done to address this issue with a kworker? I suspect perhaps the new kernel is at fault. I tried rebooting to the prior kernel 5.15.0-47-generic and 5.15.0-46-generic, but with the same result. What has changed? What can be done about this kworker and the xchi_hub_control? A temporary solution: $ sudo modprobe -r xhci_pci … which results in the kworker process disappearing from `top` (reduced CPU usage to near zero), the fans wind down, and unfortunately the ethernet expansion bay doesn’t work anymore but at least wifi does. Keyboard and touchpad also work. And suspend with deep also work well, just tested it. I assume other expansion bays will stop working too, but the laptop is at least charging: the USB-c pass-through works. See also: https://community.frame.work/t/kworker-stuck-at-near-100-cpu-usage-with-ubuntu-22-04/23053/2 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: albert 4870 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 18:14:26 2022 InstallationDate: Installed on 2022-03-11 (199 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Framework Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezm1f9@/vmlinuz-5.15.0-48-generic root=ZFS=rpool/ROOT/ubuntu_ezm1f9 ro quiet splash nvme.noacpi=1 mem_sleep_default=deep vt.handoff=1 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: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (150 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 3.16 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.10 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0B dmi.board.vendor: Framework dmi.board.version: AB dmi.chassis.asset.tag: FRANBMCPAB1484011X dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AB dmi.modalias: dmi:bvnINSYDECorp.:bvr03.10:bd07/19/2022:br3.16:svnFramework:pnLaptop:pvrAB:rvnFramework:rnFRANBMCP0B:rvrAB:cvnFramework:ct10:cvrAB:skuFRANBMCP0B: dmi.product.family: FRANBMCP dmi.product.name: Laptop dmi.product.sku: FRANBMCP0B dmi.product.version: AB dmi.sys.vend
[Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all
Hi all! I experienced the same problem on my UX582HS (ZenBook Pro Duo OLED 11th gen). Is there an update or could anyone solve the problem? Thanks! -- 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/1981433 Title: [Asus Zenbook UX3402ZA] Sound doesn't work at all Status in linux package in Ubuntu: Confirmed Bug description: Sound/speakers don't work at all on Asus Zenbook 14 OLED and other similar models with Realtek ALC294. No solution works. Audio is not muted, tried adding snd-hda arguments - no dice. This has been reported numerous times, when will a fix finally be rolled out?! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1730 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 12 13:57:05 2022 InstallationDate: Installed on 2022-07-12 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990964] Re: FTBFS on kinetic
This bug was fixed in the package strace - 5.19-0ubuntu1 --- strace (5.19-0ubuntu1) lunar; urgency=medium * New upstream release (LP: #1990964) * Update d/copyright to reflect upstream relicensing to LGPL >= 2.1 from 2018 and its switch from sourceforge to github. * Drop merged patch 0006-s390-Check-infmname-with-IS_ARRAY_ZERO-too.patch -- Adrien Nader Mon, 21 Nov 2022 16:05:44 +0100 ** Changed in: strace (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990964 Title: FTBFS on kinetic Status in linux package in Ubuntu: Fix Released Status in strace package in Ubuntu: Fix Released Status in linux source package in Kinetic: New Status in strace source package in Kinetic: New Bug description: As can be seen in [1], strace FTBFS in kinetic: this is caused by the kernel headers (linux-libc-dev) which do not define F_GETLK64 and other on 64b builds because the kernel contains a bogus commit (306f7cc1e906 "uapi: always define F_GETLK64/F_SETLK64/F_SETLKW64 in fcntl.h"). This commit actually did the opposite of what it was supposed to do, namely defining those macros even on 64b builds. There is an attempt here to fix this which was not merged yet: https://lore.kernel.org/lkml/cajf2gtqtnmoeb62-63ou8y4dbrdym7iztdtfluxx9u0ltwu...@mail.gmail.com/T/ [1]: https://launchpadlibrarian.net/625441996/buildlog_ubuntu-kinetic- amd64.strace_5.16-0ubuntu4_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990964/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998589] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998589 Title: Ubuntu shows black screen after boot, when connected to external monitor Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu shows black screen after boot, when connected to external monitor through docking station. Thinkpad e14 gen 2. Closed lid. When detached from docking station, and lid opened Ubuntu still showing blank screen even on internal monitor. There is no possibility to switch to terminal. Closing and opening lid don't fix the issue. The only option is to hard restart laptop while detached from docking station, and connect to it after logging in to the system. I didn't have the problem month ago. Some update probably caused it. Docking station - ThinkPad USB-C Dock Gen 2 (40AS). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: as 5816 F pulseaudio /dev/snd/controlC1: as 5816 F pulseaudio /dev/snd/controlC0: as 5816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Dec 2 10:10:31 2022 InstallationDate: Installed on 2020-12-06 (725 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20T6000TPB ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=a5796f3d-37a8-428b-aa28-c160ea77bc9b ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2021 dmi.bios.release: 1.16 dmi.bios.vendor: LENOVO dmi.bios.version: R1AET40W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20T6000TPB dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrR1AET40W(1.16):bd09/06/2021:br1.16:efr1.16:svnLENOVO:pn20T6000TPB:pvrThinkPadE14Gen2:rvnLENOVO:rn20T6000TPB:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20T6_BU_Think_FM_ThinkPadE14Gen2: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20T6000TPB dmi.product.sku: LENOVO_MT_20T6_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998589/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998589] [NEW] Ubuntu shows black screen after boot, when connected to external monitor
Public bug reported: Ubuntu shows black screen after boot, when connected to external monitor through docking station. Thinkpad e14 gen 2. Closed lid. When detached from docking station, and lid opened Ubuntu still showing blank screen even on internal monitor. There is no possibility to switch to terminal. Closing and opening lid don't fix the issue. The only option is to hard restart laptop while detached from docking station, and connect to it after logging in to the system. I didn't have the problem month ago. Some update probably caused it. Docking station - ThinkPad USB-C Dock Gen 2 (40AS). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: as 5816 F pulseaudio /dev/snd/controlC1: as 5816 F pulseaudio /dev/snd/controlC0: as 5816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Dec 2 10:10:31 2022 InstallationDate: Installed on 2020-12-06 (725 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20T6000TPB ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=a5796f3d-37a8-428b-aa28-c160ea77bc9b ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2021 dmi.bios.release: 1.16 dmi.bios.vendor: LENOVO dmi.bios.version: R1AET40W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20T6000TPB dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrR1AET40W(1.16):bd09/06/2021:br1.16:efr1.16:svnLENOVO:pn20T6000TPB:pvrThinkPadE14Gen2:rvnLENOVO:rn20T6000TPB:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20T6_BU_Think_FM_ThinkPadE14Gen2: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20T6000TPB dmi.product.sku: LENOVO_MT_20T6_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug 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/1998589 Title: Ubuntu shows black screen after boot, when connected to external monitor Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu shows black screen after boot, when connected to external monitor through docking station. Thinkpad e14 gen 2. Closed lid. When detached from docking station, and lid opened Ubuntu still showing blank screen even on internal monitor. There is no possibility to switch to terminal. Closing and opening lid don't fix the issue. The only option is to hard restart laptop while detached from docking station, and connect to it after logging in to the system. I didn't have the problem month ago. Some update probably caused it. Docking station - ThinkPad USB-C Dock Gen 2 (40AS). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: as 5816 F pulseaudio /dev/snd/controlC1: as 5816 F pulseaudio /dev/snd/controlC0: as 5816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Dec 2 10:10:31 2022 InstallationDate: Installed on 2020-12-06 (725 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20T6000TPB ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=a5796f3d-37a8-428b-aa28-c160ea77bc9b ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2021 dmi.bios.release: 1.16 dmi.bios.vendor: LENOVO dmi.bios.version: R1AET40W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20T6000TPB dmi.board.vendor: LENOVO dmi.
[Kernel-packages] [Bug 1998588] [NEW] package linux-intel-iotg-tools-common 5.15.0-1017.22 [modified: usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-archive.1.gz usr/share/man/man1/perf
Public bug reported: 1w ProblemType: Package DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: linux-intel-iotg-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Dec 2 12:34:33 2022 DpkgTerminalLog: Preparing to unpack .../linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb ... Unpacking linux-intel-iotg-tools-common (5.15.0-1021.26) over (5.15.0-1017.22) ... dpkg: error processing archive /var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-53.59 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-53.59 InstallationDate: Installed on 2022-10-09 (54 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-intel-iotg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check package-conflict -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/1998588 Title: package linux-intel-iotg-tools-common 5.15.0-1017.22 [modified: usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf- archive.1.gz usr/share/man/man1/perf-bench.1.gz usr/share/man/man1/perf-buildid-cache.1.gz usr/share/man/man1/perf- buildid-list.1.gz usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz usr/share/man/man1/perf- daemon.1.gz usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf- diff.1.gz usr/share/man/man1/perf-dlfilter.1.gz usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf- ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf- inject.1.gz usr/share/man/man1/perf-intel-pt.1.gz usr/share/man/man1/perf-iostat.1.gz usr/share/man/man1/perf- kallsyms.1.gz usr/share/man/man1/perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1/perf-list.1.gz usr/share/man/man1/perf-lock.1.gz usr/share/man/man1/perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz usr/share/man/man1/perf-record.1.gz usr/share/man/man1/perf-report.1.gz usr/share/man/man1/perf-sched.1.gz usr/share/man/man1/perf-script-perl.1.gz usr/share/man/man1/perf- script-python.1.gz usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf-stat.1.gz usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf-timechart.1.gz usr/share/man/man1/perf- top.1.gz usr/share/man/man1/perf-trace.1.gz usr/share/man/man1/perf- version.1.gz usr/share/man/man1/perf.1.gz] failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-53.59 Status in linux-intel-iotg package in Ubuntu: New Bug description: 1w ProblemType: Package DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: linux-intel-iotg-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Dec 2 12:34:33 2022 DpkgTerminalLog: Preparing to unpack .../linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb ... Unpacking linux-intel-iotg-tools-common (5.15.0-1021.26) over (5.15.0-1017.22) ... dpkg: error processing archive /var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-53.59 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-53.59 InstallationDate: Installed on 2022-10-09 (54 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-intel-iotg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/1998588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchp
[Kernel-packages] [Bug 1998587] [NEW] nvidia-kernel-source-520 520.56.06-0ubuntu0.20.04.1: nvidia kernel module failed to build
Public bug reported: A error message apperars in my Desktop ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-520 520.56.06-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.15.0-56-generic Date: Fri Dec 2 10:16:46 2022 Dependencies: InstallationDate: Installed on 2022-11-17 (14 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) PackageVersion: 520.56.06-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: nvidia-graphics-drivers-520 Title: nvidia-kernel-source-520 520.56.06-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-520 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-520 in Ubuntu. https://bugs.launchpad.net/bugs/1998587 Title: nvidia-kernel-source-520 520.56.06-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-520 package in Ubuntu: New Bug description: A error message apperars in my Desktop ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-520 520.56.06-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.15.0-56-generic Date: Fri Dec 2 10:16:46 2022 Dependencies: InstallationDate: Installed on 2022-11-17 (14 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) PackageVersion: 520.56.06-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: nvidia-graphics-drivers-520 Title: nvidia-kernel-source-520 520.56.06-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-520/+bug/1998587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998579] [NEW] v4l2-relayd freezes system until it is kicked by OOM
Public bug reported: This may be a very complex scenario with several components involved. But it ends up in v4l2-relayd having allocated 6GB RSS memory, and suspect this memory increase to be the problem, or is it just a side effect? I have seen this error a few times now, and it involves bluetooth, Microsoft Teams and possibly also Chrome. It occurs when I start a Teams meeting, but my bluetooth headset is not connected (possibly a bluetooth bug also). I then do something to activate bluetooth, and then my computer freezes, for half a minute (feels very long). When it becomes alive again, then I can see the OOM in the attached syslog snippet - and Chrome is also killed! System information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 Codename: jammy $ uname -a Linux kfa-Latitude-5521 5.17.0-1018-oem #19-Ubuntu SMP PREEMPT Wed Sep 21 09:54:58 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Some package versions ii libv4l2rds0:amd64 1.22.1-2build1 amd64Video4Linux Radio Data System (RDS) decoding library ii v4l2-relayd 0.1.2-0ubuntu1 amd64Streaming relay for v4l2loopback using GStreamer ii google-chrome-stable 108.0.5359.71-1 amd64The web browser from Google ii teams 1.5.00.23861 amd64Microsoft Teams for Linux is your chat-centered workspace in Office 365. ii bluez 5.64-0ubuntu1 amd64Bluetooth tools and daemons ii bluez-cups5.64-0ubuntu1 amd64Bluetooth printer driver for CUPS ii bluez-obexd 5.64-0ubuntu1 amd64bluez obex daemon ii gir1.2-gnomebluetooth-3.0:amd64 42.0-5 amd64Introspection data for GnomeBluetooth ii gnome-bluetooth 3.34.5-8 amd64GNOME Bluetooth Send To app ii gnome-bluetooth-3-common 42.0-5 all GNOME Bluetooth 3 common files ii gnome-bluetooth-common3.34.5-8 all GNOME Bluetooth common files ii libbluetooth3:amd64 5.64-0ubuntu1 amd64Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth-3.0-13:amd64 42.0-5 amd64GNOME Bluetooth 3 support library ii libgnome-bluetooth13:amd643.34.5-8 amd64GNOME Bluetooth tools - support library ii libkf5bluezqt-data5.92.0-0ubuntu1 all data files for bluez-qt ii libkf5bluezqt6:amd64 5.92.0-0ubuntu1 amd64Qt wrapper for bluez ii libldacbt-enc2:amd64 2.0.2.3+git20200429+ed310a0-4 amd64LDAC Bluetooth encoder library (shared library) ii pulseaudio-module-bluetooth 1:15.99.1+dfsg1-1ubuntu2 amd64Bluetooth module for PulseAudio sound server ii qml-module-org-kde-bluezqt:amd64 5.92.0-0ubuntu1 amd64QML wrapper for bluez ** Affects: oem-priority Importance: Undecided Status: New ** Affects: v4l2-relayd (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth chrome oem-priority teams v4l2-relayd ** Attachment added: "Syslog with OOM" https://bugs.launchpad.net/bugs/1998579/+attachment/5633873/+files/syslog ** Package changed: linux-oem-5.13 (Ubuntu) => v4l2-relayd (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1998579 Title: v4l2-relayd freezes system until it is kicked by OOM Status in OEM Priority Project: New Status in v4l2-relayd package in Ubuntu: New Bug description: This may be a very complex scenario with several components involved. But it ends up in v4l2-relayd having allocated 6GB RSS memory, and suspect this memory increase to be the problem, or is it just a side effect? I have seen this error a few times now, and it involves bluetooth, Microsoft Teams and possibly also Chrome. It occurs when I start a Teams meeting, but my bluetooth headset is not connected (possibly a bluetooth bug also). I then do something to activate bluetooth, and then my computer freezes, for hal
[Kernel-packages] [Bug 1998542] Re: Bionic update: upstream stable patchset 2022-12-01
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998542 Title: Bionic update: upstream stable patchset 2022-12-01 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-12-01 from git://git.kernel.org/ Revert "x86/cpu: Add a steppings field to struct x86_cpu_id" x86/cpufeature: Add facility to check for min microcode revisions x86/cpufeature: Fix various quality problems in the header x86/devicetable: Move x86 specific macro out of generic code x86/cpu: Add consistent CPU match macros x86/cpu: Add a steppings field to struct x86_cpu_id x86/entry: Remove skip_r11rcx x86/cpufeatures: Move RETPOLINE flags to word 11 x86/bugs: Report AMD retbleed vulnerability x86/bugs: Add AMD retbleed= boot parameter x86/bugs: Keep a per-CPU IA32_SPEC_CTRL value x86/entry: Add kernel IBRS implementation x86/bugs: Optimize SPEC_CTRL MSR writes x86/speculation: Add spectre_v2=ibrs option to support Kernel IBRS x86/bugs: Split spectre_v2_select_mitigation() and spectre_v2_user_select_mitigation() x86/bugs: Report Intel retbleed vulnerability entel_idle: Disable IBRS during long idle x86/speculation: Change FILL_RETURN_BUFFER to work with objtool x86/speculation: Add LFENCE to RSB fill sequence x86/speculation: Fix RSB filling with CONFIG_RETPOLINE=n x86/speculation: Fix firmware entry SPEC_CTRL handling x86/speculation: Fix SPEC_CTRL write on SMT state change x86/speculation: Use cached host SPEC_CTRL value for guest entry/exit x86/speculation: Remove x86_spec_ctrl_mask KVM: VMX: Prevent guest RSB poisoning attacks with eIBRS KVM: VMX: Fix IBRS handling after vmexit x86/speculation: Fill RSB on vmexit for IBRS x86/common: Stamp out the stepping madness x86/cpu/amd: Enumerate BTC_NO x86/bugs: Add Cannon lake to RETBleed affected CPU list x86/speculation: Disable RRSBA behavior x86/speculation: Use DECLARE_PER_CPU for x86_spec_ctrl_current x86/bugs: Warn when "ibrs" mitigation is selected on Enhanced IBRS parts x86/speculation: Add RSB VM Exit protections UBUNTU: Upstream stable to v4.14.297, v4.19.263 ocfs2: clear dinode links count in case of error ocfs2: fix BUG when iput after ocfs2_mknod fails x86/microcode/AMD: Apply the patch early on every logical thread ata: ahci-imx: Fix MODULE_ALIAS ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS KVM: arm64: vgic: Fix exit condition in scan_its_table() UBUNTU: [Config] updateconfigs for ARM64_ERRATUM_1742098 arm64: errata: Remove AES hwcap for COMPAT tasks r8152: add PID for the Lenovo OneLink+ Dock btrfs: fix processing of delayed data refs during backref walking ACPI: extlog: Handle multiple records HID: magicmouse: Do not set BTN_MOUSE on double report net/atm: fix proc_mpc_write incorrect return value net: hns: fix possible memory leak in hnae_ae_register() iommu/vt-d: Clean up si_domain in the init_dmars() error path media: v4l2-mem2mem: Apply DST_QUEUE_OFF_BASE on MMAP buffers across ioctls ACPI: video: Force backlight native for more TongFang devices ALSA: Use del_timer_sync() before freeing timer ALSA: au88x0: use explicitly signed char USB: add RESET_RESUME quirk for NVIDIA Jetson devices in RCM usb: dwc3: gadget: Don't set IMI for no_interrupt usb: bdc: change state when port disconnected usb: xhci: add XHCI_SPURIOUS_SUCCESS to ASM1042 despite being a V0.96 controller xhci: Remove device endpoints from bandwidth list when freeing the device tools: iio: iio_utils: fix digit calculation iio: light: tsl2583: Fix module unloading fbdev: smscufx: Fix several use-after-free bugs mac802154: Fix LQI recording drm/msm/hdmi: fix memory corruption with too many bridges mmc: core: Fix kernel panic when remove non-standard SDIO card kernfs: fix use-after-free in __kernfs_remove s390/futex: add missing EX_TABLE entry to __futex_atomic_op() Xen/gntdev: don't ignore kernel unmapping error xen/gntdev: Prevent leaking grants mm,hugetlb: take hugetlb_lock before decrementing h->resv_huge_pages net: ieee802154: fix error return code in dgram_bind() drm/msm: Fix return type of mdp4_lvds_connector_mode_valid arc: iounmap() arg is volatile ALSA: ac97: fix possible memory leak in snd_ac9
[Kernel-packages] [Bug 1998576] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1998576 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998576 Title: UBSAN: shift-out-of-bounds in WiFi driver (iwlwifi/mvm/mac-ctxt.c) Status in linux package in Ubuntu: Incomplete Bug description: Hello all! On Ubuntu 20.04.5 LTS, when I use the mdk3 tool (https://github.com/aircrack-ng/mdk3, also available in Ubuntu PPA), it raises a kernel exception in the Wi-Fi driver: UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 shift exponent 65535 is too large for 64-bit type 'long unsigned int' The exact command I use is : mdk3 wlp2s0 b -f somefile.txt -a -s 200 (Where wlp2s0 is my main Wi-Fi interface.) Here is the full logs: Dec 2 09:22:38 red-october kernel: [ 1228.100538] Dec 2 09:22:38 red-october kernel: [ 1228.100614] UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 Dec 2 09:22:38 red-october kernel: [ 1228.100714] shift exponent 65535 is too large for 64-bit type 'long unsigned int' Dec 2 09:22:38 red-october kernel: [ 1228.102683] CPU: 3 PID: 5865 Comm: ifconfig Tainted: P OE 5.15.0-53-generic #59~20.04.1-Ubuntu Dec 2 09:22:38 red-october kernel: [ 1228.102689] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401II_GA401II/GA401II, BIOS GA401II.220 03/14/2022 Dec 2 09:22:38 red-october kernel: [ 1228.102693] Call Trace: Dec 2 09:22:38 red-october kernel: [ 1228.102696] Dec 2 09:22:38 red-october kernel: [ 1228.102701] dump_stack_lvl+0x4a/0x63 Dec 2 09:22:38 red-october kernel: [ 1228.102713] dump_stack+0x10/0x16 Dec 2 09:22:38 red-october kernel: [ 1228.102718] ubsan_epilogue+0x9/0x49 Dec 2 09:22:38 red-october kernel: [ 1228.102723] __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e Dec 2 09:22:38 red-october kernel: [ 1228.102734] iwl_mvm_mac_ctxt_cmd_listener.cold+0x20/0x32 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102770] iwl_mvm_mac_ctx_send+0x8b/0xd0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102798] iwl_mvm_mac_ctxt_add+0x44/0xf0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102821] iwl_mvm_mac_add_interface+0x133/0x350 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102847] drv_add_interface+0x4a/0x100 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102912] ieee80211_add_virtual_monitor+0x11a/0x330 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102980] ieee80211_do_open+0x867/0x970 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103041] ? ieee80211_check_concurrent_iface+0x158/0x1d0 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103104] ieee80211_open+0x70/0x90 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103165] __dev_open+0xe8/0x1a0 Dec 2 09:22:38 red-october kernel: [ 1228.103172] __dev_change_flags+0x190/0x200 Dec 2 09:22:38 red-october kernel: [ 1228.103178] dev_change_flags+0x26/0x70 Dec 2 09:22:38 red-october kernel: [ 1228.103183] devinet_ioctl+0x5f2/0x780 Dec 2 09:22:38 red-october kernel: [ 1228.103192] inet_ioctl+0x169/0x190 Dec 2 09:22:38 red-october kernel: [ 1228.103199] sock_do_ioctl+0x47/0x100 Dec 2 09:22:38 red-october kernel: [ 1228.103206] sock_ioctl+0xf3/0x310 Dec 2 09:22:38 red-october kernel: [ 1228.103211] ? syscall_exit_to_user_mode+0x27/0x50 Dec 2 09:22:38 red-october kernel: [ 1228.103218] ? do_syscall_64+0x69/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103223] __x64_sys_ioctl+0x95/0xd0 Dec 2 09:22:38 red-october kernel: [ 1228.103232] do_syscall_64+0x5c/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103236] ? irqentry_exit_to_user_mode+0x9/0x20 Dec 2 09:22:38 red-october kernel: [ 1228.103241] ? irqentry_exit+0x1d/0x30 Dec 2 09:22:38 red-october kernel: [ 1228.103246] ? exc_page_fault+0x89/0x170 Dec 2 09:22:38 red-october kernel: [ 1228.103252] entry_SYSCALL_64_after_hwframe+0x61/0xcb Dec 2 09:22:38 red-october kernel: [ 1228.103257] RIP: 0033:0x7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103263] Code: 0f 1e fa 48 8b 05 e5 7a 0d 00 64 c
[Kernel-packages] [Bug 1998576] [NEW] UBSAN: shift-out-of-bounds in WiFi driver (iwlwifi/mvm/mac-ctxt.c)
Public bug reported: Hello all! On Ubuntu 20.04.5 LTS, when I use the mdk3 tool (https://github.com/aircrack-ng/mdk3, also available in Ubuntu PPA), it raises a kernel exception in the Wi-Fi driver: UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 shift exponent 65535 is too large for 64-bit type 'long unsigned int' The exact command I use is : mdk3 wlp2s0 b -f somefile.txt -a -s 200 (Where wlp2s0 is my main Wi-Fi interface.) Here is the full logs: Dec 2 09:22:38 red-october kernel: [ 1228.100538] Dec 2 09:22:38 red-october kernel: [ 1228.100614] UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 Dec 2 09:22:38 red-october kernel: [ 1228.100714] shift exponent 65535 is too large for 64-bit type 'long unsigned int' Dec 2 09:22:38 red-october kernel: [ 1228.102683] CPU: 3 PID: 5865 Comm: ifconfig Tainted: P OE 5.15.0-53-generic #59~20.04.1-Ubuntu Dec 2 09:22:38 red-october kernel: [ 1228.102689] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401II_GA401II/GA401II, BIOS GA401II.220 03/14/2022 Dec 2 09:22:38 red-october kernel: [ 1228.102693] Call Trace: Dec 2 09:22:38 red-october kernel: [ 1228.102696] Dec 2 09:22:38 red-october kernel: [ 1228.102701] dump_stack_lvl+0x4a/0x63 Dec 2 09:22:38 red-october kernel: [ 1228.102713] dump_stack+0x10/0x16 Dec 2 09:22:38 red-october kernel: [ 1228.102718] ubsan_epilogue+0x9/0x49 Dec 2 09:22:38 red-october kernel: [ 1228.102723] __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e Dec 2 09:22:38 red-october kernel: [ 1228.102734] iwl_mvm_mac_ctxt_cmd_listener.cold+0x20/0x32 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102770] iwl_mvm_mac_ctx_send+0x8b/0xd0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102798] iwl_mvm_mac_ctxt_add+0x44/0xf0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102821] iwl_mvm_mac_add_interface+0x133/0x350 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102847] drv_add_interface+0x4a/0x100 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102912] ieee80211_add_virtual_monitor+0x11a/0x330 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102980] ieee80211_do_open+0x867/0x970 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103041] ? ieee80211_check_concurrent_iface+0x158/0x1d0 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103104] ieee80211_open+0x70/0x90 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103165] __dev_open+0xe8/0x1a0 Dec 2 09:22:38 red-october kernel: [ 1228.103172] __dev_change_flags+0x190/0x200 Dec 2 09:22:38 red-october kernel: [ 1228.103178] dev_change_flags+0x26/0x70 Dec 2 09:22:38 red-october kernel: [ 1228.103183] devinet_ioctl+0x5f2/0x780 Dec 2 09:22:38 red-october kernel: [ 1228.103192] inet_ioctl+0x169/0x190 Dec 2 09:22:38 red-october kernel: [ 1228.103199] sock_do_ioctl+0x47/0x100 Dec 2 09:22:38 red-october kernel: [ 1228.103206] sock_ioctl+0xf3/0x310 Dec 2 09:22:38 red-october kernel: [ 1228.103211] ? syscall_exit_to_user_mode+0x27/0x50 Dec 2 09:22:38 red-october kernel: [ 1228.103218] ? do_syscall_64+0x69/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103223] __x64_sys_ioctl+0x95/0xd0 Dec 2 09:22:38 red-october kernel: [ 1228.103232] do_syscall_64+0x5c/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103236] ? irqentry_exit_to_user_mode+0x9/0x20 Dec 2 09:22:38 red-october kernel: [ 1228.103241] ? irqentry_exit+0x1d/0x30 Dec 2 09:22:38 red-october kernel: [ 1228.103246] ? exc_page_fault+0x89/0x170 Dec 2 09:22:38 red-october kernel: [ 1228.103252] entry_SYSCALL_64_after_hwframe+0x61/0xcb Dec 2 09:22:38 red-october kernel: [ 1228.103257] RIP: 0033:0x7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103263] Code: 0f 1e fa 48 8b 05 e5 7a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 7a 0d 00 f7 d8 64 89 01 48 Dec 2 09:22:38 red-october kernel: [ 1228.103267] RSP: 002b:7ffc147740a8 EFLAGS: 0202 ORIG_RAX: 0010 Dec 2 09:22:38 red-october kernel: [ 1228.103273] RAX: ffda RBX: 7ffc147740b0 RCX: 7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103276] RDX: 7ffc147740b0 RSI: 8914 RDI: 0004 Dec 2 09:22:38 red-october kernel: [ 1228.103278] RBP: 7ffc14774160 R08: 0008 R09: 561e451b2940 Dec 2 09:22:38 red-october kernel: [ 1228.103281] R10: 0021 R11: 0202 R12: 0041 Dec 2 09:22:38 red-october kernel: [ 1228.103283] R13: 7ffc14774458 R14: R15: Dec 2 09:22:38 red-october kernel: [ 1228.103288] Dec 2 09:22:38 red-october kernel: [ 1228.103290] ===