Date: Thu, 3 Apr 2003 16:10:04 -0500 From: "Robin P. Blanchard" <Robin.Blanchard@gactr.uga.edu> To: <current@freebsd.org> Subject: RE: Panic on fxp Message-ID: <EE3D3FBAFFCAED448C21C398FDAD91AC044284@EBE1.gc.nat>
next in thread | raw e-mail | index | archive | help
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: >=20 >>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=20 >>don't *know* it's fxp fault (for one thing, because it says = "unknown"),=20 >>but... >> >>So, two hours ago, I cvsupped and tried a new world. This one panics=20 >>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=20 >>get >>it fixed? >=20 >=20 > Some details would be useful. Pencil and paper perhaps? Serial cable = > to another machine and boot -h?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EE3D3FBAFFCAED448C21C398FDAD91AC044284>