From owner-freebsd-current  Thu Dec  4 03:40:47 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id DAA14146
          for current-outgoing; Thu, 4 Dec 1997 03:40:47 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA14141
          for <current@FreeBSD.ORG>; Thu, 4 Dec 1997 03:40:42 -0800 (PST)
          (envelope-from sos@sos.freebsd.dk)
Received: (from sos@localhost)
	by sos.freebsd.dk (8.8.8/8.8.8) id MAA05101;
	Thu, 4 Dec 1997 12:40:20 +0100 (MET)
	(envelope-from sos)
Message-Id: <199712041140.MAA05101@sos.freebsd.dk>
Subject: Re: weird current behaviour...
In-Reply-To: <8233.881232990@critter.freebsd.dk> from Poul-Henning Kamp at "Dec 4, 97 11:56:30 am"
To: phk@critter.freebsd.dk (Poul-Henning Kamp)
Date: Thu, 4 Dec 1997 12:40:20 +0100 (MET)
Cc: current@FreeBSD.ORG
From: Søren Schmidt <sos@FreeBSD.dk>
Reply-to: sos@FreeBSD.dk
X-Mailer: ELM [version 2.4ME+ PL30 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

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 ?

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt               (sos@FreeBSD.org)               FreeBSD Core Team
                Even more code to hack -- will it ever end
..