pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)

Bug #1988797 reported by Daniel van Vugt
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
HWE Next
Fix Released
Critical
Unassigned
OEM Priority Project
Fix Released
Undecided
Unassigned
linux (Ubuntu)
Fix Released
Medium
Unassigned
Jammy
Fix Released
Medium
Unassigned
Kinetic
Fix Released
Medium
Unassigned
linux-oem-5.14 (Ubuntu)
Invalid
Undecided
Unassigned
Jammy
Invalid
Undecided
Unassigned
Kinetic
Invalid
Undecided
Unassigned
linux-oem-5.17 (Ubuntu)
Invalid
Undecided
Unassigned
Jammy
Fix Released
Medium
Unassigned
Kinetic
Invalid
Undecided
Unassigned
linux-oem-6.0 (Ubuntu)
Invalid
Medium
Unassigned
Jammy
Fix Released
Medium
Unassigned
Kinetic
Invalid
Medium
Unassigned

Bug Description

My kernel log periodically bursts with:

[10405.588287] pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
[10405.593393] pcieport 0000:00:1b.0: device [8086:7ac4] error status/mask=00100000/00004000
[10405.598564] pcieport 0000:00:1b.0: [20] UnsupReq (First)
[10405.603829] pcieport 0000:00:1b.0: AER: TLP Header: 34000000 01000052 00000000 00000000
[10405.609563] pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
[10405.614959] pcieport 0000:00:1b.0: device [8086:7ac4] error status/mask=00100000/00004000
[10405.620296] pcieport 0000:00:1b.0: [20] UnsupReq (First)
[10405.625554] pcieport 0000:00:1b.0: AER: TLP Header: 34000000 01000052 00000000 00000000
[10405.631180] pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
[10405.636495] pcieport 0000:00:1b.0: device [8086:7ac4] error status/mask=00100000/00004000
[10405.641867] pcieport 0000:00:1b.0: [20] UnsupReq (First)
[10405.647169] pcieport 0000:00:1b.0: AER: TLP Header: 34000000 01000052 00000000 00000000
[10405.652919] pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
[10405.658369] pcieport 0000:00:1b.0: device [8086:7ac4] error status/mask=00100000/00004000
[10405.663803] pcieport 0000:00:1b.0: [20] UnsupReq (First)
[10405.669263] pcieport 0000:00:1b.0: AER: TLP Header: 34000000 01000052 00000000 00000000
[10405.675130] pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
[10405.680699] pcieport 0000:00:1b.0: device [8086:7ac4] error status/mask=00100000/00004000
[10405.686267] pcieport 0000:00:1b.0: [20] UnsupReq (First)
[10405.691759] pcieport 0000:00:1b.0: AER: TLP Header: 34000000 01000052 00000000 00000000

This has happened even since I got the machine. It also happened with 5.15.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-15-generic 5.19.0-15.15
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dan 2477 F.... wireplumber
 /dev/snd/seq: dan 2474 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Tue Sep 6 13:52:35 2022
InstallationDate: Installed on 2022-07-20 (47 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
MachineType: Intel(R) Client Systems NUC12DCMi7
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.19.0-15-generic N/A
 linux-backports-modules-5.19.0-15-generic N/A
 linux-firmware 20220831.gitd3c92280-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/20/2021
dmi.bios.release: 5.24
dmi.bios.vendor: Intel Corp.
dmi.bios.version: EDADL579.0046.2021.1220.2351
dmi.board.name: NUC12EDBi7
dmi.board.vendor: Intel Corporation
dmi.board.version: M27908-302
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 3.7
dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi70000:
dmi.product.family: DC
dmi.product.name: NUC12DCMi7
dmi.product.sku: RNUC12DCMi70000
dmi.product.version: M30143-302
dmi.sys.vendor: Intel(R) Client Systems

CVE References

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

The fix is here:
https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/log/?h=pci/pm

I'll do the backport once it's included in linux-next.

Changed in linux (Ubuntu):
assignee: nobody → Kai-Heng Feng (kaihengfeng)
tags: added: oem-priority originate-from-1980039 stella
tags: added: originate-from-1955958
tags: added: originate-from-1970734
Changed in linux (Ubuntu Jammy):
status: New → Confirmed
importance: Undecided → Medium
Changed in linux (Ubuntu Kinetic):
importance: Undecided → Medium
Changed in linux-oem-5.17 (Ubuntu Kinetic):
status: New → Invalid
Changed in linux-oem-5.17 (Ubuntu Jammy):
status: New → Confirmed
importance: Undecided → Medium
Changed in linux-oem-6.0 (Ubuntu Jammy):
importance: Undecided → Medium
status: New → Confirmed
Changed in linux-oem-6.0 (Ubuntu Kinetic):
importance: Undecided → Medium
status: New → Invalid
Timo Aaltonen (tjaalton)
Changed in linux-oem-5.17 (Ubuntu Jammy):
status: Confirmed → Fix Committed
Changed in linux-oem-6.0 (Ubuntu Jammy):
status: Confirmed → Fix Committed
Bin Li (binli)
tags: added: originate-from-1976477 sutton
Bin Li (binli)
tags: added: originate-from-1990332
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-oem-5.17/5.17.0-1019.20 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-done-jammy
Timo Aaltonen (tjaalton)
Changed in hwe-next:
importance: Undecided → Critical
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-oem-5.17 - 5.17.0-1019.20

---------------
linux-oem-5.17 (5.17.0-1019.20) jammy; urgency=medium

  * jammy/linux-oem-5.17: 5.17.0-1019.20 -proposed tracker (LP: #1989787)

  * Fix resume on AMD platforms when TBT monitor is plugged (LP: #1990920)
    - drm/amd/display: Detect dpcd_rev when hotplug mst monitor
    - drm/amd/display: Release remote dc_sink under mst scenario

  * pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal),
    type=Transaction Layer, (Requester ID) (LP: #1988797)
    - SAUCE: PCI/PTM: Cache PTM Capability offset
    - SAUCE: PCI/PTM: Add pci_upstream_ptm() helper
    - SAUCE: PCI/PTM: Separate configuration and enable
    - SAUCE: PCI/PTM: Add pci_suspend_ptm() and pci_resume_ptm()
    - SAUCE: PCI/PTM: Move pci_ptm_info() body into its only caller
    - SAUCE: PCI/PTM: Preserve RsvdP bits in PTM Control register
    - SAUCE: PCI/PTM: Reorder functions in logical order
    - SAUCE: PCI/PTM: Consolidate PTM interface declarations
    - SAUCE: PCI/PM: Always disable PTM for all devices during suspend
    - SAUCE: PCI/PM: Simplify pci_pm_suspend_noirq()

  * Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400)
    (LP: #1989647)
    - drm/amd/display: Ignore First MST Sideband Message Return Error

  * System hang during S3 test (LP: #1990330)
    - memcg: add per-memcg total kernel memory stat
    - mm/memcg: revert ("mm/memcg: optimize user context object stock access")
    - mm/memcg: disable threshold event handlers on PREEMPT_RT
    - mm/memcg: protect per-CPU counter by disabling preemption on PREEMPT_RT
      where needed.
    - mm/memcg: opencode the inner part of obj_cgroup_uncharge_pages() in
      drain_obj_stock()
    - mm/memcg: protect memcg_stock with a local_lock_t
    - mm/memcg: disable migration instead of preemption in drain_all_stock().
    - mm/memremap: avoid calling kasan_remove_zero_shadow() for device private
      memory

  * To support Intel Maple Ridge Thunderbolt [8086:1134] (LP: #1990240)
    - thunderbolt: Add support for Intel Maple Ridge single port controller

  * Intel graphic driver is not probing[8086:468b] (LP: #1990242)
    - drm/i915: Add new ADL-S pci id

  * support independent clock and LED GPIOs for Intel IPU6 platforms
    (LP: #1989046)
    - SAUCE: platform/x86: int3472: support independent clock and LED GPIOs

 -- Timo Aaltonen <email address hidden> Tue, 27 Sep 2022 15:12:42 +0300

Changed in linux-oem-5.17 (Ubuntu Jammy):
status: Fix Committed → Fix Released
Timo Aaltonen (tjaalton)
Changed in linux-oem-5.14 (Ubuntu Kinetic):
status: New → Invalid
Changed in linux-oem-5.14 (Ubuntu Jammy):
status: New → Fix Committed
Timo Aaltonen (tjaalton)
Changed in hwe-next:
status: New → Confirmed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-oem-5.14/5.14.0-1053.60 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-done-focal
Changed in linux (Ubuntu Kinetic):
assignee: Kai-Heng Feng (kaihengfeng) → nobody
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

fixed in 6.0 1006

Changed in linux-oem-6.0 (Ubuntu Jammy):
status: Fix Committed → Fix Released
Changed in linux-oem-5.14 (Ubuntu Jammy):
status: Fix Committed → Invalid
Revision history for this message
Stefan Bader (smb) wrote :

This was at least committed already to Kinetic. Potentially released by now...

Changed in linux (Ubuntu Kinetic):
status: Confirmed → Fix Committed
Changed in linux (Ubuntu Jammy):
status: Confirmed → Fix Committed
Timo Aaltonen (tjaalton)
Changed in hwe-next:
status: Confirmed → Fix Committed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux/5.19.0-27.28 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-kinetic-linux verification-needed-kinetic
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux/5.15.0-57.63 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux verification-needed-jammy
removed: verification-done-jammy
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Daniel, the issue is fixed by the proposed kernel at my end. Does this also fix the issue you saw?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

My affected system is running lunar. What kernel should I test there?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

P.S. Although I have seen the bug recently, it doesn't seem to be happening often enough right now for me to verify a new kernel with confidence in a short timeframe.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Try 5.19.0-27.28 on Lunar.

So let me mark it as verified since I no longer see the issue.

tags: added: verification-done-jammy verification-done-kinetic
removed: verification-needed-jammy verification-needed-kinetic
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-nvidia/5.15.0-1011.11 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-nvidia verification-needed-jammy
removed: verification-done-jammy
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Sorry for the delay - it was a long end of year break.

As a sanity test I am currently waiting for the bug to happen in vanilla lunar (5.19.0-21-generic) but it hasn't happened yet... I can't say whether any new kernel has fixed it if the original problem isn't happening on the old kernel.

Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (42.6 KiB)

This bug was fixed in the package linux - 5.15.0-57.63

---------------
linux (5.15.0-57.63) jammy; urgency=medium

  * jammy/linux: 5.15.0-57.63 -proposed tracker (LP: #1997737)

  * Packaging resync (LP: #1786013)
    - [Packaging] update variants
    - debian/dkms-versions -- update from kernel-versions (main/2022.11.14)

  * Expose built-in trusted and revoked certificates (LP: #1996892)
    - [Packaging] Expose built-in trusted and revoked certificates

  * TEE Support for CCP driver (LP: #1991608)
    - crypto: ccp: Add support for TEE for PCI ID 0x14CA

  * alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41
    codec (LP: #1996121)
    - ASoC: cs35l41: Add one more variable in the debug log
    - ASoC: cs35l41: Fix an out-of-bounds access in otp_packed_element_t

  * Fix ath11k deadlock on WCN6855 (LP: #1995041)
    - wifi: ath11k: avoid deadlock during regulatory update in
      ath11k_regd_update()

  * [UBUNTU 20.04] boot: Add s390x secure boot trailer (LP: #1996071)
    - s390/boot: add secure boot trailer

  * Fix rfkill causing soft blocked wifi (LP: #1996198)
    - platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi

  * Fix Thunderbolt device hotplug fail when connect via thunderbolt dock
    (LP: #1991366)
    - PCI: Fix used_buses calculation in pci_scan_child_bus_extend()
    - PCI: Pass available buses even if the bridge is already configured
    - PCI: Move pci_assign_unassigned_root_bus_resources()
    - PCI: Distribute available resources for root buses, too
    - PCI: Fix whitespace and indentation
    - PCI: Fix typo in pci_scan_child_bus_extend()

  * md: Replace snprintf with scnprintf (LP: #1993315)
    - md: Replace snprintf with scnprintf

  * input/keyboard: the keyboard on some Asus laptops can't work (LP: #1992266)
    - ACPI: resource: Skip IRQ override on Asus Vivobook K3402ZA/K3502ZA
    - ACPI: resource: Add ASUS model S5402ZA to quirks

  * Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU
    (LP: #1991365)
    - tools/power turbostat: Add support for RPL-S

  * pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal),
    type=Transaction Layer, (Requester ID) (LP: #1988797)
    - PCI/PTM: Cache PTM Capability offset
    - PCI/PTM: Add pci_upstream_ptm() helper
    - PCI/PTM: Separate configuration and enable
    - PCI/PTM: Add pci_suspend_ptm() and pci_resume_ptm()
    - PCI/PTM: Move pci_ptm_info() body into its only caller
    - PCI/PTM: Preserve RsvdP bits in PTM Control register
    - PCI/PTM: Reorder functions in logical order
    - PCI/PTM: Consolidate PTM interface declarations
    - PCI/PM: Always disable PTM for all devices during suspend
    - PCI/PM: Simplify pci_pm_suspend_noirq()

  * Fix RPL-S support on powercap/intel_rapl (LP: #1990161)
    - x86/cpu: Drop spurious underscore from RAPTOR_LAKE #define
    - x86/cpu: Add new Alderlake and Raptorlake CPU model numbers
    - x86/cpu: Add new Raptor Lake CPU model number
    - powercap: intel_rapl: add support for RaptorLake
    - powercap: intel_rapl: Add support for RAPTORLAKE_P
    - powercap: intel_rapl: Add support for RAPTORLAKE_S

  * AMD Yellow Carp system hang on HDMI plug ...

Changed in linux (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (100.4 KiB)

This bug was fixed in the package linux - 5.19.0-28.29

---------------
linux (5.19.0-28.29) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-28.29 -proposed tracker (LP: #1999746)

  * mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux
    5.19.0-27.28 (LP: #1999094)
    - fix coredump breakage

linux (5.19.0-27.28) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-27.28 -proposed tracker (LP: #1997794)

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/2022.11.14)

  * selftests/.../nat6to4 breaks the selftests build (LP: #1996536)
    - [Config] Disable selftests/net/bpf/nat6to4

  * Expose built-in trusted and revoked certificates (LP: #1996892)
    - [Packaging] Expose built-in trusted and revoked certificates

  * support for same series backports versioning numbers (LP: #1993563)
    - [Packaging] sameport -- add support for sameport versioning

  * Add cs35l41 firmware loading support (LP: #1995957)
    - ASoC: cs35l41: Move cs35l41 exit hibernate function into shared code
    - ASoC: cs35l41: Add common cs35l41 enter hibernate function
    - ASoC: cs35l41: Do not print error when waking from hibernation
    - ALSA: hda: cs35l41: Don't dereference fwnode handle
    - ALSA: hda: cs35l41: Allow compilation test on non-ACPI configurations
    - ALSA: hda: cs35l41: Drop wrong use of ACPI_PTR()
    - ALSA: hda: cs35l41: Consolidate selections under SND_HDA_SCODEC_CS35L41
    - ALSA: hda: hda_cs_dsp_ctl: Add Library to support CS_DSP ALSA controls
    - ALSA: hda: hda_cs_dsp_ctl: Add apis to write the controls directly
    - ALSA: hda: cs35l41: Save codec object inside component struct
    - ALSA: hda: cs35l41: Add initial DSP support and firmware loading
    - ALSA: hda: cs35l41: Save Subsystem ID inside CS35L41 Driver
    - ALSA: hda: cs35l41: Support reading subsystem id from ACPI
    - ALSA: hda: cs35l41: Support multiple load paths for firmware
    - ALSA: hda: cs35l41: Support Speaker ID for laptops
    - ALSA: hda: cs35l41: Support Hibernation during Suspend
    - ALSA: hda: cs35l41: Read Speaker Calibration data from UEFI variables
    - ALSA: hda: hda_cs_dsp_ctl: Add fw id strings
    - ALSA: hda: cs35l41: Add defaulted values into dsp bypass config sequence
    - ALSA: hda: cs35l41: Support Firmware switching and reloading
    - ALSA: hda: cs35l41: Add module parameter to control firmware load
    - Revert "ALSA: hda: cs35l41: Allow compilation test on non-ACPI
      configurations"
    - ALSA: hda/realtek: More robust component matching for CS35L41
    - [Config] updateconfigs for SND_HDA_CS_DSP_CONTROLS

  * Fibocom WWAN FM350-GL suspend error (notebook not suspend) (LP: #1990700)
    - net: wwan: t7xx: Add AP CLDMA

  * Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536]
    (LP: #1995573)
    - drm/mgag200: Optimize damage clips
    - drm/mgag200: Add FB_DAMAGE_CLIPS support
    - drm/mgag200: Enable atomic gamma lut update

  * TEE Support for CCP driver (LP: #1991608)
    - crypto: ccp: Add support for TEE for PCI ID 0x14CA

  * AMD Cezanne takes 5 minutes to wake up from suspend (LP: #1993715)
    - platform/x86/amd: pmc: Read...

Changed in linux (Ubuntu Kinetic):
status: Fix Committed → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-kinetic-linux-ibm verification-needed-kinetic
removed: verification-done-kinetic
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I'm finally noticing the bug again on lunar (5.19.0-21-generic) so will commence testing 5.19.0-28-generic ... But what is the planned series to fix lunar? Is it 6.0?

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

lunar will first get 6.1 and release with 6.2

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws/5.19.0-1018.19 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-kinetic-linux-aws
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-gke-5.15/5.15.0-1025.30~20.04.1 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: kernel-spammed-focal-linux-gke-5.15 verification-needed-focal
removed: verification-done-focal
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure/5.19.0-1017.18 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-kinetic-linux-azure
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure/5.15.0-1032.39 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-azure
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws/5.15.0-1029.33 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-aws
Revision history for this message
Abu Sayeed (sayeed843) wrote : Re: [Bug 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
Download full text (6.3 KiB)

Hi,

I am facing this problem on ubuntu 22.04, kernel version 5.15. I do not
understand which kernel version should I install to get rid of this issue.

On Wed, 18 Jan 2023, 3:57 pm Ubuntu Kernel Bot, <email address hidden>
wrote:

> This bug is awaiting verification that the linux-aws/5.15.0-1029.33
> kernel in -proposed solves the problem. Please test the kernel and
> update this bug with the results. If the problem is solved, change the
> tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
> problem still exists, change the tag 'verification-needed-jammy' to
> 'verification-failed-jammy'.
>
> If verification is not done by 5 working days from today, this fix will
> be dropped from the source code, and this bug will be closed.
>
> See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
> to enable and use -proposed. Thank you!
>
>
> ** Tags added: kernel-spammed-jammy-linux-aws
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1988797
>
> Title:
> pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-
> Fatal), type=Transaction Layer, (Requester ID)
>
> Status in HWE Next:
> Fix Committed
> Status in OEM Priority Project:
> New
> Status in linux package in Ubuntu:
> Confirmed
> Status in linux-oem-5.14 package in Ubuntu:
> Invalid
> Status in linux-oem-5.17 package in Ubuntu:
> Invalid
> Status in linux-oem-6.0 package in Ubuntu:
> 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
> Status in linux-oem-6.0 source package in Jammy:
> Fix Released
> Status in linux source package in Kinetic:
> Fix Released
> Status in linux-oem-5.14 source package in Kinetic:
> Invalid
> Status in linux-oem-5.17 source package in Kinetic:
> Invalid
> Status in linux-oem-6.0 source package in Kinetic:
> Invalid
>
> Bug description:
> My kernel log periodically bursts with:
>
> [10405.588287] pcieport 0000:00:1b.0: PCIe Bus Error:
> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
> [10405.593393] pcieport 0000:00:1b.0: device [8086:7ac4] error
> status/mask=00100000/00004000
> [10405.598564] pcieport 0000:00:1b.0: [20] UnsupReq
> (First)
> [10405.603829] pcieport 0000:00:1b.0: AER: TLP Header: 34000000
> 01000052 00000000 00000000
> [10405.609563] pcieport 0000:00:1b.0: PCIe Bus Error:
> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
> [10405.614959] pcieport 0000:00:1b.0: device [8086:7ac4] error
> status/mask=00100000/00004000
> [10405.620296] pcieport 0000:00:1b.0: [20] UnsupReq
> (First)
> [10405.625554] pcieport 0000:00:1b.0: AER: TLP Header: 34000000
> 01000052 00000000 00000000
> [10405.631180] pcieport 0000:00:1b.0: PCIe Bus Error:
> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
> [10405.636495] pcieport 0000:00:1b.0: device [8086:7ac4] error
> status/mask=00100000/00004000
> [10405.641867] pcieport 0000:00:1b.0: [20] UnsupReq
> (Fir...

Read more...

Revision history for this message
Daniel van Vugt (vanvugt) wrote (last edit ):

> I am facing this problem on ubuntu 22.04, kernel version 5.15. I do not
> understand which kernel version should I install to get rid of this
> issue.

Comment #17 says:

> This bug was fixed in the package linux - 5.15.0-57.63

so it should only require a system update:

  sudo apt update
  sudo apt full-upgrade

and reboot.

If the problem persists then please include the full kernel version affected (uname -r).

Revision history for this message
Abu Sayeed (sayeed843) wrote :
Download full text (6.0 KiB)

Hi,

Please check the output of uname -r command,
*5.15.0-58-generic*

On Mon, Jan 23, 2023 at 9:40 AM Daniel van Vugt <email address hidden>
wrote:

> > I am facing this problem on ubuntu 22.04, kernel version 5.15. I do not
> > understand which kernel version should I install to get rid of this
> > issue.
>
> Comment #17 says:
>
> > This bug was fixed in the package linux - 5.15.0-57.63
>
> so it should only require a system update:
>
> sudo apt update
> sudo apt full-upgrade
>
> and reboot.
>
> If the problem persists then please include the full kernel version
> affected (uname -r).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1988797
>
> Title:
> pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-
> Fatal), type=Transaction Layer, (Requester ID)
>
> Status in HWE Next:
> Fix Committed
> Status in OEM Priority Project:
> New
> Status in linux package in Ubuntu:
> Confirmed
> Status in linux-oem-5.14 package in Ubuntu:
> Invalid
> Status in linux-oem-5.17 package in Ubuntu:
> Invalid
> Status in linux-oem-6.0 package in Ubuntu:
> 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
> Status in linux-oem-6.0 source package in Jammy:
> Fix Released
> Status in linux source package in Kinetic:
> Fix Released
> Status in linux-oem-5.14 source package in Kinetic:
> Invalid
> Status in linux-oem-5.17 source package in Kinetic:
> Invalid
> Status in linux-oem-6.0 source package in Kinetic:
> Invalid
>
> Bug description:
> My kernel log periodically bursts with:
>
> [10405.588287] pcieport 0000:00:1b.0: PCIe Bus Error:
> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
> [10405.593393] pcieport 0000:00:1b.0: device [8086:7ac4] error
> status/mask=00100000/00004000
> [10405.598564] pcieport 0000:00:1b.0: [20] UnsupReq
> (First)
> [10405.603829] pcieport 0000:00:1b.0: AER: TLP Header: 34000000
> 01000052 00000000 00000000
> [10405.609563] pcieport 0000:00:1b.0: PCIe Bus Error:
> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
> [10405.614959] pcieport 0000:00:1b.0: device [8086:7ac4] error
> status/mask=00100000/00004000
> [10405.620296] pcieport 0000:00:1b.0: [20] UnsupReq
> (First)
> [10405.625554] pcieport 0000:00:1b.0: AER: TLP Header: 34000000
> 01000052 00000000 00000000
> [10405.631180] pcieport 0000:00:1b.0: PCIe Bus Error:
> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
> [10405.636495] pcieport 0000:00:1b.0: device [8086:7ac4] error
> status/mask=00100000/00004000
> [10405.641867] pcieport 0000:00:1b.0: [20] UnsupReq
> (First)
> [10405.647169] pcieport 0000:00:1b.0: AER: TLP Header: 34000000
> 01000052 00000000 00000000
> [10405.652919] pcieport 0000:00:1b.0: PCIe Bus Error:
> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
> [10405.658369] pcieport 0000:00:1b.0: device [8086:7ac4] error
> status/mask=00100000...

Read more...

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Can you provide a kernel log proving it's this bug?

Revision history for this message
Abu Sayeed (sayeed843) wrote :
Download full text (5.7 KiB)

Please check the dmeg.log file. I have also attached an error screenshot,
which I get during freeze my screen.
[image: Screenshot from 2023-01-24 18-15-29.png]

On Tue, Jan 24, 2023 at 1:50 PM Daniel van Vugt <email address hidden>
wrote:

> Can you provide a kernel log proving it's this bug?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1988797
>
> Title:
> pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-
> Fatal), type=Transaction Layer, (Requester ID)
>
> Status in HWE Next:
> Fix Committed
> Status in OEM Priority Project:
> New
> Status in linux package in Ubuntu:
> Confirmed
> Status in linux-oem-5.14 package in Ubuntu:
> Invalid
> Status in linux-oem-5.17 package in Ubuntu:
> Invalid
> Status in linux-oem-6.0 package in Ubuntu:
> 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
> Status in linux-oem-6.0 source package in Jammy:
> Fix Released
> Status in linux source package in Kinetic:
> Fix Released
> Status in linux-oem-5.14 source package in Kinetic:
> Invalid
> Status in linux-oem-5.17 source package in Kinetic:
> Invalid
> Status in linux-oem-6.0 source package in Kinetic:
> Invalid
>
> Bug description:
> My kernel log periodically bursts with:
>
> [10405.588287] pcieport 0000:00:1b.0: PCIe Bus Error:
> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
> [10405.593393] pcieport 0000:00:1b.0: device [8086:7ac4] error
> status/mask=00100000/00004000
> [10405.598564] pcieport 0000:00:1b.0: [20] UnsupReq
> (First)
> [10405.603829] pcieport 0000:00:1b.0: AER: TLP Header: 34000000
> 01000052 00000000 00000000
> [10405.609563] pcieport 0000:00:1b.0: PCIe Bus Error:
> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
> [10405.614959] pcieport 0000:00:1b.0: device [8086:7ac4] error
> status/mask=00100000/00004000
> [10405.620296] pcieport 0000:00:1b.0: [20] UnsupReq
> (First)
> [10405.625554] pcieport 0000:00:1b.0: AER: TLP Header: 34000000
> 01000052 00000000 00000000
> [10405.631180] pcieport 0000:00:1b.0: PCIe Bus Error:
> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
> [10405.636495] pcieport 0000:00:1b.0: device [8086:7ac4] error
> status/mask=00100000/00004000
> [10405.641867] pcieport 0000:00:1b.0: [20] UnsupReq
> (First)
> [10405.647169] pcieport 0000:00:1b.0: AER: TLP Header: 34000000
> 01000052 00000000 00000000
> [10405.652919] pcieport 0000:00:1b.0: PCIe Bus Error:
> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
> [10405.658369] pcieport 0000:00:1b.0: device [8086:7ac4] error
> status/mask=00100000/00004000
> [10405.663803] pcieport 0000:00:1b.0: [20] UnsupReq
> (First)
> [10405.669263] pcieport 0000:00:1b.0: AER: TLP Header: 34000000
> 01000052 00000000 00000000
> [10405.675130] pcieport 0000:00:1b.0: PCIe Bus Error:
> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Reques...

Read more...

Revision history for this message
Abu Sayeed (sayeed843) wrote :
Download full text (6.0 KiB)

Check the below log file also. If you need any further information, please
let me know.

On Tue, Jan 24, 2023 at 6:17 PM Mr. Nobody <email address hidden> wrote:

> Please check the dmeg.log file. I have also attached an error screenshot,
> which I get during freeze my screen.
> [image: Screenshot from 2023-01-24 18-15-29.png]
>
>
>
> On Tue, Jan 24, 2023 at 1:50 PM Daniel van Vugt <
> <email address hidden>> wrote:
>
>> Can you provide a kernel log proving it's this bug?
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1988797
>>
>> Title:
>> pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-
>> Fatal), type=Transaction Layer, (Requester ID)
>>
>> Status in HWE Next:
>> Fix Committed
>> Status in OEM Priority Project:
>> New
>> Status in linux package in Ubuntu:
>> Confirmed
>> Status in linux-oem-5.14 package in Ubuntu:
>> Invalid
>> Status in linux-oem-5.17 package in Ubuntu:
>> Invalid
>> Status in linux-oem-6.0 package in Ubuntu:
>> 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
>> Status in linux-oem-6.0 source package in Jammy:
>> Fix Released
>> Status in linux source package in Kinetic:
>> Fix Released
>> Status in linux-oem-5.14 source package in Kinetic:
>> Invalid
>> Status in linux-oem-5.17 source package in Kinetic:
>> Invalid
>> Status in linux-oem-6.0 source package in Kinetic:
>> Invalid
>>
>> Bug description:
>> My kernel log periodically bursts with:
>>
>> [10405.588287] pcieport 0000:00:1b.0: PCIe Bus Error:
>> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
>> [10405.593393] pcieport 0000:00:1b.0: device [8086:7ac4] error
>> status/mask=00100000/00004000
>> [10405.598564] pcieport 0000:00:1b.0: [20] UnsupReq
>> (First)
>> [10405.603829] pcieport 0000:00:1b.0: AER: TLP Header: 34000000
>> 01000052 00000000 00000000
>> [10405.609563] pcieport 0000:00:1b.0: PCIe Bus Error:
>> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
>> [10405.614959] pcieport 0000:00:1b.0: device [8086:7ac4] error
>> status/mask=00100000/00004000
>> [10405.620296] pcieport 0000:00:1b.0: [20] UnsupReq
>> (First)
>> [10405.625554] pcieport 0000:00:1b.0: AER: TLP Header: 34000000
>> 01000052 00000000 00000000
>> [10405.631180] pcieport 0000:00:1b.0: PCIe Bus Error:
>> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
>> [10405.636495] pcieport 0000:00:1b.0: device [8086:7ac4] error
>> status/mask=00100000/00004000
>> [10405.641867] pcieport 0000:00:1b.0: [20] UnsupReq
>> (First)
>> [10405.647169] pcieport 0000:00:1b.0: AER: TLP Header: 34000000
>> 01000052 00000000 00000000
>> [10405.652919] pcieport 0000:00:1b.0: PCIe Bus Error:
>> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
>> [10405.658369] pcieport 0000:00:1b.0: device [8086:7ac4] error
>> status/mask=00100000/00004000
>> [10405.663803] pcieport 0000:00:1b.0: ...

Read more...

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

That seems to be a different issue on a different device. Please open a new bug by running:

  ubuntu-bug linux

Revision history for this message
Abu Sayeed (sayeed843) wrote :
Download full text (5.7 KiB)

I did it. Check the below link, please
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003932

On Wed, Jan 25, 2023 at 7:57 AM Daniel van Vugt <email address hidden>
wrote:

> That seems to be a different issue on a different device. Please open a
> new bug by running:
>
> ubuntu-bug linux
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1988797
>
> Title:
> pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-
> Fatal), type=Transaction Layer, (Requester ID)
>
> Status in HWE Next:
> Fix Committed
> Status in OEM Priority Project:
> New
> Status in linux package in Ubuntu:
> Confirmed
> Status in linux-oem-5.14 package in Ubuntu:
> Invalid
> Status in linux-oem-5.17 package in Ubuntu:
> Invalid
> Status in linux-oem-6.0 package in Ubuntu:
> 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
> Status in linux-oem-6.0 source package in Jammy:
> Fix Released
> Status in linux source package in Kinetic:
> Fix Released
> Status in linux-oem-5.14 source package in Kinetic:
> Invalid
> Status in linux-oem-5.17 source package in Kinetic:
> Invalid
> Status in linux-oem-6.0 source package in Kinetic:
> Invalid
>
> Bug description:
> My kernel log periodically bursts with:
>
> [10405.588287] pcieport 0000:00:1b.0: PCIe Bus Error:
> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
> [10405.593393] pcieport 0000:00:1b.0: device [8086:7ac4] error
> status/mask=00100000/00004000
> [10405.598564] pcieport 0000:00:1b.0: [20] UnsupReq
> (First)
> [10405.603829] pcieport 0000:00:1b.0: AER: TLP Header: 34000000
> 01000052 00000000 00000000
> [10405.609563] pcieport 0000:00:1b.0: PCIe Bus Error:
> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
> [10405.614959] pcieport 0000:00:1b.0: device [8086:7ac4] error
> status/mask=00100000/00004000
> [10405.620296] pcieport 0000:00:1b.0: [20] UnsupReq
> (First)
> [10405.625554] pcieport 0000:00:1b.0: AER: TLP Header: 34000000
> 01000052 00000000 00000000
> [10405.631180] pcieport 0000:00:1b.0: PCIe Bus Error:
> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
> [10405.636495] pcieport 0000:00:1b.0: device [8086:7ac4] error
> status/mask=00100000/00004000
> [10405.641867] pcieport 0000:00:1b.0: [20] UnsupReq
> (First)
> [10405.647169] pcieport 0000:00:1b.0: AER: TLP Header: 34000000
> 01000052 00000000 00000000
> [10405.652919] pcieport 0000:00:1b.0: PCIe Bus Error:
> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
> [10405.658369] pcieport 0000:00:1b.0: device [8086:7ac4] error
> status/mask=00100000/00004000
> [10405.663803] pcieport 0000:00:1b.0: [20] UnsupReq
> (First)
> [10405.669263] pcieport 0000:00:1b.0: AER: TLP Header: 34000000
> 01000052 00000000 00000000
> [10405.675130] pcieport 0000:00:1b.0: PCIe Bus Error:
> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Req...

Read more...

Timo Aaltonen (tjaalton)
Changed in linux (Ubuntu):
status: Confirmed → Fix Released
Changed in hwe-next:
status: Fix Committed → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure-5.15/5.15.0-1033.40~20.04.1 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: kernel-spammed-focal-linux-azure-5.15
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-bluefield/5.15.0-1012.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-bluefield
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws-5.15/5.15.0-1030.34~20.04.1 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: kernel-spammed-focal-linux-aws-5.15
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-aws-5.19
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-lowlatency-hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19
Timo Aaltonen (tjaalton)
Changed in oem-priority:
status: New → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-linux-mtk'. If the problem still exists, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.