Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 20 Jul 2015 22:37:17 -0400
From:      Jason Unovitch <jason.unovitch@gmail.com>
To:        Nikos Vassiliadis <nvass@gmx.com>, freebsd-net@freebsd.org
Subject:   Re: [Bug 200319] Bridge+CARP crashes/freezes
Message-ID:  <55ADB05D.9060600@gmail.com>
In-Reply-To: <55ACE900.1060603@gmx.com>
References:  <bug-200319-2472@https.bugs.freebsd.org/bugzilla/> <bug-200319-2472-AdqyzfFyAT@https.bugs.freebsd.org/bugzilla/> <55ACE900.1060603@gmx.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST>
>> 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<PERFORMNUD,IFDISABLED>
>> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55ADB05D.9060600>