Re: [microblaze-uclinux] Boot issues on XUPV5-LX110T

[John Williams <john.williams@xxxxxxxxxxxxx>]

Hi Dana,

On Wed, Aug 26, 2009 at 4:32 AM, Dana Goyette<dgoyette@xxxxxxxxxxx> wrote:
> I've been having all sorts of issues trying to bring up a kernel from
> Michael Simek's linux-2.6-microblaze branch, using simpleImage format, on
> the XUPV5-LX110T board; for now, I am attempting the noMMU version, because
> I'd imagine that's simpler.

Which toolchain are you using to build the petaLogix git tree?  And
what about your userland - how are you building that?

> Now that I've built the system with uartlite for
> early printk, I get the following in my console on boot:
>
> early_printk_console is enabled at 0x84000000
>
> Ramdisk addr 0x00000fff, Compiled-in FDT at 0x10ae1300
>
> <board hangs here.>

This is an unfortunate side effect of how the kernel handles the
log_buf - if it dies before initialising the serial console, the log
messages stay in the buffer.

> <6>[    0.000000]  ERROR: Mismatch in kind-of-intr param

This shouldn't be here.

> <6>[    0.000000] xlnx,xps-intc-1.00.a #0 at 0x81800000, num_irq=9,
> edge=0xb0001080
> <4>[    0.000000] PID hash table entries: 1024 (order: 10, 4096 bytes)
> <6>[    0.000000] xlnx,xps-timer-1.00.a #0 at 0x83c00000, irq=0
> <5>[    0.000000] Heartbeat GPIO at 0x81400000
> <6>[    0.000000] microblaze_timer_set_mode: shutdown
> <6>[    0.000000] microblaze_timer_set_mode: periodic
> <6>[    0.008000] Dentry cache hash table entries: 32768 (order: 5,
> 131072 bytes)
> <6>[    0.068000] Inode-cache hash table entries: 16384 (order: 4, 65536
> bytes)
> <6>[    0.838000] Memory: 255876k/262144k available
> <3>[    0.860000] kfree_debugcheck: out of range ptr 1f8016c4h.
> <4>[    0.860000] BUG: failure at mm/slab.c:2855/kfree_debugcheck()!

I've not seen this before - have you checked the referenced source
line?  What is the BUG() condition?

> <0>[    0.860000] Kernel panic - not syncing: BUG!
> <0>[    0.860000] Rebooting in 120 seconds..
>
> I've run into this same issue before, when manually loading the dtb file
> into memory and storing the address in R7.  Is the odd memory address
> (kernel starts at 0x1080_0000) the cause of this, perhaps?

Keep things as simple as possible until you figure out the details -
placing the kernel at a nice round base address would be a good idea.

> I've also had a huge number of compilation issues with Petalinux from SVN...
> tons of missing symbols ("oobblock" in mtdutils, should be "writesize"),
> implicitly declared functions (see attached log), and missing include
> statements (such as stdlib).

Are you referring to the kernel tree (2.6.2) within PetaLinux?  Or the
distribution generally?

I've not seen anything like this - we build these trees on a daily
basis.  Something strange about your local setup perhaps?

> I seem to be having more trouble than I had expected, when trying to bring
> this board up.  Am I just unlucky, or am I doing something wrong?

I think it's a combination of unlucky and doing something wrong.  We
build this stuff all the time, as do many others.

Regards,

John
-- 
John Williams, PhD, B.Eng, B.IT
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com  p: +61-7-30090663  f: +61-7-30090663

___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/