From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109366] NULL pointer at pcie_capability_read_dword with Radeon SI vfio passthrough
Date: Tue, 15 Jan 2019 15:39:07 +0000 [thread overview]
Message-ID: <bug-109366-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 916 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109366
Bug ID: 109366
Summary: NULL pointer at pcie_capability_read_dword with Radeon
SI vfio passthrough
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: ryandbair@gmail.com
Created attachment 143131
--> https://bugs.freedesktop.org/attachment.cgi?id=143131&action=edit
dmesg output
My guest is seeing the attached bug and call trace during boot. Kernel
4.20.2-200, also an issue on 4.19 series. 4.18 is similar with the older drm_
prefixed version of the function.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2333 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
next reply other threads:[~2019-01-15 15:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 15:39 bugzilla-daemon [this message]
2019-01-15 16:22 ` [Bug 109366] NULL pointer at pcie_capability_read_dword with Radeon SI vfio passthrough bugzilla-daemon
2019-01-15 16:49 ` bugzilla-daemon
2019-01-15 17:16 ` bugzilla-daemon
2019-01-17 14:12 ` bugzilla-daemon
2019-01-17 14:51 ` bugzilla-daemon
2019-11-19 9:34 ` 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-109366-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.