Project

General

Profile

Actions

Regression #16980

closed

26.07 snapshot panics when WireGuard loads with IIMB enabled

Added by RED SKULL 21 days ago. Updated 19 days ago.

Status:
Resolved
Priority:
Very High
Category:
Upgrade
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Release Notes:
Force Exclusion
Affected Plus Version:
26.07
Affected Architecture:
amd64

Description

I am seeing a repeatable kernel panic after upgrading from the July 27 26.07 snapshot to the July 30 snapshot.

My Working build :
FreeBSD 16.0-CURRENT #60
plus-RELENG_26_07-n256574-9432836c3070

Broken build (this came out today) :
FreeBSD 16.0-CURRENT #65
plus-RELENG_26_07-n256582-d1a90af75647

System :
amd64
WireGuard configured
IIMB crypto enabled

The system boots, starts restoring/configuring packages, and then panics when WireGuard is loaded by ifconfig. This has happened twice on two separate install attempts.

Backtrace :
crypto_freesession() at crypto_freesession+0x1c
wg_module_event_handler() at wg_module_event_handler+0x134
module_register_init() at module_register_init+0x9c
linker_load_module() at linker_load_module+0xdb8
kern_kldload() at kern_kldload+0x165
sys_kldload() at sys_kldload+0x67

The fault is a page fault at address 0x0. The active process is ifconfig, launched by php_wg.

WireGuard and IIMB both work normally on the previous #60 build. The crash happens while the WireGuard module is loading, before any tunnel traffic starts.

Expected : WireGuard should load and the existing tunnels should come up normally.

Reality : The system panics in crypto_freesession() and cannot complete boot on the new snapshot.

Known good : n256574-9432836c3070

Known bad : n256582-d1a90af75647

Full crash report is attached


Files

Actions #1

Updated by Jim Pingle 21 days ago

  • Assignee set to Kristof Provost
  • Target version set to 26.07

We're already aware and have been working on it.

You can disable IIMB until we have a fix available in another snapshot and everything else should be OK.

Actions #2

Updated by Jim Pingle 21 days ago

  • Release Notes changed from Default to Force Exclusion
Actions #3

Updated by RED SKULL 20 days ago

Jim Pingle wrote in #note-1:

We're already aware and have been working on it.

You can disable IIMB until we have a fix available in another snapshot and everything else should be OK.

Here to report that the latest base system (26.07.b.20260731.1233), release on 7/31, has resolved the regression.

Actions #4

Updated by Christopher Cope 19 days ago

  • Status changed from New to Resolved

RED SKULL wrote in #note-3:

Jim Pingle wrote in #note-1:

We're already aware and have been working on it.

You can disable IIMB until we have a fix available in another snapshot and everything else should be OK.

Here to report that the latest base system (26.07.b.20260731.1233), release on 7/31, has resolved the regression.

Thanks for confirming that for us!

I can also confirm it is working as expected on

26.07-BETA (amd64)
built on Fri Jul 31 20:02:00 UTC 2026
FreeBSD 16.0-CURRENT

I am marking it resolved.

Actions

Also available in: Atom