From: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: linux-kernel@vger.kernel.org, Imre Deak <imre.deak@intel.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
intel-gfx@lists.freedesktop.org
Subject: Re: 3.8.2->3.8.3 i915 regression: GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5
Date: Sun, 17 Mar 2013 21:10:15 +0100 [thread overview]
Message-ID: <201303172110.15501.a.miskiewicz@gmail.com> (raw)
In-Reply-To: <CAKMK7uHXpjucZhcjMgZXi2QSXOCgA=NZaOv0m2DvfuyT3TAzRw@mail.gmail.com>
On Sunday 17 of March 2013, Daniel Vetter wrote:
> On Sat, Mar 16, 2013 at 11:35 AM, Arkadiusz Miskiewicz
>
> <a.miskiewicz@gmail.com> wrote:
> > On Thursday 14 of March 2013, Arkadiusz Miskiewicz wrote:
> >> Hello.
> >
> >> After upgrading from 3.8.2 to 3.8.3 I'm getting regression :
> > More people hits this:
> > https://bugzilla.redhat.com/show_bug.cgi?id=922304
> > https://bugs.archlinux.org/task/34327
> > (seems always GM45 gpu in these reports)
> >
> > archlinux people also noticed that xrandr reports VGA1 as connected
> > (while in reality nothing is connected to VGA1)
>
> Can you please test whether 3.9-rc kernels are affected, too?
3.9.0-rc2-00341-g0863702
works fine here
[ 0.349462] [drm] Initialized drm 1.1.0 20060810
[ 0.349566] [drm] radeon kernel modesetting enabled.
[ 0.350049] [drm] Memory usable by graphics device = 2048M
[ 0.350110] i915 0000:00:02.0: setting latency timer to 64
[ 0.374161] i915 0000:00:02.0: irq 47 for MSI/MSI-X
[ 0.374170] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 0.374229] [drm] Driver supports precise vblank timestamp query.
[ 0.436916] fbcon: inteldrmfb (fb0) is primary device
[ 0.983961] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 0.983996] i915 0000:00:02.0: registered panic notifier
[ 0.986191] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor
0
xrandr reports VGA-1 as disconnected properly
> We need
> to know this since stable rules mandate that a regression is fixed on
> upstream first. Once that's figured out we can backport a fix (if
> 3.9-rc works) or start working on a fix for 3.8-rc kernels first and
> backport afterwards.
>
> Thanks, Daniel
--
Arkadiusz Miśkiewicz, arekm / maven.pl
prev parent reply other threads:[~2013-03-17 20:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 20:36 3.8.2->3.8.3 i915 regression: GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 Arkadiusz Miskiewicz
2013-03-14 22:19 ` Michael Leun
2013-03-18 20:20 ` Greg Kroah-Hartman
2013-03-16 10:35 ` Arkadiusz Miskiewicz
2013-03-17 19:40 ` Daniel Vetter
2013-03-17 20:10 ` Arkadiusz Miskiewicz [this message]
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=201303172110.15501.a.miskiewicz@gmail.com \
--to=a.miskiewicz@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=gregkh@linuxfoundation.org \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--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