Re: kern/56705: wapbl lockdebug panic during tcpdump run

[Taylor R Campbell <riastradh%NetBSD.org@localhost>]

The following reply was made to PR kern/56705; it has been noted by GNATS.

From: Taylor R Campbell <riastradh%NetBSD.org@localhost>
To: Hauke Fath <hauke%Espresso.Rhein-Neckar.DE@localhost>
Cc: gnats-bugs%NetBSD.org@localhost
Subject: Re: kern/56705: wapbl lockdebug panic during tcpdump run
Date: Sat, 12 Feb 2022 17:16:44 +0000

 [resending to cc gnats-bugs]
 
 I bet wapbl is a red herring.
 
 Can you do `show panic'?  If it says `kernel lock spinout', that means
 that something else was hogging the kernel lock and the attempt to
 acquire it in bdev_strategy via wapbl happens to be the one that got
 bored of waiting and panicked.
 
 Can you show `ps' output, and then `bt/a ffff...' for all of the lines
 with `>' on them?
 
 Can you get a crash dump?