From: Dave Hansen <dave.hansen@intel.com>
To: Daniel Vetter <daniel.vetter@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: 4.10-rc2 oops in DRM connector code
Date: Mon, 9 Jan 2017 05:46:45 -0800 [thread overview]
Message-ID: <c680eb4f-3b83-0831-7e1d-0f0ba41791ca@intel.com> (raw)
In-Reply-To: <16a1e734-667c-5d9a-c418-555b1f13e446@intel.com>
On 01/09/2017 05:40 AM, Dave Hansen wrote:
> Is there some stable code to go back to here? Or, is there something
> about my configuration that's unique? I really wonder why nobody else
> is running into this.
Here are a couple of similar-looking reports, if that helps:
https://bugzilla.redhat.com/attachment.cgi?id=1209947
https://bugzilla.redhat.com/show_bug.cgi?id=1382342
http://marc.info/?l=openbsd-bugs&m=147487082821348&w=2
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-01-09 13:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 19:03 4.10-rc2 oops in DRM connector code Dave Hansen
2017-01-05 19:53 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-01-09 10:15 ` Daniel Vetter
2017-01-09 12:59 ` Dave Hansen
2017-01-09 13:40 ` Dave Hansen
2017-01-09 13:46 ` Dave Hansen [this message]
2017-01-09 16:41 ` Daniel Vetter
2017-01-09 16:50 ` Dave Hansen
2017-01-09 16:59 ` [Intel-gfx] " Daniel Vetter
2017-01-09 17:22 ` Dave Hansen
2017-01-09 19:34 ` [Intel-gfx] " Alex Deucher
2017-01-09 17:42 ` Dave Hansen
2017-01-10 10:31 ` [Intel-gfx] " Daniel Vetter
2017-01-10 16:52 ` Dave Hansen
2017-01-11 7:43 ` [Intel-gfx] " Daniel Vetter
2017-01-11 15:24 ` Dave Hansen
2017-01-11 15:39 ` Daniel Vetter
2017-01-11 16:16 ` Dave Hansen
2017-01-11 22:25 ` [Intel-gfx] " Daniel Vetter
2017-01-11 15:40 ` Chris Wilson
2017-01-11 20:23 ` ✗ Fi.CI.BAT: warning for 4.10-rc2 oops in DRM connector code (rev2) Patchwork
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=c680eb4f-3b83-0831-7e1d-0f0ba41791ca@intel.com \
--to=dave.hansen@intel.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.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