Date: Thu, 19 Apr 2012 16:47:00 +0200 From: Damien Fleuriot <ml@my.gd> To: Eugen Konkov <kes-kes@yandex.ru> Cc: jfvogel@gmail.com, "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>, KES <kes-kes@yandex.ua> Subject: Re: Re[4]: Problem with vlans on igb (was: fsck problem FreeBSD 8.3) Message-ID: <CAE63ME7njjrWd1YiGNw=mL3uk2s-sAKmqp6vcfmTnPdz4%2BJHiQ@mail.gmail.com> In-Reply-To: <466210703.20120418085545@yandex.ru> References: <505981334167684@web133.yandex.ru> <CAE63ME63PiY=BfHCJfxi2kU_FkrUGrkhU3X6dD-G1fW-hVA_HA@mail.gmail.com> <26203474.20120412233549@yandex.ru> <CAE63ME5nQnzMVZ9NULd8zknyw0bYjsAe4bDunvfgf=1dGWx0tQ@mail.gmail.com> <466210703.20120418085545@yandex.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Well, you see me glad that this fixes your problems. You might want to see with Jack Vogel who maintains the Intel drivers, if you can track down the issue and perhaps even find a fix for it. Taking the liberty of CCing you Jack. 2012/4/18 Eugen Konkov <kes-kes@yandex.ru>: > Hi, Damien. > > With this configuration works without reboots > > ifconfig_igb0=3D"-rxcsum -txcsum -lro -tso up" > ifconfig_igb1=3D"-rxcsum -txcsum -lro -tso up" > ifconfig_igb2=3D"-rxcsum -txcsum -lro -tso -vlanhwtag up" > ifconfig_igb3=3D"-rxcsum -txcsum -lro -tso up" > > > igb0 has only one vlan > igb1 has two vlans > igb2 has 16 vlans > igb3 has 4 vlans > > > if igb2 has vlanhwtag enabled then server starts to reboot > > DF> Yes, I suggest you try with "-vlanhwtag" as well. > DF> If that stops your unwanted reboots, you may want to remove it and se= e > DF> if the situation changes. > > > DF> 2012/4/12 =EB=CF=CE=D8=CB=CF=D7 =E5=D7=C7=C5=CE=C9=CA <kes-kes@yandex= .ru>: >>> Now i350 is configured as: >>> >>> /etc/rc.conf >>> ## TCP/IP >>> ifconfig_igb0=3D"-rxcsum -txcsum -lro -tso up" >>> ifconfig_igb1=3D"-rxcsum -txcsum -lro -tso up" >>> ifconfig_igb2=3D"-rxcsum -txcsum -lro -tso up" >>> ifconfig_igb3=3D"-rxcsum -txcsum -lro -tso up" >>> >>> # ifconfig -m igb1 >>> igb1: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu= 1500 >>> =9A =9A =9A =9Aoptions=3D400b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_H= WCSUM,VLAN_HWTSO> >>> =9A =9A =9A =9Acapabilities=3D505bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGI= NG,JUMBO_MTU,VLAN_HWCSUM,TSO4,LRO,VLAN_HWFILTER,VLAN_HWTSO> >>> =9A =9A =9A =9Aether a0:36:9f:00:66:a5 >>> =9A =9A =9A =9Amedia: Ethernet autoselect (1000baseT <full-duplex>) >>> =9A =9A =9A =9Astatus: active >>> =9A =9A =9A =9Asupported media: >>> =9A =9A =9A =9A =9A =9A =9A =9Amedia autoselect >>> =9A =9A =9A =9A =9A =9A =9A =9Amedia 1000baseT >>> =9A =9A =9A =9A =9A =9A =9A =9Amedia 1000baseT mediaopt full-duplex >>> =9A =9A =9A =9A =9A =9A =9A =9Amedia 100baseTX mediaopt full-duplex >>> =9A =9A =9A =9A =9A =9A =9A =9Amedia 100baseTX >>> =9A =9A =9A =9A =9A =9A =9A =9Amedia 10baseT/UTP mediaopt full-duplex >>> =9A =9A =9A =9A =9A =9A =9A =9Amedia 10baseT/UTP >>> >>> #pciconf -lv >>> igb0@pci0:1:0:0: =9A =9A =9A =9Aclass=3D0x020000 card=3D0x00018086 chip= =3D0x15218086 rev=3D0x01 hdr=3D0x00 >>> =9A =9Avendor =9A =9A =3D 'Intel Corporation' >>> =9A =9Aclass =9A =9A =9A=3D network >>> =9A =9Asubclass =9A =3D ethernet >>> >>> >>> >>> Do I need to disable VLAN_HWCSUM, VLAN_HWFILTER,VLAN_HWTSO also? >>> >>> PS. I will try to disable those after the holidays >>> >>> DF> Try disabling hardware VLAN tagging like so, I know we had problems= a >>> DF> few years back with it. >>> >>> DF> in /etc/rc.conf : >>> DF> ifconfig_igb2=3D" -vlanhwtag -tso -lro up" >>> >>> >>> DF> 2012/4/11 KES <kes-kes@yandex.ua>: >>>>> >>>>> >>>>> -------- =F0=C5=D2=C5=D3=D9=CC=C1=C5=CD=CF=C5 =D3=CF=CF=C2=DD=C5=CE= =C9=C5 =9A-------- >>>>> 11.04.2012, 13:14, "KES" <kes-kes@yandex.ua>: >>>>> >>>>> 10.04.2012, 08:50, "Da Rock" <freebsd-questions@herveybayaustralia.co= m.au>: >>>>> >>>>>> =9AOn 04/10/12 05:02, =EB=CF=CE=D8=CB=CF=D7 =E5=D7=C7=C5=CE=C9=CA wr= ote: >>>>>>> =9A=9AYes, I have tested. >>>>>>> =9A=9Aand on this hardware on this OS it works from =9AFri Feb 24 1= 7:07:48 UTC 2012 >>>>>>> =9A=9Abut last two days: >>>>>>> =9A=9Areboot =9A=9A=9A=9A=9A=9A=9A=9A=9A=9A~ =9A=9A=9A=9A=9A=9A=9A= =9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9AMon Apr =9A9 19:50 >>>>>>> =9A=9Areboot =9A=9A=9A=9A=9A=9A=9A=9A=9A=9A~ =9A=9A=9A=9A=9A=9A=9A= =9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9AMon Apr =9A9 18:30 >>>>>>> =9A=9Areboot =9A=9A=9A=9A=9A=9A=9A=9A=9A=9A~ =9A=9A=9A=9A=9A=9A=9A= =9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9ASun Apr =9A8 20:55 >>>>>>> =9A=9Areboot =9A=9A=9A=9A=9A=9A=9A=9A=9A=9A~ =9A=9A=9A=9A=9A=9A=9A= =9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9ASun Apr =9A8 20:00 >>>>>>> =9A=9Areboot =9A=9A=9A=9A=9A=9A=9A=9A=9A=9A~ =9A=9A=9A=9A=9A=9A=9A= =9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9ASun Apr =9A8 19:49 >>>>>>> =9A=9Areboot =9A=9A=9A=9A=9A=9A=9A=9A=9A=9A~ =9A=9A=9A=9A=9A=9A=9A= =9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9ASun Apr =9A8 17:43 >>>>>>> =9A=9Areboot =9A=9A=9A=9A=9A=9A=9A=9A=9A=9A~ =9A=9A=9A=9A=9A=9A=9A= =9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9ASun Apr =9A8 10:58 >>>>>>> =9A=9Areboot =9A=9A=9A=9A=9A=9A=9A=9A=9A=9A~ =9A=9A=9A=9A=9A=9A=9A= =9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9ASat Apr =9A7 21:13 >>>>>>> =9A=9Areboot =9A=9A=9A=9A=9A=9A=9A=9A=9A=9A~ =9A=9A=9A=9A=9A=9A=9A= =9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9ASat Apr =9A7 16:37 >>>>>>> =9A=9Areboot =9A=9A=9A=9A=9A=9A=9A=9A=9A=9A~ =9A=9A=9A=9A=9A=9A=9A= =9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9ASat Apr =9A7 16:07 >>>>>>> >>>>>>> =9A=9AI remembered. One thing changed. >>>>>>> =9A=9AI add vlans to igb2, but no traffic flow on that devices yet. >>>>>> =9APerhaps you should test removing the vlans and see if things impr= ove? >>>>> >>>>> I have removed vlans, two day server works without reboots >>>>> >>>>>>> =9A=9ABefore this I have use: igb0, igb1, igb3 >>>>>>> =9A=9Aigb0@pci0:1:0:0: =9A=9A=9A=9A=9A=9A=9Aclass=3D0x020000 card= =3D0x00018086 chip=3D0x15218086 rev=3D0x01 hdr=3D0x00 >>>>>>> =9A=9A=9A=9A=9A=9A=9Avendor =9A=9A=9A=9A=3D 'Intel Corporation' >>>>>>> =9A=9A=9A=9A=9A=9A=9Aclass =9A=9A=9A=9A=9A=3D network >>>>>>> =9A=9A=9A=9A=9A=9A=9Asubclass =9A=9A=3D ethernet >>>>>>> =9A=9Aigb1@pci0:1:0:1: =9A=9A=9A=9A=9A=9A=9Aclass=3D0x020000 card= =3D0x00018086 chip=3D0x15218086 rev=3D0x01 hdr=3D0x00 >>>>>>> =9A=9A=9A=9A=9A=9A=9Avendor =9A=9A=9A=9A=3D 'Intel Corporation' >>>>>>> =9A=9A=9A=9A=9A=9A=9Aclass =9A=9A=9A=9A=9A=3D network >>>>>>> =9A=9A=9A=9A=9A=9A=9Asubclass =9A=9A=3D ethernet >>>>>>> =9A=9Aigb2@pci0:1:0:2: =9A=9A=9A=9A=9A=9A=9Aclass=3D0x020000 card= =3D0x00018086 chip=3D0x15218086 rev=3D0x01 hdr=3D0x00 >>>>>>> =9A=9A=9A=9A=9A=9A=9Avendor =9A=9A=9A=9A=3D 'Intel Corporation' >>>>>>> =9A=9A=9A=9A=9A=9A=9Aclass =9A=9A=9A=9A=9A=3D network >>>>>>> =9A=9A=9A=9A=9A=9A=9Asubclass =9A=9A=3D ethernet >>>>>>> =9A=9Aigb3@pci0:1:0:3: =9A=9A=9A=9A=9A=9A=9Aclass=3D0x020000 card= =3D0x00018086 chip=3D0x15218086 rev=3D0x01 hdr=3D0x00 >>>>>>> =9A=9A=9A=9A=9A=9A=9Avendor =9A=9A=9A=9A=3D 'Intel Corporation' >>>>>>> =9A=9A=9A=9A=9A=9A=9Aclass =9A=9A=9A=9A=9A=3D network >>>>>>> =9A=9A=9A=9A=9A=9A=9Asubclass =9A=9A=3D ethernet >>>>>>> >>>>>>> =9A=9Aifconfig_vlan100=3D"inet =9A192.168.0.1 netmask 255.255.255.0= vlan 100 vlandev igb2" #nALL >>>>>>> =9A=9Aifconfig_vlan101=3D"inet =9A192.168.1.1 netmask 255.255.255.0= vlan 101 vlandev igb2" #n2 p24 >>>>>>> =9A=9Aifconfig_vlan102=3D"inet =9A192.168.2.1 netmask 255.255.255.0= vlan 102 vlandev igb2" #n1 p23 >>>>>>> =9A=9Aifconfig_vlan103=3D"inet =9A192.168.3.1 netmask 255.255.255.0= vlan 103 vlandev igb2" #n3 p22 >>>>>>> =9A=9Aifconfig_vlan104=3D"inet =9A192.168.4.1 netmask 255.255.255.0= vlan 104 vlandev igb2" #n7,9 p21 >>>>>>> =9A=9Aifconfig_vlan105=3D"inet =9A192.168.5.1 netmask 255.255.255.0= vlan 105 vlandev igb2" #n11 p20 >>>>>>> =9A=9Aifconfig_vlan106=3D"inet =9A192.168.6.1 netmask 255.255.255.0= vlan 106 vlandev igb2" #n13 p19 >>>>>>> =9A=9Aifconfig_vlan107=3D"inet =9A192.168.7.1 netmask 255.255.255.0= vlan 107 vlandev igb2" #n223 p18 >>>>>>> =9A=9Aifconfig_vlan108=3D"inet =9A192.168.8.1 netmask 255.255.255.0= vlan 108 vlandev igb2" #n225 p17 >>>>>>> =9A=9Aifconfig_vlan109=3D"inet =9A192.168.9.1 netmask 255.255.255.0= vlan 109 vlandev igb2" #n221 p16 >>>>>>> =9A=9Aifconfig_vlan110=3D"inet 192.168.10.1 netmask 255.255.255.0 v= lan 110 vlandev igb2" #n229 p15 >>>>>>> =9A=9Aifconfig_vlan111=3D"inet 192.168.11.1 netmask 255.255.255.0 v= lan 111 vlandev igb2" #n233 p14 >>>>>>> =9A=9Aifconfig_vlan112=3D"inet 192.168.12.1 netmask 255.255.255.0 v= lan 112 vlandev igb2" #n231 p13 >>>>>>> =9A=9Aifconfig_vlan113=3D"inet 192.168.13.1 netmask 255.255.255.0 v= lan 113 vlandev igb2" #n237 p12 >>>>>>> =9A=9Aifconfig_vlan114=3D"inet 192.168.14.1 netmask 255.255.255.0 v= lan 114 vlandev igb2" #n424 p11 >>>>>>> =9A=9Aifconfig_vlan115=3D"inet 192.168.15.1 netmask 255.255.255.0 v= lan 115 vlandev igb2" # >>>>>>> >>>>>>> =9A=9APAP> =9ANothing logged in /var/log/* or crashes that exist in= /var/crash >>>>>>> =9A=9APAP> =9Awould indicate to me some sort of hardware related pr= oblem. >>>>>>> =9A=9APAP> =9AHave you tested your hardware lately and know that it= is in operational order? >>>>>>> >>>>>>> =9A=9APAP> =9A~Paul >>>>>>> >>>>>>> =9A=9APAP> =9AOn Mon, Apr 09, 2012 at 09:36:54PM +0300, ??????? ???= ???? wrote: >>>>>>>>> =9A=9AHi. >>>>>>>>> >>>>>>>>> =9A=9AApr =9A9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTEN= CY, CANNOT RUN FAST FSCK >>>>>>>>> =9A=9AApr =9A9 19:51:58 fsck: >>>>>>>>> =9A=9AApr =9A9 19:51:58 fsck: >>>>>>>>> =9A=9AApr =9A9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTEN= CY; RUN fsck MANUALLY. >>>>>>>>> =9A=9AApr =9A9 19:51:58 fsck: /dev/ad8s1e: CANNOT SET FS_NEEDSFSC= K FLAG >>>>>>>>> =9A=9AApr =9A9 20:09:22 kernel: >>>>>>>>> >>>>>>>>> =9A=9Arunning manually: >>>>>>>>> =9A=9A# fsck -y /dev/ad8s1e >>>>>>>>> =9A=9A** /dev/ad8s1e (NO WRITE) >>>>>>>>> =9A=9A** Last Mounted on /tmp >>>>>>>>> =9A=9A** Phase 1 - Check Blocks and Sizes >>>>>>>>> =9A=9A** Phase 2 - Check Pathnames >>>>>>>>> =9A=9A** Phase 3 - Check Connectivity >>>>>>>>> =9A=9A** Phase 4 - Check Reference Counts >>>>>>>>> =9A=9A** Phase 5 - Check Cyl groups >>>>>>>>> =9A=9A99 files, 10 used, 506477 free (45 frags, 63304 blocks, 0.0= % fragmentation) >>>>>>>>> >>>>>>>>> =9A=9AServer reboot two or three time per day >>>>>>>>> =9A=9A# uname -a >>>>>>>>> =9A=9AFreeBSD flux 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #3 r2318= 81: Fri Feb 24 17:07:48 UTC 2012 =9A=9A=9A=9Aadm@flux:/usr/obj/usr/src/sys/= KES_KERN_v8 =9Aamd64 >>>>>>>>> >>>>>>>>> =9A=9Abefore this it works about month without problems >>>>>>>>> >>>>>>>>> =9A=9A/var/crash - empty, in /var/log/messages there is no any me= ssages before crash. >>>>>>>>> =9A=9ACan any help to fix problem? >>>>>> =9A_______________________________________________ >>> >>> > > > > > -- > =F3 =D5=D7=C1=D6=C5=CE=C9=C5=CD, > =9AEugen =9A =9A =9A =9A =9A =9A =9A =9A =9A =9A =9A =9A =9Amailto:kes-ke= s@yandex.ru >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAE63ME7njjrWd1YiGNw=mL3uk2s-sAKmqp6vcfmTnPdz4%2BJHiQ>