Re: kern/56561: cv_is_valid assertion failure in intel drm

[Patrick Welche <prlw1%talktalk.net@localhost>]

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

From: Patrick Welche <prlw1%talktalk.net@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/56561: cv_is_valid assertion failure in intel drm
Date: Mon, 7 Mar 2022 09:50:50 +0000

 I just observed the original cv_is_valid(cv) assertion as mentioned at
 the top of this bug on 9.99.93 of 1st March 2022.
 
 Just in case the line numbers changed:
 
 (gdb) thread apply all bt
 
 Thread 2.1 (<kvm>):
 #0  0xffffffff80222765 in cpu_reboot (howto=howto@entry=260, bootstr=bootstr@entry=0x0) at ../../../../arch/amd64/amd64/machdep.c:720
 #1  0xffffffff808af187 in kern_reboot (howto=howto@entry=260, bootstr=bootstr@entry=0x0) at ../../../../kern/kern_reboot.c:73
 #2  0xffffffff808f43ca in vpanic (fmt=0xffffffff80d8e4a8 "kernel %sassertion \"%s\" failed: file \"%s\", line %d ", ap=ap@entry=0xffffde013c59edc8) at ../../../../kern/subr_prf.c:290
 #3  0xffffffff80a701f7 in kern_assert (fmt=fmt@entry=0xffffffff80d8e4a8 "kernel %sassertion \"%s\" failed: file \"%s\", line %d ") at ../../../../../../lib/libkern/kern_assert.c:51
 #4  0xffffffff8087b1aa in cv_broadcast (cv=0xffffde014e40ab50) at ../../../../kern/kern_condvar.c:511
 #5  0xffffffff80a1a553 in linux___dma_fence_signal_wake (fence=0xffff969807f14a40, timestamp=<optimized out>) at ../../../../external/bsd/drm2/linux/linux_dma_fence.c:1176
 #6  0xffffffff8057e467 in signal_irq_work (work=0xffffde001faed1e8) at ../../../../external/bsd/drm2/dist/drm/i915/gt/intel_breadcrumbs.c:218
 #7  0xffffffff80a1f089 in irq_work_intr (cookie=<optimized out>) at ../../../../external/bsd/drm2/linux/linux_irq_work.c:74
 #8  0xffffffff808bdbd0 in softint_execute (s=5, l=0xffff969b483f24c0) at ../../../../kern/kern_softint.c:565
 #9  softint_dispatch (pinned=<optimized out>, s=5) at ../../../../kern/kern_softint.c:814
 #10 0xffffffff8021d7ff in Xsoftintr ()
 #11 0x07b77c698bd464af in ?? ()
 #12 0x07f77c298b9464ef in ?? ()
 Backtrace stopped: Cannot access memory at address 0xffffde013c59f000