From nobody Mon Aug 21 17:56:09 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RV0XD1dcwz4r6tN for ; Mon, 21 Aug 2023 17:56:12 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [66.165.241.226]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.nomadlogic.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RV0XC6dH2z4DYy for ; Mon, 21 Aug 2023 17:56:11 +0000 (UTC) (envelope-from pete@nomadlogic.org) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomadlogic.org; s=04242021; t=1692640570; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=+Wdo9UnLGx/DoM2Aj4pcqEokpx35FzdFmv0+L+Txw2I=; b=UJiKdIXOvFJXmn7GiomMJlq3REvcdCTgPU6zBEaMEc7F1XLytPUVVxXYRC5/PE/adgJfOO FPr06D6kVZTrFC1UoyFCvAuI5ET2b/URwcbrvCHRfA7hVMobytV/GkR3THH1byoYjdTxX7 77jxKeGuQQFU9iehIGUduH2BUSobdK0= Received: from [192.168.1.160] (cpe-24-24-168-214.socal.res.rr.com [24.24.168.214]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 04092928 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Mon, 21 Aug 2023 17:56:10 +0000 (UTC) Message-ID: Date: Mon, 21 Aug 2023 10:56:09 -0700 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.14.0 Subject: Re: kabylake + drm-515-kmod/drm-510-kmod hangs Content-Language: en-US To: Cy Schubert Cc: FreeBSD Current References: <76275772-a9c3-ed59-5fb3-47a13d2a69e6@nomadlogic.org> <20230821175329.2211337D@slippy.cwsent.com> From: Pete Wright In-Reply-To: <20230821175329.2211337D@slippy.cwsent.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4RV0XC6dH2z4DYy X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:29802, ipnet:66.165.240.0/22, country:US] On 8/21/23 10:53, Cy Schubert wrote: > In message <76275772-a9c3-ed59-5fb3-47a13d2a69e6@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: on iicbus0 >> Aug 21 10:40:35 colony kernel: drmn0: 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: on drmn0 >> Aug 21 10:40:35 colony kernel: iicbus1: on lkpi_iic0 >> Aug 21 10:40:35 colony kernel: iic1: on iicbus1 >> Aug 21 10:40:35 colony kernel: lkpi_iic1: on drmn0 >> Aug 21 10:40:35 colony kernel: iicbus2: on lkpi_iic1 >> Aug 21 10:40:35 colony kernel: iic2: on iicbus2 >> Aug 21 10:40:35 colony kernel: lkpi_iic2: on drmn0 >> Aug 21 10:40:35 colony kernel: iicbus3: on lkpi_iic2 >> Aug 21 10:40:35 colony kernel: iic3: on iicbus3 >> Aug 21 10:40:35 colony kernel: lkpi_iic3: on drmn0 >> Aug 21 10:40:35 colony kernel: iicbus4: on lkpi_iic3 >> Aug 21 10:40:35 colony kernel: iic4: on iicbus4 >> >> >> >> cheers, >> -pete >> >> -- >> Pete Wright >> pete@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 pete@nomadlogic.org @nomadlogicLA