From: Jani Nikula <jani.nikula@linux.intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
daniel.vetter@intel.com, airlied@linux.ie
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: log splat from Intel DRM driver on resume
Date: Mon, 26 Sep 2016 09:11:35 +0300 [thread overview]
Message-ID: <878tufp4vc.fsf@intel.com> (raw)
In-Reply-To: <20160923092003.45c86105@xeon-e3>
On Fri, 23 Sep 2016, Stephen Hemminger <stephen@networkplumber.org> wrote:
> When I resume my desktop from suspend, the following shows up in the log.
> Running 4.8.0-rc6 (net-next branch).dme
Please clarify what that is.
Please file a bug at [1] and attach full dmesg from the boot, with
drm.debug=14 module parameter.
BR,
Jani.
[1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-09-26 6:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 16:20 log splat from Intel DRM driver on resume Stephen Hemminger
2016-09-26 6:11 ` Jani Nikula [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=878tufp4vc.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stephen@networkplumber.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).