[ASUSTeK COMPUTER INC. U38DT] suspend/resume failure [non-free: wl]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
Freeze while trying to sleep. Black screen and some words. The last one: cannot add device
ProblemType: KernelOops
DistroRelease: Ubuntu 15.04
Package: linux-image-
ProcVersionSign
Uname: Linux 3.18.0-12-generic x86_64
NonfreeKernelMo
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.15.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
Date: Wed Feb 4 23:11:31 2015
DuplicateSignature: suspend/
ExecutablePath: /usr/share/
Failure: suspend/resume
HibernationDevice: RESUME=
InstallationDate: Installed on 2013-10-18 (474 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
InterpreterPath: /usr/bin/python3.4
MachineType: ASUSTeK COMPUTER INC. U38DT
ProcCmdline: /usr/bin/python3 /usr/share/
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcFB:
0 radeondrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageV
linux-
linux-
linux-firmware 1.141
SourcePackage: linux
Title: [ASUSTeK COMPUTER INC. U38DT] suspend/resume failure [non-free: wl]
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: U38DT.209
dmi.board.
dmi.board.name: U38DT
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: U38DT
dmi.product.
dmi.sys.vendor: ASUSTeK COMPUTER INC.
tags: | removed: need-duplicate-check |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.