Re: Panic on fxp
On Thu, Apr 03, 2003 at 04:10:04PM -0500, Robin P. Blanchard wrote: > # ls -ltr /usr/src/sys/dev/fxp/ > total 116 > -rw-r--r-- 1 root wheel 21318 Oct 25 2001 rcvbundl.h > -rw-r--r-- 1 root wheel 8190 Apr 2 13:00 if_fxpvar.h > -rw-r--r-- 1 root wheel 73326 Apr 3 11:46 if_fxp.c > -rw-r--r-- 1 root wheel 12975 Apr 3 15:14 if_fxpreg.h "fgrep '$FreeBSD' *fxp*" would be more useful. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Panic on fxp
I'm seeing the same thing. A kernel from first thing this morning paniced the kernel whilst attempting to probe the device. I saw a commit go in shortly after 15.00 and rebuilt the kernel. Kernel built on that commit allows the box to boot, but the device simply doesn't pass (or see) any traffic...Reverted back to a working kernel from 10March. # ls -ltr /usr/src/sys/dev/fxp/ total 116 -rw-r--r-- 1 root wheel 21318 Oct 25 2001 rcvbundl.h -rw-r--r-- 1 root wheel 8190 Apr 2 13:00 if_fxpvar.h -rw-r--r-- 1 root wheel 73326 Apr 3 11:46 if_fxp.c -rw-r--r-- 1 root wheel 12975 Apr 3 15:14 if_fxpreg.h 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? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic on fxp
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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic on fxp
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. -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Outros: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] No wonder you're tired! You understood so much today. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic on fxp
"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? Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
