linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adam Sampson <azz@gnu.org>
To: Walter Hofmann <walter.hofmann@physik.stud.uni-erlangen.de>
Cc: Alan Cox <laughing@shared-source.org>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.5-ac15
Date: 20 Jun 2001 20:25:31 +0100	[thread overview]
Message-ID: <87k827t0lw.fsf@cartman.azz.us-lot.org> (raw)
In-Reply-To: <20010615230635.A27708@lightning.swansea.linux.org.uk> <20010617201119.A2331@frodo.uni-erlangen.de> <20010619111955.B2262@frodo.uni-erlangen.de>
In-Reply-To: <20010619111955.B2262@frodo.uni-erlangen.de>

Walter Hofmann <walter.hofmann@physik.stud.uni-erlangen.de> writes:

> It hung when I tried to close a browser window after reading the
> text in it for quite some time. No swapping was going on.

I've just seen this as well (for the first time) with -ac15. I was
playing music with madplay at the time, and then did a "find . -type f
-print0 | xargs -0 chmod 644" on a large directory tree on a reiserfs
partition. A few seconds after I started the command, I got a hang
which lasted a few seconds, then another, then another just after the
find finished. It hasn't happened again since.

All I got in the kernel log was:
2001-06-20 20:15:52.260230500 warning: Sound: DMA (output) timed out -
IRQ/DRQ config error?
2001-06-20 20:16:07.472837500 warning: Sound: DMA (output) timed out -
IRQ/DRQ config error?
which makes sense, since the sound paused at the same time...

Memory stats at the moment (i.e. about five minutes after it happened,
with exactly the same stuff running):

(azz:~) free
             total       used       free     shared    buffers     cached
Mem:        288240     286652       1588        196      30348     224860
-/+ buffers/cache:      31444     256796
Swap:      1048784      52176     996608
(azz:~) vmstat
   procs                      memory    swap          io     system         cpu
 r  b  w   swpd   free   buff  cache  si  so    bi    bo   in    cs  us  sy  id
 1  0  0  52184   1588  30348 224876   0   2    53    62  153   400  68  10  22

.config available on request.

-- 
Adam Sampson <azz@gnu.org>                  <URL:http://azz.us-lot.org/>

  reply	other threads:[~2001-06-20 19:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-15 22:06 Linux 2.4.5-ac15 Alan Cox
2001-06-16 16:48 ` Tom Vier
2001-06-17 18:11 ` Walter Hofmann
2001-06-19  9:19   ` Walter Hofmann
2001-06-20 19:25     ` Adam Sampson [this message]
2001-06-19 21:23   ` Walter Hofmann
2001-06-20 19:56     ` Rik van Riel
2001-06-21 15:22       ` Walter Hofmann
2001-06-21  4:35     ` Marcelo Tosatti
2001-06-21  6:56       ` Mike Galbraith
2001-06-21  5:44         ` Marcelo Tosatti
2001-06-21  8:10           ` Mike Galbraith
2001-06-21 13:14           ` Daniel Phillips
2001-06-21 19:50             ` Marcelo Tosatti
2001-06-22  0:32               ` Daniel Phillips
2001-06-22  9:06           ` Mike Galbraith
2001-06-22  9:57             ` Marcelo Tosatti
2001-06-22 11:50               ` Mike Galbraith
2001-06-22 14:08         ` Linux 2.4.5-ac15 / 2.4.6-pre5 Walter Hofmann
2001-06-22 15:50           ` Mike Galbraith
2001-06-22 17:27             ` Walter Hofmann

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=87k827t0lw.fsf@cartman.azz.us-lot.org \
    --to=azz@gnu.org \
    --cc=laughing@shared-source.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=walter.hofmann@physik.stud.uni-erlangen.de \
    /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;
as well as URLs for NNTP newsgroup(s).