FS#55611 - [linux] Display not working after suspend/resume with Radeon GPU and and Ryzen CPU without HT
            Attached to Project:
            Arch Linux
            
Opened by Oliver Mangold (omangold) - Wednesday, 13 September 2017, 07:24 GMT
Last edited by Toolybird (Toolybird) - Sunday, 28 May 2023, 06:13 GMT
          Opened by Oliver Mangold (omangold) - Wednesday, 13 September 2017, 07:24 GMT
Last edited by Toolybird (Toolybird) - Sunday, 28 May 2023, 06:13 GMT
| 
 | Details
                    Description: After suspend/resume X11 display is not working. Screen looks like snowing/static. In syslog various kernel, X11 and graphical application errors / core dumps appear. On most tries system can still be shutdown by pressing the power button. The kernel and mesa versions do not seem to matter much. Tried several and the behavior was the same. The weird thing is that it only happens when CPU hyperthreading is disabled in BIOS. With hyperthreading on it works. Additional info: * package version(s) linux 4.12.12-1 linux-lts 4.9.48-1 mesa 17.2.0-2 mesa 17.1.8-1 xorg-server 1.19.3-3 * hardware Ryzen 7 1800X Oland PRO [Radeon R7 240/340] * config and/or log files etc. GLX renderer info: AMD OLAND (DRM 2.50.0 / 4.12.12-1-ARCH, LLVM 4.0.1) See journal-errors.txt for relevant syslog messages. Steps to reproduce: - boot system with lightdm display manager - suspend system from lightdm menu - wake up system | 
              This task depends upon
              
              
            
            
          
            Closed by  Toolybird (Toolybird)
Sunday, 28 May 2023, 06:13 GMT
Reason for closing: No response
Additional comments about closing: Plus it's old and stale. If still an issue, please report upstream.
          
        Sunday, 28 May 2023, 06:13 GMT
Reason for closing: No response
Additional comments about closing: Plus it's old and stale. If still an issue, please report upstream.
 Comment by mattia (nTia89) - Sunday,
            27 February 2022, 13:55 GMT
            
            Comment by mattia (nTia89) - Sunday,
            27 February 2022, 13:55 GMT
          
           
          
              I cannot reproduce the issue. Is it still valid?
            
           
                       journal-errors.txt
                         journal-errors.txt