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.
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 ;)
Paul
PS : Added intel-gfx and dri-devel from previous emails related to i915,
but I'm not subscribed to these lists.
On Thu, 16 Jun 2011 15:41:23 +0200, Paul Rolland (=?UTF-8?B?44Od44O844Or44O744Ot44Op44Oz?=) <[email protected]> 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
Hi Chris,
On Thu, 16 Jun 2011 15:08:48 +0100
Chris Wilson <[email protected]> wrote:
> 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.
Hey, that sounds promising ;) Glad I don't have that kind of HW...
> 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.
It is logged at 15:32:07 on my machine, and at that time, the machine was
fully up with X/KDE/compiz running.
It is a laptop and xrandr reports :
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y axis)
331mm x 207mm 1440x900 60.1*+
1024x768 60.0
800x600 60.3 56.2
640x480 59.9
VGA1 disconnected (normal left inverted right x axis y axis)
1920x1080@60Hz 60.0
DP1 disconnected (normal left inverted right x axis y axis)
But I'm used to work with a screen connected to VGA1, and I connect it
usually once my KDE session is started, and I activate it manually using
xrandr.
I just tried to repeat the process... but got another bug : activating the
second screen for the second time (after deactivating it) just resulted in
garbage on that screen. Primary (LVDS) is still ok, but VGA1 contains some
black area, and some part of the LVDS1 (though the resolution not being the
same makes it funny).
No GMBUS message again... Gotta have to reboot...
....
OK, rebooted, step by step :
1 - Boot : no message,
2 - Start my KDE session : no message
3 - Connect the screen on the VGA1 port : no message
4 - Let KDE Daemon prompt me a screen has been connected, and click
Ignore : no message
5 - Run my second screen activation screen : got the message !
Here is what the script does :
MODE=1920x1080@60Hz
$XRANDR --output LVDS1 --primary
$XRANDR --newmode $MODE 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -HSync +Vsync
$XRANDR --addmode VGA1 $MODE
$XRANDR --output VGA1 --mode $MODE --right-of LVDS1
$XRANDR --output LVDS1 --primary
> 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?
Only the LVDS1 connected at the time of the boot, but the message occured
later.
> > 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.
OK, so I guess that me feeling the display is less responsive when
switching desktop is just a feeling.
Paul
--
Paul Rolland E-Mail : rol(at)witbe.net
CTO - Witbe.net SA Tel. +33 (0)1 47 67 77 77
Les Collines de l'Arche Fax. +33 (0)1 47 67 77 99
F-92057 Paris La Defense RIPE : PR12-RIPE
LinkedIn : http://www.linkedin.com/in/paulrolland
Skype : rollandpaul
"I worry about my child and the Internet all the time, even though she's
too young to have logged on yet. Here's what I worry about. I worry that 10
or 15 years from now, she will come to me and say 'Daddy, where were you
when they took freedom of the press away from the Internet?'"
--Mike Godwin, Electronic Frontier Foundation