Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
[drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed #270
I get the following error message when the laptop boots on AC:
May 23 02:59:31 Lenovo-300-17ISK kernel: [ 26.336643] [drm:r600_ring_test [radeon]] ERROR radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD)
That is the default TLP configuration, unchanged. What i further tried out:
However, i noticed that i get no such error messages when I boot on battery instead of AC.
One more note: on older 4.4x kernels, no such errors as well - so i'm kinda puzzled now...is it a matter of 4.10, tlp or possibly a combination of both?
I've attached a couple of kern / syslog files in case it's of any help...
All the best & thanks in advance for your reply.
PS: Sorry, forgot mentioning above: in the logs, after May 23 07:05:19 is with TLP temporarily uninstalled.
And after booting on AC:
I've further tested with "radeon.nopm=0" parameter passed to grub, in which case, the warnings that appear with TLP on AC disappear (however, at the penalty of the battery lasting afterwards for at least 40% less time than before). So maybe it's also a 4.10x kernel version problem and not a TLP issue per se?
Thanks in advance for any further help / assistance.
The great majority of issues with TLP are in fact bugs in a kernel driver's pm features.
(1) RUNTIME_PM_BLACKLIST="03:00.0" is not configured currently. But this is not important, because driver blacklisting via RUNTIME_PM_DRIVER_BLACKLIST="radeon ..." actually works as the AC output shows:
"auto" is the driver default and shows that TLP didn't touch the setting. All other devices are "on".
(2) TLP uses DPM too
and this seems to be the root of your error message. You may remove your boot option and try either to disable DPM on AC by commenting
or try the BAT setting
None of the TLP tweaks above seem to remove the errors unfortunately - however, i'm convinced 110% this behavior is merely 'triggered' by TLP, and the underlying problem certainly lies very deep elsewhere. By far the most interesting & very similar bug report / thread that i stumbled upon was in Arch's forums here (with kernel 4.8x, yet the very same radeon card...):
All the best & thanks again for all!