Re: kern/53624 (dom0 freeze on domU exit)

[Emmanuel Dreyfus <manu%netbsd.org@localhost>]

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

From: Emmanuel Dreyfus <manu%netbsd.org@localhost>
To: Andreas Gustafsson <gson%gson.org@localhost>
Cc: gnats-bugs%NetBSD.org@localhost, Emmanuel Dreyfus <manu%netbsd.org@localhost>
Subject: Re: kern/53624 (dom0 freeze on domU exit)
Date: Wed, 5 Dec 2018 08:50:50 +0000

 On Wed, Dec 05, 2018 at 10:35:18AM +0200, Andreas Gustafsson wrote:
 > I reproduced the freeze using xenkernel411.   Here's some ddb output:
 > 
 >   db> ps
 >   PID    LID S CPU     FLAGS       STRUCT LWP *               NAME WAIT
 >   11125    1 3   0        80   ffffa30001f3f740           vnconfig fstcnt
 >   10492    1 3   0         0   ffffa300020c34e0           vnconfig biowait
 >   [...]
 >   0      126 3   0       200   ffffa300020834a0               vnd4 vndbp
 >   0      125 3   0       200   ffffa3000204e040               vnd3 fstchg
 >   0      124 3   0       200   ffffa30000ed1660               vnd2 vndbp
 >   0      123 3   0       200   ffffa30002031840               vnd1 fstchg
 >   0       66 3   0       200   ffffa3000088a8e0               vnd0 vndbp
 (...)
 > If there are other ddb commands I can run to help debug this, please
 > let me know.  I will try to keep the system at the ddb prompt for the
 > next 24 hours at least.
 
 PLease get a kernel backtrace for the processes of interest here:
 bt/a ffffa30001f3f740
 bt/a ffffa300020c34e0
 ...
 
 At some point, running a kernel with options LOCKDEBUG may help.
 
 
 -- 
 Emmanuel Dreyfus
 manu%netbsd.org@localhost