From owner-freebsd-current@FreeBSD.ORG  Mon Apr  7 10:45:35 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 2863837B401
	for <freebsd-current@freebsd.org>;
	Mon,  7 Apr 2003 10:45:35 -0700 (PDT)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.FreeBSD.org (Postfix) with ESMTP id AB19143FD7
	for <freebsd-current@freebsd.org>;
	Mon,  7 Apr 2003 10:45:32 -0700 (PDT)	(envelope-from mux@freebsd.org)
Received: by elvis.mu.org (Postfix, from userid 1920)
	id 8B19D2ED43E; Mon,  7 Apr 2003 10:45:32 -0700 (PDT)
Date: Mon, 7 Apr 2003 19:45:32 +0200
From: Maxime Henrion <mux@freebsd.org>
To: freebsd-current@freebsd.org
Message-ID: <20030407174532.GC1750@elvis.mu.org>
References: <20030407170504.GA1099@leafy.idv.tw>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030407170504.GA1099@leafy.idv.tw>
User-Agent: Mutt/1.4.1i
Subject: Re: recent fxp changes causes mpd to freeze
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: Mon, 07 Apr 2003 17:45:35 -0000

leafy wrote:
> Recent (in these couple of days) changes in fxp causes mpd with PPPoE to freeze. No message or anything. Restarting mpd unfreezes the condition. Is there anything I can do to get more information out of this situation?

Can you check that you're running the latest version of the fxp(4)
driver ?  Latest revsisions are :

if_fxp.c:
     $FreeBSD: src/sys/dev/fxp/if_fxp.c,v 1.162 2003/04/07 17:02:44 mux Exp $
if_fxpreg.h:
     $FreeBSD: src/sys/dev/fxp/if_fxpreg.h,v 1.33 2003/04/06 21:35:45 mux Exp $
if_fxpvar.h:
     $FreeBSD: src/sys/dev/fxp/if_fxpvar.h,v 1.24 2003/04/02 16:47:16 mux Exp $
rcvbundl.h:
     $FreeBSD: src/sys/dev/fxp/rcvbundl.h,v 1.1 2001/10/25 05:23:31 jlemon Exp $


Are you using the DEVICE_POLLING kernel option ?  If so, your problem
may be already fixed.

Cheers,
Maxime