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

[Joerg Sonnenberger <joerg%bec.de@localhost>]

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

From: Joerg Sonnenberger <joerg%bec.de@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
	netbsd-bugs%netbsd.org@localhost, Hauke Fath <hauke%Espresso.Rhein-Neckar.DE@localhost>
Subject: Re: kern/56705: wapbl lockdebug panic during tcpdump run
Date: Sat, 12 Feb 2022 23:36:08 +0100

 Am Sat, Feb 12, 2022 at 05:30:02PM +0000 schrieb Hauke Fath:
 > 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 18:28:14 +0100
 > 
 >  On Sat, 12 Feb 2022 17:20:01 +0000 (UTC), Taylor R Campbell wrote:
 >  >  Can you show [...]
 >  
 >  As mentioned, the USB console keyboard is dead at that point. I have 
 >  found and attached a ps2 keyboard (fortunately, the board is that 
 >  traditional), and am working on reproducing the panic.
 
 ddb.commandonenter can be used if you can reproduce it.
 
 Joerg