[Bug 200869] New: UVD cause amdgpu crash on CIK: [amdgpu]] UVD not responding, trying to reset the VCPU
https://bugzilla.kernel.org/show_bug.cgi?id=200869
Bug ID: 200869 Summary: UVD cause amdgpu crash on CIK: [amdgpu]] UVD not responding, trying to reset the VCPU Product: Drivers Version: 2.5 Kernel Version: 4.17.17 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri@kernel-bugs.osdl.org Reporter: janpieter.sollie@dommel.be Regression: No
Created attachment 277985 --> https://bugzilla.kernel.org/attachment.cgi?id=277985&action=edit attachments from the firepro machine
no VDPAU or VAAPI is possible with my firepro w5100 card, using a bonaire chip. The module needs to be loaded 3 times before the card is initialized successfully. 3 times is not a random number: it's every time like that: - First time, the UVD is failing, - Second time, the SDMA is failing - Third time, the GFX ring buffer test fails, but the GPU works when using HW acceleration, the GPU crashes again, and the process turns to zombie View kernel log for more details Attached: - dmesg log - Xorg log - ps aux
https://bugzilla.kernel.org/show_bug.cgi?id=200869
--- Comment #1 from Janpieter Sollie (janpieter.sollie@dommel.be) --- Small update:
When booting the module with the following parameters: amdgpu si_support=0 gpu_recovery=1 dpm=1 dc=0
I still need to load/unload the module 3 times, but it works for non-1080 videos. For 1080 videos, the mplayer already draws a black screen (didn't do that before), but does not show anything in the black window. Killing the mplayer process with kill -9 also kills the process properly. These steps do not result in any extra information in dmesg, though.
https://bugzilla.kernel.org/show_bug.cgi?id=200869
Janpieter Sollie (janpieter.sollie@dommel.be) changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID
--- Comment #2 from Janpieter Sollie (janpieter.sollie@dommel.be) --- 2nd update: after a double check of /sys/module/amdgpu, it turned out that the parameters for amdgpu were not applied at all when put in /etc/modprobe.d/options. I turned lilo into the following startup string: amdgpu.dc=1 amdgpu.audio=1 amdgpu.si_support=0 which seems to work properly. Sorry for the incorrect bug reporting.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠bugzilla.kernel.org