em0 watchdog timeouts

[Rudy]

Ah, I'll stop messing with them. 


I just set them all to 0 to see if that will help and noticed the card
was leaving tx_int_delay=1.

# sysctl dev.em.4.debug=1
Oct  2 13:26:07 mango kernel: em4: tx_int_delay = 1, tx_abs_int_delay = 0
Oct  2 13:26:07 mango kernel: em4: rx_int_delay = 0, rx_abs_int_delay = 0

# sysctl dev.em.4
dev.em.4.%desc: Intel(R) PRO/1000 Network Connection 6.9.12
dev.em.4.rx_int_delay: 0
dev.em.4.tx_int_delay: 0
dev.em.4.rx_abs_int_delay: 0
dev.em.4.tx_abs_int_delay: 0

Splitting traffic to different ports has brought down the watchdog
events to once a day.  ... essentially, I have a quad 30Mbps (not quad
1Gbps) card.  heheh.
Would turning off net.inet.ip.fastforwarding or any other setting help?

Today, I set net.inet.ip.fw.enable=0 and I'll see if that helps.  I have
a feeling that isn't related to the NIC at all, but I'm not sure what
else to try.

Rudy



Jack Vogel wrote:
> Watchdog resets the adapter. Messing with these values is of dubious value
> anyway.
>
> Jack
>
>
> On Fri, Oct 2, 2009 at 11:36 AM, Rudy <crapsh at monkeybrains.net> wrote:
>
>   
>> I noticed something interesting.
>>
>> I set the rc_int_delay to 0:
>>  sysctl dev.em.5.rx_int_delay=0
>>
>> Chcking via sysctl dev.em.5.debug=1 shows ex_int_delay is indeed 0:
>>  Oct  1 17:32:41 mango kernel: em5: rx_int_delay = 0, rx_abs_int_delay = 66
>>
>> After a watchdog event, sysctl dev.em.5.debug=1 shows ex_int_delay is
>> now 32:
>>  Oct  2 11:29:49 mango kernel: em5: rx_int_delay = 32, rx_abs_int_delay =
>> 66
>>
>> However, running sysctl dev.em.5 shows it as 0:
>> dev.em.5.rx_int_delay: 0
>> dev.em.5.tx_int_delay: 66
>>
>> Seems like the adapter and the kernel don't agree on the rx_int_delay
>> value.
>>
>> Rudy
>>
>>     
>
>