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 101946] Rebinding AMDGPU causes initialization errors [R9 290]
Date: Tue, 01 Aug 2017 14:28:05 +0000	[thread overview]
Message-ID: <bug-101946-502-n3Ff25CJP3@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101946-502@http.bugs.freedesktop.org/>


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

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

--- Comment #21 from Luke A. Guest <laguest@archeia.com> ---
Created attachment 133172
  --> https://bugs.freedesktop.org/attachment.cgi?id=133172&action=edit
Test of above with R9 380 with Windows 8.1 and latest AMD drivers

Hi,

After being asked to try this by Alex in IRC, I've added the output of the
various logs, there will be overlap in places, dmesg and messages.

I'm running 4.13.0-rc2 with drm-next-4.14 branch merged and the set of 3
patches from Alex. Tried with and without the third patch, I still get a black
screen on restarting the VM (using virt manager). The first boot from a freshly
booted host starts fine.

In the log I've put "START" and "RESTART" where the VM is started (then
shutdown) and then restarted. There is also extra PCI debugging messages
enabled in the kernel.

I too, would like an answer re the probing mentioned in 11.

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

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

  parent reply	other threads:[~2017-08-01 14:28 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-27 11:46 [Bug 101946] Rebinding AMDGPU causes initialization errors [R9 290 / 4.10 kernel] bugzilla-daemon
2017-07-27 11:47 ` bugzilla-daemon
2017-07-27 11:47 ` bugzilla-daemon
2017-07-27 11:47 ` bugzilla-daemon
2017-07-27 12:00 ` bugzilla-daemon
2017-07-27 14:42 ` bugzilla-daemon
2017-07-27 14:42 ` bugzilla-daemon
2017-07-28 10:26 ` bugzilla-daemon
2017-07-28 11:46 ` bugzilla-daemon
2017-07-28 14:24 ` bugzilla-daemon
2017-07-28 15:19 ` bugzilla-daemon
2017-07-28 15:37 ` bugzilla-daemon
2017-07-28 15:53 ` bugzilla-daemon
2017-07-28 17:26 ` bugzilla-daemon
2017-07-28 17:29 ` bugzilla-daemon
2017-07-28 20:55 ` bugzilla-daemon
2017-07-28 21:06 ` bugzilla-daemon
2017-07-28 21:17 ` bugzilla-daemon
2017-07-28 21:55 ` bugzilla-daemon
2017-07-28 23:06 ` [Bug 101946] Rebinding AMDGPU causes initialization errors [R9 290] bugzilla-daemon
2017-07-29 16:05 ` bugzilla-daemon
2017-07-29 17:20 ` bugzilla-daemon
2017-07-29 22:22 ` bugzilla-daemon
2017-08-01 14:28 ` bugzilla-daemon [this message]
2017-08-01 14:59 ` bugzilla-daemon
2017-08-01 15:16 ` bugzilla-daemon
2017-08-01 16:16 ` bugzilla-daemon
2017-08-01 16:30 ` bugzilla-daemon
2017-08-01 16:58 ` bugzilla-daemon
2017-08-01 17:47 ` bugzilla-daemon
2017-08-02  6:37 ` bugzilla-daemon
2017-08-30 20:55 ` bugzilla-daemon
2019-07-27  5:47 ` bugzilla-daemon
2019-11-19  8:20 ` 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-101946-502-n3Ff25CJP3@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