On 7/7/2011 11:49 AM, Thibaut VARENE wrote:
I have no problem with this, the only "active" user of the rp3440 is
Aurélien, so I suppose it wouldn't be a problem. Yet, my understanding
is that the rp3440 is extremely slow at building anything (much slower
than my other machines, it seems) because of the cache flush issues.
AIUI that's why Debian stuck to J6700 for buildds, because those
machines were a lot faster.
The rp3440 isn't bad for non trivial compilations. At -j4, my 800 MHz
rp3440 is the fastest
machine that I have for building GCC. It stumbles running the testsuite
where it falls behind
my c3750. The cache flush problem slows forks. If this could be
resolved, the machine
could handle significantly larger loads than the J6700.
Other than that, the rp3440 currently runs unstable with 2.6.22.19, so
I suppose a complete reinstall would be in order, and I'm not sure I
have time to deal with that just yet. I'd be happy to provide remote
access to the machine though, if someone steps up. FWIW, the only
machine I have left running lenny is a J5000, 2x440MHz PA8500,
previously used as an autobuilder for debian-multimedia.org.
The kernel on the rp3440 needs updating. 2.6.22.19 is not stable under
load. To do this,
remote access to the console would be needed. Many bugs have been fixed
since
2.6.22.19, and I think many packages may not test successfully without
updating the
kernel and build environment.
I have done this manually on my rp3440 for quite a few packages.
Dave
--
John David Anglin dave.anglin@xxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
