dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199925] system-freeze with amdgpu.dc=1 & HDMI-Output
Date: Tue, 25 Sep 2018 14:18:38 +0000	[thread overview]
Message-ID: <bug-199925-2300-lWfmT9JM9W@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199925-2300@https.bugzilla.kernel.org/>

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

mj.wilson.uk@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mj.wilson.uk@gmail.com

--- Comment #3 from mj.wilson.uk@gmail.com ---
I think I'm also seeing the same problem with hard system freezes.  However,
I'm unable to get the dmesg output from journald on reboot - it complains it's
corrupt.

However, I do get warning messages with similar stack traces to the ones above,
often when changing from virtual console to X, or when the monitors wake up
after sleep.

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

      parent reply	other threads:[~2018-09-25 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-04 21:50 [Bug 199925] New: system-freeze with amdgpu.dc=1 & HDMI-Output bugzilla-daemon
2018-06-05  8:46 ` [Bug 199925] " bugzilla-daemon
2018-06-06  9:00 ` bugzilla-daemon
2018-09-25 14:18 ` bugzilla-daemon [this message]

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-199925-2300-lWfmT9JM9W@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