Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 14 Dec 2021 08:36:12 +0300
From:      Mehmet Erol Sanliturk <m.e.sanliturk@gmail.com>
To:        "Julian H. Stacey" <jhs@berklix.com>
Cc:        hackers@freebsd.org
Subject:   Re: /boot/loader.conf debuging traces come out jumbled
Message-ID:  <CAOgwaMuGCYU1FeYwB2h2xkTah1SpdZ3MRT%2BW5TnCpMmKMWDrWA@mail.gmail.com>
In-Reply-To: <202112140007.1BE079G8030464@fire.js.berklix.net>
References:  <202112140007.1BE079G8030464@fire.js.berklix.net>

next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000551d2005d3149341
Content-Type: text/plain; charset="UTF-8"

On Tue, Dec 14, 2021 at 3:08 AM Julian H. Stacey <jhs@berklix.com> wrote:

> Debugging my /boot/loader.conf on 12.2-STABLE (with a 12.2-RELEASE kernel,
>
>   (as 12.2-STABLE & 12.3-RELEASE & 13.0-RELEASE GENERIC kernels crash
> during
>    boot on one machine here (To be subject of later analysis &
>    posting)...  I got distracted onto debugging boot options, after
>    output from booting screen rolled off the top), So I concentrated
>    first on identifying & hashing out noisey boot options , before
>    next searching how to capture boot text (maybe to a serial port ?) )
>
> I tried adding markers to loader.conf create deliberate visible error
> texts to
> mark around lines I wanted to study the effect of, eg
> fuse_load="YES" etc ...
>
> I added this in the middle of /boot/loader.conf :
>         ZZZZZZZZZ00000000_load="YES"
>         ZZZZZZZZZ00001111_load="YES"
>         ZZZZZZZZZ00002222_load="YES"
>         ZZZZZZZZZ44440000_load="YES"
>         ZZZZZZZZZ44441111_load="YES"
>         ZZZZZZZZZ44442222_load="YES"
>
> & next boot showed a weirdly disordered:
>
>         Loading configured modules...
>         can't find 'ZZZZZZZZZ00000000_load'
>         can't find 'ZZZZZZZZZ00002222_load'
>         can't find 'ZZZZZZZZZ44442222_load'
>         can't find 'ZZZZZZZZZ44440000_load'
>         can't find 'ZZZZZZZZZ44441111_load'
>         can't find 'ZZZZZZZZZ00001111_load'
>         /etc/hostid size=0x25
>
> its not even just a reverse order that one might have expected from
> a forth unstacker or some such. Makes it harder to trace what output
> lines come from which loader.conf lines.
>
> --
> Julian Stacey  http://berklix.com/jhs/  http://stolenvotes.uk
> Minimise contact,  vax insufficient.    Prime liar a liability to cons &
> UK.
>


The above message has triggered remembering one of experiences with
FreeBSD before 9.2(?) :


I am testing a C program with "clang" :


print ( ... 'A : ' ... ) a ;
print ( ... 'B : ' ... ) b ;
print ( ... 'C : ' ... ) c ;


Output ( like similar to the following but disordered with respect to its
liking ) :

B : ...
A : ...
C : ...

means "Unbelievable"  ...


Mehmet Erol Sanliturk

--000000000000551d2005d3149341--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOgwaMuGCYU1FeYwB2h2xkTah1SpdZ3MRT%2BW5TnCpMmKMWDrWA>