latitude e6410 has blank screen on return from suspend

Bug #595604 reported by John Trostel
40
This bug affects 7 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned

Bug Description

A new latitude e6410 (with Intel graphics) will go into suspend but returns with a blank screen (black screen). The fan turns back on and some HDD and wireless/network activity is seen, but there seems to be no way to get a terminal or X window back on. Attempts to use Kamal's newly patched kernel have proven fruitless also.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-23-generic 2.6.32-23.37~kamal~always~sci~en
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-23.38~kamal~always~sci~en~0-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
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: jt 1615 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf6960000 irq 22'
   Mixer name : 'Intel G45 DEVIBX'
   Components : 'HDA:111d76d5,1028040a,00100104 HDA:80862804,80860101,00100000'
   Controls : 22
   Simple ctrls : 13
Date: Thu Jun 17 13:26:39 2010
HibernationDevice: RESUME=UUID=87ea457c-6957-477f-b592-150054b94ecd
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: Dell Inc. Latitude E6410
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-23-generic root=UUID=9c923afc-4d5a-468c-953a-14de15b239c2 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.1
SourcePackage: linux
dmi.bios.date: 03/05/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A01
dmi.board.name: 0667CC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA01:bd03/05/2010:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0667CC:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6410
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.

Revision history for this message
John Trostel (jtrostel-gmail) wrote :
Revision history for this message
John Trostel (jtrostel-gmail) wrote :

The 'duplicate' bug #578673 is a different architecture (i386 vs. amd64) and is a different processor (i5 vs. i7 core). This is not to say that the same solution may not fix both these bugs. (I have tried the solutions mentioned in the 'duplicate' bug also...)

Should this remain marked as a duplicate? (It is close, but not a duplicate...)

Revision history for this message
Kamal Mostafa (kamalmostafa) wrote :

@John - Its probably not crucial whether this remains marked as a duplicate or not at this point... If the other bug gets declared to be fixed but you still experience the problem, we can detach them later.

Regarding your comment that you see HDD and network activity after the resume... Perhaps its just graphics that are hung? If you have another machine on the same network, you could try ssh'ing into the e6410 to check on that, as outlined in https://help.ubuntu.com/community/DebuggingSystemCrash .

Revision history for this message
John Trostel (jtrostel-gmail) wrote :
Download full text (13.7 KiB)

Appears that it's just the graphics that are hung. SSHing in reveals the following in /var/log/message.

Jun 17 15:27:28 jtrostele6410 kernel: [ 6008.294032] PM: Syncing filesystems ... done.
Jun 17 15:27:28 jtrostele6410 kernel: [ 6008.612416] Freezing user space processes ... (elapsed 0.00 seconds) done.
Jun 17 15:27:28 jtrostele6410 kernel: [ 6008.613001] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
Jun 17 15:27:28 jtrostele6410 kernel: [ 6008.613048] Suspending console(s) (use no_console_suspend to debug)
Jun 17 15:27:28 jtrostele6410 kernel: [ 6008.771975] PM: suspend of drv:ieee80211 dev:phy0 complete after 159.067 msecs
Jun 17 15:27:28 jtrostele6410 kernel: [ 6008.870551] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 17 15:27:28 jtrostele6410 kernel: [ 6008.871044] sd 0:0:0:0: [sda] Stopping disk
Jun 17 15:27:28 jtrostele6410 kernel: [ 6009.868371] PM: suspend of drv:sd dev:0:0:0:0 complete after 1000.210 msecs
Jun 17 15:27:28 jtrostele6410 kernel: [ 6010.311877] PM: suspend of drv:psmouse dev:serio1 complete after 424.742 msecs
Jun 17 15:27:28 jtrostele6410 kernel: [ 6010.426971] sdhci-pci 0000:03:00.0: PCI INT B disabled
Jun 17 15:27:28 jtrostele6410 kernel: [ 6010.566498] ehci_hcd 0000:00:1d.0: PCI INT A disabled
Jun 17 15:27:28 jtrostele6410 kernel: [ 6011.793468] hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x304f000c
Jun 17 15:27:28 jtrostele6410 kernel: [ 6011.793710] HDA Intel 0000:00:1b.0: PCI INT A disabled
Jun 17 15:27:28 jtrostele6410 kernel: [ 6011.813465] PM: suspend of drv:HDA Intel dev:0000:00:1b.0 complete after 1249.939 msecs
Jun 17 15:27:28 jtrostele6410 kernel: [ 6011.813478] ehci_hcd 0000:00:1a.0: PCI INT A disabled
Jun 17 15:27:28 jtrostele6410 kernel: [ 6011.978121] e1000e 0000:00:19.0: PCI INT A disabled
Jun 17 15:27:28 jtrostele6410 kernel: [ 6011.978127] e1000e 0000:00:19.0: PME# enabled
Jun 17 15:27:28 jtrostele6410 kernel: [ 6011.978133] e1000e 0000:00:19.0: wake-up capability enabled by ACPI
Jun 17 15:27:28 jtrostele6410 kernel: [ 6011.993033] PM: suspend of drv:e1000e dev:0000:00:19.0 complete after 179.978 msecs
Jun 17 15:27:28 jtrostele6410 kernel: [ 6012.042978] PM: suspend of devices complete after 3437.913 msecs
Jun 17 15:27:28 jtrostele6410 kernel: [ 6012.042982] PM: suspend devices took 3.440 seconds
Jun 17 15:27:28 jtrostele6410 kernel: [ 6012.082824] PM: late suspend of devices complete after 39.934 msecs
Jun 17 15:27:28 jtrostele6410 kernel: [ 6012.085799] ACPI: Preparing to enter system sleep state S3
Jun 17 15:27:28 jtrostele6410 kernel: [ 6012.182540] Disabling non-boot CPUs ...
Jun 17 15:27:28 jtrostele6410 kernel: [ 6012.343376] Broke affinity for irq 25
Jun 17 15:27:28 jtrostele6410 kernel: [ 6012.344461] CPU 1 is now offline
Jun 17 15:27:28 jtrostele6410 kernel: [ 6012.346421] Broke affinity for irq 26
Jun 17 15:27:28 jtrostele6410 kernel: [ 6012.347634] CPU 2 is now offline
Jun 17 15:27:28 jtrostele6410 kernel: [ 6012.349337] Broke affinity for irq 12
Jun 17 15:27:28 jtrostele6410 kernel: [ 6012.349362] Broke affinity for irq 27
Jun 17 15:27:28 jtrostele6410 kernel: [ 6012.349374] Broke affinity for irq 33
Jun 17 15:27:28 jtrostele641...

Revision history for this message
Kamal Mostafa (kamalmostafa) wrote :

@John - First, I see that Carlos reports the same AE_TIME errors in the bug this is marked a duplicate of -- I do suspect its the same issue. Second, it looks to me like the timestamps shown in the kernel log go crazy (at the point where you resume?):
...
Jun 17 15:27:28 jtrostele6410 kernel: [ 6012.451896] CPU 3 is now offline
Jun 17 15:27:28 jtrostele6410 kernel: [ 6012.451898] SMP alternatives: switching to UP code
Jun 17 15:27:28 jtrostele6410 kernel: [ 6012.456180] Extended CMOS year: 2000
Jun 17 15:27:28 jtrostele6410 kernel: [18446744049.075235] Extended CMOS year: 2000
Jun 17 15:27:28 jtrostele6410 kernel: [18446744049.075259] Enabling non-boot CPUs ...
Jun 17 15:27:28 jtrostele6410 kernel: [18446744049.075437] SMP alternatives: switching to SMP code
Jun 17 15:27:28 jtrostele6410 kernel: [18446744049.079124] Booting processor 1 APIC 0x4 ip 0x6000

Please try booting with the kernel param "notsc".

Revision history for this message
Carlos Parra Camargo (carlospc) wrote :

John: JFYI, i've also tried the solutions mentioned in the #578673 but I still having the same issue.

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

Other bug subscribers

Remote bug watches

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