[i855GME] system freezes when switching to external monitor

[jhansonxi]

Binary package hint: xserver-xorg-video-intel

Ubuntu Hardy 8.04 beta w/updates. Toshiba M35X-S114 with 855GME integrated video.
If I use the Fn+F5 display switch without an external monitor connected the system usually freezes. No log messages, no magic SysReq, no remote ssh, no LED toggling - just a black screen with a frozen mouse cursor. It doesn't matter if the monitor was connected when X was started. Even with it connected the switch doesn't seem to have any effect on display switching as the view is cloned regardless (which matches BIOS setting). There is only a small display flicker when the switch is actuated to indicated that anything happened (unless it freezes). Freeze does not occur with the i810 or vesa drivers or from within a VT with the intel driver. The i810 driver correctly cycles between the built-in, external, and both. Occurs with previous versions of the intel driver also (Bryce Harrington builds):
xserver-xorg-video-intel_2.1.0+git20070625.ccac60bf-1_i386.deb
xserver-xorg-video-intel_2.2.0+git20080102.0fd769b5-1_i386.deb

Also occurs with Fedora 9 beta on a Panasonic CF-51 with the same chipset. It has a serial port but there isn't any messages on the serial console either when it occurs.

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller [8086:3580] (rev 02)
     Subsystem: Toshiba America Info Systems Unknown device [1179:ff00]
00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02) (prog-if 00 [VGA controller])
     Subsystem: Toshiba America Info Systems Unknown device [1179:ff00]

[Jeff (jeff-redhat-bugs)]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.13) Gecko/20080325 Ubuntu/7.10 (gutsy) Firefox/2.0.0.13

Description of problem:
Fedora 9 beta w/updates. Panasonic CF-51 with 855GME integrated video.
If I use the Fn+F3 display switch without an external monitor connected the system usually freezes. No log messages, no magic SysReq, no remote ssh, no LED toggling, no messages on serial console - just a black screen with a frozen mouse cursor. It doesn't matter if the monitor was connected when X was started. Even with it connected the switch doesn't seem to have any effect on display switching as the view is cloned regardless. There is only a small display flicker when the switch is actuated to indicated that anything happened (unless it decides to freeze). I tried switching to the i810 driver but it can't find any devices. The vesa driver works and switches correctly with the external monitor connected and doesn't misbehave if it's not.

Version-Release number of selected component (if applicable):
xorg-x11-drv-i810-2.2.1-19.fc9.i386

How reproducible:
Always

Steps to Reproduce:
1.Login to desktop with intel driver enabled.
2.Disconnect external monitor.
3.Attempt to switch to external monitor.

Actual Results:
Black screen with mouse cursor, system freeze.

Expected Results:
Either not switch or black out and return after subsequent key actuation.

Additional info:
A similar bug exists in Ubuntu Hardy 8.04 beta with a Toshiba M35X-S114 using the same chipset: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/213191

[jhansonxi (jhansonxi)]

Fedora bug report: https://bugzilla.redhat.com/show_bug.cgi?id=441192

[Jeff (jeff-redhat-bugs)]

Created attachment 301459
lspci -vvnn

[Jeff (jeff-redhat-bugs)]

Created attachment 301460
dmesg

[Jeff (jeff-redhat-bugs)]

Created attachment 301461
General log not specific to occurance of problem

[mjhorsnell (matt-horsnell)]

Same occurs for me: Ubuntu 8.04 with updates (also occurred in 7.04). Using a Fujitsu-Siemens Lifebook P7010, has an intel 855GM graphics chipset.

[mjhorsnell (matt-horsnell)]

Added email notification.

[mjhorsnell (matt-horsnell)]

Hi,

I applied the patch mentioned here:

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/225958

and rebuilt xserver-xorg-video-intel using the instructions here:

https://wiki.ubuntu.com/UbuntuPackagingGuide/BuildFromDebdiff

I can now switch to external vga for presentations etc without the machine freezing up... does anyone have an update about when the patch will be committed to the repositories?

Thanks :)

[Bug (bug-redhat-bugs)]

Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[Bryce Harrington (bryce)]

Hi mjhorsnell, the patch is committed to hardy-updates as 2:2.2.1-1ubuntu13. We've got a few more updates queued up in -proposed too.

[Bryce Harrington (bryce)]

jhansonxi, I see that there's already a quirk for your 1179:ff00 card (via patch 12_quirk_sync.patch) which is also taken upstream. Are you still having this same problem with the released Hardy?

If so, does it make any difference whether ForceEnablePipeA is set to true or false?

Given that you're unable to ssh into the machine, my best guess is that it is a kernel issue... ogasawara, what steps could he take to help identify if it's a kernel issue?

[Leann Ogasawara (leannogasawara)]

Hi jhansonxi,

First if you can confirm if Bryce's suggestions work or not that would be great. If the issue still exists, one thing you may want to give a try is booting with the kernel parameter nmi_watchdog=1 . I've included a small explanation of what this parameter is used for:

"On many x86/x86-64 type hardware there is a feature that enables us to generate 'watchdog NMI interrupts'. (NMI: Non Maskable Interrupt which get executed even if the system is otherwise locked up hard). This can be used to debug hard kernel lockups. By executing periodic NMI interrupts, the kernel can monitor whether any CPU has locked up, and print out debugging messages if so. . . .A 'lockup' is the following scenario: if any CPU in the system does not execute the period local timer interrupt for more than 5 seconds, then the NMI handler generates an oops and kills the process. This
'controlled crash' (and the resulting kernel messages) can be used to debug the lockup. Thus whenever the lockup happens, wait 5 seconds and the oops will show up automatically. If the kernel produces no messages then the system has crashed so hard (eg. hardware-wise) that either it cannot even accept NMI interrupts, or the crash has made the kernel unable to print messages."

Please let us know your results using this parameter. If you could also attach the output of 'cat /proc/version_signature' so we know the exact kernel version you are running that would be great as well.

Additionally, I may also have you test an newer kernel available in the kernel-ppa (personal package archive). It is still however in the process of being built so won't be available for the next day or so. I'll be sure to update this report and provide instructions on how to install when it is ready. But, in the mean time if you could do the above testing requested by Bryce as well as myself that would be great. Thanks!

[Orestes Mas (orestes)]

Similar problem for me on a DELL latitude D620 with an integrated 945GM intel video card (devce ID 8086:27a2). I can only switch (Fn+F8) one or two times to an external monitor or beamer before system hangs completely.

I was desperated, but today, reading a lot of forum posts I tried to uninstall package xserver-xorg-video-intel (and also xserver-xorg-video-all, which is a reverse dependence), and after a X reboot xorg picked up the driver in xserver-xorg-video-i810 package and the hangups are gone!

Just so happy that I wanted to share my experience. Maybe it's useful to others.

[Bryce Harrington (bryce)]

I think we can close this one as fixed; the original issue should be solved now.

@orestes, while your issue does sound similar, I would ask that you file it as a new bug if it is still occurring with the current version of karmic. Please file the bug using 'ubuntu-bug xserver-xorg-video-intel' so that it includes all the necessary files.

[Bug (bug-redhat-bugs)]

This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[Bug (bug-redhat-bugs)]

Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.