Date: Tue, 24 Nov 2009 11:51:03 +0200 From: "Prokofiev S.P." <proks@skylinetele.com> To: Jack Vogel <jfvogel@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: Hangs down/up Intel NIC during creating vlan. Bug em driver ??? Message-ID: <4B0BAC87.7050703@skylinetele.com> In-Reply-To: <2a41acea0911230929h53771ed8j2d8f81be286476a0@mail.gmail.com> References: <4B0AA2CC.5010205@skylinetele.com> <2a41acea0911230929h53771ed8j2d8f81be286476a0@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
It happen on the 82573 and the 82546 depend on vlandev. To reproduce
this input command
ifconfig vlan557 create vlandev em1 vlan 557
and you may see
Nov 23 11:35:49 ...... kernel: em1: link state changed to DOWN
Nov 23 11:35:49 ...... kernel: vlan557: link state changed to DOWN
Nov 23 11:35:52 ...... kernel: em1: link state changed to UP
Nov 23 11:35:52 ...... kernel: vlan557: link state changed to UP
Nov 23 11:36:09 ...... kernel: em1: link state changed to DOWN
Nov 23 11:36:13 ...... kernel: em1: link state changed to UP
For example:
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
ether 00:1b:21:06:43:1a
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
ether 00:1b:21:06:43:1b
media: Ethernet autoselect
status: no carrier
....
vlan2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=3<RXCSUM,TXCSUM>
ether 00:1b:21:06:43:1a
inet 10.25.224.23 netmask 0xfffffff0 broadcast 10.25.224.31
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
vlan: 2 parent interface: em0
input command
ifconfig vlan557 create vlandev em0 vlan 557
in /var/log/messages:
Nov 24 10:59:37 ....... kernel: em0: link state changed to DOWN
Nov 24 10:59:37 ....... kernel: vlan2: link state changed to DOWN
Nov 24 10:59:37 ....... kernel: vlan557: link state changed to DOWN
Nov 24 10:59:41 ....... kernel: em0: link state changed to UP
Nov 24 10:59:41 ....... kernel: vlan2: link state changed to UP
Nov 24 10:59:41 ....... kernel: vlan557: link state changed to UP
On custom kernel ssh client lost connect and reconnect failure until
reboot.
This is tcpdump on fail server (10.25.224.23):
11:13:23.559741 IP 10.25.224.21.58222 > 10.25.224.23.22: Flags [S], seq
1981788951, win 65535, options [mss 1460,nop,wscale 8,sackOK,TS val
3107838092 ecr 0], length 0
11:13:23.559771 IP 10.25.224.23.22 > 10.25.224.21.58222: Flags [S.], seq
2713869415, ack 1981788952, win 65535, options [mss 1460,nop,wscal
e 3,sackOK,TS val 1953228413 ecr 3107838092], length 0
11:13:26.559555 IP 10.25.224.21.58222 > 10.25.224.23.22: Flags [S], seq
1981788951, win 65535, options [mss 1460,nop,wscale 8,sackOK,TS val
3107841092 ecr 0], length 0
11:13:26.559579 IP 10.25.224.23.22 > 10.25.224.21.58222: Flags [S.], seq
2713869415, ack 1981788952, win 65535, options [mss 1460,nop,wscal
e 3,sackOK,TS val 1953228413 ecr 3107841092], length 0
11:13:29.560220 IP 10.25.224.23.22 > 10.25.224.21.58222: Flags [S.], seq
2713869415, ack 1981788952, win 65535, options [mss 1460,nop,wscal
e 3,sackOK,TS val 1953228413 ecr 3107841092], length 0
11:13:29.759620 IP 10.25.224.21.58222 > 10.25.224.23.22: Flags [S], seq
1981788951, win 65535, options [mss 1460,nop,wscale 8,sackOK,TS val
3107844292 ecr 0], length
0
11:13:29.759641 IP 10.25.224.23.22 > 10.25.224.21.58222: Flags [S.], seq
2713869415, ack 1981788952, win 65535, options [mss 1460,nop,wscal
e 3,sackOK,TS val 1953228413 ecr 3107844292], length
0
11:13:32.760214 IP 10.25.224.23.22 > 10.25.224.21.58222: Flags [S.], seq
2713869415, ack 1981788952, win 65535, options [mss 1460,nop,wscal
e 3,sackOK,TS val 1953228413 ecr 3107844292], length
0
11:13:32.959809 IP 10.25.224.21.58222 > 10.25.224.23.22: Flags [S], seq
1981788951, win 65535, options [mss 1460,sackOK,eol], length 0
11:13:32.959829 IP 10.25.224.23.22 > 10.25.224.21.58222: Flags [S.], seq
2713869415, ack 1981788952, win 65535, options [mss 1460,nop,wscal
e 3,sackOK,eol], length 0
11:13:35.960214 IP 10.25.224.23.22 > 10.25.224.21.58222: Flags [S.], seq
2713869415, ack 1981788952, win 65535, options [mss 1460,nop,wscal
e 3,sackOK,eol], length
0
11:13:36.159874 IP 10.25.224.21.58222 > 10.25.224.23.22: Flags [S], seq
1981788951, win 65535, options [mss 1460,sackOK,eol], length 0
11:13:36.159892 IP 10.25.224.23.22 > 10.25.224.21.58222: Flags [S.], seq
2713869415, ack 1981788952, win 65535, options [mss 1460,nop,wscal
e 3,sackOK,eol], length 0
11:13:39.160211 IP 10.25.224.23.22 > 10.25.224.21.58222: Flags [S.], seq
2713869415, ack 1981788952, win 65535, options [mss 1460,nop,wscal
e 3,sackOK,eol], length 0
11:13:39.359940 IP 10.25.224.21.58222 > 10.25.224.23.22: Flags [S], seq
1981788951, win 65535, options [mss 1460,sackOK,eol], length 0
11:13:39.359956 IP 10.25.224.23.22 > 10.25.224.21.58222: Flags [S.], seq
2713869415, ack 1981788952, win 65535, options [mss 1460,nop,wscal
e 3,sackOK,eol], length
0
11:13:42.360212 IP 10.25.224.23.22 > 10.25.224.21.58222: Flags [S.], seq
2713869415, ack 1981788952, win 65535, options [mss 1460,nop,wscal
e 3,sackOK,eol], length 0
But on client I see only requests without reply.
On GENERIC kernel reconnect is success. But down/up interface is not
right behavior.
Jack Vogel wrote:
> Custom kernel, well, does it happen on the installed GENERIC kernel, and
> what is needed
> to reproduce this, just down/up the interface? And are you saying that it
> will happen on
> either the 82573 or the 82546 or just one of them??
>
> Would be nice if this stuff could be discovered earlier :( In any case I
> will look into it, there
> is another reported problems with em and vlans as well.
>
> Jack
>
>
> 2009/11/23 Prokofiev S.P. <proks@skylinetele.com>
>
>
>> Hi ALL !
>> I have several servers with FreeBSD 8.0-PRERELEASE on SuperMicro with
>> different Intel NICs. When I create new vlan on em interface
>> ( ifconfig vlan557 create vlandev em0 vlan 557),
>> it hangs down and then up and server becomes inaccessible by ssh, but reply
>> on icmp request.
>>
>> on amd64, custom kernel:
>>
>> em0@pci0:13:0:0: class=0x020000 card=0x108c15d9 chip=0x108c8086
>> rev=0x03 hdr=0x00
>> vendor = 'Intel Corporation'
>> device = 'Intel Corporation 82573E Gigabit Ethernet Controller
>> (Copper) (82573E)'
>> class = network
>> subclass = ethernet
>> em1@pci0:14:0:0: class=0x020000 card=0x109a15d9 chip=0x109a8086
>> rev=0x00 hdr=0x00
>> vendor = 'Intel Corporation'
>> device = 'Intel PRO/1000 PL Network Adaptor (82573L)'
>> class = network
>> subclass = ethernet
>>
>> on i386, GENERIC kernel:
>>
>> em0@pci0:2:1:0: class=0x020000 card=0x11798086 chip=0x10798086 rev=0x03
>> hdr=0x00
>> vendor = 'Intel Corporation'
>> device = 'Dual Port Gigabit Ethernet Controller (82546EB)'
>> class = network
>> subclass = ethernet
>> em1@pci0:2:1:1: class=0x020000 card=0x11798086 chip=0x10798086 rev=0x03
>> hdr=0x00
>> vendor = 'Intel Corporation'
>> device = 'Dual Port Gigabit Ethernet Controller (82546EB)'
>> class = network
>> subclass = ethernet
>>
>> /var/log/messages:
>>
>> Nov 23 11:35:49 freebsd kernel: em1: link state changed to DOWN
>> Nov 23 11:35:49 freebsd kernel: vlan557: link state changed to DOWN
>> Nov 23 11:35:52 freebsd kernel: em1: link state changed to UP
>> Nov 23 11:35:52 freebsd kernel: vlan557: link state changed to UP
>> Nov 23 11:36:09 freebsd kernel: em1: link state changed to DOWN
>> Nov 23 11:36:13 freebsd kernel: em1: link state changed to UP
>> _______________________________________________
>> freebsd-net@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-net
>> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
>>
>>
> _______________________________________________
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
>
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B0BAC87.7050703>