Project

General

Profile

Actions
Copy link

Bug #10956

closed

Panic configuring LAGG+VLAN interfaces when using a kernel with ``INVARIANTS``.

Added by Louis B about 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Operating System
Target version:
2.5.2
Start date:
10/05/2020
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Force Exclusion
Affected Version:
2.5.0
Affected Architecture:
All

Description

In very recent snapshots I have big problems which seems lagg related. May be related to freebsd issue https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240609

Please have a look at the attached crash dump

Files

Download all files
textdump.tar(23).0 (74 KB) textdump.tar(23).0 Core dump related to lagg problem Louis B, 10/05/2020 12:56 AM
info(22).0 (438 Bytes) info(22).0 Info related to that Core dump Louis B, 10/05/2020 12:56 AM
Actions
Copy link
 #1

Updated by Jim Pingle about 4 years ago

  • Priority changed from High to Normal

That's due to INVARIANTS in the kernel which is only a temporary measure to gather information while other issues are being debugged. It's going to be removed shortly.

Actions
Copy link
 #2

Updated by Jim Pingle about 4 years ago

  • Status changed from New to Feedback
  • Affected Version changed from 2.5.x to 2.5.0

INVARIANTS has been removed from the kernel, try the next new snapshot.

Actions
Copy link
 #3

Updated by Louis B about 4 years ago

A few minutes ago I updated my system via the GUI to today 1250. The router did restart properly! and seems to work normally.

Actions
Copy link
 #4

Updated by Jim Pingle about 4 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link
 #5

Updated by Jim Pingle over 3 years ago

  • Status changed from Resolved to New
  • Target version changed from 2.5.0 to 2.5.2

A fix has been committed to FreeBSD, we will make sure it gets into 2.5.2.

Author: Gleb Smirnoff <glebius@FreeBSD.org>
Date:   Tue Dec 8 16:46:00 2020 +0000
    The list of ports in configuration path shall be protected by locks,
    epoch shall be used only for fast path.  Thus use LAGG_XLOCK() in
    lagg_[un]register_vlan.  This fixes sleeping in epoch panic.
    PR:             240609
    (cherry picked from commit e1074ed6a08033ee571b4bedb3ffe6049a4a7361)
Actions
Copy link
 #6

Updated by Jim Pingle over 3 years ago

  • Subject changed from Problems with laggs in recent snapshots to Panic configuring LAGG+VLAN interfaces when using a kernel with ``INVARIANTS``.
  • Release Notes changed from Default to Force Exclusion

Updating subject but excluding from release notes since it wouldn't affect any potential release, only debugging kernels sometimes present on development snapshots.

Actions
Copy link
 #7

Updated by Jim Pingle over 3 years ago

  • Status changed from New to Feedback

The relevant commit for this should be present on a build dated after this comment.

Given the barrier to testing this (requires compiling a custom kernel with INVARIANTS in it), we can just close it after a couple days if there is no feedback.

Testing that LAGG and LAGG+VLANs still work is likely sufficient.

Actions
Copy link
 #8

Updated by Jim Pingle over 3 years ago

  • Status changed from Feedback to Closed
Actions
Copy link

Also available in: Atom PDF