From: Andrew Morton <akpm@zip.com.au>
To: Dan Maas <dmaas@dcine.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: unwanted disk access by the kernel?
Date: Thu, 14 Mar 2002 23:00:55 -0800 [thread overview]
Message-ID: <3C919C27.CA5558AF@zip.com.au> (raw)
In-Reply-To: <20020315013644.A26891@morpheus>
Dan Maas wrote:
>
> I've been trying to set up my laptop for mobile use. I'm having a
> problem with unwanted disk activity - even when the system is
> completely idle, there is still an occasional trickle of disk writes
> (which prevents the poor hard drive from ever spinning down).
>
> Yes, I thought this was a user-space issue too - but even booting into
> a bare-bones root environment does not stop the occasional disk
> access! Here is everything that's left:
Are all filesystems mounted with the `noatime' mount option?
> PID USER VSZ RSS TIME STAT COMMAND WCHAN
> 7 root 0 0 00:00:00 SW [kupdated] kupdate
> 6 root 0 0 00:00:00 SW [bdflush] bdflush
> 5 root 0 0 00:00:00 SW [kswapd] kswapd
> 4 root 0 0 00:00:00 SWN [ksoftirqd_CPU0] ksoftirqd
> 1 root 1316 524 00:00:05 S init [S] select
> 2 root 0 0 00:00:00 SW [keventd] context_thread
> 3 root 0 0 00:00:00 SW [kapmd] apm_mainloop
> 8 root 0 0 00:00:00 Z [khubd <defunct> exit
eww. Does khubd always do that? Does this patch make it behave?
--- linux-2.4.19-pre3/drivers/usb/hub.c Mon Mar 11 14:53:21 2002
+++ linux-akpm/drivers/usb/hub.c Thu Mar 14 22:59:17 2002
@@ -908,6 +908,7 @@ static int usb_hub_thread(void *__hub)
*/
daemonize();
+ reparent_to_init();
/* Setup a nice name */
strcpy(current->comm, "khubd");
-
next prev parent reply other threads:[~2002-03-15 7:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 6:36 unwanted disk access by the kernel? Dan Maas
2002-03-15 7:00 ` Andrew Morton [this message]
2002-03-15 9:20 ` Jeremy Jackson
2002-03-15 18:46 ` Dan Maas
2002-03-15 19:02 ` Alan Cox
2002-03-16 1:30 ` Mike Fedyk
2002-03-16 15:11 ` Joachim Breuer
2002-03-15 14:35 ` Alan Cox
2002-03-19 15:06 ` Pavel Machek
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=3C919C27.CA5558AF@zip.com.au \
--to=akpm@zip.com.au \
--cc=dmaas@dcine.com \
--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 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.