https://bugs.freedesktop.org/show_bug.cgi?id=98502
--- Comment #19 from Mauro Santos <registo.maill...@gmail.com> ---
(In reply to Emil Velikov from comment #18)
> (In reply to Eugene Shalygin from comment #17)
> > To clarify: lspci was never waking up the dGPU. I assume that it was always
> > reading the device config file.
>
> The kernel behaviour change(?) does sound surprising. I suggest checking
> that the device was powered off in both cases - leaning that it might not
> have been.
I do have to say that I see the same behavior, although at the time what made
me notice the change is behavior was a mesa update. The only change for the
following tests was booting with a different kernel.
With 4.4.52 lspci says:
03:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Mars
[Radeon HD 8670A/8670M/8750M] [1002:6600] (rev ff)
With 4.9.11 lspci says:
03:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Mars
[Radeon HD 8670A/8670M/8750M] [1002:6600] (rev 81)
Notice that the revision is different so I would bet the kernel was not
behaving properly before.
Also /sys/kernel/debug/dri/1/radeon_pm_info says the following right after
using lspci:
With kernel 4.4.52:
PX asic powered off
With kernel 4.9.11:
uvd vclk: 0 dclk: 0
power level 0 sclk: 30000 mclk: 15000 vddc: 900 vddci: 0 pcie gen: 2
> That said, it sounds like the root of your issue is different than the one
> covered here - pardon for dragging you :-\
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
