Date: Fri, 09 May 2003 12:52:55 +0900 (JST) From: Hiroki Sato <hrs@eos.ocn.ne.jp> To: truckman@FreeBSD.org Cc: matt@hasta.se Subject: Re: NFS problem? Message-ID: <20030509.125255.41630543.hrs@eos.ocn.ne.jp> In-Reply-To: <200305081923.h48JNNM7035986@gw.catspoiler.org> References: <IIEBLFJCECCIAJIHMKNPOEOICAAA.matt@hasta.se> <200305081923.h48JNNM7035986@gw.catspoiler.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Don Lewis <truckman@FreeBSD.org> wrote in <200305081923.h48JNNM7035986@gw.catspoiler.org>: truckman> ping -c 216 truckman> ping -c 1696 truckman> ping -c 3176 truckman> ping -c 4656 Yes, I use dc on the server and fxp on the client. I tried: ping -s 214 ... OK ping -s 216 ... no response (truncated-ip appeared) ping -s 300 ... OK ping -s 1694 ... OK ping -s 1696 ... no response (truncated-ip appeared) ping -s 3174 ... OK ping -s 3176 ... no response (truncated-ip appeared) ping -s 4654 ... OK ping -s 4656 ... no response (truncated-ip appeared) ping -s 6134 ... OK ping -s 6136 ... no response (truncated-ip appeared) The result of "pciconf -l" is: fxp0@pci7:2:0: class=0x020000 card=0x10508086 chip=0x12298086 rev=0x0d hdr=0x00 I guess this is FXP_REV_82550_C. After your patch is applied, the problem does not seem to occur! I will see how things go for a little while. Thank you for your suggestion. -- | Hiroki SATO <hrs@eos.ocn.ne.jp> / <hrs@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030509.125255.41630543.hrs>