From: Jani Nikula <jani.nikula@linux.intel.com>
To: Kai Huang <kai.huang@linux.intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: Call trace on SKL with 4.3.0-rc3+ kernel
Date: Tue, 27 Oct 2015 11:40:10 +0200 [thread overview]
Message-ID: <87611svedh.fsf@intel.com> (raw)
In-Reply-To: <562F291C.50300@linux.intel.com>
On Tue, 27 Oct 2015, Kai Huang <kai.huang@linux.intel.com> wrote:
> I got below Call Trace when booting my 4.3.0-rc3+ kernel on my SKL DT
> machine. Although my machine boots up despite this call trace, I think
> it's better to report it (and hopefully this is the right mailing list
> to report).
Please try v4.3-rc7. If that doesn't help, please file a bug at
https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-10-27 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 7:34 Call trace on SKL with 4.3.0-rc3+ kernel Kai Huang
2015-10-27 9:40 ` Jani Nikula [this message]
2015-10-27 15:59 ` John Doe
2015-10-28 1:11 ` Matt Roper
2015-10-28 12:42 ` Jani Nikula
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=87611svedh.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kai.huang@linux.intel.com \
/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