USB audio broken after hibernate

Bug #122202 reported by David Huggins-Daines
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Low
Ubuntu Audio Team

Bug Description

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

After upgrading to Feisty, my USB audio device no longer works after hibernation and resume. The volume control applet shows it as being "muted", but it is not possible to un-mute it.

The device in question is a set of Harman-Kardon SoundSticks:

Bus 001 Device 006: ID 05fc:7849 Harman Multimedia

If I unplug the device and plug it back in, it still fails to work. Removing the sound modules from the kernel and reloading them results in an oops.

Please let me know if I can provide any other information regarding this problem.

Revision history for this message
David Huggins-Daines (dhuggins) wrote :

Oh. Also, this is on AMD64. The USB controller is:

00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
        Subsystem: Elitegroup Computer Systems Unknown device 0022
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 64, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 21
        Region 4: I/O ports at d400 [size=32]
        Capabilities: [80] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Revision history for this message
Daniel T Chen (crimsun) wrote :

Does snd-usb-audio appear in the MODULES="" portion of /etc/default/acpi-support?

Changed in linux-source-2.6.20:
importance: Undecided → Low
status: New → Incomplete
assignee: nobody → ubuntu-audio
Revision history for this message
David Huggins-Daines (dhuggins) wrote :

Hmm, I tried to send this via e-mail and it didn't show up here. No, it's not in the MODULES="" section. Unfortunately, though, if I add it there, the problem doesn't go away.

Revision history for this message
David Huggins-Daines (dhuggins) wrote :

Hi, is there any more information that I can provide? Bug is still there. I will try the daily ISOs.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

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.

Revision history for this message
Michele Mangili (mangilimic) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.