Date: Fri, 13 Apr 2012 03:42:31 +0200 From: Damien Fleuriot <ml@my.gd> To: =?KOI8-R?B?68/O2MvP1yDl18fFzsnK?= <kes-kes@yandex.ru> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>, KES <kes-kes@yandex.ua> Subject: Re: Re[2]: Problem with vlans on igb (was: fsck problem FreeBSD 8.3) Message-ID: <CAE63ME5nQnzMVZ9NULd8zknyw0bYjsAe4bDunvfgf=1dGWx0tQ@mail.gmail.com> In-Reply-To: <26203474.20120412233549@yandex.ru> References: <505981334167684@web133.yandex.ru> <CAE63ME63PiY=BfHCJfxi2kU_FkrUGrkhU3X6dD-G1fW-hVA_HA@mail.gmail.com> <26203474.20120412233549@yandex.ru>
index | next in thread | previous in thread | raw e-mail
Yes, I suggest you try with "-vlanhwtag" as well. If that stops your unwanted reboots, you may want to remove it and see if the situation changes. 2012/4/12 ëÏÎØËÏ× å×ÇÅÎÉÊ <kes-kes@yandex.ru>: > Now i350 is configured as: > > /etc/rc.conf > ## TCP/IP > ifconfig_igb0="-rxcsum -txcsum -lro -tso up" > ifconfig_igb1="-rxcsum -txcsum -lro -tso up" > ifconfig_igb2="-rxcsum -txcsum -lro -tso up" > ifconfig_igb3="-rxcsum -txcsum -lro -tso up" > > # ifconfig -m igb1 > igb1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 > š š š šoptions=400b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO> > š š š šcapabilities=505bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,LRO,VLAN_HWFILTER,VLAN_HWTSO> > š š š šether a0:36:9f:00:66:a5 > š š š šmedia: Ethernet autoselect (1000baseT <full-duplex>) > š š š šstatus: active > š š š šsupported media: > š š š š š š š šmedia autoselect > š š š š š š š šmedia 1000baseT > š š š š š š š šmedia 1000baseT mediaopt full-duplex > š š š š š š š šmedia 100baseTX mediaopt full-duplex > š š š š š š š šmedia 100baseTX > š š š š š š š šmedia 10baseT/UTP mediaopt full-duplex > š š š š š š š šmedia 10baseT/UTP > > #pciconf -lv > igb0@pci0:1:0:0: š š š šclass=0x020000 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 > š švendor š š = 'Intel Corporation' > š šclass š š š= network > š šsubclass š = 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=" -vlanhwtag -tso -lro up" > > > DF> 2012/4/11 KES <kes-kes@yandex.ua>: >>> >>> >>> -------- ðÅÒÅÓÙÌÁÅÍÏÅ ÓÏÏÂÝÅÎÉÅ š-------- >>> 11.04.2012, 13:14, "KES" <kes-kes@yandex.ua>: >>> >>> 10.04.2012, 08:50, "Da Rock" <freebsd-questions@herveybayaustralia.com.au>: >>> >>>> šOn 04/10/12 05:02, ëÏÎØËÏ× å×ÇÅÎÉÊ wrote: >>>>> ššYes, I have tested. >>>>> ššand on this hardware on this OS it works from šFri Feb 24 17:07:48 UTC 2012 >>>>> ššbut last two days: >>>>> ššreboot šššššššššš~ ššššššššššššššššššššššššMon Apr š9 19:50 >>>>> ššreboot šššššššššš~ ššššššššššššššššššššššššMon Apr š9 18:30 >>>>> ššreboot šššššššššš~ ššššššššššššššššššššššššSun Apr š8 20:55 >>>>> ššreboot šššššššššš~ ššššššššššššššššššššššššSun Apr š8 20:00 >>>>> ššreboot šššššššššš~ ššššššššššššššššššššššššSun Apr š8 19:49 >>>>> ššreboot šššššššššš~ ššššššššššššššššššššššššSun Apr š8 17:43 >>>>> ššreboot šššššššššš~ ššššššššššššššššššššššššSun Apr š8 10:58 >>>>> ššreboot šššššššššš~ ššššššššššššššššššššššššSat Apr š7 21:13 >>>>> ššreboot šššššššššš~ ššššššššššššššššššššššššSat Apr š7 16:37 >>>>> ššreboot šššššššššš~ ššššššššššššššššššššššššSat Apr š7 16:07 >>>>> >>>>> ššI remembered. One thing changed. >>>>> ššI add vlans to igb2, but no traffic flow on that devices yet. >>>> šPerhaps you should test removing the vlans and see if things improve? >>> >>> I have removed vlans, two day server works without reboots >>> >>>>> ššBefore this I have use: igb0, igb1, igb3 >>>>> ššigb0@pci0:1:0:0: šššššššclass=0x020000 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 >>>>> šššššššvendor šššš= 'Intel Corporation' >>>>> šššššššclass ššššš= network >>>>> šššššššsubclass šš= ethernet >>>>> ššigb1@pci0:1:0:1: šššššššclass=0x020000 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 >>>>> šššššššvendor šššš= 'Intel Corporation' >>>>> šššššššclass ššššš= network >>>>> šššššššsubclass šš= ethernet >>>>> ššigb2@pci0:1:0:2: šššššššclass=0x020000 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 >>>>> šššššššvendor šššš= 'Intel Corporation' >>>>> šššššššclass ššššš= network >>>>> šššššššsubclass šš= ethernet >>>>> ššigb3@pci0:1:0:3: šššššššclass=0x020000 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 >>>>> šššššššvendor šššš= 'Intel Corporation' >>>>> šššššššclass ššššš= network >>>>> šššššššsubclass šš= ethernet >>>>> >>>>> ššifconfig_vlan100="inet š192.168.0.1 netmask 255.255.255.0 vlan 100 vlandev igb2" #nALL >>>>> ššifconfig_vlan101="inet š192.168.1.1 netmask 255.255.255.0 vlan 101 vlandev igb2" #n2 p24 >>>>> ššifconfig_vlan102="inet š192.168.2.1 netmask 255.255.255.0 vlan 102 vlandev igb2" #n1 p23 >>>>> ššifconfig_vlan103="inet š192.168.3.1 netmask 255.255.255.0 vlan 103 vlandev igb2" #n3 p22 >>>>> ššifconfig_vlan104="inet š192.168.4.1 netmask 255.255.255.0 vlan 104 vlandev igb2" #n7,9 p21 >>>>> ššifconfig_vlan105="inet š192.168.5.1 netmask 255.255.255.0 vlan 105 vlandev igb2" #n11 p20 >>>>> ššifconfig_vlan106="inet š192.168.6.1 netmask 255.255.255.0 vlan 106 vlandev igb2" #n13 p19 >>>>> ššifconfig_vlan107="inet š192.168.7.1 netmask 255.255.255.0 vlan 107 vlandev igb2" #n223 p18 >>>>> ššifconfig_vlan108="inet š192.168.8.1 netmask 255.255.255.0 vlan 108 vlandev igb2" #n225 p17 >>>>> ššifconfig_vlan109="inet š192.168.9.1 netmask 255.255.255.0 vlan 109 vlandev igb2" #n221 p16 >>>>> ššifconfig_vlan110="inet 192.168.10.1 netmask 255.255.255.0 vlan 110 vlandev igb2" #n229 p15 >>>>> ššifconfig_vlan111="inet 192.168.11.1 netmask 255.255.255.0 vlan 111 vlandev igb2" #n233 p14 >>>>> ššifconfig_vlan112="inet 192.168.12.1 netmask 255.255.255.0 vlan 112 vlandev igb2" #n231 p13 >>>>> ššifconfig_vlan113="inet 192.168.13.1 netmask 255.255.255.0 vlan 113 vlandev igb2" #n237 p12 >>>>> ššifconfig_vlan114="inet 192.168.14.1 netmask 255.255.255.0 vlan 114 vlandev igb2" #n424 p11 >>>>> ššifconfig_vlan115="inet 192.168.15.1 netmask 255.255.255.0 vlan 115 vlandev igb2" # >>>>> >>>>> ššPAP> šNothing logged in /var/log/* or crashes that exist in /var/crash >>>>> ššPAP> šwould indicate to me some sort of hardware related problem. >>>>> ššPAP> šHave you tested your hardware lately and know that it is in operational order? >>>>> >>>>> ššPAP> š~Paul >>>>> >>>>> ššPAP> šOn Mon, Apr 09, 2012 at 09:36:54PM +0300, ??????? ??????? wrote: >>>>>>> ššHi. >>>>>>> >>>>>>> ššApr š9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST FSCK >>>>>>> ššApr š9 19:51:58 fsck: >>>>>>> ššApr š9 19:51:58 fsck: >>>>>>> ššApr š9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. >>>>>>> ššApr š9 19:51:58 fsck: /dev/ad8s1e: CANNOT SET FS_NEEDSFSCK FLAG >>>>>>> ššApr š9 20:09:22 kernel: >>>>>>> >>>>>>> ššrunning manually: >>>>>>> šš# fsck -y /dev/ad8s1e >>>>>>> šš** /dev/ad8s1e (NO WRITE) >>>>>>> šš** Last Mounted on /tmp >>>>>>> šš** Phase 1 - Check Blocks and Sizes >>>>>>> šš** Phase 2 - Check Pathnames >>>>>>> šš** Phase 3 - Check Connectivity >>>>>>> šš** Phase 4 - Check Reference Counts >>>>>>> šš** Phase 5 - Check Cyl groups >>>>>>> šš99 files, 10 used, 506477 free (45 frags, 63304 blocks, 0.0% fragmentation) >>>>>>> >>>>>>> ššServer reboot two or three time per day >>>>>>> šš# uname -a >>>>>>> ššFreeBSD flux 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #3 r231881: Fri Feb 24 17:07:48 UTC 2012 ššššadm@flux:/usr/obj/usr/src/sys/KES_KERN_v8 šamd64 >>>>>>> >>>>>>> ššbefore this it works about month without problems >>>>>>> >>>>>>> šš/var/crash - empty, in /var/log/messages there is no any messages before crash. >>>>>>> ššCan any help to fix problem? >>>> š_______________________________________________ > >help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAE63ME5nQnzMVZ9NULd8zknyw0bYjsAe4bDunvfgf=1dGWx0tQ>