On Thu, Jun 17, 2010 at 08:12:01PM +0800, wu zhangjin wrote:
> The Email you replied is too old, the basic 2F support have been
> merged into the mainline 2.6.33 and the related workaround of the 2F's
> bug have been pushed into mainline 2.6.34.
> The latest Loongson support have been moved to
Yeah, I did notice the email I was replying to was a year old ...
*after* I hit the send button. I'll blame it on a long day at work and
leave it at that. ;-)
The link there is good to know, and I'll check it out.
> Back to your problem with FuLoong 2E, before, nobody have reported the
> hard-lock of It, If you want to check whether 2E has a hardware bug, I
> think you can try to check the NOP issue at first for 2F has such an
> To check the issue, you can download the fix-nop.c from the
> attachments of http://dev.lemote.com/code/linux-loongson-community and
> use it to replace the original NOPS of the ld and as by something
> $ make fix-nop
> $ fix-nop $(which as)
> $ fix-nop $(which ld)
> Then recompile python 2.6 with the new tools, if you have used the
> other tools, please use fix-nop on them too.
That fix-nop might be the ticket to solving this issue, we shall see.
It's been an issue for a while with various packages... if I try to
compile some package, most of the time it's okay, but every so often
I'll hit one which will hang the computer.
Compiling qucs on the Yeeloong under its stock Debian OS was one I found
that did it. Python 2.6.5 on my newly cross-compiled chroot is doing
the same on this Fulong 2E. One can never know if a package is going to
cause problems, but when it does, it's 100% repeatable; the computer
always fails compiling exactly the same file.
Something that repeatable does not sound like faulty RAM which is the
usual culprit for such problems. ;-)
Stuart Longland (aka Redhatter, VK4MSL) .'''.
Gentoo Linux/MIPS Cobalt and Docs Developer '.'` :
. . . . . . . . . . . . . . . . . . . . . . .'.'
I haven't lost my mind...
...it's backed up on a tape somewhere.