dell latitude e6510 screen stays black from suspend

Bug #596080 reported by SF Basilix
106
This bug affects 20 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

The system appears to suspend fine when I close the laptop lid, but when I open it back up, the screen stays black and I see nothing. The laptop is a Dell e6510 with an Intel Core i5.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xorg 1:7.5+5ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
Architecture: amd64
Date: Fri Jun 18 16:22:15 2010
DkmsStatus: Error: [Errno 2] No such file or directory
GdmLog2:

InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
Lsusb:
 Bus 002 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
 Bus 002 Device 002: ID 8087:0020
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0020
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude E6510
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=ab101798-172a-422a-896a-b683ca73ae88 ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
dmi.bios.date: 05/28/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 02K3Y4
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA03:bd05/28/2010:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6510
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-22-generic

Revision history for this message
SF Basilix (sf-basilix) wrote :
Revision history for this message
Leo Arias (elopio) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux.
(With many applications, you can report a future bug directly on the appropriate package by opening the application's "Help" menu and choosing "Report a Problem". https://wiki.ubuntu.com/ReportingBugs)

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Leo Arias (elopio) wrote :

We need more info in order to try to find the problem. Please answer the questions that you will find at https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume and add as separate attachments the files that are requested there.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
SF Basilix (sf-basilix) wrote :

Sorry for the delay and thanks for the assistance. I've attached the files required per the wiki site and have a bit more info regarding what is going on. As it turns out, this is actually a suspend issue. Hybernation worked successfully, when selecting it from the pull down menu in Ubuntu 10.04 (64 bit). What did not work correctly was Suspend. Upon selecting suspend, the system does shut down and the power button on the laptop blinks. However, when turning the laptop back on, by pressing the power button, it does not awaken. The keyboard lights come on and the hard drive makes some noise and shows activity, but I cannot get a display at all. I've tried Alt+F1, Alt+F12 but nothing. The system is completely unresponsive and a hard reboot is required to get it back. I've attached the following files *after* rebooting the laptop and logging back in:

1) dmesg
2) cat /proc/cmdline
3) cat /etc/initramfs-tools/conf.d/resume

The one thing I noticed when examining the cmdline and resume files was that the UUIDs were different. Is this supposed to be the case? Should I modify the /etc/initramfs-tools/conf.d/resume file to reflect the UUID from the /proc/cmdline file?

Thanks.

Revision history for this message
SF Basilix (sf-basilix) wrote :
Revision history for this message
SF Basilix (sf-basilix) wrote :
SF Basilix (sf-basilix)
Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi SF,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kernel-suspend
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Corona (stefaniefauconnier) wrote :

I have the same laptop with the same processor. I tested different mainline builds of 2.6.35, none of them fixes the issue. The patches mentioned here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/578673 only seem to work for the e6410, not for the e6510. The latest drm-intel-next kernel, which already has these patches, does not solve the issue either.

Let me know if you need any extra debugging info, or if I need to open a separate bug report.

Revision history for this message
SF Basilix (sf-basilix) wrote :

@Corona,

Please open a new ticket. I simply cannot keep up with all the bugs and reporting online. Unfortunately, as much as I would love to right now, I'm just so buried and will only cause a major slowdown in resolving this issue. Please post your link to the same problem in this thread for anyone else who is trying to resolve this and if you have time, I would appreciate it if you can run with it. I know this problem exists across the board with other similar Dell laptops as I have been getting emails from others wondering if there's a fix. The problem should not be ignored.

Revision history for this message
bruno pennec (bruno-pennec) wrote :

I had same problem with lucid on my e6510 : Black screen on resume after suspend.
This is resolved for me with kernel 2.6.35.3 that you can find in ppa for Maverick.

Revision history for this message
derf (tterribe) wrote :

Just tried a vanilla 2.6.35.4: the display still fails to turn on at all (though the backlight does come on) unless I revert commit a9daaec5a40d572d11f689edac5cb1710c998b1e (this is the same behavior as 2.6.35). And I still get a blank screen after a suspend/resume cycle (the same as every kernel I've tried).

Revision history for this message
SF Basilix (sf-basilix) wrote :

@derf

I have opened yet another ticket regarding the latest kernels causing the display on my e6510 to go black. This is not normal and there's no fix for it yet as I can't even figure out what is causing this. My ticket was opened a while ago, you can check it out here:

https://bugs.launchpad.net/ubuntu/+bug/628986

Revision history for this message
Alex Escalante (alex-eqitpro) wrote :

For what its worth, I am running Windows 7 on the same laptop and this happens to me as well whenever I close and re-open the lid. i7 nvidia 310m

Revision history for this message
Corona (stefaniefauconnier) wrote :

This is not a dupe, 578673 is for the E6410 only. This bug is for the e6510. As stated in the other bug report, both laptop have slightly different hardware and the problems are caused by different issues.

Revision history for this message
sherbang (sherbang) wrote :

I'm also having this issue. Some further info:
When the laptop resumes the screen stays blank as has been reported by others. Also the capslock key doesn't change the capslock led. The system doesn't seem to respond to any keypresses and there is no disk activity.

In my case this is a core i7 E6510 with nvidia graphics running 64bit.

I had similar (but not quite the same) issues when I first installed lucid, but I added PPAs which gave me the most recent kernel and nvidia drivers and eventually suspend/resume did start working under lucid - so for me this is a regression in Maverick. I did an upgrade to Maverick, not a reinstall.

I'd be happy to provide additional information if it will help.

Thanks

Revision history for this message
Andrew Petro (microcline) wrote :

I believe I also experience this issue on my Dell Latitude E6510.

My internal IT support at my company had this to say:

"I seem to have found the real fix to the suspend/resume problem ... on Dell Latitude E6510 runnning Ubuntu 10.10 (Maverick Meerkat). Apparently some changes in the ACPI code in the 2.6.35 kernel are to blame and are causing this issue across several platforms. This should be fixed permanently in the 2.6.36 kernel. Until then, there is a workaround that has been added to the 2.6.35 kernel.

Assuming you are using Grub2 as your bootloader, go edit /etc/default/grub as root and add "acpi_sleep=nonvs" to the end of the line for the GRUB_CMDLINE_LINUX_DEFAULT variable. Then run "sudo update-grub" to install this into your boot configuration."

I did edit GRUB_CMDLINE_LINUX_DEFAULT in the described way and so far I no longer experience the intermittent fails-to-re-light-screen-after-suspend issue.

Posting my experience here at the direction of Canonical's consumer tech support. I hope this helps to resolve this Ubuntu bug.

Revision history for this message
sherbang (sherbang) wrote :

Thanks for posting Andrew! The acpi_sleep=nonvs setting fixed it for me as well.

komputes (komputes)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
cacula (cacula) wrote :

Thanks for posting Andrew! The acpi_sleep=nonvs setting fixed it for me as well. E6510 maveric x64 8GB RAM nvidia nvs 3100M

Revision history for this message
Dan Faulks (aitaix9) wrote :

didn't work for me :(
E6510 maverick x64 nvidia nvs 3100m

Revision history for this message
isb (isb) wrote :

dell E6510

Nvidia 3100M

kernel: 2.6.35-25-generic #43-Ubuntu SMP

driver: 270.18

suspends, does not come back

broken for months

Revision history for this message
mattcasters (matt-casters) wrote :

Confirmed the bug and the fix on (updated to the latest) 10.10, E6510, 8GB, NVIDIA 3100M, driver 260.19.06

Please note you have to reboot before your kernel knows about the acpi_sleep=nonvs setting.

Revision history for this message
Ian (ifreecarve) wrote :

comment #16 seems to have solved my problem. Running 64-bit Ubuntu 10.10 on Dell Latitude E6510 with proprietary nvidia driver.

Dan Faulks (aitaix9)
Changed in linux (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Brent Rickels (brent-k) wrote : I can't believe you helped me save over $200 on this Cufflinks

Hello Customer

They look and feel exactly like the real thing.
Now you can afford expensive - and classy-looking watch to impress people with, just purchase top quality replica watch or some watches for different occasions. We don't offer cheap imitations. Our watches make you look rich and feel rich. Great selection of most popular brands and models!

****************************************
I got my watch couple days ago. I did like to thank to you first of all. The watch is fantastic and by the way thanks for the pen. It’s beautiful. I was very skeptical about buying things from the internet at the beginning but you changed my opinion. Now I know there are some serious business owners on the internet such as you. Great, reliable and on time service!
Bless
                     Rolando Dooley
****************************************

Click here ---> http://cumer.ru

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.