You are not logged in.
Checking out if others with AMD Ryzen family of mobile APUs are having the same issue.
Had to recover the installation by booting ISO and reverting to linux-6.1.12.
Offline
F2FS root? https://bugs.archlinux.org/task/77596
Moving to [testing]
Last edited by V1del (2023-02-22 12:24:22)
Offline
Nope, mine is just standard ext4. Seem to be related to amdgpu, the screen just went black.
Offline
This is the bug: https://bugs.archlinux.org/task/77595
There is already a patch, but it's not applied to testing package yet.
Offline
@The Loko Thanks, yes, I think that's the problem.
I will just wait for linux-6.2 in the stable repo. It is a very bad PR for AMD to have let such embarrassing bug slip through with kernel 6.2 released. It is strange that the issue already reported during the RC and yet they would still let it slip. Perhaps AMD engineering mindsets consider bricking an installation just a norm for those jumping on rolling update Linux distros.
Offline
You do realise it's not amd engineers that decide when / if a kernel is released as stable ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Yes, I do and I kinda understand it. Yet, such incident will hurt AMD platform stability and engineering execution capability. It happened on the Windows side, too. The market has been rather forgiving towards AMD for such mishaps.
Offline
https://lore.kernel.org/lkml/2023011407 … intel.com/ is the discussion about how to fix the issue correctly.
The fix from https://bugs.archlinux.org/task/77595 https://git.kernel.org/pub/scm/linux/ke … 8354a9f3c3 adds error recovery after the issue has occurred. It does not have Cc: stable@vger.kernel.org or a fixes entry so may not be applied to stable.
Edit:
Fixed by the Arch kernel maintainers in linux 6.2.1.arch1-1
Last edited by loqs (2023-02-26 04:40:31)
Offline