From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111968] Navi10 null pointer dereference in kernel 5.4 while running Vulkan CTS
Date: Thu, 10 Oct 2019 15:26:36 +0000 [thread overview]
Message-ID: <bug-111968-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1287 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111968
Bug ID: 111968
Summary: Navi10 null pointer dereference in kernel 5.4 while
running Vulkan CTS
Product: DRI
Version: DRI git
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: not set
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: venemo@msn.com
Created attachment 145698
--> https://bugs.freedesktop.org/attachment.cgi?id=145698&action=edit
dmesg log with kernel 5.4-rc2 that shows the null pointer dereference
While running the Vulkan CTS, I encountered the following:
Running the cases dEQP-VK.memory.allocation.* will trigger a kernel NULL
pointer dereference in amdgpu on 5.4-rc2, see the attached dmesg log. After
this happens, the GPU can hang too, but doesn't always hang.
Hardware:
AMD Radeon RX 5700XT (reference card, made by Sapphire)
Dell U2718Q (two of them: one through HDMI, other through DisplayPort)
AMD Ryzen 7 3700X
MSI B450i
Software:
Fedora Workstation 31 x86_64
LLVM 9
Mesa master (what will be 19.3)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2814 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-10-10 15:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 15:26 bugzilla-daemon [this message]
2019-10-10 15:38 ` [Bug 111968] Navi10 null pointer dereference in kernel 5.4 while running Vulkan CTS bugzilla-daemon
2019-10-10 15:41 ` bugzilla-daemon
2019-10-14 20:50 ` bugzilla-daemon
2019-10-14 20:56 ` bugzilla-daemon
2019-10-14 22:13 ` bugzilla-daemon
2019-10-15 8:35 ` bugzilla-daemon
2019-11-19 9:57 ` 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-111968-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.