On Nov 30, 2006, at 10:06 PM, Mike Tancsa wrote:

> wm0   1500  <Link>        00:15:17:0b:70:98 32226898 281780        
> 15     0     0

That's still a lot of input errors.

There are a few reasons for these to accumulate:

- Receive ring overrun.  Unfortunately, the log message for this is  
wrapped in #ifdef WM_DEBUG, so you'll need to tweak the driver and  
rebuild the kernel to see the log message.

- Failure to allocate a new receive buffer.  When this happens, the  
received packet is dropped the its buffer recycled.  Again,  
unfortunately, this has a debug-only kernel printf associated with it.

- The chip reported some sort of error with the packet.  It logs  
messages in system log for the following:

   - symbol error
   - receive sequence error
   - CRC error

A carrier extension error or a Rx data error could also occur, but  
these are not logged.

-- thorpej