Date: Wed, 18 Oct 2006 17:26:09 -0700 (PDT) From: Kip Macy <kmacy@fsmware.com> To: Jack Vogel <jfvogel@gmail.com> Cc: freebsd-net <freebsd-net@freebsd.org>, freebsd-stable@freebsd.org Subject: Re: em network issues Message-ID: <20061018171704.A3851@demos.bsdclusters.com> In-Reply-To: <2a41acea0610181531y732cd5sa7bf733cc445491c@mail.gmail.com> References: <2a41acea0610181046k822afd1qcec4187dc8514187@mail.gmail.com> <b1fa29170610181523t6d240839i887632d6d7576762@mail.gmail.com> <2a41acea0610181531y732cd5sa7bf733cc445491c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 18 Oct 2006, Jack Vogel wrote:
> On 10/18/06, Kip Macy <kip.macy@gmail.com> wrote:
> > I have a Sun T2000 that I generally run with the em driver from as of
> > July in order to avoid watchdog timeouts. One trivial scenario that
> > reproduces the problem with 100% consistency is running the ghc
> > configure script (a 20kloc shell script) over NFS. As the T2000
> > doesn't exactly represent "typical" PC hardware it may not be the most
> > desirable test platform. Nonetheless, let me know if you're
> > interested.
> > Thanks for looking into this issue.
> >
> > -Kip
>
> I'm a bit confused from the way you worded this, do you have watchdogs
> with em, or you use em to avoid them?
I have watchdogs with the current (post vendor update) em driver, but
not with an older (pre vendor update) version of it.
>
> If you have problems when running NFS then thats a clue, is it TCP or
> UDP based NFS? I am interested, give me details about the setup please.
Its UDP:
192.168.1.100:/usr/flatstor/freebsd/7.x/sparc64 / nfs bg,intr,rw 0 0
192.168.1.100:/usr/flatstor/shared /shared nfs bg,intr,rw,nfsv3 0 0
Running ./configure --help in /shared/ghc-6.4.2/ triggers it 100%
consistently.
>
> I have one of the engineers in our test organization trying to repro symptoms
> on a system installed with BETA2, it has shared interrupts between em and
> usb. Any additional stuff he could run would be helpful.
>
Let me know what else you need.
%ifconfig -a
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=18b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWCSUM,TSO4>
inet 192.168.1.5 netmask 0xffffff00 broadcast 192.168.1.255
ether 00:03:ba:d9:20:ae
media: Ethernet autoselect (1000baseTX <full-duplex>)
status: active
em1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
options=18b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWCSUM,TSO4>
ether 00:03:ba:d9:20:af
media: Ethernet autoselect
status: no carrier
em2: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
options=18b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWCSUM,TSO4>
ether 00:03:ba:d9:20:b0
media: Ethernet autoselect
status: no carrier
em3: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
options=18b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWCSUM,TSO4>
ether 00:03:ba:d9:20:b1
media: Ethernet autoselect
status: no carrier
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff000000
%pciconf -l
pcib1@pci2:0:0: class=0x060400 card=0x00000040 chip=0x853210b5 rev=0xaa hdr=0x01
pcib2@pci3:1:0: class=0x060400 card=0x00000040 chip=0x853210b5 rev=0xaa hdr=0x01
pcib3@pci3:2:0: class=0x060400 card=0x00000040 chip=0x853210b5 rev=0xaa hdr=0x01
pcib4@pci3:8:0: class=0x060400 card=0x00000040 chip=0x853210b5 rev=0xaa hdr=0x01
pcib5@pci3:9:0: class=0x060400 card=0x00000040 chip=0x853210b5 rev=0xaa hdr=0x01
em0@pci4:0:0: class=0x020000 card=0x105e108e chip=0x105e8086 rev=0x06 hdr=0x00
em1@pci4:0:1: class=0x020000 card=0x105e108e chip=0x105e8086 rev=0x06 hdr=0x00
pcib7@pci2:0:0: class=0x060400 card=0x00000040 chip=0x853210b5 rev=0xaa hdr=0x01
pcib8@pci3:1:0: class=0x060400 card=0x00000040 chip=0x853210b5 rev=0xaa hdr=0x01
pcib11@pci3:2:0: class=0x060400 card=0x00000040 chip=0x853210b5 rev=0xaa hdr=0x01
pcib12@pci3:8:0: class=0x060400 card=0x00000040 chip=0x853210b5 rev=0xaa hdr=0x01
pcib13@pci3:9:0: class=0x060400 card=0x00000040 chip=0x853210b5 rev=0xaa hdr=0x01
pcib9@pci4:0:0: class=0x060400 card=0x00000044 chip=0x03408086 rev=0x09 hdr=0x01
pcib10@pci4:0:2: class=0x060400 card=0x00000044 chip=0x03418086 rev=0x09 hdr=0x01
none0@pci5:2:0: class=0x060100 card=0x153310b9 chip=0x153310b9 rev=0x00 hdr=0x00
none1@pci5:5:0: class=0x0c0310 card=0x00000000 chip=0x523710b9 rev=0x03 hdr=0x00
none2@pci5:6:0: class=0x0c0310 card=0x00000000 chip=0x523710b9 rev=0x03 hdr=0x00
none3@pci5:8:0: class=0x0101ff card=0x00000000 chip=0x522910b9 rev=0xc4 hdr=0x00
none4@pci6:1:0: class=0x0c0400 card=0x01001077 chip=0x23121077 rev=0x02 hdr=0x00
none5@pci6:2:0: class=0x010000 card=0x30f01000 chip=0x00501000 rev=0x02 hdr=0x00
em2@pci7:0:0: class=0x020000 card=0x105e108e chip=0x105e8086 rev=0x06 hdr=0x00
em3@pci7:0:1: class=0x020000 card=0x105e108e chip=0x105e8086 rev=0x06 hdr=0x00
%vmstat -i
interrupt total rate
vec1941: em0 18533 91
Total 18533 91
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061018171704.A3851>