From owner-freebsd-net@freebsd.org Tue Jul 21 12:39:41 2015 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C7989A7651 for ; Tue, 21 Jul 2015 12:39:41 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 485241F26 for ; Tue, 21 Jul 2015 12:39:41 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from moby.local ([79.107.36.229]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0Le69A-1Yahi11t3k-00pwe7; Tue, 21 Jul 2015 14:39:37 +0200 Message-ID: <55AE3D53.60303@gmx.com> Date: Tue, 21 Jul 2015 15:38:43 +0300 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Jason Unovitch , freebsd-net@freebsd.org Subject: Re: [Bug 200319] Bridge+CARP crashes/freezes References: <55ACE900.1060603@gmx.com> <55ADB05D.9060600@gmail.com> In-Reply-To: <55ADB05D.9060600@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:GfdvILXigO5zcgFEfUcw4XY/+ijoJQTvHAcxAncym1OJeDJNvIy K2tr9RJJNUtrdb5D4ikXleLbsKsKsMy7Pemog1v0FuJZasXUxjy3/U7M+IkkL2QU0VYq6vP CKgclApjnqw+h+RfVG5/LdPxlhOpI5vrwE1jt10dtWDtmyy5sd+veuUgdHFmnw1zAYauKEL Nf3vzR1ZfzH52Fp5L1EtA== X-UI-Out-Filterresults: notjunk:1;V01:K0:0WsR6D+YaCU=:0KFtH1JzvTSsIzbiAPJjUG DwF2kg1lbjSLj3I2JvoiNPHstAs/1EztrNNEx77at9xxq54fmZa08D7xgrI6akWyu/f0oz5Li qnK0F2hfdKjdikGoOEtl16S/urcI4B9ofTR5Ibb0+NPygfi7NWIEtp/D7lTFdPkzfUoyO3OMo JG2xpsilQ/1G+XsbNNBP4nUj1Zg6g4Sb52GkuKym8JwZtPtieV5bFSFlFgNFJstUDB5ODFCPr FQ+xOnO9maIkL2RTphXWyUTZb4ZxKk6cppE3l4BSo6+8RIT9CdiBFd5vGLiuznfe1i1AshocK tLRZaWcGuyRlpqQuPDiD5CF4VZANLKd2MmviKK0OZNMsrIQ3WiACTuADGUcZPPy9to5kU/HYN 7MnxcNkOphWk/JYP8Jbe1toVCZiGXj1By1E9EGZ/5ZB8aK6BA0BEQmSDETfMgFXY1pWPVwBXb R0C0L2h/lA4vIFHohzMbhgsmnLkCh/FE7y5DGUz/XcgC8c77+63O895xL29WT0B5ckji5p3Zp ZxB8XtaWrAkGxQHyty4dQ7I4f11PTflSGoBHeqXHE+ymz16Sq0+kHI55maZ9NJz1Wv1f2pMh6 YdNpIPnkIxA1WpE1jhITgBZkOjG1GGlryEKwlIOqHgbQnpr9vdYLRayDOVikAzzcGDcCfN7J5 EPEE5Tae+7PlMrUws3utB4jMC5NdSEiwTbKDxRdo1Ofy5e4L9FdBb5qJhz549Cmt7zoQ= X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jul 2015 12:39:41 -0000 On 07/21/15 05:37, Jason Unovitch wrote: > On 07/20/2015 08:26, Nikos Vassiliadis wrote: >> Hi, >> >> regarding this bug... When carp information is about to be printed, >> it stops. All network activity has stopped by then. For example: >> >>> bridge0: flags=8943 >>> metric 0 mtu 1280 >>> ether 02:48:9e:59:98:00 >>> inet 156.0.0.2 netmask 0xffffffc0 broadcast 156.0.0.63 >>> inet 156.0.0.10 netmask 0xffffffc0 broadcast 156.0.0.63 vhid 10 >>> nd6 options=9 >>> load: 1.18 cmd: ifconfig 1683 [running] 4.14r 0.00u 0.01s 35% 2268k >>> load: 1.18 cmd: ifconfig 1683 [running] 4.59r 0.00u 0.01s 36% 2268k >>> load: 1.18 cmd: ifconfig 1683 [running] 4.85r 0.00u 0.01s 39% 2268k >>> load: 1.18 cmd: ifconfig 1683 [running] 5.05r 0.00u 0.01s 41% 2268k >>> load: 1.18 cmd: ifconfig 1683 [running] 5.27r 0.00u 0.01s 39% 2268k >>> load: 1.18 cmd: ifconfig 1683 [running] 5.48r 0.00u 0.01s 41% 2268k >>> load: 1.18 cmd: ifconfig 1683 [running] 5.69r 0.00u 0.01s 43% 2268k >>> ^C^C^C^Z >>> >>> >>> >>> >>> >>> load: 1.86 cmd: ifconfig 1683 [*carp_if] 31.26r 0.00u 30.67s 88% 2268k >>> load: 1.86 cmd: ifconfig 1683 [*carp_if] 31.42r 0.00u 30.67s 88% 2268k >>> ^Z^Z^Z^C^C^C^C >>> >>> load: 0.22 cmd: ifconfig 1683 [*carp_if] 645.27r 0.00u 30.67s 0% 2268k >>> load: 0.21 cmd: ifconfig 1683 [*carp_if] 645.81r 0.00u 30.67s 0% 2268k >>> load: 0.21 cmd: ifconfig 1683 [*carp_if] 646.17r 0.00u 30.67s 0% 2268k >> >> >> Eventually the kernel will panic: >>> panic: deadlkres: possible deadlock detected for 0xfffff800045b44a0, >>> blocked for 900246 ticks >> >> >> Is this the same bug, Jason? >> >> I could try the patch on my bhyve cluster. >> >> Thanks, >> Nikos > > Nikos, > The report at https://bugs.FreeBSD.org/200319 and associated pfSense > report at https://redmine.pfSense.org/issues/4607 indicate that network > traffic sent to the CARP IP is causing the issue. I don't see anything > that mentions printing the information. > > However with that said, I'm not familiar with the issue as I've never > used CARP. I'm just doing my due diligence passing on a report that the > patch resolved another user's issue over in the FreeBSD Forums: > https://forums.FreeBSD.org/threads/carp-bridge-crashes-freezes-on-freebsd-10.52427 > > > Hope that helps. > Jason Yes, it helps. Unfortunately the patch does not apply cleanly to 10-STABLE. If I manage to use it, I 'll post it here. Nikos