From owner-freebsd-x11@freebsd.org Sun Dec 30 00:47:05 2018 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2C2731432222 for ; Sun, 30 Dec 2018 00:47:05 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [140.82.23.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.nomadlogic.org", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5A5678BEC1 for ; Sun, 30 Dec 2018 00:47:04 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from duke.gem.co (cpe-23-243-162-239.socal.res.rr.com [23.243.162.239]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 9347d9cc TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Sat, 29 Dec 2018 16:47:02 -0800 (PST) Subject: Re: FreeBSD-12 / i915 on librem13@purism - hang on suspend after update To: Dirk-Willem van Gulik , Niclas Zeising Cc: freebsd-x11@freebsd.org References: <900A88BB-4AD8-4641-912B-DD039F53064C@webweaving.org> From: Pete Wright Message-ID: <31ebd0be-5500-b6e1-538f-a98798c3d837@nomadlogic.org> Date: Sat, 29 Dec 2018 16:47:02 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <900A88BB-4AD8-4641-912B-DD039F53064C@webweaving.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 5A5678BEC1 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of pete@nomadlogic.org designates 140.82.23.70 as permitted sender) smtp.mailfrom=pete@nomadlogic.org X-Spamd-Result: default: False [-5.71 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[239.162.243.23.zen.spamhaus.org : 127.0.0.10]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; FROM_HAS_DN(0.00)[]; TAGGED_RCPT(0.00)[freebsd]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[nomadlogic.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: mail.nomadlogic.org]; NEURAL_HAM_SHORT(-0.92)[-0.923,0]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; IP_SCORE(-2.47)[ip: (-9.15), ipnet: 140.82.16.0/21(-4.57), asn: 20473(1.43), country: US(-0.08)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:20473, ipnet:140.82.16.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Dec 2018 00:47:05 -0000 On 12/29/18 2:26 PM, Dirk-Willem van Gulik wrote: > >> On 29 Dec 2018, at 22:18, Niclas Zeising 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@nomadlogic.org @nomadlogicLA