[ASUSTeK Computer Inc. M70TL] hibernate/resume failure [non-free: slamr fglrx]

[Bernhard]

Hibernation always works fine with Windows...

Description: Ubuntu 9.10
Release: 9.10

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: SB [HDA ATI SB], device 0: ALC663 Analog [ALC663 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: streit 3887 F.... pulseaudio
 /dev/snd/seq: timidity 3443 F.... timidity
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfdaf4000 irq 16'
   Mixer name : 'Realtek ALC663'
   Components : 'HDA:10ec0663,104311c3,00100001 HDA:11c11040,10431636,00100200'
   Controls : 17
   Simple ctrls : 9
Card1.Amixer.info:
 Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfddec000 irq 19'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100000'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined
   Playback channels: Mono
   Mono: Playback [off]
Date: Sun Nov 1 17:17:47 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: hibernate/resume
HibernationDevice: RESUME=UUID=23f9e267-ab91-4ad4-a465-6dfe3367c54e
InterpreterPath: /usr/bin/python2.6
MachineType: ASUSTeK Computer Inc. M70TL
NonfreeKernelModules: slamr fglrx
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: root=UUID=c0096047-136b-49fa-8faa-ccf143b20f66 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Tags: resume hibernate
Title: [ASUSTeK Computer Inc. M70TL] hibernate/resume failure [non-free: slamr fglrx]
Uname: Linux 2.6.31-14-generic i686
UserGroups: mythtv
dmi.bios.date: 10/07/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 205
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M70TL
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr205:bd10/07/2008:svnASUSTeKComputerInc.:pnM70TL:pvr1.0:rvnPEGATRONCORPORATION:rnM70TL:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
dmi.product.name: M70TL
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[Jeremy Foshee (jeremyfoshee)]

Hi Bernhard,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 468977

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Bernhard (info-bstreit)]

Hi,
just installed Lucid, and now it hibernate works, except that it doesn't shutdown after hibernating, have to switch off the computer manually. And interestingly, Standby doesn't work any more, which it did in Karmic...

But since these two issues are different ones, I'll close this now.

Bernhard