Xilinx board and NPTL support lockup
Kevin Holland
Kevin.Holland at daktronics.com
Fri Apr 10 03:04:08 EST 2009
Thanks for your help.
This was a kernel setup issue, I had forgotten to strip the debug information out of my new libraries and my initramfs was too large.
I believe the zImage was decompressing onto itself, thats why it was stuck at the "now booting." I probably could have fixed it by changing my boot link/load address in the kernel config but I just stripped the files and it booted fine after it was smaller.
Hope this helps out anybody else with similar problems.
Kevin
________________________________________
From: John Bonesio [john.bonesio at xilinx.com]
Sent: Thursday, April 09, 2009 11:50 AM
To: Kevin Holland
Cc: linuxppc-dev at ozlabs.org
Subject: Re: Xilinx board and NPTL support lockup
Hi Kevin,
This doesn't look like an NPTL problem to me. It appears you have
rebuilt the kernel, and your new kernel has a problem booting on the
board. I would check the configuration options you have enabled in the
kernel, and I would check that xparameters.h (older kernel) or the
device-tree (newer kernel) is right for your hardware design.
If you haven't rebuilt the kernel, then I would check your setup.
- John
khollan wrote:
> Hi everyone,
>
> I have a board similar to the ml410, its been running a linux kernel happily
> for about a year now, but now the firmware guys want NPTL threading instead
> of the linuxthread library.
> I recompiled my gcc 4.0.2 and glibc 2.3.6 library with the NPTL support, and
> recompiled my kernel with the new tools.
>
> Now my kernel gets stuck at the infamous "Now Booting the Kernel" message.
>
> Any thoughts on why this might be happening, or how to verify that my glibc
> and gcc are functional other than trying to compile things with them (I know
> this works).
>
> Thanks
> Kevin
>
--
------------------------------------------------------------------------
John Bonesio
Commercial Linux Solutions
john.bonesio at xilinx.com
(408) 879-5569
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
More information about the Linuxppc-dev
mailing list