On 11/13/2010 09:08 PM, Jack Vogel wrote:
The stats changed quite a bit for 8.1, they are much more informative now,
and they can be collected from anywhere not just the console.
I don't quite understand what you are trying to do, debug an em problem
or just debug a problematic situation by us
The stats changed quite a bit for 8.1, they are much more informative now,
and they can be collected from anywhere not just the console.
I don't quite understand what you are trying to do, debug an em problem
or just debug a problematic situation by using em??
Mike is right, the driver in HEAD ha
On 11/13/2010 9:35 PM, Patrick Mahan wrote:
>
>
> On 11/13/2010 02:27 PM, Ryan Stone wrote:
>> It looks to me that you're getting a ton of input drops. That's
>> presumably the cause of your issue. You can get the em driver to
>> print debug information to the console by running:
>>
>> # sysctl
On 11/13/2010 02:27 PM, Ryan Stone wrote:
It looks to me that you're getting a ton of input drops. That's
presumably the cause of your issue. You can get the em driver to
print debug information to the console by running:
# sysctl dev.em.3.stats=1
# sysctl.dev.em.3.debug=1
The output should
It looks to me that you're getting a ton of input drops. That's
presumably the cause of your issue. You can get the em driver to
print debug information to the console by running:
# sysctl dev.em.3.stats=1
# sysctl.dev.em.3.debug=1
The output should be available in dmesg and /var/log/messages
Good afternoon,
I am trying to run down a root cause of a link failure between two of my
HP Proliant DL350's. pciconf shows them as the 82571EB chip. These are
a 4 port card on the HP.
We are doing some routing code in the kernel and have a call to our entry
function in the forwarding path in
