[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAOH1cHkkKL=LqqaHkmzG6DLckOfVj6vnJnF3BBMqWeXmHxpkSQ@mail.gmail.com>
Date: Mon, 12 Dec 2011 17:56:03 -0800
From: Mark Moseley <moseleymark@...il.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Linux filesystem caching discussion list
<linux-cachefs@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [Linux-cachefs] 3.0.3 64-bit Crash running fscache/cachefilesd
On Fri, Oct 21, 2011 at 11:09 AM, Mark Moseley <moseleymark@...il.com> wrote:
> On Fri, Oct 21, 2011 at 1:16 AM, David Howells <dhowells@...hat.com> wrote:
>> Mark Moseley <moseleymark@...il.com> wrote:
>>
>>> >> [67666.389761] kernel BUG at fs/fscache/operation.c:426!
>>> >
>>> > Can you have a look what's on line 426 for you, please? It's a blank line
>>> > in my kernel. I think I've managed to rearrange my patches to muck the
>>> > ordering up.
>>>
>>> Here's line 426 with some context:
>>
>> Ah... It's the same one you've seen before - and now the debugging patch I
>> gave you has yielded a bit more context.
>>
>> David
>>
>
> Ok, got another of the "[33353.585702] kernel BUG at
> fs/fscache/operation.c:426!" variety. I've attached a dump of fscache
> stats from basically the entire uptime of the box, minus the first
> couple minutes, right till it went down.
Anything I should be trying/testing on 3.1.5 or 3.2-rc?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists