From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111139] linux 5.2: rare NULL pointer dereference when SteamVR idles
Date: Mon, 15 Jul 2019 17:19:35 +0000 [thread overview]
Message-ID: <bug-111139-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1172 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111139
Bug ID: 111139
Summary: linux 5.2: rare NULL pointer dereference when SteamVR
idles
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: haagch@frickel.club
Created attachment 144791
--> https://bugs.freedesktop.org/attachment.cgi?id=144791&action=edit
dmesg with null pointer dereference
Vega 64, mesa git b68778e6de2, Linux 5.2.
I am relatively sure this started happening with linux 5.2 and that this did
not happen on 5.1.
When SteamVR is idle for a while (i.e. the VR headset is not moved), it stops
rendering to not waste resources.
When it does this, there is a chance that a kernel bug happens, see attached
dmesg.
It does not happen very often, but often enough that I'm relatively sure it
started happening with 5.2.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2620 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-07-15 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 17:19 bugzilla-daemon [this message]
2019-07-19 2:31 ` [Bug 111139] linux 5.2: rare NULL pointer dereference when SteamVR idles bugzilla-daemon
2019-11-19 9:36 ` 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-111139-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.