On 9/28/12 11:02 PM, Hooman Fazaeli wrote:
On 9/27/2012 9:38 PM, Rudy wrote:
On 09/27/2012 11:00 AM, Rudy wrote:
Rebooting and/or the settings change seems to have stopped the errors.
Here is a pretty little graph showing error rate on em1 for the past 3
days.
http://www.monkeybrains.net/i
On 9/27/2012 9:38 PM, Rudy wrote:
On 09/27/2012 11:00 AM, Rudy wrote:
Rebooting and/or the settings change seems to have stopped the errors.
Here is a pretty little graph showing error rate on em1 for the past 3
days.
http://www.monkeybrains.net/images/ErrorRate-em1.png
Interesting... if
On 09/27/2012 11:00 AM, Rudy wrote:
Rebooting and/or the settings change seems to have stopped the errors.
Here is a pretty little graph showing error rate on em1 for the past 3
days.
http://www.monkeybrains.net/images/ErrorRate-em1.png
Interesting... if I zoom in on the graph, I see the er
On 09/27/2012 11:00 AM, Rudy wrote:
On 09/25/2012 01:37 AM, Hooman Fazaeli wrote:
dev.em.1.link_irq: 6379725883
dev.em.2.link_irq: 6379294926
Based on the strangely high value of dev.em.1.link_irq (which means too
many link
status changes: down -> up -> down -> ), I guess the problem
On 09/25/2012 01:37 AM, Hooman Fazaeli wrote:
dev.em.1.link_irq: 6379725883
dev.em.2.link_irq: 6379294926
Based on the strangely high value of dev.em.1.link_irq (which means too
many link
status changes: down -> up -> down -> ), I guess the problem is the
same as
discussed in these th
On 9/25/2012 11:08 AM, Rudy (bulk) wrote:
On 9/24/12 11:52 PM, Hooman Fazaeli wrote:
sysctl dev.em.1
From the side having the 'No buffer space available' (FreeBSD 8.3 Sep 13 2012)
# sysctl dev.em.1
dev.em.1.%desc: Intel(R) PRO/1000 Network Connection 7.3.2
dev.em.1.%driver: em
dev.em.1.%lo
On 9/25/2012 11:08 AM, Rudy (bulk) wrote:
On 9/24/12 11:52 PM, Hooman Fazaeli wrote:
sysctl dev.em.1
From the side having the 'No buffer space available' (FreeBSD 8.3 Sep 13 2012)
# sysctl dev.em.1
dev.em.1.%desc: Intel(R) PRO/1000 Network Connection 7.3.2
dev.em.1.%driver: em
dev.em.1.%lo
On Sep 25, 2012, at 12:38 AM, "Rudy (bulk)" wrote:
> On 9/24/12 11:52 PM, Hooman Fazaeli wrote:
>> sysctl dev.em.1
>
> From the side having the 'No buffer space available' (FreeBSD 8.3 Sep 13
> 2012)
>
> # sysctl dev.em.1
> dev.em.1.%desc: Intel(R) PRO/1000 Network Connection 7.3.2
> dev.em.
On 9/24/12 11:52 PM, Hooman Fazaeli wrote:
sysctl dev.em.1
From the side having the 'No buffer space available' (FreeBSD 8.3 Sep
13 2012)
# sysctl dev.em.1
dev.em.1.%desc: Intel(R) PRO/1000 Network Connection 7.3.2
dev.em.1.%driver: em
dev.em.1.%location: slot=0 function=0
dev.em.1.%pnpinfo
On 9/24/2012 7:50 PM, Rudy (bulk) wrote:
Sometimes when I try to ping a neighbor machine (plugged directly in with no
switch involved), I get:
ping: sendto: No buffer space available
ping: sendto: No buffer space available
If I reset the interface 'ifconfig em1 down; ifconfig em1 up' the pr
On Mon, Sep 24, 2012 at 8:06 PM, Rudy (bulk) wrote:
> On 9/24/12 5:01 PM, Ryan Stone wrote:
>>
>> Can you get the output of netstat -I emX -d?
>
> ...
>
>>
>> I suspect that you are seeing the em TX queue fill up. If so you
>> should see output drops reported by the em interface.
>>
> I do see 20
On 9/24/12 8:49 PM, Erich Dollansky wrote:
Hi,
On Mon, 24 Sep 2012 20:06:22 -0700
"Rudy (bulk)" wrote:
Checking all the interfaces, there are a lot more drops/Ierrs on
em2... The igb devices (PCIe card) seem a lot better than the
Supermicro motherboard em devices. Is this an on-board vs mb t
Hi,
On Mon, 24 Sep 2012 20:06:22 -0700
"Rudy (bulk)" wrote:
> Checking all the interfaces, there are a lot more drops/Ierrs on
> em2... The igb devices (PCIe card) seem a lot better than the
> Supermicro motherboard em devices. Is this an on-board vs mb thing,
> or em vs igb thing?
>
I do not
On 9/24/12 5:01 PM, Ryan Stone wrote:
Can you get the output of netstat -I emX -d?
...
I suspect that you are seeing the em TX queue fill up. If so you
should see output drops reported by the em interface.
I do see 205 in the 'Drop' column. I ran the command twice two hours
apart... I am s
Can you get the output of netstat -I emX -d? You don't need to run
that when the problem is happening -- you just need to run it on the
machine after it exhibits the issue without any reboots in the
interim.
I suspect that you are seeing the em TX queue fill up. If so you
should see output drops
Здравствуйте, Rudy.
check routing table and show which IP you ping.
Вы писали 24 сентября 2012 г., 19:20:28:
Rb> Sometimes when I try to ping a neighbor machine (plugged directly in
Rb> with no switch involved), I get:
Rb> ping: sendto: No buffer space available
Rb> ping: sendto: No buffer sp
16 matches
Mail list logo