All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102358] WarThunder freezes at start, with activated vsync (vblank_mode=2)
Date: Fri, 25 Aug 2017 17:01:12 +0000	[thread overview]
Message-ID: <bug-102358-502-4943SxSKPI@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102358-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 2116 bytes --]

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

--- Comment #12 from Thomas Hellström <thellstrom@vmware.com> ---
(In reply to haro41 from comment #11)
> i applied your patch successful, still the freezes, maybe in average a bit
> later now.
> 
> The behavoir changed a bit:
> 
> before patch:
> 
> vblank_mode=2 (default)-> always freezes inside 0..2 minutes runtime, 
>                           framerate fix/clamped at 50(as expected)
> vblank_mode=0          -> no freezes at all, dynamic, high framerates 
> LIBGL_DRI3_DISABLE=1   -> no freezes at all, framerate fix at 50 
> 
> 
> after patch:
> 
> vblank_mode=2 (default)-> always freezes inside 0..2 minutes runtime, 
>                           framerate fix/clamped at 100(!!)
> vblank_mode=0          -> no freezes at all, dynamic, high framerates 
> LIBGL_DRI3_DISABLE=1   -> no freezes at all, framerate fix at 50 
> 
> 
> To be honest, i am not familiar enough with DRM internals to understand what
> exactly happens here, but it looks like something is broken in respect to
> DRI 3 usage.
> 
> Somehow i think i could be the only one with this freezes and to ensure i am
> not wasting your time:
> Can you give me a hint, where i should look first to exclude it is something
> specific to my system/setup?


That's really weird :).

Actually I don't think anything's wrong with your setup, but rather that
there's a multithreading bug in dri3 or the app. There's no concurrency
protection at all in the dri3 client and I'm not sure that's correct. I think
you're the only one seeing this possibly perhaps because you're the first to
try it with a heavily multithreaded application.

Anyway, I'm OK with commenting out the glFinish() wait for swapbuffers until
someone has the possibility to debug this thoroughly. Unfortunately WarThunder
doesn't run on vmware's svga driver (yet) due to bugs...

It would also be good to try to rule out server side radeon dri3 problems.
Perhaps by running it on nouveau or intel...

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3113 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-08-25 17:01 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22 11:40 [Bug 102358] WarThunder freezes always with vblanc=1 bugzilla-daemon
2017-08-22 18:12 ` [Bug 102358] WarThunder freezes always with vblank_mode=2 bugzilla-daemon
2017-08-22 18:14 ` [Bug 102358] WarThunder freezes at start, with activated vsync (vblank_mode=2) bugzilla-daemon
2017-08-23  2:04 ` bugzilla-daemon
2017-08-23 15:00 ` bugzilla-daemon
2017-08-23 15:32 ` bugzilla-daemon
2017-08-23 17:51 ` bugzilla-daemon
2017-08-23 18:02 ` bugzilla-daemon
2017-08-23 19:18 ` bugzilla-daemon
2017-08-25 11:23 ` bugzilla-daemon
2017-08-25 12:58 ` bugzilla-daemon
2017-08-25 14:36 ` bugzilla-daemon
2017-08-25 14:36 ` bugzilla-daemon
2017-08-25 16:18 ` bugzilla-daemon
2017-08-25 17:01 ` bugzilla-daemon [this message]
2017-08-25 17:35 ` bugzilla-daemon
2017-08-26  5:09 ` bugzilla-daemon
2017-08-26 16:03 ` bugzilla-daemon
2017-08-28  1:37 ` bugzilla-daemon
2017-08-28 12:08 ` bugzilla-daemon
2017-09-07 10:17 ` bugzilla-daemon
2017-09-07 14:34 ` bugzilla-daemon
2017-09-08 14:53 ` bugzilla-daemon
2017-09-17 17:43 ` bugzilla-daemon
2017-09-17 18:27 ` bugzilla-daemon
2017-09-19 18:00 ` bugzilla-daemon
2017-09-19 21:15 ` bugzilla-daemon
2017-09-19 21:32 ` bugzilla-daemon
2017-09-20 18:23 ` bugzilla-daemon
2017-10-18 21:53 ` bugzilla-daemon
2017-10-31  9:39 ` bugzilla-daemon
2017-11-02 10:50 ` bugzilla-daemon
2017-11-02 16:35 ` bugzilla-daemon
2017-11-02 16:41 ` bugzilla-daemon
2017-11-02 20:40 ` bugzilla-daemon
2017-11-03 14:02 ` bugzilla-daemon
2017-11-03 19:56 ` bugzilla-daemon
2017-11-03 20:40 ` bugzilla-daemon
2017-11-05 16:33 ` bugzilla-daemon
2017-11-05 17:30 ` bugzilla-daemon
2017-11-06 16:08 ` bugzilla-daemon
2017-11-13 13:14 ` bugzilla-daemon
2017-11-14 14:58 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-102358-502-4943SxSKPI@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.