I have done some digging and trial and error with AMD’s amdgpu DC documentation and I found booting with amdgpu.abmlevel=0 amdgpu.dcdebugmask=0x410 kernel parameters to be an effective workaround. The problem is that this disables any and all panel power-saving features, and I can tell… my laptop can hardly reach 3 hours of work on a charge in this state.
Have you reported that as a bug? I think this is the right place:
For what it’s worth, I have not observed that particular problem.
1 Like
I actually found the bug there - I will get around the posting the workaround that I found there shortly, because I am not sure I have seen it.
That’s strange. Me and other people seem to have experienced it even at high severity levels, while some seem to be completely unaffected. I guess it needs some weird edge case ro activate itself, or something like that
It has started happening a couple times a day, and my usage of the laptop is if anything less intensive than is was two weeks ago. This is the amdgpu “flip_done timed out” bug. I suspect the system is overheating; I haven’t heard the roar of the fans in awhile, and everytime it happens I have noticed that the ones for the GPU are not spinning. Less than a year old, so if that truly is the case, I guess that’s a datapoint for the “build quality” question of the OP.
EDIT: installed fw-fanctrl and nope, that’s not it - the fans work fine. Having the fan die on my Framework 13 has made me a little sensitive to this failure mode.
that’s more firmware/software bug, though. I had done some stupid things with the AMD drivers on windows, as well. You can’t exactly blame Framework for that. A Dell of equivalence will probably also run you some insane driver shenanigan, one way or another.
Yes, that is sadly the par for course on AMD platforms 