System crashes when attaching external monitor to Dell E5410

[Tim Wahrendorff]

when attaching an external monitor to a Dell Latitude E5410 and going to System->Settings->Displays the system crashes (laptopdisplay turns black and no response). Same thing when booting with external monitor attached or if composite effects are turned off.

If logged in via ssh, the Terminal will also crash. When trying to log in via ssh after a crash happened, just nothing happens in the console.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: tim 1884 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd7d40000 irq 22'
   Mixer name : 'Intel G45 DEVIBX'
   Components : 'HDA:111d7605,10280429,00100104 HDA:80862804,80860101,00100000'
   Controls : 22
   Simple ctrls : 13
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=15e5838d-8ffe-43a7-8270-7ebf4782d90d
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: Dell Inc. Latitude E5410
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-23-generic root=UUID=97e7c0f5-7087-4253-bb0e-ddbf05c6c119 ro quiet splash
ProcEnviron:
 LANG=de_DE.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Regression: No
RelatedPackageVersions: linux-firmware 1.34.1
Reproducible: Yes
Tags: lucid graphics needs-upstream-testing
Uname: Linux 2.6.32-23-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 06/02/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 03VXMC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA03:bd06/02/2010:svnDellInc.:pnLatitudeE5410:pvr0001:rvnDellInc.:rn03VXMC:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5410
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.

[Tim Wahrendorff (tim.timwahrendorff)]

apport information

[Tim Wahrendorff (tim.timwahrendorff)]

apport information

[Tim Wahrendorff (tim.timwahrendorff)]

apport information

[Tim Wahrendorff (tim.timwahrendorff)]

apport information

[Tim Wahrendorff (tim.timwahrendorff)]

apport information

[Tim Wahrendorff (tim.timwahrendorff)]

apport information

[Tim Wahrendorff (tim.timwahrendorff)]

apport information

[Tim Wahrendorff (tim.timwahrendorff)]

apport information

[Tim Wahrendorff (tim.timwahrendorff)]

apport information

[Tim Wahrendorff (tim.timwahrendorff)]

apport information

[Tim Wahrendorff (tim.timwahrendorff)]

apport information

[Tim Wahrendorff (tim.timwahrendorff)]

apport information

[Tim Wahrendorff (tim.timwahrendorff)]

apport information

[Tim Wahrendorff (tim.timwahrendorff)]

apport information

[Tim Wahrendorff (tim.timwahrendorff)]

apport information

[Tim Wahrendorff (tim.timwahrendorff)]

apport information

[Tim Wahrendorff (tim.timwahrendorff)]

apport information

[Tim Wahrendorff (tim.timwahrendorff)]

apport information

[Tim Wahrendorff (tim.timwahrendorff)]

tested some upstream kernels, too.(33,34,35) same thing...

[Tim Wahrendorff (tim.timwahrendorff)]

maybe worth a word: with 2.5.35-999 Kernel, the screen does not turn complety off when crashing.
Instead backlight is still on and the mouse cursor is shown, but: It is still a total systemfreeze and you have to turn the power off and reboot, like with the other kernels.

[Tom Gallacher (tom-gallacher)]

I Have the same model and am having the same problem as described above.

[Tom Gallacher (tom-gallacher)]

I failed to mention that I am running 10.04 (64 Bit)

[Julien Enoch (julien-enoch)]

Don't know if this could help, but I noticed following (with same hardware):

1) booting on Ubuntu 10.04 (64 bits) Live CD, not intalling but testing:
I succeed to connect and configure an external monitor !
But with an installed Ubuntu, I have the same bug than Tim reported

2) installing Kubuntu 10.04 (64 bits):
I succeed to connect and configure an external monitor !
But when shuting down, the laptop freezes, and rebooting with external monitor connected also freezes the system.

3) Mandriva 2010.1 (64 bits) suffers the same issue than Kubuntu

[Gabriele Arnulfo (gabriele-arnulfo)]

I've just installed the 2.6.35-14-generic from maverick backports. It makes me able to configure a dual monitor but after switching back to single monitor configuration I report similar bug as Tim but my system gives me a console where I could restart gdm by hand.

[Jeremy Foshee (jeremyfoshee)]

Folks,
    I need those of you affected by a similar issue to the reporter to file new bugs for your issue. This is per the Team Policy on Duplicates that relates to hijacking of bugs by well meaning users. Please have a look at: https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs

Having said that, please also keep in mind that the backport kernel is only supported on Server edition and is therefore not supported on the desktop, even if it should work.

Tim,
    It sounds like you were having a complete GPU hang that you are not seeing now on a mainline build. Does my assessment sound correct?

Thanks!

~JFo

[Tim Wahrendorff (tim.timwahrendorff)]

Jeremy, I am not sure, what you are saying.
In my eyes it's both a complete GPU hang, only difference: After searching for the external monitor on the mainline build the laptop-monitor does not turn completely off, instead it shows the mouse arrow on black background. No chance to move the mouse arrow or fall back to console, but it is more than nothing. External monitor stays black and does not even flicker on any tested kernels.

Good to

[Tim Wahrendorff (tim.timwahrendorff)]

... see people are working on this issue... sorry for double post, it's late here in Germany ;)