dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 150731] New: amdgpu: segfault on unbind in sysfs; card becomes nonresponsive
Date: Fri, 29 Jul 2016 22:41:06 +0000	[thread overview]
Message-ID: <bug-150731-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=150731

            Bug ID: 150731
           Summary: amdgpu: segfault on unbind in sysfs; card becomes
                    nonresponsive
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.6.4
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: JimiJames.Bove@gmail.com
        Regression: No

Full details here:
https://www.reddit.com/r/linux_gaming/comments/4udupx/nvidiaamd_support_questions/d5ovipc

Summary:
I'm using an R9 380. Others confirmed having this issue on the R9 285 and RX
480 (so, Tonga & Polaris 10 at least).

I can bind my video card to amdgpu, and that works. It crashes X, but when I
log back in, it's properly connected and everything.

However, if I try to unbind it, after waiting for a few seconds, I get a
segfault. Any subsequent attempts to do anything with that card in
sysfs--trying to unbind again, trying to bind to something else, etc.--will get
stuck forever, never segfaulting, because the card is not responding.

Removing the card (echo 1 > /sys/bus/pci/devices/0000:0X:00.0/remove) works,
but after a rescan (echo 1 > /sys/bus/pci/rescan), the card is no longer in
sysfs at all, as if it's been powered down. It can't be accessed by the system
in any way after that, until the computer reboots.

It may or may not be related to the "reset issues" bug:
http://vfio.blogspot.de/2015/04/progress-on-amd-front.html
https://lists.gnu.org/archive/html/qemu-devel/2015-04/msg03128.html
That bug officially only affects Hawaii and Bonaire, but Tonga cards (380, 285)
exhibit the same behavior even if it may not be for the same reason. Whether it
affects Polaris 10 (RX 480) is unknown. The RX 480 tester is currently finding
that out.

I also had this issue on 4.6.1, so it probably at least affects 4.6 in general.
Maybe all kernel versions that have amdgpu?

-- 
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

             reply	other threads:[~2016-07-29 22:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29 22:41 bugzilla-daemon [this message]
2016-07-29 22:44 ` [Bug 150731] amdgpu: segfault on unbind in sysfs; card becomes nonresponsive 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
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@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).