From owner-freebsd-bugs@FreeBSD.ORG Fri Apr 18 12:40:14 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28C7837B401 for ; Fri, 18 Apr 2003 12:40:14 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2C5943FCB for ; Fri, 18 Apr 2003 12:40:13 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h3IJeDUp018525 for ; Fri, 18 Apr 2003 12:40:13 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h3IJeDne018524; Fri, 18 Apr 2003 12:40:13 -0700 (PDT) Date: Fri, 18 Apr 2003 12:40:13 -0700 (PDT) Message-Id: <200304181940.h3IJeDne018524@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Gary Hanson Subject: Re: i386/40274: "fxp: device timeout" errors during heavy,sustained network activity X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Gary Hanson List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Apr 2003 19:40:14 -0000 The following reply was made to PR i386/40274; it has been noted by GNATS. From: Gary Hanson To: freebsd-gnats-submit@FreeBSD.org, seagull@aracnet.com Cc: Subject: Re: i386/40274: "fxp: device timeout" errors during heavy, sustained network activity Date: Fri, 18 Apr 2003 12:33:53 -0700 (PDT) Also seen on 4.8-RELEASE and 5.0-RELEASE; very easy and quick to reproduce. System is an Intel N440BX dual proc mobo with integrated 82557 (Pro100B) NIC on a dedicated IRQ. On SMP kernels, I could ping for as long as I wanted to, even with large (64000 byte) packets. Didn't try flood ping though. But try to do some real I/O like an ftp or Samba file copy and the transfer would die almost immediately and the console would start reporting fxp: device timeout messages every few seconds, even after disconnecting the ethernet cable. The system was then in a very weird state; it was acting like it was very busy (sluggish) but wasn't totally unresponsive, and it could not be shutdown properly - that would seem to hang (or I wasn't willing to wait long enough). With a single-processor kernel, 4.8 and 5.0 both had no problems. The hardware is good; it works fine with SMP OSes from Redmond; I'll try a penguin 'OS' for amusement purposes. [The penguin 'e100' driver is vastly better than the rather old FreeBSD fxp driver, but I'm not competent to adapt/port/steal it.]