All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109498] Game enabling VBO Core but disabling VAO Core causing reproducible, predictable, spontaneous powerdown
Date: Tue, 29 Jan 2019 16:56:00 +0000	[thread overview]
Message-ID: <bug-109498-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 109498
           Summary: Game enabling VBO Core but disabling VAO Core causing
                    reproducible, predictable, spontaneous powerdown
           Product: DRI
           Version: XOrg git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: awenocur@gmail.com

The game "openAstroMenace", for some reason defaults to using VBO Core in the
absence of VAO core, which predictably causes the game to crash on a modern
OpenGL implementation. The game itself crashing is not a problem; it's the PSU
switching off that's very concerning.

I'm running an ASRock E3V5 WS motherboard with a 4 GB Sapphire R9 Fury X, and
an E3-1235L CPU.

I'm early on in diagnosing it so I don't have a stack trace, but I think I've
ruled out hardware problems, as this system doesn't break a sweat maxing out
the Heaven benchmark or the Phoronix JuliaGPU (via ROCm) benchmark, and plays
every other game flawlessly. It can run with all CPU cores at 100% for hours on
end. openAstroMenace runs flawlessly with max settings when VAO Core is
enabled.

Mesa may be malfunctioning here, but a userspace library wouldn't affect PSU
behavior. This is pointing me in the direction of suspecting AMDGPU to be the
culprit. It exhibits this behavior on both my Ubuntu and Gentoo installations,
and on 4.15 and 4.18 series kernels. The system poweroff is predictable down to
less than half a second, and is triggered exactly the same way at exactly the
same time in every instance. It occurs around 3/4 of a second after the game's
menu appears.

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

[-- Attachment #1.2: Type: text/html, Size: 3247 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

             reply	other threads:[~2019-01-29 16:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29 16:56 bugzilla-daemon [this message]
2019-01-29 17:01 ` [Bug 109498] Game enabling VBO Core but disabling VAO Core causing reproducible, predictable, spontaneous powerdown bugzilla-daemon
2019-01-29 17:12 ` bugzilla-daemon
2019-01-29 17:12 ` bugzilla-daemon
2019-11-19  9:12 ` 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-109498-502@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.