public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: Jorge Nerin <comandante@zaralinux.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	linux-smp <linux-smp@vger.kernel.org>
Subject: Re: xmms child blocked at end (2.4.18pre1)
Date: Sun, 06 Jan 2002 23:19:52 +0100	[thread overview]
Message-ID: <3C38CD88.95284629@loewe-komp.de> (raw)
In-Reply-To: <3C388442.102@zaralinux.com>

Jorge Nerin schrieb:
> 
> Hello, I have a very strange thing here.
> 
> I have a 2x200mmx using 2.4.18pre1, xmms 1.2.5, xawtv-3.61 and XFree86
> Version 4.1.0.
> 
> The situation is that I have a nfs mounted share with mp3, using xmms to
> play them, (3c503 over coax) everithing goes well until I put xawtv in
> fullscreen mode. I don't know why, but at this time in short time the
> child thread of xmms blocks for a long time in end, having xawtv in a
> window does not cause this.
> 
> Here is a vmstat 1 log:
[snip] 
> The only blocked task is xmms child, as I said it's blocked in end, so
> it empties it's buffer and you can hear it
> 
> Another thing I have noticed is that when I have a big transfer with
> this card (I have another 3c595) and having xawtv in full screen I can
> see dropped frames, I assume this is for the speed downgrade of the pci
> bus to acomodate isa tranfers, the 3c503 is a very old isa nic, and my
> tv capture is a pci bt848.
> 

"end" is the name, because the address is bigger than any known symbol.
I think it has something to do with pthread in general - since I observed
it several times with  threaded apps (not only xmms)

      reply	other threads:[~2002-01-06 22:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-06 17:07 xmms child blocked at end (2.4.18pre1) Jorge Nerin
2002-01-06 22:19 ` Peter Wächtler [this message]

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=3C38CD88.95284629@loewe-komp.de \
    --to=pwaechtler@loewe-komp.de \
    --cc=comandante@zaralinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-smp@vger.kernel.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