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--
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...
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"),
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 t
"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
