<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Delay when starting firefox, thunderbird or chromium and dmesg spam"
href="https://bugs.freedesktop.org/show_bug.cgi?id=98502#c14">Comment # 14</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Delay when starting firefox, thunderbird or chromium and dmesg spam"
href="https://bugs.freedesktop.org/show_bug.cgi?id=98502">bug 98502</a>
from <span class="vcard"><a class="email" href="mailto:emil.l.velikov@gmail.com" title="Emil Velikov <emil.l.velikov@gmail.com>"> <span class="fn">Emil Velikov</span></a>
</span></b>
<pre>(In reply to Tobias Droste from <a href="show_bug.cgi?id=98502#c12">comment #12</a>)
<span class="quote">> (In reply to Eugene Shalygin from <a href="show_bug.cgi?id=98502#c11">comment #11</a>)
> > I have the same problem: Qt5 wakes up dGPU on launch [1]. However, I believe
> > that this is a kernel problem: the dGPU wakes up when a program tries to
> > read from /sys/bus/pci/devices/<bus id>/config. This was not happening with
> > 4.7 and when I use Arch's current LTS kernel (4.4) it also works fine [2].
>
> As soon as all the patches landed (from <a href="show_bug.cgi?id=98502#c10">comment #10</a>) there's no need to
> check /sys/bus/pci/devices/<bus id>/config anymore, because there's a new
> API to get that info that doesn't need to wake up the device and the problem
> goes away. But right now the mesa patches are not applied as far as I can
> tell.
> </span >
Yes and no - yes the patches in <a href="show_bug.cgi?id=98502#c10">comment #10</a> will help from graphics POV, but no
they won't help with the 'generic case' that Eugene is talking about. With
"generic case" being anyone reading the ./config file will wake up the device.
Eugene if behaviour has changed across kernel versions [i.e. you're confident
that with kernel X the dGPU was powered off and reading ./config did not wake
it up] feel free to bisect and report it.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>