All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Srihari Vijayaraghavan <sriharivijayaraghavan@yahoo.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.16.1 & D state processes
Date: Mon, 17 Apr 2006 21:03:08 -0700	[thread overview]
Message-ID: <20060417210308.1fadc766.akpm@osdl.org> (raw)
In-Reply-To: <20060417234939.28833.qmail@web52601.mail.yahoo.com>

Srihari Vijayaraghavan <sriharivijayaraghavan@yahoo.com.au> wrote:
>
> I've reported the same problem on FC5 kernels
>  (https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=186856)
>  too, assuming it was an FC only problem. But as it
>  turns out, kernel.org kernels too suffer from this,
>  though it took a while to prove that :(.

Your I/O system has lost some I/O requests: we sent write requests down,
and no completion ever came back.

It could be a broken device driver - please describe the I/O stack.

Or it could be lost interrupts - could be broken platform interrupt setup,
or broken hardware.

  reply	other threads:[~2006-04-18  4:03 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 [this message]
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
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=20060417210308.1fadc766.akpm@osdl.org \
    --to=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 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.