From owner-freebsd-current@FreeBSD.ORG  Fri Jun 27 06:29:02 2003
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 D3A6537B405; Fri, 27 Jun 2003 06:29:02 -0700 (PDT)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 056244400D; Fri, 27 Jun 2003 06:28:58 -0700 (PDT)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (localhost [127.0.0.1])
	by fledge.watson.org (8.12.9/8.12.9) with ESMTP id h5RDSWKJ072473;
	Fri, 27 Jun 2003 09:28:32 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)h5RDSWFE072470;
	Fri, 27 Jun 2003 09:28:32 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Date: Fri, 27 Jun 2003 09:28:31 -0400 (EDT)
From: Robert Watson <rwatson@FreeBSD.org>
X-Sender: robert@fledge.watson.org
To: Ying-Chieh Liao <ijliao@FreeBSD.org>
In-Reply-To: <20030627052728.GA1015@terry.dragon2.net>
Message-ID: <Pine.NEB.3.96L.1030627092756.72040C-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-net@FreeBSD.org
cc: freebsd-current@FreeBSD.org
Subject: Re: something wrong with fxp driver ?
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: Fri, 27 Jun 2003 13:29:03 -0000

You might compare the dmesg output from before/after and see if there are
any obvious changes in IRQ allocation, shared interrupts, etc.  Perhaps
the changes in interrupt routing have resulted in some new behavior.

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org      Network Associates Laboratories

On Fri, 27 Jun 2003, Ying-Chieh Liao wrote:

> my previous kernel is about May 10, and the fxp works fine for me
> but I cvsuped and make world/kernel yesterday (6/26), and then terrible thing
> happens... the connection becomes v...e...r...y... s...l...o...w...
> my ping time to the gateway is about 8000ms (but sometimes 20ms)
> 
> I've browse the mail archive of -current and -net, and I've noticed some
> similar problems with fxp (device timeout), and I also get this message
> (fxp0 device timeout) in my dmesg output, but I cant find out any solution :<
> Is there any workaround, or patches ?
> -- 
> char*p="char*p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
> 					-- Anonymous
>