Re: Via-Rhine NIC, Via SATA or reiserfs broken, how to tell??

[Masoud Sharbiani <masouds@masoud.ir>]

Can you turn on UDP checksums and try again? That would isolate the 
fault between the network or SATA.
cheers,
Masoud
Grant Coady wrote:

> On Fri, 12 Aug 2005 14:43:42 +0400, "Vladimir V. Saveliev" <vs@namesys.com> wrote:
>  
>
> > > How to test and isolate this error is in NIC driver, SATA driver or 
> > > filesystem?  
> > >
> > >      
> > Could it be that tarbal on NFS server changed?
> > It is not very likely that error in kernel drivers fixed typos in source code.
> >    
>
> The 'typos' are the observed errors from extracting kernel source tarball, 
> renaming top level directory and extracting tarball again.  Other times 
> extraction fails with corrupt tarball error.  Cached image of tarball is 
> corrupted as box doesn't go back to server.
>
> Since first report I've changed to using ext2 target filesystem, still get 
> errors, so not reiserfs specific either.  
>
> Am in process of reducing options in kernel config, try to narrow down 
> what problem is.  Nothing in logs, me have no idea ... yet.  
>
> Not a memory error as box compiled many hundred kernels last week without 
> choking.  Test just now was with 2.6.13-rc6-git3, very repeatable.
>
> Same test on different box, no errors.  Other box has pro/100 NIC, 
> reiserfs, unpack tarball from same server.  Never a problem.
>
> Cheers,
> Grant.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
>  


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/