something wrong with fxp driver ?

[Robert Watson]

You might compare the dmesg output from before/after and see if there are
any obvious changes in IRQ allocation, shared interrupts, etc.  Perhaps
the changes in interrupt routing have resulted in some new behavior.

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert at fledge.watson.org      Network Associates Laboratories

On Fri, 27 Jun 2003, Ying-Chieh Liao wrote:

> my previous kernel is about May 10, and the fxp works fine for me
> but I cvsuped and make world/kernel yesterday (6/26), and then terrible thing
> happens... the connection becomes v...e...r...y... s...l...o...w...
> my ping time to the gateway is about 8000ms (but sometimes 20ms)
> 
> I've browse the mail archive of -current and -net, and I've noticed some
> similar problems with fxp (device timeout), and I also get this message
> (fxp0 device timeout) in my dmesg output, but I cant find out any solution :<
> Is there any workaround, or patches ?
> -- 
> char*p="char*p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
> 					-- Anonymous
>