On 8/21/23 10:53, Cy Schubert wrote:
In message <76275772-a9c3-ed59-5fb3-47a13d2a6...@nomadlogic.org>, Pete
Wright w
rites:
hey there,
i've got a kabylake laptop that i've been using with drm-kmod for
several years without much hassle. after upgrading to a new CURRENT
this weekend I've found that when loading either the 510 or 515 drm-kmod
kernel modules my system will hang.
unfortunately i am not getting a panic or crash, the screen stops
updating and i am unable to ping or SSH into the system. interestingly
the capslock LED still toggles but doing a CTL+ALT+DEL does not seem to
do anything useful and i have to manually power cycle.
any tips for finding out what's going on? i've booted the system with
verbose dmesg output, and loaded the module with "kldload -v" but do not
get any useful output.
here's the uname:
FreeBSD colony 14.0-ALPHA2 FreeBSD 14.0-ALPHA2 amd64 1400096 #0
main-n264924-e2340276fc73: Sun Aug 20 21:28:44 PDT 2023
pete@colony:/usr/obj/usr/home/pete/git/freebsd/amd64.amd64/sys/GENERIC amd64
these are the log messages i see before the system locks up:
Aug 21 10:40:34 colony kernel: iic0: <I2C generic I/O> on iicbus0
Aug 21 10:40:35 colony kernel: drmn0: <drmn> on vgapci0
Aug 21 10:40:35 colony kernel: vgapci0: child drmn0 requested pci_enable_io
Aug 21 10:40:35 colony syslogd: last message repeated 1 times
Aug 21 10:40:35 colony kernel: [drm] Unable to create a private tmpfs
mount, hugepage support will be disabled(-19).
Aug 21 10:40:35 colony kernel: [drm] Got stolen memory base 0x4b800000,
size 0x4000000
Aug 21 10:40:35 colony kernel: lkpi_iic0: <LinuxKPI I2C> on drmn0
Aug 21 10:40:35 colony kernel: iicbus1: <Philips I2C bus> on lkpi_iic0
Aug 21 10:40:35 colony kernel: iic1: <I2C generic I/O> on iicbus1
Aug 21 10:40:35 colony kernel: lkpi_iic1: <LinuxKPI I2C> on drmn0
Aug 21 10:40:35 colony kernel: iicbus2: <Philips I2C bus> on lkpi_iic1
Aug 21 10:40:35 colony kernel: iic2: <I2C generic I/O> on iicbus2
Aug 21 10:40:35 colony kernel: lkpi_iic2: <LinuxKPI I2C> on drmn0
Aug 21 10:40:35 colony kernel: iicbus3: <Philips I2C bus> on lkpi_iic2
Aug 21 10:40:35 colony kernel: iic3: <I2C generic I/O> on iicbus3
Aug 21 10:40:35 colony kernel: lkpi_iic3: <LinuxKPI I2C> on drmn0
Aug 21 10:40:35 colony kernel: iicbus4: <Philips I2C bus> on lkpi_iic3
Aug 21 10:40:35 colony kernel: iic4: <I2C generic I/O> on iicbus4
cheers,
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
Rebuilding drm-51[05]-kmod after an update to LinuxKPI affecting the ABI
used by the drm modules is required. Typically I get a kernel panic on a
page fault when this occurs. Depending on how memory is laid out on your
system you may get a hang instead.
You need to install thew new kernel and world first. Disable xdm, gdm, any
other *dm, or simply not use startx. From a text console session rebuild
the drm port and reinstall it.
I use poudriere here. My procedure is to update the poudriere jail, rebuild
the port (-C option) and pkg upgrade -f or pkg install -f. Use this
approach if you use poudriere.
Thanks Cy, yes my local scripts ensure to update the ports tree, then
rebuild the drm-kmod module i'm using as a package. then i remove the
old pkg, install the freshly build one then reboot. this ensures my
kernel and drm modules match.
this is how i've been doing it for years on all my systems since we
started the work on the drm-kmod.
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
