Re: Multiple issues with current (kldload failures, missing CTF stuff, pty issues, ...)

[Alexander Leidinger]

Am 2024-03-29 18:13, schrieb Mark Johnston:

On Fri, Mar 29, 2024 at 04:52:55PM +0100, Alexander Leidinger wrote:

Hi,


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


sync and the module refuses to load.

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

What is the exact revision you're running?  There were some unrelated
changes to the kernel linker around the same time.

The working src is from 2024-03-11-094351 (GMT+0100).


Retpoline wasn't the cause, next test is the CTF stuff in the kernel...

The failing src was fetched after Glebs stabilization week message (and todays src before the sound stuff still fails).

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

nvidia modules (from ports = not yet rebuild = in /boot/modules/...ko

don't have a copy of the failure message at hand).

modules via the loader, I can see messages about missing CTF info when the 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 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)?

From my reading of linker_ctf_load_file(), this is exactly how it
already works.

Bye,
Alexander.

--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.org    netch...@freebsd.org  : PGP 0x8F31830F9F2772BF

Great that it works this way, I still suggest to print a message what the warning about missing stuff means.

signature.asc
Description: OpenPGP digital signature