Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #87911 > unrolled thread
| Started by | Matt Mower <mowerm@gmail.com> |
|---|---|
| First post | 2025-06-08 17:10 +0200 |
| Last post | 2025-11-24 06:30 +0100 |
| Articles | 14 — 5 participants |
Back to article view | Back to linux.debian.kernel
Bug#1107521: linux-image-6.12.27+bpo-amd64: ath12k_pci errors and eventual kernel panic starting with linux-image-6.12.27+bpo-amd64 Matt Mower <mowerm@gmail.com> - 2025-06-08 17:10 +0200
Processed: Re: Bug#1107521: linux-image-6.12.27+bpo-amd64: ath12k_pci errors and eventual kernel panic starting with linux-image-6.12.27+bpo-amd64 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-06-11 23:00 +0200
Bug#1107521: linux-image-6.12.27+bpo-amd64: ath12k_pci errors and eventual kernel panic starting with linux-image-6.12.27+bpo-amd64 Uwe Kleine-König <u.kleine-koenig@baylibre.com> - 2025-06-11 23:00 +0200
Bug#1107521: linux-image-6.12.27+bpo-amd64: ath12k_pci errors and eventual kernel panic starting with linux-image-6.12.27+bpo-amd64 Matt Mower <mowerm@gmail.com> - 2025-06-12 22:50 +0200
Bug#1107521: linux-image-6.12.27+bpo-amd64: ath12k_pci errors and eventual kernel panic starting with linux-image-6.12.27+bpo-amd64 Salvatore Bonaccorso <carnil@debian.org> - 2025-06-14 21:40 +0200
Processed: Re: Bug#1107521: linux-image-6.12.27+bpo-amd64: ath12k_pci errors and eventual kernel panic starting with linux-image-6.12.27+bpo-amd64 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-06-16 08:30 +0200
Processed: Re: Bug#1107521: linux-image-6.12.27+bpo-amd64: ath12k_pci errors and eventual kernel panic starting with linux-image-6.12.27+bpo-amd64 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-06-18 11:20 +0200
Bug#1107521: linux-image-6.12.27+bpo-amd64: ath12k_pci errors and eventual kernel panic starting with linux-image-6.12.27+bpo-amd64 Matt Mower <mowerm@gmail.com> - 2025-06-25 07:20 +0200
Bug#1107521: ath12k_pci errors and loss of connectivity in 6.12.y branch Robin Murphy <robin.murphy@arm.com> - 2025-06-27 12:40 +0200
Bug#1107521: ath12k_pci errors and loss of connectivity in 6.12.y branch Matt Mower <mowerm@gmail.com> - 2025-07-02 07:30 +0200
Bug#1107521: ath12k_pci errors and loss of connectivity in 6.12.y branch Matt Mower <mowerm@gmail.com> - 2025-07-02 17:00 +0200
Bug#1107521: Info received (ath12k_pci errors and loss of connectivity in 6.12.y branch) Matt Mower <mowerm@gmail.com> - 2025-08-17 18:40 +0200
Bug#1107521: marked as done (linux-image-6.12.27+bpo-amd64: ath12k_pci errors and eventual kernel panic starting with linux-image-6.12.27+bpo-amd64) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-11-23 23:50 +0100
Bug#1107521: closing 1107521 Salvatore Bonaccorso <carnil@debian.org> - 2025-11-24 06:30 +0100
| From | Matt Mower <mowerm@gmail.com> |
|---|---|
| Date | 2025-06-08 17:10 +0200 |
| Subject | Bug#1107521: linux-image-6.12.27+bpo-amd64: ath12k_pci errors and eventual kernel panic starting with linux-image-6.12.27+bpo-amd64 |
| Message-ID | <KVpON-995M-5@gated-at.bofh.it> |
Package: src:linux Version: 6.12.27-1~bpo12+1 Severity: important X-Debbugs-Cc: mowerm@gmail.com Dear Maintainer, After updating from linux-image-6.12.22+bpo-amd64 to linux-image-6.12.27+bpo- amd64, I am seeing lots of IO_PAGE_FAULT events for device ath12k_pci, and twice my system has completely frozen. The last freeze occurred during shutdown; the dmesg is attached and the tail is pasted here for convenience. My firmware is the latest available from https://git.codelinaro.org/clo/ath- firmware/ath12k-firmware as of this writing: Jun 08 07:28:16.437499 AI360 kernel: ath12k_pci 0000:c2:00.0: chip_id 0x2 chip_family 0x4 board_id 0xff soc_id 0x40170200 Jun 08 07:28:16.437945 AI360 kernel: ath12k_pci 0000:c2:00.0: fw_version 0x1108811c fw_build_timestamp 2025-05-17 00:21 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HMT.1.1.c5-00284.1-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 dmesg tail from last shutdown where system froze: Jun 08 07:31:12.531172 AI360 kernel: ath12k_pci 0000:c2:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0xfe980000 flags=0x0020] Jun 08 07:31:12.531524 AI360 kernel: ath12k_pci 0000:c2:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0xfe980400 flags=0x0020] Jun 08 07:31:12.531654 AI360 kernel: ath12k_pci 0000:c2:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0xfe980500 flags=0x0020] Jun 08 07:31:12.531770 AI360 kernel: ath12k_pci 0000:c2:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0xfe980600 flags=0x0020] Jun 08 07:31:12.531879 AI360 kernel: ath12k_pci 0000:c2:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0xfe980700 flags=0x0020] Jun 08 07:31:12.531988 AI360 kernel: ath12k_pci 0000:c2:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0xfe980800 flags=0x0020] Jun 08 07:31:12.532085 AI360 kernel: ath12k_pci 0000:c2:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0xfe980900 flags=0x0020] Jun 08 07:31:12.532137 AI360 kernel: ath12k_pci 0000:c2:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0xfe980a00 flags=0x0020] Jun 08 07:31:12.532186 AI360 kernel: ath12k_pci 0000:c2:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0xfe980b00 flags=0x0020] Jun 08 07:31:12.532237 AI360 kernel: ath12k_pci 0000:c2:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0xfe980c00 flags=0x0020] Jun 08 07:31:12.532288 AI360 kernel: AMD-Vi: IOMMU Event log restarting Jun 08 07:31:12.627163 AI360 kernel: mhi mhi0: Requested to power ON Jun 08 07:31:12.627308 AI360 kernel: mhi mhi0: Power on setup success Jun 08 07:32:42.923214 AI360 kernel: mhi mhi0: MHI did not load image over BHI, ret: -5 Jun 08 07:32:42.924008 AI360 kernel: ath12k_pci 0000:c2:00.0: failed to set mhi state: POWER_ON(2) Jun 08 07:32:42.924245 AI360 kernel: ath12k_pci 0000:c2:00.0: failed to start mhi: -110 Jun 08 07:35:56.055573 AI360 kernel: ath12k_pci 0000:c2:00.0: failed to send WMI_START_SCAN_CMDID Jun 08 07:35:56.056269 AI360 kernel: ath12k_pci 0000:c2:00.0: failed to start hw scan: -108 Jun 08 07:45:36.703208 AI360 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jun 08 07:45:41.075220 AI360 kernel: rfkill: input handler enabled Jun 08 07:45:53.291491 AI360 kernel: ath12k_pci 0000:c2:00.0: failed to submit WMI_VDEV_DELETE_CMDID Jun 08 07:45:53.309847 AI360 kernel: ath12k_pci 0000:c2:00.0: failed to delete WMI vdev 1: -108 Jun 08 07:45:53.345825 AI360 kernel: list_del corruption. next->prev should be ffff8a4f0fc69950, but was ffff8a4f0c33de50. (next=ffff8a4f0c33de50) Jun 08 07:45:53.345879 AI360 kernel: ------------[ cut here ]------------ Jun 08 07:45:53.345888 AI360 kernel: kernel BUG at lib/list_debug.c:65! -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: LENOVO product_name: 21M1001VUS product_version: ThinkPad T14s Gen 6 chassis_vendor: LENOVO chassis_version: None bios_vendor: LENOVO bios_version: R2NET36W (1.10 ) board_vendor: LENOVO board_name: 21M1001VUS board_version: SDK0T76576 WIN ** Configuration for modprobe: blacklist microcode blacklist arkfb blacklist aty128fb blacklist atyfb blacklist radeonfb blacklist cirrusfb blacklist cyber2000fb blacklist kyrofb blacklist matroxfb_base blacklist mb862xxfb blacklist neofb blacklist pm2fb blacklist pm3fb blacklist s3fb blacklist savagefb blacklist sisfb blacklist tdfxfb blacklist tridentfb blacklist vt8623fb options snd_pcsp index=-2 options cx88_alsa index=-2 options snd_atiixp_modem index=-2 options snd_intel8x0m index=-2 options snd_via82xx_modem index=-2 options bonding max_bonds=0 options dummy numdummies=0 options ifb numifbs=0 ** Network interface configuration: *** /etc/network/interfaces: source /etc/network/interfaces.d/* auto lo iface lo inet loopback ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix Root Complex [1022:1507] Subsystem: Lenovo Strix Root Complex [17aa:50f0] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- 00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Strix IOMMU [1022:1508] Subsystem: Lenovo Strix IOMMU [17aa:50f0] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 26 Capabilities: <access denied> 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix Dummy Host Bridge [1022:1509] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- IOMMU group: 1 00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Strix PCIe USB4 Bridge [1022:150a] (prog-if 00 [Normal decode]) Subsystem: Advanced Micro Devices, Inc. [AMD] Strix PCIe USB4 Bridge [1022:150a] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin ? routed to IRQ 34 IOMMU group: 2 Bus: primary=00, secondary=01, subordinate=60, sec-latency=0 I/O behind bridge: 6000-9fff [size=16K] [16-bit] Memory behind bridge: 98000000-afffffff [size=384M] [32-bit] Prefetchable memory behind bridge: 3000000000-4fffffffff [size=128G] [32-bit] Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR- BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: <access denied> Kernel driver in use: pcieport 00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Strix PCIe USB4 Bridge [1022:150a] (prog-if 00 [Normal decode]) Subsystem: Advanced Micro Devices, Inc. [AMD] Strix PCIe USB4 Bridge [1022:150a] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin ? routed to IRQ 35 IOMMU group: 3 Bus: primary=00, secondary=61, subordinate=c0, sec-latency=0 I/O behind bridge: 2000-5fff [size=16K] [16-bit] Memory behind bridge: 80000000-97ffffff [size=384M] [32-bit] Prefetchable memory behind bridge: 1000000000-2fffffffff [size=128G] [32-bit] Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR- BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: <access denied> Kernel driver in use: pcieport 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix Dummy Host Bridge [1022:1509] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- IOMMU group: 4 00:02.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Strix GPP Bridge [1022:150b] (prog-if 00 [Normal decode]) Subsystem: Lenovo Strix GPP Bridge [17aa:50f0] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin ? routed to IRQ 36 IOMMU group: 5 Bus: primary=00, secondary=c1, subordinate=c1, sec-latency=0 I/O behind bridge: [disabled] [32-bit] Memory behind bridge: b0e00000-b0efffff [size=1M] [32-bit] Prefetchable memory behind bridge: [disabled] [64-bit] Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR- BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: <access denied> Kernel driver in use: pcieport 00:02.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Strix GPP Bridge [1022:150b] (prog-if 00 [Normal decode]) Subsystem: Lenovo Strix GPP Bridge [17aa:50f0] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort+ <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin ? routed to IRQ 37 IOMMU group: 6 Bus: primary=00, secondary=c2, subordinate=c2, sec-latency=0 I/O behind bridge: [disabled] [32-bit] Memory behind bridge: b0600000-b07fffff [size=2M] [32-bit] Prefetchable memory behind bridge: [disabled] [64-bit] Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort+ <MAbort- <SERR- <PERR- BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: <access denied> Kernel driver in use: pcieport 00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix Dummy Host Bridge [1022:1509] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- IOMMU group: 7 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix Dummy Host Bridge [1022:1509] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- IOMMU group: 8 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Strix Internal GPP Bridge to Bus [C:A] [1022:150c] (prog-if 00 [Normal decode]) Subsystem: Lenovo Strix Internal GPP Bridge to Bus [C:A] [17aa:50f0] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 38 IOMMU group: 9 Bus: primary=00, secondary=c3, subordinate=c3, sec-latency=0 I/O behind bridge: 1000-1fff [size=4K] [16-bit] Memory behind bridge: b0000000-b04fffff [size=5M] [32-bit] Prefetchable memory behind bridge: 5000000000-50107fffff [size=264M] [32-bit] Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR- BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: <access denied> Kernel driver in use: pcieport 00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Strix Internal GPP Bridge to Bus [C:A] [1022:150c] (prog-if 00 [Normal decode]) Subsystem: Lenovo Strix Internal GPP Bridge to Bus [C:A] [17aa:50f0] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 39 IOMMU group: 10 Bus: primary=00, secondary=c4, subordinate=c4, sec-latency=0 I/O behind bridge: [disabled] [32-bit] Memory behind bridge: b0c00000-b0dfffff [size=2M] [32-bit] Prefetchable memory behind bridge: 5010800000-50108fffff [size=1M] [32-bit] Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR- BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: <access denied> Kernel driver in use: pcieport 00:08.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Strix Internal GPP Bridge to Bus [C:A] [1022:150c] (prog-if 00 [Normal decode]) Subsystem: Lenovo Strix Internal GPP Bridge to Bus [C:A] [17aa:50f0] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 40 IOMMU group: 11 Bus: primary=00, secondary=c5, subordinate=c5, sec-latency=0 I/O behind bridge: [disabled] [32-bit] Memory behind bridge: b0800000-b0bfffff [size=4M] [32-bit] Prefetchable memory behind bridge: [disabled] [64-bit] Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR- BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: <access denied> Kernel driver in use: pcieport 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 71) Subsystem: Lenovo FCH SMBus Controller [17aa:50f0] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- IOMMU group: 12 Kernel driver in use: piix4_smbus Kernel modules: i2c_piix4, sp5100_tco 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51) Subsystem: Lenovo FCH LPC Bridge [17aa:50f0] Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 IOMMU group: 12 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix Data Fabric; Function 0 [1022:16f8] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- IOMMU group: 13 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix Data Fabric; Function 1 [1022:16f9] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- IOMMU group: 13 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix Data Fabric; Function 2 [1022:16fa] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- IOMMU group: 13 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix Data Fabric; Function 3 [1022:16fb] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- IOMMU group: 13 Kernel driver in use: k10temp Kernel modules: k10temp 00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix Data Fabric; Function 4 [1022:16fc] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- IOMMU group: 13 00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix Data Fabric; Function 5 [1022:16fd] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- IOMMU group: 13 00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix Data Fabric; Function 6 [1022:16fe] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- IOMMU group: 13 00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix Data Fabric; Function 7 [1022:16ff] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- IOMMU group: 13 c1:00.0 Non-Volatile memory controller [0108]: KIOXIA Corporation NVMe SSD Controller XG8 [1e0f:0010] (rev 01) (prog-if 02 [NVM Express]) Subsystem: KIOXIA Corporation NVMe SSD Controller XG8 [1e0f:0001] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 25 IOMMU group: 14 Region 0: Memory at b0e00000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: nvme Kernel modules: nvme c2:00.0 Network controller [0280]: Qualcomm Technologies, Inc WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800] [17cb:1107] (rev 01) Subsystem: Lenovo WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800] [17aa:e0e6] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort+ <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin ? routed to IRQ 108 IOMMU group: 15 Region 0: Memory at b0600000 (64-bit, non-prefetchable) [size=2M] Capabilities: <access denied> Kernel driver in use: ath12k_pci Kernel modules: ath12k c3:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Strix [Radeon 880M / 890M] [1002:150e] (rev d2) Subsystem: Lenovo Strix [Radeon 880M / 890M] [17aa:50f0] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 101 IOMMU group: 16 Region 0: Memory at 5000000000 (64-bit, prefetchable) [size=256M] Region 2: Memory at b0000000 (64-bit, prefetchable) [size=2M] Region 4: I/O ports at 1000 [size=256] Region 5: Memory at b0400000 (32-bit, non-prefetchable) [size=512K] Capabilities: <access denied> Kernel driver in use: amdgpu Kernel modules: amdgpu c3:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt Radeon High Definition Audio Controller [1002:1640] Subsystem: Lenovo Rembrandt Radeon High Definition Audio Controller [17aa:50f0] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 106 IOMMU group: 17 Region 0: Memory at b04c8000 (32-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel c3:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Strix CCP/ASP [1022:17e0] Subsystem: Lenovo Strix CCP/ASP [17aa:50f0] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin C routed to IRQ 103 IOMMU group: 18 Region 2: Memory at b0300000 (32-bit, non-prefetchable) [size=1M] Region 5: Memory at b04cc000 (32-bit, non-prefetchable) [size=8K] Capabilities: <access denied> Kernel driver in use: ccp Kernel modules: ccp c3:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:151e] (prog-if 30 [XHCI]) Subsystem: Lenovo Device [17aa:50f0] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin D routed to IRQ 92 IOMMU group: 19 Region 0: Memory at b0200000 (64-bit, non-prefetchable) [size=1M] Capabilities: <access denied> Kernel driver in use: xhci_hcd Kernel modules: xhci_pci c3:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor [1022:15e2] (rev 70) Subsystem: Lenovo ACP/ACP3X/ACP6x Audio Coprocessor [17aa:50f0] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 101 IOMMU group: 20 Region 0: Memory at b0480000 (32-bit, non-prefetchable) [size=256K] Region 2: Memory at 5010000000 (64-bit, prefetchable) [size=8M] Capabilities: <access denied> Kernel driver in use: snd_acp_pci Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_rembrandt c3:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h/19h/1ah HD Audio Controller [17aa:50f0] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 107 IOMMU group: 21 Region 0: Memory at b04c0000 (32-bit, non-prefetchable) [size=32K] Capabilities: <access denied> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel c4:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Strix PCIe Dummy function [1022:150d] Subsystem: Advanced Micro Devices, Inc. [AMD] Strix PCIe Dummy function [1022:150d] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- IOMMU group: 22 Capabilities: <access denied> c4:00.1 Signal processing controller [1180]: Advanced Micro Devices, Inc. [AMD] Strix Neural Processing Unit [1022:17f0] (rev 10) Subsystem: Lenovo Strix Neural Processing Unit [17aa:50f0] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 255 IOMMU group: 23 Region 0: Memory at b0c00000 (32-bit, non-prefetchable) [disabled] [size=1M] Region 1: Memory at b0d00000 (32-bit, non-prefetchable) [disabled] [size=8K] Region 2: Memory at 5010800000 (64-bit, prefetchable) [disabled] [size=512K] Region 4: Memory at b0d03000 (32-bit, non-prefetchable) [disabled] [size=4K] Region 5: Memory at b0d02000 (32-bit, non-prefetchable) [disabled] [size=4K] Capabilities: <access denied> c5:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:151f] (prog-if 30 [XHCI]) Subsystem: Lenovo Device [17aa:50f0] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 58 IOMMU group: 24 Region 0: Memory at b0800000 (64-bit, non-prefetchable) [size=1M] Capabilities: <access denied> Kernel driver in use: xhci_hcd Kernel modules: xhci_pci c5:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:151a] (prog-if 30 [XHCI]) Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:151a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin B routed to IRQ 95 IOMMU group: 25 Region 0: Memory at b0900000 (64-bit, non-prefetchable) [size=1M] Capabilities: <access denied> Kernel driver in use: xhci_hcd Kernel modules: xhci_pci c5:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:151b] (prog-if 30 [XHCI]) Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:151b] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin C routed to IRQ 97 IOMMU group: 26 Region 0: Memory at b0a00000 (64-bit, non-prefetchable) [size=1M] Capabilities: <access denied> Kernel driver in use: xhci_hcd Kernel modules: xhci_pci c5:00.5 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:151c] (prog-if 40 [USB4 Host Interface]) Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:151c] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin D routed to IRQ 41 IOMMU group: 27 Region 0: Memory at b0b00000 (64-bit, non-prefetchable) [size=512K] Capabilities: <access denied> Kernel driver in use: thunderbolt Kernel modules: thunderbolt c5:00.6 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:151d] (prog-if 40 [USB4 Host Interface]) Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:151d] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 58 IOMMU group: 28 Region 0: Memory at b0b80000 (64-bit, non-prefetchable) [size=512K] Capabilities: <access denied> Kernel driver in use: thunderbolt Kernel modules: thunderbolt ** USB devices: Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 0489:e0fc Foxconn / Hon Hai Bus 003 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 003 Device 002: ID 06cb:00f9 Synaptics, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:1199 Bison Electronics Inc. Integrated Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- System Information: Debian Release: 12.11 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.12.22+bpo-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-6.12.27+bpo-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.142+deb12u3 ii kmod 30+20221128-1 ii linux-base 4.9 Versions of packages linux-image-6.12.27+bpo-amd64 recommends: ii apparmor 3.0.8-3 Versions of packages linux-image-6.12.27+bpo-amd64 suggests: pn debian-kernel-handbook <none> ii firmware-linux-free 20200122-1 ii grub-efi-amd64 2.06-13+deb12u1 pn linux-doc-6.12 <none> Versions of packages linux-image-6.12.27+bpo-amd64 is related to: ii firmware-amd-graphics 20250410-2~bpo12+1 ii firmware-atheros 20250410-2~bpo12+1 pn firmware-bnx2 <none> pn firmware-bnx2x <none> pn firmware-brcm80211 <none> pn firmware-cavium <none> pn firmware-cirrus <none> pn firmware-intel-graphics <none> pn firmware-intel-misc <none> pn firmware-intel-sound <none> pn firmware-ipw2x00 <none> pn firmware-ivtv <none> pn firmware-iwlwifi <none> pn firmware-libertas <none> pn firmware-marvell-prestera <none> pn firmware-mediatek <none> pn firmware-misc-nonfree <none> pn firmware-myricom <none> pn firmware-netronome <none> pn firmware-netxen <none> pn firmware-nvidia-graphics <none> pn firmware-qcom-soc <none> pn firmware-qlogic <none> ii firmware-realtek 20250410-2~bpo12+1 pn firmware-samsung <none> pn firmware-siano <none> pn firmware-ti-connectivity <none> pn xen-hypervisor <none> -- no debconf information
[toc] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2025-06-11 23:00 +0200 |
| Subject | Processed: Re: Bug#1107521: linux-image-6.12.27+bpo-amd64: ath12k_pci errors and eventual kernel panic starting with linux-image-6.12.27+bpo-amd64 |
| Message-ID | <KWAI9-9TzI-1@gated-at.bofh.it> |
| In reply to | #87911 |
Processing control commands: > tag -1 +moreinfo Bug #1107521 [src:linux] linux-image-6.12.27+bpo-amd64: ath12k_pci errors and eventual kernel panic starting with linux-image-6.12.27+bpo-amd64 Added tag(s) moreinfo. -- 1107521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107521 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [next] | [standalone]
| From | Uwe Kleine-König <u.kleine-koenig@baylibre.com> |
|---|---|
| Date | 2025-06-11 23:00 +0200 |
| Message-ID | <KWAI9-9TzI-3@gated-at.bofh.it> |
| In reply to | #87911 |
[Multipart message — attachments visible in raw view] — view raw
Control: tag -1 +moreinfo Hello Matt, On Sun, Jun 08, 2025 at 08:00:43AM -0700, Matt Mower wrote: > After updating from linux-image-6.12.22+bpo-amd64 to linux-image-6.12.27+bpo- > amd64, I am seeing lots of IO_PAGE_FAULT events for device ath12k_pci, and > twice my system has completely frozen. There are a few ath12k patches between 6.12.22 and 6.12.27 and a few more in later stable releases in the 6.12.x series. Can you please test on the latest 6.12 kernel? There is currently no backport kernel for that version, but in my experience the kernel from testing should install fine on a stable box. If the issue also happens on 6.12.32, someone has to bring that forward to upstream's attention. Best regards Uwe
[toc] | [prev] | [next] | [standalone]
| From | Matt Mower <mowerm@gmail.com> |
|---|---|
| Date | 2025-06-12 22:50 +0200 |
| Message-ID | <KWX21-a7WU-1@gated-at.bofh.it> |
| In reply to | #87911 |
[Multipart message — attachments visible in raw view] — view raw
After several suspends and plenty of uptime on battery, I'm fairly confident that linux-image-6.12.12+bpo-amd64_6.12.12-1~bpo12+1_amd64 paired with firmware-atheros_20250410-2~bpo12+1_all is stable. There are only 2 commits to the ath12k driver between 6.12.12 and 6.12.22: 44de00e8bc8f wifi: ath12k: fix handling of 6 GHz rules 425f6a38173b wifi: ath12k: fix tx power, max reg power update to firmware So, I'll next test 6.12.22 with reverts of one or both of these. On Wed, Jun 11, 2025 at 9:50 PM Matt Mower <mowerm@gmail.com> wrote: > For what it's worth, if you check the replies after the original report, > you can see that I tested 6.12.32 as well as 6.12.27 with ath12k patches > reverted. Unfortunately, I can reproduce it in 6.12.22 now as well; the bug > only seems to appear when my laptop is not connected to a power source. I > reproduce it most often when the device shuts down or goes to sleep, at > which point it freezes completely. I snapped a picture when I saw more > debugging information that normal on the screen (attached). I've tried > downgrading to firmware-atheros_20250410-2~bpo12+1_all as well (dmesg > reports firmware fw_version 0x100301e1 fw_build_timestamp 2023-12-06 > 04:05), and that didn't resolve the issue. > > I'm continuing to test older kernel and firmware versions until I find > something stable. > > On Wed, Jun 11, 2025 at 1:49 PM Uwe Kleine-König < > u.kleine-koenig@baylibre.com> wrote: > >> Control: tag -1 +moreinfo >> >> Hello Matt, >> >> On Sun, Jun 08, 2025 at 08:00:43AM -0700, Matt Mower wrote: >> > After updating from linux-image-6.12.22+bpo-amd64 to >> linux-image-6.12.27+bpo- >> > amd64, I am seeing lots of IO_PAGE_FAULT events for device ath12k_pci, >> and >> > twice my system has completely frozen. >> >> There are a few ath12k patches between 6.12.22 and 6.12.27 and a few >> more in later stable releases in the 6.12.x series. Can you please test >> on the latest 6.12 kernel? There is currently no backport kernel for >> that version, but in my experience the kernel from testing should >> install fine on a stable box. >> >> If the issue also happens on 6.12.32, someone has to bring that forward >> to upstream's attention. >> >> Best regards >> Uwe >> >
[toc] | [prev] | [next] | [standalone]
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2025-06-14 21:40 +0200 |
| Message-ID | <KXETn-aztx-3@gated-at.bofh.it> |
| In reply to | #87951 |
Hi Matt, On Thu, Jun 12, 2025 at 01:46:03PM -0700, Matt Mower wrote: > After several suspends and plenty of uptime on battery, I'm fairly > confident that linux-image-6.12.12+bpo-amd64_6.12.12-1~bpo12+1_amd64 paired > with firmware-atheros_20250410-2~bpo12+1_all is stable. There are only 2 > commits to the ath12k driver between 6.12.12 and 6.12.22: > > 44de00e8bc8f wifi: ath12k: fix handling of 6 GHz rules > 425f6a38173b wifi: ath12k: fix tx power, max reg power update to firmware > > So, I'll next test 6.12.22 with reverts of one or both of these. Looking forward to see the results, can you then please remove the moreinfo tag on the bug when providing the information? This brings the bug more prominently back on the radar. (And having identified the breaking commit helps filling a proper bugreport upstream). Regards, Salvatore
[toc] | [prev] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2025-06-16 08:30 +0200 |
| Subject | Processed: Re: Bug#1107521: linux-image-6.12.27+bpo-amd64: ath12k_pci errors and eventual kernel panic starting with linux-image-6.12.27+bpo-amd64 |
| Message-ID | <KYbvX-aU8h-1@gated-at.bofh.it> |
| In reply to | #87911 |
Processing control commands: > tag -1 -moreinfo Bug #1107521 [src:linux] linux-image-6.12.27+bpo-amd64: ath12k_pci errors and eventual kernel panic starting with linux-image-6.12.27+bpo-amd64 Removed tag(s) moreinfo. -- 1107521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107521 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2025-06-18 11:20 +0200 |
| Subject | Processed: Re: Bug#1107521: linux-image-6.12.27+bpo-amd64: ath12k_pci errors and eventual kernel panic starting with linux-image-6.12.27+bpo-amd64 |
| Message-ID | <KYX7z-boyj-11@gated-at.bofh.it> |
| In reply to | #87911 |
Processing control commands: > found -1 6.12.12-1 Bug #1107521 [src:linux] linux-image-6.12.27+bpo-amd64: ath12k_pci errors and eventual kernel panic starting with linux-image-6.12.27+bpo-amd64 Marked as found in versions linux/6.12.12-1. > notfound -1 6.12.27-1~bpo12+1 Bug #1107521 [src:linux] linux-image-6.12.27+bpo-amd64: ath12k_pci errors and eventual kernel panic starting with linux-image-6.12.27+bpo-amd64 No longer marked as found in versions linux/6.12.27-1~bpo12+1. -- 1107521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107521 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [next] | [standalone]
| From | Matt Mower <mowerm@gmail.com> |
|---|---|
| Date | 2025-06-25 07:20 +0200 |
| Message-ID | <L1qI9-cZfq-1@gated-at.bofh.it> |
| In reply to | #87911 |
[Multipart message — attachments visible in raw view] — view raw
> OK, so I suggest we wait a bit for the problem to happen on 6.15. I have not reproduced this issue on 6.15.2 or 6.15.3. I tested 6.12.34 tonight and the issue still exists. I have not found changes that can be cherry-picked to resolve the issue in 6.12.x. > Do you want to care for that then? I would appreciate some help with this so that I don't report incorrectly. Happy to continue providing information, but if someone could help with initiating the bug report, that would be helpful.
[toc] | [prev] | [next] | [standalone]
| From | Robin Murphy <robin.murphy@arm.com> |
|---|---|
| Date | 2025-06-27 12:40 +0200 |
| Subject | Bug#1107521: ath12k_pci errors and loss of connectivity in 6.12.y branch |
| Message-ID | <L2eEV-dwDG-9@gated-at.bofh.it> |
| In reply to | #87911 |
+Vasant On 2025-06-27 6:39 am, Baochen Qiang wrote: > [+ IOMMU list] > > On 6/27/2025 12:21 AM, Matt Mower wrote: >> Dear maintainer, >> >> I have been experiencing lost network connection with the ath12k_pci driver >> in the linux-6.12.y kernel branch. Often, when the issue occurs, the >> network does not recover until I reboot the computer. A full report of the >> errors I encounter, the symptoms that arise, and several dmesg attachments >> are in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107521 . I have >> attached a dmesg from 6.12.34 for convenience. The short summary is: >> >> 1. I started noticing log lines like the following soon after boot when I >> updated from 6.12.22 to 6.12.27. After these events occur, the network goes >> down and often does not come back up. >> ath12k_pci 0000:c2:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT >> domain=0x0010 address=0xfea00000 flags=0x0020] >> 2. I was able to reproduce this issue very rarely in 6.12.12 and 6.12.22. >> The issue always occurs soon after boot in 6.12.27, 6.12.30, 6.12.33, and >> 6.12.34. >> 3. I have not reproduced the issue in 6.15.2 or 6.15.3. >> 4. In some cases, when shutting down the computer, a kernel bug caused my >> computer to hang. I haven't determined whether this is related to the issue >> above or an independent issue. Search the bug report >> for PXL_20250611_140820085.jpg to see a picture of the kernel bug on my >> laptop screen. >> 5. I have tested two firmware versions: >> a. fw_version 0x1108811c fw_build_timestamp 2025-05-17 00:21 fw_build_id >> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.1.c5-00284.1-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 >> b. fw_version 0x100301e1 fw_build_timestamp 2023-12-06 04:05 fw_build_id >> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 >> >> Thanks, >> Matt >> > > I had a quick test with 6.12.27 kernel on both my Intel desktop and AMD RD but didn't hit > the issue. And I am using WLAN.HMT.1.1.c5-00284.1-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3. > > As mentioned in the Debian bug report, since reverting ath12k patches does not fix this > issue, maybe it comes from the IOMMU subsystem? Faults are usually still indicative of the client driver/subsystem doing something not quite right - racily performing dma_unmap before the device has actually finished making accesses; mapping the wrong size such that the device accesses off the end of the mapping (this can often run into another valid mapping so not necessarily fault); mapping the wrong DMA direction such that the device then tries to write to a read-only page. However I suppose it's not impossible that some fix to amd-iommu in that period might have changed its behaviour in a way that exacerbates things - Vasant, does this strike a chord with anything you're aware of? A couple more things I'd try on the ath12k side: firstly, boot with "iommu.strict=1" and see if that makes the faults any more frequent/reproducible; if a fault is fairly easily reproducible, then use the DMA API and/or IOMMU API tracepoints to compare the fault address to prior DMA mapping activity - that can usually reveal the nature of the bug enough to then know what to go looking for. I wouldn't put much significance in whatever happens *after* the fault - presumably the driver is assuming the blocked DMA write has completed, so then goes on to read some incomplete descriptor as if it were valid, and thus may fall over in all manner of entertaining ways on bogus data. Thanks, Robin.
[toc] | [prev] | [next] | [standalone]
| From | Matt Mower <mowerm@gmail.com> |
|---|---|
| Date | 2025-07-02 07:30 +0200 |
| Subject | Bug#1107521: ath12k_pci errors and loss of connectivity in 6.12.y branch |
| Message-ID | <L3YcF-eDSj-3@gated-at.bofh.it> |
| In reply to | #87911 |
> A couple more things I'd try on the ath12k side: firstly, boot with > "iommu.strict=1" and see if that makes the faults any more > frequent/reproducible; The issue is easy enough to reproduce in 6.12.27 onward and I may be mistaken about the rarity in 6.12.22; I reproduced it relatively quickly in .22 today, so if this was the primary purpose for setting iommu.strict=1, then testing with or without strict works. FWIW, I did test iommu.strict=1 with 6.15.3 and still have not reproduced this issue there. > if a fault is fairly easily reproducible, then > use the DMA API and/or IOMMU API tracepoints to compare the fault > address to prior DMA mapping activity - that can usually reveal the > nature of the bug enough to then know what to go looking for. This is unfamiliar territory for me, so I hope the following is at least close to what you requested. If not, happy to provide more test results based on a set of instructions. Here's what I did: 1. Set CONFIG_DMA_API_DEBUG=y 2. Set kernel command line to: iommu.strict=1 log_buf_len=100M dma_debug_driver=ath12k_pci trace_event=dma:*,iommu:* 3. Booted and waited for page fault, then cat'd /sys/kernel/tracing/trace to a file. Additionally, though I'm pretty sure this is irrelevant now, I added logging after each dma_map_single() in the ath12k driver to print the function name and resultant address to the kernel log. Comparing the addresses of several io_page_fault lines in the trace and in the kernel log, they line up. So, I'm hopeful this is on the right track. DMA/IOMMU trace: https://cmphys.com/ath12k/iommu_dma_trace-20250701.log Kernel log with additional logging: https://cmphys.com/ath12k/dmesg-6.12.35-20250701.log Diff showing extra logging added to v6.12.35: https://cmphys.com/ath12k/ath12k-extra-logging-6.12.35-20250701.diff Thanks, Matt
[toc] | [prev] | [next] | [standalone]
| From | Matt Mower <mowerm@gmail.com> |
|---|---|
| Date | 2025-07-02 17:00 +0200 |
| Subject | Bug#1107521: ath12k_pci errors and loss of connectivity in 6.12.y branch |
| Message-ID | <L476i-eJCp-5@gated-at.bofh.it> |
| In reply to | #87911 |
> Matt, could you help enable verbose ath12k log to verify my guess? Here are kernel logs with ath12k debugging enabled: 1. WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 https://cmphys.com/ath12k/dmesg-6.12.35-ath12kdebug-fw0x100301e1-20250702.log 2. WLAN.HMT.1.1.c5-00284.1-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 https://cmphys.com/ath12k/dmesg-6.12.35-ath12kdebug-fw0x1108811c-20250702.log I captured these after setting CONFIG_ATH12K_DEBUG=y and running "echo 0xffffffff > /sys/module/ath12k/parameters/debug_mask" during boot (using @reboot in crontab).
[toc] | [prev] | [next] | [standalone]
| From | Matt Mower <mowerm@gmail.com> |
|---|---|
| Date | 2025-08-17 18:40 +0200 |
| Subject | Bug#1107521: Info received (ath12k_pci errors and loss of connectivity in 6.12.y branch) |
| Message-ID | <LkOAh-8k1x-1@gated-at.bofh.it> |
| In reply to | #87911 |
Uwe and Salvatore, FYI, this bug affects the Trixie installer (and after installation, too). As soon as the Trixie installer reached the point of detecting network interfaces, my system completely froze with a blinking light on the caps lock key. This was not intermittent; it always happened when I retried. I was only able to proceed by removing firmware-atheros_20250410-2_all.deb from the installer ISO and then I could continue without WiFi during installation (I used a USB ethernet dongle). Now with Trixie installed, I have a stable system with my ath12k cherry-picks on top of stable 6.12 (e.g https://github.com/mdmower/linux/tree/mdm-6.12.41-ath12k ), but that doesn't help others. So, I wanted to make you two aware in case you see other reports of trouble with the ath12k firmware and/or driver in Trixie. Unfortunately, I haven't heard from Baochen Qiang since July 2. Matt
[toc] | [prev] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2025-11-23 23:50 +0100 |
| Subject | Bug#1107521: marked as done (linux-image-6.12.27+bpo-amd64: ath12k_pci errors and eventual kernel panic starting with linux-image-6.12.27+bpo-amd64) |
| Message-ID | <LUr46-ffBt-1@gated-at.bofh.it> |
| In reply to | #87911 |
[Multipart message — attachments visible in raw view] — view raw
Your message dated Sun, 23 Nov 2025 14:44:40 -0800 with message-id <CAPDiVH-S404i1O7J4EUTohx27Mbo4EaKeHK6tgXs2+1_HxmVtQ@mail.gmail.com> and subject line Re: ath12k_pci errors and loss of connectivity in 6.12.y branch has caused the Debian Bug report #1107521, regarding linux-image-6.12.27+bpo-amd64: ath12k_pci errors and eventual kernel panic starting with linux-image-6.12.27+bpo-amd64 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1107521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107521 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [next] | [standalone]
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2025-11-24 06:30 +0100 |
| Subject | Bug#1107521: closing 1107521 |
| Message-ID | <LUxjb-fk0O-3@gated-at.bofh.it> |
| In reply to | #87911 |
close 1107521 6.12.48-1 thanks
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web