Date: Tue, 25 Jan 2005 09:59:25 -0200
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: "Povolotsky, Alexander" <Alexander.Povolotsky@marconi.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: 8xx 2.6.10-rc3 console_init()->con_init()->__alloc_bootmem() caus es "Oops: kernel access of bad area"
Message-ID: <20050125115925.GC19585@logos.cnet>
References: <313680C9A886D511A06000204840E1CF0A64758D@whq-msgusr-02.pit.comms.marconi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <313680C9A886D511A06000204840E1CF0A64758D@whq-msgusr-02.pit.comms.marconi.com>
User-Agent: Mutt/1.5.5.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1091
Lines: 31

On Tue, Jan 25, 2005 at 09:30:49AM -0500, Povolotsky, Alexander wrote:
> I booting kernel on 8xx 2.6.10-rc3
> while trying to debug non-working console,
> I moved  console_init() call way down in __init start_kernel()
> and put indefinite while loop right after it -
> is it legtimate thing to do ?
> 
> Then I got soft reboot and was able to examine the content of the log buffer
> in the bootloader.
> I see that in a trace (function call sequence):
> 
> console_init()->con_init()->__alloc_bootmem() 
> 
> I am getting "Oops: kernel access of bad area"
> 
> I am looking for advise,

Hi Alexander,

I recommend using the linuxppc-2.5 BK tree for 8xx. Are you doing that?

The linuxppc-embedded list is a better place for discussion of such issues.

And about your problem, you need to get the full oops message, not only the 
beginning of it.

-
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/