From nobody Sun Apr 9 18:55:58 2023 X-Original-To: freebsd-stable@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 4PvhDH0rpDz446FX for ; Sun, 9 Apr 2023 18:57:03 +0000 (UTC) (envelope-from ota@j.email.ne.jp) Received: from hsmtpd-fgn.xspmail.jp (hsmtpd-fgn.xspmail.jp [210.130.137.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4PvhDC0NmZz4456 for ; Sun, 9 Apr 2023 18:56:58 +0000 (UTC) (envelope-from ota@j.email.ne.jp) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=j.email.ne.jp header.s=x01 header.b=Ab7aMmt3; spf=pass (mx1.freebsd.org: domain of ota@j.email.ne.jp designates 210.130.137.13 as permitted sender) smtp.mailfrom=ota@j.email.ne.jp; dmarc=pass (policy=none) header.from=j.email.ne.jp DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1681066608; d=j.email.ne.jp; s=x01; i=ota@j.email.ne.jp; h=content-transfer-encoding:content-type:mime-version:message-id:subject:to: from:date:from; bh=f4z7aFcxP0CDL7H0QqxciLKTipQsJa1WBwp1xTE/oPE=; b=Ab7aMmt3t8Ru4/4nor5S8j1lEVUF2olN59fkEqyX1c6kjg23ZvGkiFRgQPRA+GPKggVy7X3ehvpx1 Gg8BkKCKeDf0cNTvgDN8Awx1+O8sC22M9EygXCQSBjk+fZPsG5JBuamgW8zYGv8NIb1AoVlv2Mjk1y 1Z1GImvbTcoMU+ihXoQW+qWIRZt/nkAiZkheDyCKfO+j8qQGe5MxZvLUM5QnMvtehpyUgytH1qBQym YhI+tcUC9gkjt4yAyGU8O79LSVTc7/ULsuK3GMjbwq5TBhSWPBqIT5yxWD5fQxg6HFOZp5ab6DZRyg wqAP70P2m6op23K0mn7FCYbjhbNcGcA== X-Country-Code: US Received: from a315-53 (pool-173-63-27-212.nwrknj.fios.verizon.net [173.63.27.212]) by hsmtpd-out-1.asahinet.cluster.xspmail.jp (Halon) with ESMTPA id 827b4e1e-3d38-4b40-80f5-301a8e62ccb1; Mon, 10 Apr 2023 03:56:48 +0900 (JST) Date: Sun, 9 Apr 2023 14:55:58 -0400 From: Yoshihiro Ota To: freebsd-stable@FreeBSD.org Subject: FreeBSD 13.2-RELEASE started failing to load i915kms.ko after upgrade from RC5 Message-Id: <20230409145558.c7cf0e9bb11f13d41f4f6031@j.email.ne.jp> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; i386-portbld-freebsd12.2) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.50 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.995]; DMARC_POLICY_ALLOW(-0.50)[j.email.ne.jp,none]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:210.130.137.0/27]; R_DKIM_ALLOW(-0.20)[j.email.ne.jp:s=x01]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; ASN(0.00)[asn:2497, ipnet:210.130.0.0/16, country:JP]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[j.email.ne.jp:+]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4PvhDC0NmZz4456 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N Hi, I've been following releng/13.2 since it was branched. I use amd64 arch for this. I had built kernel modules during BETA/RC period. The above i915kms had worked until RC5. I had not built RC6 locally and picked up RELEASE on releng/13.2. After upgrading from RC5 to 13.2-RELEASE, the kernel started failing to load i915mks. This time, all kmod started failing such as one for virtual box, too. I thought I would need to rebuild all kernel modules, and thus started. However, even after rebuilding kernel modules several times, i915kms doesn't load properly. While new virtual box kmod works, I think my build environment isn't a problem. I cannot make i915kms back in working condition. I also updated /usr/ports and rebuilt few times but yet not successful. I get the following error: ``` linker_load_file: /boot/modules/i915kms.ko - unsupported file type ``` Any hints or same experiences? Hiro From nobody Sun Apr 9 21:45:05 2023 X-Original-To: freebsd-stable@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 4PvlyW0SRSz44KKb for ; Sun, 9 Apr 2023 21:45:23 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yw1-x1134.google.com (mail-yw1-x1134.google.com [IPv6:2607:f8b0:4864:20::1134]) (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 4PvlyV5Rmvz3H5c for ; Sun, 9 Apr 2023 21:45:22 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yw1-x1134.google.com with SMTP id 00721157ae682-54ee108142eso73783927b3.2 for ; Sun, 09 Apr 2023 14:45:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1681076722; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=cXd8JNtmrrK6dxytwHQVapzRTNPVO946d8yb+qjs/pc=; b=H+SwsAtOL0u98eoXtfgFI/pgSNkTKx1Ztqu8yOpCmTfOVY+0WOsadbyrCc0z98JWP+ 1LwEfVll/tEZ2RF3uQ8oGhrK6XH7tw2++YiMKp2ZubKmndV8xl1Pjhx1/wiD0Xq4V9s4 Ip3Mh0yfbxUvcNrzV9RRQFynFOBwRRlRhlacpcKtekTQpdm5b7iAKuVqsKUMEdEa60hv mUw/mxma129R4BM9QeQdAVNeIBhaurYXIclzm32TuBv1No585RP3uaLT0/RFWHficRfd zqnT8L9Z3/EV0NanJgrhaZ9/J7S5ZHcXudxz2UhxHokewuGVB9jYVIiF1YHkuVrVUCZO TcQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681076722; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=cXd8JNtmrrK6dxytwHQVapzRTNPVO946d8yb+qjs/pc=; b=y8BGswuto4gJC1NXpmwyTLGnRgyoT0xM0WApXWLIpjCuwBtfINQRkCjy8Wt7rP9iHI eQqVBzFXp08/Dl6xV+jy54iBOwSAg045oBlFTWK52b/S8VoCBsPcROPmgcNhvMFqbTKS ZIDE8nZpH2zX5+zjPV2zbz8ryDqylDD/ZcBByvLp2o0BQ+y4dzh4Yt+WWhs7csMPDHDD OxGPrIs0Jlekvsrd/A29m0LVEaj/fLjvDXzxlzuS13BJzZsLpzkkNe99Ixdphq2yuOcI C78GZoFivH8tZFc1uwf/5DCv/q0tOOa6npSq/ae9MQoMZTnJtgwJ+IC3jJnunQYCdFAp V+gw== X-Gm-Message-State: AAQBX9e/ksIOp3N0RDUytEo3KMKE4LfatIKHd85JP2tafB8npV63ply9 Rkz1sLxwgmb+5Q3qtt/GPy+psuX4jOCmNsIfQH3U8Sls06U= X-Google-Smtp-Source: AKy350YsY4pcgYFAl8UwOd37yFQgAoxO9o1BWvDVC0YnHWoFbylm9SppbWvnEsP3Ofz35s/U0dhZLC4JtGLcRBbCakQ= X-Received: by 2002:a81:a904:0:b0:54f:2b65:a865 with SMTP id g4-20020a81a904000000b0054f2b65a865mr569456ywh.8.1681076721854; Sun, 09 Apr 2023 14:45:21 -0700 (PDT) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 References: <20230409145558.c7cf0e9bb11f13d41f4f6031@j.email.ne.jp> In-Reply-To: <20230409145558.c7cf0e9bb11f13d41f4f6031@j.email.ne.jp> From: Kevin Oberman Date: Sun, 9 Apr 2023 14:45:05 -0700 Message-ID: Subject: Re: FreeBSD 13.2-RELEASE started failing to load i915kms.ko after upgrade from RC5 To: Yoshihiro Ota Cc: freebsd-stable@freebsd.org Content-Type: multipart/alternative; boundary="000000000000d8b0c405f8ee2cbc" X-Rspamd-Queue-Id: 4PvlyV5Rmvz3H5c X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000d8b0c405f8ee2cbc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Apr 9, 2023 at 11:57=E2=80=AFAM Yoshihiro Ota w= rote: > Hi, > > I've been following releng/13.2 since it was branched. > I use amd64 arch for this. > > I had built kernel modules during BETA/RC period. > The above i915kms had worked until RC5. > I had not built RC6 locally and picked up RELEASE on releng/13.2. > > After upgrading from RC5 to 13.2-RELEASE, the kernel started failing to > load i915mks. > This time, all kmod started failing such as one for virtual box, too. > > I thought I would need to rebuild all kernel modules, and thus started. > However, even after rebuilding kernel modules several times, i915kms > doesn't load properly. > While new virtual box kmod works, I think my build environment isn't a > problem. > > I cannot make i915kms back in working condition. > I also updated /usr/ports and rebuilt few times but yet not successful. > I get the following error: > ``` > linker_load_file: /boot/modules/i915kms.ko - unsupported file type > ``` > > Any hints or same experiences? > > Hiro > You need to rebuild the port when hte kernel is updated on hte system that has the same system source files as the one that it is being installed on. I add drm-515-kmod to PORTS_MODULES to be sure that this always happens. Add: PORTS_MODULES+=3D graphics/drm-515-kmod This should, perhaps, be graphics/drm-510-kmod on 13-STABLE since 13.2, but I'm not sure. Depends on the merge of some code that I thought was in STABLE back at some point in 1.1-STABLE. --=20 Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --000000000000d8b0c405f8ee2cbc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sun, Apr 9, 2023 at 11:57=E2= =80=AFAM Yoshihiro Ota <ota@j.email= .ne.jp> wrote:
Hi,

I've been following releng/13.2 since it was branched.
I use amd64 arch for this.

I had built kernel modules during BETA/RC period.
The above i915kms had worked until RC5.
I had not built RC6 locally and picked up RELEASE on releng/13.2.

After upgrading from RC5 to 13.2-RELEASE, the kernel started failing to loa= d i915mks.
This time, all kmod started failing such as one for virtual box, too.

I thought I would need to rebuild all kernel modules, and thus started.
However, even after rebuilding kernel modules several times, i915kms doesn&= #39;t load properly.
While new virtual box kmod works, I think my build environment isn't a = problem.

I cannot make i915kms back in working condition.
I also updated /usr/ports and rebuilt few times but yet not successful.
I get the following error:
```
linker_load_file: /boot/modules/i915kms.ko - unsupported file type
```

Any hints or same experiences?

Hiro
=C2=A0
You need to rebuild t= he port when hte kernel is updated on hte system that has the same system s= ource files as the one that it is being installed on.

I add drm-515-kmod to PORTS_MODULES to be sure that this alwa= ys happens. Add:
PORTS_MODULES+=3D graphics/drm-515-kmod
This should, perhaps, be graphics/drm-510-kmod on 13-STABLE sin= ce 13.2, but I'm not sure. Depends on the merge of some code that I tho= ught was in STABLE back at some point in 1.1-STABLE.
--
Kevin Oberman, Part time kid herder and= retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D= 03FB98AFA78E3B78C1694B318AB39EF1B055683
=
--000000000000d8b0c405f8ee2cbc-- From nobody Mon Apr 10 00:21:36 2023 X-Original-To: freebsd-stable@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 4PvqYT3tqCz44VTk for ; Mon, 10 Apr 2023 00:27:25 +0000 (UTC) (envelope-from li-fbsd@citylink.dinoex.sub.org) Received: from uucp.dinoex.org (uucp.dinoex.org [IPv6:2a0b:f840::12]) (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 "uucp.dinoex.sub.de", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PvqYR4N2fz3Pgg for ; Mon, 10 Apr 2023 00:27:23 +0000 (UTC) (envelope-from li-fbsd@citylink.dinoex.sub.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of li-fbsd@citylink.dinoex.sub.org designates 2a0b:f840::12 as permitted sender) smtp.mailfrom=li-fbsd@citylink.dinoex.sub.org; dmarc=none Received: from uucp.dinoex.org (uucp.dinoex.org [IPv6:2a0b:f840:0:0:0:0:0:12]) by uucp.dinoex.org (8.17.1/8.17.1) with ESMTPS id 33A0R6mj002542 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Mon, 10 Apr 2023 02:27:06 +0200 (CEST) (envelope-from li-fbsd@citylink.dinoex.sub.org) X-MDaemon-Deliver-To: Received: (from uucp@localhost) by uucp.dinoex.org (8.17.1/8.17.1/Submit) with UUCP id 33A0R6Wv002541 for freebsd-stable@freebsd.org; Mon, 10 Apr 2023 02:27:06 +0200 (CEST) (envelope-from li-fbsd@citylink.dinoex.sub.org) Received: from admn.intra.daemon.contact (localhost [127.0.0.1]) by admn.intra.daemon.contact (8.17.1/8.17.1) with ESMTPS id 33A0LgbW062798 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Mon, 10 Apr 2023 02:21:43 +0200 (CEST) (envelope-from li-fbsd@citylink.dinoex.sub.org) Received: from intra.daemon.contact (news@localhost) by admn.intra.daemon.contact (8.17.1/8.17.1/Submit) with NNTP id 33A0LaMX062794 for freebsd-stable@freebsd.org; Mon, 10 Apr 2023 02:21:36 +0200 (CEST) (envelope-from li-fbsd@citylink.dinoex.sub.org) X-Authentication-Warning: admn.intra.daemon.contact: news set sender to li-fbsd@citylink.dinoex.sub.org using -f From: "Peter 'PMc' Much" X-Newsgroups: m2n.fbsd.stable Subject: Re: FreeBSD 13.2-RELEASE started failing to load i915kms.ko after upgrade from RC5 Date: Mon, 10 Apr 2023 00:21:36 -0000 (UTC) Message-ID: References: <20230409145558.c7cf0e9bb11f13d41f4f6031@j.email.ne.jp> Injection-Date: Mon, 10 Apr 2023 00:21:36 -0000 (UTC) Injection-Info: admn.intra.daemon.contact; logging-data="50585"; mail-complaints-to="usenet@citylink.dinoex.sub.org" User-Agent: slrn/1.0.3 (FreeBSD) To: freebsd-stable@freebsd.org X-Milter: Spamilter (Reciever: uucp.dinoex.org; Sender-ip: 0:0:2a0b:f840::; Sender-helo: uucp.dinoex.org;) X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (uucp.dinoex.org [IPv6:2a0b:f840:0:0:0:0:0:12]); Mon, 10 Apr 2023 02:27:09 +0200 (CEST) X-Spamd-Result: default: False [-2.98 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.979]; FORGED_SENDER(0.30)[pmc@citylink.dinoex.sub.org,li-fbsd@citylink.dinoex.sub.org]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; TO_DN_NONE(0.00)[]; R_DKIM_NA(0.00)[]; DMARC_NA(0.00)[sub.org]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; RCVD_COUNT_THREE(0.00)[4]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; ASN(0.00)[asn:205376, ipnet:2a0b:f840::/32, country:DE]; TO_MATCH_ENVRCPT_ALL(0.00)[]; HAS_XAW(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; FROM_NEQ_ENVFROM(0.00)[pmc@citylink.dinoex.sub.org,li-fbsd@citylink.dinoex.sub.org] X-Rspamd-Queue-Id: 4PvqYR4N2fz3Pgg X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org On 2023-04-09, Yoshihiro Ota wrote: > Hi, > > I've been following releng/13.2 since it was branched. > I use amd64 arch for this. > > I had built kernel modules during BETA/RC period. > The above i915kms had worked until RC5. > I had not built RC6 locally and picked up RELEASE on releng/13.2. [...] > Any hints or same experiences? This is a bit strange - I had that same issue between RC2 and RC3. And there the commit logs show that somebody did explicitely change the version number (from 1302000 to 1302001), for whatever reasons I didn't fully grok. It seems the modules do not like such a change, and have to be rebuilt. That version number is visible with pkg info: > Annotations : > FreeBSD_version: 1302000 It is also present in the base installation ... $ grep FreeBSD_version /usr/include/sys/param.h #define __FreeBSD_version 1302000 /* Master, propagated to newvers */ ... and in the kernel source: $ grep FreeBSD_version /usr/src/sys/sys/param.h #define __FreeBSD_version 1302000 /* Master, propagated to newvers */ And somewhere it lingers also in the kernel itself: $ strings /boot/kernel/kernel | grep 13020 1302000 From nobody Mon Apr 10 00:33:34 2023 X-Original-To: freebsd-stable@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 4Pvqhf64Dgz44VY5; Mon, 10 Apr 2023 00:33:38 +0000 (UTC) (envelope-from Mathias.Picker@virtual-earth.de) Received: from www94.your-server.de (www94.your-server.de [213.133.104.94]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Pvqhf4Ty6z3n7P; Mon, 10 Apr 2023 00:33:38 +0000 (UTC) (envelope-from Mathias.Picker@virtual-earth.de) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=virtual-earth.de; s=default_1811; h=Content-Transfer-Encoding:Content-Type: MIME-Version:Message-ID:References:In-Reply-To:Subject:To:From:Date:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID; bh=SCJdJv3KAWSGpVBW1y1RtH3KHuDRehbal5YMQ1gSXlY=; b=ILo/yKNlwj7MHrwMaq53drP838 m6geqbWiDMjIt8jtbxHfl9koeY997XEmS0gz8/7YeN1GYlEDd6ZJhQB9rMF1dgHbApRzqwdA6CFR/ QzyKG/dnN8ciof2pY12giRRSZ9Ecyk62Z4N4Strktx3hG6BbrBuvXwej/ib32saJNonjeYjXgwk1f 9E7Tc7fHWhqiJ5kbiCQVf1x2aTp5P2AVnKfjYk9H/YMIsl8oySeW0mz9vt0Xd8PIQWfQ3veypudR3 XdmXE8kAfsrNBeY+SanvMFvU/76R4nAlPLB2CmTSLfmc2V+lsFjc8kmm7vCCyY2MZuEqbg1dcz6Ms jic/bJ/w==; Received: from sslproxy06.your-server.de ([78.46.172.3]) by www94.your-server.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1plfTT-0006SU-G7; Mon, 10 Apr 2023 02:33:35 +0200 Received: from [2a01:c23:c0bf:c100:2168:16f6:8532:6747] (helo=[IPv6:::1]) by sslproxy06.your-server.de with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1plfTT-0007hS-8y; Mon, 10 Apr 2023 02:33:35 +0200 Date: Mon, 10 Apr 2023 02:33:34 +0200 From: Mathias Picker To: stable@freebsd.org, Yoshihiro Ota , freebsd-stable@FreeBSD.org Subject: =?US-ASCII?Q?Re=3A_FreeBSD_13=2E2-RELEASE_started_failing_?= =?US-ASCII?Q?to_load_i915kms=2Eko_after_upgrade_from_RC5?= User-Agent: K-9 Mail for Android In-Reply-To: <20230409145558.c7cf0e9bb11f13d41f4f6031@j.email.ne.jp> References: <20230409145558.c7cf0e9bb11f13d41f4f6031@j.email.ne.jp> Message-ID: <2B548434-F639-4D6C-99C3-3B8FF687837A@virtual-earth.de> List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Authenticated-Sender: Mathias.Picker@virtual-earth.de X-Virus-Scanned: Clear (ClamAV 0.103.8/26870/Sun Apr 9 09:25:02 2023) X-Rspamd-Queue-Id: 4Pvqhf4Ty6z3n7P X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:213.133.96.0/19, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Am 9=2E April 2023 20:55:58 MESZ schrieb Yoshihiro Ota : >Hi, > >I've been following releng/13=2E2 since it was branched=2E >I use amd64 arch for this=2E > >I had built kernel modules during BETA/RC period=2E >The above i915kms had worked until RC5=2E >I had not built RC6 locally and picked up RELEASE on releng/13=2E2=2E > >After upgrading from RC5 to 13=2E2-RELEASE, the kernel started failing to= load i915mks=2E >This time, all kmod started failing such as one for virtual box, too=2E > >I thought I would need to rebuild all kernel modules, and thus started=2E >However, even after rebuilding kernel modules several times, i915kms does= n't load properly=2E >While new virtual box kmod works, I think my build environment isn't a pr= oblem=2E > >I cannot make i915kms back in working condition=2E >I also updated /usr/ports and rebuilt few times but yet not successful=2E Did you update /usr/src ? >I get the following error: >``` >linker_load_file: /boot/modules/i915kms=2Eko - unsupported file type >``` > >Any hints or same experiences? > >Hiro > Mathias Picker Gesch=C3=A4ftsf=C3=BChrer virtual earth Gesellschaft f=C3=BCr Wissens re/pr=C3=A4 sentation mbH Westendstr=2E 142 80339 M=C3=BCnchen +4915256178344 From nobody Mon Apr 10 00:33:34 2023 X-Original-To: stable@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 4Pvqhf64Dgz44VY5; Mon, 10 Apr 2023 00:33:38 +0000 (UTC) (envelope-from Mathias.Picker@virtual-earth.de) Received: from www94.your-server.de (www94.your-server.de [213.133.104.94]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Pvqhf4Ty6z3n7P; Mon, 10 Apr 2023 00:33:38 +0000 (UTC) (envelope-from Mathias.Picker@virtual-earth.de) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=virtual-earth.de; s=default_1811; h=Content-Transfer-Encoding:Content-Type: MIME-Version:Message-ID:References:In-Reply-To:Subject:To:From:Date:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID; bh=SCJdJv3KAWSGpVBW1y1RtH3KHuDRehbal5YMQ1gSXlY=; b=ILo/yKNlwj7MHrwMaq53drP838 m6geqbWiDMjIt8jtbxHfl9koeY997XEmS0gz8/7YeN1GYlEDd6ZJhQB9rMF1dgHbApRzqwdA6CFR/ QzyKG/dnN8ciof2pY12giRRSZ9Ecyk62Z4N4Strktx3hG6BbrBuvXwej/ib32saJNonjeYjXgwk1f 9E7Tc7fHWhqiJ5kbiCQVf1x2aTp5P2AVnKfjYk9H/YMIsl8oySeW0mz9vt0Xd8PIQWfQ3veypudR3 XdmXE8kAfsrNBeY+SanvMFvU/76R4nAlPLB2CmTSLfmc2V+lsFjc8kmm7vCCyY2MZuEqbg1dcz6Ms jic/bJ/w==; Received: from sslproxy06.your-server.de ([78.46.172.3]) by www94.your-server.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1plfTT-0006SU-G7; Mon, 10 Apr 2023 02:33:35 +0200 Received: from [2a01:c23:c0bf:c100:2168:16f6:8532:6747] (helo=[IPv6:::1]) by sslproxy06.your-server.de with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1plfTT-0007hS-8y; Mon, 10 Apr 2023 02:33:35 +0200 Date: Mon, 10 Apr 2023 02:33:34 +0200 From: Mathias Picker To: stable@freebsd.org, Yoshihiro Ota , freebsd-stable@FreeBSD.org Subject: =?US-ASCII?Q?Re=3A_FreeBSD_13=2E2-RELEASE_started_failing_?= =?US-ASCII?Q?to_load_i915kms=2Eko_after_upgrade_from_RC5?= User-Agent: K-9 Mail for Android In-Reply-To: <20230409145558.c7cf0e9bb11f13d41f4f6031@j.email.ne.jp> References: <20230409145558.c7cf0e9bb11f13d41f4f6031@j.email.ne.jp> Message-ID: <2B548434-F639-4D6C-99C3-3B8FF687837A@virtual-earth.de> List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Authenticated-Sender: Mathias.Picker@virtual-earth.de X-Virus-Scanned: Clear (ClamAV 0.103.8/26870/Sun Apr 9 09:25:02 2023) X-Rspamd-Queue-Id: 4Pvqhf4Ty6z3n7P X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:213.133.96.0/19, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Am 9=2E April 2023 20:55:58 MESZ schrieb Yoshihiro Ota : >Hi, > >I've been following releng/13=2E2 since it was branched=2E >I use amd64 arch for this=2E > >I had built kernel modules during BETA/RC period=2E >The above i915kms had worked until RC5=2E >I had not built RC6 locally and picked up RELEASE on releng/13=2E2=2E > >After upgrading from RC5 to 13=2E2-RELEASE, the kernel started failing to= load i915mks=2E >This time, all kmod started failing such as one for virtual box, too=2E > >I thought I would need to rebuild all kernel modules, and thus started=2E >However, even after rebuilding kernel modules several times, i915kms does= n't load properly=2E >While new virtual box kmod works, I think my build environment isn't a pr= oblem=2E > >I cannot make i915kms back in working condition=2E >I also updated /usr/ports and rebuilt few times but yet not successful=2E Did you update /usr/src ? >I get the following error: >``` >linker_load_file: /boot/modules/i915kms=2Eko - unsupported file type >``` > >Any hints or same experiences? > >Hiro > Mathias Picker Gesch=C3=A4ftsf=C3=BChrer virtual earth Gesellschaft f=C3=BCr Wissens re/pr=C3=A4 sentation mbH Westendstr=2E 142 80339 M=C3=BCnchen +4915256178344 From nobody Mon Apr 10 03:39:12 2023 X-Original-To: freebsd-stable@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 4Pvvpr2HQFz44hlJ for ; Mon, 10 Apr 2023 03:39:16 +0000 (UTC) (envelope-from ota@j.email.ne.jp) Received: from hsmtpd-fgn.xspmail.jp (hsmtpd-fgn.xspmail.jp [210.130.137.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Pvvpq62ppz4cV4 for ; Mon, 10 Apr 2023 03:39:15 +0000 (UTC) (envelope-from ota@j.email.ne.jp) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1681097952; d=j.email.ne.jp; s=x01; i=ota@j.email.ne.jp; h=content-transfer-encoding:content-type:mime-version:references:in-reply-to: message-id:subject:cc:to:from:date:from; bh=968751Mv2GwHnjsq7njICrxGjHkY2/29yHpO+pFX1KI=; b=ICXTjuayawBZQ6xieNmhd7PAbPtU6cEGZXOQplf/Fvx32+khtLDL3RgUhPBHe+p38k1B/z81+YpSK fVQWJaGqpM8KF0R7mRtHmBYEOLdx1xtsVo6WAPYDB0BhnEKrFTLlwBslQScbBMHdG6EJ02p/aJVlg8 F4b9BVS5vLkuL+yhnB6gIYT2pTtZjY7Zx2EAoMvb4aUf7UYGp3JUznH1ceLHCLJpwUpXOq9CoqTLse xeAzNUfyN5WyakgCkdl1NsYLrwf8lMedBbKhhLjpEC1NvS0WuPLG/L29h7V2Ce0rfWm0F6tYVGH2rW 2iQ2bzskYybEd5hCmK2lnJCSTZLBNWQ== X-Country-Code: US Received: from e20.advok.com (pool-173-63-27-212.nwrknj.fios.verizon.net [173.63.27.212]) by hsmtpd-out-0.asahinet.cluster.xspmail.jp (Halon) with ESMTPA id 01f61ebe-db4b-4d01-bab9-322dfbe386dd; Mon, 10 Apr 2023 12:39:11 +0900 (JST) Date: Sun, 9 Apr 2023 23:39:12 -0400 From: Yoshihiro Ota To: Mathias Picker Cc: stable@freebsd.org, freebsd-stable@FreeBSD.org Subject: Re: FreeBSD 13.2-RELEASE started failing to load i915kms.ko after upgrade from RC5 Message-Id: <20230409233912.91110c2b6a55052a433c99ba@j.email.ne.jp> In-Reply-To: <2B548434-F639-4D6C-99C3-3B8FF687837A@virtual-earth.de> References: <20230409145558.c7cf0e9bb11f13d41f4f6031@j.email.ne.jp> <2B548434-F639-4D6C-99C3-3B8FF687837A@virtual-earth.de> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd12.2) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Pvvpq62ppz4cV4 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:2497, ipnet:210.130.0.0/16, country:JP] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Mon, 10 Apr 2023 02:33:34 +0200 Mathias Picker wrote: > Am 9. April 2023 20:55:58 MESZ schrieb Yoshihiro Ota : > >Hi, > > > >I've been following releng/13.2 since it was branched. > >I use amd64 arch for this. > > > >I had built kernel modules during BETA/RC period. > >The above i915kms had worked until RC5. > >I had not built RC6 locally and picked up RELEASE on releng/13.2. > > > >After upgrading from RC5 to 13.2-RELEASE, the kernel started failing to load i915mks. > >This time, all kmod started failing such as one for virtual box, too. > > > >I thought I would need to rebuild all kernel modules, and thus started. > >However, even after rebuilding kernel modules several times, i915kms doesn't load properly. > >While new virtual box kmod works, I think my build environment isn't a problem. > > > >I cannot make i915kms back in working condition. > >I also updated /usr/ports and rebuilt few times but yet not successful. > > Did you update /usr/src ? Yes, I have the latest releng/13.2 under /usr/src and main under /usr/ports from git. Hiro From nobody Mon Apr 10 03:39:12 2023 X-Original-To: stable@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 4Pvvpr2D58z44hgH for ; Mon, 10 Apr 2023 03:39:16 +0000 (UTC) (envelope-from ota@j.email.ne.jp) Received: from hsmtpd-fgn.xspmail.jp (hsmtpd-fgn.xspmail.jp [210.130.137.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Pvvpq62qWz4cfd for ; Mon, 10 Apr 2023 03:39:15 +0000 (UTC) (envelope-from ota@j.email.ne.jp) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1681097952; d=j.email.ne.jp; s=x01; i=ota@j.email.ne.jp; h=content-transfer-encoding:content-type:mime-version:references:in-reply-to: message-id:subject:cc:to:from:date:from; bh=968751Mv2GwHnjsq7njICrxGjHkY2/29yHpO+pFX1KI=; b=ICXTjuayawBZQ6xieNmhd7PAbPtU6cEGZXOQplf/Fvx32+khtLDL3RgUhPBHe+p38k1B/z81+YpSK fVQWJaGqpM8KF0R7mRtHmBYEOLdx1xtsVo6WAPYDB0BhnEKrFTLlwBslQScbBMHdG6EJ02p/aJVlg8 F4b9BVS5vLkuL+yhnB6gIYT2pTtZjY7Zx2EAoMvb4aUf7UYGp3JUznH1ceLHCLJpwUpXOq9CoqTLse xeAzNUfyN5WyakgCkdl1NsYLrwf8lMedBbKhhLjpEC1NvS0WuPLG/L29h7V2Ce0rfWm0F6tYVGH2rW 2iQ2bzskYybEd5hCmK2lnJCSTZLBNWQ== X-Country-Code: US Received: from e20.advok.com (pool-173-63-27-212.nwrknj.fios.verizon.net [173.63.27.212]) by hsmtpd-out-0.asahinet.cluster.xspmail.jp (Halon) with ESMTPA id 01f61ebe-db4b-4d01-bab9-322dfbe386dd; Mon, 10 Apr 2023 12:39:11 +0900 (JST) Date: Sun, 9 Apr 2023 23:39:12 -0400 From: Yoshihiro Ota To: Mathias Picker Cc: stable@freebsd.org, freebsd-stable@FreeBSD.org Subject: Re: FreeBSD 13.2-RELEASE started failing to load i915kms.ko after upgrade from RC5 Message-Id: <20230409233912.91110c2b6a55052a433c99ba@j.email.ne.jp> In-Reply-To: <2B548434-F639-4D6C-99C3-3B8FF687837A@virtual-earth.de> References: <20230409145558.c7cf0e9bb11f13d41f4f6031@j.email.ne.jp> <2B548434-F639-4D6C-99C3-3B8FF687837A@virtual-earth.de> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd12.2) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Pvvpq62qWz4cfd X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:2497, ipnet:210.130.0.0/16, country:JP] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Mon, 10 Apr 2023 02:33:34 +0200 Mathias Picker wrote: > Am 9. April 2023 20:55:58 MESZ schrieb Yoshihiro Ota : > >Hi, > > > >I've been following releng/13.2 since it was branched. > >I use amd64 arch for this. > > > >I had built kernel modules during BETA/RC period. > >The above i915kms had worked until RC5. > >I had not built RC6 locally and picked up RELEASE on releng/13.2. > > > >After upgrading from RC5 to 13.2-RELEASE, the kernel started failing to load i915mks. > >This time, all kmod started failing such as one for virtual box, too. > > > >I thought I would need to rebuild all kernel modules, and thus started. > >However, even after rebuilding kernel modules several times, i915kms doesn't load properly. > >While new virtual box kmod works, I think my build environment isn't a problem. > > > >I cannot make i915kms back in working condition. > >I also updated /usr/ports and rebuilt few times but yet not successful. > > Did you update /usr/src ? Yes, I have the latest releng/13.2 under /usr/src and main under /usr/ports from git. Hiro From nobody Mon Apr 10 08:27:09 2023 X-Original-To: stable@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 4Pw2C61bg7z44xmb for ; Mon, 10 Apr 2023 08:27:14 +0000 (UTC) (envelope-from yuri@aetern.org) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Pw2C57291z4FCf for ; Mon, 10 Apr 2023 08:27:13 +0000 (UTC) (envelope-from yuri@aetern.org) Authentication-Results: mx1.freebsd.org; none Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 07FDF5C0092; Mon, 10 Apr 2023 04:27:13 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Mon, 10 Apr 2023 04:27:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aetern.org; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1681115233; x=1681201633; bh=FbWVgmzZye24MYexI19I5NlWKMRlcnymfag xq5CsJOQ=; b=tYFdWeC6l9guHzscxidn06vqgraVhA6p13ruSn0mwgFrRr6fPwk eVGbfklV9X8n3Herqzo404firUUeRFgduL9A0qkFTYoqiIHDJs83+ete82YGglcv WWKOQSIiOyIObs0SuODl/uwObHpxkPd/ORqv4rmCh5euZRsM2AH9xD5tauPRhKIi gVl/iHQ7G8NRFeBG/AdJbNmXx+tp0LK+1Q3RVU0hpzLGp9has+WYIgS/xwVRF0TS WjNisb95ikV+fhbel4kCj0ouLB2Ps7a+N++YRttvGSER/LPSlMn64rqiqDXx+pg0 gKbx1CgqdQldSU4nqHZD48Vzf0HZiZ1ffFA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1681115233; x=1681201633; bh=FbWVgmzZye24MYexI19I5NlWKMRlcnymfag xq5CsJOQ=; b=l1wRMpGiO8eUD+jvbXfubFubaicg/n7ZuBX1KTs4yqLhwXSqsMb tc9O5orcot+j+ncv0Ey8zS7L9V+5NpPs3meQp3DdpMtcJdSKw5k4I3wbRFFwN6BN HYt9C84y5govzJaf3RPlExEB9iJrO0QKP8o0pVUPH4npK0F6rsglIXEbEjC0D7vx Xmh++aQadlyFIMcBrCZnBVpx7BWbWhvDvXmS7btEk2PN1366xjJ6WrWzEERBdRsT Gc931A/ymF4LNqNDFOPV63PU3F3a7R3jX5Ubdf36dFMAEwkQYZoWckp5u3OqilKZ C/ycz02WKC9p5dISDDsRw7w2gTQOfgcQ8SQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdekvddgtddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfevfhfhjggtgfesth ejredttdefjeenucfhrhhomhepjghurhhiuceohihurhhisegrvghtvghrnhdrohhrgheq necuggftrfgrthhtvghrnhepkedtffeiieeigeejgfffiefgveejfedvteejtdeiuefggf elieefvefhveffheetnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghi lhhfrhhomhephihurhhisegrvghtvghrnhdrohhrgh X-ME-Proxy: Feedback-ID: i0d79475b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 10 Apr 2023 04:27:11 -0400 (EDT) Message-ID: Date: Mon, 10 Apr 2023 10:27:09 +0200 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.9.1 Subject: Re: FreeBSD 13.2-RELEASE started failing to load i915kms.ko after upgrade from RC5 To: Yoshihiro Ota Cc: stable@freebsd.org References: <20230409145558.c7cf0e9bb11f13d41f4f6031@j.email.ne.jp> <2B548434-F639-4D6C-99C3-3B8FF687837A@virtual-earth.de> <20230409233912.91110c2b6a55052a433c99ba@j.email.ne.jp> Content-Language: en-US From: Yuri In-Reply-To: <20230409233912.91110c2b6a55052a433c99ba@j.email.ne.jp> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Pw2C57291z4FCf X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Yoshihiro Ota wrote: > On Mon, 10 Apr 2023 02:33:34 +0200 > Mathias Picker wrote: > >> Am 9. April 2023 20:55:58 MESZ schrieb Yoshihiro Ota : >>> Hi, >>> >>> I've been following releng/13.2 since it was branched. >>> I use amd64 arch for this. >>> >>> I had built kernel modules during BETA/RC period. >>> The above i915kms had worked until RC5. >>> I had not built RC6 locally and picked up RELEASE on releng/13.2. >>> >>> After upgrading from RC5 to 13.2-RELEASE, the kernel started failing to load i915mks. >>> This time, all kmod started failing such as one for virtual box, too. >>> >>> I thought I would need to rebuild all kernel modules, and thus started. >>> However, even after rebuilding kernel modules several times, i915kms doesn't load properly. >>> While new virtual box kmod works, I think my build environment isn't a problem. >>> >>> I cannot make i915kms back in working condition. >>> I also updated /usr/ports and rebuilt few times but yet not successful. >> >> Did you update /usr/src ? > > Yes, I have the latest releng/13.2 under /usr/src and main under /usr/ports from git. What is in dmesg (or /var/log/messages)? There could be more verbose explanation (like missing symbols). From nobody Tue Apr 11 14:17:13 2023 X-Original-To: stable@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 4Pwnwk5X5Qz44wXM; Tue, 11 Apr 2023 14:17:26 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from mail-pg1-f177.google.com (mail-pg1-f177.google.com [209.85.215.177]) (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 4Pwnwj5yLJz4Wc1; Tue, 11 Apr 2023 14:17:25 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of uspoerlein@gmail.com designates 209.85.215.177 as permitted sender) smtp.mailfrom=uspoerlein@gmail.com; dmarc=none Received: by mail-pg1-f177.google.com with SMTP id r17so4184777pgr.1; Tue, 11 Apr 2023 07:17:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681222644; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=te0x3jETnqK23pIdXHpqZkXp92iQkFKHzdZSz5Vp+YQ=; b=ir/4UuVknOXbn4xJILjMucDlN4wkbrmqmBc0K6WDQwSK4gMtfrLyVhPbuLTLeRKgNU 93I9KhsiP5dLiMS6O0I9VM99zmlvyD4HOx+EULMT4BI533Sh+pKS54bV1Aw1SE6W4MA5 gcHBbrsdK10TxiK1bMbNxYsaHqklg3cn3VbhkkoGY6Du9akXphaX0G+0tsp2P3a7K3Ea PM83S4kOIZ1Uwu8NK1DlU37NQkGjbOlzJj4jpP9gEegEjh304e3dCOvLvxYDSLfIT599 Dpqp40N2yd3a4i8YZtyn+qeg5h9DVttl5VFZig0Seq7OmpTKDjNgSe8cgCbxpO2wKo4s AOFg== X-Gm-Message-State: AAQBX9d9fsob5+6KhYgjMTHP7M9ZftLzsXLPk7R8+spsHRyygsfw7TWY zdchJFeaDyt0wmxyfsrTGA94g4w0UKN2Fh27wM67wUR/82Ymtg== X-Google-Smtp-Source: AKy350ZkE3yqJAfzUov8zwd+Yn2Z5rJUDhQtuowD6+sol6zsbe3yFkwF3ZgHVSg93oRVIXu+YT7ukry1H9U9h/O29BY= X-Received: by 2002:a63:4e51:0:b0:50c:a45:1f99 with SMTP id o17-20020a634e51000000b0050c0a451f99mr2875511pgl.8.1681222644303; Tue, 11 Apr 2023 07:17:24 -0700 (PDT) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 References: <86o7og27eh.fsf@virtual-earth.de> <8b47d0a4-a8f1-1841-ee59-3949fe69cbd7@ShaneWare.Biz> <20230327210535.9ED5A1D7@slippy.cwsent.com> <044587F7-4BA9-4585-A789-F4B53E8D02A2@virtual-earth.de> <20230327145629.3b55eed8@slippy> <86o7oa1i6t.fsf@virtual-earth.de> In-Reply-To: <86o7oa1i6t.fsf@virtual-earth.de> From: =?UTF-8?Q?Ulrich_Sp=C3=B6rlein?= Date: Tue, 11 Apr 2023 16:17:13 +0200 Message-ID: Subject: Re: -stable from today dumps core with drm-510-kmod and some graphical clients To: Mathias Picker Cc: Cy Schubert , Shane Ambler , FreeBSD-STABLE , stable@freebsd.org Content-Type: multipart/alternative; boundary="000000000000808d8905f91026c2" X-Spamd-Result: default: False [0.34 / 15.00]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_SPAM_SHORT(0.97)[0.967]; NEURAL_SPAM_MEDIUM(0.48)[0.476]; FORGED_SENDER(0.30)[uqs@freebsd.org,uspoerlein@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; RWL_MAILSPIKE_GOOD(-0.10)[209.85.215.177:from]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_IN_DNSWL_NONE(0.00)[209.85.215.177:from]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org,stable@freebsd.org]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCPT_COUNT_FIVE(0.00)[5]; FROM_NEQ_ENVFROM(0.00)[uqs@freebsd.org,uspoerlein@gmail.com]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_SOME(0.00)[]; DMARC_NA(0.00)[freebsd.org]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4Pwnwj5yLJz4Wc1 X-Spamd-Bar: / X-ThisMailContainsUnwantedMimeParts: N --000000000000808d8905f91026c2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Mar 30, 2023 at 3:29=E2=80=AFPM Mathias Picker < Mathias.Picker@virtual-earth.de> wrote: > > Cy Schubert writes: > > > On Mon, 27 Mar 2023 23:43:35 +0200 > > Mathias Picker wrote: > > > >> Am 27. M=C3=A4rz 2023 23:05:35 MESZ schrieb Cy Schubert > >> : > >> >In message > >> ><8b47d0a4-a8f1-1841-ee59-3949fe69cbd7@ShaneWare.Biz>, Shane > >> >Ambler w > >> >rites: > >> >> On 26/3/23 01:37, Mathias Picker wrote: > >> >> > > >> >> > Starting sddm works fine, starting my normal session > >> >> > crashes or freezes > >> >> > FreeBSD. > >> >> > > >> >> > I can find no error messages after a reboot. > >> >> > > >> >> > I found out, that I can start xterm or emacs (exwm) > >> >> > without problems, > >> >> > xrandr works with external screen, but once I start > >> >> > anything more > >> >> > demanding (I guess demanding of the GPU) everything > >> >> > freezes or FreeBSD > >> >> > even reboots. > >> >> > > >> >> > =C3=A2=E2=82=AC=C5=93Demanding=C3=A2=E2=82=AC means even simple = things like > >> >> > qterminal. I tried firefox an > >> >> d > >> >> > blender and then I had it with the reboots and > >> >> > didn=C3=A2=E2=82=AC=E2=84=A2t try anything else. > >> >> > xedit works fine :) > >> >> > > >> >> > I have nothing in the logs, I have no idea where to look > >> >> > or how to debug > >> >> > this. > >> >> > > >> >> > Any ideas, tipps, help greatly apreciated. > >> >> > >> >> > >> >> FreeBSD Developers Handbook Chapter 10: Kernel Debugging > >> >> > >> >> https://docs.freebsd.org/en/books/developers-handbook/kerneldebug/ > >> >> > >> >> Running stable, kernel dumps may already be enabled, look in > >> >> /var/crash > >> >> > >> >> By enabling a kernel dump when it panics (dumpdev=3D"AUTO" in > >> >> rc.conf) the > >> >> kernel core is saved to swap space, then on reboot gets > >> >> copied to > >> >> dumpdir (/var/crash) where you can then use kgdb (from > >> >> devel/gdb) to get > >> >> a stack trace to find where the panic happened. > >> > > >> >drm-*-kmod probably needs a rebuild. Likely a data structure > >> >changed. In my > >> >experience a simple rebuild of the port solves 90% of > >> >drm-*-kmod crash > >> >problems. > >> > > >> Hi Cy, > >> > >> sorry I didn't mention that, but I did rebuild drm-kmod, I > >> actually do it after every new kernel build, just to be on the > >> safe side. > >> > >> I switched my swap to non-encrypted and will look if I can get > >> any information from the kernel dump tomorrow. > >> > >> Oh, and it's on a Thinkpad X1 Yoga 3rd gen, I just noticed I > >> didn't mention this. > > > > It may be worth trying drm-515-kmod as some MFC that works with > > 515 and > > not 510 may have been committed. Linux-KPI commits are the usual > > suspects. > > > > I use drm-515 with 14-CURRENT. > > Finally I found the time for a kernel crash dump. > This is what kgdb says > > mathiasp:amd64.amd64/sys/GENERIC% sudo kgdb kernel > /var/crash/vmcore.2 > GNU gdb (GDB) 13.1 [GDB v13.1 for FreeBSD] > Copyright (C) 2023 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. > Type "show copying" and "show warranty" for details. > This GDB was configured as "x86_64-portbld-freebsd13.1". > Type "show configuration" for configuration details. > For bug reporting instructions, please see: > . > Find the GDB manual and other documentation resources online at: > . > > For help, type "help". > Type "apropos word" to search for commands related to "word"... > Reading symbols from kernel... > Reading symbols from > /usr/obj/usr/src/amd64.amd64/sys/GENERIC/kernel.debug... > > Unread portion of the kernel message buffer: > > > __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55 > 55 __asm("movq %%gs:%P1,%0" : "=3Dr" (td) : "n" > (offsetof(struct pcpu, > (kgdb) backtrace > #0 __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55 > #1 doadump (textdump=3D) at > /usr/src/sys/kern/kern_shutdown.c:396 > #2 0xffffffff80c07c2a in kern_reboot (howto=3D260) at > /usr/src/sys/kern/kern_shutdown.c:484 > #3 0xffffffff80c080ce in vpanic (fmt=3D, > ap=3Dap@entry=3D0xfffffe01341fab50) at > /usr/src/sys/kern/kern_shutdown.c:923 > #4 0xffffffff80c07f03 in panic (fmt=3D) at > /usr/src/sys/kern/kern_shutdown.c:847 > #5 0xffffffff810c1fa7 in trap_fatal (frame=3D0xfffffe01341fac40, > eva=3D0) at /usr/src/sys/amd64/amd64/trap.c:942 > #6 0xffffffff810c1fff in trap_pfault (frame=3D0xfffffe01341fac40, > usermode=3Dfalse, signo=3D, ucode=3D) > at /usr/src/sys/amd64/amd64/trap.c:761 > #7 > #8 0xffffffff84a07067 in shmem_get_pages () from > /boot/modules/i915kms.ko > #9 0x0000000300000015 in ?? () > #10 0x0000000000000060 in ?? () > #11 0x0000000000000060 in ?? () > #12 0x0000000000060000 in ?? () > #13 0xfffffe00dc365a80 in ?? () > #14 0xfffff00100000060 in ?? () > #15 0xfffff8003e270c00 in ?? () > #16 0x00000000fffff000 in ?? () > #17 0xfffff8002138fc20 in ?? () > #18 0xfffffe00dc365a80 in ?? () > #19 0x0000000000000060 in ?? () > #20 0xfffff8003e270c00 in ?? () > #21 0x0000000000000060 in ?? () > #22 0xfffffe0131e0fc80 in ?? () > #23 0xfffffe01341fade0 in ?? () > #24 0xffffffff84a07596 in shmem_pwrite () from > /boot/modules/i915kms.ko > #25 0x0000000000000000 in ?? () > (kgdb) > > > Anything else I can do to help? > > I=E2=80=99m now building drm-515-kmod, let=E2=80=99s see how that works i= n > -stable. > > /Mathias > > Any updates here? I just ran into this myself and am very close to just installing Linux on my laptop, tbh. I've rebuilt stable/13 today, then rebuilt the 510-kmod (because the 515-kmod doesn't even build) and pretty much anything that's not an XTerm will panic/reboot the machine (a Thinkpad T490 with Intel GPU). dmesg got this to say: Fatal trap 12: page fault while in kernel mode cpuid =3D 1; apic id =3D 02 fault virtual address =3D 0x0 fault code =3D supervisor read data, page not present instruction pointer =3D 0x20:0xffffffff84430626 stack pointer =3D 0x28:0xfffffe0140c83cf0 frame pointer =3D 0x28:0xfffffe0140c83d70 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 0 (i915-userptr-acquir) trap number =3D 12 panic: page fault cpuid =3D 1 time =3D 1681221523 KDB: stack backtrace: #0 0xffffffff80c5fc15 at kdb_backtrace+0x65 #1 0xffffffff80c12e02 at vpanic+0x152 #2 0xffffffff80c12ca3 at panic+0x43 #3 0xffffffff810d1577 at trap_fatal+0x387 #4 0xffffffff810d15cf at trap_pfault+0x4f #5 0xffffffff810a8568 at calltrap+0x8 #6 0xffffffff84430c02 at __i915_gem_userptr_get_pages_worker+0x1f2 #7 0xffffffff80e80883 at linux_work_fn+0xe3 #8 0xffffffff80c746f1 at taskqueue_run_locked+0x181 #9 0xffffffff80c759b3 at taskqueue_thread_loop+0xc3 #10 0xffffffff80bcf55d at fork_exit+0x7d #11 0xffffffff810a95de at fork_trampoline+0xe It apparently dumps core, will have to reacquaint myself with how to poke at this some more... --000000000000808d8905f91026c2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Mar 30, 2023 at 3:29=E2=80=AFPM M= athias Picker <Mathia= s.Picker@virtual-earth.de> wrote:

Cy Schubert <Cy.Schubert@cschubert.com> writes:

> On Mon, 27 Mar 2023 23:43:35 +0200
> Mathias Picker <Mathias.Picker@virtual-earth.de> wrote:
>
>> Am 27. M=C3=A4rz 2023 23:05:35 MESZ schrieb Cy Schubert
>> <Cy.Schubert@cschubert.com>:
>> >In message
>> ><8b47d0a4-a8f1-1841-ee59-3949fe69cbd7@ShaneWare.Biz>, Sh= ane
>> >Ambler w
>> >rites:=C2=A0
>> >> On 26/3/23 01:37, Mathias Picker wrote:=C2=A0
>> >> >
>> >> > Starting sddm works fine, starting my normal session=
>> >> > crashes or freezes
>> >> > FreeBSD.
>> >> >
>> >> > I can find no error messages after a reboot.
>> >> >
>> >> > I found out, that I can start xterm or emacs (exwm) =
>> >> > without problems,
>> >> > xrandr works with external screen, but once I start =
>> >> > anything more
>> >> > demanding (I guess demanding of the GPU) everything =
>> >> > freezes or FreeBSD
>> >> > even reboots.
>> >> >
>> >> > =C3=A2=E2=82=AC=C5=93Demanding=C3=A2=E2=82=AC=C2=A0 = means even simple things like
>> >> > qterminal. I tried firefox an=C2=A0
>> >> d=C2=A0
>> >> > blender and then I had it with the reboots and
>> >> > didn=C3=A2=E2=82=AC=E2=84=A2t try anything else.
>> >> > xedit works fine :)
>> >> >
>> >> > I have nothing in the logs, I have no idea where to = look
>> >> > or how to debug
>> >> > this.
>> >> >
>> >> > Any ideas, tipps, help greatly apreciated.=C2=A0 >> >>
>> >>
>> >> FreeBSD Developers Handbook Chapter 10: Kernel Debugging<= br> >> >>
>> >> https://docs.fre= ebsd.org/en/books/developers-handbook/kerneldebug/
>> >>
>> >> Running stable, kernel dumps may already be enabled, look= in
>> >> /var/crash
>> >>
>> >> By enabling a kernel dump when it panics (dumpdev=3D"= ;AUTO" in
>> >> rc.conf) the
>> >> kernel core is saved to swap space, then on reboot gets <= br> >> >> copied to
>> >> dumpdir (/var/crash) where you can then use kgdb (from >> >> devel/gdb) to get
>> >> a stack trace to find where the panic happened.=C2=A0 >> >
>> >drm-*-kmod probably needs a rebuild. Likely a data structure <= br> >> >changed. In my
>> >experience a simple rebuild of the port solves 90% of
>> >drm-*-kmod crash
>> >problems.
>> >=C2=A0
>> Hi Cy,
>>
>> sorry I didn't mention that, but I did rebuild drm-kmod, I >> actually do it after every new kernel build, just to be on the >> safe side.
>>
>> I switched my swap to non-encrypted and will look if I can get >> any information from the kernel dump tomorrow.
>>
>> Oh, and it's on a Thinkpad X1 Yoga 3rd gen, I just noticed I <= br> >> didn't mention this.
>
> It may be worth trying drm-515-kmod as some MFC that works with
> 515 and
> not 510 may have been committed. Linux-KPI commits are the usual
> suspects.
>
> I use drm-515 with 14-CURRENT.

Finally I found the time for a kernel crash dump.
This is what kgdb says

mathiasp:amd64.amd64/sys/GENERIC% sudo kgdb kernel
/var/crash/vmcore.2
GNU gdb (GDB) 13.1 [GDB v13.1 for FreeBSD]
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-portbld-freebsd13.1".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
=C2=A0 =C2=A0 <http://www.gnu.org/software/gdb/docu= mentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word&= quot;...
Reading symbols from kernel...
Reading symbols from
/usr/obj/usr/src/amd64.amd64/sys/GENERIC/kernel.debug...

Unread portion of the kernel message buffer:


__curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
55=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 __asm("movq %%gs:%P= 1,%0" : "=3Dr" (td) : "n"
(offsetof(struct pcpu,
(kgdb) backtrace
#0=C2=A0 __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
#1=C2=A0 doadump (textdump=3D<optimized out>) at
=C2=A0/usr/src/sys/kern/kern_shutdown.c:396
#2=C2=A0 0xffffffff80c07c2a in kern_reboot (howto=3D260) at
=C2=A0/usr/src/sys/kern/kern_shutdown.c:484
#3=C2=A0 0xffffffff80c080ce in vpanic (fmt=3D<optimized out>,
=C2=A0ap=3Dap@entry=3D0xfffffe01341fab50) at
=C2=A0/usr/src/sys/kern/kern_shutdown.c:923
#4=C2=A0 0xffffffff80c07f03 in panic (fmt=3D<unavailable>) at
=C2=A0/usr/src/sys/kern/kern_shutdown.c:847
#5=C2=A0 0xffffffff810c1fa7 in trap_fatal (frame=3D0xfffffe01341fac40,
=C2=A0eva=3D0) at /usr/src/sys/amd64/amd64/trap.c:942
#6=C2=A0 0xffffffff810c1fff in trap_pfault (frame=3D0xfffffe01341fac40, =C2=A0usermode=3Dfalse, signo=3D<optimized out>, ucode=3D<optimize= d out>)
=C2=A0 =C2=A0 at /usr/src/sys/amd64/amd64/trap.c:761
#7=C2=A0 <signal handler called>
#8=C2=A0 0xffffffff84a07067 in shmem_get_pages () from
=C2=A0/boot/modules/i915kms.ko
#9=C2=A0 0x0000000300000015 in ?? ()
#10 0x0000000000000060 in ?? ()
#11 0x0000000000000060 in ?? ()
#12 0x0000000000060000 in ?? ()
#13 0xfffffe00dc365a80 in ?? ()
#14 0xfffff00100000060 in ?? ()
#15 0xfffff8003e270c00 in ?? ()
#16 0x00000000fffff000 in ?? ()
#17 0xfffff8002138fc20 in ?? ()
#18 0xfffffe00dc365a80 in ?? ()
#19 0x0000000000000060 in ?? ()
#20 0xfffff8003e270c00 in ?? ()
#21 0x0000000000000060 in ?? ()
#22 0xfffffe0131e0fc80 in ?? ()
#23 0xfffffe01341fade0 in ?? ()
#24 0xffffffff84a07596 in shmem_pwrite () from
=C2=A0/boot/modules/i915kms.ko
#25 0x0000000000000000 in ?? ()
(kgdb)


Anything else I can do to help?

I=E2=80=99m now building drm-515-kmod, let=E2=80=99s see how that works in =
-stable.

/Mathias


Any updates here? I just r= an into this myself and am very close to just installing Linux on my laptop= , tbh.

I've rebuilt stable/13 today, then rebu= ilt the 510-kmod (because the 515-kmod doesn't even build) and pretty m= uch anything that's not an XTerm will panic/reboot the machine (a Think= pad T490 with Intel GPU).=C2=A0

dmesg got this to = say:

Fatal trap 12: page fault while in kernel mod= e
cpuid =3D 1; apic id =3D 02
fault virtual address =C2=A0 =3D 0x0fault code =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=3D supervisor = read data, page not present
instruction pointer =C2=A0 =C2=A0 =3D 0x20:0= xffffffff84430626
stack pointer =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =3D 0= x28:0xfffffe0140c83cf0
frame pointer =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =3D 0x28:0xfffffe0140c83d70
code segment =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0=3D base 0x0, limit 0xfffff, type 0x1b
=C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =3D DPL 0, p= res 1, long 1, def32 0, gran 1
processor eflags =C2=A0 =C2=A0 =C2=A0 =C2= =A0=3D interrupt enabled, resume, IOPL =3D 0
current process =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =3D 0 (i915-userptr-acquir)
trap number =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =3D 12
panic: page fault
cpuid =3D 1
t= ime =3D 1681221523
KDB: stack backtrace:
#0 0xffffffff80c5fc15 at kdb= _backtrace+0x65
#1 0xffffffff80c12e02 at vpanic+0x152
#2 0xffffffff80= c12ca3 at panic+0x43
#3 0xffffffff810d1577 at trap_fatal+0x387
#4 0xf= fffffff810d15cf at trap_pfault+0x4f
#5 0xffffffff810a8568 at calltrap+0x= 8
#6 0xffffffff84430c02 at __i915_gem_userptr_get_pages_worker+0x1f2
= #7 0xffffffff80e80883 at linux_work_fn+0xe3
#8 0xffffffff80c746f1 at tas= kqueue_run_locked+0x181
#9 0xffffffff80c759b3 at taskqueue_thread_loop+0= xc3
#10 0xffffffff80bcf55d at fork_exit+0x7d
#11 0xffffffff810a95de a= t fork_trampoline+0xe

It apparently dumps core= , will have to reacquaint myself with how to poke at this some more...
--000000000000808d8905f91026c2-- From nobody Tue Apr 11 14:17:13 2023 X-Original-To: freebsd-stable@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 4Pwnwk5X5Qz44wXM; Tue, 11 Apr 2023 14:17:26 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from mail-pg1-f177.google.com (mail-pg1-f177.google.com [209.85.215.177]) (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 4Pwnwj5yLJz4Wc1; Tue, 11 Apr 2023 14:17:25 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of uspoerlein@gmail.com designates 209.85.215.177 as permitted sender) smtp.mailfrom=uspoerlein@gmail.com; dmarc=none Received: by mail-pg1-f177.google.com with SMTP id r17so4184777pgr.1; Tue, 11 Apr 2023 07:17:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681222644; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=te0x3jETnqK23pIdXHpqZkXp92iQkFKHzdZSz5Vp+YQ=; b=ir/4UuVknOXbn4xJILjMucDlN4wkbrmqmBc0K6WDQwSK4gMtfrLyVhPbuLTLeRKgNU 93I9KhsiP5dLiMS6O0I9VM99zmlvyD4HOx+EULMT4BI533Sh+pKS54bV1Aw1SE6W4MA5 gcHBbrsdK10TxiK1bMbNxYsaHqklg3cn3VbhkkoGY6Du9akXphaX0G+0tsp2P3a7K3Ea PM83S4kOIZ1Uwu8NK1DlU37NQkGjbOlzJj4jpP9gEegEjh304e3dCOvLvxYDSLfIT599 Dpqp40N2yd3a4i8YZtyn+qeg5h9DVttl5VFZig0Seq7OmpTKDjNgSe8cgCbxpO2wKo4s AOFg== X-Gm-Message-State: AAQBX9d9fsob5+6KhYgjMTHP7M9ZftLzsXLPk7R8+spsHRyygsfw7TWY zdchJFeaDyt0wmxyfsrTGA94g4w0UKN2Fh27wM67wUR/82Ymtg== X-Google-Smtp-Source: AKy350ZkE3yqJAfzUov8zwd+Yn2Z5rJUDhQtuowD6+sol6zsbe3yFkwF3ZgHVSg93oRVIXu+YT7ukry1H9U9h/O29BY= X-Received: by 2002:a63:4e51:0:b0:50c:a45:1f99 with SMTP id o17-20020a634e51000000b0050c0a451f99mr2875511pgl.8.1681222644303; Tue, 11 Apr 2023 07:17:24 -0700 (PDT) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 References: <86o7og27eh.fsf@virtual-earth.de> <8b47d0a4-a8f1-1841-ee59-3949fe69cbd7@ShaneWare.Biz> <20230327210535.9ED5A1D7@slippy.cwsent.com> <044587F7-4BA9-4585-A789-F4B53E8D02A2@virtual-earth.de> <20230327145629.3b55eed8@slippy> <86o7oa1i6t.fsf@virtual-earth.de> In-Reply-To: <86o7oa1i6t.fsf@virtual-earth.de> From: =?UTF-8?Q?Ulrich_Sp=C3=B6rlein?= Date: Tue, 11 Apr 2023 16:17:13 +0200 Message-ID: Subject: Re: -stable from today dumps core with drm-510-kmod and some graphical clients To: Mathias Picker Cc: Cy Schubert , Shane Ambler , FreeBSD-STABLE , stable@freebsd.org Content-Type: multipart/alternative; boundary="000000000000808d8905f91026c2" X-Spamd-Result: default: False [0.34 / 15.00]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_SPAM_SHORT(0.97)[0.967]; NEURAL_SPAM_MEDIUM(0.48)[0.476]; FORGED_SENDER(0.30)[uqs@freebsd.org,uspoerlein@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; RWL_MAILSPIKE_GOOD(-0.10)[209.85.215.177:from]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_IN_DNSWL_NONE(0.00)[209.85.215.177:from]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org,stable@freebsd.org]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCPT_COUNT_FIVE(0.00)[5]; FROM_NEQ_ENVFROM(0.00)[uqs@freebsd.org,uspoerlein@gmail.com]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_SOME(0.00)[]; DMARC_NA(0.00)[freebsd.org]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4Pwnwj5yLJz4Wc1 X-Spamd-Bar: / X-ThisMailContainsUnwantedMimeParts: N --000000000000808d8905f91026c2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Mar 30, 2023 at 3:29=E2=80=AFPM Mathias Picker < Mathias.Picker@virtual-earth.de> wrote: > > Cy Schubert writes: > > > On Mon, 27 Mar 2023 23:43:35 +0200 > > Mathias Picker wrote: > > > >> Am 27. M=C3=A4rz 2023 23:05:35 MESZ schrieb Cy Schubert > >> : > >> >In message > >> ><8b47d0a4-a8f1-1841-ee59-3949fe69cbd7@ShaneWare.Biz>, Shane > >> >Ambler w > >> >rites: > >> >> On 26/3/23 01:37, Mathias Picker wrote: > >> >> > > >> >> > Starting sddm works fine, starting my normal session > >> >> > crashes or freezes > >> >> > FreeBSD. > >> >> > > >> >> > I can find no error messages after a reboot. > >> >> > > >> >> > I found out, that I can start xterm or emacs (exwm) > >> >> > without problems, > >> >> > xrandr works with external screen, but once I start > >> >> > anything more > >> >> > demanding (I guess demanding of the GPU) everything > >> >> > freezes or FreeBSD > >> >> > even reboots. > >> >> > > >> >> > =C3=A2=E2=82=AC=C5=93Demanding=C3=A2=E2=82=AC means even simple = things like > >> >> > qterminal. I tried firefox an > >> >> d > >> >> > blender and then I had it with the reboots and > >> >> > didn=C3=A2=E2=82=AC=E2=84=A2t try anything else. > >> >> > xedit works fine :) > >> >> > > >> >> > I have nothing in the logs, I have no idea where to look > >> >> > or how to debug > >> >> > this. > >> >> > > >> >> > Any ideas, tipps, help greatly apreciated. > >> >> > >> >> > >> >> FreeBSD Developers Handbook Chapter 10: Kernel Debugging > >> >> > >> >> https://docs.freebsd.org/en/books/developers-handbook/kerneldebug/ > >> >> > >> >> Running stable, kernel dumps may already be enabled, look in > >> >> /var/crash > >> >> > >> >> By enabling a kernel dump when it panics (dumpdev=3D"AUTO" in > >> >> rc.conf) the > >> >> kernel core is saved to swap space, then on reboot gets > >> >> copied to > >> >> dumpdir (/var/crash) where you can then use kgdb (from > >> >> devel/gdb) to get > >> >> a stack trace to find where the panic happened. > >> > > >> >drm-*-kmod probably needs a rebuild. Likely a data structure > >> >changed. In my > >> >experience a simple rebuild of the port solves 90% of > >> >drm-*-kmod crash > >> >problems. > >> > > >> Hi Cy, > >> > >> sorry I didn't mention that, but I did rebuild drm-kmod, I > >> actually do it after every new kernel build, just to be on the > >> safe side. > >> > >> I switched my swap to non-encrypted and will look if I can get > >> any information from the kernel dump tomorrow. > >> > >> Oh, and it's on a Thinkpad X1 Yoga 3rd gen, I just noticed I > >> didn't mention this. > > > > It may be worth trying drm-515-kmod as some MFC that works with > > 515 and > > not 510 may have been committed. Linux-KPI commits are the usual > > suspects. > > > > I use drm-515 with 14-CURRENT. > > Finally I found the time for a kernel crash dump. > This is what kgdb says > > mathiasp:amd64.amd64/sys/GENERIC% sudo kgdb kernel > /var/crash/vmcore.2 > GNU gdb (GDB) 13.1 [GDB v13.1 for FreeBSD] > Copyright (C) 2023 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. > Type "show copying" and "show warranty" for details. > This GDB was configured as "x86_64-portbld-freebsd13.1". > Type "show configuration" for configuration details. > For bug reporting instructions, please see: > . > Find the GDB manual and other documentation resources online at: > . > > For help, type "help". > Type "apropos word" to search for commands related to "word"... > Reading symbols from kernel... > Reading symbols from > /usr/obj/usr/src/amd64.amd64/sys/GENERIC/kernel.debug... > > Unread portion of the kernel message buffer: > > > __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55 > 55 __asm("movq %%gs:%P1,%0" : "=3Dr" (td) : "n" > (offsetof(struct pcpu, > (kgdb) backtrace > #0 __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55 > #1 doadump (textdump=3D) at > /usr/src/sys/kern/kern_shutdown.c:396 > #2 0xffffffff80c07c2a in kern_reboot (howto=3D260) at > /usr/src/sys/kern/kern_shutdown.c:484 > #3 0xffffffff80c080ce in vpanic (fmt=3D, > ap=3Dap@entry=3D0xfffffe01341fab50) at > /usr/src/sys/kern/kern_shutdown.c:923 > #4 0xffffffff80c07f03 in panic (fmt=3D) at > /usr/src/sys/kern/kern_shutdown.c:847 > #5 0xffffffff810c1fa7 in trap_fatal (frame=3D0xfffffe01341fac40, > eva=3D0) at /usr/src/sys/amd64/amd64/trap.c:942 > #6 0xffffffff810c1fff in trap_pfault (frame=3D0xfffffe01341fac40, > usermode=3Dfalse, signo=3D, ucode=3D) > at /usr/src/sys/amd64/amd64/trap.c:761 > #7 > #8 0xffffffff84a07067 in shmem_get_pages () from > /boot/modules/i915kms.ko > #9 0x0000000300000015 in ?? () > #10 0x0000000000000060 in ?? () > #11 0x0000000000000060 in ?? () > #12 0x0000000000060000 in ?? () > #13 0xfffffe00dc365a80 in ?? () > #14 0xfffff00100000060 in ?? () > #15 0xfffff8003e270c00 in ?? () > #16 0x00000000fffff000 in ?? () > #17 0xfffff8002138fc20 in ?? () > #18 0xfffffe00dc365a80 in ?? () > #19 0x0000000000000060 in ?? () > #20 0xfffff8003e270c00 in ?? () > #21 0x0000000000000060 in ?? () > #22 0xfffffe0131e0fc80 in ?? () > #23 0xfffffe01341fade0 in ?? () > #24 0xffffffff84a07596 in shmem_pwrite () from > /boot/modules/i915kms.ko > #25 0x0000000000000000 in ?? () > (kgdb) > > > Anything else I can do to help? > > I=E2=80=99m now building drm-515-kmod, let=E2=80=99s see how that works i= n > -stable. > > /Mathias > > Any updates here? I just ran into this myself and am very close to just installing Linux on my laptop, tbh. I've rebuilt stable/13 today, then rebuilt the 510-kmod (because the 515-kmod doesn't even build) and pretty much anything that's not an XTerm will panic/reboot the machine (a Thinkpad T490 with Intel GPU). dmesg got this to say: Fatal trap 12: page fault while in kernel mode cpuid =3D 1; apic id =3D 02 fault virtual address =3D 0x0 fault code =3D supervisor read data, page not present instruction pointer =3D 0x20:0xffffffff84430626 stack pointer =3D 0x28:0xfffffe0140c83cf0 frame pointer =3D 0x28:0xfffffe0140c83d70 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 0 (i915-userptr-acquir) trap number =3D 12 panic: page fault cpuid =3D 1 time =3D 1681221523 KDB: stack backtrace: #0 0xffffffff80c5fc15 at kdb_backtrace+0x65 #1 0xffffffff80c12e02 at vpanic+0x152 #2 0xffffffff80c12ca3 at panic+0x43 #3 0xffffffff810d1577 at trap_fatal+0x387 #4 0xffffffff810d15cf at trap_pfault+0x4f #5 0xffffffff810a8568 at calltrap+0x8 #6 0xffffffff84430c02 at __i915_gem_userptr_get_pages_worker+0x1f2 #7 0xffffffff80e80883 at linux_work_fn+0xe3 #8 0xffffffff80c746f1 at taskqueue_run_locked+0x181 #9 0xffffffff80c759b3 at taskqueue_thread_loop+0xc3 #10 0xffffffff80bcf55d at fork_exit+0x7d #11 0xffffffff810a95de at fork_trampoline+0xe It apparently dumps core, will have to reacquaint myself with how to poke at this some more... --000000000000808d8905f91026c2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Mar 30, 2023 at 3:29=E2=80=AFPM M= athias Picker <Mathia= s.Picker@virtual-earth.de> wrote:

Cy Schubert <Cy.Schubert@cschubert.com> writes:

> On Mon, 27 Mar 2023 23:43:35 +0200
> Mathias Picker <Mathias.Picker@virtual-earth.de> wrote:
>
>> Am 27. M=C3=A4rz 2023 23:05:35 MESZ schrieb Cy Schubert
>> <Cy.Schubert@cschubert.com>:
>> >In message
>> ><8b47d0a4-a8f1-1841-ee59-3949fe69cbd7@ShaneWare.Biz>, Sh= ane
>> >Ambler w
>> >rites:=C2=A0
>> >> On 26/3/23 01:37, Mathias Picker wrote:=C2=A0
>> >> >
>> >> > Starting sddm works fine, starting my normal session=
>> >> > crashes or freezes
>> >> > FreeBSD.
>> >> >
>> >> > I can find no error messages after a reboot.
>> >> >
>> >> > I found out, that I can start xterm or emacs (exwm) =
>> >> > without problems,
>> >> > xrandr works with external screen, but once I start =
>> >> > anything more
>> >> > demanding (I guess demanding of the GPU) everything =
>> >> > freezes or FreeBSD
>> >> > even reboots.
>> >> >
>> >> > =C3=A2=E2=82=AC=C5=93Demanding=C3=A2=E2=82=AC=C2=A0 = means even simple things like
>> >> > qterminal. I tried firefox an=C2=A0
>> >> d=C2=A0
>> >> > blender and then I had it with the reboots and
>> >> > didn=C3=A2=E2=82=AC=E2=84=A2t try anything else.
>> >> > xedit works fine :)
>> >> >
>> >> > I have nothing in the logs, I have no idea where to = look
>> >> > or how to debug
>> >> > this.
>> >> >
>> >> > Any ideas, tipps, help greatly apreciated.=C2=A0 >> >>
>> >>
>> >> FreeBSD Developers Handbook Chapter 10: Kernel Debugging<= br> >> >>
>> >> https://docs.fre= ebsd.org/en/books/developers-handbook/kerneldebug/
>> >>
>> >> Running stable, kernel dumps may already be enabled, look= in
>> >> /var/crash
>> >>
>> >> By enabling a kernel dump when it panics (dumpdev=3D"= ;AUTO" in
>> >> rc.conf) the
>> >> kernel core is saved to swap space, then on reboot gets <= br> >> >> copied to
>> >> dumpdir (/var/crash) where you can then use kgdb (from >> >> devel/gdb) to get
>> >> a stack trace to find where the panic happened.=C2=A0 >> >
>> >drm-*-kmod probably needs a rebuild. Likely a data structure <= br> >> >changed. In my
>> >experience a simple rebuild of the port solves 90% of
>> >drm-*-kmod crash
>> >problems.
>> >=C2=A0
>> Hi Cy,
>>
>> sorry I didn't mention that, but I did rebuild drm-kmod, I >> actually do it after every new kernel build, just to be on the >> safe side.
>>
>> I switched my swap to non-encrypted and will look if I can get >> any information from the kernel dump tomorrow.
>>
>> Oh, and it's on a Thinkpad X1 Yoga 3rd gen, I just noticed I <= br> >> didn't mention this.
>
> It may be worth trying drm-515-kmod as some MFC that works with
> 515 and
> not 510 may have been committed. Linux-KPI commits are the usual
> suspects.
>
> I use drm-515 with 14-CURRENT.

Finally I found the time for a kernel crash dump.
This is what kgdb says

mathiasp:amd64.amd64/sys/GENERIC% sudo kgdb kernel
/var/crash/vmcore.2
GNU gdb (GDB) 13.1 [GDB v13.1 for FreeBSD]
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-portbld-freebsd13.1".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
=C2=A0 =C2=A0 <http://www.gnu.org/software/gdb/docu= mentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word&= quot;...
Reading symbols from kernel...
Reading symbols from
/usr/obj/usr/src/amd64.amd64/sys/GENERIC/kernel.debug...

Unread portion of the kernel message buffer:


__curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
55=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 __asm("movq %%gs:%P= 1,%0" : "=3Dr" (td) : "n"
(offsetof(struct pcpu,
(kgdb) backtrace
#0=C2=A0 __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
#1=C2=A0 doadump (textdump=3D<optimized out>) at
=C2=A0/usr/src/sys/kern/kern_shutdown.c:396
#2=C2=A0 0xffffffff80c07c2a in kern_reboot (howto=3D260) at
=C2=A0/usr/src/sys/kern/kern_shutdown.c:484
#3=C2=A0 0xffffffff80c080ce in vpanic (fmt=3D<optimized out>,
=C2=A0ap=3Dap@entry=3D0xfffffe01341fab50) at
=C2=A0/usr/src/sys/kern/kern_shutdown.c:923
#4=C2=A0 0xffffffff80c07f03 in panic (fmt=3D<unavailable>) at
=C2=A0/usr/src/sys/kern/kern_shutdown.c:847
#5=C2=A0 0xffffffff810c1fa7 in trap_fatal (frame=3D0xfffffe01341fac40,
=C2=A0eva=3D0) at /usr/src/sys/amd64/amd64/trap.c:942
#6=C2=A0 0xffffffff810c1fff in trap_pfault (frame=3D0xfffffe01341fac40, =C2=A0usermode=3Dfalse, signo=3D<optimized out>, ucode=3D<optimize= d out>)
=C2=A0 =C2=A0 at /usr/src/sys/amd64/amd64/trap.c:761
#7=C2=A0 <signal handler called>
#8=C2=A0 0xffffffff84a07067 in shmem_get_pages () from
=C2=A0/boot/modules/i915kms.ko
#9=C2=A0 0x0000000300000015 in ?? ()
#10 0x0000000000000060 in ?? ()
#11 0x0000000000000060 in ?? ()
#12 0x0000000000060000 in ?? ()
#13 0xfffffe00dc365a80 in ?? ()
#14 0xfffff00100000060 in ?? ()
#15 0xfffff8003e270c00 in ?? ()
#16 0x00000000fffff000 in ?? ()
#17 0xfffff8002138fc20 in ?? ()
#18 0xfffffe00dc365a80 in ?? ()
#19 0x0000000000000060 in ?? ()
#20 0xfffff8003e270c00 in ?? ()
#21 0x0000000000000060 in ?? ()
#22 0xfffffe0131e0fc80 in ?? ()
#23 0xfffffe01341fade0 in ?? ()
#24 0xffffffff84a07596 in shmem_pwrite () from
=C2=A0/boot/modules/i915kms.ko
#25 0x0000000000000000 in ?? ()
(kgdb)


Anything else I can do to help?

I=E2=80=99m now building drm-515-kmod, let=E2=80=99s see how that works in =
-stable.

/Mathias


Any updates here? I just r= an into this myself and am very close to just installing Linux on my laptop= , tbh.

I've rebuilt stable/13 today, then rebu= ilt the 510-kmod (because the 515-kmod doesn't even build) and pretty m= uch anything that's not an XTerm will panic/reboot the machine (a Think= pad T490 with Intel GPU).=C2=A0

dmesg got this to = say:

Fatal trap 12: page fault while in kernel mod= e
cpuid =3D 1; apic id =3D 02
fault virtual address =C2=A0 =3D 0x0fault code =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=3D supervisor = read data, page not present
instruction pointer =C2=A0 =C2=A0 =3D 0x20:0= xffffffff84430626
stack pointer =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =3D 0= x28:0xfffffe0140c83cf0
frame pointer =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =3D 0x28:0xfffffe0140c83d70
code segment =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0=3D base 0x0, limit 0xfffff, type 0x1b
=C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =3D DPL 0, p= res 1, long 1, def32 0, gran 1
processor eflags =C2=A0 =C2=A0 =C2=A0 =C2= =A0=3D interrupt enabled, resume, IOPL =3D 0
current process =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =3D 0 (i915-userptr-acquir)
trap number =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =3D 12
panic: page fault
cpuid =3D 1
t= ime =3D 1681221523
KDB: stack backtrace:
#0 0xffffffff80c5fc15 at kdb= _backtrace+0x65
#1 0xffffffff80c12e02 at vpanic+0x152
#2 0xffffffff80= c12ca3 at panic+0x43
#3 0xffffffff810d1577 at trap_fatal+0x387
#4 0xf= fffffff810d15cf at trap_pfault+0x4f
#5 0xffffffff810a8568 at calltrap+0x= 8
#6 0xffffffff84430c02 at __i915_gem_userptr_get_pages_worker+0x1f2
= #7 0xffffffff80e80883 at linux_work_fn+0xe3
#8 0xffffffff80c746f1 at tas= kqueue_run_locked+0x181
#9 0xffffffff80c759b3 at taskqueue_thread_loop+0= xc3
#10 0xffffffff80bcf55d at fork_exit+0x7d
#11 0xffffffff810a95de a= t fork_trampoline+0xe

It apparently dumps core= , will have to reacquaint myself with how to poke at this some more...
--000000000000808d8905f91026c2-- From nobody Tue Apr 11 15:03:06 2023 X-Original-To: freebsd-stable@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 4Pwpxg0KjKz450gr; Tue, 11 Apr 2023 15:03:19 +0000 (UTC) (envelope-from Mathias.Picker@virtual-earth.de) Received: from www94.your-server.de (www94.your-server.de [213.133.104.94]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Pwpxf5TW2z3PWx; Tue, 11 Apr 2023 15:03:18 +0000 (UTC) (envelope-from Mathias.Picker@virtual-earth.de) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=virtual-earth.de; s=default_1811; h=Content-Transfer-Encoding:Content-Type: MIME-Version:Message-ID:References:In-Reply-To:Subject:CC:To:From:Date:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID; bh=BxS3QvLplEr3rM6yvmj6+hKHGLp4wUjzeLLZm407510=; b=Eq2DbIETitZ3SLl8XSSUB7VJoY vBz/RPVmvL/bAzeO5ZbUEl9ZfwkL+y1mW7npUMfHPuoEPZMnmstS7wCRLxYXKpQFSNvIIIOviUP5O hOg4nFOWirgnX/cZ9+YJ9cjFP9KzQ0DB0TYAoZy9JeXbi8cZlian5df8bF5oB3A7pqvIfiG7Xpv5Z QD1GBva70b/zwhia5t3YqiEthuJWd4e9G6dC7jQ7nVA6yKuvFG1mprFiJYCp1X1q3hDGqODIa1gpP Gqbg1bIGySAgNa+V4/Z3dmIoI28zNjERDfEiuQcpjoGcQmG1XWjIVk97CHXAgdgXdYPaLGzoBIePg CCRpINFQ==; Received: from sslproxy05.your-server.de ([78.46.172.2]) by www94.your-server.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pmFWY-000NKf-5n; Tue, 11 Apr 2023 17:03:10 +0200 Received: from [2a01:598:c824:ec5c:4913:c3c1:3e7b:3ec] (helo=[IPv6:::1]) by sslproxy05.your-server.de with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pmFWX-0002UF-Kt; Tue, 11 Apr 2023 17:03:09 +0200 Date: Tue, 11 Apr 2023 17:03:06 +0200 From: Mathias Picker To: =?ISO-8859-1?Q?Ulrich_Sp=F6rlein?= CC: Cy Schubert , Shane Ambler , FreeBSD-STABLE , stable@freebsd.org Subject: =?US-ASCII?Q?Re=3A_-stable_from_today_dumps_core_with_?= =?US-ASCII?Q?drm-510-kmod_and_some_graphical_clients?= User-Agent: K-9 Mail for Android In-Reply-To: References: <86o7og27eh.fsf@virtual-earth.de> <8b47d0a4-a8f1-1841-ee59-3949fe69cbd7@ShaneWare.Biz> <20230327210535.9ED5A1D7@slippy.cwsent.com> <044587F7-4BA9-4585-A789-F4B53E8D02A2@virtual-earth.de> <20230327145629.3b55eed8@slippy> <86o7oa1i6t.fsf@virtual-earth.de> Message-ID: List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Authenticated-Sender: Mathias.Picker@virtual-earth.de X-Virus-Scanned: Clear (ClamAV 0.103.8/26872/Tue Apr 11 09:26:30 2023) X-Rspamd-Queue-Id: 4Pwpxf5TW2z3PWx X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:213.133.96.0/19, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Am 11=2E April 2023 16:17:13 MESZ schrieb "Ulrich Sp=C3=B6rlein" : >On Thu, Mar 30, 2023 at 3:29=E2=80=AFPM Mathias Picker < >Mathias=2EPicker@virtual-earth=2Ede> wrote: > >> >> Cy Schubert writes: >> >> > On Mon, 27 Mar 2023 23:43:35 +0200 >> > Mathias Picker wrote: >> > >> >> Am 27=2E M=C3=A4rz 2023 23:05:35 MESZ schrieb Cy Schubert >> >> : >> >> >In message >> >> ><8b47d0a4-a8f1-1841-ee59-3949fe69cbd7@ShaneWare=2EBiz>, Shane >> >> >Ambler w >> >> >rites: >> >> >> On 26/3/23 01:37, Mathias Picker wrote: >> >> >> > >> >> >> > Starting sddm works fine, starting my normal session >> >> >> > crashes or freezes >> >> >> > FreeBSD=2E >> >> >> > >> >> >> > I can find no error messages after a reboot=2E >> >> >> > >> >> >> > I found out, that I can start xterm or emacs (exwm) >> >> >> > without problems, >> >> >> > xrandr works with external screen, but once I start >> >> >> > anything more >> >> >> > demanding (I guess demanding of the GPU) everything >> >> >> > freezes or FreeBSD >> >> >> > even reboots=2E >> >> >> > >> >> >> > =C3=A2=E2=82=AC=C5=93Demanding=C3=A2=E2=82=AC means even simpl= e things like >> >> >> > qterminal=2E I tried firefox an >> >> >> d >> >> >> > blender and then I had it with the reboots and >> >> >> > didn=C3=A2=E2=82=AC=E2=84=A2t try anything else=2E >> >> >> > xedit works fine :) >> >> >> > >> >> >> > I have nothing in the logs, I have no idea where to look >> >> >> > or how to debug >> >> >> > this=2E >> >> >> > >> >> >> > Any ideas, tipps, help greatly apreciated=2E >> >> >> >> >> >> >> >> >> FreeBSD Developers Handbook Chapter 10: Kernel Debugging >> >> >> >> >> >> https://docs=2Efreebsd=2Eorg/en/books/developers-handbook/kerneld= ebug/ >> >> >> >> >> >> Running stable, kernel dumps may already be enabled, look in >> >> >> /var/crash >> >> >> >> >> >> By enabling a kernel dump when it panics (dumpdev=3D"AUTO" in >> >> >> rc=2Econf) the >> >> >> kernel core is saved to swap space, then on reboot gets >> >> >> copied to >> >> >> dumpdir (/var/crash) where you can then use kgdb (from >> >> >> devel/gdb) to get >> >> >> a stack trace to find where the panic happened=2E >> >> > >> >> >drm-*-kmod probably needs a rebuild=2E Likely a data structure >> >> >changed=2E In my >> >> >experience a simple rebuild of the port solves 90% of >> >> >drm-*-kmod crash >> >> >problems=2E >> >> > >> >> Hi Cy, >> >> >> >> sorry I didn't mention that, but I did rebuild drm-kmod, I >> >> actually do it after every new kernel build, just to be on the >> >> safe side=2E >> >> >> >> I switched my swap to non-encrypted and will look if I can get >> >> any information from the kernel dump tomorrow=2E >> >> >> >> Oh, and it's on a Thinkpad X1 Yoga 3rd gen, I just noticed I >> >> didn't mention this=2E >> > >> > It may be worth trying drm-515-kmod as some MFC that works with >> > 515 and >> > not 510 may have been committed=2E Linux-KPI commits are the usual >> > suspects=2E >> > >> > I use drm-515 with 14-CURRENT=2E >> >> Finally I found the time for a kernel crash dump=2E >> This is what kgdb says >> >> mathiasp:amd64=2Eamd64/sys/GENERIC% sudo kgdb kernel >> /var/crash/vmcore=2E2 >> GNU gdb (GDB) 13=2E1 [GDB v13=2E1 for FreeBSD] >> Copyright (C) 2023 Free Software Foundation, Inc=2E >> License GPLv3+: GNU GPL version 3 or later >> >> This is free software: you are free to change and redistribute it=2E >> There is NO WARRANTY, to the extent permitted by law=2E >> Type "show copying" and "show warranty" for details=2E >> This GDB was configured as "x86_64-portbld-freebsd13=2E1"=2E >> Type "show configuration" for configuration details=2E >> For bug reporting instructions, please see: >> =2E >> Find the GDB manual and other documentation resources online at: >> =2E >> >> For help, type "help"=2E >> Type "apropos word" to search for commands related to "word"=2E=2E=2E >> Reading symbols from kernel=2E=2E=2E >> Reading symbols from >> /usr/obj/usr/src/amd64=2Eamd64/sys/GENERIC/kernel=2Edebug=2E=2E=2E >> >> Unread portion of the kernel message buffer: >> >> >> __curthread () at /usr/src/sys/amd64/include/pcpu_aux=2Eh:55 >> 55 __asm("movq %%gs:%P1,%0" : "=3Dr" (td) : "n" >> (offsetof(struct pcpu, >> (kgdb) backtrace >> #0 __curthread () at /usr/src/sys/amd64/include/pcpu_aux=2Eh:55 >> #1 doadump (textdump=3D) at >> /usr/src/sys/kern/kern_shutdown=2Ec:396 >> #2 0xffffffff80c07c2a in kern_reboot (howto=3D260) at >> /usr/src/sys/kern/kern_shutdown=2Ec:484 >> #3 0xffffffff80c080ce in vpanic (fmt=3D, >> ap=3Dap@entry=3D0xfffffe01341fab50) at >> /usr/src/sys/kern/kern_shutdown=2Ec:923 >> #4 0xffffffff80c07f03 in panic (fmt=3D) at >> /usr/src/sys/kern/kern_shutdown=2Ec:847 >> #5 0xffffffff810c1fa7 in trap_fatal (frame=3D0xfffffe01341fac40, >> eva=3D0) at /usr/src/sys/amd64/amd64/trap=2Ec:942 >> #6 0xffffffff810c1fff in trap_pfault (frame=3D0xfffffe01341fac40, >> usermode=3Dfalse, signo=3D, ucode=3D) >> at /usr/src/sys/amd64/amd64/trap=2Ec:761 >> #7 >> #8 0xffffffff84a07067 in shmem_get_pages () from >> /boot/modules/i915kms=2Eko >> #9 0x0000000300000015 in ?? () >> #10 0x0000000000000060 in ?? () >> #11 0x0000000000000060 in ?? () >> #12 0x0000000000060000 in ?? () >> #13 0xfffffe00dc365a80 in ?? () >> #14 0xfffff00100000060 in ?? () >> #15 0xfffff8003e270c00 in ?? () >> #16 0x00000000fffff000 in ?? () >> #17 0xfffff8002138fc20 in ?? () >> #18 0xfffffe00dc365a80 in ?? () >> #19 0x0000000000000060 in ?? () >> #20 0xfffff8003e270c00 in ?? () >> #21 0x0000000000000060 in ?? () >> #22 0xfffffe0131e0fc80 in ?? () >> #23 0xfffffe01341fade0 in ?? () >> #24 0xffffffff84a07596 in shmem_pwrite () from >> /boot/modules/i915kms=2Eko >> #25 0x0000000000000000 in ?? () >> (kgdb) >> >> >> Anything else I can do to help? >> >> I=E2=80=99m now building drm-515-kmod, let=E2=80=99s see how that works= in >> -stable=2E >> >> /Mathias >> >> >Any updates here? I just ran into this myself and am very close to just >installing Linux on my laptop, tbh=2E 515 does not build, but RC6 works fine=2E =20 Have not tried -stable again, too much work currently=E2=80=A6 Good luck, Mathias > >I've rebuilt stable/13 today, then rebuilt the 510-kmod (because the >515-kmod doesn't even build) and pretty much anything that's not an XTerm >will panic/reboot the machine (a Thinkpad T490 with Intel GPU)=2E > >dmesg got this to say: > >Fatal trap 12: page fault while in kernel mode >cpuid =3D 1; apic id =3D 02 >fault virtual address =3D 0x0 >fault code =3D supervisor read data, page not present >instruction pointer =3D 0x20:0xffffffff84430626 >stack pointer =3D 0x28:0xfffffe0140c83cf0 >frame pointer =3D 0x28:0xfffffe0140c83d70 >code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, long 1, def32 0, gran 1 >processor eflags =3D interrupt enabled, resume, IOPL =3D 0 >current process =3D 0 (i915-userptr-acquir) >trap number =3D 12 >panic: page fault >cpuid =3D 1 >time =3D 1681221523 >KDB: stack backtrace: >#0 0xffffffff80c5fc15 at kdb_backtrace+0x65 >#1 0xffffffff80c12e02 at vpanic+0x152 >#2 0xffffffff80c12ca3 at panic+0x43 >#3 0xffffffff810d1577 at trap_fatal+0x387 >#4 0xffffffff810d15cf at trap_pfault+0x4f >#5 0xffffffff810a8568 at calltrap+0x8 >#6 0xffffffff84430c02 at __i915_gem_userptr_get_pages_worker+0x1f2 >#7 0xffffffff80e80883 at linux_work_fn+0xe3 >#8 0xffffffff80c746f1 at taskqueue_run_locked+0x181 >#9 0xffffffff80c759b3 at taskqueue_thread_loop+0xc3 >#10 0xffffffff80bcf55d at fork_exit+0x7d >#11 0xffffffff810a95de at fork_trampoline+0xe > >It apparently dumps core, will have to reacquaint myself with how to poke >at this some more=2E=2E=2E Mathias Picker Gesch=C3=A4ftsf=C3=BChrer virtual earth Gesellschaft f=C3=BCr Wissens re/pr=C3=A4 sentation mbH Westendstr=2E 142 80339 M=C3=BCnchen +4915256178344 From nobody Tue Apr 11 15:03:06 2023 X-Original-To: stable@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 4Pwpxg0KjKz450gr; Tue, 11 Apr 2023 15:03:19 +0000 (UTC) (envelope-from Mathias.Picker@virtual-earth.de) Received: from www94.your-server.de (www94.your-server.de [213.133.104.94]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Pwpxf5TW2z3PWx; Tue, 11 Apr 2023 15:03:18 +0000 (UTC) (envelope-from Mathias.Picker@virtual-earth.de) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=virtual-earth.de; s=default_1811; h=Content-Transfer-Encoding:Content-Type: MIME-Version:Message-ID:References:In-Reply-To:Subject:CC:To:From:Date:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID; bh=BxS3QvLplEr3rM6yvmj6+hKHGLp4wUjzeLLZm407510=; b=Eq2DbIETitZ3SLl8XSSUB7VJoY vBz/RPVmvL/bAzeO5ZbUEl9ZfwkL+y1mW7npUMfHPuoEPZMnmstS7wCRLxYXKpQFSNvIIIOviUP5O hOg4nFOWirgnX/cZ9+YJ9cjFP9KzQ0DB0TYAoZy9JeXbi8cZlian5df8bF5oB3A7pqvIfiG7Xpv5Z QD1GBva70b/zwhia5t3YqiEthuJWd4e9G6dC7jQ7nVA6yKuvFG1mprFiJYCp1X1q3hDGqODIa1gpP Gqbg1bIGySAgNa+V4/Z3dmIoI28zNjERDfEiuQcpjoGcQmG1XWjIVk97CHXAgdgXdYPaLGzoBIePg CCRpINFQ==; Received: from sslproxy05.your-server.de ([78.46.172.2]) by www94.your-server.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pmFWY-000NKf-5n; Tue, 11 Apr 2023 17:03:10 +0200 Received: from [2a01:598:c824:ec5c:4913:c3c1:3e7b:3ec] (helo=[IPv6:::1]) by sslproxy05.your-server.de with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pmFWX-0002UF-Kt; Tue, 11 Apr 2023 17:03:09 +0200 Date: Tue, 11 Apr 2023 17:03:06 +0200 From: Mathias Picker To: =?ISO-8859-1?Q?Ulrich_Sp=F6rlein?= CC: Cy Schubert , Shane Ambler , FreeBSD-STABLE , stable@freebsd.org Subject: =?US-ASCII?Q?Re=3A_-stable_from_today_dumps_core_with_?= =?US-ASCII?Q?drm-510-kmod_and_some_graphical_clients?= User-Agent: K-9 Mail for Android In-Reply-To: References: <86o7og27eh.fsf@virtual-earth.de> <8b47d0a4-a8f1-1841-ee59-3949fe69cbd7@ShaneWare.Biz> <20230327210535.9ED5A1D7@slippy.cwsent.com> <044587F7-4BA9-4585-A789-F4B53E8D02A2@virtual-earth.de> <20230327145629.3b55eed8@slippy> <86o7oa1i6t.fsf@virtual-earth.de> Message-ID: List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Authenticated-Sender: Mathias.Picker@virtual-earth.de X-Virus-Scanned: Clear (ClamAV 0.103.8/26872/Tue Apr 11 09:26:30 2023) X-Rspamd-Queue-Id: 4Pwpxf5TW2z3PWx X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:213.133.96.0/19, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Am 11=2E April 2023 16:17:13 MESZ schrieb "Ulrich Sp=C3=B6rlein" : >On Thu, Mar 30, 2023 at 3:29=E2=80=AFPM Mathias Picker < >Mathias=2EPicker@virtual-earth=2Ede> wrote: > >> >> Cy Schubert writes: >> >> > On Mon, 27 Mar 2023 23:43:35 +0200 >> > Mathias Picker wrote: >> > >> >> Am 27=2E M=C3=A4rz 2023 23:05:35 MESZ schrieb Cy Schubert >> >> : >> >> >In message >> >> ><8b47d0a4-a8f1-1841-ee59-3949fe69cbd7@ShaneWare=2EBiz>, Shane >> >> >Ambler w >> >> >rites: >> >> >> On 26/3/23 01:37, Mathias Picker wrote: >> >> >> > >> >> >> > Starting sddm works fine, starting my normal session >> >> >> > crashes or freezes >> >> >> > FreeBSD=2E >> >> >> > >> >> >> > I can find no error messages after a reboot=2E >> >> >> > >> >> >> > I found out, that I can start xterm or emacs (exwm) >> >> >> > without problems, >> >> >> > xrandr works with external screen, but once I start >> >> >> > anything more >> >> >> > demanding (I guess demanding of the GPU) everything >> >> >> > freezes or FreeBSD >> >> >> > even reboots=2E >> >> >> > >> >> >> > =C3=A2=E2=82=AC=C5=93Demanding=C3=A2=E2=82=AC means even simpl= e things like >> >> >> > qterminal=2E I tried firefox an >> >> >> d >> >> >> > blender and then I had it with the reboots and >> >> >> > didn=C3=A2=E2=82=AC=E2=84=A2t try anything else=2E >> >> >> > xedit works fine :) >> >> >> > >> >> >> > I have nothing in the logs, I have no idea where to look >> >> >> > or how to debug >> >> >> > this=2E >> >> >> > >> >> >> > Any ideas, tipps, help greatly apreciated=2E >> >> >> >> >> >> >> >> >> FreeBSD Developers Handbook Chapter 10: Kernel Debugging >> >> >> >> >> >> https://docs=2Efreebsd=2Eorg/en/books/developers-handbook/kerneld= ebug/ >> >> >> >> >> >> Running stable, kernel dumps may already be enabled, look in >> >> >> /var/crash >> >> >> >> >> >> By enabling a kernel dump when it panics (dumpdev=3D"AUTO" in >> >> >> rc=2Econf) the >> >> >> kernel core is saved to swap space, then on reboot gets >> >> >> copied to >> >> >> dumpdir (/var/crash) where you can then use kgdb (from >> >> >> devel/gdb) to get >> >> >> a stack trace to find where the panic happened=2E >> >> > >> >> >drm-*-kmod probably needs a rebuild=2E Likely a data structure >> >> >changed=2E In my >> >> >experience a simple rebuild of the port solves 90% of >> >> >drm-*-kmod crash >> >> >problems=2E >> >> > >> >> Hi Cy, >> >> >> >> sorry I didn't mention that, but I did rebuild drm-kmod, I >> >> actually do it after every new kernel build, just to be on the >> >> safe side=2E >> >> >> >> I switched my swap to non-encrypted and will look if I can get >> >> any information from the kernel dump tomorrow=2E >> >> >> >> Oh, and it's on a Thinkpad X1 Yoga 3rd gen, I just noticed I >> >> didn't mention this=2E >> > >> > It may be worth trying drm-515-kmod as some MFC that works with >> > 515 and >> > not 510 may have been committed=2E Linux-KPI commits are the usual >> > suspects=2E >> > >> > I use drm-515 with 14-CURRENT=2E >> >> Finally I found the time for a kernel crash dump=2E >> This is what kgdb says >> >> mathiasp:amd64=2Eamd64/sys/GENERIC% sudo kgdb kernel >> /var/crash/vmcore=2E2 >> GNU gdb (GDB) 13=2E1 [GDB v13=2E1 for FreeBSD] >> Copyright (C) 2023 Free Software Foundation, Inc=2E >> License GPLv3+: GNU GPL version 3 or later >> >> This is free software: you are free to change and redistribute it=2E >> There is NO WARRANTY, to the extent permitted by law=2E >> Type "show copying" and "show warranty" for details=2E >> This GDB was configured as "x86_64-portbld-freebsd13=2E1"=2E >> Type "show configuration" for configuration details=2E >> For bug reporting instructions, please see: >> =2E >> Find the GDB manual and other documentation resources online at: >> =2E >> >> For help, type "help"=2E >> Type "apropos word" to search for commands related to "word"=2E=2E=2E >> Reading symbols from kernel=2E=2E=2E >> Reading symbols from >> /usr/obj/usr/src/amd64=2Eamd64/sys/GENERIC/kernel=2Edebug=2E=2E=2E >> >> Unread portion of the kernel message buffer: >> >> >> __curthread () at /usr/src/sys/amd64/include/pcpu_aux=2Eh:55 >> 55 __asm("movq %%gs:%P1,%0" : "=3Dr" (td) : "n" >> (offsetof(struct pcpu, >> (kgdb) backtrace >> #0 __curthread () at /usr/src/sys/amd64/include/pcpu_aux=2Eh:55 >> #1 doadump (textdump=3D) at >> /usr/src/sys/kern/kern_shutdown=2Ec:396 >> #2 0xffffffff80c07c2a in kern_reboot (howto=3D260) at >> /usr/src/sys/kern/kern_shutdown=2Ec:484 >> #3 0xffffffff80c080ce in vpanic (fmt=3D, >> ap=3Dap@entry=3D0xfffffe01341fab50) at >> /usr/src/sys/kern/kern_shutdown=2Ec:923 >> #4 0xffffffff80c07f03 in panic (fmt=3D) at >> /usr/src/sys/kern/kern_shutdown=2Ec:847 >> #5 0xffffffff810c1fa7 in trap_fatal (frame=3D0xfffffe01341fac40, >> eva=3D0) at /usr/src/sys/amd64/amd64/trap=2Ec:942 >> #6 0xffffffff810c1fff in trap_pfault (frame=3D0xfffffe01341fac40, >> usermode=3Dfalse, signo=3D, ucode=3D) >> at /usr/src/sys/amd64/amd64/trap=2Ec:761 >> #7 >> #8 0xffffffff84a07067 in shmem_get_pages () from >> /boot/modules/i915kms=2Eko >> #9 0x0000000300000015 in ?? () >> #10 0x0000000000000060 in ?? () >> #11 0x0000000000000060 in ?? () >> #12 0x0000000000060000 in ?? () >> #13 0xfffffe00dc365a80 in ?? () >> #14 0xfffff00100000060 in ?? () >> #15 0xfffff8003e270c00 in ?? () >> #16 0x00000000fffff000 in ?? () >> #17 0xfffff8002138fc20 in ?? () >> #18 0xfffffe00dc365a80 in ?? () >> #19 0x0000000000000060 in ?? () >> #20 0xfffff8003e270c00 in ?? () >> #21 0x0000000000000060 in ?? () >> #22 0xfffffe0131e0fc80 in ?? () >> #23 0xfffffe01341fade0 in ?? () >> #24 0xffffffff84a07596 in shmem_pwrite () from >> /boot/modules/i915kms=2Eko >> #25 0x0000000000000000 in ?? () >> (kgdb) >> >> >> Anything else I can do to help? >> >> I=E2=80=99m now building drm-515-kmod, let=E2=80=99s see how that works= in >> -stable=2E >> >> /Mathias >> >> >Any updates here? I just ran into this myself and am very close to just >installing Linux on my laptop, tbh=2E 515 does not build, but RC6 works fine=2E =20 Have not tried -stable again, too much work currently=E2=80=A6 Good luck, Mathias > >I've rebuilt stable/13 today, then rebuilt the 510-kmod (because the >515-kmod doesn't even build) and pretty much anything that's not an XTerm >will panic/reboot the machine (a Thinkpad T490 with Intel GPU)=2E > >dmesg got this to say: > >Fatal trap 12: page fault while in kernel mode >cpuid =3D 1; apic id =3D 02 >fault virtual address =3D 0x0 >fault code =3D supervisor read data, page not present >instruction pointer =3D 0x20:0xffffffff84430626 >stack pointer =3D 0x28:0xfffffe0140c83cf0 >frame pointer =3D 0x28:0xfffffe0140c83d70 >code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, long 1, def32 0, gran 1 >processor eflags =3D interrupt enabled, resume, IOPL =3D 0 >current process =3D 0 (i915-userptr-acquir) >trap number =3D 12 >panic: page fault >cpuid =3D 1 >time =3D 1681221523 >KDB: stack backtrace: >#0 0xffffffff80c5fc15 at kdb_backtrace+0x65 >#1 0xffffffff80c12e02 at vpanic+0x152 >#2 0xffffffff80c12ca3 at panic+0x43 >#3 0xffffffff810d1577 at trap_fatal+0x387 >#4 0xffffffff810d15cf at trap_pfault+0x4f >#5 0xffffffff810a8568 at calltrap+0x8 >#6 0xffffffff84430c02 at __i915_gem_userptr_get_pages_worker+0x1f2 >#7 0xffffffff80e80883 at linux_work_fn+0xe3 >#8 0xffffffff80c746f1 at taskqueue_run_locked+0x181 >#9 0xffffffff80c759b3 at taskqueue_thread_loop+0xc3 >#10 0xffffffff80bcf55d at fork_exit+0x7d >#11 0xffffffff810a95de at fork_trampoline+0xe > >It apparently dumps core, will have to reacquaint myself with how to poke >at this some more=2E=2E=2E Mathias Picker Gesch=C3=A4ftsf=C3=BChrer virtual earth Gesellschaft f=C3=BCr Wissens re/pr=C3=A4 sentation mbH Westendstr=2E 142 80339 M=C3=BCnchen +4915256178344 From nobody Tue Apr 11 21:30:51 2023 X-Original-To: stable@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 4PwzXs2r15z44ccv for ; Tue, 11 Apr 2023 21:30:53 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PwzXs2DJDz3LTk; Tue, 11 Apr 2023 21:30:53 +0000 (UTC) (envelope-from jhb@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1681248653; 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; bh=MXbHr9ljf3OyAO0dxY5ZcjTPu1RX+Q+mbwusgrNcBHU=; b=WKRmeZMGGJ3/AMYnpaerjbqcTGK5aFgqyaik+s0OIk4r9tGh50Nm7ZAAXUdvxXVaUYZ3Dx s075+oNGBux/ERjWGEJWOWFpjsZM8XG0WizfRhe1gUuVoWyD7FYAAU96/a5PUlAGr9GQ7F 4qyrAAutwthqAqRmbFDzxvI1KRRU+Aq6O01UTu1he3ZpQpdeyM2Cdb1ff1qEIwlRweTmQ2 qaYMwrzf81GB/jERPHgJWGtQoin8RyqqPy+x9WhAGKEKbEkeHN/dX9frRvM5xSuUlAWq40 HDS0RZfWljLgOsSptk59fKi8Zi3rbjE12+n+rxw1IE3orwAcsz2c1efpHWHB7Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1681248653; 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; bh=MXbHr9ljf3OyAO0dxY5ZcjTPu1RX+Q+mbwusgrNcBHU=; b=ljrm9YWy6FcyI5PTito7SYxDqMMdPTueERChacYArLH8KK1XlGwqULU+uQ64h+j6QnAreJ vWRIzoi712CQ5uW47MLPVLN3tpp0FGIt1LTFKRYWMXXLbMGJgzeUju5xUg9wiDq4W7UrgN 6G8QKtcSXKiSFI/Kt8stZz8mZ3evJQVyLm7KxbE6vDhsc8o1uEUFd1NSmPGTfZ2PhaXO11 XmpkWfa9iDSayQgqDFLG1jvDhKeOPfUrT+CR+tBp04esJi2eGonXUTRNqtJJztKxpKaDS7 9IxszRI5w9XtZ6ELi2iWHJ+2CvvnINpNkJ7cRl6+laVfUkJ/ZX6LqzSagSWEDA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1681248653; a=rsa-sha256; cv=none; b=qlcGoJt8+H4HBHxT9rySU4w4ZHpIWbmUev1cU4+VJLnqiZ86CaMtzTVnuWe5LcVOZev7yq BwJh7gKAlAMAuRwXNGpzSUhPW9H+zvZgYOZfnMNf1wBhzFOyqJIIuqsJ/SG4UQrojY+Oqw SF4J5nvGo8OmgNKSZnKWzKTedXLS5DjACi0jv8ITzDTu90bD43i/nCtnF2OTrlW2tm+U9u PW6HWV9lVgwkvt4k9r7EjFEUKoUOGiZuNX6jz0Qnsl/JKo9sV+P1MdeHwZxwksXZi3RyUd +1SK5UhrJycLJBiyeyNJa9biTUloAYbNntxdvTCGg0Ol081Cwz4ZuM4NdHPaKg== Received: from [IPV6:2601:648:8680:16b0:f4ff:5acc:9dc0:ebcf] (unknown [IPv6:2601:648:8680:16b0:f4ff:5acc:9dc0:ebcf]) (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 did not present a certificate) (Authenticated sender: jhb) by smtp.freebsd.org (Postfix) with ESMTPSA id 4PwzXr6NNNz195n; Tue, 11 Apr 2023 21:30:52 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Message-ID: Date: Tue, 11 Apr 2023 14:30:51 -0700 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.9.1 Content-Language: en-US From: John Baldwin To: stable@FreeBSD.org Subject: Clarifications to kernel TLS offload support in 13.x Cc: Graham Perrin Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-ThisMailContainsUnwantedMimeParts: N Kernel TLS offload support for each direction (transmit and receive) operates in three different modes: software, ifnet, and TOE. Software KTLS uses software ciphers (or crypto offload engines on co-processors like qat(4)) to encrypt/decrypt TLS records at the socket buffer layer. ifnet TLS depends on encrpytion/decryption of TLS records being performed by the NIC as TLS records are either sent or received (mlx5 and cxgbe T6 do transmit ifnet TLS, mlx5 does receive ifnet TLS). TOE TLS is similar to ifnet TLS but it relies on a smart NIC that has a TCP offload engine that performs the encryption/decryption in the NIC (cxgbe T6 can do this) 13.0 included kernel TLS offload transmit support for all three modes and covering most commonly-used ciphers (TLS 1.0-1.3 using AES-CBC (MtE) and AES-GCM). It also included support for TLS offload receive support for AES-GCM with TLS 1.2 using either the software or TOE modes. 13.1 added support for the Chacha20-Poly1305 cipher suite, both for TLS 1.2 (send and receive) and TLS 1.3 (send-only) using the software mode. 13.2 added support for TLS 1.3 receive (AES-GCM and Chacha20), but only via the software mode. 14.0 adds support for ifnet mode TLS receive (currently supported on mlx5 adapters) for AES-GCM using versions 1.2 and 1.3. It also includes easier to use TOE support. KTLS is enabled/disabled on a global basis via the kern.ipc.tls.enable sysctl. In addition, ifnet TLS can be enabled/disabled on individual NICs via ifconfig using the "txtls" (for transmit) or "rxtls" (for receive) flags. Software and TOE TLS do not depend on ifconfig flags however. Software TLS is only controlled via the global sysctl. TOE TLS is controlled via driver-specific sysctls. -- John Baldwin From nobody Thu Apr 13 16:42:33 2023 X-Original-To: freebsd-stable@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 4Py53V2Mfvz45P0s for ; Thu, 13 Apr 2023 16:42:46 +0000 (UTC) (envelope-from greg.bal4@gmail.com) Received: from mail-oi1-x232.google.com (mail-oi1-x232.google.com [IPv6:2607:f8b0:4864:20::232]) (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 4Py53T3GRbz3sbj for ; Thu, 13 Apr 2023 16:42:45 +0000 (UTC) (envelope-from greg.bal4@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=lfsOO4zf; spf=pass (mx1.freebsd.org: domain of greg.bal4@gmail.com designates 2607:f8b0:4864:20::232 as permitted sender) smtp.mailfrom=greg.bal4@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-oi1-x232.google.com with SMTP id cd20so3945080oib.0 for ; Thu, 13 Apr 2023 09:42:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1681404164; x=1683996164; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=5XeaWiAuhhN+geh4KSeUoyzUzA3TyJGVAKhv+S+vbmM=; b=lfsOO4zfoZjtmBW6GmeXDw9I6kA2t6A67+KOTbVJ6s6YmZ6wvQXFvV4BonriO2rHVs mh8OUYuG4O9nh2IXxXb7EgwA12JwiZgiS16EeJEa5ULsurBmCwnXEAmno53DsXnLy8rL KI+0OpcHmARKMhC1fXSAgI4pSDj66mdWFXZxSMPmwyR9WT9l9a1BIyQS2seTQlwlc6Z+ K3+YfXLjh3KoXLLJG5545g7vhpZl0/UtsAtWpbbKemA2p9kkFgHIEAKPaAdMUAueUgqu lAHAwyo0YNjQtTIembXWswCDuWaSUZN5wpk3uifzBVJO8JbtEJ672zjxVbRn2lqQp7T/ mP9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681404164; x=1683996164; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=5XeaWiAuhhN+geh4KSeUoyzUzA3TyJGVAKhv+S+vbmM=; b=VvCIR6o9FndyE9QjBxpCxFrUBFjLQ1xZXSKRCz3PXWkGqfO5Kg1xg1/VrDoQnSiR+K rZJDtUg2XnWIuW//aQ2cIn8z8BW97uSjHTUwzcyZwbKqCgHDTyza35YKrTKvhutVU8+E K372GdoDuPD20iuMjs/Bbdw6a6yTMLqKv21TCXWa5mhrIvbY46M7rmHhGt969TcdSbBy jkmR2I4y/HUFhIziq1GbfbqT4OCh++B6YDE2tsm+SEu3ztydPgurgJ+yRKmst0/VxfUR kzJUIlOp239SSdxaxVggzwV3gvAx1oRCJH2gytm84sZVQZoWfgsWxV6bxL1kiwWK5OIQ A9Ig== X-Gm-Message-State: AAQBX9cNGCKqPPeNHRyKCE1RIBdA3El6flziLgQGEjEI/+9GVpbTkq/f TzeH5m+dA5tu1Cda8PrPkMFvxdLzBlkYzr2uH4S6QBIhhCo= X-Google-Smtp-Source: AKy350ZAqo8xC7ZuvwqvYOPc1YCt/4VkacHRkUx9dKfziGDUiMPdhsR4KF2tkxKUAoJWqkrK2oyZmJkTJswv6/EBAU4= X-Received: by 2002:a05:6808:288b:b0:384:6607:401 with SMTP id eu11-20020a056808288b00b0038466070401mr632576oib.0.1681404164044; Thu, 13 Apr 2023 09:42:44 -0700 (PDT) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 From: Greg Balfour Date: Thu, 13 Apr 2023 11:42:33 -0500 Message-ID: Subject: 13.2-RELEASE and firefox To: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::232:from]; ARC_NA(0.00)[]; TAGGED_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_NONE(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4Py53T3GRbz3sbj X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N I installed 13.2-RELEASE in a VMware VM and can't get firefox to start. Everything (xorg, vmware, firefox, etc.) is installed with packages. There are error messages about "Can't find profile directory." but Firefox does create the usual config directories with appropriate permissions. Interestingly, if I install www/tor-browser that does work. $ ls ~/.mozilla/firefox/ ./ installs.ini ../ irt0vtne.default/ bka4pgd6.default-release/ profiles.ini $ firefox console.error: ({}) JavaScript error: resource://gre/modules/XULStore.jsm, line 58: Error: Can't find profile directory. JavaScript error: resource://gre/modules/XULStore.jsm, line 58: Error: Can't find profile directory. console.error: (new TypeError("Cc[aContract] is undefined", "resource://gre/modules/XPCOMUtils.sys.mjs", 137)) JavaScript error: resource://gre/modules/XPCOMUtils.sys.mjs, line 137: TypeError: Cc[aContract] is undefined [ERROR glean_core] Error setting metrics feature config: Json(Error("EOF while parsing a value", line: 1, column: 0)) JavaScript error: resource://gre/modules/XULStore.jsm, line 58: Error: Can't find profile directory. console.error: (new SecurityError("Navigator.requestMIDIAccess: Access not allowed", (void 0), 3012)) JavaScript error: resource://gre/modules/TelemetrySession.sys.mjs, line 747: NS_ERROR_NOT_AVAILABLE: Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsITelemetry.msSinceProcessStartExcludingSuspend]