linux-kernel - Re: 2.6.18 BUG: unable to handle kernel NULL pointer dereference at virtual address 000,0000a

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20060924095029.0262a2c8.akpm@osdl.org>
Date:	Sun, 24 Sep 2006 09:50:29 -0700
From:	Andrew Morton <akpm@...l.org>
To:	Christian Weiske <cweiske@...iske.de>
Cc:	linux-kernel@...r.kernel.org, reiserfs-dev@...esys.com,
	Ingo Molnar <mingo@...e.hu>,
	Nick Piggin <nickpiggin@...oo.com.au>
Subject: Re: 2.6.18 BUG: unable to handle kernel NULL pointer dereference at
 virtual address 000,0000a

On Sun, 24 Sep 2006 14:20:14 +0200
Christian Weiske <cweiske@...iske.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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/