Date: Mon, 21 Aug 2023 11:53:13 -0700 From: Pete Wright <pete@nomadlogic.org> To: Mark Johnston <markj@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: kabylake + drm-515-kmod/drm-510-kmod hangs Message-ID: <05e489c4-ed6b-46f1-8650-1a3fb4ea1223@nomadlogic.org> In-Reply-To: <ZOOr--4YR-wHWZ-0@nuc> References: <76275772-a9c3-ed59-5fb3-47a13d2a69e6@nomadlogic.org> <ZOOr--4YR-wHWZ-0@nuc>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/21/23 11:24, Mark Johnston wrote: > > Does your system have the debug.debugger_on_panic sysctl set to 1? If > so, does setting it to 0 allow the system to reboot following the hang? > oh fantastic, yea that works - thanks for the heads up! > > Commit cedc82c0466a in src changed the layout of a structure used by a > stub in the GPU firmware kernel modules. If you rebuild the one(s) you > need from ports, does the problem persist? > > FWIW I had to do this: > > $ cd /usr/ports/graphics/gpu-firmware-intel-kmod > $ sudo make reinstall FLAVOR=kabylake bingo that was it. i missed that change, thanks for pointing that out Mark. I'm able to load the i915kms module now. next step is figuring out why the nvidia-drm module is causing a panic (this is one of those funky intel + nvidia GPU laptops). but i get a core on that, and having the intel gpu load allows me to run X at least. thanks everyone! -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?05e489c4-ed6b-46f1-8650-1a3fb4ea1223>