All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 194843] [amdgpu] oops [drm:gfx_v8_0_priv_reg_irq] *ERROR* Illegal register access in command stream
Date: Tue, 18 Apr 2017 19:40:50 +0000	[thread overview]
Message-ID: <bug-194843-2300-NDrwtVDbrN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-194843-2300@https.bugzilla.kernel.org/>

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

--- Comment #6 from Johannes Hirte (johannes.hirte@datenkhaos.de) ---
Some more observation: It seems the hangs happen much more often/frequent with
kernel 4.11 than with 4.10. Where 4.10 kernels running usually several days, I
have a hang with 4.11 within a day.

Additionally I've found some of the 

WARNING: CPU: 1 PID: 872 at ./include/linux/dma-fence.h:349 amdgpu_vm_grab_id 

entries in the logs without a hang at this time. As far as I've seen this was
always with a 4.10 kernel.

-- 
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:[~2017-04-18 19:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10 20:34 [Bug 194843] New: [amdgpu] oops [drm:gfx_v8_0_priv_reg_irq] *ERROR* Illegal register access in command stream bugzilla-daemon
2017-03-10 20:40 ` [Bug 194843] " bugzilla-daemon
2017-03-10 21:05 ` bugzilla-daemon
2017-03-10 21:05 ` bugzilla-daemon
2017-03-10 21:08 ` bugzilla-daemon
2017-03-12 11:26 ` bugzilla-daemon
2017-04-18 19:40 ` bugzilla-daemon [this message]
2017-04-19  3:23 ` bugzilla-daemon
2017-04-24 12:49 ` bugzilla-daemon
2017-04-24 14:23 ` bugzilla-daemon
2017-06-21 19:04 ` 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-194843-2300-NDrwtVDbrN@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.