[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1386097126.2741.1.camel@buesod1.americas.hpqcorp.net>
Date: Tue, 03 Dec 2013 10:58:46 -0800
From: Davidlohr Bueso <davidlohr@...com>
To: Jan Kara <jack@...e.cz>
Cc: tytso@....edu, Linux Kernel <linux-kernel@...r.kernel.org>,
linux-ext4@...r.kernel.org
Subject: Re: still running into WARNING: CPU: at fs/ext4/inode.c:230
ext4_evict_inode+0x4a6/0x4e0
On Fri, 2013-11-29 at 08:37 +0100, Jan Kara wrote:
> On Wed 16-10-13 20:38:07, Jan Kara wrote:
> > On Wed 16-10-13 08:56:07, Davidlohr Bueso wrote:
> > > On Wed, 2013-10-16 at 14:50 +0200, Jan Kara wrote:
> > > > On Tue 15-10-13 19:02:04, Davidlohr Bueso wrote:
> > > > > Hello Jan,
> > > > >
> > > > > Just wanted to let you know I hit this[1] again on Linus' latest. The
> > > > > setup/workload is *identical* to the reported one a few months ago.
> > > > >
> > > > > [1] https://lkml.org/lkml/2013/8/1/532
> > > > >
> > > > > Here's the complete output, I hope it helps...
> > > > Thanks for the headup. Last time I wasn't able to reproduce this and
> > > > eventually forgot about the problem. Can I send you a debug patch and you
> > > > would run a kernel with it? Thanks.
> > >
> > > Sure.
> > OK, attached is the debug patch. Please apply it and send dmesg when the
> > problem reproduces. Also please attach System.map so that I can map the
> > 'created at' addresses to symbols. Thanks.
> Ping? Any luck with the debug patch?
Sorry for the delay, I haven't had much time to look into this. I do
remember applying the patch and getting a panic - I don't have any more
data at the moment, hopefully I can get back soon with details.
Thanks,
Davidlohr
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists