Hi, I had a quick look and this code is confusing. I could not see what lock it's trying to get. Presumably you have a netbsd.gdb in the build directory (seems to be the way now). Could you feed it to gdb and try: "info line *execlists_update_context+0x1234" where 0x1234 is the actual offset shown in the backtrace.
Andrew On Thu, Dec 19, 2019 at 03:31:15PM +0000, Patrick Welche wrote: > Just tried NetBSD on a lapto that has what I think is a Kaybe lake > intel chip, and (no serial console - just copied off the screen): > > vpanic > snprintf > lockdebug_abort1 > mutex_enter > execlists_update_context > execlists_context_unqueue > gen8_emit_request > __i915_add_request > i915_gem_init_hw > i915_gem_init > i915_driver_load > drm_dev_register > drm_pci_attach > i915drmkms_attach_real > config_mountroot_thread > > (x/s panicstr doesn't show me much) > > ps shows 2 x configroot, 2 x idle. > > What does one look for in show locks? > > Lock 0 initialized at drm_dev_alloc, sleep/adaptive, no active turnstile > > > Lock 0 initialized at main, spin, holds 0 excl 1, wants 0 excl 1 > curcpu holds 1 wanted by 000000000000000 > Lock 1 initialized at logical_ring_init, spin, holds 0 excl 1, wants 0 excl 0 > wait/spin 0/1 > > > Cheers, > > Patrick