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-...@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-...@yandex.ua>: >>> >>> >>> -------- Пересылаемое сообщение -------- >>> 11.04.2012, 13:14, "KES" <kes-...@yandex.ua>: >>> >>> 10.04.2012, 08:50, "Da Rock" <freebsd-questi...@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? >>>> _______________________________________________ > > _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"