Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 05 Feb 2019 11:04:13 +0000
From:      bugzilla-noreply@freebsd.org
To:        x11@FreeBSD.org
Subject:   [Bug 217689] x11-drivers/xf86-video-intel: Panic since latest update
Message-ID:  <bug-217689-7141-YuuVZA1Bc8@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-217689-7141@https.bugs.freebsd.org/bugzilla/>
References:  <bug-217689-7141@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217689

--- Comment #14 from Friedrich Volkmann <bsd@volki.at> ---
(In reply to Niclas Zeising from comment #13)

I was using FBSD 11-STABLE and now upgraded to 12-STABLE. No significant
change...

I do not have any drm in the kernel config file. Upon starting X, i915kms.ko
and drm2.ko are automatically loaded. These are certainly taken from the
/boot/kernel directory, as the same thing happens when I load i915kms.ko in=
 the
console manually. The console gets black, so I can't ready any output nor w=
hat
I'm writing. But when I type "startx", the display mode changes into graphi=
cs
and it works. When I return to the console via ctrl-alt-F1 or terminating X=
, it
is black again.

/usr/src/UPDATING advises to:

1) add WITHOUT_DRM_MODULE=3Dt and WITHOUT_DRM2_MODULE=3Dt
but it doesn't say where to add them. In the kernel config they don't work.
After a quick web search, I've added them to /etc/make.conf, but I still ha=
ve
no Idea what they are doing.
2) "amd64 users should just install the drm-kmod port", but that ports inst=
alls
documentation only, no modules. So I installed drm-fbsd12.0-kmod (version:
4.16.g20181215) instead. But there seem to be numerous issues with that por=
t:

# kldload /boot/modules/i915kms.ko
link_elf_obj: symbol vt_fb_attach undefined
Warning: memory type linux leaked memory on destroy (2 allocations, 144 byt=
es
leaked).
linker_load_file: /boot/modules/drm.ko - unsupported file type
KLD i915kms.ko: depends on drmn - not available or version mismatch
linker_load_file: /boot/modules/i915kms.ko - unsupported file type
kldload: an error occurred while loading module /boot/modules/i915kms.ko.
Please check dmesg(8) for more details.

So I deinstalled that port and installed drm-legacy-kmod, but kldloading
/boot/modules/i915kms.ko has the same effect as /boot/kernel/i915kms.ko.

There's some output when the module is loaded, but I can't read it, because=
 it
immediately disappears. This is what's in /var/log/messages:
kernel: drmn0: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
kernel: drmn0: This code is obsolete abandonware. Install the
graphics/drm-legacy-kmod pkg
kernel: drmn0: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
kernel: drmn0: Deprecated code (to be removed in FreeBSD 13): drm2 drivers
kernel: drmn0: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
kernel: drmn0: This code is obsolete abandonware. Install the
graphics/drm-legacy-kmod pkg
kernel: drmn0: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
kernel: drmn0: Deprecated code (to be removed in FreeBSD 13): drm2 drivers
kernel: drmn0: <Intel Haswell (GT2 desktop)> on vgapci0
kernel: info: [drm] Memory usable by graphics device =3D 2048M
kernel: info: [drm] MTRR allocation failed.  Graphics performance may suffe=
r.
kernel: intel_iicbb0 on drmn0
kernel: iicbus0: <Philips I2C bus>error: [drm:pid2681:i915_write32] *ERROR*
Unknown unclaimed register before writing to c5100
kernel:  on iicbb0 addr 0xff
[...]
kernel: info: [drm] Initialized i915 1.6.0 20080730 for drmn0 on minor 0
kernel: info: [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off

Writing this, I realize that this has been closed. That's certainly ok, bec=
ause
it's not an x11-drivers issue but a kernel issue. I just wonder where the n=
ew
bug resides?

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217689-7141-YuuVZA1Bc8>