[Mesa-dev] [Bug 98502] Delay when starting firefox, thunderbird or chromium and dmesg spam

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Oct 30 14:24:37 UTC 2016


https://bugs.freedesktop.org/show_bug.cgi?id=98502

            Bug ID: 98502
           Summary: Delay when starting firefox, thunderbird or chromium
                    and dmesg spam
           Product: Mesa
           Version: 13.0
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Mesa core
          Assignee: mesa-dev at lists.freedesktop.org
          Reporter: registo.mailling at gmail.com
        QA Contact: mesa-dev at lists.freedesktop.org

With mesa 13.0.0rc2 I'm seeing a 2 to 3 second delay when starting firefox,
thunderbird or chromium. This happens every time the programs are closed (all
instances) and run again. Glxgears (without prime offloading) also seems to be
affected as well as lspci, this wasn't the case before with mesa 12.0.3.

When this happens the following messages are logged in dmesg:

[drm] probing gen 2 caps for device 8086:9d18 = 9724043/e
[drm] enabling PCIE gen 3 link speeds, disable with radeon.pcie_gen2=0
[drm] PCIE GART of 2048M enabled (table at 0x00000000001D6000).
radeon 0000:03:00.0: WB enabled
radeon 0000:03:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and
cpu addr 0xffff88042bbafc00
radeon 0000:03:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and
cpu addr 0xffff88042bbafc04
radeon 0000:03:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and
cpu addr 0xffff88042bbafc08
radeon 0000:03:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and
cpu addr 0xffff88042bbafc0c
radeon 0000:03:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and
cpu addr 0xffff88042bbafc10
radeon 0000:03:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and
cpu addr 0xffffc90002235a18
radeon 0000:03:00.0: failed VCE resume (-110).
[drm] ring test on 0 succeeded in 1 usecs
[drm] ring test on 1 succeeded in 1 usecs
[drm] ring test on 2 succeeded in 1 usecs
[drm] ring test on 3 succeeded in 4 usecs
[drm] ring test on 4 succeeded in 4 usecs
[drm] ring test on 5 succeeded in 2 usecs
[drm] UVD initialized successfully.
[drm] ib test on ring 0 succeeded in 0 usecs
[drm] ib test on ring 1 succeeded in 0 usecs
[drm] ib test on ring 2 succeeded in 0 usecs
[drm] ib test on ring 3 succeeded in 0 usecs
[drm] ib test on ring 4 succeeded in 0 usecs
[drm] ib test on ring 5 succeeded

I'm using a laptop with an Intel iGPU with and an AMD dGPU, it seems that with
mesa 13.0.0rc2 all the gpus in the system (iGPU+dGPU) are probed instead of
only the gpu that is going to be used (iGPU).

Given that the dGPU is usually automatically turned off for power saving it
takes 2 to 3 seconds to be re-initialized and this causes the delay on startup
for the programs I've mentioned before (I suspect many more are affected).

This might not be an actual bug (new intended behavior?) but it is a change in
behavior and it is annoying as opening any affected application will incur a 2
to 3 second delay on startup, even if all files are already cached in ram and
the startup would otherwise be virtually instant.

OS: Arch Linux x86-64, kernel 4.8.4, mesa 13.0.0rc2, xorg 1.18.4 using the
modesetting driver for all cards.

Machine: Lenovo E560, iGPU HD Graphics 520 (rev 07), dGPU [AMD/ATI] Mars
[Radeon HD 8670A/8670M/8750M] (rev 81)

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20161030/359b29b6/attachment.html>


More information about the mesa-dev mailing list