[i855gm] Lid close with intel 82852/855GM provokes black screen, loss of control and overheat

Bug #462939 reported by Zenigata17
94
This bug affects 15 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: xserver-xorg-video-intel

Well basicly this bug looks almost like bug #138256 :

When closing the lid and reopening it, the screen remains black and the laptop is not responding to anything (ctrl alt + Fx, ctrl alt +backspace or even SysRq are not working) the only way to get out is to power off the laptop with button.

Tis bug is quite dangerous because the PC is NOT in suspend mode : it generate a lot of heat, and thus closing the lid and putting the laptop in a bag may result in dangerous overheat leading irremediable to hardware failure.

1) #138256 is old (2007) and fix is released, when this is a bug I did not have under 9.04 and have under 9.10
2) Putting the following in xorg.conf does not help

Section "Device"
 ... <other options here> ...
 Option "ForceEnablePipeA" "true"
EndSection

Maybe the solution 2 works if there is something else than xorg.conf where to put this since a few Ubuntu release xorg.conf is minimalistic.

I believe this bug is very severe.

ProblemType: Bug
Architecture: i386
Date: Wed Oct 28 22:54:32 2009
DistroRelease: Ubuntu 9.10
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Dell Computer Corporation Latitude D400
Package: xserver-xorg-video-intel 2:2.9.0-1ubuntu2
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   3.3V 32-bit PC Card
 Socket 1:
   no card
ProcCmdLine: root=UUID=bac99d64-6dae-4fc0-bb2c-1124f8e5a6fa ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=POSIX
 SHELL=/bin/zsh
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu7
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SourcePackage: xserver-xorg-video-intel
Uname: Linux 2.6.31-14-generic i686
XsessionErrors:
 (gnome-settings-daemon:2467): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:2467): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:2521): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:2496): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (gnome-panel:2494): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window
dmi.bios.date: 06/28/2005
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A08
dmi.board.name: 0W0328
dmi.board.vendor: Dell Computer Corporation
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: dmi:bvnDellComputerCorporation:bvrA08:bd06/28/2005:svnDellComputerCorporation:pnLatitudeD400:pvr:rvnDellComputerCorporation:rn0W0328:rvr:cvnDellComputerCorporation:ct8:cvr:
dmi.product.name: Latitude D400
dmi.sys.vendor: Dell Computer Corporation
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-14-generic

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02)
     Subsystem: Dell Device [1028:0139]

Revision history for this message
Zenigata17 (bedouin-drebon) wrote :
summary: - Lid close with intel 82852/855GM provoques black screen, loss of control
- and overeat
+ Lid close with intel 82852/855GM provokes black screen, loss of control
+ and overheat
Bryce Harrington (bryce)
Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Confirmed
Revision history for this message
Zenigata17 (bedouin-drebon) wrote : Re: Lid close with intel 82852/855GM provokes black screen, loss of control and overheat

This does not occur when putting the laptop in suspend mode via the session menu, but this may occur when power-manager turns off the screen.

Geir Ove Myhr (gomyhr)
summary: - Lid close with intel 82852/855GM provokes black screen, loss of control
- and overheat
+ [i855GM]Lid close with intel 82852/855GM provokes black screen, loss of
+ control and overheat
tags: added: 855gm karmic
summary: - [i855GM]Lid close with intel 82852/855GM provokes black screen, loss of
+ [i855GM] Lid close with intel 82852/855GM provokes black screen, loss of
control and overheat
Revision history for this message
slhoir (sebastien-lhoir) wrote :

Lid close or standby with nVidia Corporation G72M [Quadro NVS 110M/GeForce Go 7300] (rev a1)
--> loss of control

Revision history for this message
Zenigata17 (bedouin-drebon) wrote :

Is there any news, or anything I can do to provide more information ?

Revision history for this message
Zenigata17 (bedouin-drebon) wrote :

Well as far as I can see, maybe re-enabling the i810 driver would solve the problem, or making an alternate set of xserver-xorg-video-intel driver that would be the same as the one of jeunty would do te trick...

Anyow, I do not see any option the is able to solve that problem with the current intel driver...

Revision history for this message
Zenigata17 (bedouin-drebon) wrote :
Revision history for this message
kludge (undercovercop) wrote :

confirmed on dell latitude d400, fresh 9.10 install, using intel driver with xorg.

Revision history for this message
kludge (undercovercop) wrote :

follow up: worked around bug by adding "nomodeset" kernel paramter, a la bug 385445

Revision history for this message
Zenigata17 (bedouin-drebon) wrote :

If I set nomodeset, I am unable to start X, I got a fully blinking screen on a console login, with the keyboard only working synchronously with the blink.

However, I can start X if running recovery mode.

Revision history for this message
Zenigata17 (bedouin-drebon) wrote :

Well it indeed seems to be a duplicate of 385445...

Kludge, could you please post your xorg.conf, I'd like to understand why I am unable to launch X if I set nomodeset.

Thank you

Revision history for this message
Zenigata17 (bedouin-drebon) wrote :

Ah, if this bug is really linked to KMS, is it a driver or a kernel bug ?

Revision history for this message
kludge (undercovercop) wrote :

reconstructing xorg.conf from memory (on another machine not booted and i gotta run out the house):

Section "Device"

Identifier "Builtin Default intel device 0"
# I stole the identifier from Xorg.0.conf run with no xorg.conf
Driver "intel"
Option "ForceEnablePipeA" "True"

EndSection

...and that's it; everything else is autodetected. for thoroughness sake, i ought to test without it, but i haven't yet.

also, it's a driver bug. drivers are part of the kernel, but also their own separate projects.

Revision history for this message
Zenigata17 (bedouin-drebon) wrote :

Strange, I am still unable to launch X without modeset...

And by running a X -configure, the option ForceEnalePipeA seems to not be listed by X as options supported by the intel driver...

Revision history for this message
Mads Bennedbæk (mads-bennedbaek) wrote :

The nomodeset parameter worked on my D400.

I don't have a xorg.conf, just running with Ubuntu default, no special options.

Revision history for this message
Zenigata17 (bedouin-drebon) wrote :

Ok, the workaround works, I had troubles because I tried the ppa xorg-edgers dirvers to see if they fix the thing...

So with the Ubuntu's official repositories, and disabling the modesetting with the kernel parameter options (I am not sure wether the ForceEnablePipeA option is required) seems very effective.

However this bug is still problematic because :

    * It makes KMS unusable
    * The newer releases of xorg intel driver seem to require KMS, so if this is not fixed upstream there will be a problem with no workaround for future Ubuntu releases...

Revision history for this message
Zenigata17 (bedouin-drebon) wrote :

On other weird side effects, after disabling KMS, when I et into gnome, my pointer is invisible, but if I switch to tty1 and back to tty7, then it is visible...

My laptop also tends to randomly freeze (but is still accessible y ssh) and with no process wonsumming cpu...

Revision history for this message
beekley (beekley) wrote :

I can confirm having the exact problem with Dell Latitude D400 and a fresh install of Karmic.

Revision history for this message
Zenigata17 (bedouin-drebon) wrote :

Well te freeze while kms being deactiated has nothing to do with this (it's a problem with my wifi card)

But I can confirm that disabling modesetting makes the mouse pointer invisble in gnome without switching to a TTY and back to gnome...

Revision history for this message
millenium-hand (yairgordon) wrote :

I have the same issues, also with dell d400.
I upgraded from Jaunty, where this was not an issue at all, to Karmic, where this is a most frustrating issue.

Bryce Harrington (bryce)
description: updated
Revision history for this message
Stanislas Couix (stanislas-couix) wrote :

Hi everybody !

I am experiencing the same problem. I'm under Karmic, a fresh install, a 82852/855GM graphic card (but on a Dell 510m). The "nomodeset" workaround didn't work for me. But maybe I've missed something as in grub-pc, there is no /boot/grub/menu.lst and you have to set options in /etc/default/grub. I tried to set nomodeset on this line :
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"

Closing the lid still freeze the system. No escape !! hard and dirty reboot is still the only way.

Did anyone have any clue ?

Thanks !

Stan

Bryce Harrington (bryce)
tags: added: black-screen
Bryce Harrington (bryce)
summary: - [i855GM] Lid close with intel 82852/855GM provokes black screen, loss of
- control and overheat
+ [i855] [i855GM] Lid close with intel 82852/855GM provokes black screen,
+ loss of control and overheat
Bryce Harrington (bryce)
summary: - [i855] [i855GM] Lid close with intel 82852/855GM provokes black screen,
- loss of control and overheat
+ [i855gm] Lid close with intel 82852/855GM provokes black screen, loss of
+ control and overheat
Revision history for this message
Brian D (turbo) wrote :

...add me to the list for this bug, as well. Dell Latitude D400 with built-in i855 graphics. Running Linux Mint 8 (Helena), which is essentially Ubuntu 9.10 / Karmic with a few bells & whistles tacked on.

I will try the kernel boot parameter when I get home tonight, and report back here if it doesn't seem to temporarily resolve the issue for me. I previously had Linux Mint 7 (Gloria) on this laptop, which is essentially Ubuntu 9.04 / Jaunty ...so, my issues are identical to those related in these comments... suspend/resume works fine under Jaunty (or Mint 7) and doesn't work under Karmic (or Mint 8).

Revision history for this message
Stefan Glasenhardt (glasen) wrote :

This is not a problem of the intel-driver. It's a kernel-bug! Just boot the system with activated KMS and no Xserver running. Close the lid and ... crash.

Revision history for this message
Bryce Harrington (bryce) wrote :

Yeah sounds like it needs the lid-close quirk

affects: xserver-xorg-video-intel (Ubuntu) → linux (Ubuntu)
tags: added: kms
Revision history for this message
Bryce Harrington (bryce) wrote :

If anyone gets a chance to test this with lucid, you should add the tag 'lucid-kms' so it gets on the kernel team's radar. It's not likely to get on their list if it is only tested against karmic.

Be aware though that kms got blacklisted for i855 but quite a few people have reported this isn't working for them, so you will need to force kms on by passing the kernel option i915.radeon=1 from grub.

Revision history for this message
Peter M. Clausen (pclausen) wrote :

I have tested Lucid 10.04 on a Dell Lattitude D505 with Intel Corporation 82852/855GM Graphics. This bug seems to pop up SOMETIMES...

I can boot alright with following kernels using /etc/modprobe.d/i915-kms.conf "options i915 modeset=1":
/boot/vmlinuz-2.6.32-15-generic
/boot/vmlinuz-2.6.32-21-generic
/boot/vmlinuz-2.6.32-22-generic
/boot/vmlinuz-2.6.34rc3-51-generic (from https://launchpad.net/~brian-rogers/+archive/experimental )

One of the kernels did not boot correctly without the modeset option.

I have also updated to the intel driver:
deb http://ppa.launchpad.net/ubuntu-x-swat/x-updates/ubuntu lucid main

which seems to run a bit smoother. But this bug still persist in all configurations. Please tell me if I can give you any hints / logs to help fix this problem.

Revision history for this message
Peter M. Clausen (pclausen) wrote :

With the latest updates and kernel: 2.6.32-22-generic the problem seems to be fixed, although it persist with 2.6.34rc3-51-generic

I am quite unsure regarding what the solution may be, because I have been messing quite a bit around with my settings (xorg.conf) now using intel driver, UXA grafics accelleration according to http://www.ubuntugeek.com/intel-graphics-performance-guide-for-ubuntu-904-jaunty-users.html

Right now I am not going to change a working system. :-)

tags: added: lucid-kms
Revision history for this message
Peter M. Clausen (pclausen) wrote :

well I retried to install ubuntu 10.04.1 (hoping the intel issues were solve - my mistake) and updated the following:

$ sudo add-apt-repository ppa:glasen/intel-driver
$ sudo apt-get update && sudo apt-get upgrade

$ sudo add-apt-repository ppa:glasen/855gm-fix
$ sudo apt-get update && sudo apt-get install dkms 855gm-fix-dkms

as described in https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes

the problem persist and I am back in Ubuntu 8.04...

Revision history for this message
Peter M. Clausen (pclausen) wrote :

oh, yeah, tried the ForceEnablePipeA-quirck (see bug #138256) but that also did not resolve the problem

I tried to revert the ppa-changes, but failed and I am now not able to get ubuntu 10.04.1 running at all...

Revision history for this message
Peter M. Clausen (pclausen) wrote : apport information

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 2575 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with STAC9750,51 at irq 5'
   Mixer name : 'SigmaTel STAC9750,51'
   Components : 'AC97a:83847650'
   Controls : 36
   Simple ctrls : 23
DistroRelease: Ubuntu 10.04
LiveMediaBuild: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude D505
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash i915.modeset=1 -- console-setup/layoutcode=de
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Regression: Yes
RelatedPackageVersions: linux-firmware 1.34.1
Reproducible: Yes
RfKill:

Tags: lucid graphics regression-potential needs-upstream-testing
Uname: Linux 2.6.32-24-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 01/28/2005
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0H2049
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/28/2005:svnDellInc.:pnLatitudeD505:pvr:rvnDellInc.:rn0H2049:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D505
dmi.sys.vendor: Dell Inc.

tags: added: apport-collected
Revision history for this message
Peter M. Clausen (pclausen) wrote : AlsaDevices.txt

apport information

Revision history for this message
Peter M. Clausen (pclausen) wrote : AplayDevices.txt

apport information

Revision history for this message
Peter M. Clausen (pclausen) wrote : ArecordDevices.txt

apport information

Revision history for this message
Peter M. Clausen (pclausen) wrote : BootDmesg.txt

apport information

Revision history for this message
Peter M. Clausen (pclausen) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Peter M. Clausen (pclausen) wrote : Card0.Codecs.codec97.0.ac97.0.0.txt

apport information

Revision history for this message
Peter M. Clausen (pclausen) wrote : Card0.Codecs.codec97.0.ac97.0.0.regs.txt

apport information

Revision history for this message
Peter M. Clausen (pclausen) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Peter M. Clausen (pclausen) wrote : IwConfig.txt

apport information

Revision history for this message
Peter M. Clausen (pclausen) wrote : Lspci.txt

apport information

Revision history for this message
Peter M. Clausen (pclausen) wrote : PciMultimedia.txt

apport information

Revision history for this message
Peter M. Clausen (pclausen) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Peter M. Clausen (pclausen) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Peter M. Clausen (pclausen) wrote : ProcModules.txt

apport information

Revision history for this message
Peter M. Clausen (pclausen) wrote : UdevDb.txt

apport information

Revision history for this message
Peter M. Clausen (pclausen) wrote : UdevLog.txt

apport information

Revision history for this message
Peter M. Clausen (pclausen) wrote : WifiSyslog.txt

apport information

Revision history for this message
Peter M. Clausen (pclausen) wrote :

To reproduce bug:

- clean install ubuntu 10.04.1 (using i915.modeset=1 , seehttps://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes )
- System -> Preference -> Powermanagement
  * set laptop lid close-action to "blank screen"

I ran apport-collect 462939 to get above infos

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
Revision history for this message
kalehrl (kalehrl) wrote :

I've reported the same bug against the latest Ubuntu release here:
https://bugs.launchpad.net/bugs/1254131

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.