Suspend/resume failing with Audigy2 PCMCIA attached

[John Doe]

System hangs up completely after trying to wake up from suspend. Seems to be a problem with my Audigy 2 PCMCIA.

Kernel is 2.6.31-13-generic-pae

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nordlicht 1924 F.... pulseaudio
 /dev/snd/controlC1: nordlicht 1924 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'ICH6'/'Intel ICH6 with ALC650F at irq 17'
   Mixer name : 'Realtek ALC650F'
   Components : 'AC97a:414c4723'
   Controls : 50
   Simple ctrls : 33
Card1.Amixer.info:
 Card hw:1 'Audigy2'/'SB Audigy 2 ZS Notebook [SB0530] (rev.0, serial:0x20011102) at 0xd000, irq 17'
   Mixer name : ''
   Components : ''
   Controls : 182
   Simple ctrls : 26
Date: Sun Oct 11 22:45:28 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=514f5301-2cd7-4840-bf06-639fb9bbbc66
InterpreterPath: /usr/bin/python2.6
MachineType: ASUSTeK Computer INC. V6V
Package: linux-image-2.6.31-13-generic-pae 2.6.31-13.44
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   3.3V 32-bit PC Card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-13-generic-pae root=UUID=41522051-5d85-47e9-8896-9ed65b359a5d ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic-pae
RelatedPackageVersions: linux-firmware 1.21
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Tags: resume suspend
Title: [ASUSTeK Computer INC. V6V] suspend/resume failure
Uname: Linux 2.6.31-13-generic-pae i686
UserGroups:

dmi.bios.date: 10/12/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1201
dmi.board.name: V6V
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 2.00
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd10/12/2005:svnASUSTeKComputerINC.:pnV6V:pvr1.0:rvnASUSTeKComputerINC.:rnV6V:rvr2.00:cvnASUSTekComputerINC.:ct10:cvr1.0:
dmi.product.name: V6V
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer INC.

[John Doe (jodo-deactivatedaccount)]

Ok, now running the Final Karmic. I figured out that the problem only occours with my Soundblaster Audigy PCMCIA. Without it, suspend works.

But this is not a solution, only a hint. In 9.04 suspend worked WITH the Soundcard attached.

[John Doe (jodo-deactivatedaccount)]

Something like "Yes, we've noticed this report" would be nice. This Bug is really nasty.

[Adamansky Anton (adamansky)]

I've not found any workaround except to not use suspend/hibernate with attached audigy2, just power off/on :)

[John Doe (jodo-deactivatedaccount)]

;) This isn't a real solution. The bad thing is that this worked in 9.04 like a charm. The SBA is attached permanently on this System because of the bad Quality the AC97 offers.

Even with the Kernel-Updates that came after posting this report, the situation is the same.

[John Doe (jodo-deactivatedaccount)]

Also occours on Lucid Lynx.

[Chris Coulson (chrisccoulson)]

There's no evidence of this being a gnome-power-manager bug

[Jeremy Foshee (jeremyfoshee)]

reassigning to the linux task for investigation.

~JFo

[John Doe (jodo-deactivatedaccount)]

Thanks. I really hope this could be fixed. I know the hardware isn't the newest, but it still makes a good job for me.

[John Doe (jodo-deactivatedaccount)]

Ok, tested under Lucid with Standardkernel and Mainlinekernel 2.6.34-5, still the same behaviour. System goes to Suspend and sleeps forever then...

[John Doe (jodo-deactivatedaccount)]

Still the same on Maverick Alpha, with Kernel 2.6.35-5. I really don't want to bother anyone, but is someone still reading here?

[Bartosz Woronicz (mastier1)]

hey, at least, please sound team for some tips how to inspect the bug ? I can even look for a fix in source, but some help could be useful, duh ?

[John Doe (jodo-deactivatedaccount)]

Hey, it would be very great if this could get a bit attention. ;) I won't give up hope til now.

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[John Doe (jodo-deactivatedaccount)]

COuld someone file this against Oneiric? It's still not fixed, suspend/hibernate is still not possible.

[John Doe (jodo-deactivatedaccount)]

I found a solution.

Running "sudo rmmod -f snd_emu10k1" helps. But sadly, it does only work on my Arch-Install, not under Ubuntu because Ubuntus Kernel isn't compiled with the "Forced Module Removal"-Option.

Maybe this is the reason why blacklisting the module does not do the trick?