Re: kernel diagnostic assertion "psl == 0" failed

["Mathew, Cherry G." <cherry%zyx.in@localhost>]

On September 12, 2018 10:25:34 PM GMT+08:00, SAITOH Masanobu <msaitoh%execsw.org@localhost> wrote:
> Hi.
>
>I got a panic on a dom0 while running ./build.sh on a domU's
>NetBSD-current:
>
>> [ 1293.1834301] panic: kernel diagnostic assertion "psl == 0" failed:
>file "../../../../arch/xen/x86/xen_intr.c", line 76
>> [ 1293.1834301] cpu0: Begin traceback...
>> [ 1293.1834301] vpanic() at netbsd:vpanic+0x152
>> [ 1293.1834301] kern_assert() at netbsd:kern_assert+0x48
>> [ 1293.1834301] spllower() at netbsd:spllower+0xbf
>> [ 1293.1834301] mutex_exit() at netbsd:mutex_exit+0x14e
>> [ 1293.1834301] evtchn_do_event() at netbsd:evtchn_do_event+0x362
>> [ 1293.1834301] do_hypervisor_callback() at
>netbsd:do_hypervisor_callback+0x196
>> [ 1293.1834301] hypervisor_callback() at
>netbsd:hypervisor_callback+0xb2
>> [ 1293.1834301] Xresume_xenev6() at netbsd:Xresume_xenev6+0x49
>> [ 1293.1834301] --- interrupt ---
>> [ 1293.1834301] Xspllower() at netbsd:Xspllower+0xe
>> [ 1293.1834301] trap() at netbsd:trap+0x819
>> [ 1293.1834301] --- trap (number 3) ---
>> [ 1293.1834301] 74450523e77a:
>> [ 1293.1834301] cpu0: End traceback...
>> [ 1293.1834301] Mutex error: mutex_vector_enter,525: assertion
>failed: !cpu_intr_p()
>> 
>> [ 1293.1834301] lock address : 0xffffb1000740ef78 type     :    
>sleep/adaptive
>> [ 1293.1834301] initialized  : 0xffffffff8081ef4e
>> [ 1293.1834301] shared holds :                  0 exclusive:         
>        0
>> [ 1293.1834301] shares wanted:                  0 exclusive:         
>        0
>> [ 1293.1834301] current cpu  :                  0 last held:         
>        0
>> [ 1293.1834301] current lwp  : 0xffffb1000a71c480 last held:
>000000000000000000
>> [ 1293.1834301] last locked  : 0xffffffff80835ef4 unlocked*:
>0xffffffff80835f25
>> [ 1293.1834301] owner field  : 000000000000000000 wait/spin:         
>      0/0
>> 
>> [ 1293.1834301] Turnstile chain at 0xffffffff80e296b0.
>> [ 1293.1834301] => No active turnstile for this lock.
>
>Is this known problem?
>
>Both dom0's kernel and domU's kernel are from yesterday's -current
>source.

Hi - do you have a dmesg please to share? I'm trying to understand if this is related to my last two commits.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.