Date: Sun, 25 Jan 2004 15:25:59 -0800
From: Andrew Morton <akpm@osdl.org>
To: Eric <eric@cisu.net>
Cc: sboyce@blueyonder.co.uk, linux-kernel@vger.kernel.org, bunk@fs.tum.de,
       Linus Torvalds <torvalds@osdl.org>
Subject: Re: 2.6.2-rc1-mm2 kernel oops
Message-Id: <20040125152559.55165860.akpm@osdl.org>
In-Reply-To: <200401251714.57799.eric@cisu.net>
References: <4013D0AA.8060906@blueyonder.co.uk>
	<16404.8968.349900.566999@gargle.gargle.HOWL>
	<4014283D.9040207@blueyonder.co.uk>
	<200401251714.57799.eric@cisu.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 902
Lines: 26

Eric <eric@cisu.net> wrote:
>
> 	I am now having this problem. See the thread "Kernels > 2.6.1-mm3 do not 
>  boot." I had a kernel that would hang after uncompressing. Seems that gcc 3.3 
>  generates bad code w/ -funit-at-a-time. Now I get the test_wp_bit oops w/ 
>  kernel version 2.6.2-rc2-mm2.
>  	Since I have already commented out the line.. and it led to this oops, what 
>  the heck is the real problem here?
>  	Seems alot of other SMP systems are breaking with this too.

Pretty simple:

init/main.c does

	mem_init();
	kmem_cache_init();
	sort_main_extable();

but mem_init() calls test_wp_bit().  The exception tables haven't been
sorted yet.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/