[Kernel-packages] [Bug 1952041] Re: Fix i915 TypeC disconnect problems for Intel ADL-P
this needs to be fixed in jammy/5.15 too, unless it's ok to regress when going to hwe-5.15 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1952041 Title: Fix i915 TypeC disconnect problems for Intel ADL-P Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.14 source package in Focal: In Progress Bug description: [SRU Justification] [Impact] When the ADL-P system connects the external display via TypeC port, it will hang after unplugging the TypeC connector. The system will never come back until reboot. [Fix] Intel has released a patch set to fix the TypeC PHY connect/disconnect logic. The shift for ownership of PHY and power domain will be handled correctly for ADL-P. [Test] The ADL-P system will no longer freeze and the ownership will shift correctly after disconnecting the external display connects via TypeC port. [Where problem could occur] It's kind of a big refactor for the i915 TypeC PHY handling logic. Don't know if there's any problems on older platforms. Targeting only on Unstable and latest OEM kernel for lower risk. == Original Bug Description == [Summary] The system will hang on after unplug DA310 with external monitor (on-demand) Note: 1. Build-in HDMI port cannot duplicate. 2. VGA/HDMI/DP on DA310 to system all can duplicate. 3. Unplug VGA/DP/HDMI from DA310, then unplug DA310 from the system cannot duplicate. [Steps to reproduce] 1. Install dell-bto-focal-fossa-pypar-adl-X160-20210923-2.iso 2. Plug DA310 to USB-C port 3. Plug DP/VGA/HDMI to DA310 4. Unplug DA310 > The system hangs on with black screen [Expected result] The system works well after unplug USB-C with external monitor [Actual result] The system hangs on blackscreen after unplug DA310 with external monitor [Failure rate] 3/3 [Additional information] SKU: SIF-MLK-DVT1-C1, SIF-MLK-DVT1-C5, SIF-MLK-DVT1-C6 Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-pypar-adl+X160 system-manufacturer: Dell Inc. system-product-name: Dell G15 5520 bios-version: 0.2.9 CPU: Genuine Intel(R) (12x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:46a3] :01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:25e2] (rev a1) kernel-version: 5.14.0-9002-oem To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952041] 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 1952041 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 ** Changed in: linux (Ubuntu Focal) Status: New => Incomplete ** Tags added: disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1952041 Title: Fix i915 TypeC disconnect problems for Intel ADL-P Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.14 source package in Focal: In Progress Bug description: [SRU Justification] [Impact] When the ADL-P system connects the external display via TypeC port, it will hang after unplugging the TypeC connector. The system will never come back until reboot. [Fix] Intel has released a patch set to fix the TypeC PHY connect/disconnect logic. The shift for ownership of PHY and power domain will be handled correctly for ADL-P. [Test] The ADL-P system will no longer freeze and the ownership will shift correctly after disconnecting the external display connects via TypeC port. [Where problem could occur] It's kind of a big refactor for the i915 TypeC PHY handling logic. Don't know if there's any problems on older platforms. Targeting only on Unstable and latest OEM kernel for lower risk. == Original Bug Description == [Summary] The system will hang on after unplug DA310 with external monitor (on-demand) Note: 1. Build-in HDMI port cannot duplicate. 2. VGA/HDMI/DP on DA310 to system all can duplicate. 3. Unplug VGA/DP/HDMI from DA310, then unplug DA310 from the system cannot duplicate. [Steps to reproduce] 1. Install dell-bto-focal-fossa-pypar-adl-X160-20210923-2.iso 2. Plug DA310 to USB-C port 3. Plug DP/VGA/HDMI to DA310 4. Unplug DA310 > The system hangs on with black screen [Expected result] The system works well after unplug USB-C with external monitor [Actual result] The system hangs on blackscreen after unplug DA310 with external monitor [Failure rate] 3/3 [Additional information] SKU: SIF-MLK-DVT1-C1, SIF-MLK-DVT1-C5, SIF-MLK-DVT1-C6 Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-pypar-adl+X160 system-manufacturer: Dell Inc. system-product-name: Dell G15 5520 bios-version: 0.2.9 CPU: Genuine Intel(R) (12x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:46a3] :01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:25e2] (rev a1) kernel-version: 5.14.0-9002-oem To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952041] Re: Fix i915 TypeC disconnect problems for Intel ADL-P
** Tags added: oem-priority originate-from-1945575 somerville ** Tags added: originate-from-1943562 ** Tags added: originate-from-1949425 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1952041 Title: Fix i915 TypeC disconnect problems for Intel ADL-P Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: In Progress Bug description: [SRU Justification] [Impact] When the ADL-P system connects the external display via TypeC port, it will hang after unplugging the TypeC connector. The system will never come back until reboot. [Fix] Intel has released a patch set to fix the TypeC PHY connect/disconnect logic. The shift for ownership of PHY and power domain will be handled correctly for ADL-P. [Test] The ADL-P system will no longer freeze and the ownership will shift correctly after disconnecting the external display connects via TypeC port. [Where problem could occur] It's kind of a big refactor for the i915 TypeC PHY handling logic. Don't know if there's any problems on older platforms. Targeting only on Unstable and latest OEM kernel for lower risk. == Original Bug Description == [Summary] The system will hang on after unplug DA310 with external monitor (on-demand) Note: 1. Build-in HDMI port cannot duplicate. 2. VGA/HDMI/DP on DA310 to system all can duplicate. 3. Unplug VGA/DP/HDMI from DA310, then unplug DA310 from the system cannot duplicate. [Steps to reproduce] 1. Install dell-bto-focal-fossa-pypar-adl-X160-20210923-2.iso 2. Plug DA310 to USB-C port 3. Plug DP/VGA/HDMI to DA310 4. Unplug DA310 > The system hangs on with black screen [Expected result] The system works well after unplug USB-C with external monitor [Actual result] The system hangs on blackscreen after unplug DA310 with external monitor [Failure rate] 3/3 [Additional information] SKU: SIF-MLK-DVT1-C1, SIF-MLK-DVT1-C5, SIF-MLK-DVT1-C6 Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-pypar-adl+X160 system-manufacturer: Dell Inc. system-product-name: Dell G15 5520 bios-version: 0.2.9 CPU: Genuine Intel(R) (12x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:46a3] :01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:25e2] (rev a1) kernel-version: 5.14.0-9002-oem To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952041] [NEW] Fix i915 TypeC disconnect problems for Intel ADL-P
Public bug reported: [SRU Justification] [Impact] When the ADL-P system connects the external display via TypeC port, it will hang after unplugging the TypeC connector. The system will never come back until reboot. [Fix] Intel has released a patch set to fix the TypeC PHY connect/disconnect logic. The shift for ownership of PHY and power domain will be handled correctly for ADL-P. [Test] The ADL-P system will no longer freeze and the ownership will shift correctly after disconnecting the external display connects via TypeC port. [Where problem could occur] It's kind of a big refactor for the i915 TypeC PHY handling logic. Don't know if there's any problems on older platforms. Targeting only on Unstable and latest OEM kernel for lower risk. == Original Bug Description == [Summary] The system will hang on after unplug DA310 with external monitor (on-demand) Note: 1. Build-in HDMI port cannot duplicate. 2. VGA/HDMI/DP on DA310 to system all can duplicate. 3. Unplug VGA/DP/HDMI from DA310, then unplug DA310 from the system cannot duplicate. [Steps to reproduce] 1. Install dell-bto-focal-fossa-pypar-adl-X160-20210923-2.iso 2. Plug DA310 to USB-C port 3. Plug DP/VGA/HDMI to DA310 4. Unplug DA310 > The system hangs on with black screen [Expected result] The system works well after unplug USB-C with external monitor [Actual result] The system hangs on blackscreen after unplug DA310 with external monitor [Failure rate] 3/3 [Additional information] SKU: SIF-MLK-DVT1-C1, SIF-MLK-DVT1-C5, SIF-MLK-DVT1-C6 Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-pypar-adl+X160 system-manufacturer: Dell Inc. system-product-name: Dell G15 5520 bios-version: 0.2.9 CPU: Genuine Intel(R) (12x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:46a3] :01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:25e2] (rev a1) kernel-version: 5.14.0-9002-oem ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: In Progress ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress -- 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/1952041 Title: Fix i915 TypeC disconnect problems for Intel ADL-P Status in linux package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: In Progress Bug description: [SRU Justification] [Impact] When the ADL-P system connects the external display via TypeC port, it will hang after unplugging the TypeC connector. The system will never come back until reboot. [Fix] Intel has released a patch set to fix the TypeC PHY connect/disconnect logic. The shift for ownership of PHY and power domain will be handled correctly for ADL-P. [Test] The ADL-P system will no longer freeze and the ownership will shift correctly after disconnecting the external display connects via TypeC port. [Where problem could occur] It's kind of a big refactor for the i915 TypeC PHY handling logic. Don't know if there's any problems on older platforms. Targeting only on Unstable and latest OEM kernel for lower risk. == Original Bug Description == [Summary] The system will hang on after unplug DA310 with external monitor (on-demand) Note: 1. Build-in HDMI port cannot duplicate. 2. VGA/HDMI/DP on DA310 to system all can duplicate. 3. Unplug VGA/DP/HDMI from DA310, then unplug DA310 from the system cannot duplicate. [Steps to reproduce] 1. Install dell-bto-focal-fossa-pypar-adl-X160-20210923-2.iso 2. Plug DA310 to USB-C port 3. Plug DP/VGA/HDMI to DA310 4. Unplug DA310 > The system hangs on with black screen [Expected result] The system works well after unplug USB-C with external monitor [Actual result] The system hangs on blackscreen after unplug DA310 with external monitor [Failure rate] 3/3 [Additional information] SKU: SIF-MLK-DVT1-C1, SIF-MLK-DVT1-C5, SIF-MLK-DVT1-C6 Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-pypar-adl+X160 system-manufacturer: Dell Inc. system-product-name: Dell G15 5520 bios-version: 0.2.9 CPU: Genuine Intel(R) (12x) GPU: :00:02.0 VGA compatible controller [0300]: Intel
[Kernel-packages] [Bug 1951861] Re: Fix non-working e1000e device after resume
** Tags added: originate-from-1947661 ** Tags added: originate-from-1947678 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1951861 Title: Fix non-working e1000e device after resume Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] e1000e devices stop working after s2idle resume. [Fix] Revert the offending patch series, which is to bring some minor power saving. [Test] Vendor did extensive tests and didn't find any regression, and the power consumption remains the same. [Where problems could occur] Maybe on some system the series can save some energy, so reverting will cause some power consumption increase. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952018] 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 1952018 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/1952018 Title: [ADL] Thunderbolt patches Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The patches enable discrete thunderbolt supports. [Fix] Intel provides a list of patches to enable discrete thunderbolt [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952018] [NEW] [ADL] Thunderbolt patches
Public bug reported: [Impact] The patches enable discrete thunderbolt supports. [Fix] Intel provides a list of patches to enable discrete thunderbolt [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel AlderLake. Further testing will be required. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: intel oem-priority originate-from-1943511 ** Tags added: intel oem-priority originate-from-1943511 -- 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/1952018 Title: [ADL] Thunderbolt patches Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: [Impact] The patches enable discrete thunderbolt supports. [Fix] Intel provides a list of patches to enable discrete thunderbolt [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952011] Re: [SRU] linux-firmware: add sof-firmware for adl platforms from sof-firmware-v1.9.2
** Description changed: - This bug is for tracking purpose + Because we plan to remove sof-firmware related files from linux-firmware + of jammy and replace them with a debian package firmware-sof-signed, so + this SRU is not applied to jammy. I will submit another SRU to + firmware-sof-signed package later. + + [Impact] + In the Dell oem project, we have many laptops which has sof dmic or + sof soundwire audio design, they need to load firmware and topology + files specific to ADL, otherwise the audio driver will fail to + initialize and the whole audio can't work. + + [Fix] + Integrate the firmware and topology files from sof-firmware-v1.9.2 + + [Test] + Installed the patched linux-firmware and booting the patched kernel, + the audio work well, all output and input devices work normally + + [Where problems could occur] + This SRU introduces new firmware and topology files for adl, it has + low possibility to introduce regression. If it could, it could + possibilily affect the other machines which also need to load firmware + and topology files, it could make the audio can't work on those machines, + but this possibility is very low, we have tested the SRU on many laptops, + no regression found. ** Changed in: linux-firmware (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Impish) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1952011 Title: [SRU] linux-firmware: add sof-firmware for adl platforms from sof- firmware-v1.9.2 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: In Progress Status in linux-firmware source package in Hirsute: In Progress Status in linux-firmware source package in Impish: In Progress Bug description: Because we plan to remove sof-firmware related files from linux-firmware of jammy and replace them with a debian package firmware-sof-signed, so this SRU is not applied to jammy. I will submit another SRU to firmware-sof-signed package later. [Impact] In the Dell oem project, we have many laptops which has sof dmic or sof soundwire audio design, they need to load firmware and topology files specific to ADL, otherwise the audio driver will fail to initialize and the whole audio can't work. [Fix] Integrate the firmware and topology files from sof-firmware-v1.9.2 [Test] Installed the patched linux-firmware and booting the patched kernel, the audio work well, all output and input devices work normally [Where problems could occur] This SRU introduces new firmware and topology files for adl, it has low possibility to introduce regression. If it could, it could possibilily affect the other machines which also need to load firmware and topology files, it could make the audio can't work on those machines, but this possibility is very low, we have tested the SRU on many laptops, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952011] [NEW] [SRU] linux-firmware: add sof-firmware for adl platforms from sof-firmware-v1.9.2
Public bug reported: This bug is for tracking purpose ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Impish) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1948800 somerville ** Changed in: linux-firmware (Ubuntu) Importance: Undecided => High ** Also affects: linux-firmware (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Tags added: oem-priority originate-from-1948800 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1952011 Title: [SRU] linux-firmware: add sof-firmware for adl platforms from sof- firmware-v1.9.2 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Hirsute: New Status in linux-firmware source package in Impish: New Bug description: This bug is for tracking purpose To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952007] 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 1952007 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/1952007 Title: [ADL] ITBM support for Hybrid platforms Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Need ITBM support for Hybrid platforms. Need to change the scheduling order from Core, HT, ATOM to Core, ATOM, HT. When using ITBM on systems that has a mixture of CPUs supporting Hyper-Threading and others not supporting it (even offlining HT siblings may cause the issue to be reproducible). Hybrid topologies meet the aforementioned condition. In such cases, threads will be consolidated on CPUs of high priority using got HT siblings, while CPUs of medium priority will remain idle. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable AlderLake [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952006] Re: [TGL][ADL] ACRN hypervisor support
** Description changed: [Impact] The driver enables the host to run ACRN hypervisor which is a flexible, lightweight reference hypervisor, built with real-time and safety- criticality in mind, optimized to streamline embedded development through an open-source platform. https://projectacrn.org/ [Fix] - Intel provides a list of patches to enable Tiger Lake ROP CET. + Intel provides a list of patches to enable ACRN hypervisor [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel TigerLake/AlderLake. Further testing will be required. -- 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/1952006 Title: [TGL][ADL] ACRN hypervisor support Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The driver enables the host to run ACRN hypervisor which is a flexible, lightweight reference hypervisor, built with real-time and safety-criticality in mind, optimized to streamline embedded development through an open-source platform. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable ACRN hypervisor [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel TigerLake/AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952007] [NEW] [ADL] ITBM support for Hybrid platforms
Public bug reported: [Impact] Need ITBM support for Hybrid platforms. Need to change the scheduling order from Core, HT, ATOM to Core, ATOM, HT. When using ITBM on systems that has a mixture of CPUs supporting Hyper-Threading and others not supporting it (even offlining HT siblings may cause the issue to be reproducible). Hybrid topologies meet the aforementioned condition. In such cases, threads will be consolidated on CPUs of high priority using got HT siblings, while CPUs of medium priority will remain idle. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable AlderLake [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel AlderLake. Further testing will be required. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: intel oem-priority originate-from-1943549 ** Tags added: intel oem-priority originate-from-1943549 -- 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/1952007 Title: [ADL] ITBM support for Hybrid platforms Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: [Impact] Need ITBM support for Hybrid platforms. Need to change the scheduling order from Core, HT, ATOM to Core, ATOM, HT. When using ITBM on systems that has a mixture of CPUs supporting Hyper-Threading and others not supporting it (even offlining HT siblings may cause the issue to be reproducible). Hybrid topologies meet the aforementioned condition. In such cases, threads will be consolidated on CPUs of high priority using got HT siblings, while CPUs of medium priority will remain idle. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable AlderLake [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952006] 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 1952006 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/1952006 Title: [TGL][ADL] ACRN hypervisor support Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The driver enables the host to run ACRN hypervisor which is a flexible, lightweight reference hypervisor, built with real-time and safety-criticality in mind, optimized to streamline embedded development through an open-source platform. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable Tiger Lake ROP CET. [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel TigerLake/AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952006] [NEW] [TGL][ADL] ACRN hypervisor support
Public bug reported: [Impact] The driver enables the host to run ACRN hypervisor which is a flexible, lightweight reference hypervisor, built with real-time and safety- criticality in mind, optimized to streamline embedded development through an open-source platform. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable Tiger Lake ROP CET. [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel TigerLake/AlderLake. Further testing will be required. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: intel oem-priority originate-from-1943552 ** Tags added: intel oem-priority originate-from-1943552 -- 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/1952006 Title: [TGL][ADL] ACRN hypervisor support Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: [Impact] The driver enables the host to run ACRN hypervisor which is a flexible, lightweight reference hypervisor, built with real-time and safety-criticality in mind, optimized to streamline embedded development through an open-source platform. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable Tiger Lake ROP CET. [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel TigerLake/AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947709] Re: Drop "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active"
verified the same revert is on Impish/Focal/Bionic. switching verification completed for those ** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-impish ** Tags added: verification-done-bionic verification-done-focal verification-done-impish -- 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/1947709 Title: Drop "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active" Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Confirmed Bug description: [Impact] "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active" has been applied to fix a page leaking issue. However a slightly different fix has been applied upstream: 9a24ce5b66f9c8190d63b15f4473600db4935f1f cachefiles: Fix page leak in cachefiles_read_backing_file while vmscan is active Basically we are fixing the same issue in two different ways at the same time, but even worse our patch an introduce a potential NULL pointer dereference: we do a put_page(newpage) and set newpage = NULL in the main for() loop and then we may do additional put_page(newpage) after the main for loop if ret == -EEXIST, that would trigger the NULL pointer dereference. [Test case] No test case or reproducer is available at the moment, this issue has been found simply by reviewing the code. [Fix] Drop the SAUCE patch and rely on the upstream fix. [Regression potential] If the analysis is not correct we may re-introduce a page leak in cachefiles (NFS for example), but it seems unlikely to happen, since the upstream fix is addressing the page leaking already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947709/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950339] 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 1950339 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-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950339] Re: Screen stays black after going idle or waking up from suspend on AMD laptop
** Also 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-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux package in Ubuntu: New Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798363] Re: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
Rmmod and modprone i2c_hid doesn't work. I can't figure out what's causing this problem I tried all the lastest Linux kernels and still same issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798363 Title: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740053] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740764] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.741478] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.742205] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.742921] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.743624] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.744321] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.745026] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.745714] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.746420] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Lots of these things ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: blurhy 2908 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 17 20:07:13 2018 InstallationDate: Installed on 2018-10-10 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. Bus 001 Device 003: ID 13d3:5666 IMC Networks Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. FX503VD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX503VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX503VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: FX dmi.product.name: FX503VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950087] Re: ubuntu 21.10 live usb does not recognize Razer Blade 15 (2021) nvme drive (possible kernel bug)
I see this bug on MSI GS 66 and Ubuntu 21.10 too. The underlying issue is https://bugzilla.kernel.org/show_bug.cgi?id=214035 - removing the acpi_turn_off_unused_power_resources() call in kernel shipped with 21.10 and recompiling allowed ubuntu to see the second SSD drive. Very annoying bug - with new hardware you need 21.10 so all the new peripherals work, howerver the SSD cannot be accessed by any means. Hopefuly will be solved soon, glad to support if you need more info. ** Bug watch added: Linux Kernel Bug Tracker #214035 https://bugzilla.kernel.org/show_bug.cgi?id=214035 -- 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/1950087 Title: ubuntu 21.10 live usb does not recognize Razer Blade 15 (2021) nvme drive (possible kernel bug) Status in linux package in Ubuntu: Confirmed Bug description: I am attempting to install Ubuntu on to a new Razer Blade 15 Advanced (mid-2021) laptop. However, there seems to be some issues with kernel compatibility. When installing 20.04 LTS I have many issues with hardware not being detected (especially the intel AX210 wifi card). Running the 21.10 release from a live usb happily detected all of my hardware out of the box, with one show-stopping exception.. the internal nvme drive is not visible at all. I have tried every combination of bios options imaginable, as well as multiple Ubuntu-based distros such as Kubuntu, Pop!OS and Ubuntu Studio - all with the same results: 20.04 LTS detects the internal nvme and will install, but lacks important hardware support - while 21.10 (running in live mode) is compatible with all the essential hardware out of the box, but does not "see" the internal nvme. My short-term solution has been to install a 20.04 release using a wired internet connection, followed by upgrading to 21.04. This configuration then works, however if I upgrade again to 21.10 the internal drive again becomes undetectable, making it impossible to boot the OS. This seems to be an emerging issue.. see: https://askubuntu.com/questions/1370379/21-10-does-not-see-windows- nvme-drive/1374079?noredirect=1#comment2364713_1374079 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951997] Re: Bionic update: upstream stable patchset 2021-11-23
Note: scsi: core: Fix shost->cmd_per_lun calculation in scsi_add_host_with_dma() from v4.14.253 is being held out, pending testing w.r.t. UBUNTU: SAUCE: Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue" https://bugs.launchpad.net/bugs/1940564 ** Description changed: + SRU Justification - 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: - 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 2021-11-23 +    from git://git.kernel.org/ -upstream stable patchset 2021-11-23 -from git://git.kernel.org/ + btrfs: always wait on ordered extents at fsync time + ARM: dts: at91: sama5d2_som1_ek: disable ISC node by default + xtensa: xtfpga: use CONFIG_USE_OF instead of CONFIG_OF + xtensa: xtfpga: Try software restart before simulating CPU reset + NFSD: Keep existing listeners on portlist error + netfilter: ipvs: make global sysctl readonly in non-init netns + NIOS2: irqflags: rename a redefined register name + can: rcar_can: fix suspend/resume + can: peak_usb: pcan_usb_fd_decode_status(): fix back to ERROR_ACTIVE state notification + can: peak_pci: peak_pci_remove(): fix UAF + ocfs2: fix data corruption after conversion from inline format + ocfs2: mount fails with buffer overflow in strlen + elfcore: correct reference to CONFIG_UML + ALSA: usb-audio: Provide quirk for Sennheiser GSP670 Headset + ASoC: DAPM: Fix missing kctl change notifications + nfc: nci: fix the UAF of rf_conn_info object + isdn: cpai: check ctr->cnr to avoid array index out of bound + netfilter: Kconfig: use 'default y' instead of 'm' for bool config option + btrfs: deal with errors when checking if a dir entry exists during log replay + net: stmmac: add support for dwmac 3.40a + ARM: dts: spear3xx: Fix gmac node + isdn: mISDN: Fix sleeping function called from invalid context + platform/x86: intel_scu_ipc: Update timeout value in comment + ALSA: hda: avoid write to STATESTS if controller is in reset + tracing: Have all levels of checks prevent recursion + ARM: 9122/1: select HAVE_FUTEX_CMPXCHG + dma-debug: fix sg checks in debug_dma_map_sg() + ASoC: wm8960: Fix clock configuration on slave mode + lan78xx: select CRC32 + net: hns3: add limit ets dwrr bandwidth cannot be 0 + net: hns3: disable sriov before unload hclge layer + ALSA: hda/realtek: Add quirk for Clevo PC50HS + mm, slub: fix mismatch between reconstructed freelist depth and cnt + gcc-plugins/structleak: add makefile var for disabling structleak + UBUNTU: upstream stable to v4.14.253, v4.19.214 ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Description changed: 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 2021-11-23 + + Ported from the following upstream stable releases: + v4.14.253, v4.19.214 +    from git://git.kernel.org/ btrfs: always wait on ordered extents at fsync time ARM: dts: at91: sama5d2_som1_ek: disable ISC node by default xtensa: xtfpga: use CONFIG_USE_OF instead of CONFIG_OF xtensa: xtfpga: Try software restart before simulating CPU reset NFSD: Keep existing listeners on portlist error netfilter: ipvs: make global sysctl readonly in non-init netns NIOS2: irqflags: rename a redefined register name can: rcar_can: fix suspend/resume can: peak_usb: pcan_usb_fd_decode_status(): fix back to ERROR_ACTIVE state notification can: peak_pci: peak_pci_remove(): fix UAF ocfs2: fix data corruption after conversion from inline
[Kernel-packages] [Bug 1951997] [NEW] Bionic update: upstream stable patchset 2021-11-23
Public bug reported: 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 2021-11-23 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Bionic) 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/1951997 Title: Bionic update: upstream stable patchset 2021-11-23 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New 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 2021-11-23 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951140] Re: [Jammy] Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.2 for Ubuntu 22.04
99154581b05c -- 982fc3965d13 -- 7e98b1e548da scsi: lpfc: Don't release final kref on Fport node while ABTS outstanding 20d2279f90ce -- 88f7702984e6 -- 3a874488d2e9 -- a864ee709bc0 -- b507357f7917 -- 855f5d44fa11 scsi: lpfc: Fix NVMe I/O failover to non-optimized path cd8a36a90bab -- 235262173ec5 scsi: lpfc: Fix FCP I/O flush functionality for TMF routines 25ac2c970be3 -- d5ac69b332d8 -- 3ea998cbf9e7 -- afd63fa51149 -- 315b3fd13521 -- 0d6b26795bd2 -- Three of these patches were merged into 5.15, looks like may be they were pulled as part of an SRU. -- 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/1951140 Title: [Jammy] Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.2 for Ubuntu 22.04 Status in linux package in Ubuntu: Confirmed Bug description: this set fixes some bugs and updates the Broadcom lpfc driver to the latest bits. It has been requested for inclusion by the Broadcom FC storage team and didn't get accepted upstream in time for 5.15. Applied to 5.16/scsi-queue, thanks! [01/14] lpfc: Fix list_add corruption in lpfc_drain_txq https://git.kernel.org/mkp/scsi/c/99154581b05c [02/14] lpfc: Don't release final kref on Fport node while ABTS outstanding https://git.kernel.org/mkp/scsi/c/982fc3965d13 [03/14] lpfc: Fix premature rpi release for unsolicited TPLS and LS_RJT https://git.kernel.org/mkp/scsi/c/20d2279f90ce [04/14] lpfc: Fix hang on unload due to stuck fport node https://git.kernel.org/mkp/scsi/c/88f7702984e6 [05/14] lpfc: Fix rediscovery of tape device after issue lip https://git.kernel.org/mkp/scsi/c/3a874488d2e9 [06/14] lpfc: Don't remove ndlp on PRLI errors in P2P mode https://git.kernel.org/mkp/scsi/c/a864ee709bc0 [07/14] lpfc: Fix NVME I/O failover to non-optimized path https://git.kernel.org/mkp/scsi/c/b507357f7917 [08/14] lpfc: Fix FCP I/O flush functionality for TMF routines https://git.kernel.org/mkp/scsi/c/cd8a36a90bab [09/14] lpfc: Fix EEH support for NVME I/O https://git.kernel.org/mkp/scsi/c/25ac2c970be3 [10/14] lpfc: Adjust bytes received vales during cmf timer interval https://git.kernel.org/mkp/scsi/c/d5ac69b332d8 [11/14] lpfc: Fix I/O block after enabling managed congestion mode https://git.kernel.org/mkp/scsi/c/3ea998cbf9e7 [12/14] lpfc: Zero CGN stats only during initial driver load and stat reset https://git.kernel.org/mkp/scsi/c/afd63fa51149 [13/14] lpfc: Improve PBDE checks during SGL processing https://git.kernel.org/mkp/scsi/c/315b3fd13521 [14/14] lpfc: Update lpfc version to 14.0.0.2 https://git.kernel.org/mkp/scsi/c/0d6b26795bd2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946486] Re: Unable to reboot ARM64 node with 5.11.0-27-realtime
The 5.11 kernel will not support realtime, so updating bug to reflect Focal and 5.15. ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Hirsute) Status: Confirmed => Invalid ** Summary changed: - Unable to reboot ARM64 node with 5.11.0-27-realtime + Unable to reboot ARM64 node with 5.15 realtime -- 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/1946486 Title: Unable to reboot ARM64 node with 5.15 realtime Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: Invalid Bug description: It looks like this issue is affecting some ARM64 bare metal node: * helo-kernel 2 failed out of 2 attempts * kuzzle 11 failed out of 13 attempts (as far as I can recall 2 deployments failed early, the system was not deployed at all, so probably we can call it 9 failed) The boot test will fail, the system was unable to reboot with the 5.11.0-27-realtime kernel, here is the steps (integrated with the deployment script) 1. Deploy this node with Hirsute 2. Install the 5.11.0-27-realtime kernel and set to boot with this kernel by using the boot-kernel-simple in ckct. Reboot 3. System can boot with 5.11.0-27-realtime, reboot again to make sure it's OK It seem the system will stuck at the last reboot attempt in step 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1946486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951140] Re: [Jammy] Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.2 for Ubuntu 22.04
No need for apport collect, this is a pick request ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951140 Title: [Jammy] Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.2 for Ubuntu 22.04 Status in linux package in Ubuntu: Confirmed Bug description: this set fixes some bugs and updates the Broadcom lpfc driver to the latest bits. It has been requested for inclusion by the Broadcom FC storage team and didn't get accepted upstream in time for 5.15. Applied to 5.16/scsi-queue, thanks! [01/14] lpfc: Fix list_add corruption in lpfc_drain_txq https://git.kernel.org/mkp/scsi/c/99154581b05c [02/14] lpfc: Don't release final kref on Fport node while ABTS outstanding https://git.kernel.org/mkp/scsi/c/982fc3965d13 [03/14] lpfc: Fix premature rpi release for unsolicited TPLS and LS_RJT https://git.kernel.org/mkp/scsi/c/20d2279f90ce [04/14] lpfc: Fix hang on unload due to stuck fport node https://git.kernel.org/mkp/scsi/c/88f7702984e6 [05/14] lpfc: Fix rediscovery of tape device after issue lip https://git.kernel.org/mkp/scsi/c/3a874488d2e9 [06/14] lpfc: Don't remove ndlp on PRLI errors in P2P mode https://git.kernel.org/mkp/scsi/c/a864ee709bc0 [07/14] lpfc: Fix NVME I/O failover to non-optimized path https://git.kernel.org/mkp/scsi/c/b507357f7917 [08/14] lpfc: Fix FCP I/O flush functionality for TMF routines https://git.kernel.org/mkp/scsi/c/cd8a36a90bab [09/14] lpfc: Fix EEH support for NVME I/O https://git.kernel.org/mkp/scsi/c/25ac2c970be3 [10/14] lpfc: Adjust bytes received vales during cmf timer interval https://git.kernel.org/mkp/scsi/c/d5ac69b332d8 [11/14] lpfc: Fix I/O block after enabling managed congestion mode https://git.kernel.org/mkp/scsi/c/3ea998cbf9e7 [12/14] lpfc: Zero CGN stats only during initial driver load and stat reset https://git.kernel.org/mkp/scsi/c/afd63fa51149 [13/14] lpfc: Improve PBDE checks during SGL processing https://git.kernel.org/mkp/scsi/c/315b3fd13521 [14/14] lpfc: Update lpfc version to 14.0.0.2 https://git.kernel.org/mkp/scsi/c/0d6b26795bd2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951941] Re: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels)
What’s your result when run below cmd? And which kernel are you using? cat /sys/devices/system/cpu/cpu*/cpufreq/*driver | uniq -c intel_pstate cat /sys/devices/system/cpu/cpuidle/*driver intel_idle -- 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/1951941 Title: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels) Status in linux package in Ubuntu: Confirmed Bug description: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels). Intel wants to investigate this, and they want to see if there are missing patches that could resolve this. [steps] $ dmesg | grep "intel_pstate" [actual] > intel_pstate: CPU model not supported [expected] > intel_pstate: supported [details] lore.kernel.org reference: https://yhbt.net/lore/all/CAAYoRsUcyFsFWDE=r+amgdba6hcgxgte2jj_nhas5e4tdgi...@mail.gmail.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951941] Re: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels)
Update from email: Intel_pstate driver is part of CPU performance scaling system which is focus on performance scaling. (https://01.org/linuxgraphics/gfx-docs/drm/admin-guide/pm/cpufreq.html) And the Linux kernel supports CPU performance scaling by means of the CPUFreq (CPU Frequency scaling) subsystem that consists of three layers of code: the core, scaling governors and scaling drivers(intel_pstate). Intel_idle driver is for CPU idle time management. (https://01.org/linuxgraphics/gfx-docs/drm/admin-guide/pm/intel_idle.html?highlight=intel_idle) It is the default CPU idle time management driver for the Nehalem and later generations of Intel processors IceLake support Intel_pstate. Currently Intel_pstate is platform independent, not special code of ICX. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951941 Title: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels) Status in linux package in Ubuntu: Confirmed Bug description: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels). Intel wants to investigate this, and they want to see if there are missing patches that could resolve this. [steps] $ dmesg | grep "intel_pstate" [actual] > intel_pstate: CPU model not supported [expected] > intel_pstate: supported [details] lore.kernel.org reference: https://yhbt.net/lore/all/CAAYoRsUcyFsFWDE=r+amgdba6hcgxgte2jj_nhas5e4tdgi...@mail.gmail.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920794] Re: tc tool does not accept ipset match
This is caused be mismatch between Kernel and iproute2 version. The kernel v5 offers ipset v7 which causes iproute to not be built with ematch ipset functionality. This has been fixed in iproute upstream in - its a one line fix - Pulling this into iproute2 and rebuilding (After committing it) works. https://github.com/shemminger/iproute2/commit/650591a7a70cd79d826fcdc579a20c168c987cf2 commit 650591a7a70cd79d826fcdc579a20c168c987cf2 Author: Tony Ambardar Date: Tue Jul 7 00:58:33 2020 -0700 configure: support ipset version 7 with kernel version 5 The configure script checks for ipset v6 availability but doesn't test for v7, which is backward compatible and used on kernel v5.x systems. Update the script to test for both ipset versions. Without this change, the tc ematch function em_ipset will be disabled. Signed-off-by: Tony Ambardar Signed-off-by: Stephen Hemminger ** Changed in: iproute2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1920794 Title: tc tool does not accept ipset match Status in iproute2 package in Ubuntu: Confirmed Bug description: Steps to reproduce: tc qdisc add dev eth0 root handle 1: htb tc class add dev eth0 parent 1: classid 1:1 htb rate 1024Kbit ipset create mytest hash:net tc filter add dev eth0 protocol ip parent 1:0 prio 1 basic match 'ipset(mytest src)' classid 1:1 Last command fails with the message: Unknown ematch "ipset" Illegal "ematch" It works well with 18.04. On 20.04 machine it also works fine inside Ubuntu 18.04 LXD container. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: iproute2 5.5.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Mar 22 16:18:17 2021 SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1920794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942319] Re: When booting with UEFI, mokvar table and %:.platform keyring must be available
This bug was fixed in the package linux-kvm - 5.13.0-1006.6+22.04.1 --- linux-kvm (5.13.0-1006.6+22.04.1) jammy; urgency=medium * jammy/linux-kvm: 5.13.0-1006.6+22.04.1 -proposed tracker (LP: #1949727) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update update.conf - debian/dkms-versions -- update from kernel-versions (main/2021.11.08) [ Ubuntu: 5.13.0-1006.6 ] * impish/linux-kvm: 5.13.0-1006.6 -proposed tracker (LP: #1949728) * impish/linux: 5.13.0-22.22 -proposed tracker (LP: #1949740) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2021.11.08) * ebpf: bpf_redirect fails with ip6 gre interfaces (LP: #1947164) - net: handle ARPHRD_IP6GRE in dev_is_mac_header_xmit() * require CAP_NET_ADMIN to attach N_HCI ldisc (LP: #1949516) - Bluetooth: hci_ldisc: require CAP_NET_ADMIN to attach N_HCI ldisc * CVE-2021-3744 // CVE-2021-3764 - crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd() * ppc64 BPF JIT mod by 1 will not return 0 (LP: #1948351) - powerpc/bpf: Fix BPF_MOD when imm == 1 * Fix Screen freeze after resume from suspend with iGPU [1002:6987] (LP: #1949050) - drm/amdgpu: reenable BACO support for 699F:C7 polaris12 SKU - drm/amdgpu: add missing cleanups for Polaris12 UVD/VCE on suspend - drm/amdgpu: Fix crash on device remove/driver unload * Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed with error -1 (LP: #1945576) - igc: Remove _I_PHY_ID checking - igc: Remove phy->type checking * Fail to detect audio output from external monitor (LP: #1948767) - ALSA: hda: intel: Allow repeatedly probing on codec configuration errors * Drop "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active" (LP: #1947709) - Revert "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active" * rtw89 kernel module for Realtek 8852 wifi is missing (LP: #1945967) - rtw89: add Realtek 802.11ax driver - rtw89: Remove redundant check of ret after call to rtw89_mac_enable_bb_rf - rtw89: fix return value check in rtw89_cam_send_sec_key_cmd() - rtw89: remove unneeded semicolon - [Config] RTW89=m * Impish update: upstream stable patchset 2021-11-03 (LP: #1949636) - mm: fix uninitialized use in overcommit_policy_handler - usb: gadget: r8a66597: fix a loop in set_feature() - usb: dwc2: gadget: Fix ISOC flow for BDMA and Slave - usb: dwc2: gadget: Fix ISOC transfer complete handling for DDMA - usb: musb: tusb6010: uninitialized data in tusb_fifo_write_unaligned() - cifs: fix incorrect check for null pointer in header_assemble - xen/x86: fix PV trap handling on secondary processors - usb-storage: Add quirk for ScanLogic SL11R-IDE older than 2.6c - USB: serial: cp210x: add ID for GW Instek GDM-834x Digital Multimeter - USB: cdc-acm: fix minor-number release - Revert "USB: bcma: Add a check for devm_gpiod_get" - binder: make sure fd closes complete - staging: greybus: uart: fix tty use after free - Re-enable UAS for LaCie Rugged USB3-FW with fk quirk - usb: dwc3: core: balance phy init and exit - usb: core: hcd: Add support for deferring roothub registration - USB: serial: mos7840: remove duplicated 0xac24 device ID - USB: serial: option: add Telit LN920 compositions - USB: serial: option: remove duplicate USB device ID - USB: serial: option: add device id for Foxconn T99W265 - mcb: fix error handling in mcb_alloc_bus() - erofs: fix up erofs_lookup tracepoint - btrfs: prevent __btrfs_dump_space_info() to underflow its free space - xhci: Set HCD flag to defer primary roothub registration - serial: 8250: 8250_omap: Fix RX_LVL register offset - serial: mvebu-uart: fix driver's tx_empty callback - scsi: sd_zbc: Ensure buffer size is aligned to SECTOR_SIZE - drm/amd/pm: Update intermediate power state for SI - net: hso: fix muxed tty registration - comedi: Fix memory leak in compat_insnlist() - afs: Fix incorrect triggering of sillyrename on 3rd-party invalidation - afs: Fix updating of i_blocks on file/dir extension - platform/x86/intel: punit_ipc: Drop wrong use of ACPI_PTR() - enetc: Fix illegal access when reading affinity_hint - enetc: Fix uninitialized struct dim_sample field usage - bnxt_en: Fix TX timeout when TX ring size is set to the smallest - net: hns3: fix change RSS 'hfunc' ineffective issue - net: hns3: check queue id range before using - net/smc: add missing error check in smc_clc_prfx_set() - net/smc: fix 'workqueue leaked lock' in smc_conn_abort_work - net: dsa: don't allocate the slave_mii_bus using devres - net: dsa: realtek: register the MDIO bus under devres - kselftest/arm64: signal: Add SVE to the set of features we can check for
[Kernel-packages] [Bug 1948351] Re: ppc64 BPF JIT mod by 1 will not return 0
In the ppc64el ADT tests
(https://autopkgtest.ubuntu.com/results/autopkgtest-
hirsute/hirsute/ppc64el/l/linux/2020_190628_a83f4@/log.gz) for
hirsute:linux(5.11.0-41.45):
18:11:23 DEBUG| [stdout] # selftests: net: test_bpf.sh
18:11:23 DEBUG| [stdout] # test_bpf: ok
18:11:23 DEBUG| [stdout] ok 1 selftests: net: test_bpf.sh
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
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/1948351
Title:
ppc64 BPF JIT mod by 1 will not return 0
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
When doing MOD by 1 with a immediate/constant divisor on PPC, the JIT will
produce code that returns the dividend, just like a division, instead of 0.
Both eBPF and cBPF will fail as well when doing such operations.
[Test case]
$ cat bpf-mod1.c
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#define ARRAY_SIZE(array) (sizeof(array)/sizeof(array[0]))
static int pair[2];
static int attach()
{
int r;
struct sock_filter insn[] = {
{ BPF_LD | BPF_W | BPF_ABS, 0, 0, 0 },
{ BPF_ALU | BPF_MOD, 0, 0, 1 },
{ BPF_RET | BPF_A, 0, 0, 0 },
};
struct sock_fprog prog = {};
prog.filter = insn;
prog.len = ARRAY_SIZE(insn);
socketpair(AF_UNIX, SOCK_DGRAM, 0, pair);
setsockopt(pair[1], SOL_SOCKET, SO_ATTACH_FILTER, ,
sizeof(prog));
return 0;
}
int main(int argc, char **argv)
{
int buf[5];
int r;
r = attach();
if (r < 0) {
err(1, "function will error out already");
}
write(pair[0], "hello", 5);
r = recv(pair[1], buf, 5, MSG_DONTWAIT);
if (r != -1 || errno != EAGAIN) {
err(1, "program failed");
}
return 0;
}
$ gcc -o bpf-mod1 bpf-mod1.c
$ ./bpf-mod1
cbpf-mod1: program failed: Success
After fix:
$ ./bpf-mod1
$ echo $?
0
[Potential regression]
BPF programs might be misbehave on ppc64el.
This is a scripted bug report about ADT failures while running linux
tests for linux/5.4.0-90.101 on focal. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be
determined.
Consistently failing on Focal/linux 5.4.0-90.101
13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh
13:15:27 DEBUG| [stdout] # test_bpf: [FAIL]
13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1
Testing failed on:
ppc64el:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948351/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947161] Re: ACL updates on OCFS2 are not revalidated
Since this was part of an upstream stable set for Hirsute, I am
considering the verification as done.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
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/1947161
Title:
ACL updates on OCFS2 are not revalidated
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
When ACLs are updated on OCFS2, their caches are not revalidated, requiring
remounts to be able to see the updates.
[Fix]
Upstream commits:
504ec37dfdfbf9c65166c51f7b12126d2a9b18dc ("ocfs2: fix remounting needed after
setfacl command")
9c0f0a03e386f4e1df33db676401547e1b7800c6 ("ocfs2: drop acl cache for
directories too")
[Test case]
On a single node:
setfacl -m u:user1:rwX dir1
getfacl dir1
On multiple nodes:
Node1:
getfacl dir1
Node2:
getfacl dir1
Node1:
setfacl -m u:user1:rwX dir1
getfacl dir1
Node2:
getfacl dir1
[Potential regression]
ACL changes on OCFS2 may stop working properly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947161/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947709] Re: Drop "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active"
Since there is nothing to verify this based on an installed kernel I just double checked that the requested revert is part of the Ubuntu-5.11.0-41.45 proposed kernel. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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/1947709 Title: Drop "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active" Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Confirmed Bug description: [Impact] "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active" has been applied to fix a page leaking issue. However a slightly different fix has been applied upstream: 9a24ce5b66f9c8190d63b15f4473600db4935f1f cachefiles: Fix page leak in cachefiles_read_backing_file while vmscan is active Basically we are fixing the same issue in two different ways at the same time, but even worse our patch an introduce a potential NULL pointer dereference: we do a put_page(newpage) and set newpage = NULL in the main for() loop and then we may do additional put_page(newpage) after the main for loop if ret == -EEXIST, that would trigger the NULL pointer dereference. [Test case] No test case or reproducer is available at the moment, this issue has been found simply by reviewing the code. [Fix] Drop the SAUCE patch and rely on the upstream fix. [Regression potential] If the analysis is not correct we may re-introduce a page leak in cachefiles (NFS for example), but it seems unlikely to happen, since the upstream fix is addressing the page leaking already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947709/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951971] 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/1951971 Title: Touchpad entry missing in the command cat /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: Touchpad entry missing in cat /proc/bus/input/devices for HP laptop 15s series. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-21-generic 5.13.0-21.21 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sameer 1597 F pulseaudio /dev/snd/controlC0: sameer 1597 F pulseaudio /dev/snd/controlC2: sameer 1597 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 23 19:55:24 2021 InstallationDate: Installed on 2021-11-23 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP Laptop 15s-ey1xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=daca68ee-d11b-4861-8224-906f9e68b463 ro quiet splash acpi = offp vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2021 dmi.bios.release: 15.52 dmi.bios.vendor: AMI dmi.bios.version: F.52 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8707 dmi.board.vendor: HP dmi.board.version: 37.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.21 dmi.modalias: dmi:bvnAMI:bvrF.52:bd09/22/2021:br15.52:efr37.21:svnHP:pnHPLaptop15s-ey1xxx:pvr:rvnHP:rn8707:rvr37.21:cvnHP:ct10:cvrChassisVersion:sku38Z30PA#ACJ: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-ey1xxx dmi.product.sku: 38Z30PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951971/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951971] [NEW] Touchpad entry missing in the command cat /proc/bus/input/devices
Public bug reported: Touchpad entry missing in cat /proc/bus/input/devices for HP laptop 15s series. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-21-generic 5.13.0-21.21 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sameer 1597 F pulseaudio /dev/snd/controlC0: sameer 1597 F pulseaudio /dev/snd/controlC2: sameer 1597 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 23 19:55:24 2021 InstallationDate: Installed on 2021-11-23 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP Laptop 15s-ey1xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=daca68ee-d11b-4861-8224-906f9e68b463 ro quiet splash acpi = offp vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2021 dmi.bios.release: 15.52 dmi.bios.vendor: AMI dmi.bios.version: F.52 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8707 dmi.board.vendor: HP dmi.board.version: 37.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.21 dmi.modalias: dmi:bvnAMI:bvrF.52:bd09/22/2021:br15.52:efr37.21:svnHP:pnHPLaptop15s-ey1xxx:pvr:rvnHP:rn8707:rvr37.21:cvnHP:ct10:cvrChassisVersion:sku38Z30PA#ACJ: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-ey1xxx dmi.product.sku: 38Z30PA#ACJ dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish 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/1951971 Title: Touchpad entry missing in the command cat /proc/bus/input/devices Status in linux package in Ubuntu: New Bug description: Touchpad entry missing in cat /proc/bus/input/devices for HP laptop 15s series. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-21-generic 5.13.0-21.21 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sameer 1597 F pulseaudio /dev/snd/controlC0: sameer 1597 F pulseaudio /dev/snd/controlC2: sameer 1597 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 23 19:55:24 2021 InstallationDate: Installed on 2021-11-23 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP Laptop 15s-ey1xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=daca68ee-d11b-4861-8224-906f9e68b463 ro quiet splash acpi = offp vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2021 dmi.bios.release: 15.52 dmi.bios.vendor: AMI dmi.bios.version: F.52 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8707 dmi.board.vendor: HP dmi.board.version: 37.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.21 dmi.modalias: dmi:bvnAMI:bvrF.52:bd09/22/2021:br15.52:efr37.21:svnHP:pnHPLaptop15s-ey1xxx:pvr:rvnHP:rn8707:rvr37.21:cvnHP:ct10:cvrChassisVersion:sku38Z30PA#ACJ: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-ey1xxx dmi.product.sku: 38Z30PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951971/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948502] Re: TP-Link UB500 Bluetooth USB adapter not working properly
Solved with kernel 5.15.4-arch1-1 ** Changed in: linux (Arch Linux) Status: New => 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/1948502 Title: TP-Link UB500 Bluetooth USB adapter not working properly Status in linux package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Released Bug description: I have just bought a Tp-link bluetooth 5.0 usb adapter (UB500). According to this website https://usb-ids.gowdy.us/read/UD/2357/0604 the chip is Realtek RTL8761B. It works just fine on Windows 10, but I'm having problems on Ubuntu. I'm running Ubuntu 21.10 with the 5.14.14-051414-generic kernel The adapter seems to be correctly installed and properly working, however scanning does not pick up any bluetooth device. I've tried two headsets (that I know are properly working) and my phone, with no success. When performing a scan on my phone, the computer doesn't show up, even if I've set it to visible. (I'm sorry if the information is not complete, but ubuntu-bug is not working for me) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948502] Re: TP-Link UB500 Bluetooth USB adapter not working properly
-- 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/1948502 Title: TP-Link UB500 Bluetooth USB adapter not working properly Status in linux package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Released Bug description: I have just bought a Tp-link bluetooth 5.0 usb adapter (UB500). According to this website https://usb-ids.gowdy.us/read/UD/2357/0604 the chip is Realtek RTL8761B. It works just fine on Windows 10, but I'm having problems on Ubuntu. I'm running Ubuntu 21.10 with the 5.14.14-051414-generic kernel The adapter seems to be correctly installed and properly working, however scanning does not pick up any bluetooth device. I've tried two headsets (that I know are properly working) and my phone, with no success. When performing a scan on my phone, the computer doesn't show up, even if I've set it to visible. (I'm sorry if the information is not complete, but ubuntu-bug is not working for me) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951166] Re: nvidia_drm error at the end of kernel ring buffer (dmesg)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1951166 Title: nvidia_drm error at the end of kernel ring buffer (dmesg) Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: Recently, I have noticed an error about nvidia_drm logged several times on my kernel ring buffer output occasionally. I am using the Nvidia driver version 470.82 on Ubuntu 20.04.03 LTS with kernel version 5.11.0-40-generic. My graphics card is RTX 2070 Mobile and I am using it via external G-SYNC monitor. Some output log describing the error from dmesg command: [16166.980676] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [19268.970816] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [19268.970930] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-470 470.82.00-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 01:20:13 2021 InstallationDate: Installed on 2021-09-24 (53 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: nvidia-graphics-drivers-470 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-470/+bug/1951166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951941] 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 1951941 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 ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951941 Title: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels) Status in linux package in Ubuntu: Incomplete Bug description: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels). Intel wants to investigate this, and they want to see if there are missing patches that could resolve this. [steps] $ dmesg | grep "intel_pstate" [actual] > intel_pstate: CPU model not supported [expected] > intel_pstate: supported [details] lore.kernel.org reference: https://yhbt.net/lore/all/CAAYoRsUcyFsFWDE=r+amgdba6hcgxgte2jj_nhas5e4tdgi...@mail.gmail.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951940] 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 1951940 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 ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951940 Title: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels) Status in linux package in Ubuntu: Incomplete Bug description: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels). Intel wants to investigate this, and they want to see if there are missing patches that could resolve this. [steps] $ dmesg | grep "intel_pstate" [actual] > intel_pstate: CPU model not supported [expected] > intel_pstate: supported [details] lore.kernel.org reference: https://yhbt.net/lore/all/CAAYoRsUcyFsFWDE=r+amgdba6hcgxgte2jj_nhas5e4tdgi...@mail.gmail.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951939] 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 1951939 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 ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951939 Title: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels) Status in linux package in Ubuntu: Incomplete Bug description: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels). Intel wants to investigate this, and they want to see if there are missing patches that could resolve this. [steps] $ dmesg | grep "intel_pstate" [actual] > intel_pstate: CPU model not supported [expected] > intel_pstate: supported [details] lore.kernel.org reference: https://yhbt.net/lore/all/CAAYoRsUcyFsFWDE=r+amgdba6hcgxgte2jj_nhas5e4tdgi...@mail.gmail.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951939] [NEW] Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels)
Public bug reported: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels). Intel wants to investigate this, and they want to see if there are missing patches that could resolve this. [steps] $ dmesg | grep "intel_pstate" [actual] > intel_pstate: CPU model not supported [expected] > intel_pstate: supported [details] lore.kernel.org reference: https://yhbt.net/lore/all/CAAYoRsUcyFsFWDE=r+amgdba6hcgxgte2jj_nhas5e4tdgi...@mail.gmail.com/ ** Affects: linux (Ubuntu) Importance: High 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/1951939 Title: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels) Status in linux package in Ubuntu: New Bug description: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels). Intel wants to investigate this, and they want to see if there are missing patches that could resolve this. [steps] $ dmesg | grep "intel_pstate" [actual] > intel_pstate: CPU model not supported [expected] > intel_pstate: supported [details] lore.kernel.org reference: https://yhbt.net/lore/all/CAAYoRsUcyFsFWDE=r+amgdba6hcgxgte2jj_nhas5e4tdgi...@mail.gmail.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951940] [NEW] Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels)
Public bug reported: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels). Intel wants to investigate this, and they want to see if there are missing patches that could resolve this. [steps] $ dmesg | grep "intel_pstate" [actual] > intel_pstate: CPU model not supported [expected] > intel_pstate: supported [details] lore.kernel.org reference: https://yhbt.net/lore/all/CAAYoRsUcyFsFWDE=r+amgdba6hcgxgte2jj_nhas5e4tdgi...@mail.gmail.com/ ** Affects: linux (Ubuntu) Importance: High 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/1951940 Title: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels) Status in linux package in Ubuntu: New Bug description: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels). Intel wants to investigate this, and they want to see if there are missing patches that could resolve this. [steps] $ dmesg | grep "intel_pstate" [actual] > intel_pstate: CPU model not supported [expected] > intel_pstate: supported [details] lore.kernel.org reference: https://yhbt.net/lore/all/CAAYoRsUcyFsFWDE=r+amgdba6hcgxgte2jj_nhas5e4tdgi...@mail.gmail.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951941] [NEW] Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels)
Public bug reported: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels). Intel wants to investigate this, and they want to see if there are missing patches that could resolve this. [steps] $ dmesg | grep "intel_pstate" [actual] > intel_pstate: CPU model not supported [expected] > intel_pstate: supported [details] lore.kernel.org reference: https://yhbt.net/lore/all/CAAYoRsUcyFsFWDE=r+amgdba6hcgxgte2jj_nhas5e4tdgi...@mail.gmail.com/ ** Affects: linux (Ubuntu) Importance: High 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/1951941 Title: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels) Status in linux package in Ubuntu: New Bug description: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels). Intel wants to investigate this, and they want to see if there are missing patches that could resolve this. [steps] $ dmesg | grep "intel_pstate" [actual] > intel_pstate: CPU model not supported [expected] > intel_pstate: supported [details] lore.kernel.org reference: https://yhbt.net/lore/all/CAAYoRsUcyFsFWDE=r+amgdba6hcgxgte2jj_nhas5e4tdgi...@mail.gmail.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945938] Re: [impish] Remove the downstream xr-usb-uart driver
** Tags removed: verification-done-focal ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945938 Title: [impish] Remove the downstream xr-usb-uart driver Status in linux package in Ubuntu: In Progress Status in linux source package in Impish: Fix Released Bug description: [Impact] The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS kernel to add support for USB UART chips: Family: USB UART Part Numbers: XR21V1410, XR21V1412, XR21V1414, XR21B1411, XR21B1420, XR21B1422, XR21B1424, XR22801, XR22802, XR22804 [Fix] In 5.13.x, support for these devices was added to the kernel via. following patch series: Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/ There have been long term maintenance challenges with the downstream vendor driver over the period of time (since 4.4.y based Xenial LTS). Now that upstream driver supports most of the above part numbers, let's remove this redundant out-of-tree driver. [Test] The driver was functionally verified to work fine with XR21V1412. The support for other chips with part numbers mentioned above are also supported with the above patch series. [Where problems could occur] The downstream driver was designed to work with specific BIOS configs only defined on an IoT GW project which is locked to use only Xenial ESM and Bionic LTS kernels, there is a low chance of regression on the Impish series. [This is a tracking bug, please do not triage] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939210] Re: When using HWE, zfs-kmod and zfs user tools versions must match
Script helping to reproduce problems relating to this ticket while transferring ZFS clones with zfs send and receive. ** Attachment added: "zfsbug_with_hwe.tar.gz" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939210/+attachment/5542768/+files/zfsbug_with_hwe.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1939210 Title: When using HWE, zfs-kmod and zfs user tools versions must match Status in zfs-linux package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.2 LTS I ran into a problem recently (https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177) due to mismatched versions when HWE upgraded the kernel from 5.8 to 5.11 where the userspace tools don't match the zfs-kmod version. After the update the system ended up with zfs-0.8.3-1ubuntu12.12 and zfs- kmod-2.0.2-1ubuntu5 My understanding from asking in the OpenZFS github is that the two versions must match. This bug is to figure out what to do for those of us who use HWE and zfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939210/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939210] Re: When using HWE, zfs-kmod and zfs user tools versions must match
I can confirm problems relating to this ticket while transferring ZFS clones with zfs send and receive. This impacts on most Docker and LXD installations using ZFS. Reproduced on: Operating System: Ubuntu 20.04.3 LTS Kernel (HWE): Linux 5.11.0-40-generic ZFS Packages: 0.8.3-1ubuntu12.13 ZFS Kernel Module: 2.0.2-1ubuntu5.4 The problem can be reproduced with the attached script (zfsbug_with_hwe.tar.gz). The error is sporadic so you have to start the script several times until the following occurs: "cannot receive: local origin for clone dummypool2/dataset1/clone2@snap3 does not exist" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1939210 Title: When using HWE, zfs-kmod and zfs user tools versions must match Status in zfs-linux package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.2 LTS I ran into a problem recently (https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177) due to mismatched versions when HWE upgraded the kernel from 5.8 to 5.11 where the userspace tools don't match the zfs-kmod version. After the update the system ended up with zfs-0.8.3-1ubuntu12.12 and zfs- kmod-2.0.2-1ubuntu5 My understanding from asking in the OpenZFS github is that the two versions must match. This bug is to figure out what to do for those of us who use HWE and zfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939210/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945938] Re: [impish] Remove the downstream xr-usb-uart driver
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945938 Title: [impish] Remove the downstream xr-usb-uart driver Status in linux package in Ubuntu: In Progress Status in linux source package in Impish: Fix Released Bug description: [Impact] The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS kernel to add support for USB UART chips: Family: USB UART Part Numbers: XR21V1410, XR21V1412, XR21V1414, XR21B1411, XR21B1420, XR21B1422, XR21B1424, XR22801, XR22802, XR22804 [Fix] In 5.13.x, support for these devices was added to the kernel via. following patch series: Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/ There have been long term maintenance challenges with the downstream vendor driver over the period of time (since 4.4.y based Xenial LTS). Now that upstream driver supports most of the above part numbers, let's remove this redundant out-of-tree driver. [Test] The driver was functionally verified to work fine with XR21V1412. The support for other chips with part numbers mentioned above are also supported with the above patch series. [Where problems could occur] The downstream driver was designed to work with specific BIOS configs only defined on an IoT GW project which is locked to use only Xenial ESM and Bionic LTS kernels, there is a low chance of regression on the Impish series. [This is a tracking bug, please do not triage] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951924] [NEW] linux-azure 4.15 fails to boot on Standard_M416s_v2 in Azure
Public bug reported: To reproduce: * start a bionic VM in azure: az vm create --name bionic --resource-group test-bionic --image "Canonical:UbuntuServer:18_04-lts-gen2:latest" --size Standard_M416s_v2 --admin-username ubuntu --ssh-key-value SSH_KEY_PATH * "downgrade" the kernel to 4.15 and delete the 5.4 kernel * reboot (the machine should fail to boot) The serial console logs can be found on the azure portal (boot diagnostic needs to be enabled for the VM first). Logs: https://pastebin.ubuntu.com/p/mhKMdMJCtX/ ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- 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/1951924 Title: linux-azure 4.15 fails to boot on Standard_M416s_v2 in Azure Status in linux-azure package in Ubuntu: New Bug description: To reproduce: * start a bionic VM in azure: az vm create --name bionic --resource-group test-bionic --image "Canonical:UbuntuServer:18_04-lts-gen2:latest" --size Standard_M416s_v2 --admin-username ubuntu --ssh-key-value SSH_KEY_PATH * "downgrade" the kernel to 4.15 and delete the 5.4 kernel * reboot (the machine should fail to boot) The serial console logs can be found on the azure portal (boot diagnostic needs to be enabled for the VM first). Logs: https://pastebin.ubuntu.com/p/mhKMdMJCtX/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1951924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950721] Re: Re-enable CONFIG_PINCTRL_ELKHARTLAKE
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950721 Title: Re-enable CONFIG_PINCTRL_ELKHARTLAKE Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Fix Committed Bug description: We have test BIOS now for supporting pinctrl. From what we learnt, ODMs also got the BIOS fix, it's now time to re-enable this kernel config. [Impact] Without this fix, pinctrl functionality will be missing. [Test plan] 1. Make sure the computer has a BIOS that supports pinctrl for EHL 2. Before installing the new kernel, GPIO should not work 3. Install the new kernel, and confirm GPIO works [Where problems could occur] If the computer does not have a BIOS that support pinctrl, you will get an error like "kernel NULL pointer dereference in intel_pinctrl_get_soc_data" during system boot. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951767] Re: [SRU][I/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks
** Changed in: linux (Ubuntu Impish) Status: New => Triaged ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1951767 Title: [SRU][I/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: Triaged Status in linux source package in Jammy: Incomplete Bug description: [Impact] MAC pass through is not working on new TBT and USB-C docks. [Fix] Enable MAC pass through based on Lenovo USB hub. [Test] Tested on Lenovo TBT4 and TBT3 dock, MAC pass through works well. [Where problems could occur] The Realtek USB ethernet in Lenovo USB hub will mess the MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837348] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels (Error: Unknown device type)
** Also affects: linux-kvm (Ubuntu Focal) Importance: Undecided Status: New ** Tags added: sru-20211108 ** Summary changed: - test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels (Error: Unknown device type) + test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels - Error: Unknown device type (missing config) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1837348 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels - Error: Unknown device type (missing config) Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Disco: Won't Fix Status in linux-kvm source package in Eoan: Won't Fix Status in linux-kvm source package in Focal: New Bug description: Issue found on a AMD64 KVM node with Disco KVM kernel. selftests: net: test_vxlan_under_vrf.sh Error: Unknown device type. not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=2 Note, the following error has been fix in bug 1908342 Cannot remove namespace file "/var/run/netns/hv-2": No such file or directory Cannot remove namespace file "/var/run/netns/vm-1": No such file or directory Cannot remove namespace file "/var/run/netns/vm-2": No such file or directory ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1010-kvm 5.0.0-1010.11 ProcVersionSignature: User Name 5.0.0-1010.11-kvm 5.0.8 Uname: Linux 5.0.0-1010-kvm x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Jul 22 05:04:42 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837348/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950042] Re: Let NVMe with HMB use native power control again
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950042 Title: Let NVMe with HMB use native power control again Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: Impact] NVMe with HMB may still do DMA during suspend, so there was a commit that put the NVMe to PCI D3 during suspend to prevent DMA activities. However, this makes them consumes much more power because modern NVMe requires to stay at PCI D0 to make its natve power control work. [Fix] Instead of put the NVMe to PCI D3 and reset it afterward, simply disable HMB and re-enable HMB, for suspend and resume respectively. [Test] On affected system, Intel SoC can only reach PC3 during suspend. With the SRU applied, the Intel SoC can reach PC10 and SLP_S0 and use significant less power. [Where problems could occur] The original approach, i.e. disable NVMe and put it to PCI D3 to prevent DMA activies, was just a precaution. There wasn't any case that indicates it happens in practice. This is a different approach to the same problem, which is a theoretical problem. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949516] Re: require CAP_NET_ADMIN to attach N_HCI ldisc
** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1949516 Title: require CAP_NET_ADMIN to attach N_HCI ldisc Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.10 source package in Jammy: Invalid Bug description: [Impact] Any unprivileged user can attach N_HCI ldisc and send packets coming from a virtual controller by using PTYs. This exposes attack surface on systems where bluetooth is not needed or even allow local attacks that would otherwise require physical proximity. [Test case] Try attaching N_HCI ldisc to a tty. ldattach HCI /dev/tty [Potential regression] Users who rely on programs using N_HCI line discipline in order to emulate or proxy a bluetooth controller will require privilege they may not have. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950239 Title: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] setgid files may be created on setgid directories owned by the directory group by users not belonging to that group. That is restricted to XFS. [Fix/Backport] The fix for 5.11 and 5.10 kernels is one simple commit with a minor backport conflict fixup on 5.10. 5.4, on the other hand, required other 3 pre-requisites, which could be picked cleanly. On 4.15, however, they needed a lot of mangling and fixes. [Test case] creat09 LTP test case. [Potential regression] The creation of files on XFS may have the wrong attributes. Also, on 5.4 and 4.15, the potential regression is larger, also affecting quota, statistics and other interfaces where uid, gid and projid are exposed. = These two tests, creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve are actually the same test. Issue found on F-oem-5.10.0-1051.53 With LTP upstream head SHA1 2ac54d426 This is not a regression, it's because of a recent update that enables this test on different filesystems: https://github.com/linux-test-project/ltp/commit/433b6cf7ade3d5e3bd4b85ac89b164c53312e65a Test failed on XFS with: tst_test.c:1431: TINFO: Testing on xfs tst_test.c:932: TINFO: Formatting /dev/loop3 with xfs opts='' extra opts='' tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/creat.tmp: Setgid bit is set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/open.tmp: Setgid bit is set Test log: Checking for required user/group ids 'nobody' user id and group found. 'bin' user id and group found. 'daemon' user id and group found. Users group found. Sys group found. Required users/groups exist. no big block device was specified on commandline. Tests which require a big block device are disabled. You can specify it with option -z INFO: Test start time: Mon Nov 8 10:00:06 UTC 2021 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 61758 -n 61758 -f /tmp/ltp-shLYORuoRT/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_device.c:88: TINFO: Found free device 3 '/dev/loop3' tst_supported_fs_types.c:88: TINFO: Kernel supports ext2 tst_supported_fs_types.c:50: TINFO: mkfs.ext2 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext3 tst_supported_fs_types.c:50: TINFO: mkfs.ext3 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext4 tst_supported_fs_types.c:50: TINFO: mkfs.ext4 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports xfs tst_supported_fs_types.c:50: TINFO: mkfs.xfs does exist tst_supported_fs_types.c:88: TINFO: Kernel supports btrfs tst_supported_fs_types.c:50: TINFO: mkfs.btrfs does exist tst_supported_fs_types.c:146: TINFO: Skipping vfat as requested by the test tst_supported_fs_types.c:146: TINFO: Skipping exfat as requested by the test tst_supported_fs_types.c:88: TINFO: Kernel supports tmpfs tst_supported_fs_types.c:37: TINFO: mkfs is not needed for tmpfs tst_test.c:1431: TINFO: Testing on ext2 tst_test.c:932: TINFO: Formatting /dev/loop3 with ext2 opts='' extra opts='' mke2fs 1.45.5 (07-Jan-2020) tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID
