new em-driver still broken

Jack Vogel jfvogel at gmail.com
Tue Oct 31 18:50:19 UTC 2006


On 10/31/06, Mikhail Teterin <mi+mx at aldan.algebra.com> wrote:
> понеділок 30 жовтень 2006 23:23, Mikhail Teterin написав:
> > Ok. I rebooted and restarted the heavy traffic dump (DEVICE_POLLING in
> > kernel, but without polling actialy enabled). The dump got underway,
> > although the amount of "sys" load was rather high -- way above 70%
> > most of the time (on a dual-CPU machine).
> >
> > Then I tried to enable polling. The following command worked fine:
> >
> > (ifconfig em0 down; sleep 1; ifconfig em0 polling; sleep 1; ifconfig em0
> > up) &
> >
> > Traffic resumed a couple of second later...
> >
> > A minute later, ALL TRAFFIC stopped. The machine is, again, unreachable
> > via network...
> >
> > Conclusion: The only way to have a working em-interface is to compile
> > with DEVICE_POLLING, but without polling enabled... It is slow (very CPU
> > intensive), but it seems to work...
>
> FWIW, enabling polling at boot (via rc.conf) does not change anything
> either...

Scott's question still hasnt been answered, or if so I dont understand it.
If everything was working why were you trying to turn on polling?

And if the machine is unreachable over the net, what is happening ON
the machine at that point, does it emit any useful information?

Jack


More information about the freebsd-stable mailing list