From: Hans Lambrechts <hans.lambrechts@skynet.be>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Hans Lambrechts <hans.lambrechts@skynet.be>,
linux-kernel@vger.kernel.org,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: Happy v2.6.28
Date: Tue, 30 Dec 2008 08:42:34 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0812300835300.3744@server.home.lan> (raw)
In-Reply-To: <1230548230.8603.5.camel@penberg-laptop>
On Mon, 29 Dec 2008, Pekka Enberg wrote:
> Hi Hans,
>
> On Thu, 2008-12-25 at 13:45 +0100, Hans Lambrechts wrote:
> > > Looks like slab corruption. Can we have your .config, please? I'm
> > > cc'ing netdev as the oops happens in kmem_cache_alloc() so the
> > > networking code is a prime suspect of the corrupting kmem_cache_free()
> > > call (although the bug might be elsewhere as well).
>
> Can you boot the kernel with "slub_debug slub_nomerge" passed as kernel
> parameters and try to reproduce the oops, please? Maybe we can get more
> information on the bug.
>
> Alternatively, you can do a git bisect to pinpoint the broken patch
> between -rc9 and -final.
>
> Pekka
>
Hi Pekka,
after the first oops I've decided to try 2.6.28 again so I could send
you more information. I'm running 2.6.28 now for a few days with several
restarts and no more oops.
This seems a very rare to hit bug or my 6yo box is almost end of life.
Hans
next prev parent reply other threads:[~2008-12-30 7:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bMLNZ-3QM-1@gated-at.bofh.it>
[not found] ` <200812250853.mBP8rxrr004080@server.home.lan>
2008-12-25 12:26 ` Happy v2.6.28 Pekka Enberg
2008-12-25 12:45 ` Hans Lambrechts
2008-12-29 10:57 ` Pekka Enberg
2008-12-30 7:42 ` Hans Lambrechts [this message]
2009-01-02 14:06 ` Christoph Lameter
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=Pine.LNX.4.64.0812300835300.3744@server.home.lan \
--to=hans.lambrechts@skynet.be \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).