From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Marco Berizzi" <pupilla@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at mm/slab.c:610
Date: Wed, 14 Mar 2007 12:41:51 +0200 [thread overview]
Message-ID: <84144f020703140341p322d9dc5wb9edc37bf923685d@mail.gmail.com> (raw)
In-Reply-To: <BAY103-DAV1337A9B2136C6C89DC0C0DB2730@phx.gbl>
Hi Marco,
On 3/14/07, Marco Berizzi <pupilla@hotmail.com> wrote:
> Hello everybody. Sorry for posting to this list, but I'm pretty lost.
Don't worry, this is the proper mailing list for bug reports.
On 3/14/07, Marco Berizzi <pupilla@hotmail.com> wrote:
> I don't think this is related to buggy hardware because it is happening
> on 3 different boxes with the same hardware config.
No, looks like someone is feeding a bad pointer to slab. The debug
check is relatively new and in previous kernels the problem would
might have gone unnoticed causing silent corruption of the slab.
On 3/14/07, Marco Berizzi <pupilla@hotmail.com> wrote:
> ksymoops 2.4.10 on i686 2.6.20. Options used
>From Documentation/oops-tracing.txt:
"NOTE: ksymoops is useless on 2.6. Please use the Oops in its original format
(from dmesg, etc). Ignore any references in this or other docs to "decoding
the Oops" or "running it through ksymoops". If you post an Oops from 2.6 that
has been run through ksymoops, people will just tell you to repost it."
So, can you please repost the original oops? Also, please enable
CONFIG_DEBUG_SLAB and try to reproduce. Thanks.
next prev parent reply other threads:[~2007-03-14 10:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 9:11 Marco Berizzi
2007-03-14 10:41 ` Pekka Enberg [this message]
2007-03-14 11:21 ` Marco Berizzi
2007-03-14 11:54 Marco Berizzi
2007-03-14 12:05 ` Pekka Enberg
2007-03-14 13:55 Chris Rankin
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=84144f020703140341p322d9dc5wb9edc37bf923685d@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=pupilla@hotmail.com \
/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
all inboxes | Powered by JetHome®