dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111229] Unable to unbind GPU from amdgpu
Date: Sun, 28 Jul 2019 11:35:35 +0000	[thread overview]
Message-ID: <bug-111229-502-F5mZ5YCkp9@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111229-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 970 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=111229

--- Comment #5 from wedens13@yandex.ru ---
Created attachment 144896
  --> https://bugs.freedesktop.org/attachment.cgi?id=144896&action=edit
unbinding without X running

I've attached a log of attempt to unbind without X running:

systemctl stop sddm
echo 0 > /sys/class/vtconsole/vtcon0/bind
echo 0 > /sys/class/vtconsole/vtcon1/bind
echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind ||
true

echo "0000:03:00.0" > /sys/bus/pci/devices/0000:03:00.0/driver/unbind

Result is the same but backtrace seems a bit different. This was done with
kernel 5.2.1.

I've tried suspend to ram and another reset bug mitigation (which helps in
other cases), but gpu is still unusable after this failed attempt to unbind. I
still can't re-bind it to amdgpu or vfio-pci and clean shutdown is not
happening.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1865 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

  parent reply	other threads:[~2019-07-28 11:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-27  4:14 [Bug 111229] Unable to unbind GPU from amdgpu bugzilla-daemon
2019-07-27  4:14 ` bugzilla-daemon
2019-07-27  4:14 ` bugzilla-daemon
2019-07-27  4:15 ` bugzilla-daemon
2019-07-27  5:47 ` bugzilla-daemon
2019-07-27  5:47 ` bugzilla-daemon
2019-07-27  5:49 ` bugzilla-daemon
2019-07-28 11:35 ` bugzilla-daemon [this message]
2019-07-28 18:38 ` bugzilla-daemon
2019-07-29  8:54 ` bugzilla-daemon
2019-07-29  8:54 ` bugzilla-daemon
2019-07-29 13:09 ` bugzilla-daemon
2019-08-06  0:14 ` bugzilla-daemon
2019-09-03 19:06 ` bugzilla-daemon
2019-10-05 22:13 ` bugzilla-daemon
2019-10-21  7:22 ` bugzilla-daemon
2019-11-04  4:08 ` bugzilla-daemon
2019-11-04  4:09 ` bugzilla-daemon
2019-11-05 10:28 ` bugzilla-daemon
2019-11-19  9:37 ` 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-111229-502-F5mZ5YCkp9@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