Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 04 Dec 1997 12:41:45 +0100
From:      Poul-Henning Kamp <phk@critter.freebsd.dk>
To:        sos@FreeBSD.dk
Cc:        current@FreeBSD.ORG
Subject:   Re: weird current behaviour... 
Message-ID:  <8332.881235705@critter.freebsd.dk>
In-Reply-To: Your message of "Thu, 04 Dec 1997 12:40:20 %2B0100." <199712041140.MAA05101@sos.freebsd.dk> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <199712041140.MAA05101@sos.freebsd.dk>, Søren Schmidt writes:
>In reply to Poul-Henning Kamp who wrote:
>> 
>> 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...
>
>The de? driver could be heavily CPU bound maybe ??
>
>The problem goes away if you use another driver/card combo, yes ?

It doesn't happen on the en0 or fxp0 interfaces, and it also doesn't
happen for traffic on the de0 that stays in the kernel (ie: gets
routed through to another interface...)

--
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?8332.881235705>