mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
To: Valdis.Kletnieks@vt.edu
Cc: nishimura@mxp.nes.nec.co.jp,
	Andrew Morton <akpm@linux-foundation.org>,
	penguin-kernel@i-love.sakura.ne.jp, linux-kernel@vger.kernel.org
Subject: Re: Random freeze (Re: mmotm 2008-11-19-02-19 uploaded)
Date: Fri, 21 Nov 2008 15:54:54 +0900	[thread overview]
Message-ID: <20081121155454.a376d737.nishimura@mxp.nes.nec.co.jp> (raw)
In-Reply-To: <5539.1227244998@turing-police.cc.vt.edu>

Hi.

On Fri, 21 Nov 2008 00:23:18 -0500, Valdis.Kletnieks@vt.edu wrote:
> On Thu, 20 Nov 2008 15:20:54 PST, Andrew Morton said:
> 
> > The traditional cause of the above trace is that someone mucked up the
> > block/driver/irq-routing layer and we lost an IO completion.
> 
> Yes, that would explain all the symptoms and tracebacks - everybody comes
> to a screeching halt the next time they try to go to disk, while the actual
> disk drive is showing zero activity.
> 
> > It's also of course possible (but less common) that someone mucked up
> > the VFS.  It would be interesting to revert
> > do_mpage_readpage-dont-submit-lots-of-small-bios-on-boundary.patch.
> 
> I'm seeing an MTBF of about 2-3 hours when actually applying an I/O load to the
> system.  I'll try reverting that patch, and if it survives an entire day or
> two it will be pretty strong circumstantial evidence that patch is the culprit...
> 
Just FYI, I had seen similar errors with recent mmotms,
but current mmotm(2008-11-20-17-03) seems more stable in my environment.


Thanks,
Daisuke Nishimura.

  reply	other threads:[~2008-11-21  8:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-20  6:09 Tetsuo Handa
2008-11-20 23:05 ` Valdis.Kletnieks
2008-11-20 23:20   ` Andrew Morton
2008-11-21  5:23     ` Valdis.Kletnieks
2008-11-21  6:54       ` Daisuke Nishimura [this message]
2008-11-21 18:12     ` Valdis.Kletnieks
2008-11-25  2:32 Tetsuo Handa

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=20081121155454.a376d737.nishimura@mxp.nes.nec.co.jp \
    --to=nishimura@mxp.nes.nec.co.jp \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    /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

all inboxes | Powered by JetHome®