Skip to contentSkip to conversation

Xilinx board and NPTL support lockup

DISCUSSION khollan 3 participants 3 messages Apr 8, 2009 – Apr 9, 2009

lore
Share & tools
lore

khollan

author
#0 lore raw

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

Signature · 2 lines
View this message in context: http://www.nabble.com/Xilinx-board-and-NPTL-support-lockup-tp22960621p22960621.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.
#1 lore raw

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

Quoted 17 lines · khollan

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

Signature · 8 lines
------------------------------------------------------------------------

John Bonesio
Commercial Linux Solutions
[email protected]
(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.
#2 lore raw

Thanks for your help.

This was a kernel setup issue, I had forgotten to strip the debug informati= on 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 l= ink/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 [[email protected]]
Sent: Thursday, April 09, 2009 11:50 AM
To: Kevin Holland
Cc: [email protected]
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

Quoted 3 lines · khollan

Hi everyone,

I have a board similar to the ml410, its been running a linux kernel happ=

ily

Quoted 1 line

for about a year now, but now the firmware guys want NPTL threading inste=

ad

Quoted 2 lines

of the linuxthread library.
I recompiled my gcc 4.0.2 and glibc 2.3.6 library with the NPTL support, =

and

Quoted 3 lines

recompiled my kernel with the new tools.

Now my kernel gets stuck at the infamous "Now Booting the Kernel" message=

.

Quoted 2 lines

Any thoughts on why this might be happening, or how to verify that my gli=

bc

Quoted 1 line

and gcc are functional other than trying to compile things with them (I k=

now

Quoted 5 lines

this works).

Thanks
Kevin

--
------------------------------------------------------------------------

John Bonesio
Commercial Linux Solutions
[email protected]
(408) 879-5569

This email and any attachments are intended for the sole use of the named r= ecipient(s) and contain(s) confidential information that may be proprietary= , privileged or copyrighted under applicable law. If you are not the intend= ed recipient, do not read, copy, or forward this email message or any attac= hments. Delete this email message and any attachments immediately.