On Fri, 14 Jan 2011, Chuck Swiger wrote:
On Jan 14, 2011, at 2:12 AM, Bruce Evans wrote:
On a good day, my MUA sends "Content-type: text/plain; format=flowed" and
should contain line breaks following the 80-character-per-line Usenet conventions, which
modern MUAs might well reassemble based u
Thanks for all the feedback on polling, Jack and others. Very helpful.
We are working to merge the latest RELENG_8 em/igb driver into our
custom build that's based on RELENG_8_1. I've been able to create a
patch using the following command:
cvs di -N -up -jRELENG_8_1 -jRELENG_8 sys/dev/e100
On Jan 14, 2011, at 2:12 AM, Bruce Evans wrote:
>> On a good day, my MUA sends "Content-type: text/plain; format=flowed" and
>> should contain line breaks following the 80-character-per-line Usenet
>> conventions, which modern MUAs might well reassemble based upon the user's
>> window size. If i
> > I have a couple of servers with Broadcom (bge) GigE interfaces. These
> > servers became completely unresponsive/unusable at high network traffic
> > (presumably due to the interrupt processing) but were able to handle the
> > same traffic with no problems after switching to polling. This was i
On Thu, 13 Jan 2011, Chuck Swiger wrote:
On Jan 13, 2011, at 8:54 PM, Bruce Evans wrote:
To quote an earlier post:
"Polling mode operation generally performs better when using older 100Mbs ethernet
NICs which do not support interrupt mitigation and various capabilities like TSO4;
gigabit eth
On Fri, 14 Jan 2011 sth...@nethelp.no wrote:
They have enough buffers (128 for each of tx and rx IIRC). The only thing
polling mode gave for them was lower latency, but this cost enabling
polling in the idle loop, which wastes 100% of at least 1 CPU and some
power. Without polling in idle, pol
> > They have enough buffers (128 for each of tx and rx IIRC). The only thing
> > polling mode gave for them was lower latency, but this cost enabling
> > polling in the idle loop, which wastes 100% of at least 1 CPU and some
> > power. Without polling in idle, polling gives very high latency (ev
On Thu, 13 Jan 2011, Chuck Swiger wrote:
On Jan 13, 2011, at 1:42 PM, Charles Owens wrote:
This is very good news overall, in that we can certainly disable polling for
igb. This begs the question, though, as to whether polling is recommended
these days at all for em/igb NICs... or even in ge
On Jan 13, 2011, at 8:54 PM, Bruce Evans wrote:
>> To quote an earlier post:
>>
>> "Polling mode operation generally performs better when using older 100Mbs
>> ethernet NICs which do not support interrupt mitigation and various
>> capabilities like TSO4; gigabit ethernet NICs are smarter hardwar
On Thu, 13 Jan 2011, Jack Vogel wrote:
Polling has seemed to me to be a way around other problems, problems that
these days
no longer exist. I remember back in the FreeBSD 6 days having interrupt
problems which
of course also led to watchdogs. Polling got rid of that. But now there are
dedicated
Polling has seemed to me to be a way around other problems, problems that
these days
no longer exist. I remember back in the FreeBSD 6 days having interrupt
problems which
of course also led to watchdogs. Polling got rid of that. But now there are
dedicated
MULTIPLE interrupts by using MSIX, so tha
On Jan 13, 2011, at 1:42 PM, Charles Owens wrote:
> This is very good news overall, in that we can certainly disable polling for
> igb. This begs the question, though, as to whether polling is recommended
> these days at all for em/igb NICs... or even in general. From other
> conversations we'
So we went back to basics (stock 8.1-RELEASE) and found no issue!We
then added in our kernel mods one by one and ultimately discovered that
device-polling is the culprit (the kernel config was simply GENERIC +
PAE + polling).
Immediately upon running "ifconfig igb0 polling" the symptoms ap
The 8.2 latest does have the latest igb, so using that should be
indicative...
Jack
On Thu, Jan 13, 2011 at 7:56 AM, Charles Owens
wrote:
> Ok... I got my wires crossed: our first time testing 8.1 on this
> particular platform was with a kernel that had ichwd enabled (a new thing
> for us) an
Ok... I got my wires crossed: our first time testing 8.1 on this
particular platform was with a kernel that had ichwd enabled (a new
thing for us) and so when igb started complaining about "watchdog" we
thought it was related.
We've tested again and clearly the real story is that we're simply
The problem that Robin saw was due to having MSIX interrupts disabled on the
system, I doubt that
is going to be the "issue" for others.
Get the latest version of the igb code and see if that helps you as a first
step.
Jack
On Wed, Jan 12, 2011 at 6:43 PM, Charles Owens
wrote:
> I'd like to re
I'd like to report that we're running into this issue also, in our case
on systems that are based on the Intel S5520UR Server Board, running
8.1-RELEASE. If the ichwd driver is loaded we see the same messages,
and network communication via the igb nics is non-functional.
Have you had any luck
I don't suppose you have ASPM enabled? If so, turn it off. That seemed
to make things go much better here at Yahoo.
Sean
I can get in to the data center later this week and check the BIOS. I
can't control that from freebsd, can I? I may as well build a new
kernel as long as I am re
On Mon, 2011-01-03 at 13:02 -0800, Robin Sommer wrote:
> Hello all,
>
> quite a while ago I asked about the problem below. Unfortunately, I
> haven't found a solution yet and I'm actually still seeing these
> timeouts after just upgrading to 8.2-RC1. Any further ideas on what
> could be triggering
I get them as well... on my em devices. I was just thinking of
upgrading to a dual port igb I have kicking around, but your email is
not encouraging. :)
# grep watchdog /var/log/message
Jan 2 21:13:38 turtle kernel: em5: watchdog timeout -- resetting
Jan 3 04:31:37 turtle kernel: em4: watch
Hello all,
quite a while ago I asked about the problem below. Unfortunately, I
haven't found a solution yet and I'm actually still seeing these
timeouts after just upgrading to 8.2-RC1. Any further ideas on what
could be triggering them, or how I could track down the cause?
Thanks,
Robin
On Thu
Mike Tancsa (m...@sentex.net) [10.07.30 20:25] wrote:
>
> Try using the tools in /usr/src/tools/tools/netrate
>
> you can generate a lot more traffic this way.
>
thank you Mike,
it works! :)
netsend 10.11.0.2 5 1000 20 60
Sending packet of payload size 1000 every 0.05000s for 60
At 12:52 PM 7/30/2010, Zeus V Panchenko wrote:
but the maximum i was able to get was 500Mbit/s
btw, is it correct to test it such way?
Try using the tools in /usr/src/tools/tools/netrate
you can generate a lot more traffic this way.
---Mike
--
Zeus V. Panchenko
IT Dpt., IBS ltd
Robin Sommer (ro...@icir.org) [10.07.30 18:38] wrote:
> I'm going to try the driver from 8-STABLE, as suggested by Jack
> (thanks!), but for the record, I've already updated the BIOS and I'm
> still seeing the timeouts.
just have CVS-ed to RELENG_8, recompiled the kernel and loaded the
drivers em
On Fri, Jul 30, 2010 at 08:35 +0300, Zeus V Panchenko wrote:
> the same was for me untill i upgraded BIOS up to the latest one
> available from the MB vendor site
I'm going to try the driver from 8-STABLE, as suggested by Jack
(thanks!), but for the record, I've already updated the BIOS and I'm
> Steve
>
> - Original Message -
> *From:* Jack Vogel
> *To:* Steven Hartland
> *Cc:* Robin Sommer ; freebsd-net
> *Sent:* Friday, July 30, 2010 4:47 AM
> *Subject:* Re: igb watchdog timeouts
>
> Try the code from STABLE/8 or HEAD if you would please, if you hav
Just the changes in sys/dev/e1000 required or are there any other dependencies?
Regards
Steve
- Original Message -
From: Jack Vogel
To: Steven Hartland
Cc: Robin Sommer ; freebsd-net
Sent: Friday, July 30, 2010 4:47 AM
Subject: Re: igb watchdog timeouts
Try the
Hi,
the same was for me untill i upgraded BIOS up to the latest one
available from the MB vendor site
i run: FreeBSD 8.1-RELEASE amd64
on: Base Board Information
Manufacturer: Supermicro
Product Name: X8SIL-F
Version: 0123456789
BIOS Information
Vendor: Amer
Try the code from STABLE/8 or HEAD if you would please, if you have
questions
of what or how let me know.
Jack
On Thu, Jul 29, 2010 at 3:48 PM, Steven Hartland wrote:
> Seeing a similar thing here, if we can help diagnose let us know.
>
> Regards
> Steve
> - Original Message - From:
Seeing a similar thing here, if we can help diagnose let us know.
Regards
Steve
- Original Message -
From: "Robin Sommer"
To: "freebsd-net"
Sent: Thursday, July 29, 2010 10:56 PM
Subject: igb watchdog timeouts
Since upgrading from 8.0 to 8.1-RELEASE, I'm seeing lots of messag
30 matches
Mail list logo
