From: Daniel Mack <zonque@gmail.com>
To: Josh Boyer <jwboyer@redhat.com>
Cc: Takashi Iwai <tiwai@suse.de>,
bruno@wolff.to, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org
Subject: Re: Logitech USB headset not working in 3.6-rc3
Date: Sat, 25 Aug 2012 00:30:22 +0200 [thread overview]
Message-ID: <5038007E.5060505@gmail.com> (raw)
In-Reply-To: <20120824190808.GC20043@zod.bos.redhat.com>
Hi,
On 24.08.2012 21:08, Josh Boyer wrote:
> We've had a report[1] that the Logitech USB headset 0003:046D:0A0C isn't
> working with 3.6-rc3. It seems the last working kernel was based on
> commit 10c63c9, and it first stopped working with a kernel based on
> commit 23dcfa6. There are only a few ALSA commits between those
> revisions, so hopefully this is something that is fairly easy to
> identify. The only commit to USB audio in that set is:
[...]
> !!ALSA/HDA dmesg
> !!------------------
>
> [ 38.190306] SELinux: initialized (dev configfs, type configfs), uses genfs_contexts
> [ 38.229616] snd_hda_intel 0000:00:1b.0: irq 66 for MSI/MSI-X
> [ 38.270699] ALSA sound/usb/mixer.c:866 6:0: cannot get min/max values for control 2 (id 6)
> [ 38.274097] ALSA sound/usb/mixer.c:866 1:0: cannot get min/max values for control 2 (id 1)
> [ 38.276753] ALSA sound/usb/mixer.c:866 2:0: cannot get min/max values for control 2 (id 2)
> [ 38.279322] ALSA sound/pci/hda/hda_auto_parser.c:322 autoconfig: line_outs=1 (0xe/0x0/0x0/0x0/0x0) type:line
> [ 38.279326] ALSA sound/pci/hda/hda_auto_parser.c:326 speaker_outs=1 (0x11/0x0/0x0/0x0/0x0)
> [ 38.279329] ALSA sound/pci/hda/hda_auto_parser.c:330 hp_outs=1 (0xd/0x0/0x0/0x0/0x0)
> [ 38.279331] ALSA sound/pci/hda/hda_auto_parser.c:331 mono: mono_out=0x0
> [ 38.279333] ALSA sound/pci/hda/hda_auto_parser.c:335 inputs:
> [ 38.279336] ALSA sound/pci/hda/hda_auto_parser.c:339 Mic=0x10
> [ 38.279342] ALSA sound/pci/hda/hda_auto_parser.c:339 Line=0xf
> [ 38.285983] usbcore: registered new interface driver snd-usb-audio
Also, according to this dmesg, the device is probed just fine (which the
commit you mentioned wouldn't change anything about though).
So what does "isn't working anymore" refer to precisely? Are there any
more dmesg entries generated once the stream is started?
Daniel
next prev parent reply other threads:[~2012-08-24 22:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 19:08 Logitech USB headset not working in 3.6-rc3 Josh Boyer
2012-08-24 21:30 ` Daniel Mack
2012-08-24 22:30 ` Josh Boyer
2012-08-24 22:30 ` Daniel Mack [this message]
2012-08-25 11:17 ` Bruno Wolff III
2012-08-25 11:54 ` Bruno Wolff III
2012-08-25 12:02 ` Daniel Mack
2012-08-25 12:07 ` Bruno Wolff III
2012-08-25 12:13 ` Josh Boyer
2012-08-25 12:16 ` Bruno Wolff III
2012-08-26 12:46 ` Kernel module build workflow (Re: Logitech USB headset not working in 3.6-rc3) Takashi Iwai
2012-08-27 17:22 ` Felix Homann
2012-08-27 18:46 ` Takashi Iwai
2012-08-25 15:00 ` Logitech USB headset not working in 3.6-rc3 Bruno Wolff III
2012-08-25 12:13 ` Daniel Mack
2012-08-25 12:17 ` Josh Boyer
2012-08-25 13:45 ` Takashi Iwai
2012-08-29 11:26 ` Daniel Mack
2012-08-29 13:29 ` Takashi Iwai
2012-08-29 13:32 ` Daniel Mack
2012-08-29 14:14 ` Takashi Iwai
2012-08-29 14:25 ` Daniel Mack
2012-08-29 15:01 ` Takashi Iwai
2012-08-29 17:07 ` Josh Boyer
2012-08-29 17:22 ` Josh Boyer
2012-08-29 18:50 ` Bruno Wolff III
2012-08-30 14:10 ` Takashi Iwai
2012-08-30 15:03 ` Bruno Wolff III
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5038007E.5060505@gmail.com \
--to=zonque@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=bruno@wolff.to \
--cc=jwboyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).