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
