[Bug 105962] "enable_rc6" parameter deprecation brings back freezing

[bugzilla-daemon at freedesktop.org]

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

--- Comment #7 from Filip <tyx027 at gmail.com> ---
Unfortunately the other user says there is zero output with netconsole when the
freezes occur, but he has added the debug option and will see if something
happens. 

As for me, I haven't had a freeze so far, but will keep testing since the
freezes can happen multiple times a day, but also only once in a few days. I
reckon if they don't occur after a week or two it would be confirmation enough
that limiting c-states is a workaround.

In the meantime I would like to provide a short summary of what the issue with
these laptops has been. I apologize if this is spammy in any way and please
ignore if it is, but I realized the thread I linked is too long so maybe this
can be helpful.

The freezes that we refer to are random in nature and total in their effect -
meaning physical power-off  is necessary. They happen both in Windows and
Linux. Even though the thread is for the Kaby Lake V510 model, IIRC there have
been freezes with the V310 series as well, and the Skylake version was not
exempt. The last time I counted, some 30-ish users had reported this issue, but
the confirmed count is much higher since some IT personnel reported freezes on
their whole batches of acquired laptops. We believe the issue has something to
do with Intel power-saving, but it's quite unclear if this is caused by a
driver issue or is a result of bad Lenovo BIOS or motherboard. Lenovo has been
unresponsive, while their service centers have usually been replacing the
motherboards, which is a solution that helped only one user so far. Windows
hacks that worked for some (but not all) users:
https://forums.lenovo.com/t5/Lenovo-C-E-K-M-N-and-V-Series/V510-15IKB-Laptop-Freeze/m-p/3852313#M24549.
And the Linux hack that worked involved disabling DC and RC6. And oh yes, there
was also a previous one that involved turning off DRI, but that came with heavy
side-effects.

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