[Bug 85421] radeon stalled, GPU lockup, reset and failed on resume; crashed by firefox.
bugzilla-daemon at bugzilla.kernel.org
bugzilla-daemon at bugzilla.kernel.org
Tue Mar 24 09:19:52 PDT 2015
https://bugzilla.kernel.org/show_bug.cgi?id=85421
--- Comment #37 from EmanueL Czirai <emanueLczirai at cryptoLab.net> ---
Created attachment 172011
--> https://bugzilla.kernel.org/attachment.cgi?id=172011&action=edit
instant blanking without recovery when radeon.lockup_timeout=20
I accidentally added kernel param: radeon.lockup_timeout=20
which made it blank in firefox without being locked up or frozen first, and
remained blank, but i was able to ctrl+alt+del of course.
But this tells me that the (soft?)reset gpu thing isn't working. Is there a way
to make it work?
If that doesn't work normally, that explains why when it really locks up, it
can't get back to life again unless a warm boot happens. If this would work,
then I assume it would be able to recover from the current issue being
described in this thread.
the log for this case is attached (search for: 20msec )
the problem i guess are these:
Mar 24 17:00:42 manji kernel: [drm:radeon_dp_link_train] *ERROR* displayport
link status failed
Mar 24 17:00:42 manji kernel: [drm:radeon_dp_link_train] *ERROR* clock recovery
failed
btw the correct param I wanted was: radeon.lockup_timeout=20000 for 20 sec.
and by now I have also added some extra kernel params:
nohz=on rcu_nocbs=1-3 pcie_aspm=force radeon.audio=0
radeon.lockup_timeout=20000 radeon.test=0 radeon.agpmode=-1 radeon.benchmark=0
radeon.tv=0 radeon.hard_reset=1 radeon.aspm=1 radeon.msi=1 radeon.pcie_gen2=-1
radeon.no_wb=1 radeon.dynclks=1 radeon.r4xx_atom=0 radeonfb radeon.fastfb=1
radeon.modeset=1 radeon.dpm=1 radeon.runpm=1
which still allow me to reproduce the issue described in the previous comment.
--
You are receiving this mail because:
You are watching the assignee of the bug.
More information about the dri-devel
mailing list