Date: Thu, 10 Mar 2022 12:44:00 +0100 From: Kristof Provost <kp@FreeBSD.org> To: Johan Hendriks <joh.hendriks@gmail.com> Cc: "Bjoern A. Zeeb" <bz@FreeBSD.org>, mops@punkt.de, FreeBSD Net <freebsd-net@freebsd.org> Subject: Re: epair and vnet jail loose connection. Message-ID: <CC8129F5-A596-43EA-9F26-834DD4DC60F0@FreeBSD.org> In-Reply-To: <65a18f1b-ea22-a3d2-b4ad-41fd52b7fbae@gmail.com> References: <051d51b6-2a07-fbc6-7b4d-13947e7fcdbb@gmail.com> <CF7D877C-E6AC-4FB3-92D8-68E54580631F@punkt.de> <65a18f1b-ea22-a3d2-b4ad-41fd52b7fbae@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10 Mar 2022, at 10:13, Johan Hendriks wrote:
> On 10/03/2022 08:54, Patrick M. Hausen wrote:
>> Hi Johan,
>>
>> we experience the same on 13.1-PRERELEASE. Currently trying to collect=
some evidence
>> (dtrace) to send to Kristof Provost who was so kind to assist. We are =
hit by the problem
>> in production in 12-24 hour intervals. Have not done any artificial lo=
ad tests, yet.
>>
>> May I ask you to run this dtrace script while at least one jail is dis=
connected and while
>> traffic is present that is trying to reach the jail? If you can afford=
to do that in production (?)
>> that would be great. Forward to Kristof (kp@), please.
>>
>> Thanks and kind regards
>> Patrick
>> ----------
>> #!/usr/sbin/dtrace -s
>>
>> BEGIN
>> {
>> self->in_menq =3D 0;
>> }
>>
>> fbt:if_epair:epair_menq:entry
>> {
>> self->in_menq =3D 1;
>> printf("In epair_menq");
>> }
>>
>> fbt:if_epair:epair_menq:return
>> / self->in_menq =3D=3D 1 /
>> {
>> self->in_menq =3D 0;
>> printf("Leave epair_menq");
>> }
>>
>> fbt:kernel:taskqueue_enqueue:entry
>> / self->in_menq =3D=3D 1 /
>> {
>> printf("Enqueue task");
>>
>> }
>>
>> fbt:if_epair:epair_tx_start_deferred:entry
>> {
>> printf("epair_tx_start_deferred");
>> }
>> ----------
>>
> I was asked the above, so hereby the output of that command.
> I did do a=C2=A0 hey -h2 -n 10 -c 10 -z 60s https://wp.test.nl to that =
machine and in the 60 seconds the jail became unresponsive. Then i did ru=
n the dtrace.sh script above like so /root/bin/dtrace.sh > /root/dtrace_o=
utput
>
> I hope this helps, if you need anything please let me know. Also root a=
ccess is possible if you want. That way you do not have to create a test =
environment.
Were there other epair interfaces running at this time, with active traff=
ic?
The dtrace output appears to show that the appropriate callouts (to epair=
_tx_start_deferred()) are getting through, so I=E2=80=99d expect traffic =
to be flowing.
Kristof
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CC8129F5-A596-43EA-9F26-834DD4DC60F0>