From nobody Thu Oct 5 22:11:02 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4S1m3Y627Yz4vxph for ; Thu, 5 Oct 2023 22:11:05 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4S1m3Y3fj8z3GqQ; Thu, 5 Oct 2023 22:11:05 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Authentication-Results: mx1.freebsd.org; none Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.17.1/8.17.1) with ESMTP id 395MB3ZO000488; Thu, 5 Oct 2023 15:11:03 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.17.1/8.17.1/Submit) id 395MB3oa000487; Thu, 5 Oct 2023 15:11:03 -0700 (PDT) (envelope-from sgk) Date: Thu, 5 Oct 2023 15:11:02 -0700 From: Steve Kargl To: Kristof Provost Cc: freebsd-current@freebsd.org Subject: Re: panic in cypto code Message-ID: Reply-To: sgk@troutmask.apl.washington.edu References: <10AA8134-04A9-43D3-90C9-CBC3012A77D3@FreeBSD.org> <77656A9F-CDBA-4FB6-AE42-896285E967CC@FreeBSD.org> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <77656A9F-CDBA-4FB6-AE42-896285E967CC@FreeBSD.org> X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US] X-Rspamd-Queue-Id: 4S1m3Y3fj8z3GqQ On Thu, Oct 05, 2023 at 11:33:46PM +0200, Kristof Provost wrote: > On 5 Oct 2023, at 19:34, Steve Kargl wrote: > > On Thu, Oct 05, 2023 at 06:05:37PM +0200, Kristof Provost wrote: > >> > >> On 5 Oct 2023, at 17:36, Steve Kargl wrote: > >>> In case anyone else is using openvpn. > >>> (dump removed to keep this brief) > >>> > >> Do you have a bit more information about what happened here? > >> As in: can you reproduce this, or do you have any idea what > >> was going on to trigger this? Did anything change in your > >> setup (i.e. is if_ovpn use new, or did you update either kernel > >> or userspace or ? > > > > I updated the system on the date displayed by 'uname -a'. > > This included both base system and all installed ports; > > including openvpn. I normally leave the system running Xorg, > > and I would find the system in a "locked-up" blank-screen > > saver state. I assumed I was having a Xorg/drm-kmod problem, > > so I shut Xorg down last night. The above panic was waiting > > for me this morning. The panic happens every night. > > > > Note , I don't use if_ovpn. This a client over a tun0 device > > through wlan0. > > > The backtrace contradicts you, but DCO is relatively transparent, > so it’s quite possible you didn’t notice. It defaults to being > enabled, and ought to just work. Certainly, possible as I only quickly reviewed the dump. The kernel is a custom kernel. I don't recall adding a "device opvn" line. Perhaps, starting openvpn autoloads a kernel module. I'll need to check when I get home. > >> > >> Do you have the full core dump to poke at? > >> > > > > Yes, I do, but it's on a home system. I can put it up on > > my kargl@freefall later tonight (in 10-ish hours). I'll > > include the dmesg.boot so you have some idea about the > > hardware. > > > That’d be very helpful, thanks. > I'll ping you off list when it's available. -- Steve