ICE1712 sound does not work after S3/S4-resume

[Alexander Jones]

Binary package hint: linux-image-2.6.20-11-generic

After an S3 or S4-resume, sound does not work with snd-ice1712. It causes any application attempting to use sound to seem to block, yet remain responsive until you attempt to do anything like pausing/seeking, at which point they hang. Reloading the driver repairs the situation, though all sound apps need to be killed first in order to unload (volume applet, browsers, etc.).

Known affected hardware:
 • M-Audio Audiophile 2496

Workaround:
 1. Kill all processes using the sound device (e.g. with "fuser -k /dev/snd/*")
 2. Unload the snd-ice1712 module (e.g. "rmmod snd-ice1712")
 3. Then reload it again (e.g. "modprobe snd-ice1712")
"Pop!" Sound is back.

This does not seem to affect my Creative SoundBlaster Live 5.1 Digital (emu10k1) hardware.

ProblemType: Bug
Architecture: i386
Date: Sun Mar 18 02:24:03 2007
DistroRelease: Ubuntu 7.04
Uname: Linux flash 2.6.20-11-generic #2 SMP Thu Mar 15 08:03:07 UTC 2007 i686 GNU/Linux

[nine (niin-deactivatedaccount-deactivatedaccount)]

It unfortunately appears that this bug is not yet resolved. Would it be possible to check whether this issue still exist in the Hardy Heron 8.04 LTS release?

If so, the Intrepid Ibex 8.10 Alpha2 is also scheduled for release today. It will appear at the following when available: http://www.ubuntu.com/testing/intrepid/alpha2 . It contains the actively developed 2.6.26 Ubuntu kernel. It would be great if you could test this upcoming release via a LiveCD and verify if the issue still exists. If so, please include the appropriate debugging information as outlined at https://wiki.ubuntu.com/DebuggingSoundProblems . Thanks in advance.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Tim Butler (timbutler)]

I can confirm that this is still occurring for Intrepid as I have encountered the same problem. The card I'm using is an M-Audio Delta 66 and the above steps correct the problem. I'm currently using the 2.6.27-7-generic kernel.

[Leann Ogasawara (leannogasawara)]

The 18 month support period for Feisty Fawn 7.04 has reached it's end of life - http://www.ubuntu.com/news/ubuntu-7.04-end-of-life . As a result we are closing the linux-source-2.6.20 task. However, this will remain open against the actively developed kernel. Thanks.

[Leann Ogasawara (leannogasawara)]

@Tim Butler, per the kernel team's bug policy, can you please attach the following information. Please be sure to attach each file as a separate attachment.

* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

Additionally, it would be best to wait to capture the dmesg output until after you do a suspend/resume cycle and apply the workaround. For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

[Jisakiel (jisakiel)]

I just want to say I have the same problem, although on Debian's 2.6.29 and a DMX6Fire (same module, different card), so I'm guessing the problem might be pulseaudio or upstream related.

If I open envy24control (the mixer for ice1712 cards) I can see the monitor for several channels stuck as if they had sound, although I have my front speakers setup to hear "digital mix" (so if there was noise I'd hear it) and they remain mute.

If wanted, which I'm not sure of as I'm not in ubuntu, I can provide given logs as soon as possible, as well as do some regression testing with debian's 2.6.29 to 2.6.26 and even ubuntu's kernels (but on a debian mixed testing / unstable userland). Just tell me if that would be ok, or wasting time (for both mantainers and me).

[Alexander Jones (alex-weej)]

This is nothing to do with PulseAudio, as I originally reported the bug many
years ago!

[Jisakiel (jisakiel)]

I doubt it will help posting my logs, as I'm in debian testing with 2.6.29-1-amd64 kernel, so I doubt ubuntu kernel team will accept this bug, and right now I don't have the time nor the free space to install native ubuntu to try on its kernel (although I will around august).

I've also tried installing native alsa drivers -to report directly to them-, but unfortunately neither alsa-source nor alsa-drivers official tar gz compile because of some problems on my build environment (which I made with "m-a prepare").

Nonetheless, here they go. A lot of fglrx crap because of my gfx card (tainted kernel, another red flag) in dmesg and even a panic (I'll try to get a clean suspend-resume with no X), but it works nonetheless. I believe the relevant lines to be:

$ grep ICE /var/log/kern.log
May 13 18:56:58 blackie kernel: [ 12.163038] ICE1712 0000:03:06.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
May 13 23:06:49 blackie kernel: [ 12.267027] ICE1712 0000:03:06.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
May 13 23:38:43 blackie kernel: [ 12.595079] ICE1712 0000:03:06.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
May 14 16:00:43 blackie kernel: [ 12.799021] ICE1712 0000:03:06.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
May 14 22:12:55 blackie kernel: [22349.282929] ICE1712 0000:03:06.0: PCI INT A disabled
May 14 22:12:59 blackie kernel: [22353.292774] ICE1712 0000:03:06.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
May 15 11:42:22 blackie kernel: [ 13.771020] ICE1712 0000:03:06.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
May 15 13:28:45 blackie kernel: [ 12.711263] ICE1712 0000:03:06.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
May 15 13:33:40 blackie kernel: [ 12.874986] ICE1712 0000:03:06.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
May 16 13:57:22 blackie kernel: [35616.284299] ICE1712 0000:03:06.0: PCI INT A disabled
May 16 13:57:22 blackie kernel: [35618.102356] ICE1712 0000:03:06.0: restoring config space at offset 0xf (was 0x1ff, writing 0x10a)
May 16 13:57:22 blackie kernel: [35618.102356] ICE1712 0000:03:06.0: restoring config space at offset 0x7 (was 0x1, writing 0xd801)
May 16 13:57:22 blackie kernel: [35618.102356] ICE1712 0000:03:06.0: restoring config space at offset 0x6 (was 0x1, writing 0xe001)
May 16 13:57:22 blackie kernel: [35618.102356] ICE1712 0000:03:06.0: restoring config space at offset 0x5 (was 0x1, writing 0xe401)
May 16 13:57:22 blackie kernel: [35618.102356] ICE1712 0000:03:06.0: restoring config space at offset 0x4 (was 0x1, writing 0xe801)
May 16 13:57:22 blackie kernel: [35618.102356] ICE1712 0000:03:06.0: restoring config space at offset 0x3 (was 0x0, writing 0x4000)
May 16 13:57:22 blackie kernel: [35618.102356] ICE1712 0000:03:06.0: restoring config space at offset 0x1 (was 0x2100000, writing 0x2100101)
May 16 13:57:22 blackie kernel: [35619.394819] ICE1712 0000:03:06.0: PME# disabled
May 16 13:57:22 blackie kernel: [35619.394822] ICE1712 0000:03:06.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
May 16 14:01:23 blackie kernel: [35863.421351] ICE1712 0000:03:06.0: PCI INT A disabled
May 16 14:01:28 blackie kernel: [35868.027157] ICE1712 0000:03:06.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21

[Jisakiel (jisakiel)]

dmesg just in case

[Peter Nelson (peter+launchpad)]

I also have this on Debian Lenny, however...

http://mailman.alsa-project.org/pipermail/alsa-devel/2009-February/014840.html

"The driver doesn't support PM (yet).
So, it's no bug but a feature :)"

[Alexander Jones (alex-weej)]

With pulseaudio managing audio hardware, I think we can just safely unload
and reload the module on either side of an S3. The hardware will vanish and
re-appear but because PA is in between applications and the sound devices it
should be ok.

2009/8/18 Peter Nelson <<email address hidden><peter%<email address hidden>>
>

> I also have this on Debian Lenny, however...
>
> http://mailman.alsa-project.org/pipermail/alsa-
> devel/2009-February/014840.html
>
> "The driver doesn't support PM (yet).
> So, it's no bug but a feature :)"
>
> --
> ICE1712 sound does not work after S3/S4-resume
> https://bugs.launchpad.net/bugs/93273
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

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

[Peter Nelson (peter+launchpad)]

For For what it's worth, the ice1712 driver still doesn't support suspend/resume.

The answer given previously about PulseAudio managing hardware; well actually, no,
PulseAudio doesn't work properly with ice1712 cards because PA expects 2-channel stereo
devices to exist.

PulseAudio also doesn't manage the MIDI ports on the card. If they're in-use,
then the module can't be unloaded either.

[HannesB (hannesb)]

Ubuntu 11.10
Suspend/resume still broken.

[Eduard Hasenleithner (eduard-hasenleithner)]

Ubuntu 12.04
Suspend/Resome apparently still broken.

[Alexander Jones (alex-weej)]

Ubuntu 14672785.04
Heat death of universe
Suspend/resume still broken

[Tim Passingham (tim-8aw3u04umo)]

Still broken for me on 12.04.