All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 204559] amdgpu: kernel oops with constant gpu resets while using mpv
Date: Sat, 07 Sep 2019 06:58:35 +0000	[thread overview]
Message-ID: <bug-204559-2300-kP3QUus3fr@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204559-2300@https.bugzilla.kernel.org/>

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

--- Comment #11 from Christopher Snowhill (kode54@gmail.com) ---
Oops, I neglected to mention: The system is non-responsive to input devices, as
the USB input appears to all be completely powered off after the GPU crashes,
but the network interface is still working, as is sound output, and I'm able to
log into the machine via SSH. It does, however, lock up if I attempt to soft
reboot it.

The full dmesg from the session that eventually crashed is still available in
the journal, up to where it was flooding sdma0 timeouts and failures.

-- 
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:[~2019-09-07  6:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-12 10:53 [Bug 204559] New: amdgpu: kernel oops with constant gpu resets while using mpv bugzilla-daemon
2019-08-12 13:04 ` [Bug 204559] " bugzilla-daemon
2019-08-12 13:30 ` bugzilla-daemon
2019-08-12 14:19 ` bugzilla-daemon
2019-08-12 14:22 ` bugzilla-daemon
2019-08-12 15:56 ` bugzilla-daemon
2019-08-12 16:42 ` bugzilla-daemon
2019-08-12 16:56 ` bugzilla-daemon
2019-08-12 17:01 ` bugzilla-daemon
2019-08-12 17:26 ` bugzilla-daemon
2019-09-07  6:55 ` bugzilla-daemon
2019-09-07  6:58 ` bugzilla-daemon [this message]
2019-10-25 16:38 ` bugzilla-daemon
2020-01-03 17:40 ` bugzilla-daemon
2020-01-07 22:31 ` bugzilla-daemon
2022-01-17 22:52 ` 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-204559-2300-kP3QUus3fr@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.