Date: Thu, 04 Dec 1997 11:56:30 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: current@FreeBSD.ORG Subject: Re: weird current behaviour... Message-ID: <8233.881232990@critter.freebsd.dk> In-Reply-To: Your message of "Thu, 04 Dec 1997 11:23:17 %2B0100." <8106.881230997@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
More data... If I don't run the two rc564 processes, then this phenomena goes away. I still don't understand why I see it on the de0 but not on the fxp0 or en0 interface... Poul-Henning In message <8106.881230997@critter.freebsd.dk>, Poul-Henning Kamp writes: > >Network: > > machine-A en0 ------------ en0 machine-B > de0 fxp0 > | \ > | ----------------- de0 machine-C > | > hub ----- machine-D > | > | > ed0 > machine-E > > >These two cases: > >1. ping from A to E >2. ping from A to D > >I see the round-trip time flutter from 9msec to 70 msec... > >Every other path the round-trip time is OK, including confusingly >enough: > > from E to A > from D to A > from B&C to E > from B&C to D > >What gives ? > >Is the if_de driver broken somehow ? > >Does anybody else see this ? > >Machine-A is a PR440FX motherboard with 2xP6/233 running current-SMP. > >I have tried two different de0 cards and both does this. > >-- >Poul-Henning Kamp FreeBSD coreteam member >phk@FreeBSD.ORG "Real hackers run -current on their laptop." > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8233.881232990>