<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Lockup/Freezes on Laptop with switchable graphics"
href="https://bugs.freedesktop.org/show_bug.cgi?id=99881#c14">Comment # 14</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Lockup/Freezes on Laptop with switchable graphics"
href="https://bugs.freedesktop.org/show_bug.cgi?id=99881">bug 99881</a>
from <span class="vcard"><a class="email" href="mailto:matthew@tech3.me" title="Matthew Fox <matthew@tech3.me>"> <span class="fn">Matthew Fox</span></a>
</span></b>
<pre>Hi,
It's rare that the PC doesn't lock up with runpm enabled so I've only been able
to test this a couple of times.
In the first try, the PC had stabilized (stopped freezing) after a while. I
then ran xrandr. Immediately after I cat /sys/kernel/debug/vgaswitcheroo/switch
and the discrete gpu had powered up. dmesg showed 1 block of gpu initialization
lines. A few seconds later vgaswitcheroo/switch showed the discrete gpu as
being off. dmesg also showed 2 or 3 blocks of the gpu initialization. It looked
like the gpu was being enabled and disabled repeatedly. The computer then
locked up a few seconds later. I don't have any logs for this session.
In the second try, the PC had stabilized. I ran xrandr and vgaswitcheroo/switch
had changed from 'DynOff' to 'DynPwr' for the discrete gpu. dmesg showed 1
block of the gpu initialization. The computer locked up a few seconds later.
The logs I have were captured straight after xrandr had run so the 'dmesg
after' log only shows one of the gpu initialization blocks but I suspect the
gpu was being enabled and disabled repeatedly before the PC locked up. I wasn't
able to run dmesg again before the lockup to confirm.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>