[Bug 196273] New: Loss of video output and system freezes *ERROR* Couldn't read SADs: 0

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Tue Jul 4 17:49:22 UTC 2017


https://bugzilla.kernel.org/show_bug.cgi?id=196273

            Bug ID: 196273
           Summary: Loss of video output and system freezes *ERROR*
                    Couldn't read SADs: 0
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.12.0
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri at kernel-bugs.osdl.org
          Reporter: olaf at seldiame.net
        Regression: No

Created attachment 257353
  --> https://bugzilla.kernel.org/attachment.cgi?id=257353&action=edit
lspci output

I have a Gentoo system with kernel 4.12.0 and after a while the display goes
black. After of that the system is accessible via ssh, but any intent of
restart the xserver results in a freeze.

I have to reset the system in order to have a working systems.

This situation repeats very often in different time lapses.


The video card is an AMD Radeon R9 380 (sapphire nitro).

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Tonga
PRO [Radeon R9 285/380] (rev f1)


I have downloaded and tested with the new firmware from 

http://people.freedesktop.org/~agd5f/radeon_ucode/tonga/

Seems to be a problem with amdgpu driver.

I can see a variety of errors in dmesg:

[    8.088336] AMD-Vi: Event logged [
[    8.088337] IO_PAGE_FAULT device=01:00.0 domain=0x000f
address=0x000000f4001a8300 flags=0x0010]


[    8.642870] amdgpu: [powerplay] Can't find requested voltage id in
vdd_dep_on_sclk table!



This message seems to be the last before the video goes black.

drm:0xffffffffa00d4f5d] *ERROR* Couldn't read SADs: 0

I can provide any additional information required. Thanks for your help in
advance.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.


More information about the dri-devel mailing list