From owner-freebsd-current@FreeBSD.ORG  Thu Apr  3 13:09:51 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 3C84637B401
	for <current@freebsd.org>; Thu,  3 Apr 2003 13:09:51 -0800 (PST)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.FreeBSD.org (Postfix) with ESMTP id BCB5E43F93
	for <current@freebsd.org>; Thu,  3 Apr 2003 13:09:50 -0800 (PST)
	(envelope-from mux@freebsd.org)
Received: by elvis.mu.org (Postfix, from userid 1920)
	id 9DEE02ED40E; Thu,  3 Apr 2003 13:09:50 -0800 (PST)
Date: Thu, 3 Apr 2003 23:09:50 +0200
From: Maxime Henrion <mux@freebsd.org>
To: "Daniel C. Sobral" <dcs@tcoip.com.br>
Message-ID: <20030403210950.GN1750@elvis.mu.org>
References: <20030403210214.519B42A8A5@canning.wemm.org>
	<3E8CA248.7010000@tcoip.com.br>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3E8CA248.7010000@tcoip.com.br>
User-Agent: Mutt/1.4.1i
cc: current@freebsd.org
Subject: Re: Panic on fxp
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: Thu, 03 Apr 2003 21:09:51 -0000

Daniel C. Sobral wrote:
> Peter Wemm wrote:
> >"Daniel C. Sobral" wrote:
> >
> >>It seems recent current doesn't like my fxp. A current from some 10 
> >>hours ago keeps complaining about device timeout and dma timeout. I 
> >>don't *know* it's fxp fault (for one thing, because it says "unknown"), 
> >>but...
> >>
> >>So, two hours ago, I cvsupped and tried a new world. This one panics on 
> >>boot, while doing something with fxp (attaching, I think), and doesn't 
> >>even get me a core dump.
> >>
> >>I'll try a new world tomorrow. People tweaking fxp, do please try to get 
> >>it fixed?
> >
> >
> >Some details would be useful.  Pencil and paper perhaps?  Serial cable
> >to another machine and boot -h?
> 
> I'll have to see if I can manage a serial cable here. It shouldn't be 
> difficult, I just have never done it before, let alone on this computer, 
> so I don't know what traps I might fall into.
> 
> If not that, I'll get at least the functions and the offset of the first 
> few. But not today. Tomorrow, after a new cvsup and a new world. I see 
> there were at least two commits to fxp since my last cvsup.

This should be fixed in revision 1.30 of if_fxpreg.h that I committed
recently.  Sorry for that guys.

Cheers,
Maxime