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

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Wed, Dec 05, 2018 at 08:40:00AM +0000, Andreas Gustafsson wrote:
> The following reply was made to PR kern/53624; it has been noted by GNATS.
> 
> From: Andreas Gustafsson <gson%gson.org@localhost>
> To: gnats-bugs%NetBSD.org@localhost
> Cc: Emmanuel Dreyfus <manu%netbsd.org@localhost>
> Subject: Re: kern/53624 (dom0 freeze on domU exit)
> Date: Wed, 5 Dec 2018 10:35:18 +0200
> 
>  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
>    [...]
>    db> call fstrans_dump
>    Fstrans locks by lwp:
>    [ 87719.6801535] 10492.1  (/) shared 1 cow 0
>    [ 87719.6801535] Fstrans state by mount:
>    [ 87719.6801535] /                state suspending
>    0
>    db>
>  
>  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.

Can you get a stack trace (tr/a) for the processes listed above ?

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--