From owner-freebsd-questions@FreeBSD.ORG Wed Apr 18 05:55:53 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BC30D106564A for ; Wed, 18 Apr 2012 05:55:53 +0000 (UTC) (envelope-from kes-kes@yandex.ru) Received: from forward20.mail.yandex.net (forward20.mail.yandex.net [IPv6:2a02:6b8:0:1402::5]) by mx1.freebsd.org (Postfix) with ESMTP id 8D13D8FC0C for ; Wed, 18 Apr 2012 05:55:52 +0000 (UTC) Received: from smtp19.mail.yandex.net (smtp19.mail.yandex.net [95.108.252.19]) by forward20.mail.yandex.net (Yandex) with ESMTP id 2C3E21041AEF; Wed, 18 Apr 2012 09:55:51 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1334728551; bh=0h8WpgaXR4MFc+yfjS2J6BYbe7PiSa5/7c4K7V19itA=; h=Date:From:Reply-To:Message-ID:To:CC:Subject:In-Reply-To: References:MIME-Version:Content-Type:Content-Transfer-Encoding; b=g+nrE/5/hlwBx0tbASRYFgKkRaFQMIDGYkXwGPH99YKOHHYtD5EO4TBsp0kTK8ATk zwcVasOR1I57VW7BRAbtm9xYUrrDu4JAyI2XfF64fYWw9+6x6uucy80dWTNWYvocA4 VCjXJB0S/EVEnzIT+3O1VmaNICnstOl8R4Z9GNpQ= Received: from smtp19.mail.yandex.net (localhost [127.0.0.1]) by smtp19.mail.yandex.net (Yandex) with ESMTP id 0896FBE021C; Wed, 18 Apr 2012 09:55:50 +0400 (MSK) Received: from unknown (unknown [77.93.52.20]) by smtp19.mail.yandex.net (nwsmtp/Yandex) with ESMTP id tl9q4wXE-to9G8X0h; Wed, 18 Apr 2012 09:55:50 +0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1334728550; bh=0h8WpgaXR4MFc+yfjS2J6BYbe7PiSa5/7c4K7V19itA=; h=Date:From:X-Mailer:Reply-To:Organization:X-Priority:Message-ID:To: CC:Subject:In-Reply-To:References:MIME-Version:Content-Type: Content-Transfer-Encoding; b=hNQk1Lj5whtGS2uajK5JASCfdQNN0XATMs63egLI2JR2p2763/aD1iFEwx/PbQcQM wOGEoWEQjFWH38UtyegmY1JG8kYfQcRBYa+pgni0MUF5UizLFDJjB9tD2WKZ4Nm6aA xIPpKpZ7QydIeGJIsp4AuSu2UNVk1HnRyBGnx7EA= Date: Wed, 18 Apr 2012 08:55:45 +0300 From: Eugen Konkov X-Mailer: The Bat! (v4.0.24) Professional Organization: ISP FreeLine X-Priority: 3 (Normal) Message-ID: <466210703.20120418085545@yandex.ru> To: Damien Fleuriot In-Reply-To: References: <505981334167684@web133.yandex.ru> <26203474.20120412233549@yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Cc: "freebsd-questions@freebsd.org" , KES Subject: Re[4]: Problem with vlans on igb (was: fsck problem FreeBSD 8.3) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Eugen Konkov List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Apr 2012 05:55:53 -0000 Hi, Damien. With this configuration works without reboots ifconfig_igb0="-rxcsum -txcsum -lro -tso up" ifconfig_igb1="-rxcsum -txcsum -lro -tso up" ifconfig_igb2="-rxcsum -txcsum -lro -tso -vlanhwtag up" ifconfig_igb3="-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 see DF> if the situation changes. DF> 2012/4/12 ëÏÎØËÏ× å×ÇÅÎÉÊ : >> 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 metric 0 mtu 1500 >> š š š šoptions=400b8 >> š š š šcapabilities=505bb >> š š š šether a0:36:9f:00:66:a5 >> š š š šmedia: Ethernet autoselect (1000baseT ) >> š š š š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 : >>>> >>>> >>>> -------- ðÅÒÅÓÙÌÁÅÍÏÅ ÓÏÏÂÝÅÎÉÅ š-------- >>>> 11.04.2012, 13:14, "KES" : >>>> >>>> 10.04.2012, 08:50, "Da Rock" : >>>> >>>>> š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? >>>>> š_______________________________________________ >> >> -- ó Õ×ÁÖÅÎÉÅÍ, Eugen mailto:kes-kes@yandex.ru