Replying to myself... I made the cardinal sin of not including a uname -a... The system in question is: FreeBSD bling.home 6.0-CURRENT FreeBSD 6.0-CURRENT #1: Sat Sep 11 18:31:59 EDT 2004 root_at_bling.home:/usr/CURRENT/sys/i386/compile/BLING i386 I have a fresh dmesg up at http://bling.properkernel.com/dmesg.boot.txt and a boot -v at http://bling.properkernel.com/boot-v.txt Andy | Andre Guibert de Bruet | Enterprise Software Consultant > | Silicon Landmark, LLC. | http://siliconlandmark.com/ > On Sat, 11 Sep 2004, Andre Guibert de Bruet wrote: > Anyone have any ideas on this one? > > # cvsupdate [...] > Updating collection src-all/cvs > TreeList failed: Network write failure: ChannelMux.ProtocolError > Will retry at 18:43:42 > ^C > > The machine in question is a dual Athlon with a custom SMP kernel config > which can be found at http://bling.properkernel.com/BLING . Reverting to > GENERIC does _not_ fix the problem. The interface in question is an > nge-compatible 64-bit Linksys card detected as: > > nge0_at_pci0:8:0: class=0x020000 card=0x10641737 chip=0x0022100b rev=0x00 > hdr=0x00 > vendor = 'National Semiconductor' > device = 'DP83820/1 10/100/1000 Gigabit Ethernet Adapter' > class = network > subclass = ethernet > > I've also noticed data corruption in the form of failed CRCs (And hence > dropped SSH connections) while transferring large amounts of data via SSH > over gige to a machine on its subnet. These problems started occuring after > the giant-less networking megacommit. Older kernels check out without any > such issues. > > Additional information on the system can be found online: > pciconf -vl: http://bling.properkernel.com/pciconf-vl.txt > kernel config: http://bling.properkernel.com/BLING > old dmesg (Can be updated): http://bling.properkernel.com/dmesg.boot.txtReceived on Sun Sep 12 2004 - 04:42:09 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:11 UTC