public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ted Ts'o" <tytso@mit.edu>
To: Dave Jones <davej@redhat.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Wu Fengguang <fengguang.wu@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: lockups shortly after booting in current git.
Date: Thu, 29 Mar 2012 14:45:10 -0700	[thread overview]
Message-ID: <20120329214510.GD13970@thunk.org> (raw)
In-Reply-To: <20120329211244.GA18684@redhat.com>

On Thu, Mar 29, 2012 at 05:12:44PM -0400, Dave Jones wrote:
> 
> I'll try a build with just that reverted, given the bisect build is taking a while.
> 

Something else you could try doing without even have to do a rebuild
is to just mount the filesystem with the mount option
nomblk_io_submit, which avoids using any of the code in
fs/ext4/page_io.c.  (This option causes ext4 will send blocks to the
block layer old fashioned way, on 4k block at a time, and rely on the
elevator code to coaslece the write requests.)

> Any thoughts on any printk's I could add to verify a situation occurred or not ?
> The problem with bisecting a bug like this is that it's hard to tell if
> the bug has been fixed, or if I've just not hit it yet.

If it really is about the PageWriteback bit not getting cleared, not
really.  If you're willing to expand the struct page to include a
timestamp, we could use that to note pages which have been in
writeback for a long time, but that's obviously quite expensive.

But actually, normally when it's a PageWriteback stall, usually you
get a soft lockup warning, assuming that was compiled into the system.
And I didn't see that in your trace, which is surprising given the
symptoms you described.  Was it perhaps not included in your log file
snippet?  Or was soft lockup detection not enabled?

	     	      	     	       	   - Ted



  reply	other threads:[~2012-03-29 21:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-29 15:55 lockups shortly after booting in current git Dave Jones
2012-03-29 18:23 ` Linus Torvalds
2012-03-29 18:29   ` Dave Jones
     [not found] ` <CA+55aFxOcMt_mcr+ZYwc-SpKbROnh4Gn7jqrFY_SZcBy1Ev7Qw@mail.gmail.com>
     [not found]   ` <20120329182632.GA6891@redhat.com>
2012-03-29 18:36     ` Linus Torvalds
2012-03-29 19:53       ` Dave Jones
2012-03-29 20:10         ` Linus Torvalds
2012-03-29 20:26           ` Dave Jones
2012-03-29 20:38             ` Linus Torvalds
2012-03-29 20:39             ` Ted Ts'o
2012-03-29 20:59               ` Linus Torvalds
2012-03-29 21:12                 ` Dave Jones
2012-03-29 21:45                   ` Ted Ts'o [this message]
2012-03-29 21:49                     ` Dave Jones
2012-03-29 21:52                       ` Linus Torvalds
2012-03-29 22:54                         ` Dave Jones
2012-03-29 23:04                           ` Linus Torvalds
2012-03-29 23:35                             ` Ted Ts'o
2012-03-29 23:25                         ` Ted Ts'o
2012-03-29 21:52                     ` Dave Jones

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=20120329214510.GD13970@thunk.org \
    --to=tytso@mit.edu \
    --cc=davej@redhat.com \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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