From: Andrew Morton <akpm@digeo.com>
To: J Sloan <joe@tmsusa.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: slab error in 2.5.64-mm4
Date: Mon, 10 Mar 2003 00:00:14 -0800 [thread overview]
Message-ID: <20030310000014.64de2f36.akpm@digeo.com> (raw)
In-Reply-To: <3E6C3075.4040408@tmsusa.com>
J Sloan <joe@tmsusa.com> wrote:
>
> This may be of interest -
>
> kernel: 2.5.64-mm4
>
> Linux distro: Red Hat 8.0 + updates
>
> Hardware:
> Celeron 1.2 Ghz on genuine Intel Motherboard, 512 MB RAM
>
> Just recompiled 2.5.64-mm4 with full debugging
> and saw a slab error right after bringing up the
> ethernet interfaces -
>
> Full kernel log attached, but the meat of it is here:
>
> Mar 9 21:42:54 jyro kernel: Slab corruption: start=dfc15964,
> expend=dfc159e3, problemat=dfc1599c
> Mar 9 21:42:54 jyro kernel: Last user: [<00000000>](0x0)
Drat. We should _not_ have a zero here. Without this info we know next to
nothing.
Please ensure that you have CONFIG_FRAME_PONTER enabled. But the slab
diagnostic seems to work OK here without that.
Oh well. It'll come again.
prev parent reply other threads:[~2003-03-10 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 6:28 slab error in 2.5.64-mm4 J Sloan
2003-03-10 8:00 ` Andrew Morton [this message]
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=20030310000014.64de2f36.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=joe@tmsusa.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.