All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jorge Nerin <comandante@zaralinux.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
	linux-smp <linux-smp@vger.kernel.org>
Subject: xmms child blocked at end (2.4.18pre1)
Date: Sun, 06 Jan 2002 18:07:14 +0100	[thread overview]
Message-ID: <3C388442.102@zaralinux.com> (raw)

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:

    procs                      memory    swap          io     system 
      cpu
  r  b  w   swpd   free   buff  cache  si  so    bi    bo   in    cs  us 
  sy  id
  4  0  0  58864   2928   3172  41072   0   0     0     0  153  1213  30 
  13  57
  1  1  0  58864   2932   3156  41088   0   0     0     0  150  1166  20 
  14  66
  2  1  0  58864   2932   3156  41088   0   0     0     0  152  1115  20 
  20  60
  0  1  0  58864   2920   3164  41088   0   0     0    12  161  1117  20 
  20  60
  1  1  0  58864   2920   3164  41088   0   0     0     0  160  1119  19 
  20  62
  2  1  0  58864   2920   3164  41088   0   0     0     0  153  1212   9 
  28  63
  0  1  0  58864   3288   3164  41088   0   0     0     0  161  1086  16 
  17  68
  0  1  0  58864   3272   3164  41100   0   0     0     0  155  1030  12 
  16  72
  0  1  0  58864   3264   3172  41088   0   0     0    56  174   978  14 
  14  72
  0  1  0  58864   3272   3172  41088   0   0     0     0  156   992   8 
  15  77
  1  1  0  58864   3264   3172  41088   0   0     0     0  159  1012   9 
  15  76
  1  1  0  58864   3264   3172  41088   0   0     0     0  151  1044  10 
   9  81
  2  1  0  58864   3256   3172  41088   0   0     0     0  276  1265  17 
  18  66
  3  1  0  58864   3256   3180  41088   0   0     0    12  398  1832  30 
  23  47
  0  1  0  58864   3244   3180  41088   0   0     0     0  278  1412  19 
  15  66
  0  1  0  58864   3252   3180  41088   0   0     0     0  151  1068  10 
   5  85
  0  1  0  58864   3244   3180  41088   0   0     0     0  155  1150  10 
  10  80
  2  0  0  58864   3232   3188  41088   0   0     0    12  193   951  20 
  24  56
  2  0  0  58864   3156   3188  41088   0   0     0     0  155   834  72 
  13  16

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.

Don't know if this rings a bell of somebody.

P.D. Sorry for my bad english.

-- 
Jorge Nerin
<comandante@zaralinux.com>


             reply	other threads:[~2002-01-06 21:17 UTC|newest]

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

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=3C388442.102@zaralinux.com \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.