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] [day] [month] [year] [list]
Date:	Sun, 08 Jun 2008 12:04:58 +1000
From:	Ben Nizette <bn@...sdigital.com>
To:	Luke -Jr <luke@...hjr.org>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: bcm33xx port


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ