https://bugs.freedesktop.org/show_bug.cgi?id=98964
GitLab Migration User changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=98964
--- Comment #14 from Emil Velikov ---
(In reply to Zoltán Böszörményi from comment #12)
> (In reply to Emil Velikov from comment #11)
> > Above all: yes using hard links is nasty.
>
> Thanks for confirming. :-)
>
> > If you're having a
https://bugs.freedesktop.org/show_bug.cgi?id=98964
--- Comment #13 from Zoltán Böszörményi ---
More details from testing several scenarios:
1. When there is only a single X screen then this line does not appear in the
logs. It does not matter if we have the default mirrored screen
https://bugs.freedesktop.org/show_bug.cgi?id=98964
--- Comment #12 from Zoltán Böszörményi ---
(In reply to Emil Velikov from comment #11)
> Above all: yes using hard links is nasty.
Thanks for confirming. :-)
> If you're having a single (or multiple fixed) GPU system then building
>
https://bugs.freedesktop.org/show_bug.cgi?id=98964
--- Comment #11 from Emil Velikov ---
(In reply to Zoltán Böszörményi from comment #9)
> Although the OS is Yocto, the Mesa recipe is mostly mine including the patch
> to revert this horrible idea of hard links. Hard links are good until
https://bugs.freedesktop.org/show_bug.cgi?id=98964
--- Comment #10 from Zoltán Böszörményi ---
This 3 year old bug ticket (around Chromium 30-35) talks about this problem:
https://bugs.chromium.org/p/chromium/issues/detail?id=231945
Turned off CRTC?
Does the CRTC considered "turned off"
https://bugs.freedesktop.org/show_bug.cgi?id=98964
--- Comment #9 from Zoltán Böszörményi ---
(In reply to Emil Velikov from comment #7)
> Zoltán - the "g" in "i915g" implies the driver type rather than the actual
> filename.
I know, "g" is for Gallium. The symlink points to the classic
https://bugs.freedesktop.org/show_bug.cgi?id=98964
--- Comment #8 from Emil Velikov ---
(In reply to Zoltán Böszörményi from comment #6)
> When did Chromium started to use the vertical sync?
>
Don't any of us know this one. As Matt mentioned your help in tracking the
issue down will be
https://bugs.freedesktop.org/show_bug.cgi?id=98964
--- Comment #7 from Emil Velikov ---
Zoltán - the "g" in "i915g" implies the driver type rather than the actual
filename.
Humble (off topic) request: please look into the the Yocto recipe to create
hard links for the files as opposed to
https://bugs.freedesktop.org/show_bug.cgi?id=98964
--- Comment #6 from Zoltán Böszörményi ---
I don't know if it's a regression or if it's in Mesa at all.
When did Chromium started to use the vertical sync?
49 and 51 didn't print this, but it's true that we used 12.0.x or 11.1.x for
them.
https://bugs.freedesktop.org/show_bug.cgi?id=98964
Matt Turner changed:
What|Removed |Added
Component|Drivers/DRI/i965|Drivers/DRI/i915
QA
https://bugs.freedesktop.org/show_bug.cgi?id=98964
Zoltán Böszörményi changed:
What|Removed |Added
Component|Drivers/Gallium/radeonsi|Drivers/DRI/i965
QA
https://bugs.freedesktop.org/show_bug.cgi?id=98964
Bug ID: 98964
Summary: Chromium complains about glXGetSyncValuesOML in 13.0.2
Product: Mesa
Version: 13.0
Hardware: Other
OS: All
Status: NEW
Severity:
13 matches
Mail list logo
