[<prev] [next>] [day] [month] [year] [list]
Message-ID: <jsxWbRo1gYFzI7aJrbed9G_LN5oi0KAa-HWI7qiQF1o5Nch_7RFkRFlHAKpokpB6Too9hFXmIGHoT_mcuLHfowUKP3oV7BbyaNo4wfj_HOM=@pm.me>
Date: Fri, 13 Jun 2025 19:00:34 +0000
From: John Hall <johncowleyhall@...me>
To: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc: "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>
Subject: [REGRESSION] System hangs after few minutes on 6.12.30, works fine on 6.12.27
Hi,
I'm experiencing a regression where my system hangs after a few minutes when running kernel 6.12.30, but works perfectly fine on 6.12.27.
**System Information:**
- Hardware: AMD Ryzen 5 3600, ASRock B450 Gaming-ITX/ac motherboard
- GPU: AMD RX 6600 XT (amdgpu driver)
- RAM: 16GB
- Distribution: Debian (kernel 6.12.30-amd64)
**Problem:**
- 6.12.27: System runs stable indefinitely
- 6.12.30: System hangs completely after 2-5 minutes of normal operation
- Hang type: [FILL IN - complete freeze/partial response/etc.]
**Regression Range:**
- Working: 6.12.27-amd64
- Broken: 6.12.30-amd64
- Suspected range: 6.12.28 - 6.12.30
**Notable Issues in Logs:**
Both kernels show these issues (but only 6.12.30 hangs):
1. USB bandwidth errors: "usb 1-2: Not enough bandwidth for new device state"
2. AMD GPU SMU version mismatch: "SMU driver if version not matched"
3. ACPI _DSM evaluation failures
Since these exist in both working (6.12.27) and broken (6.12.30) kernels,
they don't appear to be the root cause.
**Attached:**
- boot-6.12.30-attempt.log (full boot log from 6.12.30)
The regression appears to be timing-dependent since the hang occurs after several minutes rather than immediately. Let me know if you need anything else, and thanks for your time!
Cheers,John
Content of type "text/html" skipped
View attachment "boot-6.12.30-attempt.log" of type "text/x-log" (349050 bytes)
Powered by blists - more mailing lists