linux-kernel - Kernel bug after 6.1 bug ryzen

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <Z93RVS.RPMYFU5Y3A7F1@att.net>
Date: Sun, 04 May 2025 14:56:23 -0400
From: Steven J Abner <pheonix.sja@....net>
To: linux-kernel@...r.kernel.org
Subject: Kernel bug after 6.1 bug ryzen

 I introduced as amdgpu issue on 30 Apr, but believe it should be moved 
to kernel. This even effects my OS mainline kernel upgrade, tried 6.8.
 I'm on a AMD 2400g, Asrock B450, GCC14.2.0, Binutils 2.44. Successful 
builds of 5.15 and 6.1. Starting with 6.13.4 I encountered display 
blackouts, disconnection of gpu from monitor, with a working console. I 
got the same result downloading on a debian/ubuntu based OS's mainline 
upgrade of 6.8 running a 5.15 kernel. That's when I back-tracked and 
built 5.15 on new LFS system, which I got working, no issue. Proceeded 
to 6.1 using 5.15 config as baseline and got that working 100%. Used 
6.1 as baseline for 6.14 and same issues as before. I ruled out 
firmware since all 3 ran on 250410 download of firmware. Please note 
that on initial 5.15 build I did have to change kernel setting but 
major difference of it didn't disconnect the gpu as 6.1 didn't either. 
Screwy sequence of builds: 6.14, 6.1, OS 6.8, 5.15, 6.1, 6.14. Most of, 
if not all, I found same results using safe mode also. For 'working', 
ran X server with a program I created as test.
 Not sure how to help, other than not use 2400g :) I've seem to run out 
of ideas. But felt since this in OS mainline's upgrades I should try to 
get peoples attention.
Steve