[Samsung NP350E5C-A02AU] Suspend hang with blank screen on lid open

Bug #1320554 reported by slumbergod
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

When I close the lid of my laptop in either 13.10 or 14.04, then open it again, intermittently there is a blank screen and I am unable to do anything at all, not even start an alternative log in. The only option is to hold the power button in. In the system's power settings suspend and hibernation are disabled but those settings would seem ignored. This issue does not occur in 13.04.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-27-generic 3.13.0-27.50
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: slumbergod 2145 F.... pulseaudio
CurrentDesktop: XFCE
Date: Sun May 18 09:14:41 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-04-18 (29 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140414)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 350V5C/351V5C/3540VC/3440VC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic.efi.signed root=UUID=7ef0aef5-c4f9-45fb-b729-95b463a492d6 ro quiet splash acpi_backlight=vendor vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-27-generic N/A
 linux-backports-modules-3.13.0-27-generic N/A
 linux-firmware 1.127.2
SourcePackage: linux
StagingDrivers: rts5139
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P09ABE
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NP350E5C-A02AU
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: BOARD REVISION 00
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP09ABE:bd07/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn350V5C/351V5C/3540VC/3440VC:pvrP09ABE.012.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350E5C-A02AU:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 350V5C/351V5C/3540VC/3440VC
dmi.product.version: P09ABE.012.CP
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
slumbergod (slumbergod) 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)
summary: - Suspend hang with blank screen on lid open
+ [Samsung NP350E5C-A02AU] Suspend hang with blank screen on lid open
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
slumbergod (slumbergod) wrote :

There is no BIOS update. I am using the latest BIOS update, as provided through Samsung's SW Update software (P09ABE).

In fact, the New Zealand Samsung support website doesn't even list any BIOS update and most of their software downloads are only available for Windows XP, which this laptop never came with. It is a Windows 8 only machine.

Clearly, Samsung are making no effort to support their machines with linux. What information could they provide that would allow developers to fix these issues.

Now the wireless mouse has stopped being detected on reboot. No changes to the system were made other than booting to windows to check for BIOS updates. Now mouse is not detected with any kernel, including 3.14.1-031401-lowlatency

Revision history for this message
slumbergod (slumbergod) wrote :

So it isn't just me....
https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1303736

I am just unlucky in that not only do have the suspend/blank screen bug, but my hardware also gives me the disappearing wireless mouse on reboot!

Revision history for this message
penalvch (penalvch) wrote :

slumbergod, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine 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. For example:
kernel-fixed-upstream-3.15-rc5

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. As well, please remove the tag:
needs-upstream-testing

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

As well, please remove the tag:
needs-upstream-testing

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-p09abe
Changed in linux (Ubuntu):
importance: Low → Medium
Revision history for this message
slumbergod (slumbergod) wrote :

Christopher, I have changed kernel to 3.15.0-031500rc2-generic.
After reboot, the **wireless mouse was not detected**

I have changed back from xscreensaver to light-locker.
Bug #1303736 suggests that the bug is with the interaction between light-locker and xfce4-power-manager settings.
Lots of Xubuntu users are affected.

I'll continue using this kernel until it something goes wrong but these issues are starting the affect my ability to work on my machine and soon I will revert back to Xubuntu 13.04, the last stable Xubuntu.

Revision history for this message
slumbergod (slumbergod) wrote :

I had to reboot to a different kernel. I couldn't log into my VPN with 3.15.0-031500rc2-generic.

I decided to see which kernels would give me my wireless mouse back after a reboot.
Tried 3.13.0-27-generic > no wireless mouse detected
Tried 3.13.0-26-generic > yes, mouse detected

With it working again I decided to retry the others again
Tried 3.13.0.24-generic > yes, mouse detected
Re-Tried 3.13.0.27-generic > yes, mouse detected

I just don't get it. It seems completely random as to whether the wireless mouse is detected. No other changes are made between reboots -- it is just sometimes the mouse is detected and sometimes it isn't.

I'd like to say it is my system has a hardware fault but then it works flawlessly with Xubuntu 13.04 and Windows 8.1

penalvch (penalvch)
tags: added: regression-release
Revision history for this message
slumbergod (slumbergod) wrote :

With v3.15-rc5-utopic
-- wireless mouse was detected
-- unable to connect to my VPN so reverted back to 3.13.0-27-generic

I woke up this morning to find my machine had suspended to a black screen using 3.13.0-27-generic. I am now almost certain the issue is entirely related to light-locker and xfce4-power-manager and will not be resolved until those packages are updated.

The issue with the disappearing wireless mouse on reboot (which seems to be entirely random because sometimes it is not present and other times is detected normally even when the *same* kernel is used) would be Samsung's lack of transparency with their hardware.

If someone could tell me what the kernel developers need to include better support for Samsung laptops I would happily try contacting Samsung to plead for better support.

Revision history for this message
penalvch (penalvch) wrote :

slumbergod, just to clarify, this bug report is only about your computer suspending to a black screen. Any other issues regarding mouse detection, VPN, etc. would need to be handled in a separate report, one per issue. Hence, when using the latest upstream kernel, was the suspend to black screen problem reproducible?

description: updated
slumbergod (slumbergod)
Changed in linux (Ubuntu):
status: Incomplete → Invalid
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.