Re: Strange Lag with 3.2

[John Eisenschmidt <jweisen_(_at_)_eisenschmidt_(_dot_)_org>]

Rumor has it that Marco Peereboom (slash_(_at_)_peereboom_(_dot_)_us) said:
> I use 3 e100b without any problems on my firewall.
>
> dmesg excerpt:
> fxp0 at pci1 dev 9 function 0 "Intel 82557" rev 0x05: irq 11, address
> 00:90:27:45:f8:ad
> inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 0
> fxp1 at pci1 dev 10 function 0 "Intel 82557" rev 0x05: irq 10, address
> 00:a0:c9:d5:e2:61
> inphy1 at fxp1 phy 1: i82555 10/100 media interface, rev. 0
> fxp2 at pci1 dev 11 function 0 "Intel 82557" rev 0x05: irq 10, address
> 00:90:27:62:0d:96
> inphy2 at fxp2 phy 1: i82555 10/100 media interface, rev. 0
>
> As a matter of fact I basically only use intel NIC's and I have no
> problems whatsoever. In my opinion they are the most solid NIC's out
> there.

Which is why they are/were all I used, until this. My 2.9 box had 2 in
there without a problem.

> Did you check your network cables and devices?

It all seems fine.

> Are you sure it is not something else in the box that is messed up?

As far as I can tell, yes. With the exception of the 2 new 120GB
drives (which I've had running for three weeks) all the hardware had
been in service at least a year without any problems. I really hope
it's something I screwed up, and I really thought it was an interrupt
problem, but since I eliminated that this is the only thing I've come
up with, and I'm baffled. I don't know if it is the interraction
between raidframe and pf, but I can recreate the behavior after
disabling pf. The only combination I've come up with that doesn't
cause this problem is no Intel NIC on the inside.

--
John W. Eisenschmidt (jweisen_(_at_)_eisenschmidt_(_dot_)_org)
  http://www.eisenschmidt.org/jweisen/pgp.html

"If God were cheese, would we still worship on Sundays?"

[demime 0.98d removed an attachment of type application/pgp-signature]