kldxref error when installing drm-next-kmod from ports 11.1

[Pete Wright]

On 03/06/2018 19:39, Tom Rushworth wrote:
> Hi All,
>
> I'm running X11 with screen saver and the i915kms graphics driver and
> they seem to work, however I got the following messages when installing
> drm-next-kmod from /usr/ports:
>
> Installing drm-next-kmod-4.11.g20180224...
> kldxref: error while reading
> //boot/modules/i915_bxt_huc_ver01_07_1398_bin.ko: Bad address
> kldxref: error while reading
> //boot/modules/i915_kbl_huc_ver02_00_1810_bin.ko: Bad address
> kldxref: error while reading
> //boot/modules/i915_skl_huc_ver01_07_1398_bin.ko: Bad address
>
> and I get them again when I install other kernel module (e.g. virtualbox
> kmods).
>
> The machine in question is a Compulab Airtop, CPU (from boot in
> /bar/log/messages):
>
> CPU: Intel(R) Xeon(R) CPU E3-1285L v4 @ 3.40GHz (3392.22-MHz K8-class CPU)
> Mar  5 07:45:01 maxwell kernel: Origin="GenuineIntel"  Id=0x40671
> Family=0x6  Model=0x47  Stepping=1
>
> and from Xorg.log.0:
>
>   9.042] (--) intel(0): Integrated Graphics Chipset: Intel(R) Iris Pro
> Graphics P6300
>
> # uname -a
> FreeBSD maxwell.mannynkapy.net 11.1-STABLE FreeBSD 11.1-STABLE #0
> r330126: Thu Mar  1 11:27:24 PST 2018
> tbr at maxwell:/usr/obj/usr/src/sys/MAXWELL  amd64
>
> The machine has 32G of memory.  I checked out the latest 11.1 STABLE
> kernel source, built a custom kernel from GENERIC by dropping the
> network devices not present and the old ATA disk stuff, then checked out
> the latest stable ports and did "make install" in
> /usr/ports/graphics/drm-next-kmod.
>
> As I said, it seems to be running reasonably well, can anyone tell me if
> I should worry about the error messages?
>
> I have the entire "make install" output saved via the "script" command
> if more details are needed.
>
> Thanks in advance for any info or pointers.

I've been seeing this as well - i believe it is mostly harmless since it 
just relates to the HUC firmware blobs for i915 graphics. I'm not %100 
clear as to why that error is happening, but I believe it should be 
fixed with the next release of the gpu-firmware-kmod packages.

-pete

>
> Regards,
>

-- 
Pete Wright
pete at nomadlogic.org
@nomadlogicLA