From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754434Ab2HYNpL (ORCPT ); Sat, 25 Aug 2012 09:45:11 -0400 Received: from cantor2.suse.de ([195.135.220.15]:52927 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752025Ab2HYNpG (ORCPT ); Sat, 25 Aug 2012 09:45:06 -0400 Date: Sat, 25 Aug 2012 15:45:05 +0200 Message-ID: From: Takashi Iwai To: Josh Boyer Cc: Daniel Mack , Bruno Wolff III , Jaroslav Kysela , alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org Subject: Re: Logitech USB headset not working in 3.6-rc3 In-Reply-To: <20120825121758.GF20043@zod.bos.redhat.com> References: <20120824190808.GC20043@zod.bos.redhat.com> <5038007E.5060505@gmail.com> <20120825111749.GA17048@wolff.to> <20120825115423.GA14327@wolff.to> <5038BEEB.6090303@gmail.com> <20120825120740.GA19539@wolff.to> <5038C186.7000107@gmail.com> <20120825121758.GF20043@zod.bos.redhat.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/24.1 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org At Sat, 25 Aug 2012 08:17:58 -0400, Josh Boyer wrote: > > On Sat, Aug 25, 2012 at 02:13:58PM +0200, Daniel Mack wrote: > > On 25.08.2012 14:07, Bruno Wolff III wrote: > > > On Sat, Aug 25, 2012 at 14:02:51 +0200, > > > Daniel Mack wrote: > > >> > > >> Can you revert commit e9ba389c5 ("ALSA: usb-audio: Fix > > >> scheduling-while-atomic bug in PCM capture stream") and see if that > > > > > > I can try that, but it takes a long time to build a new kernel on my > > > old hardware. > > > > > >> helps? If not, can you summarize again which kernels still work for you > > >> and which don't? > > > > > > The latest kernel that works is 3.6.0-0.rc2.git1.2.fc18. The earliest that > > > doesn't work is 3.6.0-0.rc2.git2.1.fc18. > > > > > > > The report you sent doesn't look like it could be caused by e9ba389c5. > > It fixes a kernel Ooops. But as it is the only relevant patch in that > > area, it would be interesting if reverting it fixes anything. > > Yep, agreed. If this revert kernel doesn't work, we're likely down to a > git bisect, Bruno. Yes, please. I'm currently traveling for KS and Plumbers, so I cannot debug it deeply, unfortunately. If the culprit were really my patch, I still don't figure out why it breaks. In that case, it must be really a subtle timing issue... thanks, Takashi