Bug 1607146

Summary: Computer freezes and becomes complete unresponsive
Product: [Fedora] Fedora Reporter: jon <jon780>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: airlied, bskeggs, ewk, faber, hdegoede, ichavero, itamar, jarodwilson, jglisse, john.j5live, jonathan, josef, kernel-maint, leigh.orf, linville, mchehab, mjg59, steved
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-21 21:11:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg output after rebooting following issue
none
lspci output none

Description jon 2018-07-22 13:40:03 UTC
Created attachment 1469770 [details]
dmesg output after rebooting following issue

Description of problem:  Freezing, no input keyboard/mouse, numlock light "stuck", etc.


Version-Release number of selected component (if applicable):  appears to be related to amdgpu driver from dmesg


How reproducible:  Intermittent, happens usually 2-3 times per day.  


Steps to Reproduce:
1.  Boot 
2.  Open terminals, firefox, etc
3.  Wait

Actual results:


Expected results:


Additional info:
This problem started early in July.  Prior to that, this machine/installation had been stable for months with uptimes measured in weeks.  

Ryzen 1700X (replaced under RMA - not defective CPU)
MSI B350 Tomahawk Arctic
Using the following bootline:

BOOT_IMAGE=/boot/vmlinuz-4.17.6-200.fc28.x86_64 root=/dev/mapper/fedora_ssd_vg00-root ro resume=/dev/mapper/fedora_ssd_vg00-swap rd.lvm.lv=fedora_ssd_vg00/root rd.lvm.lv=fedora_ssd_vg00/swap idle=nomwait rcu_nocbs=0-15 rhgb quiet LANG=en_US.UTF-8

Comment 1 jon 2018-07-22 13:40:44 UTC
Created attachment 1469771 [details]
lspci output

Comment 2 jon 2018-08-06 01:45:20 UTC
Update:  I continued to experience the same behavior all the way up through 4.17.9-200.  I just upgraded to 4.17.11-200 and after booting the new kernel, I see the message repeatedly, but the system is no longer freezing yet:

[Sun Aug  5 16:49:40 2018] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:956

[Sun Aug  5 17:55:12 2018] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:956

[Sun Aug  5 16:50:56 2018] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:956

[Sun Aug  5 17:08:29 2018] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:956

[Sun Aug  5 17:17:33 2018] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:956

[Sun Aug  5 17:55:12 2018] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:956

[Sun Aug  5 20:01:04 2018] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:956

Comment 3 Justin M. Forbes 2019-01-29 16:26:13 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs.

Fedora 28 has now been rebased to 4.20.5-100.fc28.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29.

If you experience different issues, please open a new bug report for those.

Comment 4 Justin M. Forbes 2019-02-21 21:11:05 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.