From owner-freebsd-bugs@freebsd.org  Wed May 17 14:56:22 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 B6400D5C25E
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 17 May 2017 14:56:22 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id A5C091758
 for <freebsd-bugs@FreeBSD.org>; Wed, 17 May 2017 14:56:22 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4HEuM8V006666
 for <freebsd-bugs@FreeBSD.org>; Wed, 17 May 2017 14:56:22 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 219356] Using AES-GCM with IPSEC with aesni module loaded
 panics FreeBSD 11 stable
Date: Wed, 17 May 2017 14:56:22 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: ae@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-219356-8-cnazvJaEME@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-219356-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-219356-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 17 May 2017 14:56:22 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219356

Andrey V. Elsukov <ae@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ae@FreeBSD.org

--- Comment #1 from Andrey V. Elsukov <ae@FreeBSD.org> ---
(In reply to lab from comment #0)
> Created attachment 182666 [details]
> Core text file from panic
>=20
> Using iperf to pass data between two hosts behind two FreeBSD gateways th=
at
> have an IPSec tunnel between them will panic gateway. The gateway that
> panics os the one doing most of the decryption (gateway in front of iperf
> running in server mode). I used iperf in UDP mode. Not sure if that is
> needed. If I use 11.0-RELEASE-p9 I do not see this issue.=20
>=20
> I used strongswan to create IPSec tunnel between gateways. If duplicating,
> make sure GCM option is turned on for strongswan.

What revision do you use to build FreeBSD 11.0-STABLE and what strongswan
version do you use? Does it panics immediately after starting iperf test or=
 it
needs some time?

--=20
You are receiving this mail because:
You are the assignee for the bug.=