All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bish, Jim" <jim.bish@intel.com>
To: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>,
	"Larry.Finger@lwfinger.net" <Larry.Finger@lwfinger.net>,
	"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Shrivastava, Shubhangi" <shubhangi.shrivastava@intel.com>,
	"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Critical regression in 4.7-rcX
Date: Fri, 15 Jul 2016 16:36:48 +0000	[thread overview]
Message-ID: <1468600589.8910.6.camel@intel.com> (raw)
In-Reply-To: <9d76da4f-6b5b-9bfc-e3c5-475422696a5f@lwfinger.net>

On Fri, 2016-07-15 at 10:34 -0500, Larry Finger wrote:
> On 07/15/2016 09:43 AM, Ville Syrjälä wrote:
> > 
> > On Fri, Jul 15, 2016 at 04:27:27PM +0200, Daniel Vetter wrote:
> > > 
> > > On Fri, Jul 15, 2016 at 8:55 AM, Linus Torvalds
> > > <torvalds@linux-foundation.org> wrote:
> > > > 
> > > > On Thu, 14 Jul 2016, Larry Finger wrote:
> > > > > 
> > > > > To anyone keeping track of regressions in kernel 4.7, I call
> > > > > your attention to
> > > > > https://bugs.freedesktop.org/show_bug.cgi?id=96675.
> > > > > 
> > > > > This bug causes driver i915 to fail to connect to the
> > > > > display, and results in
> > > > > a blank screen as soon as the kernel is loaded. The only way
> > > > > to operate with
> > > > > kernel 4.7 is to add "nomodeset" to the command line. The
> > > > > problem was bisected
> > > > > to commit f21a21983ef13a ("drm/i915: Splitting
> > > > > intel_dp_detect").
> > > > Daniel? Jani? Time to revert?
> > > Yup. Means that I'll get to revert a pile of patches (plus even
> > > more
> > > in -next), but that's what we get for not handling regressions
> > > timely.
> > > Dave poked me about the same bug already too. But will take a few
> > > days
> > > until the pull is in your inbox I guess.
> > I attached a oneliner to the bug today, that I *think* should fix
> > the
> > problem.
> After I checked out the problem commit and built that kernel with the
> one-line 
> patch, the display works; however, mainline still fails. I am
> currently 
> bisecting to find what other commit fails. At a minimum, we should be
> able to 
> reduce the number of commits that need reverting.
> 
> Larry
I was seeing the same issue Linus reported but very sporadically.
 Assumed it was due to my wierd configuration - eDP + usb type c -> MST
hub -> DVI KVM -> dual head HDMI.  Checked out the one liner - works
for me but I guess there are still other failures.

Jim
> 
> 
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: "Bish, Jim" <jim.bish@intel.com>
To: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>,
	"Larry.Finger@lwfinger.net" <Larry.Finger@lwfinger.net>,
	"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>
Cc: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Shrivastava, Shubhangi" <shubhangi.shrivastava@intel.com>
Subject: Re: [Intel-gfx] Critical regression in 4.7-rcX
Date: Fri, 15 Jul 2016 16:36:48 +0000	[thread overview]
Message-ID: <1468600589.8910.6.camel@intel.com> (raw)
In-Reply-To: <9d76da4f-6b5b-9bfc-e3c5-475422696a5f@lwfinger.net>

On Fri, 2016-07-15 at 10:34 -0500, Larry Finger wrote:
> On 07/15/2016 09:43 AM, Ville Syrjälä wrote:
> > 
> > On Fri, Jul 15, 2016 at 04:27:27PM +0200, Daniel Vetter wrote:
> > > 
> > > On Fri, Jul 15, 2016 at 8:55 AM, Linus Torvalds
> > > <torvalds@linux-foundation.org> wrote:
> > > > 
> > > > On Thu, 14 Jul 2016, Larry Finger wrote:
> > > > > 
> > > > > To anyone keeping track of regressions in kernel 4.7, I call
> > > > > your attention to
> > > > > https://bugs.freedesktop.org/show_bug.cgi?id=96675.
> > > > > 
> > > > > This bug causes driver i915 to fail to connect to the
> > > > > display, and results in
> > > > > a blank screen as soon as the kernel is loaded. The only way
> > > > > to operate with
> > > > > kernel 4.7 is to add "nomodeset" to the command line. The
> > > > > problem was bisected
> > > > > to commit f21a21983ef13a ("drm/i915: Splitting
> > > > > intel_dp_detect").
> > > > Daniel? Jani? Time to revert?
> > > Yup. Means that I'll get to revert a pile of patches (plus even
> > > more
> > > in -next), but that's what we get for not handling regressions
> > > timely.
> > > Dave poked me about the same bug already too. But will take a few
> > > days
> > > until the pull is in your inbox I guess.
> > I attached a oneliner to the bug today, that I *think* should fix
> > the
> > problem.
> After I checked out the problem commit and built that kernel with the
> one-line 
> patch, the display works; however, mainline still fails. I am
> currently 
> bisecting to find what other commit fails. At a minimum, we should be
> able to 
> reduce the number of commits that need reverting.
> 
> Larry
I was seeing the same issue Linus reported but very sporadically.
 Assumed it was due to my wierd configuration - eDP + usb type c -> MST
hub -> DVI KVM -> dual head HDMI.  Checked out the one liner - works
for me but I guess there are still other failures.

Jim
> 
> 
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-07-15 16:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14 19:27 Critical regression in 4.7-rcX Larry Finger
2016-07-15  6:55 ` Linus Torvalds
2016-07-15  6:55   ` Linus Torvalds
2016-07-15 14:27   ` Daniel Vetter
2016-07-15 14:43     ` Ville Syrjälä
2016-07-15 14:43       ` Ville Syrjälä
2016-07-15 14:53       ` Larry Finger
2016-07-15 15:34       ` Larry Finger
2016-07-15 15:34         ` Larry Finger
2016-07-15 16:36         ` Bish, Jim [this message]
2016-07-15 16:36           ` [Intel-gfx] " Bish, Jim
2016-07-15 17:26           ` Larry Finger
2016-07-15 17:26             ` [Intel-gfx] " Larry Finger

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=1468600589.8910.6.camel@intel.com \
    --to=jim.bish@intel.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shubhangi.shrivastava@intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=ville.syrjala@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 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.