Re: Kernel boots failed after Sept 12 (main-n289064-0d022baa047a)
Date: Sun, 20 Sep 2026 06:50:29 UTC
On Fri, Sep 18, 2026 at 7:07 PM Adrian Chadd <adrian@freebsd.org> wrote: > Did i915 module and kernel abi change? You may need to uninstall i915, > rebuild / boot kernel, and rebuild i915 / drm-kmod from scratch. > > > -a > Thanks! I never considered this simple potential possibility. I usually don't install rebuilt kmods until the kernel is installed, so I can easily boot the old one if there are problems. I failed to consider that, in some cases, the new kernel could blow-up as soon as the kmod loaded and before it was ever used. Thanks so much for taking the time to look at this with all of the work you do on 803.11 and other stuff. Kevi > > On Fri, 18 Sept 2026 at 16:01, Kevin Oberman <rkoberman@gmail.com> wrote: > >> I have been unable to build a kernel that would boot to multi-user since >> almost a week ago. It looks like it is tied to lkpi: >> drmn0: successfully loaded firmware image 'i915/adlp_dmc.bin' >> drmn0: [drm] Finished loading DMC firmware i915/adlp_dmc.bin (v2.20) >> drmn0: [drm] [ENCODER:244:DDI B/PHY B] unusable PPS, disabling eDP >> Kernel page fault with the following non-sleepable locks held: >> exclusive sleep mutex lkpi-priv-dma (lkpi-priv-dma) r = 0 >> (0xfffff800080b2f20) locked @ >> /usr/src/sys/compat/linuxkpi/common/src/linux_pci.c:2117 >> stack backtrace: >> #0 0xffffffff80cce50c at witness_debugger+0x6c >> #1 0xffffffff80ccfe0c at witness_warn+0x4bc >> #2 0xffffffff811eb9c7 at trap_pfault+0x97 >> #3 0xffffffff811b8ea8 at calltrap+0x8 >> #4 0xffffffff8360927c at i915_gem_gtt_prepare_pages+0x3c >> #5 0xffffffff8378c281 at shmem_get_pages+0xe1 >> #6 0xffffffff837895e8 at __i915_gem_object_get_pages+0x38 >> #7 0xffffffff8361697a at i915_vma_pin_ww+0x11a >> #8 0xffffffff836173e6 at __i915_ggtt_pin+0x76 >> #9 0xffffffff837257f4 at __intel_context_do_pin_ww+0x474 >> #10 0xffffffff83725b6b at __intel_context_do_pin+0x3b >> #11 0xffffffff83727d0f at intel_engine_create_pinned_context+0xef >> #12 0xffffffff837284ed at intel_engines_init+0x5ed >> #13 0xffffffff83735cfe at intel_gt_init+0x17e >> #14 0xffffffff83607bdd at i915_gem_init+0x26d >> #15 0xffffffff83603ded at i915_driver_probe+0x8ed >> #16 0xffffffff80f3843b at linux_pci_attach_device+0x55b >> #17 0xffffffff80c92606 at device_attach+0x466 >> >> System is an AlderLake 2th Gen Intel(R) Core(TM) i5-1235U (2496.00-MHz >> K8-class CPU) >> >> While I can provide a core.txt file, to my inexperienced eyes, it looks >> corrupted. >> >> Kernel build cleanly, but several builds over the past 6 days have all >> failed. >> >> Any clues would be appreciated. >> -- >> Kevin Oberman, Part time kid herder and retired Network Engineer >> E-mail: rkoberman@gmail.com >> >> -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com