public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Christian Weiske <cweiske@cweiske.de>
Cc: linux-kernel@vger.kernel.org, reiserfs-dev@namesys.com,
	Ingo Molnar <mingo@elte.hu>,
	Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: 2.6.18 BUG: unable to handle kernel NULL pointer dereference at virtual address 000,0000a
Date: Sun, 24 Sep 2006 09:50:29 -0700	[thread overview]
Message-ID: <20060924095029.0262a2c8.akpm@osdl.org> (raw)
In-Reply-To: <451677FE.2070409@cweiske.de>

On Sun, 24 Sep 2006 14:20:14 +0200
Christian Weiske <cweiske@cweiske.de> wrote:

> > It would be interesting to find out if enabling CONFIG_4KSTACKS makes this
> > go away (although I'm not sure why).
> So, here are the results from the 4K runs:
> 
> Beside one Oops message, I got a "kernel BUG at mm/slab.c:2747!" in log
> #1. Call traces as usual.
> 
> Further, logs #2 and #3 show funny things; the thing just rebooted. Log
> #2 has some oversized ethernet frames before the reboot.

I assume that you have confirmed that the machine doesn't have hardware
problems?  Does it run some earlier kernel OK?  

And how long does it take to crash?

Thanks.

  reply	other threads:[~2006-09-24 16:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-23 15:56 2.6.18 BUG: unable to handle kernel NULL pointer dereference at virtual address 000,0000a Christian Weiske
2006-09-23 20:42 ` Andrew Morton
2006-09-23 20:39   ` Ingo Molnar
2006-09-24  9:11   ` Christian Weiske
2006-09-24  9:30     ` Christian Weiske
2006-09-24 10:19     ` Andrew Morton
2006-09-24 17:59       ` Ingo Molnar
2006-09-24 12:20   ` Christian Weiske
2006-09-24 16:50     ` Andrew Morton [this message]
2006-09-24 17:47       ` Christian Weiske
2006-09-25  4:14         ` Nick Piggin
2006-09-25 18:36         ` Christian Weiske
2006-09-25 21:26           ` Andrew Morton
2006-10-02 17:01             ` Christian Weiske
2006-10-03 14:20               ` Christian Weiske

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=20060924095029.0262a2c8.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=cweiske@cweiske.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nickpiggin@yahoo.com.au \
    --cc=reiserfs-dev@namesys.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