From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95517] Constant GPU VM faults
Date: Fri, 27 May 2016 19:31:26 +0000 [thread overview]
Message-ID: <bug-95517-502-3PKcEbIydE@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95517-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 643 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=95517
--- Comment #6 from lumetili@gmail.com ---
Created attachment 124132
--> https://bugs.freedesktop.org/attachment.cgi?id=124132&action=edit
kernel oops
Without pci=nommconf , the kernel logs PCI bus errors that get corrected, they
seem to be connected to this issue? I reliably get a visible kernel oops from
radeon with this configuration. With nommconf, no errors seemingly get logged
(except VM faults) but regardless, eventually it crashes so hard not even SysRq
works.
Attached kernel oops.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1462 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 prev parent reply other threads:[~2016-05-27 19:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-95517-502@http.bugs.freedesktop.org/>
2016-05-24 6:49 ` [Bug 95517] Constant GPU VM faults bugzilla-daemon
2016-05-24 15:04 ` bugzilla-daemon
2016-05-25 23:11 ` bugzilla-daemon
2016-05-27 14:11 ` bugzilla-daemon
2016-05-27 19:31 ` bugzilla-daemon [this message]
2016-06-07 20:02 ` bugzilla-daemon
2016-08-23 23:14 ` bugzilla-daemon
2016-08-24 21:47 ` bugzilla-daemon
2018-09-20 1:30 ` bugzilla-daemon
2018-12-20 16:20 ` bugzilla-daemon
2019-01-14 22:41 ` bugzilla-daemon
2019-09-25 17:54 ` 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-95517-502-3PKcEbIydE@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox