All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Simon Li <simon.jiyou@gmail.com>
Cc: Robert Hancock <hancockrwd@gmail.com>,
	Jeff Garzik <jeff@garzik.org>,
	linux-ide@vger.kernel.org
Subject: Re: Pls help for LibATA caused kernel temporary hung.
Date: Tue, 29 Jun 2010 09:20:16 +0200	[thread overview]
Message-ID: <4C299EB0.6070102@gmail.com> (raw)
In-Reply-To: <AANLkTimnoyjEVTmorcPD_Ph9TDjNo33jz7qcwEE0z6-2@mail.gmail.com>

Hello, Simon.

On 06/29/2010 09:10 AM, Simon Li wrote:
> We observed that all the processes on the blade are totally stuck,
> though only one process is actually accessing the disks, other
> processes are mostly CPU-consuming applications.

Can you please turn on printk timestamp and attach the dmesg output
_after_ such failure?  I think there are two possibilities.  The
kernel could be generating too many messages to slow serial console,
or the it might as well be that all processes got stuck on IO.  It's
really difficult to figure out what's going on without more specific
information.  What does "stuck" mean?  Does it mean all of them are in
iowait or is the kernel just stuck inside kernel?

Thanks.

-- 
tejun

  reply	other threads:[~2010-06-29  7:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTinbQHdo40Drqc5Ydur5lCrAktHHDig45HDrC6s1@mail.gmail.com>
     [not found] ` <4C2777D3.1050208@gmail.com>
2010-06-28  7:38   ` Pls help for LibATA caused kernel temporary hung Simon Li
2010-06-28  9:02     ` Jeff Garzik
2010-06-28  9:09       ` Simon Li
2010-06-29  1:36         ` Marek Vasut
2010-06-29  5:11         ` Robert Hancock
2010-06-29  7:10           ` Simon Li
2010-06-29  7:20             ` Tejun Heo [this message]
2010-06-29  7:27               ` Simon Li
2010-06-29  7:29                 ` Tejun Heo
     [not found]                   ` <AANLkTinYbtr1qBLibK7wYizCDq8V0HwFu01NUr-f_KfR@mail.gmail.com>
2010-06-30  0:38                     ` Robert Hancock

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=4C299EB0.6070102@gmail.com \
    --to=htejun@gmail.com \
    --cc=hancockrwd@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=simon.jiyou@gmail.com \
    /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.