[Bug 106262] [BXT] GPU HANG: ecode 9:2:0xbefffffe, in Main Thread [4018], reason: Hang on bsd ring,

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=106262

--- Comment #9 from Patrick Beaulieu <patrick.beaulieu at avigilon.com> ---
(In reply to Jani Nikula from comment #8)
> (In reply to Patrick Beaulieu from comment #6)
> > What is the official intel-gfx position on enable_rc6=0 and/or max_cstate=1 ?
> > Should we be using these if the goal is maximum stability?
> 
> enable_rc6 parameter has been removed upstream. In general, I can't
> recommend anyone running non-default i915 parameters. Most of them are for
> debugging, taint the kernel, and aren't properly tested. If you have issues,
> we'll only support the default settings.


How do you align that with errata from intel for certain platforms (baytail,
possibly apollolake/broxton as well) that basically says "using low power
states may hang your system due to hardware issue, we recommend max C1 and
disable rc6"

I won't paste the exact text since the doc is supposed to be confidential:
But somebody has it up for reading.
http://advci.eastasia.cloudapp.azure.com/wordpress/wp-content/uploads/2017/05/570005_Intel_Celeron_Processor_J1900_Sighting_Alert_4995585_Rev1_0.pdf#page=4

There are also numerous bugs/hangs filed in this project where the suggested
and functioning workaround is enable_rc6=0

I see some are complaining about enable_rc6 being taken away already:
https://bugs.freedesktop.org/show_bug.cgi?id=105962

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180510/03af22d0/attachment.html>