From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Gorman <chrisjohgorman@gmail.com>, intel-gfx@lists.freedesktop.org
Subject: Re: Unclaimed read from register 0x1f0034
Date: Thu, 03 Aug 2017 17:19:27 +0300 [thread overview]
Message-ID: <87a83ghgy8.fsf@nikula.org> (raw)
In-Reply-To: <CAHVeOW9-JLogJ2=65j6+CEz5CF=Ha7ne1puMzWaRYTEANG6wWg@mail.gmail.com>
On Sun, 23 Jul 2017, Chris Gorman <chrisjohgorman@gmail.com> wrote:
> I'm not too sure where to report this but I got an unusual output in dmesg
> a couple of days ago and wanted to pass it on. Please let me know if I
> need to submit a bug report too.
If you can reproduce it, please file a bug over at [1], along with
dmesg. If you can run with drm.debug=14 module parameter, even better.
BR,
Jani.
[1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-08-03 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-23 19:59 Unclaimed read from register 0x1f0034 Chris Gorman
2017-08-03 14:19 ` Jani Nikula [this message]
2017-08-03 14:25 ` Chris Wilson
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=87a83ghgy8.fsf@nikula.org \
--to=jani.nikula@linux.intel.com \
--cc=chrisjohgorman@gmail.com \
--cc=intel-gfx@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.