From nobody Mon Aug 21 18:24:59 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 4RV19X1MJmz4r8WP for ; Mon, 21 Aug 2023 18:25:04 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RV19W6lnpz4HtF for ; Mon, 21 Aug 2023 18:25:03 +0000 (UTC) (envelope-from markjdb@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qt1-x82c.google.com with SMTP id d75a77b69052e-40ff82320a7so24296541cf.3 for ; Mon, 21 Aug 2023 11:25:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692642303; x=1693247103; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:from:to:cc:subject:date:message-id :reply-to; bh=uMivFOJmPVLLzDd+B1nKVC8SmP+VGCPFQzDrNwNQWnk=; b=WFfGG0yFB2zu2g2ge1XFlo7kH6fcQL7hPfQ3hQ7OGyBOCZeuMW4HEPg+qVAygQ7JBM ZLz7yIQDQn2Il7yIA9FUHY/i7WbD3hed/JyDujlYWAFJoL0uRngNySYrRWZh88YY5Bif fRyCll3V8EQwZwXzzPrSIsbhNZzny2/XAgv0od1LUAAo8RBrp/XSBOPatt7BBk0GJh+i 7NPlxMgXwC5wIJS1n5obBBa4Kg4q/pX2Z5SJJnUaeuPAihjtmXWCjDDQjQKhHG4T/O6Q ZIBzrD6Jty3MURaUaiRRxXFmLe278zKYLo/X7mUgE+mVgPRtKFWBBYHoso302Xvk/CfR qPYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692642303; x=1693247103; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=uMivFOJmPVLLzDd+B1nKVC8SmP+VGCPFQzDrNwNQWnk=; b=bAtuX2sJpj6kO+gFv+G0rUqNZFjjGoLHrej+fuTKql59Uls+zO+qetQzOCRe7AE7xc yVogemhC6Hc4VgmTWAF8tcpNlql2sxXN9rIgXA6ZLleS7YROIwkccQYxyOka1vr95nXg C3Y64Z2F7uuWwjvtEbV0gWKpU7i0NZgBmtCXe06VqaPrYDe4LUwxeWBSvmDZB/1pLFkA 9/tKhargRy2ZggGZoXyAsP1wf5bVtsuJgqa3GR8J+HuBDFeGWvl6QiKFSIqv4Y+pbUy2 gzAsLjO2Mkj4keW12kMxv7rzusL3J/WSH9c6KAzBPm/Xejoju9jLtrz4gMOKWicEtoMF +etQ== X-Gm-Message-State: AOJu0Yya6d7+0fdFnUzEeau3z0Io16oSt5TA8AxhM8Eh/CWxRvJHsgIf OKRD73I8vwgvn+IbmoH/HXa8j5ps8S8= X-Google-Smtp-Source: AGHT+IF8emZPmB2Kx86ivVDnFoeVPbPncMI8HAOZROFwDMw0HNiAWAFyIAKsDJPAyGkJgRAhX0IiOA== X-Received: by 2002:a05:622a:1a81:b0:403:affb:57ac with SMTP id s1-20020a05622a1a8100b00403affb57acmr9689665qtc.19.1692642303006; Mon, 21 Aug 2023 11:25:03 -0700 (PDT) Received: from nuc (192-0-220-237.cpe.teksavvy.com. [192.0.220.237]) by smtp.gmail.com with ESMTPSA id y10-20020ac83e8a000000b00403ff38d855sm2547983qtf.4.2023.08.21.11.25.01 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 21 Aug 2023 11:25:02 -0700 (PDT) Date: Mon, 21 Aug 2023 14:24:59 -0400 From: Mark Johnston To: Pete Wright Cc: FreeBSD Current Subject: Re: kabylake + drm-515-kmod/drm-510-kmod hangs Message-ID: References: <76275772-a9c3-ed59-5fb3-47a13d2a69e6@nomadlogic.org> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <76275772-a9c3-ed59-5fb3-47a13d2a69e6@nomadlogic.org> X-Rspamd-Queue-Id: 4RV19W6lnpz4HtF 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:15169, ipnet:2607:f8b0::/32, country:US] On Mon, Aug 21, 2023 at 10:44:28AM -0700, Pete Wright wrote: > 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. 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? > 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. 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