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--