From owner-freebsd-current@FreeBSD.ORG  Tue Oct 26 03:30:50 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 D5DF216A4CE
	for <current@freebsd.org>; Tue, 26 Oct 2004 03:30:50 +0000 (GMT)
Received: from harmony.village.org (rover.village.org [168.103.84.182])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 747BB43D1F
	for <current@freebsd.org>; Tue, 26 Oct 2004 03:30:50 +0000 (GMT)
	(envelope-from imp@bsdimp.com)
Received: from localhost (harmony.village.org [10.0.0.6])
	by harmony.village.org (8.13.1/8.13.1) with ESMTP id i9Q3RnbV041282;
	Mon, 25 Oct 2004 21:27:49 -0600 (MDT)
	(envelope-from imp@bsdimp.com)
Date: Mon, 25 Oct 2004 21:28:20 -0600 (MDT)
Message-Id: <20041025.212820.60925870.imp@bsdimp.com>
To: vova@fbsd.ru
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <1098564131.1064.3.camel@localhost>
References: <1098564131.1064.3.camel@localhost>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: current@freebsd.org
Subject: Re: fxp does not work after upgrade to latest current
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Oct 2004 03:30:50 -0000

In message: <1098564131.1064.3.camel@localhost>
            Vladimir Grebenschikov <vova@fbsd.ru> writes:
: 
: After upgrade to latest current fxp driver didn't work:
: 
: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
: fxp0: DMA timeout
: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
: fxp0: DMA timeout
: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
: fxp0: DMA timeout
: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
: fxp0: device timeout
: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
: fxp0: DMA timeout
: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
: fxp0: DMA timeout
: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
: fxp0: DMA timeout
: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
: fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
: 
: any clues ?
: 
: With about week-old kernel all is ok.

Uggg.  Maybe this is due to the address that is assigned to it.  I'm
having horrible luck with your machine, no?

Warner