Date: Thu, 12 Nov 2009 17:56:38 -0900 From: Royce Williams <royce.williams@gmail.com> To: Jeremy Chadwick <freebsd@jdc.parodius.com>, Jack Vogel <jfvogel@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: 82573 xfers pause, no watchdog timeouts, DCGDIS ineffective (7.2-R) Message-ID: <9dd082310911121856te64bc71x5cad46199d38f53e@mail.gmail.com> In-Reply-To: <9dd082310911121518l24adaa23jdb41ff567374d11c@mail.gmail.com> References: <4AFC63B0.5020707@alaska.net> <20091112204736.GA29095@icarus.home.lan> <9dd082310911121518l24adaa23jdb41ff567374d11c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 12, 2009 at 2:18 PM, Royce Williams <royce.williams@gmail.com> wrote: > On Thu, Nov 12, 2009 at 11:47 AM, Jeremy Chadwick >> - All machines connected to an HP ProCurve 2626 switch (100mbit, >> =A0full-duplex ports, all autoneg). > No firewall is active on the problem system, and none of this back > have been DCGDIS-ified, but otherwise, our setup is identical. Er, s/back/batch/g, and it's not a ProCurve. ;-) But we are also usually full-duplex and autoneg on both sides. Based on new (embarrassing) information, I'll leave it to Jack to decide whether or not he wants to pursue this further. The problem box is sitting in my grotty mini-lab, with a subnet partially serviced by a 10M hub. Guess which Ethernet cable I picked up. Guess what happens when I move the system to a 100M/full connection. As my cow-orker put it, "You and the other four people on Earth using that NIC on 10M hubs" can probably find workarounds. My apologies for the noise, though it's theoretically possible that the root cause might still need addressing. Jack, let me know if you want me to do any testing for you. Or I can always send you my hub. ;-) Royce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9dd082310911121856te64bc71x5cad46199d38f53e>