Ubuntu
linux package

[Dell Latitude 2110] Screen is blank after restoring from hibernate

Bug #904844 reported by Daniel Manrique on 2011-12-15

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Fix Released	Medium	Unassigned

Bug Description

To reproduce on a fully-updated Precise installation on this system:

- Open a terminal and type sudo pm-hibernate
- After the system hibernates, restart it by pressing power button, so it starts loading the kernel / system again

Expected result:
- System resumes where it left off and the screen restores correctly.

Actual result:
- System does resume and works fine, EXCEPT for the screen, which is completely blank. The backlight is on, but there is nothinig displayed.

An easy workaround is to put the system to sleep (S3), either by closing the lid, or "blind-typing" to issue e.g. pm-suspend. Once the system resumes from suspend, the display is back to normal and can be used. No data is lost if this technique is used.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-4-generic 3.2.0-4.10
ProcVersionSignature: Ubuntu 3.2.0-4.10-generic 3.2.0-rc5
Uname: Linux 3.2.0-4-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 1.90-0ubuntu1
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1385 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf6dfc000 irq 47'
   Mixer name : 'Realtek ALC269VB'
   Components : 'HDA:10ec0269,10280461,00100100'
   Controls : 16
   Simple ctrls : 10
Date: Thu Dec 15 11:50:44 2011
HibernationDevice: RESUME=UUID=066d6226-da21-4afb-8f46-54933770f3f8
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111129.1)
MachineType: Dell Inc. Latitude 2110
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-generic root=UUID=bdb7ca01-1f93-419b-a71d-98a93c40591a ro quiet splash initcall_debug vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-4-generic N/A
linux-backports-modules-3.2.0-4-generic N/A
linux-firmware 1.63
SourcePackage: linux
StagingDrivers: rts_pstor
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: X06
dmi.board.name: MOE3C3
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrX06:bd01/25/2010:svnDellInc.:pnLatitude2110:pvr:rvnDellInc.:rnMOE3C3:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude 2110
dmi.sys.vendor: Dell Inc.

Tags:

Revision history for this message

Daniel Manrique (roadmr) wrote on 2011-12-15:

AcpiTables.txt Edit (129.0 KiB, text/plain; charset="utf-8")
AlsaDevices.txt Edit (382 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (119.6 KiB, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (2.2 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.0.txt Edit (9.0 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (71.0 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.9 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (509 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (12.0 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (390 bytes, text/plain; charset="utf-8")
PciMultimedia.txt Edit (599 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.0 KiB, text/plain; charset="utf-8")
PulseSinks.txt Edit (2.1 KiB, text/plain; charset="utf-8")
PulseSources.txt Edit (3.4 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (240 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (106.0 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (256.7 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (2.4 MiB, text/plain; charset="utf-8")

Brad Figg (brad-figg) on 2011-12-15

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Brad Figg (brad-figg) wrote on 2011-12-16: Test with newer development kernel (3.2.0-5.11)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status:	Confirmed → Incomplete
tags:	added: kernel-request-3.2.0-5.11

Revision history for this message

Daniel Manrique (roadmr) wrote on 2011-12-16:

Hi Brad! (or brad-bot!)

I did a full dist-upgrade on this system, it brought me up to this kernel version:

Linux version 3.2.0-5-generic (buildd@rothera) (gcc version 4.6.2 (Ubuntu/Linaro 4.6.2-7ubuntu1) ) #11-Ubuntu SMP Thu Dec 15 19:04:59 UTC 2011

With this kernel, the observed behavior is still present.

I'm switching the bug to Confirmed as per the bot instructions, but not touching the kernel-request tag.

Let me know if you need any logs or information from this system.

Thanks!

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2011-12-16:

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest v3.2-rcN kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.2-rc1'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. If you believe this bug does not require upstream testing, please add the tag: 'kernel-upstream-testing-not-needed'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

Changed in linux (Ubuntu):
importance:	Undecided → Medium
tags:	added: needs-upstream-testing
Changed in linux (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

Daniel Manrique (roadmr) wrote on 2011-12-16:

Hi Joseph!

Yes, I tested the 3.2.0-rc5 kernel, version string as follows:

Linux version 3.2.0-030200rc5-generic (root@gomeisa) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #201112091935 SMP Sat Dec 10 00:44:15 UTC 2011

With this kernel I still observe the reported behavior. I hibernate, then restore, the display is blank, I close the lid to suspend the system, open it again to resume, and then the display is fine). Note that, after resuming from suspend, the system crashes after about 5 seconds, but that's another issue - the behavior as reported here is still present.

I'll remove needs-upstream-testing and put back to confirmed.

tags:

removed: needs-upstream-testing

Daniel Manrique (roadmr) on 2012-01-05

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

Brad Figg (brad-figg) wrote on 2012-01-05: Test with newer development kernel (3.2.0-7.13)

Thank you for taking the time to file a bug report on this issue.

You can update to the latest development kernel by simply running the following commands in a terminal window:

sudo apt-get update
sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status:	Confirmed → Incomplete
tags:	added: kernel-request-3.2.0-7.13

Revision history for this message

Daniel Manrique (roadmr) wrote on 2012-01-11:

Hi,

This problem is still present with kernel 3.2.0-8.14:

3.2.0-8-generic-pae #14-Ubuntu SMP Fri Jan 6 03:57:56 UTC 2012 i686 i686 i386 GNU/Linux

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

Brad Figg (brad-figg) wrote on 2012-01-11: Test with newer development kernel (3.2.0-8.14)

Thank you for taking the time to file a bug report on this issue.

You can update to the latest development kernel by simply running the following commands in a terminal window:

sudo apt-get update
sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status:	Confirmed → Incomplete
tags:	added: kernel-request-3.2.0-8.14

Revision history for this message

Daniel Manrique (roadmr) wrote on 2012-01-11:

Hi, I see a bot is in action :)

The kernel I tested is 3.2.0-8.14. I'm setting this back to confirmed.

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

Brad Figg (brad-figg) wrote on 2012-01-12: Test with newer development kernel (3.2.0-8.15)

#10

Thank you for taking the time to file a bug report on this issue.

You can update to the latest development kernel by simply running the following commands in a terminal window:

sudo apt-get update
sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status:	Confirmed → Incomplete
tags:	added: kernel-request-3.2.0-8.15

Revision history for this message

Daniel Manrique (roadmr) wrote on 2012-02-08:

#11

Hi,

I retested with Precise Alpha2, kernel is 3.2.0-12.21. The issue is no longer present; the screen is restored correctly after hibernating.

Marking fix released, thanks!

Changed in linux (Ubuntu):
status:	Incomplete → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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

Ubuntulinux package

[Dell Latitude 2110] Screen is blank after restoring from hibernate

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package