Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760698Ab0HLVRQ (ORCPT ); Thu, 12 Aug 2010 17:17:16 -0400 Received: from cantor2.suse.de ([195.135.220.15]:59046 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752441Ab0HLVRL (ORCPT ); Thu, 12 Aug 2010 17:17:11 -0400 Date: Thu, 12 Aug 2010 23:17:10 +0200 Message-ID: From: Takashi Iwai To: Jiri Slaby Cc: Pekka Enberg , Thomas Meyer , Linux Kernel Mailing List , Linus Torvalds Subject: Re: 2.6.36: Sound stop working In-Reply-To: <4C646110.1040104@gmail.com> References: <201008122200.05598.thomas@m3y3r.de> <4C646110.1040104@gmail.com> User-Agent: Wanderlust/2.15.6 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.7 Emacs/23.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 Content-Length: 1675 Lines: 45 At Thu, 12 Aug 2010 23:01:04 +0200, Jiri Slaby wrote: > > On 08/12/2010 10:26 PM, Takashi Iwai wrote: > > At Thu, 12 Aug 2010 23:10:15 +0300, > > Pekka Enberg wrote: > >> > >> On Thu, Aug 12, 2010 at 11:00 PM, Thomas Meyer wrote: > >>> My sound card stop to work since a few commits. I tried to bisect it and ended up with this: > >>> > >>> There are only 'skip'ped commits left to test. > >>> The first bad commit could be any of: > >>> 3bcf3860a4ff9bbc522820b4b765e65e4deceb3e > >>> c1e5c954020e123d30b4abf4038ce501861bcf9f > >>> We cannot bisect more! > >>> > >>> any ideas what to do now? > >> > >> Takashi, maybe this is related to Linus' problem? > > > > Yeah, I guess so, since I couldn't see any obvious problem in sound/*. > > > > PulseAudio uses inotify in udev-detection module, at least. > > It's possible that inotify change may hit the sound in the end. > > Probably I got into this problem yesterday. Found out that PA fails to > open /dev/snd/pcmC0D0p _second_ time. It opens it, then closes, then > opens it again and gets EBUSY. aplay is OK. Yes, I can also confirm that it's broken on my machine in the same way now :) PA log shows that the succeeding open failed. PA tries to do quick open/close of the same device to figure out which configuration is available at start-up. This implies that the fs/notify commits touching the open/close stuff can be the culprit. thanks, Takashi -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/