From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 150731] amdgpu: segfault on unbind in sysfs; card becomes nonresponsive
Date: Thu, 11 Aug 2016 23:46:49 +0000 [thread overview]
Message-ID: <bug-150731-2300-4ai7wNBuCf@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-150731-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=150731
--- Comment #6 from Jimi <JimiJames.Bove@gmail.com> ---
Created attachment 228431
--> https://bugzilla.kernel.org/attachment.cgi?id=228431&action=edit
dmesg log
And now I've tried unbinding it from amdgpu without X running at all, and it of
course didn't work, confirming its kernel bug status. I've captured the dmesg
log, and as far as I can tell, the part of the log that pertains to amdgpu is
the stack trace starting at [1131.985756].
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-08-11 23:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 22:41 [Bug 150731] New: amdgpu: segfault on unbind in sysfs; card becomes nonresponsive bugzilla-daemon
2016-07-29 22:44 ` [Bug 150731] " bugzilla-daemon
2016-07-29 22:45 ` bugzilla-daemon
2016-08-09 16:50 ` bugzilla-daemon
2016-08-11 23:32 ` bugzilla-daemon
2016-08-11 23:33 ` bugzilla-daemon
2016-08-11 23:46 ` bugzilla-daemon [this message]
2016-08-12 0:16 ` bugzilla-daemon
2016-08-12 1:09 ` bugzilla-daemon
2016-08-16 9:21 ` bugzilla-daemon
2016-08-16 9:23 ` bugzilla-daemon
2017-06-08 14:27 ` bugzilla-daemon
2017-06-10 19:28 ` 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-150731-2300-4ai7wNBuCf@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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;
as well as URLs for NNTP newsgroup(s).