[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090528004959.GH26625@mit.edu>
Date: Wed, 27 May 2009 20:49:59 -0400
From: Theodore Tso <tytso@....edu>
To: Jens Axboe <jens.axboe@...cle.com>
Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
chris.mason@...cle.com, david@...morbit.com, hch@...radead.org,
akpm@...ux-foundation.org, jack@...e.cz,
yanmin_zhang@...ux.intel.com, richard@....demon.co.uk,
damien.wyart@...e.fr
Subject: Re: [PATCH 0/11] Per-bdi writeback flusher threads v8
On Wed, May 27, 2009 at 09:45:43PM +0200, Jens Axboe wrote:
>
> This one has been tested good, where good means that it boots and
> functions normally at least. Whether it fixes your issue, that would be
> interesting to know :-)
>
Unfortunately, it doesn't seem to have. Here's a dmesg with the
softlockup report and the sysrq-t output. Unfortunately the dmesg
file is too big for LKML, so I've compressed it so you can get the
whole thing.
There's also a lockdep warning which fsx triggered.
Same .config as last time, except I bumped up CONFIG_LOG_BUF_SHIFT to
19 to make sure dmesg could capture everything.
- Ted
Download attachment "dmesg-with-patch.gz" of type "application/octet-stream" (41877 bytes)
Powered by blists - more mailing lists