From: Greg KH <gregkh@linuxfoundation.org>
To: Rainer Fiebig <jrf@mailbox.org>
Cc: stable@vger.kernel.org
Subject: Re: 4.9.62: intermittent flicker after upgrade from 4.9.61
Date: Sun, 19 Nov 2017 11:07:12 +0100 [thread overview]
Message-ID: <20171119100712.GA25266@kroah.com> (raw)
In-Reply-To: <faf76b8a-baa9-01a2-3f17-ce9aa0be4877@mailbox.org>
On Sat, Nov 18, 2017 at 05:08:20PM +0100, Rainer Fiebig wrote:
> Greg KH wrote:
> > On Sat, Nov 18, 2017 at 01:47:32PM +0100, Rainer Fiebig wrote:
> >> Hi!
> >>
> >> Hopefully the right addressee.
> >>
> >> Encountered two bad backports which cause screen-flicker.
> >> dmesg shows:
> >>
> >> ...
> >> [drm:ironlake_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
> >> [drm:ironlake_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun
> >> [drm:ironlake_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun
> >> [drm:ironlake_irq_handler [i915]] *ERROR* PCH transcoder B FIFO underrun
> >> ...
> >>
> >> CPU: Intel Core i3 (Clarkdale/Ironlake)
> >>
> >> The backports are:
> >>
> >> - diff --git a/drivers/gpu/drm/i915/intel_pm.c
> >> b/drivers/gpu/drm/i915/intel_pm.c
> >> index 49de476..277a802 100644
> >> - diff --git a/drivers/gpu/drm/i915/intel_drv.h
> >> b/drivers/gpu/drm/i915/intel_drv.h
> >> index a19ec06..3ce9ba3 100644
> >>
> >> After reversing them the flicker is gone, no more messages in dmesg. All
> >> else OK so far.
> >
> > So which commit was the one that caused the problem? I will be glad to
> > revert it.
> >
> > thanks,
> >
> > greg k-h
> >
> >
>
> I started by reverting the more complex one first ("index
> 49de476..277a802100644"). But the kernel wouldn't compile then.
What git commit id is that? I don't see those ids in the 4.9-stable
tree.
> So I also reverted "index a19ec06..3ce9ba3 100644". After that the
> kernel compiled just fine and the problems were gone (still are).
Same here, what git commit id was this?
thanks,
greg k-h
next prev parent reply other threads:[~2017-11-19 10:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-18 12:47 4.9.62: intermittent flicker after upgrade from 4.9.61 Rainer Fiebig
2017-11-18 12:51 ` Greg KH
2017-11-18 16:08 ` Rainer Fiebig
2017-11-19 10:07 ` Greg KH [this message]
2017-11-19 11:02 ` Rainer Fiebig
2017-11-19 11:56 ` Rainer Fiebig
2017-11-19 12:08 ` Greg KH
2017-11-19 12:44 ` Rainer Fiebig
2017-11-19 13:27 ` Greg KH
2017-11-20 8:40 ` Jani Nikula
2017-11-20 8:51 ` Rainer Fiebig
2017-11-20 11:27 ` Maarten Lankhorst
2017-11-20 11:38 ` Rainer Fiebig
2017-11-20 12:07 ` Maarten Lankhorst
2017-11-20 11:45 ` Rainer Fiebig
2017-11-20 12:17 ` Rainer Fiebig
2017-11-23 21:09 ` Rainer Fiebig
2017-11-24 6:48 ` Greg KH
2017-11-24 6:57 ` Rainer Fiebig
2017-11-24 7:03 ` Rainer Fiebig
2017-11-28 9:17 ` Greg KH
2017-11-18 17:19 ` Rainer Fiebig
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=20171119100712.GA25266@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jrf@mailbox.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).