From owner-freebsd-alpha Fri Jul 14 14:23:35 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 902FC37C755; Fri, 14 Jul 2000 14:23:30 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA27764; Fri, 14 Jul 2000 17:23:22 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id RAA35266; Fri, 14 Jul 2000 17:23:22 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 14 Jul 2000 17:23:21 -0400 (EDT) To: dg@root.com Cc: mjacob@feral.com, David Greenman , Mike Smith , Bernd Walter , freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE In-Reply-To: <200007141908.MAA17583@implode.root.com> References: <14703.24005.384580.704375@grasshopper.cs.duke.edu> <200007141908.MAA17583@implode.root.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14703.31808.282545.767536@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David Greenman writes: > >David: Is the fxp module unloadable, or will it crash the machine in > >strange and mysterious ways upon unload, like most of the network > >drivers do? > It looks like its close to being unloadable, but it somehow clobers the intr. of a device sharing the same irq. I'm not at all sure that's the fxp driver's fault. Let's not worry about that for now. As for the bug. I can duplicate it I run both the sender & receiver fairly hard, like 2 100Mb/tcp connections running in opposite directions. When I do this, it looks like the xmit side locks up but the recv. side is at least partially OK. And I'm still getting stats updates. From looking at the fxp stats in a debugger, it looks like its still getting packets (fxp_stats.rx_good is non-zero if I throw packets at the box). There are no collisions, ierrors, underruns, or anything else that looks at all suspicious. Just 128 packets waiting on tx_queued. If I call fxp_intr() from ddb, there's no improvement. I can bring the interface back by running tcpdump. At the top of fxp_stats_update(), you have a comment regarding how expensive it is to get "_all_ of the statistics it maintains" Does sc->fxp_stats include all of them, or are there others that might shed some light on the problem? Do any of the symptoms sound familiar? Also, are there any docs on this thing that are available? I've searched intel's web site & cannot seem to find anything.. Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message