Date: Thu, 3 Apr 2003 23:09:50 +0200 From: Maxime Henrion <mux@freebsd.org> To: "Daniel C. Sobral" <dcs@tcoip.com.br> Cc: current@freebsd.org Subject: Re: Panic on fxp Message-ID: <20030403210950.GN1750@elvis.mu.org> In-Reply-To: <3E8CA248.7010000@tcoip.com.br> References: <20030403210214.519B42A8A5@canning.wemm.org> <3E8CA248.7010000@tcoip.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030403210950.GN1750>