Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1443712 > unrolled thread

Critical regression in 4.7-rcX

Started byLarry Finger <Larry.Finger@lwfinger.net>
First post2016-07-14 21:30 +0200
Last post2016-07-15 19:30 +0200
Articles 8 — 5 participants

Back to article view | Back to linux.kernel

Contents

  Critical regression in 4.7-rcX Larry Finger <Larry.Finger@lwfinger.net> - 2016-07-14 21:30 +0200
    Re: Critical regression in 4.7-rcX Linus Torvalds <torvalds@linux-foundation.org> - 2016-07-15 09:00 +0200
      Re: Critical regression in 4.7-rcX Daniel Vetter <daniel.vetter@ffwll.ch> - 2016-07-15 16:30 +0200
        Re: Critical regression in 4.7-rcX Ville Syrjälä <ville.syrjala@linux.intel.com> - 2016-07-15 16:50 +0200
          Re: Critical regression in 4.7-rcX Larry Finger <Larry.Finger@lwfinger.net> - 2016-07-15 17:00 +0200
          Re: Critical regression in 4.7-rcX Larry Finger <Larry.Finger@lwfinger.net> - 2016-07-15 17:40 +0200
            Re: [Intel-gfx] Critical regression in 4.7-rcX "Bish, Jim" <jim.bish@intel.com> - 2016-07-15 18:40 +0200
              Re: [Intel-gfx] Critical regression in 4.7-rcX Larry Finger <Larry.Finger@lwfinger.net> - 2016-07-15 19:30 +0200

#1443712 — Critical regression in 4.7-rcX

FromLarry Finger <Larry.Finger@lwfinger.net>
Date2016-07-14 21:30 +0200
SubjectCritical regression in 4.7-rcX
Message-ID<rUUuB-5j0-3@gated-at.bofh.it>
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").

This bug was reported on 2016-06-25 16:10 UTC, but seems to have received no 
attention by the Intel group. That is the reason that I am complaining here. It 
seems very likely that kernel 4.7 will be released with this bug, and a number 
of high-end Toshiba laptops will break.

Thanks,

Larry
-- 
If I was stranded on an island and the only way to get off
the island was to make a pretty UI, I’d die there.

Linus Torvalds

[toc] | [next] | [standalone]

#1443976

FromLinus Torvalds <torvalds@linux-foundation.org>
Date2016-07-15 09:00 +0200
Message-ID<rV5gl-3BF-11@gated-at.bofh.it>
In reply to#1443712
[ Adding the proper people to the cc. ]

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?

              Linus

[toc] | [prev] | [next] | [standalone]

#1444346

FromDaniel Vetter <daniel.vetter@ffwll.ch>
Date2016-07-15 16:30 +0200
Message-ID<rVchQ-7ZP-11@gated-at.bofh.it>
In reply to#1443976
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.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

[toc] | [prev] | [next] | [standalone]

#1444349

FromVille Syrjälä <ville.syrjala@linux.intel.com>
Date2016-07-15 16:50 +0200
Message-ID<rVcBb-86v-7@gated-at.bofh.it>
In reply to#1444346
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

[toc] | [prev] | [next] | [standalone]

#1444353

FromLarry Finger <Larry.Finger@lwfinger.net>
Date2016-07-15 17:00 +0200
Message-ID<rVcKR-8a2-17@gated-at.bofh.it>
In reply to#1444349
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.

Unfortunately, that patch did not help. If you have any other patches, or a repo 
I can pull from for testing, please let me know.

Larry

[toc] | [prev] | [next] | [standalone]

#1444380

FromLarry Finger <Larry.Finger@lwfinger.net>
Date2016-07-15 17:40 +0200
Message-ID<rVdnz-ap-7@gated-at.bofh.it>
In reply to#1444349
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

[toc] | [prev] | [next] | [standalone]

#1444437 — Re: [Intel-gfx] Critical regression in 4.7-rcX

From"Bish, Jim" <jim.bish@intel.com>
Date2016-07-15 18:40 +0200
SubjectRe: [Intel-gfx] Critical regression in 4.7-rcX
Message-ID<rVejF-K7-49@gated-at.bofh.it>
In reply to#1444380
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

[toc] | [prev] | [next] | [standalone]

#1444469 — Re: [Intel-gfx] Critical regression in 4.7-rcX

FromLarry Finger <Larry.Finger@lwfinger.net>
Date2016-07-15 19:30 +0200
SubjectRe: [Intel-gfx] Critical regression in 4.7-rcX
Message-ID<rVf61-1fR-1@gated-at.bofh.it>
In reply to#1444437
On 07/15/2016 11:36 AM, Bish, Jim wrote:
> 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.

I'm not sure what I did wrong before, but when I retested mainline with the one 
liner, it now works. Once that is pushed to mainline, the bug should be fixed.

Sorry for any confusion.

Larry

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web