From nobody Fri Mar 29 18:43:40 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4V5q731WPLz5FSCs for ; Fri, 29 Mar 2024 18:43:43 +0000 (UTC) (envelope-from bojan.novkovic@kset.org) Received: from mail-ej1-f42.google.com (mail-ej1-f42.google.com [209.85.218.42]) (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 4V5q726rkzz4r8Y for ; Fri, 29 Mar 2024 18:43:42 +0000 (UTC) (envelope-from bojan.novkovic@kset.org) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-f42.google.com with SMTP id a640c23a62f3a-a44ad785a44so265723366b.3 for ; Fri, 29 Mar 2024 11:43:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711737821; x=1712342621; h=content-transfer-encoding:in-reply-to:autocrypt:from:cc:references :to:content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=nlU302bSgVlbmp6HYPZ9pMeDuhDjZZft13jand9Du1s=; b=KlkgpTizGRF0WD54LOiEGp3yZa9KhaFcHVxGEOHEGvCIRJtdTueCeprF49F9FGa3/x ubAbLmGejO/0CbsLVbFKPJaWWsO4lnfet7fWtxVxtcoXGdNMhMwsc2JJxJIeHpJcf3ga AiC5uST4SE8iDOQsNkFk1T0e2YqmfYXw4vs15La6GHKS2MT11vJ0wY1XSoVfQCGNkUMd mtnHMnjYI+C6GdAfLWrM5wvaMkH7A+YRK62tV1Ij27c9hjLq/MBUg3xHwbbPsOaQ8Zkn ZnHA/FD/+PXRwPUUtbXgqWzUbdUoADWApYxAyba6oIRjphXP81x1z7hm/pIka1XGxoJL k+MA== X-Gm-Message-State: AOJu0Yw6qDPaG5vRF32SAqgD/SI6kX28e180MYq2Y5dJXHs4IYe6TTgh fypSsoIKu1wgcFI7aIfvoat3xvLaES7rYCBFslc8Po4aaNqnMoCPVyVVy8qzFJJEbt/dBGtp8UP 4 X-Google-Smtp-Source: AGHT+IGGkf42m6fE2/KjnVxFkvuhfwJjHLszsidn3VbhuYD25XKLUj7JzvqRHqGF7W68mzpp/h31Og== X-Received: by 2002:a17:906:e8b:b0:a4e:eab:a8c1 with SMTP id p11-20020a1709060e8b00b00a4e0eaba8c1mr2184993ejf.33.1711737821051; Fri, 29 Mar 2024 11:43:41 -0700 (PDT) Received: from [192.168.0.91] ([109.60.96.219]) by smtp.gmail.com with ESMTPSA id x18-20020a1709060a5200b00a46ab3adea5sm2209603ejf.113.2024.03.29.11.43.40 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 29 Mar 2024 11:43:40 -0700 (PDT) Message-ID: <9dce6c42-0236-447c-b78b-dd03adff6eaa@freebsd.org> Date: Fri, 29 Mar 2024 19:43:40 +0100 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Multiple issues with current (kldload failures, missing CTF stuff, pty issues, ...) Content-Language: en-US To: Alexander Leidinger References: <09ef22679b76cb2dbeace8e78bf9f80e@Leidinger.net> Cc: Current From: =?UTF-8?Q?Bojan_Novkovi=C4=87?= Autocrypt: addr=bnovkov@freebsd.org; keydata= xjMEZdIQsxYJKwYBBAHaRw8BAQdA/V2uVmdN7VY2Ps8wDgLlWU3b9+kPdg9bf+FHgEEX49TN JUJvamFuIE5vdmtvdmnEhyA8Ym5vdmtvdkBGcmVlQlNELm9yZz7CmQQTFgoAQRYhBLAb6L2d hfD6hKflVB43npi7IZ8rBQJl0hCzAhsDBQkFo5qABQsJCAcCAiICBhUKCQgLAgQWAgMBAh4H AheAAAoJEB43npi7IZ8rzb0A/0aY3c/XubbtQzNyA0xzyKNZlDc9zesxEMVi6rOAZNz/AQC2 QmBTBEcbyOKDfJ5m02LpudVi9thZxlrr2n0ZX9kgA844BGXSELMSCisGAQQBl1UBBQEBB0Dn 3m+8g7KTp3yC4CLICis/CIonFfNqQcJOVv6Gd73adQMBCAfCfgQYFgoAJhYhBLAb6L2dhfD6 hKflVB43npi7IZ8rBQJl0hCzAhsMBQkFo5qAAAoJEB43npi7IZ8ruPcBAJM5wq5j64RFu4sc zrryK4FeCTt/Xhfyn3UhT2hHuYkPAQDWHDN6XZ097C5wUkWUr8ywHDlMM5gWIDbr9TMUudoc Aw== In-Reply-To: <09ef22679b76cb2dbeace8e78bf9f80e@Leidinger.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Queue-Id: 4V5q726rkzz4r8Y On 3/29/24 16:52, Alexander Leidinger wrote: > Hi, > > sources from 2024-03-11 work. Sources from 2024-03-25 and today don't > work (see below for the issue). As the monthly stabilisation pass > didn't find obvious issues, it is something related to my setup: >  - not a generic kernel >  - very modular kernel (as much as possible as a module) >  - bind_now (a build without fails too, tested with clean /usr/obj) >  - ccache (a build without fails too, tested with clean /usr/obj) >  - kernel retpoline (build without in progress) >  - userland retpoline (build without in progress) >  - kernel build with WITH_CTF / DDB_CTF (next one to test if it isn't > retpoline) >  - -fno-builtin >  - CPUFLAGS=native (except for stuff in /usr/src/sys/boot) >  - malloc production >  - COPTFLAGS= -O2 -pipe > > The issue is, that kernel modules load OK from loader, but once it > starts init any module fails to load (e.g. via autodetection of > hardware or rc.conf kld_list) with the message that the kernel and > module versions are out of sync and the module refuses to load. > > I tried the workaround to load the modules from the loader, which > works, but then I can't login remotely as ssh fails to allocate a pty. > By loading modules via the loader, I can see messages about missing > CTF info when the nvidia modules (from ports = not yet rebuild = in > /boot/modules/...ko instead of /boot/kernel/...ko) try to get > initialised... and it looks like they are failing to get initialised > because of this missing CTF stuff (I'm back to the previous boot env > to be able to login remotely and send mails, I don't have a copy of > the failure message at hand). > > I assume the missing CTF stuff is due to the CTF based pretty printing > (https://cgit.freebsd.org/src/commit/?id=c21bc6f3c2425de74141bfee07b609bf65b5a6b3). > Is this supposed to fail to load modules which are compiled without > CTF data? Shouldn't this work gracefully (e.g. spit out a warning that > pretty printing is not available for module X and have the module > working)? > This is indeed how it works, those messages are emitted by CTF loading routines in 'kern/kern_ctf.c' as a warning and do not affect the rest of the module loading process. However, I completely agree that they are cryptic and spammy, I'll try to do something about that. Bojan