New driver cause suddenly black screen and reboot
Before submitting your bug report:
< TODO: Drop this section >
- Check if your bug has already been reported here.
- For any logs, backtraces, etc - use code blocks
- As examples of good bug reports you may review one of these - #1698 (closed), #1536, #1734 (closed)
Otherwise, fill the requested information below. And please remove anything that doesn't apply to keep things readable :)
Brief summary of the problem:
< TODO: Describe what you are doing, what you expect and what you're seeing instead. How frequent is the issue? Is it a one time occurrence? Does it appear multiple times but randomly? Can you easily reproduce it?
"It doesn't work" usually is not a helpful description of an issue. The more detail about how things are going wrong, the better. >
Hardware description:
- CPU: AMD Ryzen 7 3700X
- GPU: AMD Readon RX 5700XT
- System Memory: 64GB
- Display(s): LG Electronics 34" 3440x1440 21:9
- Type of Display Connection: DP
System information:
- Distro name and Version: 20.04.4 LTS (Focal Fossa)
- Kernel version: Linux PowerPC 5.13.0-37-generic #42 (closed)~20.04.1-Ubuntu SMP Tue Mar 15 15:44:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
- Custom kernel: N/A
- AMD official driver version: 21.50.2
How to reproduce the issue:
The games which use Vulkan render may cause suddenly black screen and reboot after running around 15-60 mins.
Such as Elden Ring, Mafia, Humankind, Metro Exodus, Cyberpunk 2077 (I experienced this issue on these games).
The games which rely on OpenGL are not affected, for example, XPlane 11 Linux version, American Truck Simulator Linux version.
Web browsing, Online Videos such as Youtube, Netflix are not affected.
Mining programs that rely on OpenCL are not affected.
Attached files:
Screenshots/video files
N/A
Log files (for system lockups / game freezes / crashes)
- Dmesg log (full log)
- Xorg log
- Any other log
Activity
This issue hasn't had any activity since 2022-03-22. The AMD driver stack changes rapidly and contains lots of shared code across products so it's possible that it has already been fixed. Please upgrade to a current stable kernel and userspace stack and try again. If you still experience this issue with the latest driver stack, please capture relevant logging and open a new issue referring back to this one.
