Folks, I built a GENERIC kernel "hot off the presses" as of the commits cited above. I am surprised that I'm still getting error messages in dmesg about:
- Firmware errors - i915/skl_dmc_ver1_27.bin: could not load binary firmware /boot/firmware/i915/skl_dmc_ver1_27.bin either (repeats) - drmn0: could not load firmware image 'i915/skl_dmc_ver1_27.bin' - drmn0: [drm] Failed to load DMC firmware...Disabling runtime power management - Wait, that sounds like...useful. Is that screen blanking and backlight shushing? - Also, I don't lilke false negatives in dmesg - I built arm-515-kmod from port (which worked) and made appropriate file and group edits, but even after reboot it didn't affect these messages - Stack trace in the VT: Replacement action. Shortly after "VT: Replacing driver "efifb" with new "fb"" I see a stack trace - exclusive sleep mutex vtdev.... locked at /usr/src/sys/dev/vt/vt_core.c:3260 - Now this just happened to be the file I was hacking so I was worried I'd intro'd a regression ;) But this is a generic kernel, so don't look at me :) - The trace ultimately shows frames involving i915_driver_(register|probe)...which suggests that maybe these two things are related. Line 3260 is where a mutex is sought as part of the replace routine. I think I've troubleshot this reasonably, is there some angle I've missed? I'd like to have a clean dmesg on my GENERIC before I start bolting in my Frankenstein ideas into a custom kernel. Thanks! Steven --- Public Key: 22BE39E2FA68D8BA8DC4B43A55A16D8CE2B036DE Messages from this account are considered the best-secured and most reliable. Send information regarding health, wealth, or requiring higher standards of security to this address. Sent with [Proton Mail](https://proton.me/mail/home) secure email.
