[Kernel-packages] [Bug 1982104] Re: intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes
** 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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1982104 Title: intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] Ubuntu 22.04 installation crashes on our Intel Sapphire Rapids proto server. Attaching the console logs. Currently, it looks like disabling VT-D option in BIOS settings helps mitigate the issue. Console logs indicate something is wrong in iommu/dmar subsystem. [Fix] The IOMMU driver shares the pasid table for PCI alias devices. When the RID2PASID entry of the shared pasid table has been filled by the first device, the subsequent device will encounter the "DMAR: Setup RID2PASID failed" failure as the pasid entry has already been marked as present. As the result, the IOMMU probing process will be aborted. On the contrary, when any alias device is hot-removed from the system, for example, by writing to /sys/bus/pci/devices/.../remove, the shared RID2PASID will be cleared without any notifications to other devices. As the result, any DMAs from those rest devices are blocked. Sharing pasid table among PCI alias devices could save two memory pages for devices underneath the PCIe-to-PCI bridges. Anyway, considering that those devices are rare on modern platforms that support VT-d in scalable mode and the saved memory is negligible, it's reasonable to remove this part of immature code to make the driver feasible and stable. [Test Case] 1. use the target machine(Intel Sapphire Rapids) and install the kernel with the fix. 2. boot the target machine 3. check dmesg if the error message exists [ 8.120527] pci :03:01.0: DMAR: Setup RID2PASID failed [Where problems could occur] After enable intel_iommu, the errors may be occurred. We need to figure out one by one once the related errors are triggered in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1982104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983071] Re: [L860-R+] Need to manually reconnect to cellular after waking from cold boot/reboot/airplane mode/wwan radio disabled/reboot/s0ix state
** Information type changed from Private to Public ** Information type changed from Public to Private Security -- 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/1983071 Title: [L860-R+] Need to manually reconnect to cellular after waking from cold boot/reboot/airplane mode/wwan radio disabled/reboot/s0ix state Status in Canonical HWE Sutton: New Status in linux package in Ubuntu: New Bug description: [Description] After resuming from states such as airplane mode, reboot, cold boot, s0ix and wwan radio disabled, user needs to manually connect using the "nmcli conn up " command or turn off Mobile broadband and connect to the APN profile to be able to connect to cellular. Need more information why stalling is happening with reconnection using this kernel. [Expected Result] After resuming from the mentioned states, user should be able to establish Mobile broadband connection right after selecting the APN profile right away. [Actual Result] After resuming from the mentioned states, user is unable to establish Mobile broadband connection right after selecting the APN profile right away. [Workaround] User needs to manually reconnect to cellular by either of the following: 1) running nmcli conn up '' 2) turning off Mobile broadband and then reconnecting to the APN profile via Mobile broadband GUI In the attached zip file, modem logs were collected following the results: [Airplane mode] 1 minute - PASS 5 minutes - FAIL 15 minutes - FAIL [WWAN radio] 1 minute - PASS 5 minutes - PASS 15 minutes - FAIL [S0ix] 1 minute - PASS 5 minutes - FAIL ([manufacturer unknown] model unknown/mobile broadband unavailable error appears) 15 minutes - N/A According to Intel, "In logs it is observed that there is ~1 minute gap between modem being enabled back after airplane mode and pdp getting established. This stall is not alone in MM. Syslog indicates that there is stall in entire system level logging for almost a min. After this stall, MM is able to establish successful PDP connection within the same second." Jul 13 16:05:56 ubuntu-ThinkPad-T14-Gen-3 systemd[1]: systemd-rfkill.service: Succeeded. Jul 13 16:06:51 ubuntu-ThinkPad-T14-Gen-3 ModemManager[811]: [modem1] 3GPP registration state changed (home -> idle) Jul 13 16:06:51 ubuntu-ThinkPad-T14-Gen-3 ModemManager[811]: [modem1] state changed (connecting -> connected) Jul 13 16:06:51 ubuntu-ThinkPad-T14-Gen-3 ModemManager[811]: [modem1] simple connect state (8/8): all done "In the provided logs I can see that there is no issue or delay observed in establishment of PDP connection. It is taking approximately 4-6 seconds for PDP establishment. Please find file level analysis as below." radio.txt- - "Only one instance of airplane mode toggling was observed. PDP re-established within ~4 seconds of switching off airplane mode and within ~2 seconds of registration." ModemManager[4773]: [1658906907.307452] [modem0] updating power state: 'on'... ModemManager[4773]: [1658906909.236937] [modem0] state changed (enabled -> registered) ModemManager[4773]: [1658906911.841261] [modem0] simple connect started... ModemManager[4773]: [1658906911.854284] [modem0] state changed (connecting -> connected) s0ix.txt- -- "No instance of airplane mode toggling. During boot up PDP has been established within the same second of PDP connection request." ModemManager[5412]: [1658908777.915076] [modem0] updating power state: 'on'... ModemManager[5412]: [1658908779.774030] [modem0] state changed (enabled -> registered) ModemManager[5412]: [1658908789.113728] [modem0] simple connect started... ModemManager[5412]: [1658908789.129582] [modem0] state changed (connecting -> connected) "There seems to be an issue with data connection observed later though. MM is triggering PDP connection request and modem is responding with error. Need to be analysed from modem end what is the issue." ModemManager[5412]: [1658908877.516999] [modem1/bearer3] connection attempt #1 failed: Unknown error ModemManager[5412]: [1658908877.613880] [modem1/bearer3] connection attempt #2 failed: Unknown error ModemManager[5412]: [1658908877.717007] [modem1/bearer3] connection attempt #3 failed: Unknown error ModemManager[5412]: [1658908877.821648] [modem1/bearer3] connection attempt #4 failed: Unknown error ModemManager[5412]: [1658908877.933048] [modem1/bearer4] connection attempt #1 failed: Unknown error ModemManager[5412]: [1658908877.989101] [modem1/bearer5] connection attempt #1 failed: Unknown error ModemManager[5412]: [1658908878.073209] [modem1/bearer6] connection attempt #1 failed: Unknown error ModemManager[5412]: [1658908878.173125] [modem1/bearer4] connection
[Kernel-packages] [Bug 1983071] [NEW] [L860-R+] Need to manually reconnect to cellular after waking from cold boot/reboot/airplane mode/wwan radio disabled/reboot/s0ix state
Private bug reported: [Description] After resuming from states such as airplane mode, reboot, cold boot, s0ix and wwan radio disabled, user needs to manually connect using the "nmcli conn up " command or turn off Mobile broadband and connect to the APN profile to be able to connect to cellular. Need more information why stalling is happening with reconnection using this kernel. [Expected Result] After resuming from the mentioned states, user should be able to establish Mobile broadband connection right after selecting the APN profile right away. [Actual Result] After resuming from the mentioned states, user is unable to establish Mobile broadband connection right after selecting the APN profile right away. [Workaround] User needs to manually reconnect to cellular by either of the following: 1) running nmcli conn up '' 2) turning off Mobile broadband and then reconnecting to the APN profile via Mobile broadband GUI In the attached zip file, modem logs were collected following the results: [Airplane mode] 1 minute - PASS 5 minutes - FAIL 15 minutes - FAIL [WWAN radio] 1 minute - PASS 5 minutes - PASS 15 minutes - FAIL [S0ix] 1 minute - PASS 5 minutes - FAIL ([manufacturer unknown] model unknown/mobile broadband unavailable error appears) 15 minutes - N/A According to Intel, "In logs it is observed that there is ~1 minute gap between modem being enabled back after airplane mode and pdp getting established. This stall is not alone in MM. Syslog indicates that there is stall in entire system level logging for almost a min. After this stall, MM is able to establish successful PDP connection within the same second." Jul 13 16:05:56 ubuntu-ThinkPad-T14-Gen-3 systemd[1]: systemd-rfkill.service: Succeeded. Jul 13 16:06:51 ubuntu-ThinkPad-T14-Gen-3 ModemManager[811]: [modem1] 3GPP registration state changed (home -> idle) Jul 13 16:06:51 ubuntu-ThinkPad-T14-Gen-3 ModemManager[811]: [modem1] state changed (connecting -> connected) Jul 13 16:06:51 ubuntu-ThinkPad-T14-Gen-3 ModemManager[811]: [modem1] simple connect state (8/8): all done "In the provided logs I can see that there is no issue or delay observed in establishment of PDP connection. It is taking approximately 4-6 seconds for PDP establishment. Please find file level analysis as below." radio.txt- - "Only one instance of airplane mode toggling was observed. PDP re-established within ~4 seconds of switching off airplane mode and within ~2 seconds of registration." ModemManager[4773]: [1658906907.307452] [modem0] updating power state: 'on'... ModemManager[4773]: [1658906909.236937] [modem0] state changed (enabled -> registered) ModemManager[4773]: [1658906911.841261] [modem0] simple connect started... ModemManager[4773]: [1658906911.854284] [modem0] state changed (connecting -> connected) s0ix.txt- -- "No instance of airplane mode toggling. During boot up PDP has been established within the same second of PDP connection request." ModemManager[5412]: [1658908777.915076] [modem0] updating power state: 'on'... ModemManager[5412]: [1658908779.774030] [modem0] state changed (enabled -> registered) ModemManager[5412]: [1658908789.113728] [modem0] simple connect started... ModemManager[5412]: [1658908789.129582] [modem0] state changed (connecting -> connected) "There seems to be an issue with data connection observed later though. MM is triggering PDP connection request and modem is responding with error. Need to be analysed from modem end what is the issue." ModemManager[5412]: [1658908877.516999] [modem1/bearer3] connection attempt #1 failed: Unknown error ModemManager[5412]: [1658908877.613880] [modem1/bearer3] connection attempt #2 failed: Unknown error ModemManager[5412]: [1658908877.717007] [modem1/bearer3] connection attempt #3 failed: Unknown error ModemManager[5412]: [1658908877.821648] [modem1/bearer3] connection attempt #4 failed: Unknown error ModemManager[5412]: [1658908877.933048] [modem1/bearer4] connection attempt #1 failed: Unknown error ModemManager[5412]: [1658908877.989101] [modem1/bearer5] connection attempt #1 failed: Unknown error ModemManager[5412]: [1658908878.073209] [modem1/bearer6] connection attempt #1 failed: Unknown error ModemManager[5412]: [1658908878.173125] [modem1/bearer4] connection attempt #2 failed: Unknown error ModemManager[5412]: [1658908878.253013] [modem1/bearer5] connection attempt #2 failed: Unknown error ModemManager[5412]: [1658908878.333056] [modem1/bearer6] connection attempt #2 failed: Unknown error ModemManager[5412]: [1658908878.440927] [modem1/bearer4] connection attempt #3 failed: Unknown error ModemManager[5412]: [1658908878.521164] [modem1/bearer5] connection attempt #3 failed: Unknown error ModemManager[5412]: [1658908878.601119] [modem1/bearer6] connection attempt #3 failed: Unknown error ModemManager[5412]: [1658908878.684948] [modem1/bearer4] connection attempt #4 failed: Unknown error ModemManager[5412]:
[Kernel-packages] [Bug 1979267] Re: Fix WD22TB4 suspend and resume, two external monitor can not output
** Merge proposal linked: https://code.launchpad.net/~vicamo/hwe-next/+git/intermediate-kernel/+merge/427596 -- 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/1979267 Title: Fix WD22TB4 suspend and resume, two external monitor can not output Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Incomplete Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] Resume SUT from suspend mode, found external monitors can not output, but display setting can recognize external monitors. [Fix] The WD22TB4 Thunderbolt dock at least will revert its DP_MAX_LINK_RATE from HBR3 to HBR2 after system suspend/resume if the DP_DP13_DPCD_REV registers are not read subsequently also as required. Fix this by reading DP_DP13_DPCD_REV registers as well, matching what is done during connector detection. While at it also fix up the same call in drm_dp_mst_dump_topology(). [Test Case] 1. Connect two 4K external monitor to WD22TB4. 2. Put SUT into suspend mode and wait 30sec 3. Resume SUT from suspend mode, found external monitors can not output. [Where problems could occur] low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1979267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983070] Re: Ubuntu 22.04 Lock Screen is changing the brightness level automatically - Asus Vivobook
** Tags removed: regression-update -- 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/1983070 Title: Ubuntu 22.04 Lock Screen is changing the brightness level automatically - Asus Vivobook Status in linux package in Ubuntu: Confirmed Bug description: I just installed Ubuntu 22.04 on my new laptop Asus Vivobook Pro 15 OLED. I noticed a weird behavior when the screens goes locked, the brightness level is automatically increased when the screen turns on back again. I also noticed that the file /sys/class/backlight/amdgpu_bl0/actual_brightness is automatically changed to a higher level that the one that I had before the screen went locked. The problem WAS NOT PRESENT in kernel version 15.5.0-25-generic. After that version the problem comes as described. Thank you. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-43-generic 5.15.0-43.46 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexrm 1954 F pulseaudio /dev/snd/controlC0: alexrm 1954 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 28 22:39:38 2022 InstallationDate: Installed on 2022-07-29 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop M3500QA_M3500QA ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=UUID=6094f527-24fc-43a9-b689-6a3922fec129 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: M3500QA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M3500QA 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:bvnAmericanMegatrendsInternational,LLC.:bvrM3500QA.308:bd04/27/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivobook_ASUSLaptopM3500QA_M3500QA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM3500QA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: Vivobook dmi.product.name: Vivobook_ASUSLaptop M3500QA_M3500QA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1979173] Re: Enable WiFi hotspot feature for MediaTek MT7921
** Merge proposal linked:
https://code.launchpad.net/~vicamo/hwe-next/+git/intermediate-kernel/+merge/427594
--
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/1979173
Title:
Enable WiFi hotspot feature for MediaTek MT7921
Status in HWE Next:
New
Status in OEM Priority Project:
In Progress
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux-oem-5.17 source package in Focal:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-5.14 source package in Jammy:
Invalid
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Bug description:
[Impact]
The wifi hotspot on systems with Mediatek MT7921 wifi chip doesn't work.
[Fix]
MediaTek already have the commit 116c69603b01 ("mt76: mt7921: Add AP mode
support") upstream. But it's based on kernel 5.18. Mediatek also suggest to add
patches https://patchwork.kernel.org/project/linux-mediatek/list/?series=648452
which are already accepted by upstream to fix bug in AP mode. Enable AP mode on
specific kernel versions.
[Test]
Verified on the machines with MediaTek MT7921 chip.
[Where problems could occur]
The patches are to enable AP mode and and fix related issues on new VIF with
AP capability, should have minimal impact to the origin behaviors.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1979173/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983070] 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/1983070 Title: Ubuntu 22.04 Lock Screen is changing the brightness level automatically - Asus Vivobook Status in linux package in Ubuntu: Confirmed Bug description: I just installed Ubuntu 22.04 on my new laptop Asus Vivobook Pro 15 OLED. I noticed a weird behavior when the screens goes locked, the brightness level is automatically increased when the screen turns on back again. I also noticed that the file /sys/class/backlight/amdgpu_bl0/actual_brightness is automatically changed to a higher level that the one that I had before the screen went locked. The problem WAS NOT PRESENT in kernel version 15.5.0-25-generic. After that version the problem comes as described. Thank you. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-43-generic 5.15.0-43.46 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexrm 1954 F pulseaudio /dev/snd/controlC0: alexrm 1954 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 28 22:39:38 2022 InstallationDate: Installed on 2022-07-29 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop M3500QA_M3500QA ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=UUID=6094f527-24fc-43a9-b689-6a3922fec129 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: M3500QA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M3500QA 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:bvnAmericanMegatrendsInternational,LLC.:bvrM3500QA.308:bd04/27/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivobook_ASUSLaptopM3500QA_M3500QA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM3500QA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: Vivobook dmi.product.name: Vivobook_ASUSLaptop M3500QA_M3500QA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] Re: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
** Merge proposal linked: https://code.launchpad.net/~vicamo/hwe-next/+git/intermediate-kernel/+merge/427593 -- 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/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: Fix Released Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Hirsute: Won't Fix 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-oem-5.17 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [SRU Justification] [Impact] VMD PCI-E bridges on ADL-M/P/S use new device IDs and therefore not covered by previous LTR reset fix in bug 1896598. [Fix] Additional entires to vmd_bridge_tbl in drivers/pci/quirks.c is requierd: * ADL-M: [8086:464d] * ADL-P: [8086:51b0] * ADL-S: [8086:7ab4] [Test Case] $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' ... 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ [Where problems could occur] This will reset zeroed PCI_LTR_MAX_SNOOP_LAT and PCI_LTR_MAX_NOSNOOP_LAT values to a fixed 3145728ns that is used on Windows. Devices might want to set itself to a smaller value, but while this is not yet correctly supported by VMD controller driver, so the device power consumption might be little worse than ideal. [Other Info] VMD ASPM was first supported for Tiger Lake cpus, so all kernel versions newer than 5.6 should have already the supporting function. This patch targets Alder Lake cpus that are supported since 5.10-oem and on. == original bug report == * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384, https://bugs.launchpad.net/bugs/1896598. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0
[Kernel-packages] [Bug 1983070] [NEW] Ubuntu 22.04 Lock Screen is changing the brightness level automatically - Asus Vivobook
Public bug reported: I just installed Ubuntu 22.04 on my new laptop Asus Vivobook Pro 15 OLED. I noticed a weird behavior when the screens goes locked, the brightness level is automatically increased when the screen turns on back again. I also noticed that the file /sys/class/backlight/amdgpu_bl0/actual_brightness is automatically changed to a higher level that the one that I had before the screen went locked. The problem WAS NOT PRESENT in kernel version 15.5.0-25-generic. After that version the problem comes as described. Thank you. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-43-generic 5.15.0-43.46 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexrm 1954 F pulseaudio /dev/snd/controlC0: alexrm 1954 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 28 22:39:38 2022 InstallationDate: Installed on 2022-07-29 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop M3500QA_M3500QA ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=UUID=6094f527-24fc-43a9-b689-6a3922fec129 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: M3500QA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M3500QA 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:bvnAmericanMegatrendsInternational,LLC.:bvrM3500QA.308:bd04/27/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivobook_ASUSLaptopM3500QA_M3500QA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM3500QA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: Vivobook dmi.product.name: Vivobook_ASUSLaptop M3500QA_M3500QA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy regression-release regression-update 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/1983070 Title: Ubuntu 22.04 Lock Screen is changing the brightness level automatically - Asus Vivobook Status in linux package in Ubuntu: New Bug description: I just installed Ubuntu 22.04 on my new laptop Asus Vivobook Pro 15 OLED. I noticed a weird behavior when the screens goes locked, the brightness level is automatically increased when the screen turns on back again. I also noticed that the file /sys/class/backlight/amdgpu_bl0/actual_brightness is automatically changed to a higher level that the one that I had before the screen went locked. The problem WAS NOT PRESENT in kernel version 15.5.0-25-generic. After that version the problem comes as described. Thank you. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-43-generic 5.15.0-43.46 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexrm 1954 F pulseaudio /dev/snd/controlC0: alexrm 1954 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 28 22:39:38 2022 InstallationDate: Installed on 2022-07-29 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop M3500QA_M3500QA ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=UUID=6094f527-24fc-43a9-b689-6a3922fec129 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: M3500QA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M3500QA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset
[Kernel-packages] [Bug 1956509] Re: Support AMD P-State cpufreq control mechanism
** Merge proposal linked:
https://code.launchpad.net/~vicamo/hwe-next/+git/intermediate-kernel/+merge/427591
--
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/1956509
Title:
Support AMD P-State cpufreq control mechanism
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux-oem-5.17 source package in Focal:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-oem-5.14 source package in Jammy:
Invalid
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Bug description:
[SRU Justification]
[Impact]
AMD P-State CPU performance scaling driver not yet supported on AMD Zen
based CPU series.
[Fix]
Mainline commits starting at commit d341db8f48ea ("x86/cpufeatures: Add
AMD Collaborative Processor Performance Control feature flag") from v5.17.
Even this committed, the defconfig will build it as module, and that
prevents AMD P-State driver from actually taking effect. Therefore an
additional fix to the kernel configs is necessary.
[Test Case]
$ sudo cpupower frequency-info
analyzing CPU 0:
driver: amd-pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 131 us
hardware limits: 400 MHz - 3.10 GHz
available cpufreq governors: conservative ondemand userspace powersave
performance schedutil
current policy: frequency should be within 1.60 GHz and 3.10 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 1.59 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
Boost States: 0
Total States: 3
Pstate-P0: 3100MHz
Pstate-P1: 1800MHz
Pstate-P2: 1600MHz
[Where problems could occur]
The CPPC feature is implemented in two ways depending on underlying HW
details for the APU/CPU:
* Dedicated MSR
* Shared memory
The metrics used to measure power/performance efficiency don't show any
improvement on the designs that use shared memory. They do show
improvements in the MSR designs.
So the code will only enable it by default on the MSR implementation.
[Other Info]
Althought the v5.17 kernel and newer should have already this committed,
an additional fix to the kernel configs is necessary, and
unstable/oem-5.17 are also nominated (in a separate thread for they don't
need other parts but the config).
== original bug report ==
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-
pm.git/commit/?h=linux-
next=40181d67f1e9f1ac87af9c0c194e40ab2a081974
$ sudo cpupower frequency-info
analyzing CPU 0:
driver: amd-pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 131 us
hardware limits: 400 MHz - 3.10 GHz
available cpufreq governors: conservative ondemand userspace powersave
performance schedutil
current policy: frequency should be within 1.60 GHz and 3.10 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 1.59 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
Boost States: 0
Total States: 3
Pstate-P0: 3100MHz
Pstate-P1: 1800MHz
Pstate-P2: 1600MHz
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1956509/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
** Merge proposal linked: https://code.launchpad.net/~vicamo/hwe-next/+git/intermediate-kernel/+merge/427590 -- 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/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux-wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
@Scott, it seems that if you only have one additional SATA card in your system then the error is annoying but benign. But, if you have more than one SATA expansion card then you would have a real problem. -- 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/1970074 Title: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 Status in linux package in Ubuntu: Confirmed Bug description: Something wrong with ata driver in dmesg found: [1.980693] kernel: [1.980699] kernel: fbcon: Taking over console [1.980703] kernel: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 [1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]' [1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted 5.15.0-25-generic #25-Ubuntu [1.980716] kernel: Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [1.980718] kernel: Call Trace: [1.980721] kernel: [1.980723] kernel: show_stack+0x52/0x58 [1.980729] kernel: dump_stack_lvl+0x4a/0x5f [1.980734] kernel: dump_stack+0x10/0x12 [1.980736] kernel: ubsan_epilogue+0x9/0x45 [1.980739] kernel: __ubsan_handle_out_of_bounds.cold+0x44/0x49 [1.980742] kernel: ahci_qc_issue+0x166/0x170 [libahci] [1.980748] kernel: ata_qc_issue+0x135/0x240 [1.980752] kernel: ata_exec_internal_sg+0x2c4/0x580 [1.980754] kernel: ? vprintk_default+0x1d/0x20 [1.980759] kernel: ata_exec_internal+0x67/0xa0 [1.980762] kernel: sata_pmp_read+0x8d/0xc0 [1.980765] kernel: sata_pmp_read_gscr+0x3c/0x90 [1.980768] kernel: sata_pmp_attach+0x8b/0x310 [1.980771] kernel: ata_eh_revalidate_and_attach+0x28c/0x4b0 [1.980775] kernel: ata_eh_recover+0x6b6/0xb30 [1.980778] kernel: ? ahci_do_hardreset+0x180/0x180 [libahci] [1.980783] kernel: ? ahci_stop_engine+0xb0/0xb0 [libahci] [1.980787] kernel: ? ahci_do_softreset+0x290/0x290 [libahci] [1.980792] kernel: ? trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0 [1.980795] kernel: sata_pmp_eh_recover.isra.0+0x214/0x560 [1.980799] kernel: sata_pmp_error_handler+0x23/0x40 [1.980802] kernel: ahci_error_handler+0x43/0x80 [libahci] [1.980806] kernel: ata_scsi_port_error_handler+0x2b1/0x600 [1.980810] kernel: ata_scsi_error+0x9c/0xd0 [1.980813] kernel: scsi_error_handler+0xa1/0x180 [1.980817] kernel: ? scsi_unjam_host+0x1c0/0x1c0 [1.980820] kernel: kthread+0x12a/0x150 [1.980823] kernel: ? set_kthread_struct+0x50/0x50 [1.980826] kernel: ret_from_fork+0x22/0x30 [1.980831] kernel: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene16798 F pulseaudio /dev/snd/pcmC0D0p: eugene16798 F...m pulseaudio /dev/snd/controlC1: eugene16798 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 24 05:13:34 2022 HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61 InstallationDate: Installed on 2019-04-13 (1106 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp2s0no wireless extensions. virbr0no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (1 days ago) dmi.bios.date: 06/11/2010 dmi.bios.release: 11.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias:
[Kernel-packages] [Bug 1978347] Re: horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27
*** This bug is a duplicate of bug 1969482 *** https://bugs.launchpad.net/bugs/1969482 Resolved with the release of 5.15.0-43-generic that contains (confirmed on the same laptop). Please close. -- 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/1978347 Title: horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27 Status in linux package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: IO on encrypted zfs root has fallen off a cliff in kernel versions after 5.15.0-27 (the degradation is observed since version 5.15.0-30, also seen on -33 and -37, -25 and -27 work like a charm). Heavy usage almost hangs a new laptop (building large singularity images or synthetic testing with dd). I have confirmed that things are working as expected on a default + upgraded Ubuntu 22.04 desktop LVM+LUKS installation using another NVMe SSD on the same laptop. There seems to be a regression when using the native zfs encryption (did aes-ni acceleration get turned off?) How to reproduce: - install ubuntu 22.04 desktop from iso, don't install web updates, check use zfs and encryption - sudo apt update && apt install dstat htop - create a dataset with compression disabled so that dd actually writes things to disk * sudo zfs create rpool/dummy * sudo zfs set compress=off rpool/dummy * sudo chown -R myusername. /dummy - start dstat and htop in the background (show kernel threads in the htop config) - dd if=/dev/zero of=/dummy/bigfile bs=1M count=16384 - sudo apt upgradeand reboot on the latest kernel, repeat Expected: some cpu load, dstat reports write speeds about as much as the SSD can sustain (2.9-3GiB/s with a 2TiB Samsung 970 EVO Plus for a 16GiB write test, 1.4GiB/s for a few seconds then 800MiB/s sustained for whatever WD 512GiB model I had laying around). Observed on versions -30 and later: 700% or more system cpu load, mostly in z_wr_iss threads, writes top at around 150-180MiB/s, the system becomes somewhat unresponsive. Reads are also not good but I have not benchmarked. Booting the system and launching apps seems about normal due to the low IO load. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-37-generic 5.15.0-37.39 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laperlej 4100 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 15:52:12 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-05-10 (31 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP EliteBook 850 G8 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rgwvzq@/vmlinuz-5.15.0-37-generic root=ZFS=rpool/ROOT/ubuntu_rgwvzq ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-37-generic N/A linux-backports-modules-5.15.0-37-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2022 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: T76 Ver. 01.08.00 dmi.board.name: 8846 dmi.board.vendor: HP dmi.board.version: KBC Version 30.37.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 48.55 dmi.modalias: dmi:bvnHP:bvrT76Ver.01.08.00:bd01/11/2022:br8.0:efr48.55:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.37.00:cvnHP:ct10:cvr:sku4V1S3UP#ABL: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G8 Notebook PC dmi.product.sku: 4V1S3UP#ABL dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978980] Re: [amdgpu] Wrong external screen resolution after wake up from sleep
The bug is also effective on ubuntu 20.04.3 - fresh installation with all updates. But it wasn't effective prior updating. After downgrading xserver-xorg-legacy and xserver-xorg-core from 2:1.20.13-1ubuntu1~20.04.3 back to the version 2:1.20.13-1ubuntu1~20.04.2, the problem seems to be gone. I'll come back in a week and confirm whether this is really true. -- 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/1978980 Title: [amdgpu] Wrong external screen resolution after wake up from sleep Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: After the Ubuntu distro upgrade (upgrade from LTS 20.04 to LTS 22.04, running KDE) I started experiencing a problem with external screen resolution after the wake up from sleep. The monitor resolution is small (1280x768) and doesn't respect the setting prior the sleep (1920x1200). After the wake up from sleep: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1280x768 59.94* # a list of lower resolutions ``` There is an error when trying to change the setting to the highest resolution supported by the monitor (which is not included in the above list). ``` > xrandr --output DisplayPort-1 --mode 1920x1200 xrandr: cannot find mode 1920x1200 ``` After the turn off and turn on of the external monitor, the resolution is somehow added to the xrandr list: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1920x1200 59.95 + # a list of resolutions 1280x768 59.94* # a list of lower resolutions ``` Now it is possible to change the resolution: ``` > xrandr --output DisplayPort-1 --mode 1920x1200 # no output, the resolution was successfully changed ``` After the change, the resolution is successfully changed and xrandr gives proper output: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1920x1200 59.95*+ # a list of lower resolutions ``` The problem is not present on fresh start. However, it is consistently present after the wake up from sleep. What can cause the problem and how may I fix it? Running AMD based laptop (Ryzen 7 3700U with integrated graphics), the external monitor is connected via USB-C. There are no problems with laptop screen resolution, only external monitor is affected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Jun 16 18:12:05 2022 DistUpgraded: 2022-05-08 07:52:25,560 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2019-08-21 (1030 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20NE000BMC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=0fff4104-4909-4124-b8b0-8430281f24be ro open splash iommu=soft vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-05-08 (39 days ago) dmi.bios.date: 01/26/2022 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET44W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NE000BMC dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.24 dmi.modalias:
[Kernel-packages] [Bug 1982994] Re: zfsutils-linux fails to install in lxc ubuntu 20.04 guest container
** Package changed: ubuntu => zfs-linux (Ubuntu) -- 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/1982994 Title: zfsutils-linux fails to install in lxc ubuntu 20.04 guest container Status in zfs-linux package in Ubuntu: New Bug description: I wasn't allowed to enter 'zfsutils-linux' as the package name in this bug report because" '"zfsutils-linux" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know"' yet here it is: https://packages.ubuntu.com/focal/amd64/zfsutils-linux Here is the transcript of the failure: sudo apt install zfsutils-linux Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvpair1linux libuutil1linux libzfs2linux libzpool2linux zfs-zed Suggested packages: nfs-kernel-server samba-common-bin zfs-initramfs | zfs-dracut The following NEW packages will be installed: libnvpair1linux libuutil1linux libzfs2linux libzpool2linux zfs-zed zfsutils-linux 0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded. Need to get 1,523 kB of archives. After this operation, 5,407 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libnvpair1linux amd64 0.8.3-1ubuntu12.14 [48.2 kB] Get:2 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libuutil1linux amd64 0.8.3-1ubuntu12.14 [41.6 kB] Get:3 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libzfs2linux amd64 0.8.3-1ubuntu12.14 [207 kB] Get:4 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libzpool2linux amd64 0.8.3-1ubuntu12.14 [812 kB] Get:5 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 zfsutils-linux amd64 0.8.3-1ubuntu12.14 [355 kB] Get:6 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 zfs-zed amd64 0.8.3-1ubuntu12.14 [59.7 kB] Fetched 1,523 kB in 3s (490 kB/s) Selecting previously unselected package libnvpair1linux. (Reading database ... 40830 files and directories currently installed.) Preparing to unpack .../0-libnvpair1linux_0.8.3-1ubuntu12.14_amd64.deb ... Unpacking libnvpair1linux (0.8.3-1ubuntu12.14) ... Selecting previously unselected package libuutil1linux. Preparing to unpack .../1-libuutil1linux_0.8.3-1ubuntu12.14_amd64.deb ... Unpacking libuutil1linux (0.8.3-1ubuntu12.14) ... Selecting previously unselected package libzfs2linux. Preparing to unpack .../2-libzfs2linux_0.8.3-1ubuntu12.14_amd64.deb ... Unpacking libzfs2linux (0.8.3-1ubuntu12.14) ... Selecting previously unselected package libzpool2linux. Preparing to unpack .../3-libzpool2linux_0.8.3-1ubuntu12.14_amd64.deb ... Unpacking libzpool2linux (0.8.3-1ubuntu12.14) ... Selecting previously unselected package zfsutils-linux. Preparing to unpack .../4-zfsutils-linux_0.8.3-1ubuntu12.14_amd64.deb ... Unpacking zfsutils-linux (0.8.3-1ubuntu12.14) ... Selecting previously unselected package zfs-zed. Preparing to unpack .../5-zfs-zed_0.8.3-1ubuntu12.14_amd64.deb ... Unpacking zfs-zed (0.8.3-1ubuntu12.14) ... Setting up libuutil1linux (0.8.3-1ubuntu12.14) ... Setting up libnvpair1linux (0.8.3-1ubuntu12.14) ... Setting up libzfs2linux (0.8.3-1ubuntu12.14) ... Setting up libzpool2linux (0.8.3-1ubuntu12.14) ... Setting up zfsutils-linux (0.8.3-1ubuntu12.14) ... modprobe: FATAL: Module zfs not found in directory /lib/modules/5.15.0-41-generic Created symlink /etc/systemd/system/zfs-import.target.wants/zfs-import-cache.service → /lib/systemd/system/zfs-import-cache.service. Created symlink /etc/systemd/system/zfs.target.wants/zfs-import.target → /lib/systemd/system/zfs-import.target. Created symlink /etc/systemd/system/zfs-mount.service.wants/zfs-load-module.service → /lib/systemd/system/zfs-load-module.service. Created symlink /etc/systemd/system/zfs.target.wants/zfs-load-module.service → /lib/systemd/system/zfs-load-module.service. Created symlink /etc/systemd/system/zfs.target.wants/zfs-mount.service → /lib/systemd/system/zfs-mount.service. Created symlink /etc/systemd/system/zfs.target.wants/zfs-share.service → /lib/systemd/system/zfs-share.service. Created symlink /etc/systemd/system/zfs-volumes.target.wants/zfs-volume-wait.service → /lib/systemd/system/zfs-volume-wait.service. Created symlink /etc/systemd/system/zfs.target.wants/zfs-volumes.target → /lib/systemd/system/zfs-volumes.target. Created symlink /etc/systemd/system/multi-user.target.wants/zfs.target → /lib/systemd/system/zfs.target. zfs-import-scan.service is a disabled or a static unit, not starting it. zfs-import-scan.service is a disabled or a static unit, not starting it. Job for zfs-mount.service failed because the control process exited with error code. See "systemctl
[Kernel-packages] [Bug 1982994] [NEW] zfsutils-linux fails to install in lxc ubuntu 20.04 guest container
You have been subscribed to a public bug: I wasn't allowed to enter 'zfsutils-linux' as the package name in this bug report because" '"zfsutils-linux" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know"' yet here it is: https://packages.ubuntu.com/focal/amd64/zfsutils-linux Here is the transcript of the failure: sudo apt install zfsutils-linux Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvpair1linux libuutil1linux libzfs2linux libzpool2linux zfs-zed Suggested packages: nfs-kernel-server samba-common-bin zfs-initramfs | zfs-dracut The following NEW packages will be installed: libnvpair1linux libuutil1linux libzfs2linux libzpool2linux zfs-zed zfsutils-linux 0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded. Need to get 1,523 kB of archives. After this operation, 5,407 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libnvpair1linux amd64 0.8.3-1ubuntu12.14 [48.2 kB] Get:2 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libuutil1linux amd64 0.8.3-1ubuntu12.14 [41.6 kB] Get:3 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libzfs2linux amd64 0.8.3-1ubuntu12.14 [207 kB] Get:4 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libzpool2linux amd64 0.8.3-1ubuntu12.14 [812 kB] Get:5 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 zfsutils-linux amd64 0.8.3-1ubuntu12.14 [355 kB] Get:6 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 zfs-zed amd64 0.8.3-1ubuntu12.14 [59.7 kB] Fetched 1,523 kB in 3s (490 kB/s) Selecting previously unselected package libnvpair1linux. (Reading database ... 40830 files and directories currently installed.) Preparing to unpack .../0-libnvpair1linux_0.8.3-1ubuntu12.14_amd64.deb ... Unpacking libnvpair1linux (0.8.3-1ubuntu12.14) ... Selecting previously unselected package libuutil1linux. Preparing to unpack .../1-libuutil1linux_0.8.3-1ubuntu12.14_amd64.deb ... Unpacking libuutil1linux (0.8.3-1ubuntu12.14) ... Selecting previously unselected package libzfs2linux. Preparing to unpack .../2-libzfs2linux_0.8.3-1ubuntu12.14_amd64.deb ... Unpacking libzfs2linux (0.8.3-1ubuntu12.14) ... Selecting previously unselected package libzpool2linux. Preparing to unpack .../3-libzpool2linux_0.8.3-1ubuntu12.14_amd64.deb ... Unpacking libzpool2linux (0.8.3-1ubuntu12.14) ... Selecting previously unselected package zfsutils-linux. Preparing to unpack .../4-zfsutils-linux_0.8.3-1ubuntu12.14_amd64.deb ... Unpacking zfsutils-linux (0.8.3-1ubuntu12.14) ... Selecting previously unselected package zfs-zed. Preparing to unpack .../5-zfs-zed_0.8.3-1ubuntu12.14_amd64.deb ... Unpacking zfs-zed (0.8.3-1ubuntu12.14) ... Setting up libuutil1linux (0.8.3-1ubuntu12.14) ... Setting up libnvpair1linux (0.8.3-1ubuntu12.14) ... Setting up libzfs2linux (0.8.3-1ubuntu12.14) ... Setting up libzpool2linux (0.8.3-1ubuntu12.14) ... Setting up zfsutils-linux (0.8.3-1ubuntu12.14) ... modprobe: FATAL: Module zfs not found in directory /lib/modules/5.15.0-41-generic Created symlink /etc/systemd/system/zfs-import.target.wants/zfs-import-cache.service → /lib/systemd/system/zfs-import-cache.service. Created symlink /etc/systemd/system/zfs.target.wants/zfs-import.target → /lib/systemd/system/zfs-import.target. Created symlink /etc/systemd/system/zfs-mount.service.wants/zfs-load-module.service → /lib/systemd/system/zfs-load-module.service. Created symlink /etc/systemd/system/zfs.target.wants/zfs-load-module.service → /lib/systemd/system/zfs-load-module.service. Created symlink /etc/systemd/system/zfs.target.wants/zfs-mount.service → /lib/systemd/system/zfs-mount.service. Created symlink /etc/systemd/system/zfs.target.wants/zfs-share.service → /lib/systemd/system/zfs-share.service. Created symlink /etc/systemd/system/zfs-volumes.target.wants/zfs-volume-wait.service → /lib/systemd/system/zfs-volume-wait.service. Created symlink /etc/systemd/system/zfs.target.wants/zfs-volumes.target → /lib/systemd/system/zfs-volumes.target. Created symlink /etc/systemd/system/multi-user.target.wants/zfs.target → /lib/systemd/system/zfs.target. zfs-import-scan.service is a disabled or a static unit, not starting it. zfs-import-scan.service is a disabled or a static unit, not starting it. Job for zfs-mount.service failed because the control process exited with error code. See "systemctl status zfs-mount.service" and "journalctl -xe" for details. invoke-rc.d: initscript zfs-mount, action "start" failed. ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2022-07-28 13:26:08 AEST; 7ms ago Docs: man:zfs(8) Process: 1116 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE)
[Kernel-packages] [Bug 1969482] Re: zfs-2.1.4+ sru
The updated kernel was released, and it fixes the performance regression. Thank you! # uname -a Linux arpa 5.15.0-43-generic #46-Ubuntu SMP Tue Jul 12 10:30:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux # zfs --version zfs-2.1.4-0ubuntu0.1 zfs-kmod-2.1.4-0ubuntu0.1 # grep . /sys/module/icp/parameters/*impl* /sys/module/icp/parameters/icp_aes_impl:cycle [fastest] generic x86_64 aesni /sys/module/icp/parameters/icp_gcm_impl:cycle [fastest] avx generic pclmulqdq # dd if=14GBfile.tmp of=/dev/null bs=1M 13411+1 records in 13411+1 records out 14062902185 bytes (14 GB, 13 GiB) copied, 12.6139 s, 1.1 GB/s -- 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/1969482 Title: zfs-2.1.4+ sru Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Jammy: Fix Released Bug description: [Impact] * Upstream stable point release update with bugfixes, performance fixes, and newer kernel support as needed already in the OEM kernel and will be needed in the future HWE kernels. [Test Plan] * autopkgtest pass * kernel regression zfs testsuite pass * zsys integration test pass [Where problems could occur] * The stable branches maintain api/abi. Certain bugfixes do change userspace visible behavior of either succeeeding (when previously operations failed), or return errors when previously succeeding in error. For example there are changes when unlinking files in full volumes; changes to fallocate behaviour, etc. Overall they are minor corner cases, and bugfixes to correct the bahaviour to what is universally expected and how things behave on other filesystems (i.e. ext4). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971151] Re: [Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support
Hi Michael, Could you please help with the test kernel ? Thanks, Sumit -- 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/1971151 Title: [Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support Status in linux package in Ubuntu: In Progress Bug description: Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: ed567615f7ec scsi: mpi3mr: Fix build errors in uapi header scsi_bsg_mpi3mr.h dde822e21700 scsi: mpi3mr: Update driver version to 8.0.0.69.0 04dfa01e77ea scsi: mpi3mr: Add support for NVMe passthrough 937a6f2c4f2e scsi: mpi3mr: Expose adapter state to sysfs 83959ce5204a scsi: mpi3mr: Add support for PEL commands eb8a3217cd7d scsi: mpi3mr: Add support for MPT commands 455aac4f7a13 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header a212ebe7d4b1 scsi: mpi3mr: Add support for driver commands 7fbaf8b0d8b8 scsi: mpi3mr: Add bsg device support Thanks, Sumit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959973] Re: [22.04 FEAT] KVM: Attestation support for Secure Execution (crypto)
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959973 Title: [22.04 FEAT] KVM: Attestation support for Secure Execution (crypto) Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: == [Impact] * This is a hardware enablement SRU in support of IBM z15 and LinuxONE III (FC 115) secure execution feature. * It adds a misc character device to expose some Ultravisor functions to userspace. * The device is only available if the (optional) Ultravisor Facility (158) is present in the system. * Two Ultravisor calls are supported: - Query Ultravisor Information (QUI) and - Receive Attestation Measurement (Attest[ation]) * This is in support of for example. external frameworks, specific deployment models or especially potentially regulatory requirements. [Fix] * 4689752c79fa 4689752c79fa30e91b49b39a9fba93c4d1f3e20c "drivers/s390/char: Add Ultravisor io device" * eb3de2d8f78d eb3de2d8f78d893303891d879f941c47f2f2d13d "s390/uv_uapi: depend on CONFIG_S390" * patch to set kernel config option 'CONFIG_S390_UV_UAPI=y' [Test Plan] * An IBM z15 or LinuxONE III LPAR with FC 115 enabled is required. * Installation of Ubuntu Server 22.04 LTS on top. * Install a kernel that incl. the above patches/commits (that has the kernel config option 'CONFIG_S390_UV_UAPI' enabled). * Activate the kernel (reboot) and look for the existence of the uvdevice '/dev/uv'. * Use a userspace test program that makes use of the new misc device by exploiting 'ATTEST'. * Due to hardware requirements this test needs to be conducted by IBM. [Where problems could occur] * The definitions in uv_cmds_inst and uv_feat_ind could be wrong and the codes wrong or mixed up, which would lead to a broken functionality/interface. * The uvdevice header definitions could be erroneous, defining an wrong interface. * The newly added kernel options could be implemented in a wrong way, so that it doesn't enable the 'uvdevice', but unlikely. * The implementation of the device itself in 'uvdevice.c' could be broken by wrong or broken pointer arithmetics, wrong method arguments, wrong sizeof/length calculations, which - in worst case - could entirely crash a system. * The ioctl control block implementation could be wrong in a way, that it doesn't properly handle the case where the facility is not available in the system. * Entry point, copy and check routines could be wrong, allowing non-desired calls. * This is an s390x-only functionality, that is only available on IBM z15 / LinuxONE III systems and newer, and only is the optional feature 'FC 115' in place, which is limited to 'secure-execution' workloads. [Other Info] * The above commit is marked to be merged into 5.19-rc2, and since the planned target kernel for kinetic is 5.19, the SRU is not needed for kinetic. __ KVM: Attestation support for Secure Execution (crypto) Description: Provide attestations support, e.g. for external frameworks, specific deployment models or potentially regulatory requirements. Request Type: Kernel - Enhancement from IBM Upstream Acceptance: In Progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959973/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980951] Re: [UBUNTU 22.04] Kernel oops while removing device from cio_ignore list
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980951 Title: [UBUNTU 22.04] Kernel oops while removing device from cio_ignore list Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: == [Impact] * A kernel Oops occurs when a device is removed from the cio_ignore list (that is used to hide ccw devices) on a system with non-I/O subchannels (e.g. SCM or CHSC subchannels). * As a result, previously ignored devices cannot be activated again, and new devices cannot be found. [Fix] * 0c3812c347bf 0c3812c347bfb0dc213556a195e79850c55702f5 "s390/cio: derive cdev information only for IO-subchannels" [Test Plan] * An IBM zSystems or LinuxONE LPAR with with non-I/O subchannels. * Ubuntu Server 22.04 LTS (with GA kernel 5.15) installed. * Define a cio_ignore list (to hide ccw devices). * Remove a device from the cio_ignore list. * Due to hardware requirements this test needs to be conducted by IBM. [Where problems could occur] * General problems may occur with ccw device activation/deactivation in case the new initialization is erroneous. * Issues may also have an impact on the type of ccw devices, and may no longer be limited to non-I/O subchannels. * Things could still go wrong in case cdev is still not properly derived from sch-type SUBCHANNEL_TYPE_IO. [Other Info] * The commit is upstream since kernel 5.16 (next-20220315). __ ---Problem Description from Peter--- A kernel oops occurs when a device is removed from the cio_ignore list on a system with non-I/O subchannels (e.g. SCM or CHSC subchannels). As a result, previously ignored devices cannot be activated, and new devices cannot be found. ---uname output--- Linux localhost 5.15.0-40-generic #43-Ubuntu SMP Wed Jun 15 12:53:53 UTC 2022 s390x s390x s390x GNU/Linux Machine Type = s390x ---Steps to Reproduce--- On an s390x-LPAR with non-I/O subchannels, remove a device from the cio_ignore list. Oops output: [ 51.597505] Unable to handle kernel pointer dereference in virtual kernel address space [ 51.597516] Failing address: 2081e99191e98000 TEID: 2081e99191e98803 [ 51.597520] Fault in home space mode while using kernel ASCE. [ 51.597524] AS:82adc007 R3:0024 [ 51.597665] Oops: 0038 ilc:3 [#1] SMP [ 51.597671] Modules linked in: scm_block chsc_sch vfio_ccw mdev vfio_iommu_type1 vfio eadm_sch sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua drm i2c_core drm_panel_orientation_quirks ip_tables x_tables btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_ xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear pkey zcrypt crc32_vx_s390 ghash_s390 prng chacha_s390 libchacha aes_s390 des_s390 libdes qeth_l2 bridge stp llc zfcp qeth qdio scsi_transport_fc ccwgroup sha512_s390 sha256_s390 sha1_s390 sha_common [ 51.597735] CPU: 6 PID: 1418 Comm: cio_ignore Not tainted 5.15.0-40-generic #43-Ubuntu [ 51.597740] Hardware name: IBM 2964 NC9 702 (LPAR) [ 51.597742] Krnl PSW : 0704e0018000 81b0c632 (__unset_online+0x22/0x70) [ 51.597752]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [ 51.597756] Krnl GPRS: 0001 004a3ca8 038007e49000 2081e99191e98528 [ 51.597760] 81b0c610 81b07f10 [ 51.597762]02aa 81b0c610 038007e49000 038007a6bc98 [ 51.597765]941f9200 03ffa8cf95e0 81818900 038007a6bbf8 [ 51.597773] Krnl Code: 81b0c624: a784000cbrc 8,81b0c63c [ 51.597773]81b0c628: e3303022ltg %r3,32(%r3) [ 51.597773] #81b0c62e: a7840007brc 8,81b0c63c [ 51.597773] >81b0c632: e3303212lt %r3,512(%r3) [ 51.597773]81b0c638: a7740007brc 7,81b0c646 [ 51.597773]81b0c63c: a729lghi%r2,0 [ 51.597773]81b0c640: c0f400089854brcl 15,81c1f6e8 [ 51.597773]81b0c646: ebeff0880024stmg %r14,%r15,136(%r15) [ 51.597818] Call Trace: [ 51.597820] [<81b0c632>] __unset_online+0x22/0x70 [ 51.597824] ([<818188e6>] bus_for_each_dev+0x66/0xc0) [ 51.597828] [<81b0e378>] css_schedule_eval_cond+0xe8/0x130 [ 51.597832] [<81b08062>]
[Kernel-packages] [Bug 1982716] Re: Audio mute key (f5) LED and Mic mute key (f8) LED are no function on HP 440/450/640/650 G9
@Stefan This fix also needs to be added in linux-oem-5.14 (Ubuntu) Focal. Could you help add this. Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1982716 Title: Audio mute key (f5) LED and Mic mute key (f8) LED are no function on HP 440/450/640/650 G9 Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-hwe-5.17 source package in Jammy: In Progress Bug description: [Impact] The audio mute key (F5) and mic-mute LED (F8) don't work on some HP 440/450/640/650 G9 laptops. [Fix] The HP ProBook 440/450 G9 and EliteBook 640/650 G9 have multiple motherboard design and they are using different subsystem ID of audio codec. Add the same quirk for other MBs. [Test] After applying the fix, the mute LEDs are working. [Where problems could occur] It's low risk as it's specific ID for HP new machines. If the HP ships other machines using same SSID, then the LED may not work on those machines. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1982716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981173] Re: Clear PCI errors left from BIOS
** 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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1981173 Title: Clear PCI errors left from BIOS Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] Errors like Master Abort can be flagged before setting up PCI devices. [Fix] Clear PCI status that BIOS handed over to the OS. [Test] Using `lspci`, no more errors after boot. [Where problems could occur] If there's any driver's probe routine depends on PCI status to have different behavior, this can cause some cracks. There doesn't seem to be any driver doing such insane thing though. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981773] Re: Make cm32181 sensor work after system suspend
** 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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1981773 Title: Make cm32181 sensor work after system suspend 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-oem-5.17 package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] cm32181 ambient light sensor stops working after system suspend. [Fix] Add PM support for cm32181 so it can work after system suspend. [Test] The sysfs in_illuminance_input continues to change after system suspend. [Where problems could occur] This changeset is limited to a specific device, and it already lacks PM support - so the worst case is that it stops working after resume like it always has been. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
** Also affects: network-manager (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Also affects: urfkill (Ubuntu Kinetic) 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/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in urfkill package in Ubuntu: New Status in linux source package in Jammy: Fix Released Status in network-manager source package in Jammy: Invalid Status in urfkill source package in Jammy: New Status in linux source package in Kinetic: Invalid Status in network-manager source package in Kinetic: Invalid Status in urfkill source package in Kinetic: New Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983030] [NEW] Kernel fails to boot on some AMD systems
Public bug reported: [Impact] 4.4 kernels will fail to boot on AWS instance types m6a and c6a. [Test case] Boot kernels on those instance types. [Fix] Flushes TLB global mappings when system is not affected by Meltdown. [Potential regression] Missing TLB flushes may lead to security vulnerabilities. Unneeded TLB flushes lead to performance impact. ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Xenial) Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu) 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/1983030 Title: Kernel fails to boot on some AMD systems Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Bug description: [Impact] 4.4 kernels will fail to boot on AWS instance types m6a and c6a. [Test case] Boot kernels on those instance types. [Fix] Flushes TLB global mappings when system is not affected by Meltdown. [Potential regression] Missing TLB flushes may lead to security vulnerabilities. Unneeded TLB flushes lead to performance impact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981773] Re: Make cm32181 sensor work after system suspend
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1047.54 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1981773 Title: Make cm32181 sensor work after system suspend 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-oem-5.17 package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] cm32181 ambient light sensor stops working after system suspend. [Fix] Add PM support for cm32181 so it can work after system suspend. [Test] The sysfs in_illuminance_input continues to change after system suspend. [Where problems could occur] This changeset is limited to a specific device, and it already lacks PM support - so the worst case is that it stops working after resume like it always has been. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981173] Re: Clear PCI errors left from BIOS
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1047.54 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1981173 Title: Clear PCI errors left from BIOS Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] Errors like Master Abort can be flagged before setting up PCI devices. [Fix] Clear PCI status that BIOS handed over to the OS. [Test] Using `lspci`, no more errors after boot. [Where problems could occur] If there's any driver's probe routine depends on PCI status to have different behavior, this can cause some cracks. There doesn't seem to be any driver doing such insane thing though. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981950] Re: Failed to resume from S3 blocked by atlantic driver[1d6a:94c0]
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1047.54 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1981950 Title: Failed to resume from S3 blocked by atlantic driver[1d6a:94c0] Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] The system with atlantic NIC[1d6a:94c0] fails to resume from S3 and hang with the following errors Jun 7 13:13:54 ubuntu kernel: [ 116.000561] aq_nic_deinit+0xb4/0xd0 [atlantic] Jun 7 13:13:54 ubuntu kernel: [ 116.000566] atl_resume_common+0x6d/0x110 [atlantic] Jun 7 13:13:54 ubuntu kernel: [ 116.000571] aq_pm_resume_restore+0x13/0x20 [atlantic] Jun 7 13:13:54 ubuntu kernel: [ 116.000575] pci_pm_resume+0x5c/0x90 Jun 7 13:13:54 ubuntu kernel: [ 116.000578] ? pci_pm_thaw+0x80/0x80 Jun 7 13:13:54 ubuntu kernel: [ 116.000580] dpm_run_callback+0x4e/0x120 Jun 7 13:13:54 ubuntu kernel: [ 116.000582] device_resume+0xad/0x200 Jun 7 13:13:54 ubuntu kernel: [ 116.000583] async_resume+0x1e/0x40 Jun 7 13:13:54 ubuntu kernel: [ 116.000585] async_run_entry_fn+0x33/0x120 Jun 7 13:13:54 ubuntu kernel: [ 116.000586] process_one_work+0x220/0x3c0 Jun 7 13:13:54 ubuntu kernel: [ 116.000588] worker_thread+0x4d/0x3f0 Jun 7 13:13:54 ubuntu kernel: [ 116.000589] ? process_one_work+0x3c0/0x3c0 Jun 7 13:13:54 ubuntu kernel: [ 116.000591] kthread+0x12a/0x150 Jun 7 13:13:54 ubuntu kernel: [ 116.000592] ? set_kthread_struct+0x40/0x40 Jun 7 13:13:54 ubuntu kernel: [ 116.000593] ret_from_fork+0x22/0x30 Jun 7 13:13:54 ubuntu kernel: [ 116.000596] Jun 7 13:13:54 ubuntu kernel: [ 116.000596] ---[ end trace 9d3fcd41d27dae25 ]--- [Fix] aq_nic_deinit() has been called while suspending, so don't need to call it again on resuming. Applied below 2 commits from v5.19-rc7 fix the issue, and the 2 commits have been applied to stable kernel v5.10, v5.15, and v5.18. 2e15c51fefaf net: atlantic: remove aq_nic_deinit() when resume 0f3325076038 net: atlantic: remove deep parameter on suspend/resume functions [Test] Verified on the system with atlantic NIC[1d6a:94c0] and run S3 test for more than 200 times. [Where problems could occur] The 2 commits remove the redundant code, aq_nic_deinit() has been called while suspending, so we don't need to call it again while resuming, and this fix the issue. I don't think this would introduce any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982104] Re: intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1047.54 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1982104 Title: intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] Ubuntu 22.04 installation crashes on our Intel Sapphire Rapids proto server. Attaching the console logs. Currently, it looks like disabling VT-D option in BIOS settings helps mitigate the issue. Console logs indicate something is wrong in iommu/dmar subsystem. [Fix] The IOMMU driver shares the pasid table for PCI alias devices. When the RID2PASID entry of the shared pasid table has been filled by the first device, the subsequent device will encounter the "DMAR: Setup RID2PASID failed" failure as the pasid entry has already been marked as present. As the result, the IOMMU probing process will be aborted. On the contrary, when any alias device is hot-removed from the system, for example, by writing to /sys/bus/pci/devices/.../remove, the shared RID2PASID will be cleared without any notifications to other devices. As the result, any DMAs from those rest devices are blocked. Sharing pasid table among PCI alias devices could save two memory pages for devices underneath the PCIe-to-PCI bridges. Anyway, considering that those devices are rare on modern platforms that support VT-d in scalable mode and the saved memory is negligible, it's reasonable to remove this part of immature code to make the driver feasible and stable. [Test Case] 1. use the target machine(Intel Sapphire Rapids) and install the kernel with the fix. 2. boot the target machine 3. check dmesg if the error message exists [ 8.120527] pci :03:01.0: DMAR: Setup RID2PASID failed [Where problems could occur] After enable intel_iommu, the errors may be occurred. We need to figure out one by one once the related errors are triggered in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1982104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912509] Re: usci_acpi USBC000:00: PPM init failed (-110)
I get this message on TUXEDO InfinityBook S 14 - Gen6 with Linux 5.15 kernel. The boot works fine. However, the system freezes later on, unless I have something plugged into a USB port (like a USB mouse), but i do not know if this is related. -- 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/1912509 Title: usci_acpi USBC000:00: PPM init failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: When booting with kernel 5.8.0-38-generic on my Asus Tuf 15 with 2 NVMe drives I get: usci_acpi USBC000:00: PPM init failed (-110) and the laptop freezes. kernel 5.4.0-26-generic usually boots (but get an occasional freeze). Since I cannot boot in the 5.8 kernel I cannot file the bug with that kernel running. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vincent1381 F pulseaudio /dev/snd/controlC0: vincent1381 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 20 17:28:23 2021 InstallationDate: Installed on 2021-01-20 (0 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 003: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX506LI_FX506LI ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=74589408-5655-4728-b040-86c06177a989 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX506LI.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX506LI 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.:bvrFX506LI.307:bd12/17/2020:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506LI_FX506LI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506LI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ASUS TUF Gaming F15 dmi.product.name: ASUS TUF Gaming F15 FX506LI_FX506LI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912509/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983019] [NEW] Pinctrl driver has a race condition bug
Public bug reported: [Impact] * The pinctrl-starfive driver has a race when initializing groups and functions that may result in other drivers not being able to initialize. * If this happens to the mmc driver the board will fail to boot. * This is an example of this happening: Loading device tree blob... [ 13.933777] pinctrl-starfive 1191.pinctrl: does not have pin group sdio0-0.sdio-pins [ 13.941940] pinctrl-starfive 1191.pinctrl: invalid group sdio0-0.sdio-pins in map table [ 13.957656] pinctrl-starfive 1191.pinctrl: does not have pin group sdio0-0.sdio-pins [ 13.965801] pinctrl-starfive 1191.pinctrl: could not map group config for "sdio0-0.sdio-pins" [ 13.974746] Unable to handle kernel NULL pointer dereference at virtual address [ 13.983581] Oops [#1] [ 13.985853] Modules linked in: phylink dw_mmc_pltfm clk_starfive_jh7100_audio reset_starfive_jh7100_audio(+) dw_mc [ 13.986227] starfive-drm soc:display-subsystem: bound 1200.crtc (ops starfive_crtc_component_ops) [ 13.996286] CPU: 1 PID: 8 Comm: kworker/u4:0 Not tainted 5.17.0-1004-starfive #5-Ubuntu [ 13.996297] Hardware name: StarFive VisionFive V1 (DT) [ 13.996305] Workqueue: events_unbound async_run_entry_fn [ 14.023868] epc : strcmp+0x12/0x36 [ 14.027274] ra : pinmux_func_name_to_selector+0x5a/0x76 [ 14.032583] epc : 80521224 ra : 805307d8 sp : ffd88006bb00 [ 14.039781] gp : 81e32e30 tp : ffd87ffd t0 : 0040 [ 14.046988] t1 : t2 : 81004ed4 s0 : ffd88006bb10 [ 14.054190] s1 : 0006 a0 : ffd9ff1d3cb8 a1 : [ 14.061392] a2 : a3 : a4 : ffd88c45ce00 [ 14.068594] a5 : 0073 a6 : ffd88c45cdb0 a7 : ffd88c45ce08 [ 14.075795] s2 : ffd897c53000 s3 : 0007 s4 : ffd9ff1d3cb8 [ 14.082996] s5 : 810776f0 s6 : s7 : ffd8801aa5c0 [ 14.090199] s8 : ffd890fdf780 s9 : fdfb s10: 81d80008 [ 14.097400] s11: t3 : 0002 t4 : 0402 [ 14.104600] t5 : ffd897c53040 t6 : ffd897c53048 [ 14.109896] status: 00020120 badaddr: cause: 000d [ 14.117986] ---[ end trace ]--- [Test Plan] * Unfortunately this is a race that happens rarely so rebooting the board several times is the only known way to reproduce. [Where problems could occur] * The fix could get the locking wrong and lock up the machine at boot. ** Affects: linux-starfive-5.17 (Ubuntu) Importance: Undecided Assignee: Emil Renner Berthing (esmil) Status: In Progress ** Changed in: linux-starfive-5.17 (Ubuntu) Assignee: (unassigned) => Emil Renner Berthing (esmil) ** Changed in: linux-starfive-5.17 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1983019 Title: Pinctrl driver has a race condition bug Status in linux-starfive-5.17 package in Ubuntu: In Progress Bug description: [Impact] * The pinctrl-starfive driver has a race when initializing groups and functions that may result in other drivers not being able to initialize. * If this happens to the mmc driver the board will fail to boot. * This is an example of this happening: Loading device tree blob... [ 13.933777] pinctrl-starfive 1191.pinctrl: does not have pin group sdio0-0.sdio-pins [ 13.941940] pinctrl-starfive 1191.pinctrl: invalid group sdio0-0.sdio-pins in map table [ 13.957656] pinctrl-starfive 1191.pinctrl: does not have pin group sdio0-0.sdio-pins [ 13.965801] pinctrl-starfive 1191.pinctrl: could not map group config for "sdio0-0.sdio-pins" [ 13.974746] Unable to handle kernel NULL pointer dereference at virtual address [ 13.983581] Oops [#1] [ 13.985853] Modules linked in: phylink dw_mmc_pltfm clk_starfive_jh7100_audio reset_starfive_jh7100_audio(+) dw_mc [ 13.986227] starfive-drm soc:display-subsystem: bound 1200.crtc (ops starfive_crtc_component_ops) [ 13.996286] CPU: 1 PID: 8 Comm: kworker/u4:0 Not tainted 5.17.0-1004-starfive #5-Ubuntu [ 13.996297] Hardware name: StarFive VisionFive V1 (DT) [ 13.996305] Workqueue: events_unbound async_run_entry_fn [ 14.023868] epc : strcmp+0x12/0x36 [ 14.027274] ra : pinmux_func_name_to_selector+0x5a/0x76 [ 14.032583] epc : 80521224 ra : 805307d8 sp : ffd88006bb00 [ 14.039781] gp : 81e32e30 tp : ffd87ffd t0 : 0040 [ 14.046988] t1 : t2 : 81004ed4 s0 : ffd88006bb10 [ 14.054190] s1 : 0006 a0 : ffd9ff1d3cb8 a1 : [
[Kernel-packages] [Bug 1978980] Re: [amdgpu] Wrong external screen resolution after wake up from sleep
The bug is also effective on ubuntu 20.04 (fresh installation with all updates). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1978980 Title: [amdgpu] Wrong external screen resolution after wake up from sleep Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: After the Ubuntu distro upgrade (upgrade from LTS 20.04 to LTS 22.04, running KDE) I started experiencing a problem with external screen resolution after the wake up from sleep. The monitor resolution is small (1280x768) and doesn't respect the setting prior the sleep (1920x1200). After the wake up from sleep: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1280x768 59.94* # a list of lower resolutions ``` There is an error when trying to change the setting to the highest resolution supported by the monitor (which is not included in the above list). ``` > xrandr --output DisplayPort-1 --mode 1920x1200 xrandr: cannot find mode 1920x1200 ``` After the turn off and turn on of the external monitor, the resolution is somehow added to the xrandr list: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1920x1200 59.95 + # a list of resolutions 1280x768 59.94* # a list of lower resolutions ``` Now it is possible to change the resolution: ``` > xrandr --output DisplayPort-1 --mode 1920x1200 # no output, the resolution was successfully changed ``` After the change, the resolution is successfully changed and xrandr gives proper output: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1920x1200 59.95*+ # a list of lower resolutions ``` The problem is not present on fresh start. However, it is consistently present after the wake up from sleep. What can cause the problem and how may I fix it? Running AMD based laptop (Ryzen 7 3700U with integrated graphics), the external monitor is connected via USB-C. There are no problems with laptop screen resolution, only external monitor is affected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Jun 16 18:12:05 2022 DistUpgraded: 2022-05-08 07:52:25,560 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2019-08-21 (1030 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20NE000BMC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=0fff4104-4909-4124-b8b0-8430281f24be ro open splash iommu=soft vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-05-08 (39 days ago) dmi.bios.date: 01/26/2022 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET44W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NE000BMC dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrR11ET44W(1.24):bd01/26/2022:br1.24:efr1.24:svnLENOVO:pn20NE000BMC:pvrThinkPadE495:rvnLENOVO:rn20NE000BMC:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NE_BU_Think_FM_ThinkPadE495: dmi.product.family: ThinkPad E495 dmi.product.name: 20NE000BMC dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495 dmi.product.version: ThinkPad E495 dmi.sys.vendor: LENOVO
[Kernel-packages] [Bug 1980590] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1980590/+attachment/5605731/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980590 Title: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress Status in linux package in Ubuntu: Confirmed Bug description: an android app is sending big UDP datagrams, this generates IPv4 fragments this IPv4 fragments can not be controlled in firewall nftables family netdev hook ingress. platform: Ubuntu 22.04LTS, latest patches installed I documented 2 screenshots fragment1.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, frag-offset=0, total=1500 fragment2.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, frag-offset=1480, total=413 at the bottom of the screenshots is "/usr/sbin/nft monitor trace" family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data total=0x765=1893, ID=0x2466, glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops the nftables TRACE shows an already processed bigger ipv4 packet. there is a race condition! the ipv4 processing has to WAIT for all the rules in family "netdev" hook "ingress" I cannot control ether type 0x800 completely in family "netdev" hook "ingress" this is a security vulnerability! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1324 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/06/2017 dmi.bios.release: 15.101 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.65 dmi.board.name: 1618 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.78 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560p dmi.product.sku: LG731EA#ABD dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980590] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1980590/+attachment/5605730/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980590 Title: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress Status in linux package in Ubuntu: Confirmed Bug description: an android app is sending big UDP datagrams, this generates IPv4 fragments this IPv4 fragments can not be controlled in firewall nftables family netdev hook ingress. platform: Ubuntu 22.04LTS, latest patches installed I documented 2 screenshots fragment1.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, frag-offset=0, total=1500 fragment2.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, frag-offset=1480, total=413 at the bottom of the screenshots is "/usr/sbin/nft monitor trace" family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data total=0x765=1893, ID=0x2466, glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops the nftables TRACE shows an already processed bigger ipv4 packet. there is a race condition! the ipv4 processing has to WAIT for all the rules in family "netdev" hook "ingress" I cannot control ether type 0x800 completely in family "netdev" hook "ingress" this is a security vulnerability! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1324 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/06/2017 dmi.bios.release: 15.101 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.65 dmi.board.name: 1618 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.78 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560p dmi.product.sku: LG731EA#ABD dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980590] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1980590/+attachment/5605732/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980590 Title: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress Status in linux package in Ubuntu: Confirmed Bug description: an android app is sending big UDP datagrams, this generates IPv4 fragments this IPv4 fragments can not be controlled in firewall nftables family netdev hook ingress. platform: Ubuntu 22.04LTS, latest patches installed I documented 2 screenshots fragment1.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, frag-offset=0, total=1500 fragment2.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, frag-offset=1480, total=413 at the bottom of the screenshots is "/usr/sbin/nft monitor trace" family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data total=0x765=1893, ID=0x2466, glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops the nftables TRACE shows an already processed bigger ipv4 packet. there is a race condition! the ipv4 processing has to WAIT for all the rules in family "netdev" hook "ingress" I cannot control ether type 0x800 completely in family "netdev" hook "ingress" this is a security vulnerability! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1324 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/06/2017 dmi.bios.release: 15.101 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.65 dmi.board.name: 1618 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.78 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560p dmi.product.sku: LG731EA#ABD dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948626] Re: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010
This bug was fixed in the package linux - 5.15.0-43.46 --- linux (5.15.0-43.46) jammy; urgency=medium * jammy/linux: 5.15.0-43.46 -proposed tracker (LP: #1981243) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.07.11) * nbd: requests can become stuck when disconnecting from server with qemu-nbd (LP: #1896350) - nbd: don't handle response without a corresponding request message - nbd: make sure request completion won't concurrent - nbd: don't clear 'NBD_CMD_INFLIGHT' flag if request is not completed - nbd: fix io hung while disconnecting device * Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events (LP: #1965241) - PCI/portdrv: Rename pm_iter() to pcie_port_device_iter() - PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset - [Config] Enable config option CONFIG_PCIE_EDR * [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 (LP: #1948626) - nvme: add CNTRLTYPE definitions for 'identify controller' - nvme: send uevent on connection up - nvme: expose cntrltype and dctype through sysfs * [UBUNTU 22.04] Kernel oops while removing device from cio_ignore list (LP: #1980951) - s390/cio: derive cdev information only for IO-subchannels * Jammy Charmed OpenStack deployment fails over connectivity issues when using converged OVS bridge for control and data planes (LP: #1978820) - net/mlx5e: TC NIC mode, fix tc chains miss table * Hairpin traffic does not work with centralized NAT gw (LP: #1967856) - net: openvswitch: fix misuse of the cached connection on tuple changes * alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines (LP: #1980700) - ASoC: amd: Add driver data to acp6x machine driver - ASoC: amd: Add support for enabling DMIC on acp6x via _DSD * AMD ACP 6.x DMIC Supports (LP: #1949245) - ASoC: amd: add Yellow Carp ACP6x IP register header - ASoC: amd: add Yellow Carp ACP PCI driver - ASoC: amd: add acp6x init/de-init functions - ASoC: amd: add platform devices for acp6x pdm driver and dmic driver - ASoC: amd: add acp6x pdm platform driver - ASoC: amd: add acp6x irq handler - ASoC: amd: add acp6x pdm driver dma ops - ASoC: amd: add acp6x pci driver pm ops - ASoC: amd: add acp6x pdm driver pm ops - ASoC: amd: enable Yellow carp acp6x drivers build - ASoC: amd: create platform device for acp6x machine driver - ASoC: amd: add YC machine driver using dmic - ASoC: amd: enable Yellow Carp platform machine driver build - ASoC: amd: fix uninitialized variable in snd_acp6x_probe() - [Config] Enable AMD ACP 6 DMIC Support * [UBUNTU 20.04] Include patches to avoid self-detected stall with Secure Execution (LP: #1979296) - KVM: s390: pv: add macros for UVC CC values - KVM: s390: pv: avoid stalls when making pages secure * [22.04 FEAT] KVM: Attestation support for Secure Execution (crypto) (LP: #1959973) - drivers/s390/char: Add Ultravisor io device - s390/uv_uapi: depend on CONFIG_S390 - [Config] CONFIG_S390_UV_UAPI=y for s390x * CVE-2022-1679 - SAUCE: ath9k: fix use-after-free in ath9k_hif_usb_rx_cb * CVE-2022-28893 - SUNRPC: Ensure we flush any closed sockets before xs_xprt_free() - SUNRPC: Don't leak sockets in xs_local_connect() * CVE-2022-34918 - netfilter: nf_tables: stricter validation of element data * CVE-2022-1652 - floppy: use a statically allocated error counter -- Stefan Bader Tue, 12 Jul 2022 10:51:03 +0200 ** Changed in: linux (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1652 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1679 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-28893 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-34918 -- 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/1948626 Title: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: [Impact] NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one. TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to
[Kernel-packages] [Bug 1896350] Re: nbd: requests can become stuck when disconnecting from server with qemu-nbd
This bug was fixed in the package linux - 5.15.0-43.46
---
linux (5.15.0-43.46) jammy; urgency=medium
* jammy/linux: 5.15.0-43.46 -proposed tracker (LP: #1981243)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.07.11)
* nbd: requests can become stuck when disconnecting from server with qemu-nbd
(LP: #1896350)
- nbd: don't handle response without a corresponding request message
- nbd: make sure request completion won't concurrent
- nbd: don't clear 'NBD_CMD_INFLIGHT' flag if request is not completed
- nbd: fix io hung while disconnecting device
* Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment
events (LP: #1965241)
- PCI/portdrv: Rename pm_iter() to pcie_port_device_iter()
- PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset
- [Config] Enable config option CONFIG_PCIE_EDR
* [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client
- TP 8010 (LP: #1948626)
- nvme: add CNTRLTYPE definitions for 'identify controller'
- nvme: send uevent on connection up
- nvme: expose cntrltype and dctype through sysfs
* [UBUNTU 22.04] Kernel oops while removing device from cio_ignore list
(LP: #1980951)
- s390/cio: derive cdev information only for IO-subchannels
* Jammy Charmed OpenStack deployment fails over connectivity issues when using
converged OVS bridge for control and data planes (LP: #1978820)
- net/mlx5e: TC NIC mode, fix tc chains miss table
* Hairpin traffic does not work with centralized NAT gw (LP: #1967856)
- net: openvswitch: fix misuse of the cached connection on tuple changes
* alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines
(LP: #1980700)
- ASoC: amd: Add driver data to acp6x machine driver
- ASoC: amd: Add support for enabling DMIC on acp6x via _DSD
* AMD ACP 6.x DMIC Supports (LP: #1949245)
- ASoC: amd: add Yellow Carp ACP6x IP register header
- ASoC: amd: add Yellow Carp ACP PCI driver
- ASoC: amd: add acp6x init/de-init functions
- ASoC: amd: add platform devices for acp6x pdm driver and dmic driver
- ASoC: amd: add acp6x pdm platform driver
- ASoC: amd: add acp6x irq handler
- ASoC: amd: add acp6x pdm driver dma ops
- ASoC: amd: add acp6x pci driver pm ops
- ASoC: amd: add acp6x pdm driver pm ops
- ASoC: amd: enable Yellow carp acp6x drivers build
- ASoC: amd: create platform device for acp6x machine driver
- ASoC: amd: add YC machine driver using dmic
- ASoC: amd: enable Yellow Carp platform machine driver build
- ASoC: amd: fix uninitialized variable in snd_acp6x_probe()
- [Config] Enable AMD ACP 6 DMIC Support
* [UBUNTU 20.04] Include patches to avoid self-detected stall with Secure
Execution (LP: #1979296)
- KVM: s390: pv: add macros for UVC CC values
- KVM: s390: pv: avoid stalls when making pages secure
* [22.04 FEAT] KVM: Attestation support for Secure Execution (crypto)
(LP: #1959973)
- drivers/s390/char: Add Ultravisor io device
- s390/uv_uapi: depend on CONFIG_S390
- [Config] CONFIG_S390_UV_UAPI=y for s390x
* CVE-2022-1679
- SAUCE: ath9k: fix use-after-free in ath9k_hif_usb_rx_cb
* CVE-2022-28893
- SUNRPC: Ensure we flush any closed sockets before xs_xprt_free()
- SUNRPC: Don't leak sockets in xs_local_connect()
* CVE-2022-34918
- netfilter: nf_tables: stricter validation of element data
* CVE-2022-1652
- floppy: use a statically allocated error counter
-- Stefan Bader Tue, 12 Jul 2022 10:51:03
+0200
** Changed in: linux (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1652
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1679
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-28893
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-34918
--
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/1896350
Title:
nbd: requests can become stuck when disconnecting from server with
qemu-nbd
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Won't Fix
Status in linux source package in Focal:
In Progress
Status in linux source package in Impish:
Won't Fix
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Bug description:
BugLink: https://bugs.launchpad.net/bugs/1896350
[Impact]
After 2516ab1("nbd: only clear the queue on device teardown"), present
in 4.12-rc1 onward, the ioctl NBD_CLEAR_SOCK can no longer clear
requests currently being processed. This change was made to fix a race
between using the NBD_CLEAR_SOCK ioctl to clear requests, and teardown
[Kernel-packages] [Bug 1949245] Re: AMD ACP 6.x DMIC Supports
This bug was fixed in the package linux - 5.15.0-43.46 --- linux (5.15.0-43.46) jammy; urgency=medium * jammy/linux: 5.15.0-43.46 -proposed tracker (LP: #1981243) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.07.11) * nbd: requests can become stuck when disconnecting from server with qemu-nbd (LP: #1896350) - nbd: don't handle response without a corresponding request message - nbd: make sure request completion won't concurrent - nbd: don't clear 'NBD_CMD_INFLIGHT' flag if request is not completed - nbd: fix io hung while disconnecting device * Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events (LP: #1965241) - PCI/portdrv: Rename pm_iter() to pcie_port_device_iter() - PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset - [Config] Enable config option CONFIG_PCIE_EDR * [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 (LP: #1948626) - nvme: add CNTRLTYPE definitions for 'identify controller' - nvme: send uevent on connection up - nvme: expose cntrltype and dctype through sysfs * [UBUNTU 22.04] Kernel oops while removing device from cio_ignore list (LP: #1980951) - s390/cio: derive cdev information only for IO-subchannels * Jammy Charmed OpenStack deployment fails over connectivity issues when using converged OVS bridge for control and data planes (LP: #1978820) - net/mlx5e: TC NIC mode, fix tc chains miss table * Hairpin traffic does not work with centralized NAT gw (LP: #1967856) - net: openvswitch: fix misuse of the cached connection on tuple changes * alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines (LP: #1980700) - ASoC: amd: Add driver data to acp6x machine driver - ASoC: amd: Add support for enabling DMIC on acp6x via _DSD * AMD ACP 6.x DMIC Supports (LP: #1949245) - ASoC: amd: add Yellow Carp ACP6x IP register header - ASoC: amd: add Yellow Carp ACP PCI driver - ASoC: amd: add acp6x init/de-init functions - ASoC: amd: add platform devices for acp6x pdm driver and dmic driver - ASoC: amd: add acp6x pdm platform driver - ASoC: amd: add acp6x irq handler - ASoC: amd: add acp6x pdm driver dma ops - ASoC: amd: add acp6x pci driver pm ops - ASoC: amd: add acp6x pdm driver pm ops - ASoC: amd: enable Yellow carp acp6x drivers build - ASoC: amd: create platform device for acp6x machine driver - ASoC: amd: add YC machine driver using dmic - ASoC: amd: enable Yellow Carp platform machine driver build - ASoC: amd: fix uninitialized variable in snd_acp6x_probe() - [Config] Enable AMD ACP 6 DMIC Support * [UBUNTU 20.04] Include patches to avoid self-detected stall with Secure Execution (LP: #1979296) - KVM: s390: pv: add macros for UVC CC values - KVM: s390: pv: avoid stalls when making pages secure * [22.04 FEAT] KVM: Attestation support for Secure Execution (crypto) (LP: #1959973) - drivers/s390/char: Add Ultravisor io device - s390/uv_uapi: depend on CONFIG_S390 - [Config] CONFIG_S390_UV_UAPI=y for s390x * CVE-2022-1679 - SAUCE: ath9k: fix use-after-free in ath9k_hif_usb_rx_cb * CVE-2022-28893 - SUNRPC: Ensure we flush any closed sockets before xs_xprt_free() - SUNRPC: Don't leak sockets in xs_local_connect() * CVE-2022-34918 - netfilter: nf_tables: stricter validation of element data * CVE-2022-1652 - floppy: use a statically allocated error counter -- Stefan Bader Tue, 12 Jul 2022 10:51:03 +0200 ** Changed in: linux (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1652 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1679 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-28893 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-34918 -- 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/1949245 Title: AMD ACP 6.x DMIC Supports Status in HWE Next: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] AMD's Yellow carp platforms will have an updated ACP IP block (ACP 6.x) which will not work with existing ACP drivers. [Fix] Backport the new driver that is now in linux-next (to be in 5.16) [Test] This is requested by AMD. [Where problems could occur] Low risk. This is a stand-alone driver that does not
[Kernel-packages] [Bug 1959973] Re: [22.04 FEAT] KVM: Attestation support for Secure Execution (crypto)
This bug was fixed in the package linux - 5.15.0-43.46 --- linux (5.15.0-43.46) jammy; urgency=medium * jammy/linux: 5.15.0-43.46 -proposed tracker (LP: #1981243) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.07.11) * nbd: requests can become stuck when disconnecting from server with qemu-nbd (LP: #1896350) - nbd: don't handle response without a corresponding request message - nbd: make sure request completion won't concurrent - nbd: don't clear 'NBD_CMD_INFLIGHT' flag if request is not completed - nbd: fix io hung while disconnecting device * Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events (LP: #1965241) - PCI/portdrv: Rename pm_iter() to pcie_port_device_iter() - PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset - [Config] Enable config option CONFIG_PCIE_EDR * [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 (LP: #1948626) - nvme: add CNTRLTYPE definitions for 'identify controller' - nvme: send uevent on connection up - nvme: expose cntrltype and dctype through sysfs * [UBUNTU 22.04] Kernel oops while removing device from cio_ignore list (LP: #1980951) - s390/cio: derive cdev information only for IO-subchannels * Jammy Charmed OpenStack deployment fails over connectivity issues when using converged OVS bridge for control and data planes (LP: #1978820) - net/mlx5e: TC NIC mode, fix tc chains miss table * Hairpin traffic does not work with centralized NAT gw (LP: #1967856) - net: openvswitch: fix misuse of the cached connection on tuple changes * alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines (LP: #1980700) - ASoC: amd: Add driver data to acp6x machine driver - ASoC: amd: Add support for enabling DMIC on acp6x via _DSD * AMD ACP 6.x DMIC Supports (LP: #1949245) - ASoC: amd: add Yellow Carp ACP6x IP register header - ASoC: amd: add Yellow Carp ACP PCI driver - ASoC: amd: add acp6x init/de-init functions - ASoC: amd: add platform devices for acp6x pdm driver and dmic driver - ASoC: amd: add acp6x pdm platform driver - ASoC: amd: add acp6x irq handler - ASoC: amd: add acp6x pdm driver dma ops - ASoC: amd: add acp6x pci driver pm ops - ASoC: amd: add acp6x pdm driver pm ops - ASoC: amd: enable Yellow carp acp6x drivers build - ASoC: amd: create platform device for acp6x machine driver - ASoC: amd: add YC machine driver using dmic - ASoC: amd: enable Yellow Carp platform machine driver build - ASoC: amd: fix uninitialized variable in snd_acp6x_probe() - [Config] Enable AMD ACP 6 DMIC Support * [UBUNTU 20.04] Include patches to avoid self-detected stall with Secure Execution (LP: #1979296) - KVM: s390: pv: add macros for UVC CC values - KVM: s390: pv: avoid stalls when making pages secure * [22.04 FEAT] KVM: Attestation support for Secure Execution (crypto) (LP: #1959973) - drivers/s390/char: Add Ultravisor io device - s390/uv_uapi: depend on CONFIG_S390 - [Config] CONFIG_S390_UV_UAPI=y for s390x * CVE-2022-1679 - SAUCE: ath9k: fix use-after-free in ath9k_hif_usb_rx_cb * CVE-2022-28893 - SUNRPC: Ensure we flush any closed sockets before xs_xprt_free() - SUNRPC: Don't leak sockets in xs_local_connect() * CVE-2022-34918 - netfilter: nf_tables: stricter validation of element data * CVE-2022-1652 - floppy: use a statically allocated error counter -- Stefan Bader Tue, 12 Jul 2022 10:51:03 +0200 ** Changed in: linux (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1652 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1679 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-28893 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-34918 -- 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/1959973 Title: [22.04 FEAT] KVM: Attestation support for Secure Execution (crypto) Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: == [Impact] * This is a hardware enablement SRU in support of IBM z15 and LinuxONE III (FC 115) secure execution feature. * It adds a misc character device to expose some Ultravisor functions to userspace. * The device is only available if the (optional) Ultravisor Facility (158) is present in the system. * Two Ultravisor calls are supported: - Query Ultravisor Information (QUI) and - Receive Attestation Measurement (Attest[ation]) * This is in
[Kernel-packages] [Bug 1965241] Re: Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events
This bug was fixed in the package linux - 5.15.0-43.46 --- linux (5.15.0-43.46) jammy; urgency=medium * jammy/linux: 5.15.0-43.46 -proposed tracker (LP: #1981243) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.07.11) * nbd: requests can become stuck when disconnecting from server with qemu-nbd (LP: #1896350) - nbd: don't handle response without a corresponding request message - nbd: make sure request completion won't concurrent - nbd: don't clear 'NBD_CMD_INFLIGHT' flag if request is not completed - nbd: fix io hung while disconnecting device * Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events (LP: #1965241) - PCI/portdrv: Rename pm_iter() to pcie_port_device_iter() - PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset - [Config] Enable config option CONFIG_PCIE_EDR * [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 (LP: #1948626) - nvme: add CNTRLTYPE definitions for 'identify controller' - nvme: send uevent on connection up - nvme: expose cntrltype and dctype through sysfs * [UBUNTU 22.04] Kernel oops while removing device from cio_ignore list (LP: #1980951) - s390/cio: derive cdev information only for IO-subchannels * Jammy Charmed OpenStack deployment fails over connectivity issues when using converged OVS bridge for control and data planes (LP: #1978820) - net/mlx5e: TC NIC mode, fix tc chains miss table * Hairpin traffic does not work with centralized NAT gw (LP: #1967856) - net: openvswitch: fix misuse of the cached connection on tuple changes * alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines (LP: #1980700) - ASoC: amd: Add driver data to acp6x machine driver - ASoC: amd: Add support for enabling DMIC on acp6x via _DSD * AMD ACP 6.x DMIC Supports (LP: #1949245) - ASoC: amd: add Yellow Carp ACP6x IP register header - ASoC: amd: add Yellow Carp ACP PCI driver - ASoC: amd: add acp6x init/de-init functions - ASoC: amd: add platform devices for acp6x pdm driver and dmic driver - ASoC: amd: add acp6x pdm platform driver - ASoC: amd: add acp6x irq handler - ASoC: amd: add acp6x pdm driver dma ops - ASoC: amd: add acp6x pci driver pm ops - ASoC: amd: add acp6x pdm driver pm ops - ASoC: amd: enable Yellow carp acp6x drivers build - ASoC: amd: create platform device for acp6x machine driver - ASoC: amd: add YC machine driver using dmic - ASoC: amd: enable Yellow Carp platform machine driver build - ASoC: amd: fix uninitialized variable in snd_acp6x_probe() - [Config] Enable AMD ACP 6 DMIC Support * [UBUNTU 20.04] Include patches to avoid self-detected stall with Secure Execution (LP: #1979296) - KVM: s390: pv: add macros for UVC CC values - KVM: s390: pv: avoid stalls when making pages secure * [22.04 FEAT] KVM: Attestation support for Secure Execution (crypto) (LP: #1959973) - drivers/s390/char: Add Ultravisor io device - s390/uv_uapi: depend on CONFIG_S390 - [Config] CONFIG_S390_UV_UAPI=y for s390x * CVE-2022-1679 - SAUCE: ath9k: fix use-after-free in ath9k_hif_usb_rx_cb * CVE-2022-28893 - SUNRPC: Ensure we flush any closed sockets before xs_xprt_free() - SUNRPC: Don't leak sockets in xs_local_connect() * CVE-2022-34918 - netfilter: nf_tables: stricter validation of element data * CVE-2022-1652 - floppy: use a statically allocated error counter -- Stefan Bader Tue, 12 Jul 2022 10:51:03 +0200 ** Changed in: linux (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1652 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1679 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-28893 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-34918 -- 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/1965241 Title: Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events Status in dellserver: New Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: [Impact] Recovery from DownPort Containment events fail and the NVMe endpoint is not accessible in some scenarios. [Fix] These are some of the DPC fixes which help in handling some of the failure cases of DownPort Containment events. Upstream kernel patches to be included into Ubuntu 22.04 and into Ubuntu 20.04.5: Already in Jammy as of Ubuntu-5.15.0-1.1 PCI/portdrv: Enable Bandwidth Notification only if port supports it
[Kernel-packages] [Bug 1978820] Re: Jammy Charmed OpenStack deployment fails over connectivity issues when using converged OVS bridge for control and data planes
This bug was fixed in the package linux - 5.15.0-43.46 --- linux (5.15.0-43.46) jammy; urgency=medium * jammy/linux: 5.15.0-43.46 -proposed tracker (LP: #1981243) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.07.11) * nbd: requests can become stuck when disconnecting from server with qemu-nbd (LP: #1896350) - nbd: don't handle response without a corresponding request message - nbd: make sure request completion won't concurrent - nbd: don't clear 'NBD_CMD_INFLIGHT' flag if request is not completed - nbd: fix io hung while disconnecting device * Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events (LP: #1965241) - PCI/portdrv: Rename pm_iter() to pcie_port_device_iter() - PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset - [Config] Enable config option CONFIG_PCIE_EDR * [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 (LP: #1948626) - nvme: add CNTRLTYPE definitions for 'identify controller' - nvme: send uevent on connection up - nvme: expose cntrltype and dctype through sysfs * [UBUNTU 22.04] Kernel oops while removing device from cio_ignore list (LP: #1980951) - s390/cio: derive cdev information only for IO-subchannels * Jammy Charmed OpenStack deployment fails over connectivity issues when using converged OVS bridge for control and data planes (LP: #1978820) - net/mlx5e: TC NIC mode, fix tc chains miss table * Hairpin traffic does not work with centralized NAT gw (LP: #1967856) - net: openvswitch: fix misuse of the cached connection on tuple changes * alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines (LP: #1980700) - ASoC: amd: Add driver data to acp6x machine driver - ASoC: amd: Add support for enabling DMIC on acp6x via _DSD * AMD ACP 6.x DMIC Supports (LP: #1949245) - ASoC: amd: add Yellow Carp ACP6x IP register header - ASoC: amd: add Yellow Carp ACP PCI driver - ASoC: amd: add acp6x init/de-init functions - ASoC: amd: add platform devices for acp6x pdm driver and dmic driver - ASoC: amd: add acp6x pdm platform driver - ASoC: amd: add acp6x irq handler - ASoC: amd: add acp6x pdm driver dma ops - ASoC: amd: add acp6x pci driver pm ops - ASoC: amd: add acp6x pdm driver pm ops - ASoC: amd: enable Yellow carp acp6x drivers build - ASoC: amd: create platform device for acp6x machine driver - ASoC: amd: add YC machine driver using dmic - ASoC: amd: enable Yellow Carp platform machine driver build - ASoC: amd: fix uninitialized variable in snd_acp6x_probe() - [Config] Enable AMD ACP 6 DMIC Support * [UBUNTU 20.04] Include patches to avoid self-detected stall with Secure Execution (LP: #1979296) - KVM: s390: pv: add macros for UVC CC values - KVM: s390: pv: avoid stalls when making pages secure * [22.04 FEAT] KVM: Attestation support for Secure Execution (crypto) (LP: #1959973) - drivers/s390/char: Add Ultravisor io device - s390/uv_uapi: depend on CONFIG_S390 - [Config] CONFIG_S390_UV_UAPI=y for s390x * CVE-2022-1679 - SAUCE: ath9k: fix use-after-free in ath9k_hif_usb_rx_cb * CVE-2022-28893 - SUNRPC: Ensure we flush any closed sockets before xs_xprt_free() - SUNRPC: Don't leak sockets in xs_local_connect() * CVE-2022-34918 - netfilter: nf_tables: stricter validation of element data * CVE-2022-1652 - floppy: use a statically allocated error counter -- Stefan Bader Tue, 12 Jul 2022 10:51:03 +0200 ** Changed in: linux (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1652 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1679 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-28893 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-34918 -- 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/1978820 Title: Jammy Charmed OpenStack deployment fails over connectivity issues when using converged OVS bridge for control and data planes Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Released Bug description: Platform: OpenStack Yoga, Ubuntu 22.04 Jammy, Kernel 5.15.0-37-generic Charmed Openstack deployment with HW Offload over Jammy series will look ok until Vault initialization phase, then after initializing Vault all DB-related apps will end up in block/error state over "Failed to connect to MYSQL". Connectivity testing between DB containers located on different nodes will show there is unexplained sporadic packet loss preventing proper communication between the DB related apps. This will happen when the
[Kernel-packages] [Bug 1967856] Re: Hairpin traffic does not work with centralized NAT gw
This bug was fixed in the package linux - 5.15.0-43.46 --- linux (5.15.0-43.46) jammy; urgency=medium * jammy/linux: 5.15.0-43.46 -proposed tracker (LP: #1981243) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.07.11) * nbd: requests can become stuck when disconnecting from server with qemu-nbd (LP: #1896350) - nbd: don't handle response without a corresponding request message - nbd: make sure request completion won't concurrent - nbd: don't clear 'NBD_CMD_INFLIGHT' flag if request is not completed - nbd: fix io hung while disconnecting device * Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events (LP: #1965241) - PCI/portdrv: Rename pm_iter() to pcie_port_device_iter() - PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset - [Config] Enable config option CONFIG_PCIE_EDR * [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 (LP: #1948626) - nvme: add CNTRLTYPE definitions for 'identify controller' - nvme: send uevent on connection up - nvme: expose cntrltype and dctype through sysfs * [UBUNTU 22.04] Kernel oops while removing device from cio_ignore list (LP: #1980951) - s390/cio: derive cdev information only for IO-subchannels * Jammy Charmed OpenStack deployment fails over connectivity issues when using converged OVS bridge for control and data planes (LP: #1978820) - net/mlx5e: TC NIC mode, fix tc chains miss table * Hairpin traffic does not work with centralized NAT gw (LP: #1967856) - net: openvswitch: fix misuse of the cached connection on tuple changes * alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines (LP: #1980700) - ASoC: amd: Add driver data to acp6x machine driver - ASoC: amd: Add support for enabling DMIC on acp6x via _DSD * AMD ACP 6.x DMIC Supports (LP: #1949245) - ASoC: amd: add Yellow Carp ACP6x IP register header - ASoC: amd: add Yellow Carp ACP PCI driver - ASoC: amd: add acp6x init/de-init functions - ASoC: amd: add platform devices for acp6x pdm driver and dmic driver - ASoC: amd: add acp6x pdm platform driver - ASoC: amd: add acp6x irq handler - ASoC: amd: add acp6x pdm driver dma ops - ASoC: amd: add acp6x pci driver pm ops - ASoC: amd: add acp6x pdm driver pm ops - ASoC: amd: enable Yellow carp acp6x drivers build - ASoC: amd: create platform device for acp6x machine driver - ASoC: amd: add YC machine driver using dmic - ASoC: amd: enable Yellow Carp platform machine driver build - ASoC: amd: fix uninitialized variable in snd_acp6x_probe() - [Config] Enable AMD ACP 6 DMIC Support * [UBUNTU 20.04] Include patches to avoid self-detected stall with Secure Execution (LP: #1979296) - KVM: s390: pv: add macros for UVC CC values - KVM: s390: pv: avoid stalls when making pages secure * [22.04 FEAT] KVM: Attestation support for Secure Execution (crypto) (LP: #1959973) - drivers/s390/char: Add Ultravisor io device - s390/uv_uapi: depend on CONFIG_S390 - [Config] CONFIG_S390_UV_UAPI=y for s390x * CVE-2022-1679 - SAUCE: ath9k: fix use-after-free in ath9k_hif_usb_rx_cb * CVE-2022-28893 - SUNRPC: Ensure we flush any closed sockets before xs_xprt_free() - SUNRPC: Don't leak sockets in xs_local_connect() * CVE-2022-34918 - netfilter: nf_tables: stricter validation of element data * CVE-2022-1652 - floppy: use a statically allocated error counter -- Stefan Bader Tue, 12 Jul 2022 10:51:03 +0200 ** Changed in: linux (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1652 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1679 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-28893 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-34918 -- 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/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Invalid Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Impish: Won't Fix Status in openvswitch source package in Impish: New Status in ovn source package in Impish: New Status in linux source package in Jammy: Fix Released Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Invalid Status in openvswitch source package in Kinetic:
[Kernel-packages] [Bug 1979296] Re: [UBUNTU 20.04] Include patches to avoid self-detected stall with Secure Execution
This bug was fixed in the package linux - 5.15.0-43.46 --- linux (5.15.0-43.46) jammy; urgency=medium * jammy/linux: 5.15.0-43.46 -proposed tracker (LP: #1981243) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.07.11) * nbd: requests can become stuck when disconnecting from server with qemu-nbd (LP: #1896350) - nbd: don't handle response without a corresponding request message - nbd: make sure request completion won't concurrent - nbd: don't clear 'NBD_CMD_INFLIGHT' flag if request is not completed - nbd: fix io hung while disconnecting device * Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events (LP: #1965241) - PCI/portdrv: Rename pm_iter() to pcie_port_device_iter() - PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset - [Config] Enable config option CONFIG_PCIE_EDR * [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 (LP: #1948626) - nvme: add CNTRLTYPE definitions for 'identify controller' - nvme: send uevent on connection up - nvme: expose cntrltype and dctype through sysfs * [UBUNTU 22.04] Kernel oops while removing device from cio_ignore list (LP: #1980951) - s390/cio: derive cdev information only for IO-subchannels * Jammy Charmed OpenStack deployment fails over connectivity issues when using converged OVS bridge for control and data planes (LP: #1978820) - net/mlx5e: TC NIC mode, fix tc chains miss table * Hairpin traffic does not work with centralized NAT gw (LP: #1967856) - net: openvswitch: fix misuse of the cached connection on tuple changes * alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines (LP: #1980700) - ASoC: amd: Add driver data to acp6x machine driver - ASoC: amd: Add support for enabling DMIC on acp6x via _DSD * AMD ACP 6.x DMIC Supports (LP: #1949245) - ASoC: amd: add Yellow Carp ACP6x IP register header - ASoC: amd: add Yellow Carp ACP PCI driver - ASoC: amd: add acp6x init/de-init functions - ASoC: amd: add platform devices for acp6x pdm driver and dmic driver - ASoC: amd: add acp6x pdm platform driver - ASoC: amd: add acp6x irq handler - ASoC: amd: add acp6x pdm driver dma ops - ASoC: amd: add acp6x pci driver pm ops - ASoC: amd: add acp6x pdm driver pm ops - ASoC: amd: enable Yellow carp acp6x drivers build - ASoC: amd: create platform device for acp6x machine driver - ASoC: amd: add YC machine driver using dmic - ASoC: amd: enable Yellow Carp platform machine driver build - ASoC: amd: fix uninitialized variable in snd_acp6x_probe() - [Config] Enable AMD ACP 6 DMIC Support * [UBUNTU 20.04] Include patches to avoid self-detected stall with Secure Execution (LP: #1979296) - KVM: s390: pv: add macros for UVC CC values - KVM: s390: pv: avoid stalls when making pages secure * [22.04 FEAT] KVM: Attestation support for Secure Execution (crypto) (LP: #1959973) - drivers/s390/char: Add Ultravisor io device - s390/uv_uapi: depend on CONFIG_S390 - [Config] CONFIG_S390_UV_UAPI=y for s390x * CVE-2022-1679 - SAUCE: ath9k: fix use-after-free in ath9k_hif_usb_rx_cb * CVE-2022-28893 - SUNRPC: Ensure we flush any closed sockets before xs_xprt_free() - SUNRPC: Don't leak sockets in xs_local_connect() * CVE-2022-34918 - netfilter: nf_tables: stricter validation of element data * CVE-2022-1652 - floppy: use a statically allocated error counter -- Stefan Bader Tue, 12 Jul 2022 10:51:03 +0200 ** Changed in: linux (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1652 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1679 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-28893 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-34918 -- 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/1979296 Title: [UBUNTU 20.04] Include patches to avoid self-detected stall with Secure Execution Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: == [Impact] * On IBM Z secure execution environments under heavy load (means with over-committed resources - KVM guests) rcu_sched self-detected stalls can occur, which lead to LPAR crashes. [Fix] * 57c5df13eca4 57c5df13eca4017ed28f9375dc1d246ec0f54217 "KVM: s390: pv: add macros for UVC CC values" * 1e2aa46de526 1e2aa46de526a5adafe580bca4c25856bb06f09e "KVM: s390: pv: avoid stalls for
[Kernel-packages] [Bug 1980590] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1980590/+attachment/5605742/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980590 Title: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress Status in linux package in Ubuntu: Confirmed Bug description: an android app is sending big UDP datagrams, this generates IPv4 fragments this IPv4 fragments can not be controlled in firewall nftables family netdev hook ingress. platform: Ubuntu 22.04LTS, latest patches installed I documented 2 screenshots fragment1.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, frag-offset=0, total=1500 fragment2.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, frag-offset=1480, total=413 at the bottom of the screenshots is "/usr/sbin/nft monitor trace" family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data total=0x765=1893, ID=0x2466, glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops the nftables TRACE shows an already processed bigger ipv4 packet. there is a race condition! the ipv4 processing has to WAIT for all the rules in family "netdev" hook "ingress" I cannot control ether type 0x800 completely in family "netdev" hook "ingress" this is a security vulnerability! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1324 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/06/2017 dmi.bios.release: 15.101 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.65 dmi.board.name: 1618 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.78 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560p dmi.product.sku: LG731EA#ABD dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980590] Re: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress
and here is the catch of today ** Attachment added: "ether_type_0x800_miss_2022-07-28 08-28-24.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980590/+attachment/5605746/+files/ether_type_0x800_miss_2022-07-28%2008-28-24.png -- 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/1980590 Title: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress Status in linux package in Ubuntu: Confirmed Bug description: an android app is sending big UDP datagrams, this generates IPv4 fragments this IPv4 fragments can not be controlled in firewall nftables family netdev hook ingress. platform: Ubuntu 22.04LTS, latest patches installed I documented 2 screenshots fragment1.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, frag-offset=0, total=1500 fragment2.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, frag-offset=1480, total=413 at the bottom of the screenshots is "/usr/sbin/nft monitor trace" family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data total=0x765=1893, ID=0x2466, glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops the nftables TRACE shows an already processed bigger ipv4 packet. there is a race condition! the ipv4 processing has to WAIT for all the rules in family "netdev" hook "ingress" I cannot control ether type 0x800 completely in family "netdev" hook "ingress" this is a security vulnerability! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1324 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/06/2017 dmi.bios.release: 15.101 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.65 dmi.board.name: 1618 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.78 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560p dmi.product.sku: LG731EA#ABD dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980590] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1980590/+attachment/5605743/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980590 Title: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress Status in linux package in Ubuntu: Confirmed Bug description: an android app is sending big UDP datagrams, this generates IPv4 fragments this IPv4 fragments can not be controlled in firewall nftables family netdev hook ingress. platform: Ubuntu 22.04LTS, latest patches installed I documented 2 screenshots fragment1.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, frag-offset=0, total=1500 fragment2.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, frag-offset=1480, total=413 at the bottom of the screenshots is "/usr/sbin/nft monitor trace" family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data total=0x765=1893, ID=0x2466, glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops the nftables TRACE shows an already processed bigger ipv4 packet. there is a race condition! the ipv4 processing has to WAIT for all the rules in family "netdev" hook "ingress" I cannot control ether type 0x800 completely in family "netdev" hook "ingress" this is a security vulnerability! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1324 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/06/2017 dmi.bios.release: 15.101 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.65 dmi.board.name: 1618 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.78 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560p dmi.product.sku: LG731EA#ABD dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980590] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1980590/+attachment/5605741/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980590 Title: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress Status in linux package in Ubuntu: Confirmed Bug description: an android app is sending big UDP datagrams, this generates IPv4 fragments this IPv4 fragments can not be controlled in firewall nftables family netdev hook ingress. platform: Ubuntu 22.04LTS, latest patches installed I documented 2 screenshots fragment1.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, frag-offset=0, total=1500 fragment2.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, frag-offset=1480, total=413 at the bottom of the screenshots is "/usr/sbin/nft monitor trace" family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data total=0x765=1893, ID=0x2466, glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops the nftables TRACE shows an already processed bigger ipv4 packet. there is a race condition! the ipv4 processing has to WAIT for all the rules in family "netdev" hook "ingress" I cannot control ether type 0x800 completely in family "netdev" hook "ingress" this is a security vulnerability! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1324 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/06/2017 dmi.bios.release: 15.101 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.65 dmi.board.name: 1618 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.78 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560p dmi.product.sku: LG731EA#ABD dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980590] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1980590/+attachment/5605740/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980590 Title: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress Status in linux package in Ubuntu: Confirmed Bug description: an android app is sending big UDP datagrams, this generates IPv4 fragments this IPv4 fragments can not be controlled in firewall nftables family netdev hook ingress. platform: Ubuntu 22.04LTS, latest patches installed I documented 2 screenshots fragment1.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, frag-offset=0, total=1500 fragment2.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, frag-offset=1480, total=413 at the bottom of the screenshots is "/usr/sbin/nft monitor trace" family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data total=0x765=1893, ID=0x2466, glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops the nftables TRACE shows an already processed bigger ipv4 packet. there is a race condition! the ipv4 processing has to WAIT for all the rules in family "netdev" hook "ingress" I cannot control ether type 0x800 completely in family "netdev" hook "ingress" this is a security vulnerability! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1324 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/06/2017 dmi.bios.release: 15.101 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.65 dmi.board.name: 1618 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.78 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560p dmi.product.sku: LG731EA#ABD dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980590] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1980590/+attachment/5605738/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980590 Title: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress Status in linux package in Ubuntu: Confirmed Bug description: an android app is sending big UDP datagrams, this generates IPv4 fragments this IPv4 fragments can not be controlled in firewall nftables family netdev hook ingress. platform: Ubuntu 22.04LTS, latest patches installed I documented 2 screenshots fragment1.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, frag-offset=0, total=1500 fragment2.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, frag-offset=1480, total=413 at the bottom of the screenshots is "/usr/sbin/nft monitor trace" family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data total=0x765=1893, ID=0x2466, glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops the nftables TRACE shows an already processed bigger ipv4 packet. there is a race condition! the ipv4 processing has to WAIT for all the rules in family "netdev" hook "ingress" I cannot control ether type 0x800 completely in family "netdev" hook "ingress" this is a security vulnerability! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1324 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/06/2017 dmi.bios.release: 15.101 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.65 dmi.board.name: 1618 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.78 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560p dmi.product.sku: LG731EA#ABD dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980590] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1980590/+attachment/5605739/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980590 Title: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress Status in linux package in Ubuntu: Confirmed Bug description: an android app is sending big UDP datagrams, this generates IPv4 fragments this IPv4 fragments can not be controlled in firewall nftables family netdev hook ingress. platform: Ubuntu 22.04LTS, latest patches installed I documented 2 screenshots fragment1.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, frag-offset=0, total=1500 fragment2.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, frag-offset=1480, total=413 at the bottom of the screenshots is "/usr/sbin/nft monitor trace" family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data total=0x765=1893, ID=0x2466, glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops the nftables TRACE shows an already processed bigger ipv4 packet. there is a race condition! the ipv4 processing has to WAIT for all the rules in family "netdev" hook "ingress" I cannot control ether type 0x800 completely in family "netdev" hook "ingress" this is a security vulnerability! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1324 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/06/2017 dmi.bios.release: 15.101 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.65 dmi.board.name: 1618 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.78 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560p dmi.product.sku: LG731EA#ABD dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980590] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1980590/+attachment/5605737/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980590 Title: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress Status in linux package in Ubuntu: Confirmed Bug description: an android app is sending big UDP datagrams, this generates IPv4 fragments this IPv4 fragments can not be controlled in firewall nftables family netdev hook ingress. platform: Ubuntu 22.04LTS, latest patches installed I documented 2 screenshots fragment1.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, frag-offset=0, total=1500 fragment2.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, frag-offset=1480, total=413 at the bottom of the screenshots is "/usr/sbin/nft monitor trace" family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data total=0x765=1893, ID=0x2466, glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops the nftables TRACE shows an already processed bigger ipv4 packet. there is a race condition! the ipv4 processing has to WAIT for all the rules in family "netdev" hook "ingress" I cannot control ether type 0x800 completely in family "netdev" hook "ingress" this is a security vulnerability! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1324 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/06/2017 dmi.bios.release: 15.101 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.65 dmi.board.name: 1618 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.78 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560p dmi.product.sku: LG731EA#ABD dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980590] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1980590/+attachment/5605736/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980590 Title: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress Status in linux package in Ubuntu: Confirmed Bug description: an android app is sending big UDP datagrams, this generates IPv4 fragments this IPv4 fragments can not be controlled in firewall nftables family netdev hook ingress. platform: Ubuntu 22.04LTS, latest patches installed I documented 2 screenshots fragment1.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, frag-offset=0, total=1500 fragment2.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, frag-offset=1480, total=413 at the bottom of the screenshots is "/usr/sbin/nft monitor trace" family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data total=0x765=1893, ID=0x2466, glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops the nftables TRACE shows an already processed bigger ipv4 packet. there is a race condition! the ipv4 processing has to WAIT for all the rules in family "netdev" hook "ingress" I cannot control ether type 0x800 completely in family "netdev" hook "ingress" this is a security vulnerability! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1324 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/06/2017 dmi.bios.release: 15.101 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.65 dmi.board.name: 1618 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.78 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560p dmi.product.sku: LG731EA#ABD dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980590] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1980590/+attachment/5605734/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980590 Title: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress Status in linux package in Ubuntu: Confirmed Bug description: an android app is sending big UDP datagrams, this generates IPv4 fragments this IPv4 fragments can not be controlled in firewall nftables family netdev hook ingress. platform: Ubuntu 22.04LTS, latest patches installed I documented 2 screenshots fragment1.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, frag-offset=0, total=1500 fragment2.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, frag-offset=1480, total=413 at the bottom of the screenshots is "/usr/sbin/nft monitor trace" family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data total=0x765=1893, ID=0x2466, glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops the nftables TRACE shows an already processed bigger ipv4 packet. there is a race condition! the ipv4 processing has to WAIT for all the rules in family "netdev" hook "ingress" I cannot control ether type 0x800 completely in family "netdev" hook "ingress" this is a security vulnerability! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1324 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/06/2017 dmi.bios.release: 15.101 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.65 dmi.board.name: 1618 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.78 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560p dmi.product.sku: LG731EA#ABD dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980590] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1980590/+attachment/5605735/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980590 Title: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress Status in linux package in Ubuntu: Confirmed Bug description: an android app is sending big UDP datagrams, this generates IPv4 fragments this IPv4 fragments can not be controlled in firewall nftables family netdev hook ingress. platform: Ubuntu 22.04LTS, latest patches installed I documented 2 screenshots fragment1.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, frag-offset=0, total=1500 fragment2.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, frag-offset=1480, total=413 at the bottom of the screenshots is "/usr/sbin/nft monitor trace" family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data total=0x765=1893, ID=0x2466, glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops the nftables TRACE shows an already processed bigger ipv4 packet. there is a race condition! the ipv4 processing has to WAIT for all the rules in family "netdev" hook "ingress" I cannot control ether type 0x800 completely in family "netdev" hook "ingress" this is a security vulnerability! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1324 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/06/2017 dmi.bios.release: 15.101 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.65 dmi.board.name: 1618 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.78 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560p dmi.product.sku: LG731EA#ABD dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980590] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1980590/+attachment/5605733/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980590 Title: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress Status in linux package in Ubuntu: Confirmed Bug description: an android app is sending big UDP datagrams, this generates IPv4 fragments this IPv4 fragments can not be controlled in firewall nftables family netdev hook ingress. platform: Ubuntu 22.04LTS, latest patches installed I documented 2 screenshots fragment1.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, frag-offset=0, total=1500 fragment2.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, frag-offset=1480, total=413 at the bottom of the screenshots is "/usr/sbin/nft monitor trace" family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data total=0x765=1893, ID=0x2466, glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops the nftables TRACE shows an already processed bigger ipv4 packet. there is a race condition! the ipv4 processing has to WAIT for all the rules in family "netdev" hook "ingress" I cannot control ether type 0x800 completely in family "netdev" hook "ingress" this is a security vulnerability! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1324 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/06/2017 dmi.bios.release: 15.101 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.65 dmi.board.name: 1618 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.78 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560p dmi.product.sku: LG731EA#ABD dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980590] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1980590/+attachment/5605745/+files/acpidump.txt ** 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/1980590 Title: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress Status in linux package in Ubuntu: Confirmed Bug description: an android app is sending big UDP datagrams, this generates IPv4 fragments this IPv4 fragments can not be controlled in firewall nftables family netdev hook ingress. platform: Ubuntu 22.04LTS, latest patches installed I documented 2 screenshots fragment1.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, frag-offset=0, total=1500 fragment2.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, frag-offset=1480, total=413 at the bottom of the screenshots is "/usr/sbin/nft monitor trace" family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data total=0x765=1893, ID=0x2466, glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops the nftables TRACE shows an already processed bigger ipv4 packet. there is a race condition! the ipv4 processing has to WAIT for all the rules in family "netdev" hook "ingress" I cannot control ether type 0x800 completely in family "netdev" hook "ingress" this is a security vulnerability! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1324 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/06/2017 dmi.bios.release: 15.101 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.65 dmi.board.name: 1618 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.78 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560p dmi.product.sku: LG731EA#ABD dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980590] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1980590/+attachment/5605744/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980590 Title: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress Status in linux package in Ubuntu: Confirmed Bug description: an android app is sending big UDP datagrams, this generates IPv4 fragments this IPv4 fragments can not be controlled in firewall nftables family netdev hook ingress. platform: Ubuntu 22.04LTS, latest patches installed I documented 2 screenshots fragment1.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, frag-offset=0, total=1500 fragment2.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, frag-offset=1480, total=413 at the bottom of the screenshots is "/usr/sbin/nft monitor trace" family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data total=0x765=1893, ID=0x2466, glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops the nftables TRACE shows an already processed bigger ipv4 packet. there is a race condition! the ipv4 processing has to WAIT for all the rules in family "netdev" hook "ingress" I cannot control ether type 0x800 completely in family "netdev" hook "ingress" this is a security vulnerability! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1324 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/06/2017 dmi.bios.release: 15.101 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.65 dmi.board.name: 1618 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.78 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560p dmi.product.sku: LG731EA#ABD dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980590] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1980590/+attachment/5605729/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980590 Title: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress Status in linux package in Ubuntu: Confirmed Bug description: an android app is sending big UDP datagrams, this generates IPv4 fragments this IPv4 fragments can not be controlled in firewall nftables family netdev hook ingress. platform: Ubuntu 22.04LTS, latest patches installed I documented 2 screenshots fragment1.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, frag-offset=0, total=1500 fragment2.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, frag-offset=1480, total=413 at the bottom of the screenshots is "/usr/sbin/nft monitor trace" family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data total=0x765=1893, ID=0x2466, glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops the nftables TRACE shows an already processed bigger ipv4 packet. there is a race condition! the ipv4 processing has to WAIT for all the rules in family "netdev" hook "ingress" I cannot control ether type 0x800 completely in family "netdev" hook "ingress" this is a security vulnerability! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1324 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/06/2017 dmi.bios.release: 15.101 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.65 dmi.board.name: 1618 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.78 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560p dmi.product.sku: LG731EA#ABD dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980590] Re: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress
apport information ** Tags added: apport-collected jammy ** Description changed: an android app is sending big UDP datagrams, this generates IPv4 fragments this IPv4 fragments can not be controlled in firewall nftables family netdev hook ingress. platform: Ubuntu 22.04LTS, latest patches installed I documented 2 screenshots fragment1.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, frag-offset=0, total=1500 fragment2.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, frag-offset=1480, total=413 at the bottom of the screenshots is "/usr/sbin/nft monitor trace" family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data total=0x765=1893, ID=0x2466, glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops the nftables TRACE shows an already processed bigger ipv4 packet. there is a race condition! the ipv4 processing has to WAIT for all the rules in family "netdev" hook "ingress" I cannot control ether type 0x800 completely in family "netdev" hook "ingress" this is a security vulnerability! + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: bernie 1324 F pulseaudio + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-05-31 (58 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) + MachineType: Hewlett-Packard HP EliteBook 8560p + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init + ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.15.0-41-generic N/A + linux-backports-modules-5.15.0-41-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.3 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: yes + Hard blocked: no + Tags: jammy + Uname: Linux 5.15.0-41-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 04/06/2017 + dmi.bios.release: 15.101 + dmi.bios.vendor: Hewlett-Packard + dmi.bios.version: 68SCF Ver. F.65 + dmi.board.name: 1618 + dmi.board.vendor: Hewlett-Packard + dmi.board.version: KBC Version 97.4E + dmi.chassis.type: 10 + dmi.chassis.vendor: Hewlett-Packard + dmi.ec.firmware.release: 151.78 + dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD: + dmi.product.family: 103C_5336AN + dmi.product.name: HP EliteBook 8560p + dmi.product.sku: LG731EA#ABD + dmi.product.version: A0001D02 + dmi.sys.vendor: Hewlett-Packard ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1980590/+attachment/5605728/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980590 Title: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress Status in linux package in Ubuntu: Confirmed Bug description: an android app is sending big UDP datagrams, this generates IPv4 fragments this IPv4 fragments can not be controlled in firewall nftables family netdev hook ingress. platform: Ubuntu 22.04LTS, latest patches installed I documented 2 screenshots fragment1.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, frag-offset=0, total=1500 fragment2.png wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, frag-offset=1480, total=413 at the bottom of the screenshots is "/usr/sbin/nft monitor trace" family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data total=0x765=1893, ID=0x2466, glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops the nftables TRACE shows an already processed bigger ipv4 packet. there is a race condition! the ipv4 processing has to WAIT for all the rules in family "netdev" hook "ingress" I cannot control ether type 0x800 completely in family "netdev" hook "ingress" this is a security vulnerability! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1324 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy
[Kernel-packages] [Bug 1980700] Re: alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1014.15 --- linux-oem-5.17 (5.17.0-1014.15) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1014.15 -proposed tracker (LP: #1981244) * Clear PCI errors left from BIOS (LP: #1981173) - PCI: Clear PCI_STATUS when setting up device * intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes (LP: #1982104) - iommu/vt-d: Fix RID2PASID setup/teardown failure * Failed to resume from S3 blocked by atlantic driver[1d6a:94c0] (LP: #1981950) - net: atlantic: remove deep parameter on suspend/resume functions - net: atlantic: remove aq_nic_deinit() when resume * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines (LP: #1980700) - ASoC: amd: Add support for enabling DMIC on acp6x via _DSD * CVE-2022-34918 - netfilter: nf_tables: stricter validation of element data * System freeze after resuming from suspend due to PCI ASPM settings (LP: #1980829) - PCI/ASPM: Save/restore L1SS Capability for suspend/resume - PCI:ASPM: Remove pcie_aspm_pm_state_change() -- Chia-Lin Kao (AceLan) Tue, 19 Jul 2022 22:07:45 +0800 -- 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/1980700 Title: alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: The fix is already in the upstream kernel v5.19-rc1, no need to send the patches to unstable kernel. And for Jammy kernel, this SRU depends on #1949245, after merging the patchset for #1949245, then could apply this SRU to jammy. [Impact] On the AMD YC platforms, the internal mic can't be detected and there is no internal mic for users to use. [Fix] Backport 2 patches from mainline kernel to fix this problem. [Test] boot the patched kernel on the machine which has updated BIOS, after loging into the desktop, open the gnome-sound-setting, there is internal mic, and could record sound via internal mic. [Where problems could occur] This only impacts intenal mic detection on AMD yc machines, it will check the acpi variable first, if not detected, it will check the acpi dmi table as before, so the regression possibility is very low, and we already tested these patches on a couple of Lenovo YC machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980700] Re: alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines
This bug was fixed in the package linux - 5.15.0-43.46 --- linux (5.15.0-43.46) jammy; urgency=medium * jammy/linux: 5.15.0-43.46 -proposed tracker (LP: #1981243) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.07.11) * nbd: requests can become stuck when disconnecting from server with qemu-nbd (LP: #1896350) - nbd: don't handle response without a corresponding request message - nbd: make sure request completion won't concurrent - nbd: don't clear 'NBD_CMD_INFLIGHT' flag if request is not completed - nbd: fix io hung while disconnecting device * Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events (LP: #1965241) - PCI/portdrv: Rename pm_iter() to pcie_port_device_iter() - PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset - [Config] Enable config option CONFIG_PCIE_EDR * [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 (LP: #1948626) - nvme: add CNTRLTYPE definitions for 'identify controller' - nvme: send uevent on connection up - nvme: expose cntrltype and dctype through sysfs * [UBUNTU 22.04] Kernel oops while removing device from cio_ignore list (LP: #1980951) - s390/cio: derive cdev information only for IO-subchannels * Jammy Charmed OpenStack deployment fails over connectivity issues when using converged OVS bridge for control and data planes (LP: #1978820) - net/mlx5e: TC NIC mode, fix tc chains miss table * Hairpin traffic does not work with centralized NAT gw (LP: #1967856) - net: openvswitch: fix misuse of the cached connection on tuple changes * alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines (LP: #1980700) - ASoC: amd: Add driver data to acp6x machine driver - ASoC: amd: Add support for enabling DMIC on acp6x via _DSD * AMD ACP 6.x DMIC Supports (LP: #1949245) - ASoC: amd: add Yellow Carp ACP6x IP register header - ASoC: amd: add Yellow Carp ACP PCI driver - ASoC: amd: add acp6x init/de-init functions - ASoC: amd: add platform devices for acp6x pdm driver and dmic driver - ASoC: amd: add acp6x pdm platform driver - ASoC: amd: add acp6x irq handler - ASoC: amd: add acp6x pdm driver dma ops - ASoC: amd: add acp6x pci driver pm ops - ASoC: amd: add acp6x pdm driver pm ops - ASoC: amd: enable Yellow carp acp6x drivers build - ASoC: amd: create platform device for acp6x machine driver - ASoC: amd: add YC machine driver using dmic - ASoC: amd: enable Yellow Carp platform machine driver build - ASoC: amd: fix uninitialized variable in snd_acp6x_probe() - [Config] Enable AMD ACP 6 DMIC Support * [UBUNTU 20.04] Include patches to avoid self-detected stall with Secure Execution (LP: #1979296) - KVM: s390: pv: add macros for UVC CC values - KVM: s390: pv: avoid stalls when making pages secure * [22.04 FEAT] KVM: Attestation support for Secure Execution (crypto) (LP: #1959973) - drivers/s390/char: Add Ultravisor io device - s390/uv_uapi: depend on CONFIG_S390 - [Config] CONFIG_S390_UV_UAPI=y for s390x * CVE-2022-1679 - SAUCE: ath9k: fix use-after-free in ath9k_hif_usb_rx_cb * CVE-2022-28893 - SUNRPC: Ensure we flush any closed sockets before xs_xprt_free() - SUNRPC: Don't leak sockets in xs_local_connect() * CVE-2022-34918 - netfilter: nf_tables: stricter validation of element data * CVE-2022-1652 - floppy: use a statically allocated error counter -- Stefan Bader Tue, 12 Jul 2022 10:51:03 +0200 ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1980700 Title: alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: The fix is already in the upstream kernel v5.19-rc1, no need to send the patches to unstable kernel. And for Jammy kernel, this SRU depends on #1949245, after merging the patchset for #1949245, then could apply this SRU to jammy. [Impact] On the AMD YC platforms, the internal mic can't be detected and there is no internal mic for users to use. [Fix] Backport 2 patches from mainline
[Kernel-packages] [Bug 1980700] Re: alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1046.53 --- linux-oem-5.14 (5.14.0-1046.53) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1046.53 -proposed tracker (LP: #1980928) * alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines (LP: #1980700) - ASoC: amd: Add driver data to acp6x machine driver - ASoC: amd: Add support for enabling DMIC on acp6x via _DSD * CVE-2022-34918 - netfilter: nf_tables: stricter validation of element data * System freeze after resuming from suspend due to PCI ASPM settings (LP: #1980829) - PCI/ASPM: Save/restore L1SS Capability for suspend/resume - PCI:ASPM: Remove pcie_aspm_pm_state_change() -- Chia-Lin Kao (AceLan) Wed, 13 Jul 2022 21:02:35 +0800 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-34918 ** Changed in: linux (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1652 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1679 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-28893 -- 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/1980700 Title: alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: The fix is already in the upstream kernel v5.19-rc1, no need to send the patches to unstable kernel. And for Jammy kernel, this SRU depends on #1949245, after merging the patchset for #1949245, then could apply this SRU to jammy. [Impact] On the AMD YC platforms, the internal mic can't be detected and there is no internal mic for users to use. [Fix] Backport 2 patches from mainline kernel to fix this problem. [Test] boot the patched kernel on the machine which has updated BIOS, after loging into the desktop, open the gnome-sound-setting, there is internal mic, and could record sound via internal mic. [Where problems could occur] This only impacts intenal mic detection on AMD yc machines, it will check the acpi variable first, if not detected, it will check the acpi dmi table as before, so the regression possibility is very low, and we already tested these patches on a couple of Lenovo YC machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980829] Re: System freeze after resuming from suspend due to PCI ASPM settings
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1046.53 --- linux-oem-5.14 (5.14.0-1046.53) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1046.53 -proposed tracker (LP: #1980928) * alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines (LP: #1980700) - ASoC: amd: Add driver data to acp6x machine driver - ASoC: amd: Add support for enabling DMIC on acp6x via _DSD * CVE-2022-34918 - netfilter: nf_tables: stricter validation of element data * System freeze after resuming from suspend due to PCI ASPM settings (LP: #1980829) - PCI/ASPM: Save/restore L1SS Capability for suspend/resume - PCI:ASPM: Remove pcie_aspm_pm_state_change() -- Chia-Lin Kao (AceLan) Wed, 13 Jul 2022 21:02:35 +0800 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-34918 ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1980829 Title: System freeze after resuming from suspend due to PCI ASPM settings Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] The 2 commits fix the issue, but still not get accepted yet. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ [Test] Verified on the failed machines and ODM also verified on their side. [Where problems could occur] The 2 patches look pretty safe to me, they try to preserve the ASPM state of devices. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980829] Re: System freeze after resuming from suspend due to PCI ASPM settings
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1014.15 --- linux-oem-5.17 (5.17.0-1014.15) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1014.15 -proposed tracker (LP: #1981244) * Clear PCI errors left from BIOS (LP: #1981173) - PCI: Clear PCI_STATUS when setting up device * intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes (LP: #1982104) - iommu/vt-d: Fix RID2PASID setup/teardown failure * Failed to resume from S3 blocked by atlantic driver[1d6a:94c0] (LP: #1981950) - net: atlantic: remove deep parameter on suspend/resume functions - net: atlantic: remove aq_nic_deinit() when resume * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines (LP: #1980700) - ASoC: amd: Add support for enabling DMIC on acp6x via _DSD * CVE-2022-34918 - netfilter: nf_tables: stricter validation of element data * System freeze after resuming from suspend due to PCI ASPM settings (LP: #1980829) - PCI/ASPM: Save/restore L1SS Capability for suspend/resume - PCI:ASPM: Remove pcie_aspm_pm_state_change() -- Chia-Lin Kao (AceLan) Tue, 19 Jul 2022 22:07:45 +0800 -- 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/1980829 Title: System freeze after resuming from suspend due to PCI ASPM settings Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] The 2 commits fix the issue, but still not get accepted yet. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ [Test] Verified on the failed machines and ODM also verified on their side. [Where problems could occur] The 2 patches look pretty safe to me, they try to preserve the ASPM state of devices. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980951] Re: [UBUNTU 22.04] Kernel oops while removing device from cio_ignore list
This bug was fixed in the package linux - 5.15.0-43.46 --- linux (5.15.0-43.46) jammy; urgency=medium * jammy/linux: 5.15.0-43.46 -proposed tracker (LP: #1981243) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.07.11) * nbd: requests can become stuck when disconnecting from server with qemu-nbd (LP: #1896350) - nbd: don't handle response without a corresponding request message - nbd: make sure request completion won't concurrent - nbd: don't clear 'NBD_CMD_INFLIGHT' flag if request is not completed - nbd: fix io hung while disconnecting device * Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events (LP: #1965241) - PCI/portdrv: Rename pm_iter() to pcie_port_device_iter() - PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset - [Config] Enable config option CONFIG_PCIE_EDR * [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 (LP: #1948626) - nvme: add CNTRLTYPE definitions for 'identify controller' - nvme: send uevent on connection up - nvme: expose cntrltype and dctype through sysfs * [UBUNTU 22.04] Kernel oops while removing device from cio_ignore list (LP: #1980951) - s390/cio: derive cdev information only for IO-subchannels * Jammy Charmed OpenStack deployment fails over connectivity issues when using converged OVS bridge for control and data planes (LP: #1978820) - net/mlx5e: TC NIC mode, fix tc chains miss table * Hairpin traffic does not work with centralized NAT gw (LP: #1967856) - net: openvswitch: fix misuse of the cached connection on tuple changes * alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines (LP: #1980700) - ASoC: amd: Add driver data to acp6x machine driver - ASoC: amd: Add support for enabling DMIC on acp6x via _DSD * AMD ACP 6.x DMIC Supports (LP: #1949245) - ASoC: amd: add Yellow Carp ACP6x IP register header - ASoC: amd: add Yellow Carp ACP PCI driver - ASoC: amd: add acp6x init/de-init functions - ASoC: amd: add platform devices for acp6x pdm driver and dmic driver - ASoC: amd: add acp6x pdm platform driver - ASoC: amd: add acp6x irq handler - ASoC: amd: add acp6x pdm driver dma ops - ASoC: amd: add acp6x pci driver pm ops - ASoC: amd: add acp6x pdm driver pm ops - ASoC: amd: enable Yellow carp acp6x drivers build - ASoC: amd: create platform device for acp6x machine driver - ASoC: amd: add YC machine driver using dmic - ASoC: amd: enable Yellow Carp platform machine driver build - ASoC: amd: fix uninitialized variable in snd_acp6x_probe() - [Config] Enable AMD ACP 6 DMIC Support * [UBUNTU 20.04] Include patches to avoid self-detected stall with Secure Execution (LP: #1979296) - KVM: s390: pv: add macros for UVC CC values - KVM: s390: pv: avoid stalls when making pages secure * [22.04 FEAT] KVM: Attestation support for Secure Execution (crypto) (LP: #1959973) - drivers/s390/char: Add Ultravisor io device - s390/uv_uapi: depend on CONFIG_S390 - [Config] CONFIG_S390_UV_UAPI=y for s390x * CVE-2022-1679 - SAUCE: ath9k: fix use-after-free in ath9k_hif_usb_rx_cb * CVE-2022-28893 - SUNRPC: Ensure we flush any closed sockets before xs_xprt_free() - SUNRPC: Don't leak sockets in xs_local_connect() * CVE-2022-34918 - netfilter: nf_tables: stricter validation of element data * CVE-2022-1652 - floppy: use a statically allocated error counter -- Stefan Bader Tue, 12 Jul 2022 10:51:03 +0200 ** Changed in: linux (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1652 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1679 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-28893 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-34918 -- 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/1980951 Title: [UBUNTU 22.04] Kernel oops while removing device from cio_ignore list Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: == [Impact] * A kernel Oops occurs when a device is removed from the cio_ignore list (that is used to hide ccw devices) on a system with non-I/O subchannels (e.g. SCM or CHSC subchannels). * As a result, previously ignored devices cannot be activated again, and new devices cannot be found. [Fix] * 0c3812c347bf 0c3812c347bfb0dc213556a195e79850c55702f5 "s390/cio: derive cdev information only for IO-subchannels" [Test Plan] * An IBM zSystems or LinuxONE
[Kernel-packages] [Bug 1981173] Re: Clear PCI errors left from BIOS
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1014.15 --- linux-oem-5.17 (5.17.0-1014.15) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1014.15 -proposed tracker (LP: #1981244) * Clear PCI errors left from BIOS (LP: #1981173) - PCI: Clear PCI_STATUS when setting up device * intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes (LP: #1982104) - iommu/vt-d: Fix RID2PASID setup/teardown failure * Failed to resume from S3 blocked by atlantic driver[1d6a:94c0] (LP: #1981950) - net: atlantic: remove deep parameter on suspend/resume functions - net: atlantic: remove aq_nic_deinit() when resume * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines (LP: #1980700) - ASoC: amd: Add support for enabling DMIC on acp6x via _DSD * CVE-2022-34918 - netfilter: nf_tables: stricter validation of element data * System freeze after resuming from suspend due to PCI ASPM settings (LP: #1980829) - PCI/ASPM: Save/restore L1SS Capability for suspend/resume - PCI:ASPM: Remove pcie_aspm_pm_state_change() -- Chia-Lin Kao (AceLan) Tue, 19 Jul 2022 22:07:45 +0800 ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-34918 -- 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/1981173 Title: Clear PCI errors left from BIOS Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] Errors like Master Abort can be flagged before setting up PCI devices. [Fix] Clear PCI status that BIOS handed over to the OS. [Test] Using `lspci`, no more errors after boot. [Where problems could occur] If there's any driver's probe routine depends on PCI status to have different behavior, this can cause some cracks. There doesn't seem to be any driver doing such insane thing though. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981773] Re: Make cm32181 sensor work after system suspend
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1014.15 --- linux-oem-5.17 (5.17.0-1014.15) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1014.15 -proposed tracker (LP: #1981244) * Clear PCI errors left from BIOS (LP: #1981173) - PCI: Clear PCI_STATUS when setting up device * intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes (LP: #1982104) - iommu/vt-d: Fix RID2PASID setup/teardown failure * Failed to resume from S3 blocked by atlantic driver[1d6a:94c0] (LP: #1981950) - net: atlantic: remove deep parameter on suspend/resume functions - net: atlantic: remove aq_nic_deinit() when resume * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines (LP: #1980700) - ASoC: amd: Add support for enabling DMIC on acp6x via _DSD * CVE-2022-34918 - netfilter: nf_tables: stricter validation of element data * System freeze after resuming from suspend due to PCI ASPM settings (LP: #1980829) - PCI/ASPM: Save/restore L1SS Capability for suspend/resume - PCI:ASPM: Remove pcie_aspm_pm_state_change() -- Chia-Lin Kao (AceLan) Tue, 19 Jul 2022 22:07:45 +0800 ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-34918 -- 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/1981773 Title: Make cm32181 sensor work after system suspend 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-oem-5.17 package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] cm32181 ambient light sensor stops working after system suspend. [Fix] Add PM support for cm32181 so it can work after system suspend. [Test] The sysfs in_illuminance_input continues to change after system suspend. [Where problems could occur] This changeset is limited to a specific device, and it already lacks PM support - so the worst case is that it stops working after resume like it always has been. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981950] Re: Failed to resume from S3 blocked by atlantic driver[1d6a:94c0]
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1014.15 --- linux-oem-5.17 (5.17.0-1014.15) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1014.15 -proposed tracker (LP: #1981244) * Clear PCI errors left from BIOS (LP: #1981173) - PCI: Clear PCI_STATUS when setting up device * intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes (LP: #1982104) - iommu/vt-d: Fix RID2PASID setup/teardown failure * Failed to resume from S3 blocked by atlantic driver[1d6a:94c0] (LP: #1981950) - net: atlantic: remove deep parameter on suspend/resume functions - net: atlantic: remove aq_nic_deinit() when resume * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines (LP: #1980700) - ASoC: amd: Add support for enabling DMIC on acp6x via _DSD * CVE-2022-34918 - netfilter: nf_tables: stricter validation of element data * System freeze after resuming from suspend due to PCI ASPM settings (LP: #1980829) - PCI/ASPM: Save/restore L1SS Capability for suspend/resume - PCI:ASPM: Remove pcie_aspm_pm_state_change() -- Chia-Lin Kao (AceLan) Tue, 19 Jul 2022 22:07:45 +0800 ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-34918 -- 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/1981950 Title: Failed to resume from S3 blocked by atlantic driver[1d6a:94c0] Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] The system with atlantic NIC[1d6a:94c0] fails to resume from S3 and hang with the following errors Jun 7 13:13:54 ubuntu kernel: [ 116.000561] aq_nic_deinit+0xb4/0xd0 [atlantic] Jun 7 13:13:54 ubuntu kernel: [ 116.000566] atl_resume_common+0x6d/0x110 [atlantic] Jun 7 13:13:54 ubuntu kernel: [ 116.000571] aq_pm_resume_restore+0x13/0x20 [atlantic] Jun 7 13:13:54 ubuntu kernel: [ 116.000575] pci_pm_resume+0x5c/0x90 Jun 7 13:13:54 ubuntu kernel: [ 116.000578] ? pci_pm_thaw+0x80/0x80 Jun 7 13:13:54 ubuntu kernel: [ 116.000580] dpm_run_callback+0x4e/0x120 Jun 7 13:13:54 ubuntu kernel: [ 116.000582] device_resume+0xad/0x200 Jun 7 13:13:54 ubuntu kernel: [ 116.000583] async_resume+0x1e/0x40 Jun 7 13:13:54 ubuntu kernel: [ 116.000585] async_run_entry_fn+0x33/0x120 Jun 7 13:13:54 ubuntu kernel: [ 116.000586] process_one_work+0x220/0x3c0 Jun 7 13:13:54 ubuntu kernel: [ 116.000588] worker_thread+0x4d/0x3f0 Jun 7 13:13:54 ubuntu kernel: [ 116.000589] ? process_one_work+0x3c0/0x3c0 Jun 7 13:13:54 ubuntu kernel: [ 116.000591] kthread+0x12a/0x150 Jun 7 13:13:54 ubuntu kernel: [ 116.000592] ? set_kthread_struct+0x40/0x40 Jun 7 13:13:54 ubuntu kernel: [ 116.000593] ret_from_fork+0x22/0x30 Jun 7 13:13:54 ubuntu kernel: [ 116.000596] Jun 7 13:13:54 ubuntu kernel: [ 116.000596] ---[ end trace 9d3fcd41d27dae25 ]--- [Fix] aq_nic_deinit() has been called while suspending, so don't need to call it again on resuming. Applied below 2 commits from v5.19-rc7 fix the issue, and the 2 commits have been applied to stable kernel v5.10, v5.15, and v5.18. 2e15c51fefaf net: atlantic: remove aq_nic_deinit() when resume 0f3325076038 net: atlantic: remove deep parameter on suspend/resume functions [Test] Verified on the system with atlantic NIC[1d6a:94c0] and run S3 test for more than 200 times. [Where problems could occur] The 2 commits remove the redundant code, aq_nic_deinit() has been called while suspending, so we don't need to call it again while resuming, and this fix the issue. I don't think this would introduce any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982104] Re: intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1014.15 --- linux-oem-5.17 (5.17.0-1014.15) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1014.15 -proposed tracker (LP: #1981244) * Clear PCI errors left from BIOS (LP: #1981173) - PCI: Clear PCI_STATUS when setting up device * intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes (LP: #1982104) - iommu/vt-d: Fix RID2PASID setup/teardown failure * Failed to resume from S3 blocked by atlantic driver[1d6a:94c0] (LP: #1981950) - net: atlantic: remove deep parameter on suspend/resume functions - net: atlantic: remove aq_nic_deinit() when resume * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines (LP: #1980700) - ASoC: amd: Add support for enabling DMIC on acp6x via _DSD * CVE-2022-34918 - netfilter: nf_tables: stricter validation of element data * System freeze after resuming from suspend due to PCI ASPM settings (LP: #1980829) - PCI/ASPM: Save/restore L1SS Capability for suspend/resume - PCI:ASPM: Remove pcie_aspm_pm_state_change() -- Chia-Lin Kao (AceLan) Tue, 19 Jul 2022 22:07:45 +0800 ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-34918 -- 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/1982104 Title: intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] Ubuntu 22.04 installation crashes on our Intel Sapphire Rapids proto server. Attaching the console logs. Currently, it looks like disabling VT-D option in BIOS settings helps mitigate the issue. Console logs indicate something is wrong in iommu/dmar subsystem. [Fix] The IOMMU driver shares the pasid table for PCI alias devices. When the RID2PASID entry of the shared pasid table has been filled by the first device, the subsequent device will encounter the "DMAR: Setup RID2PASID failed" failure as the pasid entry has already been marked as present. As the result, the IOMMU probing process will be aborted. On the contrary, when any alias device is hot-removed from the system, for example, by writing to /sys/bus/pci/devices/.../remove, the shared RID2PASID will be cleared without any notifications to other devices. As the result, any DMAs from those rest devices are blocked. Sharing pasid table among PCI alias devices could save two memory pages for devices underneath the PCIe-to-PCI bridges. Anyway, considering that those devices are rare on modern platforms that support VT-d in scalable mode and the saved memory is negligible, it's reasonable to remove this part of immature code to make the driver feasible and stable. [Test Case] 1. use the target machine(Intel Sapphire Rapids) and install the kernel with the fix. 2. boot the target machine 3. check dmesg if the error message exists [ 8.120527] pci :03:01.0: DMAR: Setup RID2PASID failed [Where problems could occur] After enable intel_iommu, the errors may be occurred. We need to figure out one by one once the related errors are triggered in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1982104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1944712] Re: systemd/237-3ubuntu10.52 ADT test failure with linux-aws-5.4/5.4.0-1057.60~18.04.1
Closing this bug for systemd, as it's not relevant anymore IMO and is a red herring in proposed-migration. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1944712 Title: systemd/237-3ubuntu10.52 ADT test failure with linux- aws-5.4/5.4.0-1057.60~18.04.1 Status in linux-aws-5.4 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux-aws-5.4/5.4.0-1057.60~18.04.1 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/s/systemd/20210923_022411_52338@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws-5.4/+bug/1944712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
