> The strange thing is that it  also happens on a totally quiet ethernet.
> The 'pattern' I'm seeing in that case is something like this:
> 
> qe0: ring overrun, resync'd by skipping 1
> qe0: ring overrun, resync'd by skipping 2
> qe0: ring overrun, resync'd by skipping 4
> qe0: ring overrun, resync'd by skipping 5
> qe0: ring overrun, resync'd by skipping 9
> qe0: ring overrun, resync'd by skipping 10 
> .
> .
> .
> 
> As if something is not keeping track of some buffer-pointer..
> 
> Wild guess based on _no_ factual code knowledge here! Feel free
> to beat me senseless for spouting nonsense..

Likewise. The exact number skipped differs from time to time, but it
always looks like an ascending series of numbers. The highest I've seen is
14 I think.

I was thinking that it might have something to do with SQL, or possibly
what transciever you are using.

	Johnny

Johnny Billquist                  || "I'm on a bus
                                  ||  on a psychedelic trip
email: bqt@update.uu.se           ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol