mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ben Nizette <bn@niasdigital.com>
To: Luke -Jr <luke@dashjr.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: bcm33xx port
Date: Sun, 08 Jun 2008 12:04:58 +1000	[thread overview]
Message-ID: <1212890698.4089.17.camel@moss.renham> (raw)
In-Reply-To: <200806072019.42108.luke@dashjr.org>


On Sat, 2008-06-07 at 20:19 -0500, Luke -Jr wrote:
> I am working on a port for the bcm33xx platform, which includes a MIPS CPU:
> 	http://wiki.openwrt.org/BroadcomBCM33xxPort
> 
> However, I seem to be hitting problems with memory allocation, as 
> load_elf_binary is segfaulting inside padzero/__bzero.

Seems to have issues way before that ;-)

> 
> This is my first attempt at real Linux kernel development, so if anyone could 
> throw me pointers on how I would approach debugging and fixing this problem, 
> I'd really appreciate it. (boot log with early printk is attached)

I'm not too up on MIPS but there're a few things in the log which stand
out to me:

Determined physical RAM map:
 memory: 00fa0000 @ 00000000 (usable)
User-defined physical RAM map:
 memory: 007a1200 @ 00000000 (usable)

Can you confirm these sizes and locations for RAM?  Does anything change
if you don't force the size constraint?

CPU frequency 32.00 MHz

Really?  Is your bootloader setting the CPU up correctly before handing
control to Linux?

irq 8: nobody cared (try booting with the "irqpoll" option)

What's on IRQ8, should anyone care at this early stage?  Did the
bootloader enable this (should it)?

Reserved instruction in kernel code[#1]:

You're compiling with an appropriate -march switch?

Good luck :-)
	--Ben.

  reply	other threads:[~2008-06-08  2:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-08  1:19 Luke -Jr
2008-06-08  2:04 ` Ben Nizette [this message]
2008-06-08  2:13 Luke -Jr
2008-06-08  3:19 ` Maciej W. Rozycki
2008-06-08  4:32   ` Luke -Jr
2008-06-08 12:53     ` Maciej W. Rozycki
2008-06-08 18:56       ` Luke -Jr
2008-06-08 19:53         ` Kevin D. Kissell
2008-06-08 20:14           ` Maciej W. Rozycki
2008-06-08 20:20           ` Luke -Jr
2008-06-08 19:59         ` Maciej W. Rozycki
2008-06-08 20:27           ` Luke -Jr
2008-06-08 22:13             ` Maciej W. Rozycki
2008-06-08 23:36               ` Luke -Jr
2008-06-09  6:40                 ` Geert Uytterhoeven
2008-06-09  6:05               ` Luke -Jr

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=1212890698.4089.17.camel@moss.renham \
    --to=bn@niasdigital.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@dashjr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome