<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Video cutout on Kaby Lake U processors."
href="https://bugs.freedesktop.org/show_bug.cgi?id=107543#c62">Comment # 62</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Video cutout on Kaby Lake U processors."
href="https://bugs.freedesktop.org/show_bug.cgi?id=107543">bug 107543</a>
from <span class="vcard"><a class="email" href="mailto:anshuman.gupta@intel.com" title="Anshuman Gupta <anshuman.gupta@intel.com>"> <span class="fn">Anshuman Gupta</span></a>
</span></b>
<pre>(In reply to Jan from <a href="show_bug.cgi?id=107543#c61">comment #61</a>)
Hi Jan,
Please find my inline response.
<span class="quote">> Last two days I performed various tests to get a better understanding of the
> root-cause. First I kept the machine switched on a full night with the
> settings i915.modeset=1, nouveau.modeset=0. Dmesg showed no failed hardware.
> In the morning the machine had crashed, ssh-server down. I can't see any
> errors in dmesg.</span >
This is strange, this particular bug is about Watermark configuration with 4k
high-resolution display (we have a workaround patch also for that
<a href="https://bugs.freedesktop.org/attachment.cgi?id=141958&action=edit">https://bugs.freedesktop.org/attachment.cgi?id=141958&action=edit</a> ).
ssh server was working while this issue observed. Could you please get us the
log, in order to check if it is a similar bug.
<span class="quote">>
> I subsequently repeated with recovery mode. First booting until the login
> screen: crashed. Then by booting to the recovery console: crash.
>
> After every test I reboot by pressing the power-key. The tests show that the
> machine crashes within a few minutes when keeping the machine on for a long
> time.
>
> I also tested by keeping the machine in the GRUB menu. The machine has not
> crashed then. The machine also does nog crash by using Windows 10. Kept the
> machine on for a full day.
>
> In my opinion the above rules out any hardware malfunction. The issue occurs
> by loading the linux in the current configuration.</span >
Can you please test with the recently merged patch-series to drm-tip
<a href="https://patchwork.freedesktop.org/series/51878/">https://patchwork.freedesktop.org/series/51878/</a>
<span class="quote">>
> Since my machine also has a nvidia 940mx card on board, I am now planning to
> install the nvidia driver from the nvidia site :
> 'NVIDIA-Linux-x86_64-340.96.run'. Wonder what's gonna happen then.
>
> I am also planning to see if I can enhance debugging to see if I can get any
> logging on the error.</span >
You enhance log message by below command,
echo 0xe > /sys/module/drm/parameter/debug
<span class="quote">>
>
> ps: with all due respect, I am somewhat annoyed that there isn't any
> response on my previous posts. Currently, I am typing in the void, while many
> messages on this topic have been posted in this thread. At least replying
> would be nice :-)</span >
Thanks,
Anshuman Gupta.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>