Suspend-to-disk (hibernation) fails on Samsung NP300E7A-A02 notebook
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
The Suspend-to-Disk (hibernation) feature fails on my Samsung NP300E7A-A02 notebook running Kubuntu 13.04 with Kernel version 3.8.0-22-generic.
Only my user account gets logged out when activating hibernation mode.
I've enabled hibernation as described in the manual under
http://
Ettore Atalan
---
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA:
country DE:
(2400 - 2483 @ 40), (N/A, 20)
(5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR
(5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS
(5470 - 5725 @ 40), (N/A, 26), DFS
DistroRelease: Ubuntu 13.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=
InstallationDate: Installed on 2012-05-05 (381 days ago)
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E4A/
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.106
Tags: raring
Uname: Linux 3.8.0-22-generic x86_64
UpgradeStatus: Upgraded to raring on 2013-04-28 (23 days ago)
UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare sudo
WifiSyslog:
dmi.bios.date: 11/11/2011
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 02QA
dmi.board.
dmi.board.name: 300E4A/
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: 300E4A/
dmi.product.
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1182977
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.