EeePC 1000 screen black waking up from sleep

Bug #1406054 reported by Velo Traveler
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

See the bug description at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283938

When netbook running Xubuntu X-Windows session is woken up from sleep (for example, after closing and re-opening lid while running Xubuntu), I am prompted for my password, then the screen goes black. I can control-alt-F1 and get a text console, machine is still up and running, I can switch back to X session, get black screen, but use control-alt-T to open a new terminal window, and run the reboot command successfully. As per one of the comments on above-referenced bug description, I was able to recover screen by restarting lightdm, but then wifi was no longer working.

$ uname -a
Linux ubookie 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:44 UTC 2014 i686 i686 i686 GNU/Linux

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-43-generic 3.13.0-43.72
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic i686
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: elr 1847 F.... pulseaudio
CurrentDesktop: XFCE
Date: Sun Dec 28 00:59:34 2014
InstallationDate: Installed on 2014-08-18 (132 days ago)
InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723)
MachineType: ASUSTeK Computer INC. 1000
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-43-generic root=UUID=f40fa2f9-e64e-483d-ba67-336eae39eac6 ro rootflags=subvol=@ quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-43-generic N/A
 linux-backports-modules-3.13.0-43-generic N/A
 linux-firmware 1.127.10
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/01/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0803
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1000
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/01/2008:svnASUSTeKComputerINC.:pn1000:pvrx.x:rvnASUSTeKComputerINC.:rn1000:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 1000
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

Revision history for this message
Velo Traveler (5-ubuntuone-j) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
penalvch (penalvch)
tags: added: bios-outdated-1003
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Velo Traveler (5-ubuntuone-j) wrote :

Problem still happening after BIOS upgrade. Requested info below:

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
1003
06/11/2009

Revision history for this message
Velo Traveler (5-ubuntuone-j) wrote :

Still happening with latest BIOS.

Is there any command-line workaround besides restarting lightdm?

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

Velo Traveler, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested exactly shown as:
kernel-fixed-upstream-3.19-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: latest-bios-1003
removed: bios-outdated-1003
Changed in linux (Ubuntu):
importance: Low → Medium
status: Confirmed → Incomplete
tags: added: resume suspend
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Velo Traveler (5-ubuntuone-j) wrote :

have not been able to try out the upstream kernel yet.

Just upgraded with apt-get to 3.13.0-46-generic #79-Ubuntu SMP Tue mar 10 20:08:14 UTC 2015 i686, problem still exists.

Changed in linux (Ubuntu):
status: Expired → Incomplete
Revision history for this message
Kevin Lipe (kevin-lipe) wrote :

Seeing exactly this same issue on a fresh installation of Xubuntu 14.10 on my Thinkpad X200.

Revision history for this message
Kevin Lipe (kevin-lipe) wrote :

sorry, forgot to include uname -a on my machine:
Linux frenesi 3.16.0-31-generic #43-Ubuntu SMP Tue Mar 10 17:37:36 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
penalvch (penalvch) wrote :

Kevin Lipe, it would help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.