public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Tue, 18 Apr 2006 19:35:21 +1000 (EST)	[thread overview]
Message-ID: <20060418093521.41424.qmail@web52610.mail.yahoo.com> (raw)
In-Reply-To: <1145341823.9243.10.camel@homer>

--- 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'm on 2.6.16.7 full config now. I'll try a few
things, if I were to observe problems:
1. Use deadline elevator
2. Start eliminating a few kernel configurations to
narrow it down

Thanks 

Send instant messages to your online friends http://au.messenger.yahoo.com 

  reply	other threads:[~2006-04-18  9:35 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 [this message]
2006-04-18 12:47         ` Mike Galbraith
2006-04-20  5:54           ` Srihari Vijayaraghavan
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=20060418093521.41424.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox