public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Srihari Vijayaraghavan <sriharivijayaraghavan@yahoo.com.au>
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 08:45:21 +0200	[thread overview]
Message-ID: <1145515521.9712.8.camel@homer> (raw)
In-Reply-To: <20060420055422.37845.qmail@web52610.mail.yahoo.com>

On Thu, 2006-04-20 at 15:54 +1000, Srihari Vijayaraghavan wrote:
> 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.

Ah.  Something bad happened to time keeping, and that likely screwed up
(time dependent) io, not the other way around.

> 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.)

Good idea.  What time source are you using?  I'd try plain old pit.

	-Mike

(As an aside, I suspect you're going to find that you've got dodgy
hardware.) 


  reply	other threads:[~2006-04-20  6:44 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
2006-04-20  6:45             ` Mike Galbraith [this message]
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=1145515521.9712.8.camel@homer \
    --to=efault@gmx.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sriharivijayaraghavan@yahoo.com.au \
    /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