New alpha 5.x bug
Wilko Bulte
wkb at freebie.xs4all.nl
Tue Nov 4 14:18:32 PST 2003
On Tue, Nov 04, 2003 at 11:12:51PM +0100, Bernd Walter wrote:
> On Tue, Nov 04, 2003 at 09:55:52AM -0800, Kris Kennaway wrote:
> > On Tue, Nov 04, 2003 at 01:48:27PM +0100, Bernd Walter wrote:
> > > I can't speak for this problem yet, because my test systems are a bit
> > > older, but speaking for the pipe corruption:
> > > I did a lots of bzip1, tar, scp, nfs(client) without noticing any
> > > sign of problem.
> > > What is so special with the port cluster?
> > > I have no clue about it's design.
> >
> > It does lots of parallel package builds (untar, pkg_add, compile, tar) and NFS copying.
>
> Any special NFS options?
> tcp, udp, v2, v3, IPv4, IPv6?
>
> Just to get the picture complete.
> The build is local and the package is then copied to a NFS server on
> which t has a corrupted CRC?
> Is the bzip2 CRC wrong, or the tar CRC (does tar have a CRC?), or both?
> Can you say how likely such a corruption is?
> Are other packages compiled during copying a package file to the server?
> Are the building machines memory stressed while creating the bz file or
> while copying it?
Hmmm.. the package builders are Miatas right?
Are they using a PCI add-in ethernet card?
I'm thinking of the Miata's rather fragile DMA stuff in the Pyxis
core logic chip.
W/
--
| / o / /_ _ wilko at FreeBSD.org
|/|/ / / /( (_) Bulte
More information about the freebsd-alpha
mailing list