[Dell Inc. Studio 1535] hibernate/resume failure [non-free: wl]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
PC RYcycle came up with an error:
gdu-notificatio
A hard disk is failing
One or more hard disks report health
problems. Click the icon to get more
information. Cancel OK
Palimpsest Disk Utility
Assessment: Passed The disk has bad sectors
System, Administration, Log file viewer
Can't find any logs anywhere that say there are HD problems.
ProblemType: KernelOops
Annotation: This occured during a previous hibernate and prevented it from resuming properly.
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf6dfc000 irq 21'
Mixer name : 'Silicon Image SiI1392 HDMI'
Components : 'HDA:111d7675,
Controls : 28
Simple ctrls : 16
Date: Sat Sep 19 01:49:26 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/
Failure: hibernate/resume
HibernationDevice: RESUME=
InterpreterPath: /usr/bin/python2.6
MachineType: Dell Inc. Studio 1535
NonfreeKernelMo
Package: linux-image-
ProcCmdLine: root=UUID=
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron: PATH=(custom, no user)
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.19
SourcePackage: linux
Tags: resume hibernate
Title: [Dell Inc. Studio 1535] hibernate/resume failure [non-free: wl]
Uname: Linux 2.6.31-10-generic i686
UserGroups:
WpaSupplicantLog:
dmi.bios.date: 07/30/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0M263C
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Studio 1535
dmi.sys.vendor: Dell Inc.
Hi Dale,
Can you comment how often this issue occurs? Is it every hibernate/resume, or more infrequently?