From: Srihari Vijayaraghavan <sriharivijayaraghavan@yahoo.com.au>
To: Mike Galbraith <efault@gmx.de>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.16.1 & D state processes
Date: Thu, 20 Apr 2006 15:54:22 +1000 (EST) [thread overview]
Message-ID: <20060420055422.37845.qmail@web52610.mail.yahoo.com> (raw)
In-Reply-To: <1145364422.7515.5.camel@homer>
--- Mike Galbraith <efault@gmx.de> wrote:
> On Tue, 2006-04-18 at 19:35 +1000, Srihari
> Vijayaraghavan wrote:
> > --- Mike Galbraith <efault@gmx.de> wrote:
> > > On Tue, 2006-04-18 at 15:07 +1000, Srihari
> > > Vijayaraghavan wrote:
> > > > io scheduler cfq registered (default)
> > > ...
> > > Hmm. Recovers [odd] but takes long time
> [odder].
> > > I'd try to eliminate
> > > io scheduler at this point.
> >
> > Interesting. Considering the minimal .config,
> where I
> > haven't experienced this problem over a week
> uptime,
> > also having CFQ as the default elevator, do you
> still
> > believe CFQ is involved? (I guess if CFQ could be
> > influenced by other kernel configurations, then
> > perhaps another elevator might help. It's worth
> > trying.)
>
> I don't know that CFQ is involved. With it
> recovering though, the only
> thing I could think of was a request stucking in the
> io scheduler's
> gizzard for some reason.
>
> It's just a suggestion, and one you can try without
> even rebooting.
Thanks for that. When it happened today on 2.6.16.7,
I've started using deadline now.
A couple of interesting things I've noticed after its
recovery:
1. Executing "time sleep 1", takes more than 1 second.
It reports real as 3 to 5 seconds, while my stop watch
measures it as closer to 50 seconds.
2. Pressing & holding a key at the console doesn't
produce repeating characters.
Thought they might shed some light on the problem. (I
ought to look at all the RTC & Time related settings
between my minimal .config & FC5's, for I believe
they're connected.)
I haven't rebooted it yet. I'm sure it'll be back to
normal after the reboot.
Thanks
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-04-20 5:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 23:49 2.6.16.1 & D state processes Srihari Vijayaraghavan
2006-04-18 4:03 ` Andrew Morton
2006-04-18 5:07 ` Srihari Vijayaraghavan
2006-04-18 6:30 ` Mike Galbraith
2006-04-18 9:35 ` Srihari Vijayaraghavan
2006-04-18 12:47 ` Mike Galbraith
2006-04-20 5:54 ` Srihari Vijayaraghavan [this message]
2006-04-20 6:45 ` Mike Galbraith
2006-04-20 6:51 ` Mike Galbraith
2006-05-03 7:04 ` Srihari Vijayaraghavan
2006-05-03 7:18 ` Mike Galbraith
2006-05-08 0:57 ` Srihari Vijayaraghavan
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=20060420055422.37845.qmail@web52610.mail.yahoo.com \
--to=sriharivijayaraghavan@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=efault@gmx.de \
--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.