no sound // 3:3:1: cannot set freq 16000 to ep 0x86

Bug #459445 reported by Daniel on 2009-10-23
302
This bug affects 67 people
Affects Status Importance Assigned to Milestone
linux (Fedora)
Won't Fix
High
linux (Ubuntu)
Undecided
Unassigned
Nominated for Lucid by Marko Martinović

Bug Description

Binary package hint: pulseaudio

Some time (not always) my system does not have sound until I reboot.

The only thing I have seen are this syslog/dmesg messages every second, even when there is no sound to playback.
[ 5225.020139] 3:3:1: cannot set freq 16000 to ep 0x86
[ 5226.020131] 3:3:1: cannot set freq 16000 to ep 0x86
[ 5227.020124] 3:3:1: cannot set freq 16000 to ep 0x86
[ 5228.020493] 3:3:1: cannot set freq 16000 to ep 0x86
[ 5229.020109] 3:3:1: cannot set freq 16000 to ep 0x86

Symptoms are:
- no mixer icon in tray bar
- audio players like rhythmbox look as they would play but they dont
- system->preferences->sound only shows message "Waiting for sound system to respond"

ProblemType: Bug
Architecture: i386
Card0.Amixer.info:
 Card hw:0 'Audigy2'/'SB Audigy 2 Platinum [SB0240P] (rev.4, serial:0x10021102) at 0xa000, irq 18'
   Mixer name : 'SigmaTel STAC9721,23'
   Components : 'AC97a:83847609'
   Controls : 214
   Simple ctrls : 49
Card1.Amixer.info:
 Card hw:1 'Intel'/'HDA Intel at 0xe8000000 irq 16'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,1458e601,00100001'
   Controls : 40
   Simple ctrls : 22
Card2.Amixer.info:
 Card hw:2 'U0x46d0x9a4'/'USB Device 0x46d:0x9a4 at usb-0000:00:1d.7-6, high speed'
   Mixer name : 'USB Mixer'
   Components : 'USB046d:09a4'
   Controls : 2
   Simple ctrls : 1
Card2.Amixer.values:
 Simple mixer control 'Mic',0
   Capabilities: cvolume cvolume-joined cswitch cswitch-joined
   Capture channels: Mono
   Limits: Capture 0 - 14
   Mono: Capture 7 [50%] [29.00dB] [on]
Card3.Amixer.info:
 Card hw:3 'HDMI'/'HDA ATI HDMI at 0xe1010000 irq 17'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100000'
   Controls : 4
   Simple ctrls : 1
Card3.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined
   Playback channels: Mono
   Mono: Playback [off]
Card4.Amixer.info:
 Card hw:4 'CX8811'/'Conexant CX8811 at 0xe5000000'
   Mixer name : 'CX88'
   Components : ''
   Controls : 3
   Simple ctrls : 2
Card5.Amixer.info:
 Card hw:5 'SAA7134'/'saa7134[0] at 0xe7005000 irq 19'
   Mixer name : 'SAA7134 Mixer'
   Components : ''
   Controls : 6
   Simple ctrls : 3
Date: Sat Oct 24 00:24:00 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/pulseaudio
NonfreeKernelModules: fglrx
Package: pulseaudio 1:0.9.19-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: pulseaudio
Uname: Linux 2.6.31-14-generic i686

Daniel (hackie) wrote :
Daniel (hackie) wrote :

also get problems when running VLC:

VLC media player 1.0.2 Goldeneye
[0xb73007e0] main interface error: no interface module matched "globalhotkeys,none"
[0xb73007e0] main interface error: no suitable interface module
[0x8df0250] main libvlc error: interface "globalhotkeys,none" initialization failed
[0x8df0250] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
QPainter::begin: Paint device returned engine == 0, type: 1
QPainter::begin: Paint device returned engine == 0, type: 1
[0xb7321f20] pulse audio output: No. of Audio Channels: 2
   (then it sleep ~ 30s, showing first frame of movie)
[0xb7321f20] pulse audio output error: Failed to connect to server: Timeout
[0xb7321f20] pulse audio output error: Pulse initialization failed
   (movie continues, but no sound (as the whole system..))

Also the system sometimes freezes, also ~ 30s. Mainly in combination with Alt-Tab, Gnome-panels or Firefox. (might be relevant...)

Daniel (hackie) wrote :

Problem solved (for me):

It was my QuickCam. Immediately after unplugging i was able to start Rhythmbox and hear sound.

The question remains:
Why does pulseaudio completely block sound functions if a device which was not even used makes trouble.

[ 8815.020140] 3:3:1: cannot set freq 16000 to ep 0x86
[ 8816.020264] 3:3:1: cannot set freq 16000 to ep 0x86
[ 8817.020132] 3:3:1: cannot set freq 16000 to ep 0x86
[ 8817.044529] usb 1-6: USB disconnect, address 3
[ 8817.044628] 3:3:1: cannot set freq 16000 to ep 0x86
[ 8817.044658] 3:3:1: cannot set freq 16000 to ep 0x86
[ 8817.044691] 3:3:1: cannot set freq 16000 to ep 0x86
[ 8817.044759] 3:3:1: cannot set freq 16000 to ep 0x86
[ 8817.044802] 3:3:1: cannot set freq 16000 to ep 0x86
[ 8817.045343] 3:3:1: usb_set_interface failed
[ 8817.045389] 3:3:1: usb_set_interface failed
[ 8817.045494] 3:3:1: usb_set_interface failed
(last mesage 10x totally, then finished)

In Jaunty it worked like a charm

Btw; i wonder lsusb did not list it with the address 3:3:1...

Sheldon Hearn (sheldonh) wrote :

I didn't see any version info, so thought I would add mine, since this bug helped me work around the problem too.

DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: pulseaudio 1:0.9.19-0ubuntu4
PackageArchitecture: amd64

ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: pulseaudio
Uname: Linux 2.6.31-14-generic x86_64

 [ 8.976085] uvcvideo: Found UVC 1.00 device <unnamed> (046d:08c9)
 [ 8.994476] input: UVC Camera (046d:08c9) as /devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4:1.0/input/input5

Marco Ballesio (marco-ballesio) wrote :

Same issue for me (with audacity) but only after upgrading yesterday for the first time after Christmas. After rmmoding snd_usb_audio and snd_usb_lib audacity worked fine again and it was possible to use the (video facilities of) webcam again.

I guess either the lock occurs in pulseaudio or in the kernel modules.

Seems indeed related to the Logitech QuickCam. I own one and experience the same bug.

2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009 x86_64 GNU/Linux
Propreitary nvidia kernel module loaded.

The following error message block is repeated ad infinitum

Jan 19 16:40:49 robert-desktop pulseaudio[1745]: module-alsa-card.c: Failed to find a working profile.
Jan 19 16:40:49 robert-desktop kernel: [ 864.120048] 4:3:1: cannot set freq 16000 to ep 0x86
Jan 19 16:40:49 robert-desktop pulseaudio[1745]: module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="usb-046d_09a4_60C2D510-02" card_name="alsa_card.usb-046d_09a4_60C2D510-02" tsched=yes ignore_dB=no card_properties="module-udev-detect.discovered=1""): initialization failed.
Jan 19 16:40:50 robert-desktop kernel: [ 865.170170] 4:3:1: cannot set freq 16000 to ep 0x86
Jan 19 16:40:51 robert-desktop kernel: [ 866.170041] 4:3:1: cannot set freq 16000 to ep 0x86
Jan 19 16:40:52 robert-desktop kernel: [ 867.170163] 4:3:1: cannot set freq 16000 to ep 0x86
Jan 19 16:40:53 robert-desktop kernel: [ 868.170158] 4:3:1: cannot set freq 16000 to ep 0x86
Jan 19 16:40:54 robert-desktop kernel: [ 869.170783] 4:3:1: cannot set freq 16000 to ep 0x86
Jan 19 16:40:55 robert-desktop kernel: [ 870.170150] 4:3:1: cannot set freq 16000 to ep 0x86
Jan 19 16:40:56 robert-desktop kernel: [ 871.170146] 4:3:1: cannot set freq 16000 to ep 0x86
Jan 19 16:40:57 robert-desktop kernel: [ 872.170142] 4:3:1: cannot set freq 16000 to ep 0x86
Jan 19 16:40:58 robert-desktop kernel: [ 873.170136] 4:3:1: cannot set freq 16000 to ep 0x86
Jan 19 16:40:59 robert-desktop kernel: [ 874.170134] 4:3:1: cannot set freq 16000 to ep 0x86
Jan 19 16:41:00 robert-desktop kernel: [ 875.170131] 4:3:1: cannot set freq 16000 to ep 0x86
Jan 19 16:41:01 robert-desktop kernel: [ 876.170125] 4:3:1: cannot set freq 16000 to ep 0x86
Jan 19 16:41:02 robert-desktop kernel: [ 877.170373] 4:3:1: cannot set freq 16000 to ep 0x86
Jan 19 16:41:03 robert-desktop kernel: [ 878.170117] 4:3:1: cannot set freq 16000 to ep 0x86
Jan 19 16:41:04 robert-desktop kernel: [ 879.176235] 4:3:1: cannot set freq 16000 to ep 0x86
Jan 19 16:41:05 robert-desktop kernel: [ 880.180108] 4:3:1: cannot set freq 16000 to ep 0x86
Jan 19 16:41:06 robert-desktop kernel: [ 881.172817] 4:3:1: cannot set freq 16000 to ep 0x86
Jan 19 16:41:07 robert-desktop kernel: [ 882.170101] 4:3:1: cannot set freq 16000 to ep 0x86
Jan 19 16:41:08 robert-desktop kernel: [ 883.170097] 4:3:1: cannot set freq 16000 to ep 0x86

Plafuro (plafuro) wrote :

Also suffering this bug over here... it's rather annoying...

Daniel T Chen (crimsun) on 2010-03-06
affects: pulseaudio (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Confirmed

Suffering from this bug with my Logitech E3500 in Lucid. Please would someone be nice to take a look at this problem :) My Logs contain same thing as Robert Elsner's in comment #6.

Same over here ...

I have this problem since 9.04 I think ...

dmesg output:

----
[ 383.580019] usb 1-5: new high speed USB device using ehci_hcd and address 9
[ 383.848358] usb 1-5: configuration #1 chosen from 1 choice
[ 383.848567] uvcvideo: Found UVC 1.00 device <unnamed> (046d:09a4)
[ 383.879525] input: UVC Camera (046d:09a4) as /devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.0/input/input8
[ 384.890337] set volume quirk for QuickCam E3500
[ 385.630876] 9:3:1: cannot set freq 16000 to ep 0x86
[ 385.634503] 9:3:1: cannot set freq 16000 to ep 0x86
----

unplugging and replugging sometimes helps.

Kris969 (cby469-free) wrote :

Also affected by this bug, I also have a logitec Quickcam connected to the system.
It appears when I switch from one user session to another, sometimes the system seems to be freeze, but when I switch t the console (Alt+F1) I witness it's steel working, and the message "Cannot set from 16000..." is printed every second
To conclude I will say that if the user know what to do, cause he is friendly with Ubuntu console commands it can go ahead. In other case, if the user is just a poor user, the system for him is freeze and he get a poor image about Ubuntu stability... To continue to raise up the Ubuntu image I propose to set the gravity of this bug to a importance criteria different than "Undecided"

I am back with my logs when this bug crashes party uninvited:

Jun 18 00:33:20 Marko-PC pulseaudio[1599]: module-alsa-card.c: Failed to find a working profile.
Jun 18 00:33:20 Marko-PC pulseaudio[1599]: module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="usb-046d_09a4_5D256620-02-U0x46d0x9a4" card_name="alsa_card.usb-046d_09a4_5D256620-02-U0x46d0x9a4" tsched=yes ignore_dB=no card_properties="module-udev-detect.discovered=1""): initialization failed.
Jun 18 00:33:21 Marko-PC kernel: [ 200.476158] 6:3:1: cannot set freq 16000 to ep 0x86
Jun 18 00:33:22 Marko-PC kernel: [ 201.476078] 6:3:1: cannot set freq 16000 to ep 0x86
Jun 18 00:33:23 Marko-PC kernel: [ 202.476128] 6:3:1: cannot set freq 16000 to ep 0x86
Jun 18 00:33:24 Marko-PC kernel: [ 203.476052] 6:3:1: cannot set freq 16000 to ep 0x86
Jun 18 00:33:25 Marko-PC kernel: [ 204.476101] 6:3:1: cannot set freq 16000 to ep 0x86
Jun 18 00:33:26 Marko-PC kernel: [ 205.476148] 6:3:1: cannot set freq 16000 to ep 0x86
Jun 18 00:33:27 Marko-PC kernel: [ 206.476073] 6:3:1: cannot set freq 16000 to ep 0x86

Please, please fix this.

Rolf Sander (mail-rolf-sander) wrote :

I have similar symptoms as Kris969. I also think it would be good to
assign a somewhat higher priority to this bug because of this freeze.

Here are my symptoms:

- The system seems to freeze, although "top" from the command line still
  works and shows just a few % CPU usage.

- The Workspace Switcher needs 10 to 20 seconds to switch between
  workspaces.

Here is some more technical info about my system:

lsusb:
  ...
  Bus 001 Device 002: ID 046d:09a4 Logitech, Inc. QuickCam E 3500
  ...

lsb_release -rs:
  10.04

I have found a sort of workaround for this bug. It needs more testing but please try and comment here or on by web log.
Here's the link to the post with workaround, hope it helps:
http://www.techytalk.co.cc/2010/07/logitech-e3500-webcam-and-cannot-set-freq-16000-to-ep-0x86/

Lew Palm (lew) wrote :

Hi,

I can confirm the same bug. My logitech cam with integrated microphone (046d:09a5) seems to provoke it in combination with pulseaudio. I am using a 64-bit 10.04 Ubuntu with the newest updates.
It is an intermittent failure, it does not occur after every boot.
The annoying message "cannot set freq 16000 to ep 0x86" is repeated every second or so.
Pulseaudio seems to hang - I can not kill it via "killall pulseaudio" but "killall -9 pulseaudio" stops the message.
The gnome loudness applet does not work, too. But sounds still works! I can use for example skype.

Pulseaudio produces the bug message - it vanishes after killing "-9" pulseaudio.
The bug could crawl there.

greetings,
  Lew

I have the same problem. The last kernel update has improved the problem. But I still get a lock about every 1 in 7 times. I've found a purported workaround at this site: http://www.techytalk.co.cc/2010/07/logitech-e3500-wXTlSgCebcam-and-cannot-set-freq-16000-to-ep-0x86/. But i haven't tested yet.

Cengiz Can (cengizcan) wrote :

I have the same problem.

Using Logitech QuickCam with Ubuntu 10.10 x86 on a

Intel Tylersburg X58 / Intel 82801JR ICH10R / QuadCore Intel Core i7 920.

The error message is written repeatedly on screen and even on the Alt+F1 alternate shell prompt.

I didn't notice sound problems but I can't click with my mouse (USB generic mouse). Mouse moves fine but it does not send any click messages to gnome.

Guys i wrote comment #14. I made bash script as a workaround for this problem and posted link to my workaround. Link in comment #16 is not valid so I will put valid link again: http://www.techytalk.co.cc/2010/07/logitech-e3500-webcam-and-cannot-set-freq-16000-to-ep-0x86/

My script starts at the end of boot process and checks last 30 lines of /var/log/kern.log. If it founds more than 3 occurrences of “cannot set freq 16000 to ep 0×86″ it removes kernel module snd-usb-audio form kernel and plugs it back again. Script can be modified for your error that pops up in kern.log and you can put your solution if removing snd-usb-audio doesn't work.

This problem should really get some attention. We don't need new theme every Ubuntu release or new set of icons. We need our hardware to work.

ingo (ingo-steiner) wrote :

My guess is that all these troubles are related to the kernel module snd-usb-audio.

Got the same Webcam here E3500 with built in microphone. With snd-usb-audio loaded I am unable to suspend/resume (kernel-suspend) in Lucid-amd64.

Module snd-usb-audio has no suspend/resume script!

My solution is to blacklist the module (micro) in /etc/modprobe.d/blacklist-xyz.conf and rebuild initramfs. Now suspend and resume works smoothly.

Yes. My dirty script rmmod-s and modprobe-s snd-usb-audio module when it detects troubles and then things work again, until system restart. Without snd-usb-audio users webcam mic is not working. In fact any usb audio device won't work if you blacklist snd-usb-audio. That is like healing sick patient by killing him ;) But if someone has a lot of problems with usb device blacklisting faulty module is an option.

On 19.10.2010 18:58, Marko Martinović wrote:
> That is like healing sick patient by killing him ;)

Sometimes that's the way Ubuntu's bugs are "fixed":
If for some reason console is not available, direct output to /dev/null

+++ This bug was initially created as a clone of Bug #583168 +++

Original bug was closed due to EOL. Bug is still present in FC14. Sometimes when system starts up the system is very slow. Taking a look at the /var/log/messages file shows a large number of entries of the form:

Dec 16 10:31:57 kernel: [ 2711.698066] ALSA sound/usb/clock.c:233: 3:3:3: cannot set freq 16000 to ep 0x86

And a bit less but also frequently:

Dec 16 10:38:13 pulseaudio[2043]: module-alsa-card.c: Failed to find a working profile.
Dec 16 10:38:13 pulseaudio[2043]: module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="usb-046d_08c9_56B751A2-02-U0x46d0x8c9" card_name="alsa_card.usb-046d_08c9_56B751A2-02-U0x46d0x8c9" tsched=yes ignore_dB=no card_properties="module-udev-detect.discovered=1""): initialization failed.

Login in is also very slow since it is unable to play the required sounds when selecting a username to use for login; this is the first indicator of this bug when using the system.

What kind of USB sound device?

Two USB sound devices:

- Logitech USB Headset / A-0356A (with mic)
- Logitech QuickCam (with mic)

$ lsusb
...
Bus 001 Device 005: ID 046d:0a01 Logitech, Inc. USB Headset
Bus 001 Device 003: ID 046d:08c9 Logitech, Inc. QuickCam Ultra Vision
...

I have problem with mic on Logitech 9000 (on 2 PC).
To avoid it, I have disabled snd-usb-audio.ko module.

This problem appears to be widespread and is triggered somehow by pulseaudio. One workaround is to remove the snd-usb-audio module, wait a few seconds, and then load it again.

julesb (j-blundell) wrote :

Got the same problem.
Occasionally start getting

cannot set freq 16000 to ep 0x86

about once a second, the whole system goes very slow and I have to power down the computer to escape.

I too have a logitec camera with an internal mic.

Ubuntu 10.10 Maveric

Same here, changing user seems to trigger this bug.
Instead of blacklisting or removing (not possible in my system due to dependencies) snd-usb-audio, i restart usbhid using
modprobe -r usbhid &&
sleep 7 &&
modprobe usbhid
or i simply unplug and replug offending logitech hardware

Bus 001 Device 002: ID 046d:0802 Logitech, Inc.
2.6.38-4-generic #31~lucid1-Ubuntu SMP Thu Feb 17 12:34:53 UTC 2011 x86_64 GNU/Linux

suddenly, i am meeting this bug. it has appeared at least 5 times today. the system is now stable.

these are my usb devices:
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 003: ID 046d:c05a Logitech, Inc. Optical Mouse M90
Bus 003 Device 002: ID 046d:c31c Logitech, Inc.
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 07d1:3c03 D-Link System AirPlus G DWL-G122 Wireless Adapter(rev.C1) [Ralink RT73]
Bus 001 Device 004: ID 046d:0825 Logitech, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

and this is a sample from /var/log/messages:
kernel: [ 4497.987096] ALSA sound/usb/clock.c:233: 4:3:4: cannot set freq 48000 to ep 0x86

the only thing i think of other than auto yum updates everyday is that i updated/installed the latest version of skype on april 22

also, out of character is when i log in to a particular user on this system kde tells me that :
audio device playback HDA intel (ALC662 rev1 Analog) does not work

i am testing this:

the contents of /etc/modprobe.d/snd-usb-audio.conf :
alias snd-usb-audio off

I'm also affected with F15.
QuickCam E3500

moony (simon-brem) wrote :

Hi, I got the same problem, same messages in syslog. Immediatly after unplugging my QuickCam E 3500 out of my USB hub and connecting it to a free USB port, clementine (audio player) startet it's playback and "cannot set freq 16000 to ep 0x86" messages ended.
Must be related to the webcam and maybe to the USB hub.

I would like to emphasize that this problem is intermittent; however, I am noticing an increased frequency whenever I have 2 devices that have sound capabilities, in particular microphone sound devices. Similar to Joël Wijngaarde's (original bug reporter) report I am seeing in the syslog messages the following:

Jun 14 10:13:02 mobile-pc pulseaudio[2885]: module.c: Failed to load module "mo
dule-alsa-card" (argument: "device_id="0" name="usb-046d_0991_0E39ACE1-02-U0x46d
0x991" card_name="alsa_card.usb-046d_0991_0E39ACE1-02-U0x46d0x991" tsched=yes ig
nore_dB=no card_properties="module-udev-detect.discovered=1""): initialization f
ailed.
Jun 14 10:13:03 mobile-pc kernel: [ 1529.584231] ALSA sound/usb/clock.c:233: 2:3
:1: cannot set freq 16000 to ep 0x86
Jun 14 10:13:04 mobile-pc kernel: [ 1530.584149] ALSA sound/usb/clock.c:233: 2:3
:1: cannot set freq 16000 to ep 0x86
Jun 14 10:13:05 mobile-pc kernel: [ 1531.584183] ALSA sound/usb/clock.c:233: 2:3
:1: cannot set freq 16000 to ep 0x86

The "sound/usb/clock.c:233" report line repeats several times (> 15 times) and the overall system response time noticeably slows to a grind. The frequency of this intermittent bug occurence appears to be more often when I have more than one audio input device connected:

# lsusb
Bus 001 Device 002: ID 046d:0991 Logitech, Inc. QuickCam Pro for Notebooks

and my native mobo audio device (from "lshw")
pci@0000:00:1b.0 N10/ICH 7 Family High Definition Audio Controller [8086:27D8]

I am observing this bug on a "Lenovo Thinkpad T60p" using the following:

GNU/Linux Distribution: Fedora 14
Kernel: 2.6.35.13-92.fc14.i686.PAE #1 SMP

Confirming the bug. Reproducible every suspend/resume cycle.
My case is :
Logitech C310 webcam
#lsusb
Bus 002 Device 006: ID 046d:081b Logitech, Inc.
#tail -f /var/log/messages
kernel: [13358.103143] ALSA clock.c:218: 7:3:2: cannot set freq 24000 to ep 0x86
kernel: [13358.240523] ALSA clock.c:233: current rate 290 is different from the runtime rate 32000

Latest F14 stock kernel, pulseaudio from repo.
Mic works ok until first suspend, after which no recording is possible. Plug out/in fixes the problem.

Since i have to use custom 2.6.39-rc1+ kernel, i tried it with latest ALSA from git (needs to compile /usr/src/kernels/`uname -r`/linux/include/smp_lock.h, which has been removed, i took it from 13-92.fc14 src), and it triggers new behavior :

Upon coldboot:

1.Recording seemingly possible, but recording indicator is inactive (in pavucontrol it's seen only if "All Streams" is chosen but still inactive) or "stream empty" when trying to playback.
or
2.Recording, but probably with wrong frequency, so playback of recorded sound is pitchshifted and speeded up.

Plug-out/plug-in fixes the problem unreliably. Worst of all even if it does - only before first wakeup from suspend. Then disconnect-reconnect doesn't help anymore.

A dirty workaround prooved to be functional - modules, alsa and pulseaudio have to be stopped and restarted in particular order :

Create executable script 20snd in /usr/lib/pm-utils/sleep.d/
#cat /usr/lib/pm-utils/sleep.d/20snd

#!/bin/sh
#
#I'm logged in as root, so it may require adaptation.
. "${PM_FUNCTIONS}"

case "$1" in
 hibernate|suspend)
killall pulseaudio
/etc/init.d/alsasound stop
#skype hangs on resume if everything sound-related was restarted
killall skype
modprobe -r snd_usb_audio
;;
 thaw|resume)
#kmods u've to reload. my specific are xfi,via. determine your with lsmod.
modprobe -v snd_hda_codec_via
modprobe -v snd_hda_intel
modprobe -v snd_ctxfi
modprobe -v snd snd_hda_codec_via snd_hda_intel snd_hda_codec snd_hwdep ctxfi snd_seq snd_seq_device snd_pcm snd_timer
modprobe -v snd_usb_audio
sleep 1
# /etc/init.d/alsasound start #probably unnecessary
pulseaudio -D
export DISPLAY=:0
#substitute root with your username
su -c - root "gmixer -d" &disown
su -c - root "skype" & disown
;;
    *) exit $NA
  ;;
esac

This fixes it for me.

(In reply to comment #9)

> Since i have to use custom 2.6.39-rc1+ kernel, i tried it with latest ALSA from
> git, and it triggers new
> behavior :

Forgot to add :
I was unable to defeat this behavior, so i reverted to last stable alsa-driver.

> Upon coldboot:
>
> 1.Recording seemingly possible, but recording indicator is inactive (in
> pavucontrol it's seen only if "All Streams" is chosen but still inactive) or
> "stream empty" when trying to playback.
> or
> 2.Recording, but probably with wrong frequency, so playback of recorded sound
> is pitchshifted and speeded up.

Symptom 1 pertains to both both kernels after resume, symptom 2 only to 39-rc1+ with alsa from git.
With latest Fedora's kernel it's indeed enough to disconnect/reconnect the cam to make it work.

> A dirty workaround

Script is tested in this config :
kernel 2.6.35.13-92.fc14.i686 + alsa-driver 1.0.24
kerenel 2.6.39-rc1+ + alsa-driver 1.0.24

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.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
Igor Starikov (idlesign) wrote :

Experienced this after the upgrade to 11.10. The symptom is an absence of audio devices in sound manager.
Camera (QuickCam E 3500) unplug & plug helped.
Weird enough that was the first time since 10.04.

Stapel (wstapelberg) wrote :

I have also experienced this bug. I could see all the ¨cannot set freq 16000 to ep 0x86" when I do a dmesg in the terminal. Also my sound indicator was muted and I could not adjust the sound. I also have a Logitech webcam (not sure what model) and I am running a new install of 11.10 64-bit.

After I unplugged my webcam I could again adjust my sound and the system was back to normal.

Robert Hutton (rwh-helms-deep) wrote :

I have the same symptoms as Stapel reported. Ubuntu 11.10 64-bit updated with latest updates. After update and reboot, sound wouldn't work, sound icon displaying muted icon. Sound settings showed no hardware present. Unplugged the Logitech webcam and sound works again.

[ 3753.528186] 2:3:3: cannot set freq 16000 to ep 0x86
[ 3754.528185] 2:3:3: cannot set freq 16000 to ep 0x86
(repeating)

(unplugged webcam)

[ 3755.290207] usb 1-1: USB disconnect, device number 2
[ 3755.294055] 2:3:3: cannot set freq 16000 to ep 0x86
[ 3755.294413] 2:3:3: cannot set freq 16000 to ep 0x86
[ 3755.325177] 2:3:3: usb_set_interface failed
[ 3755.325189] 2:3:3: usb_set_interface failed
(repeating)

Ted Strong (tstrong) wrote :

I am experiencing this problem, but my sound DOES work ( im using onboard spdif output for sound ).

What does not work is using my Quickcam Fusion's Microphone as a sound input ( this worked in Ubuntu 11.04 ). Now in 11.10, when I try to use it I am getting no input, and these messages:

[ 3753.528186] 2:3:3: cannot set freq 16000 to ep 0x86
[ 3754.528185] 2:3:3: cannot set freq 16000 to ep 0x86
(repeating)

I had some problems booting with the webcam attached ( like corruption of my lirc usb device ), but managed to solve that by blacklisting the module uvcvideo.

Guillaume (tomekin2000) wrote :

I am experiencing the same problem after upgrading to 11.10.
I have a logitech webcam :

Bus 002 Device 006: ID 046d:08c3 Logitech, Inc. Camera (Notebooks Pro)

Sound is muted,
no sound device is reported in the sound menu,
banshee crashes
Firefox is much slower (video with sound playing in youtube)

I get two messages in kern.log :

   3:3:3: cannot set freq 16000 to ep 0x86
   3:3:3: usb_set_interface failed

The problem is appears randomly but quite often.

Alessandro Menti (elgaton) wrote :

The current bug report for Oneiric is at bug #884210 - feel free to comment there.

João Pinto (joaopinto) wrote :

I have sent a support request to Logitech regarding this bug.

Also seeing this on RHEL 6.1 2.6.32-131.6.1.el6.x86_64 with a Logitech, Inc. Webcam Pro 9000.

Bus 001 Device 102: ID 046d:0809 Logitech, Inc. Webcam Pro 9000

Nov 17 20:02:56 godzilla kernel: 87:3:4: cannot set freq 48000 to ep 0x86
Nov 17 20:02:57 godzilla kernel: 87:3:4: cannot set freq 48000 to ep 0x86
Nov 17 20:02:58 godzilla kernel: 87:3:4: cannot set freq 48000 to ep 0x86
Nov 17 20:02:59 godzilla kernel: 87:3:4: cannot set freq 48000 to ep 0x86
Nov 17 20:03:00 godzilla pulseaudio[6397]: alsa-source.c: Failed to set hardware parameters: Connection timed out

messages above were being logged until I unplugged the webcam.

Lito (lito-eordes) wrote :

Also fails in precise with logitech webcam:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu precise (development branch)
Release: 12.04
Codename: precise

$ uname -a
Linux lito-portatil 3.2.0-2-generic-pae #5-Ubuntu SMP Mon Nov 28 20:21:50 UTC 2011 i686 i686 i386 GNU/Linux

Gauss (gauss1989) wrote :

I also have the same problem with my Logitech QuickCam E3500

uname -a
Linux ivan-desktop 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

I can confirm this bug. But only with Logitec Quickcam enabled

Anton Gladky (gladky-anton) wrote :

Same problem here on Precise.

Jason Sharp (jsharp) wrote :

Also confirmed

Ubuntu 11.04 natty

Tim Kuijsten (kuijsten) wrote :

since this bug has status won't fix (although it's still present in the latest oneiric), a new report is filed at #567565

Tim Kuijsten (kuijsten) wrote :

#567565 is actually also a duplicate of bug #884210

This message is a notice that Fedora 14 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 14. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 14 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

This bug is still present in Fedora 18.

Confirming previous comment. This bug is still present on Fedora 18.

I run F18 and see the this bug frequently.

I use F18, with all updates applied, on a X86_64 kernel with Evga Geforce 7600 GS PCI-E 256mb DDR2 video card. Have a Logitech quickcam connected to a usb.

Still experiencing this on F19. Created bug #991234.

(In reply to Raman Gupta from comment #16)
> Still experiencing this on F19. Created bug #991234.

I agree the bug is still present on F19.

pi4630 (p-imbemba) wrote :

Confirmed on 12.04 LTS 64 bit (also with Logitech Quickcam 4500).

Kostis Leledakis (koleygr) wrote :

I have the same issue in 12.04 LTS 32-bit
(I have sound but when booting i get 4:3:1 cannot set freq16000 to ep 0x86 etc)

I just running the command:
apport-collect -p linux 459445

Kostis Leledakis (koleygr) wrote :

i will try with the :
apport-collect -p linux 884210
because previews command didn;t work

Just ran into this error with F20 - This error is present there too/still.

#lsusb
Bus 001 Device 003: ID 046d:08ce Logitech, Inc. QuickCam Pro 5000

Main error (repeated on any tty I approach, X is unresponsive (black screen)
kernel: ALSA sound/usb/clock.c:309 3:3:3: cannot get freq at ep 0x86

messages also shows:
ALSA sound/usb/mixer.c:1303 usb_audio: Warning! Unlikely big volume range (=3072), cval->res is probably wrong.
ALSA sound/usb/mixer.c:1307 usb_audio: [5] FU [Mic Capture Volume] ch = 1, val = 4608/7680/1<6>
usbcore: registered new interface driver snd-usb-audio
uvcvideo: Found UVC 1.00 device <unnamed> (046d:08ce)

It happend also to me on Fedora 20.

[ 8712.359253] ALSA sound/usb/clock.c:300 4:3:4: cannot set freq 48000 to ep 0x86
[ 8717.366675] ALSA sound/usb/clock.c:300 4:3:4: cannot set freq 48000 to ep 0x86
[ 8722.374131] ALSA sound/usb/clock.c:300 4:3:4: cannot set freq 48000 to ep 0x86
[ 8727.381577] ALSA sound/usb/clock.c:300 4:3:4: cannot set freq 48000 to ep 0x86
[ 8732.389020] ALSA sound/usb/clock.c:300 4:3:4: cannot set freq 48000 to ep 0x86
[ 8737.398441] ALSA sound/usb/clock.c:300 4:3:4: cannot set freq 48000 to ep 0x86

My Camera is Logitech C270
Bus 003 Device 004: ID 046d:0825 Logitech, Inc. Webcam C270

Can we have this bug opened back up please since it happens still, on Fedora 20?

floriankeim (floriankeim) wrote :

Same problem with Ubuntu Gnome 15.10 and a logitech webcam, makes booting and logon very slow. only solution is unplugging the cam.

Changed in linux (Fedora):
importance: Unknown → High
status: Unknown → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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