FreeBSD-12 / i915 on librem13 at purism - hang on suspend after update

[Pete Wright]

On 12/29/18 2:26 PM, Dirk-Willem van Gulik wrote:
>
>> On 29 Dec 2018, at 22:18, Niclas Zeising <zeising+freebsd at daemonic.se> wrote:
>> On 12/29/18 9:46 PM, Dirk-Willem van Gulik wrote:
>>> After a routine update to FreeBSD-12.0-RELEASE and a ports update -- I am getting hard hangs on suspend on a librem13 laptop with the i915 chipset (works fine until that point).
>>> Screen lit up but black; does not respond to the off-key/alt-F1/vty and not a peep on serial/network (so likely a fairly hard hang). Have tried both with and without letting it load the firmware.
>>> Does that ring a bell with anyone ? Any clever ways to debug such a hang ?
>>> FreeBSD-12.0
>>> drm-fbsd12.0-kmod-4.16.g20181215
>>> drm-kmod-g20181126
>>> gpu-firmware-kmod-g20180825
>> Which version did you upgrade from?  Which CPU and GPU do you have?
>  From 11.1. CPU is a Core i7 6500U (Skylake) with a Intel HD Graphics 520 card using the build in screen*.
>
>> Can you try drm-fbsd11.2-kmod (it works on 12.0), or drm-legacy-kmod?
> No luck there on either version.
>
> Dw
>
> full specs: https://puri.sm/products/librem-13/#specs
>
> pkg info
> 	drm-fbsd11.2-kmod-4.11g20181210
> 	gpu-firmware-kmod-g20181104
>
> kldstat -v
> ..
> 17    1 0xffffffff82c23000  120400 i915kms.ko (/boot/modules/i915kms.ko)
> 18    1 0xffffffff82d44000    74770 drm.ko (/boot/modules/drm.ko)
> 22    1 0xffffffff82ddd000    2283f i915_skl_huc_ver01_07_bin.ko (/boot/modules/i915_skl_huc_ver01_07_bin.ko)
> 23    1 0xffffffff82e00000    245d i915_skl_dmc_ver1_26_bin.ko (/boot/modules/i915_skl_dmc_ver1_26_bin.ko)

just to fully rule out the drm-kmod stuff, are you able to 
suspend/resume without loading that i915kms and firmware modules?  i 
have a skylake system where suspend/resume works, but it is not a laptop 
- so it's possible that it may be a regression in another subsystem 
(acpi maybe?).

another thing worth testing is changing your bios to boot in UEFI mode, 
or vice-versa.  i've had mixed results with that, and may help isolate 
where the potential bug is.

-pete


-- 
Pete Wright
pete at nomadlogic.org
@nomadlogicLA