All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Shubhangi Shrivastava <shubhangi.shrivastava@intel.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: Critical regression in 4.7-rcX
Date: Fri, 15 Jul 2016 17:43:30 +0300	[thread overview]
Message-ID: <20160715144330.GI4329@intel.com> (raw)
In-Reply-To: <CAKMK7uFspkDUOh8f-w895rLAe6c8y-FnsuCcT4edG_0XeN0SYg@mail.gmail.com>

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.

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
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: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	LKML <linux-kernel@vger.kernel.org>,
	Shubhangi Shrivastava <shubhangi.shrivastava@intel.com>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: Critical regression in 4.7-rcX
Date: Fri, 15 Jul 2016 17:43:30 +0300	[thread overview]
Message-ID: <20160715144330.GI4329@intel.com> (raw)
In-Reply-To: <CAKMK7uFspkDUOh8f-w895rLAe6c8y-FnsuCcT4edG_0XeN0SYg@mail.gmail.com>

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.

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2016-07-15 14:43 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ä [this message]
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
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=20160715144330.GI4329@intel.com \
    --to=ville.syrjala@linux.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 \
    /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.