From: Takashi Iwai <tiwai@suse.de>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Pekka Enberg <penberg@kernel.org>, Thomas Meyer <thomas@m3y3r.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: 2.6.36: Sound stop working
Date: Thu, 12 Aug 2010 23:17:10 +0200 [thread overview]
Message-ID: <s5hbp97ttt5.wl%tiwai@suse.de> (raw)
In-Reply-To: <4C646110.1040104@gmail.com>
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 <thomas@m3y3r.de> 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
next prev parent reply other threads:[~2010-08-12 21:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 20:00 Thomas Meyer
2010-08-12 20:10 ` Pekka Enberg
2010-08-12 20:20 ` Linus Torvalds
2010-08-12 21:01 ` Linus Torvalds
2010-08-12 20:26 ` Takashi Iwai
2010-08-12 21:01 ` Jiri Slaby
2010-08-12 21:14 ` Maxim Levitsky
2010-08-12 21:17 ` Takashi Iwai [this message]
2010-08-12 21:41 ` Linus Torvalds
2010-08-12 21:50 ` Linus Torvalds
2010-08-12 21:52 ` Al Viro
2010-08-12 22:19 ` Linus Torvalds
2010-08-13 1:53 ` Eric Paris
2010-08-13 7:50 ` Jiri Slaby
2010-08-12 22:07 ` Takashi Iwai
2010-08-12 21:18 ` Linus Torvalds
2010-08-12 21:24 ` Jiri Slaby
2010-08-12 21:45 ` Takashi Iwai
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=s5hbp97ttt5.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=thomas@m3y3r.de \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®