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

[Greg Oster <oster%netbsd.org@localhost>]

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

From: Greg Oster <oster%netbsd.org@localhost>
To: gnats-bugs%netbsd.org@localhost, kern-bug-people%netbsd.org@localhost,
 gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost,
 Hauke Fath <hauke%Espresso.Rhein-Neckar.DE@localhost>
Cc: 
Subject: Re: kern/56705: wapbl lockdebug panic during tcpdump run
Date: Sat, 12 Feb 2022 15:35:16 -0600

 On 2022-02-12 15:25, Hauke Fath wrote:
 > The following reply was made to PR kern/56705; it has been noted by GNATS.
 > 
 > From: Hauke Fath <hauke%Espresso.Rhein-Neckar.DE@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc: kern-bug-people%NetBSD.org@localhost, gnats-admin%NetBSD.org@localhost
 > Subject: Re: kern/56705: wapbl lockdebug panic during tcpdump run
 > Date: Sat, 12 Feb 2022 22:21:43 +0100
 > 
 >   On Sat, 12 Feb 2022 18:15:01 +0000 (UTC), Martin Husemann wrote:
 >   >  On Sat, Feb 12, 2022 at 05:30:02PM +0000, Hauke Fath wrote:
 >   >  >  >  Can you get a crash dump?
 >   >  >
 >   >  >  swap on raid0b, so no.
 >   >
 >   >  Why "so no"? Have you tried?
 >   
 >   Well, the machine tried (and failed)... and a quick search comes up
 >   with <https://marc.info/?l=netbsd-port-i386&m=109042024503576>.
 >   
 
 kernel core dumps to swap on RAID 1 sets should be working.  If they 
 arn't, that's a bug.  (initial implementation was in 2007, with some 
 fixes in 2016... but perhaps crash dumps to RAID 1 swap isn't as widely 
 advertised as it might otherwise be...)
 
 Later...
 
 Greg Oster