Date: Sat, 5 Apr 2003 02:24:44 +0200 From: Maxime Henrion <mux@freebsd.org> To: "Robin P. Blanchard" <Robin.Blanchard@gactr.uga.edu> Cc: current@freebsd.org Subject: HEADS UP: fxp breakage Message-ID: <20030405002444.GR1750@elvis.mu.org> In-Reply-To: <EE3D3FBAFFCAED448C21C398FDAD91AC0107DF@EBE1.gc.nat> References: <EE3D3FBAFFCAED448C21C398FDAD91AC0107DF@EBE1.gc.nat>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi all, Robin P. Blanchard wrote: > Following sources still yield unresponsive fxp interface. The same behavious > occurs on both of my test boxes (dell 4350 and home-grown athlon xp), each > having identical Intel Pro 100+M nics with v4.1.0.9 intel PXE rom. > > # fgrep -h \*\ \$FreeBSD /usr/src/sys/dev/fxp/* > > * $FreeBSD: src/sys/dev/fxp/if_fxp.c,v 1.154 2003/04/03 20:39:43 mux Exp $ > * $FreeBSD: src/sys/dev/fxp/if_fxpreg.h,v 1.30 2003/04/03 18:39:48 mux Exp $ > * $FreeBSD: src/sys/dev/fxp/if_fxpvar.h,v 1.24 2003/04/02 16:47:16 mux Exp $ > * $FreeBSD: src/sys/dev/fxp/rcvbundl.h,v 1.1 2001/10/25 05:23:31 jlemon Exp > $ Could everyone which has problems with the fxp(4) driver mail me some informations ? I'd need the exact symptoms, the output of ifconfig on the interface, the part of pciconf -lv relevant to your fxp card, your kernel configuration file and the output of dmesg. That would be help me a lot to understand what's going on, since I can't reproduce these problems on any of my fxp(4) cards. Since this is a commonly used driver in the FreeBSD community, I've put a kernel module for fxp online, built with the sources prior to the busdma commit. It's at http://people.freebsd.org/~mux/if_fxp.ko.gz. > Reverting back to kernel sources from 11 April yield functional interface. 11 April ? Did you make a typo ? Thanks, Maxime
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030405002444.GR1750>