Re: kern/60703: panic: LOCKDEBUG: Mutex error: kmem_intr_free,397: allocation contains active lock

["Manuel Bouyer via gnats" <gnats-admin%NetBSD.org@localhost>]

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

From: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Subject: Re: kern/60703: panic: LOCKDEBUG: Mutex error: kmem_intr_free,397:
 allocation contains active lock
Date: Thu, 10 Sep 2026 16:14:06 +0200

 On Wed, Sep 09, 2026 at 01:25:00PM +0000, Manuel.Bouyer%lip6.fr@localhost via gnats wrote:
 > 	This is a desktop workstation. At the time of the panic I had one
 > 	application running, reading data from a USB device and printing
 > 	line of text in its xterm, in a tight loop (top did show high CPU 
 > 	usage for X, xterm, system and interrupts.
 > 	At some point the system paniced, crash on the core dump shows:
 > armandeche# crash -M netbsd.3.core -N netbsd.3
 > Crash version 11.0_STABLE, image version 11.0_STABLE.
 > System panicked: LOCKDEBUG: Mutex error: kmem_intr_free,397: allocation contains active lock
 
 I got a similar panic on my laptop:
 System panicked: LOCKDEBUG: Mutex error: kmem_intr_free,397: allocation contains active lock
 Backtrace from time of crash is available.
 crash> tr
 __kernel_end() at 0
 kern_reboot() at kern_reboot+0x93
 vpanic() at vpanic+0x17b
 panic() at printf_nostamp
 lockdebug_abort1() at lockdebug_more.part.0
 kmem_intr_free() at kmem_intr_free+0xb4
 gen8_ppgtt_create() at gen8_ppgtt_create+0x277
 i915_ppgtt_create() at i915_ppgtt_create+0x2b
 i915_gem_create_context() at i915_gem_create_context+0x34f
 i915_gem_context_create_ioctl() at i915_gem_context_create_ioctl+0x6d
 drm_ioctl() at drm_ioctl+0x23d
 drm_ioctl_shim() at drm_ioctl_shim+0x32
 sys_ioctl() at sys_ioctl+0x4ca
 syscall() at syscall+0x9d
 --- syscall (number 54) ---
 
 very light load, only a few xterm, firefox was starting (crashed before it
 could open a window).
 The hardware is:
 cpu0: "Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz"
 cpu0: Intel 7th or 8th gen Core (Kaby Lake, Coffee Lake) or Xeon E (Coffee Lake) (686-class), 2712.00 MHz
 cpu0: CPU base freq 2700000000 Hz
 cpu0: CPU max freq 3100000000 Hz
 cpu0: TSC freq CPUID 2712000000 Hz
 cpu0: family 0x6 model 0x8e stepping 0x9 (id 0x806e9)
 
 
 i915drmkms0 at pci0 dev 2 function 0: Intel HD Graphics 620 (GT2) (rev. 0x02)
 [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 [drm] Driver supports precise vblank timestamp query.
 i915drmkms0: interrupting at msi7 vec 0 (i915drmkms0)
 i915drmkms0: notice: Failed to load DMC firmware i915/kbl_dmc_ver1_04.bin. Disabling runtime power management.
 [drm] Initialized i915 1.6.0 20200114 for i915drmkms0 on minor 0
 intelfb0 at i915drmkms0
 [drm] DRM_I915_DEBUG enabled
 [drm] DRM_I915_DEBUG_GEM enabled
 
 -- 
 Manuel Bouyer <bouyer%antioche.eu.org@localhost>
      NetBSD: 26 ans d'experience feront toujours la difference
 --