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: Wed, 21 Jun 2017 19:04:13 +0000 [thread overview]
Message-ID: <bug-194843-2300-ueADE3tG4y@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-194843-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=194843
Johannes Hirte (johannes.hirte@datenkhaos.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #10 from Johannes Hirte (johannes.hirte@datenkhaos.de) ---
(In reply to Michel Dänzer from comment #7)
> I wonder if there might be memory corruption going on, in which case
> enabling CONFIG_KASAN for the kernel build might give more clues.
You're right, KASAN pointet me at two other bugs:
https://bugzilla.kernel.org/show_bug.cgi?id=195677
https://bugzilla.kernel.org/show_bug.cgi?id=196145
After eliminating this, no more problems with amdgpu happened. Closing this
report as invalid.
--
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
prev parent reply other threads:[~2017-06-21 19:04 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
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 [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-194843-2300-ueADE3tG4y@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.