Date: Wed, 05 May 2004 13:31:29 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@DeepCore.dk> To: Pawel Jakub Dawidek <pjd@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: em(4) problems. Message-ID: <4098D091.5020507@DeepCore.dk> In-Reply-To: <20040505105034.GN24376@darkness.comp.waw.pl> References: <20040505104248.GM24376@darkness.comp.waw.pl> <20040505105034.GN24376@darkness.comp.waw.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
Pawel Jakub Dawidek wrote: > On Wed, May 05, 2004 at 12:42:48PM +0200, Pawel Jakub Dawidek wrote: > +> Hi. > +> > +> I've problems with em(4) and IPSEC/FAST_IPSEC and TCP_STREAM netperf test. > +> While running netperf tests between two FreeBSD machines directly connected > +> em0 goes down once every few minutes and I've no idea why. > +> Without IPSEC everything works just fine, with IPSEC/FAST_IPSEC it also > +> works fine but for other tests (UDP_STREAM, TCP_RR, UDP_RR). For what its worth I have problems with one em based interface as well, it locks the machine solid when used: em0: <Intel(R) PRO/1000 Network Connection, Version - 1.7.25> port 0xb000-0xb01f mem 0xfb100000-0xfb11ffff irq 10 at device 1.0 on pci1 em0: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xfb100000 em0: Reserved 0x20 bytes for rid 0x18 type 4 at 0xb000 em0: [GIANT-LOCKED] em0: Ethernet address: 00:30:48:80:9f:b6 where this one works just fine: em1: <Intel(R) PRO/1000 Network Connection, Version - 1.7.25> port 0xa800-0xa83f mem 0xfa000000-0xfa01ffff irq 19 at device 10.0 on pci3 em1: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xfa000000 em1: Reserved 0x40 bytes for rid 0x18 type 4 at 0xa800 em1: [GIANT-LOCKED] em1: Ethernet address: 00:30:48:80:9f:b7 The chips are these em0@pci1:1:0: class=0x020000 card=0x10758086 chip=0x10758086 rev=0x00 hdr=0x00 em1@pci3:10:0: class=0x020000 card=0x10768086 chip=0x10768086 rev=0x00 hdr=0x00 -- -Søren
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4098D091.5020507>