public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Jiri Slaby" <jirislaby@gmail.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	"Linux kernel mailing list" <linux-kernel@vger.kernel.org>,
	linux-ext4@vger.kernel.org, "Jan Sonnek" <xsonnek@fi.muni.cz>,
	"Christoph Lameter" <clameter@sgi.com>
Subject: Re: [2.6.25-rc2-mm1] Oops in __kmalloc
Date: Tue, 4 Mar 2008 14:51:40 +0200	[thread overview]
Message-ID: <84144f020803040451u562eb378h2d6c2378d1b174fe@mail.gmail.com> (raw)
In-Reply-To: <47CD2753.5050905@gmail.com>

On Tue, Mar 4, 2008 at 12:41 PM, Jiri Slaby <jirislaby@gmail.com> wrote:
>  >> while booting up a notebook on 32 bit, this oopses appeared on the console
>  >> after ext3 fsck:
>  >> http://www.fi.muni.cz/~xslaby/sklad/mem_oops/
>  >>
>  >> It's 2.6.25-rc2-mm1, I can't find similar reports, is this known or hardware
>  >> issue (unlikely, 2.6.24.2 seems to be OK)?
>  >
>  > I don't recall seeing a similar report and yes, it'll be a kernel bug.
>  >
>  > We've fixed a few things and it could be that this will just go away in
>  > next -mm.  If it doesn't, a bisection search would be good, thanks.
>
>  Well, next -mm is out. Could you test, Jan? [our -mm git is up-to-date]

I don't see your config but if you have CONFIG_SLUB enabled, this is
probably the same problem as:

http://bugzilla.kernel.org/show_bug.cgi?id=10015

which is fixed since 2.6.25-rc2 in mainline.

                              Pekka

  reply	other threads:[~2008-03-04 12:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 15:18 [2.6.25-rc2-mm1] Oops in __kmalloc Jiri Slaby
2008-02-26 18:09 ` Andrew Morton
2008-03-04 10:41   ` Jiri Slaby
2008-03-04 12:51     ` Pekka Enberg [this message]
2008-03-04 12:55       ` Jiri Slaby
2008-03-04 12:57         ` Pekka Enberg

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=84144f020803040451u562eb378h2d6c2378d1b174fe@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=jirislaby@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xsonnek@fi.muni.cz \
    /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