From owner-freebsd-current  Thu Dec  4 03:43:53 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id DAA14361
          for current-outgoing; Thu, 4 Dec 1997 03:43:53 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA14354
          for <current@FreeBSD.ORG>; Thu, 4 Dec 1997 03:43:45 -0800 (PST)
          (envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1])
	by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id MAA08334;
	Thu, 4 Dec 1997 12:41:45 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: sos@FreeBSD.dk
cc: current@FreeBSD.ORG
Subject: Re: weird current behaviour... 
In-reply-to: Your message of "Thu, 04 Dec 1997 12:40:20 +0100."
             <199712041140.MAA05101@sos.freebsd.dk> 
Date: Thu, 04 Dec 1997 12:41:45 +0100
Message-ID: <8332.881235705@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

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."