From: David Chinner <dgc@sgi.com>
To: Laurent Caron <lcaron@lncsa.com>
Cc: drbd-user@linbit.com, linux-kernel@vger.kernel.org
Subject: Re: Crash on 2.6.21.7 Vanilla + DRBD 0.7
Date: Mon, 8 Oct 2007 09:36:18 +1000 [thread overview]
Message-ID: <20071007233618.GV995458@sgi.com> (raw)
In-Reply-To: <20071004092111.ahweigho@trusted.lncsa.com>
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
next prev parent reply other threads:[~2007-10-07 23:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 7:29 Crash on 2.6.21.7 Vanilla + DRBD 0.7 Laurent Caron
2007-10-07 23:36 ` David Chinner [this message]
2007-10-08 12:47 ` Laurent CARON
-- strict thread matches above, loose matches on Subject: below --
2007-10-04 13:33 vindex+lists-xfs
2007-10-04 14:27 ` Hannes Dorbath
2007-10-04 16:42 ` Laurent CARON
2007-10-04 14:35 ` Hannes Dorbath
2007-10-04 16:33 ` Laurent CARON
2007-10-10 15:15 ` Louis-David Mitterrand
2007-10-10 22:46 ` David Chinner
2007-10-11 7:36 ` Laurent CARON
2007-10-04 23:10 ` David Chinner
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=20071007233618.GV995458@sgi.com \
--to=dgc@sgi.com \
--cc=drbd-user@linbit.com \
--cc=lcaron@lncsa.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.