dri-devel Archive on lore.kernel.org
 help / color / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 206475] amdgpu under load drop signal to monitor until hard reset
Date: Sat, 23 May 2020 14:40:22 +0000
Message-ID: <bug-206475-2300-i8x6i7GJWX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206475-2300@https.bugzilla.kernel.org/>


--- Comment #11 from Andrew Ammerlaan (andrewammerlaan@riseup.net) ---
Created attachment 289245
  --> https://bugzilla.kernel.org/attachment.cgi?id=289245&action=edit

Happened again today, while playing GTA V. Same problems appear in the log

I think the title of this bug should be changed, there is more going on here
then just dropping the signal to the monitor. Because the monitors connected to
the iGPU freeze as well (no signal drop, just a freeze).

It would be great if someone could give me some pointers as to where I could
find more useful logs. /var/log/messages doesn't seem to be very informative.
It just says a GPU reset began and that it failed to sends some messages after.
Or do I maybe need to set some boot parameters, or kernel configs to get more
verbose logs?

You are receiving this mail because:
You are watching the assignee of the bug.
dri-devel mailing list

  parent reply index

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-09 20:36 [Bug 206475] New: " bugzilla-daemon
2020-02-10 13:20 ` [Bug 206475] " bugzilla-daemon
2020-02-10 13:21 ` bugzilla-daemon
2020-02-10 16:39 ` bugzilla-daemon
2020-02-10 16:40 ` bugzilla-daemon
2020-02-10 19:33 ` bugzilla-daemon
2020-02-17 13:23 ` bugzilla-daemon
2020-02-21 21:13 ` bugzilla-daemon
2020-02-24 13:50 ` bugzilla-daemon
2020-02-24 13:52 ` bugzilla-daemon
2020-05-22 12:55 ` bugzilla-daemon
2020-05-23 14:40 ` bugzilla-daemon [this message]
2020-05-23 16:44 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-206475-2300-i8x6i7GJWX@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

dri-devel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/dri-devel/0 dri-devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dri-devel dri-devel/ https://lore.kernel.org/dri-devel \
	public-inbox-index dri-devel

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git