Re: NSLU2 seems to work again, no more checksum weirdness

[Andy Ruhl <acruhl%gmail.com@localhost>]

On Sun, Jul 5, 2009 at 9:43 PM, Andy Ruhl<acruhl%gmail.com@localhost> wrote:
>
> It would be really nice to know what changed to fix the CPU problem.
>
> Anyone know?

Well, I may have run into problems again. Although this only showed up
since I had to switch the NFS server from my Cobalt to my Mobilepro
880, so I'm really not sure what's going on here:

===> Building for digest-20080510
cc -DHAVE_CONFIG_H -I. -I. -DHOST=\"armeb--netbsd\"
-DVERSION=\"20080510\"  -O2 -c digest.c -o digest.o
cc -DHAVE_CONFIG_H -I. -I. -DHOST=\"armeb--netbsd\"
-DVERSION=\"20080510\"  -O2 -c md5c.c -o md5c.o
cc -DHAVE_CONFIG_H -I. -I. -DHOST=\"armeb--netbsd\"
-DVERSION=\"20080510\"  -O2 -c rmd160.c -o rmd160.o
cc -DHAVE_CONFIG_H -I. -I. -DHOST=\"armeb--netbsd\"
-DVERSION=\"20080510\"  -O2 -c rmd160hl.c -o rmd160hl.o
cc -DHAVE_CONFIG_H -I. -I. -DHOST=\"armeb--netbsd\"
-DVERSION=\"20080510\"  -O2 -c sha2.c -o sha2.o
cc -DHAVE_CONFIG_H -I. -I. -DHOST=\"armeb--netbsd\"
-DVERSION=\"20080510\"  -O2 -c sha2hl.c -o sha2hl.o
cc -DHAVE_CONFIG_H -I. -I. -DHOST=\"armeb--netbsd\"
-DVERSION=\"20080510\"  -O2 -c md5hl.c -o md5hl.o
cc -DHAVE_CONFIG_H -I. -I. -DHOST=\"armeb--netbsd\"
-DVERSION=\"20080510\"  -O2 -c sha1.c -o sha1.o
cc -DHAVE_CONFIG_H -I. -I. -DHOST=\"armeb--netbsd\"
-DVERSION=\"20080510\"  -O2 -c sha1hl.c -o sha1hl.o
cc -DHAVE_CONFIG_H -I. -I. -DHOST=\"armeb--netbsd\"
-DVERSION=\"20080510\"  -O2 -c tiger.c -o tiger.o
cc -DHAVE_CONFIG_H -I. -I. -DHOST=\"armeb--netbsd\"
-DVERSION=\"20080510\"  -O2 -c whirlpool.c -o whirlpool.o
whirlpool.c: In function 'whirlpool_end':
whirlpool.c:1637: internal compiler error: Bus error
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.NetBSD.org/Misc/send-pr.html> for instructions.

This seems either CPU or compiler related I guess.

Note that I'm not having checksum problems anymore though. And I
successfully built this package just a few days ago when I was using
my "normal" NFS/DHCP/TFTP server to boot the NSLU2. Very weird.

I'll try some stuff to see what I can come up with.

If anyone has any suggestions, this would be great.

Andy