[Bug 99715] Don't print: "Note: Buggy applications may crash, if they do please report to vendor"

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Feb 8 18:35:22 UTC 2017


            Bug ID: 99715
           Summary: Don't print: "Note: Buggy applications may crash, if
                    they do please report to vendor"
           Product: Mesa
           Version: 13.0
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Vulkan/intel
          Assignee: intel-3d-bugs at lists.freedesktop.org
          Reporter: rjklindsay at hotmail.com
        QA Contact: intel-3d-bugs at lists.freedesktop.org
                CC: jason at jlekstrand.net

I'm running into issues when using the Mesa Vulkan driver on Ubuntu 16.04.
When I enumerate the physical devices, Vulkan returns 2 options for me:
1: NVidia GTX 660 Ti
2: Intel HD Graphics 530 (Skylake GT2)

(On some machines, the order is reversed.)

Next, I determine which GPU (VkPhysicalDevice) the desktop is currently running
on, by searching for presentable queue-families on each GPU, using either:
   vkGetPhysicalDeviceSurfaceSupportKHR(), or

I HAVE enabled DRI3 support for Intel (in: /etc/X11/xorg.conf.d/20-intel.conf)
so when the desktop is running on Intel, the query returns "True" for the Intel
queue.  And, when I use nvidia-prime, to switch the desktop to run on the
NVidia GPU,  NVidia's first queue-family returns true, and Intel's queue-family
returns false.  So far so good...

The problem is, Mesa then also prints an error message to stderr:

"vulkan: No DRI3 support detected - required for presentation"
"Note: Buggy applications may crash, if they do please report to vendor"

(See line 268 in file: /mesa/src/vulkan/wsi/wsi_common_x11.c)
As I said, I DO have DRI3 enabled, but it seems Mesa doesn't detect it when the
NVidia GPU is active.
Besides, it should be perfectly valid to use these query functions to search
for presentable queues, without risking an error message being displayed.  I do
see the value of informing the user if DRI3 was not set up correctly, but only
when its valid.  Mesa should not accuse the app of being buggy, just because a
non-Intel GPU is being used.  

Which brings up the next issue. The second line: "Buggy applications may crash"
implies that the Vulkan application is buggy, even when its not.  This leads to
users incorrectly filing bug-reports against Vulkan app developers, which is a
bit unfair: ( see: https://github.com/SaschaWillems/Vulkan/issues/226 )

At least, can we remove the second line from that error message?
I don't want users thinking that my apps are buggy too.

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/intel-3d-bugs/attachments/20170208/aedaa753/attachment.html>

More information about the intel-3d-bugs mailing list