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"
Date: Tue, 25 Jan 2005 09:59:25 -0200 [thread overview]
Message-ID: <20050125115925.GC19585@logos.cnet> (raw)
In-Reply-To: <313680C9A886D511A06000204840E1CF0A64758D@whq-msgusr-02.pit.comms.marconi.com>
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.
prev parent reply other threads:[~2005-01-25 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 14:30 8xx 2.6.10-rc3 console_init()->con_init()->__alloc_bootmem() caus es "Oops: kernel access of bad area" Povolotsky, Alexander
2005-01-25 11:59 ` Marcelo Tosatti [this message]
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=20050125115925.GC19585@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=Alexander.Povolotsky@marconi.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.