mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: "Måns Rullgård" <mru@kth.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Strange xmms deaths under high disk load
Date: Tue, 27 Jan 2004 10:27:06 +1100	[thread overview]
Message-ID: <4015A24A.3090101@cyberone.com.au> (raw)
In-Reply-To: <yw1xu12i1fak.fsf@ford.guide>



Måns Rullgård wrote:

>I have encountered a very strange (to me, at least) error.  I can
>reliably cause xmms to crash by simply doing some intensive disk IO.
>Copying a few hundred megabytes usually does it.  After about 20
>seconds of heavy disk IO, xmms will die with this message:
>
>** WARNING **: snd_pcm_wait: Input/output error
>Xlib: unexpected async reply (sequence 0x2ef5c)!
>
>The hex number varies.
>
>The machine is an Alpha SX164 running Linux 2.6.2-rc2 patched up to
>ALSA 1.0.1.  The problem has been around for quite a while, probably
>also with kernel 2.4.21, though I can't confirm that at the moment.
>The sound card is a cmi8738.
>
>If I play music with TCVP instead, it keeps playing, but sound is
>choppy at intervals.  Below is vmstat output during a copying.
>
>procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu----
> r  b   swpd   free   buff  cache   si   so    bi    bo   in    cs us sy id wa
> 0  0      0  86128   3424 165920    0    0    66    66   24     4 23 23 54  0
> 0  0      0  86128   3424 165920    0    0     0     0 1131  1352 17 14 69  0
> 0  0      0  86128   3424 165920    0    0     0     0 1128  1360 13  4 84  0
> 0  0      0  86128   3424 165920    0    0     0     0 1129  1351 13  4 84  0
> 0  0      0  86128   3424 165920    0    0     0   153 1142  1361 14  3 83  0
> 0  0      0  86128   3424 165920    0    0     0     0 1127  1353 14  4 83  0
> 0  0      0  86128   3424 165920    0    0     0     0 1128  1348 12  3 84  0
> 0  0      0  86128   3424 165920    0    0     0     0 1130  1344 17 15 69  0
> 0  0      0  86000   3424 166048    0    0   128     0 1132  1356 13  3 84  0
>
...

>11  2      0   2400   3392 246368    0    0   768 26112  969   626 25 71  0  3
>
...

>11  0      0   3040   1704 248160    0    0     0 33704  696    58 10 90  0  0
>
...

>
> 1  1      0   2528   1736 250608    0    0  1756 21332  965   590 35 56  0  8
>

Looks like you might be losing timer interrupts, possibly caused
by an IDE disk doing PIO?



  reply	other threads:[~2004-01-26 23:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-26 23:05 Måns Rullgård
2004-01-26 23:27 ` Nick Piggin [this message]
2004-01-26 23:45   ` Måns Rullgård
2004-01-27 10:36 Piotr Kowalczyk

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=4015A24A.3090101@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mru@kth.se \
    /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