From owner-freebsd-current@FreeBSD.ORG Sat Aug 7 10:17:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6ED1416A4CE for ; Sat, 7 Aug 2004 10:17:48 +0000 (GMT) Received: from lakermmtao04.cox.net (lakermmtao04.cox.net [68.230.240.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEA5643D2F for ; Sat, 7 Aug 2004 10:17:47 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao04.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP id <20040807101747.YLOC9099.lakermmtao04.cox.net@dolphin.local.net>; Sat, 7 Aug 2004 06:17:47 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with ESMTP id i77AHkCl000818; Sat, 7 Aug 2004 05:17:46 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.13.1/8.13.1/Submit) id i77AHkOf000817; Sat, 7 Aug 2004 05:17:46 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20040806214351.Y14680@volatile.chemikals.org> Date: Sat, 07 Aug 2004 05:17:46 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: Wesley Morgan cc: current@freebsd.org Subject: Re: fxp problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: conrads@cox.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Aug 2004 10:17:48 -0000 On 07-Aug-2004 Wesley Morgan wrote: > I've got a box running 5.2.1-R p8 that has several times caught > itself in > a fit of errors on both fxp devices, alternating between the two. A > little > searching through PR's shows it reported back in 2003 and possibly > again > in 2004, but always on -stable. Some posts to -stable seem to think > it's > an interaction with the PCI and SCSI layers, but I'm not sure if this > applies to -current. Anyone have any experience with these type of > errors? > I've got the kernel conf and dmesg attached. > > > Aug 6 00:00:14 tiamat kernel: fxp1: device timeout > Aug 6 00:00:14 tiamat kernel: fxp1: SCB timeout: 0xff 0xff 0xff > 0xffff > Aug 6 00:00:14 tiamat kernel: fxp1: DMA timeout > Aug 6 00:00:14 tiamat kernel: fxp1: SCB timeout: 0xff 0xff 0xff > 0xffff > Aug 6 00:00:14 tiamat kernel: fxp1: DMA timeout > Aug 6 00:00:14 tiamat kernel: fxp1: SCB timeout: 0xff 0xff 0xff > 0xffff > Aug 6 00:00:14 tiamat kernel: fxp1: DMA timeout > Aug 6 00:00:14 tiamat kernel: fxp1: SCB timeout: 0xff 0xff 0xff > 0xffff > Aug 6 00:00:14 tiamat kernel: fxp1: SCB timeout: 0xff 0xff 0xff > 0xffff > > Aug 6 00:00:29 tiamat kernel: fxp0: device timeout > Aug 6 00:00:29 tiamat kernel: fxp0: SCB timeout: 0xff 0xff 0xff > 0xffff > Aug 6 00:00:29 tiamat kernel: fxp0: DMA timeout > Aug 6 00:00:29 tiamat kernel: fxp0: SCB timeout: 0xff 0xff 0xff > 0xffff > Aug 6 00:00:29 tiamat kernel: fxp0: DMA timeout > Aug 6 00:00:29 tiamat kernel: fxp0: SCB timeout: 0xff 0xff 0xff > 0xffff > Aug 6 00:00:29 tiamat kernel: fxp0: DMA timeout > Aug 6 00:00:29 tiamat kernel: fxp0: SCB timeout: 0xff 0xff 0xff > 0xffff > Aug 6 00:00:29 tiamat kernel: fxp0: SCB timeout: 0xff 0xff 0xff > 0xffff > Aug 6 00:00:29 tiamat kernel: fxp1: SCB timeout: 0xff 0xff 0xff > 0xffff I recently tried running an SMP kernel here, even though my box is UP, as a temporary workaround for the broken state of UP kernel builds on amd64. When I did, I experienced the fxp timeouts. When I finally got a UP kernel to build again, the fxp problem went away. Perhaps there's a clue there. :-) -- Conrad J. Sabatier -- "In Unix veritas"