All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106291] amdgpu fails GPU reset when resuming from suspend
Date: Wed, 11 Nov 2015 17:26:38 +0000	[thread overview]
Message-ID: <bug-106291-2300-VzDcrfrZdO@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-106291-2300@https.bugzilla.kernel.org/>

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

--- Comment #9 from universaledge97@gmail.com ---
Created attachment 192801
  --> https://bugzilla.kernel.org/attachment.cgi?id=192801&action=edit
dmesg 4.3.0 - Xorg hang

I ended up having to reinstall Arch Linux after my gpg directory was corrupted
when the system auto-suspended in the middle of a package upgrade.

Running Linux 4.3.0 from Arch Linux testing repo: I'm not getting the GPU reset
bug anymore; rather Xorg just randomly hangs indefinitely after waking from
suspend, resulting in an uninteractive black screen. Curiously, there's no Xorg
crash log. The dmesg log provides a call trace from before the hang.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-11-11 17:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-19 20:13 [Bug 106291] New: amdgpu fails GPU reset when resuming from suspend bugzilla-daemon
2015-10-20  9:50 ` [Bug 106291] " bugzilla-daemon
2015-10-20 14:06 ` bugzilla-daemon
2015-10-21  1:29 ` bugzilla-daemon
2015-10-25  3:18 ` bugzilla-daemon
2015-10-25  3:19 ` bugzilla-daemon
2015-10-25  3:20 ` bugzilla-daemon
2015-10-27  3:43 ` bugzilla-daemon
2015-10-27 15:53 ` bugzilla-daemon
2015-11-11 17:26 ` bugzilla-daemon [this message]
2016-05-01 16:35 ` 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-106291-2300-VzDcrfrZdO@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.