I'm wondering if it's this commit that added it back in January

commit 7617a0a180a2cd3427a8ffa9534152df6a8fecbf
Author: Qiang Yu <qiang...@amd.com>
Date:   Wed Jan 11 13:59:22 2017 +0800

   dri2: refine dri2_probe_driver_name (v2)

   V2:
   1. update comment
   2. check bustype if PCI
   3. configure add libdrm version check for drmGetDevice

   Get PCI information from info->fd with drmGetDevice instead of
   assuming the info->fd is the first entity of scrn which is not
   true for multi entities scrn.

   Signed-off-by: Qiang Yu <qiang...@amd.com>
   Reviewed-by: Emil Velikov <emil.l.veli...@gmail.com>

On 11 April 2018 at 23:11, Mike Lothian <m...@fireburn.co.uk> wrote:
> I've also noticed the AMDGPU powers up each time I play a video -
> either using SMplayer or on Chromium
>
> [50458.810260] snd_hda_codec_ca0132 hdaudioC0D0: ca0132 DSP downloaded
> and running
> [50459.699224] [drm] PCIE GART of 1024M enabled (table at 0x000000F400000000).
> [50459.797265] [drm] UVD initialized successfully.
> [50460.008408] [drm] VCE initialized successfully.
> [50465.175833] amdgpu 0000:01:00.0: GPU pci config reset
>
> I used to see this before the drmDevice2 (my memory is a bit fuzzy)
> stuff landed, so the device wouldn't power up when the device node was
> probed
>
> On 11 April 2018 at 22:53, Mike Lothian <m...@fireburn.co.uk> wrote:
>> The journal.freeze I mentioned but was too big to attach
>>
>> On 11 April 2018 at 22:53, Mike Lothian <m...@fireburn.co.uk> wrote:
>>> Hi
>>>
>>> Hopefully 3rd time lucky (sorry Roman)
>>>
>>> I've done some more testing. The flashing I was seeing with Xserver
>>> 1.19.5 goes away when I use egl rather then glx with Kwin - I won't be
>>> using egl in any of the next tests
>>>
>>> When I use Xserver 1.20 RC4 with Intel/AMDPGU DDXs Kwin doesn't start
>>> - the X server is running (I'm attaching logs) - that's the case
>>> whether compositing is enabled or not in Kwin
>>>
>>> With the modesetting driver, Kwin launches with compositing enabled or
>>> disabled. However the lockups in plasmashell are still present. These
>>> happen with compositing enabled or disabled too. Simplest way to
>>> reproduce - press the start button multiple times until it locks up
>>> (usually within 4 times) - leaving it overnight, it seems to have
>>> unlocked itself. Alternatively "killall -9 plasmashell && sleep 1 &&
>>> plasmashell" sorts it from "Alt + F2". I've attached the journal again
>>> just after a freeze (journalctl.freeze in the next email)
>>>
>>> Cheers
>>>
>>> Mike
_______________________________________________
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel

Reply via email to