public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: linux-kernel@vger.kernel.org
Subject: Inexplicable disk activity trying to load modules on devfs
Date: Sat, 15 Jun 2002 17:22:44 -0500	[thread overview]
Message-ID: <20020615172244.C19123@crack.them.org> (raw)

I just booted into 2.4.19-pre10-ac2 for the first time, and noticed
something very odd: my disk activity light was flashing at about
half-second intervals, very regularly, and I could hear the disk
moving.  I was only able to track it down to which disk controller, via
/proc/interrupts (are there any tools for monitoring VFS activity? 
They'd be really useful).  Eventually I hunted down the program causing
it: xmms.

The reason turned out to be that I hadn't remembered to build my sound
driver for this kernel version.  Every half-second xmms tried to open
/dev/mixer (and failed, ENOENT).  Every time it did that there was
actual disk activity.  Easily reproducible without xmms.  Reproducible
on any non-existant device in devfs, but not for nonexisting files on
other filesystems.  Is something bypassing the normal disk cache
mechanisms here?  That doesn't seem right at all.

-- 
Daniel Jacobowitz                           Debian GNU/Linux Developer
MontaVista Software                         Carnegie Mellon University

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-15 22:22 Daniel Jacobowitz [this message]
2002-06-15 22:44 ` Inexplicable disk activity trying to load modules on devfs Andrew Morton
2002-06-15 23:04   ` Daniel Jacobowitz
2002-06-18 17:05     ` Rob Landley
2002-06-17 10:10 ` bert hubert
  -- strict thread matches above, loose matches on Subject: below --
2002-06-17  6:59 Borsenkow Andrej
2002-06-17 15:01 ` Daniel Jacobowitz
2002-06-26  3:38   ` Richard Gooch
2002-06-26 22:03     ` Keith Owens
2002-07-19  0:22       ` Richard Gooch
2002-06-26  3:37 ` Richard Gooch

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=20020615172244.C19123@crack.them.org \
    --to=drow@false.org \
    --cc=linux-kernel@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