From: Chris Wilson <chris@chris-wilson.co.uk>
To: Paul Rolland <rol@witbe.net>,
linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Cc: rol@witbe.net
Subject: Re: [3.0.0-rc3] GMBUS timed out
Date: Thu, 16 Jun 2011 15:08:48 +0100 [thread overview]
Message-ID: <d08817$d6fmn@azsmga001.ch.intel.com> (raw)
In-Reply-To: <20110616154123.259414a3@tux.DEF.witbe.net>
On Thu, 16 Jun 2011 15:41:23 +0200, Paul Rolland (=?UTF-8?B?44Od44O844Or44O744Ot44Op44Oz?=) <rol@witbe.net> wrote:
> Hello,
>
> I've just booted 3.0.0-rc3 on my machine, and I got that message :
> Jun 16 15:32:07 tux kernel: [drm] GMBUS timed out, falling back to bit banging on pin 5 [i915 gmbus dpb]
>
> I've checked my logs, and I never got that with my previous 2.6.39.1
> kernel, so that looks like something new to 3.x.
Attempting to use GMBUS when enabled for 3.0. It will have to be
disabled again until the GMBUS/GPIO adapter aligns better with the i2c
interface and doesn't cause a deadlock upon booting with the eeprom
module.
In the meantime, if you have the time and inclination, you can help by
working out under what conditions GMBUS fails. That info message is only
generated after we write a message over GMBUS and receive no response.
I've looked into one exchange that suggests that we may timeout if the
monitor is disconnected. Do you have anything connected to what would be
the first external output? Does the message go away if you boot with
that connected/disconnected?
> Should I report more details (and if so, which ones) or is that harmless
> (though I doubt kernel messages about a time out are harmless ;)
It's harmless in this case. Just a warning that the new hw driven method
failed and we are now using the old CPU driven method.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-06-16 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 13:41 [3.0.0-rc3] GMBUS timed out Paul Rolland
2011-06-16 14:08 ` Chris Wilson [this message]
2011-06-16 15:45 ` Paul Rolland
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='d08817$d6fmn@azsmga001.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rol@witbe.net \
/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