On Sun, Apr 5, 2020 at 14:42 bch <brad.har...@gmail.com> wrote: > I have a system tracking netbsd-9. > > I recently rebooted it (after ~30-some days uptime) w latest kernel, > modules, userland and it faults before completing boot. > > To my eye it looks to be intelfb/drm/kms related, but I’m not certain, > haven’t been able to work around it yet. > > Here’s an initial select transcription of the kernel log and trace: > > ... > kern info: [drm] failed to find VBIOS tables > i915drmkms0: interrupting at ioapic0 pin 16 (i915drmkms0) > keen error: > [drm:(/usr/src/sys/external/bsd/drm/i915/i915_drv.c:636)i915_firmware_load_error_print > *ERROR* failed to load firmware i915/skl_dmc_ver1.bin (0) > ... > keen error: [drm:(/usr/.../intel_guc_loader.c:560)guc_fw_fetch] *ERROR* > Failed to fetch GuC firmware... > kern error: ... Failed to initialize GuC... > kern info: [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit > banging on pin 5 > intelfb0 at i915drmkms0 > intelfb0: framebuffer at 0xffffae8182ccc000, size 1920x1080, depth 32, > stride 7680 > ... > kern info: [drm] RC6 on > wsdisplay0 at intelfb0 kbdmux 1: console (default, vt100 emulation), using > wskbd0 > panic: init died (signal 0, exit 11) > cpu0: Begin traceback... > vpanic() at netbsd:vpanic+0x160 > ... > sys_exit() at netbsd:sys_exit+0x3d > syscall() at netbsd:syscall+0x157 > —- syscall (number 1) —- > 4652ba: > cpu0: End traceback... > fatal breakpoint trap in supervisor mode > trap type 1 code 0 rip 0xffffffff8021dd15 cs 0x8 rflags 0x202 cr2 > 0x7017f2e93000 I level 0 rsp 0xffffae81820d5df0 > curlwp 0xffffacc26fe53620 pid 1.1 lowest kstack 0xffffae81820d32c0 > Stopped in pid 1.1 (init) at netbsd:breakpoint+0x5: leave >
I no longer think this is (necessarily) drm/kms issue, but init dies no matter which kernel I’m using: a backup, the original install kernel, or a copy of a an otherwise working rescue kernel... Anybody else seeing this, or remembering anything from the last 30 or so days in netbsd-9 cvs that might correspond? -bch > >
