From: Pedro Larroy <piotr@member.fsf.org>
To: Andrew Morton <akpm@osdl.org>
Cc: wli@holomorphy.com, linux-kernel@vger.kernel.org
Subject: Re: [BUG] D-states in test8
Date: Mon, 20 Oct 2003 04:24:43 +0200 [thread overview]
Message-ID: <20031020022443.GA1723@81.38.200.176> (raw)
In-Reply-To: <20031019183610.4410757b.akpm@osdl.org>
On Sun, Oct 19, 2003 at 06:36:10PM -0700, Andrew Morton wrote:
> Pedro Larroy <piotr@member.fsf.org> wrote:
> >
> > On Sun, Oct 19, 2003 at 04:01:27PM -0700, Andrew Morton wrote:
> > > Pedro Larroy <piotr@member.fsf.org> wrote:
> > > >
> > > > Process just started to get into D state, all subsequent ps got into D.
> > > > The first that got into D state was mplayer.
> > >
> > > This might help.
> > >
> > > --- 25/sound/core/pcm_native.c~pcm_native-deadlock-fix 2003-10-19 15:58:31.000000000 -0700
> >
> >
> > Thanks. Also thanks to wli for the insight.
> >
>
> Well. The emphasis is on "might". That locking bug was on an error path
> and it's quite possible that the deadlock is due to a different bug which
> is still there.
>
Now seems I can't get them stuck.
Hmm, Before I just opened twice /dev/dsp IIRC and then both processes got
stuck in D.
so snd_pcm_open_file must have returned < 0
I can try to play a little with it tomorrow to see why gets into the error
path.
--
Pedro Larroy Tovar | piotr%member.fsf.org
Software patents are a threat to innovation in Europe please check:
http://www.eurolinux.org/
next prev parent reply other threads:[~2003-10-20 2:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-19 20:56 Pedro Larroy
2003-10-19 21:03 ` William Lee Irwin III
2003-10-19 22:26 ` Pedro Larroy
2003-10-19 23:02 ` William Lee Irwin III
2003-10-19 23:01 ` Andrew Morton
2003-10-20 1:29 ` Pedro Larroy
2003-10-20 1:36 ` Andrew Morton
2003-10-20 2:24 ` Pedro Larroy [this message]
2003-10-20 3:33 ` William Lee Irwin III
2003-10-20 12:53 ` Diego Calleja García
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=20031020022443.GA1723@81.38.200.176 \
--to=piotr@member.fsf.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.com \
/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
Powered by JetHome