[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071007233618.GV995458@sgi.com>
Date: Mon, 8 Oct 2007 09:36:18 +1000
From: David Chinner <dgc@....com>
To: Laurent Caron <lcaron@...sa.com>
Cc: drbd-user@...bit.com, linux-kernel@...r.kernel.org
Subject: Re: Crash on 2.6.21.7 Vanilla + DRBD 0.7
On Thu, Oct 04, 2007 at 09:29:40AM +0200, Laurent Caron wrote:
>
> Hi,
>
> I did compile a fresh 2.6.21.7 kernel from kernel.org (no distro patch, ....), and latest svn (3062) 0.7.X drbd.
>
> After just 2 days of uptime, I did experience another crash.
>
> I wonder if it is an XFS related bug, a DRBD one, or related to XFS on top of DRBD.
>
> This bug seems to occur with intensive IO operations.
>
> What do you think about it ?
This still looks like memory corruption of some sort:. I'd
suspect DRBD at this point because nobody is repprting this against
other block devices in 2.6.21....
> Oct 3 18:55:23 kernel: Oops: 0002 [#1]
> Oct 3 18:55:23 kernel: SMP
> Oct 3 18:55:23 kernel: CPU: 7
> Oct 3 18:55:23 kernel: EIP: 0060:[<c016540c>] Not tainted VLI
> Oct 3 18:55:23 kernel: EFLAGS: 00010046 (2.6.21-dl380-g5-20071001 #1)
> Oct 3 18:55:23 kernel: EIP is at cache_alloc_refill+0x11c/0x4f0
Can you turn on slab debug and poisoning and see where
the kernel fails with that? e.g. set:
CONFIG_DEBUG_SLAB=y
CONFIG_DEBUG_SLAB_LEAK=y
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
-
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