All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110509] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout
Date: Tue, 30 Apr 2019 10:44:25 +0000	[thread overview]
Message-ID: <bug-110509-502-0zVy9d7fKV@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110509-502@http.bugs.freedesktop.org/>


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

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

--- Comment #11 from James.Dutton@gmail.com ---
I tried with drm-next-5.2-wip.

It does not hang any more, but I have a new error now.

It is better, in the sense that I can now reboot the system normally, and not
resort to echo b >/proc/sysrq-trigger

[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

After the GPU reset, the screen is corrupted.
I can do, via ssh,  service gdm stop.  service gdm start   and I then get a
working login screen. (Mouse moves, I can type in password)
I cannot actually login because X fails. The desktop fails to appear and it
returns to the login greeter screen.

I will try to get more details when I have time later.

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

[-- Attachment #1.2: Type: text/html, Size: 1621 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-04-30 10:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 17:26 [Bug 110509] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout bugzilla-daemon
2019-04-24 17:31 ` bugzilla-daemon
2019-04-24 17:32 ` bugzilla-daemon
2019-04-24 17:33 ` bugzilla-daemon
2019-04-24 17:35 ` bugzilla-daemon
2019-04-28 15:42 ` bugzilla-daemon
2019-04-29 13:41 ` bugzilla-daemon
2019-04-29 18:30 ` bugzilla-daemon
2019-04-29 22:41 ` bugzilla-daemon
2019-04-30  1:26 ` bugzilla-daemon
2019-04-30 10:40 ` bugzilla-daemon
2019-04-30 10:44 ` bugzilla-daemon [this message]
2019-04-30 14:22 ` bugzilla-daemon
2019-04-30 14:26 ` bugzilla-daemon
2019-04-30 14:43 ` bugzilla-daemon
2019-08-13 20:56 ` bugzilla-daemon
2019-08-13 21:20 ` bugzilla-daemon
2019-09-25 18:49 ` 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-110509-502-0zVy9d7fKV@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 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.