Re: Catastrophe Re: Proliferating LLVMs

Louis Epstein <le@main.lekno.ws> wrote:

Steven G. Kargl <sgk@removetroutmask.apl.washington.edu> wrote:

On Wed, 13 Mar 2024 00:37:39 +0000, Louis Epstein wrote:
 

Louis Epstein <le@main.lekno.ws> wrote:
 
My FTP upgrade from 13.2 to 13.3
has unexpectedly crashed everything
(here I am posting from a backup account
from an Ubuntu partition).
 
I can boot single-user on the SSD but
any attempt to go multi-user produces
a crash on a kldload process.
 
The messages with regard to the page panic
include a kdb backtrace listing
vpanic
panic
trap_fatal
trap_pfault
calltrap
ttm_bo_validate
ttm_bo_init_reserved
ttm_bo_init
radeon_bo_create
radeon_ttm_init
si_init
radeon_device_init
radeon_driver_load_kms
drm_dev_register
radeon_pci_probe
linux_pci_attach_device
device_attach
 
and it hits around kernel module loading time after the uhubs.
 
Any idea if there's a way to get a working 13.3 install without
destroying the existing accounts and so forth?
 
(I backed up a lot of the SSD's key partitions to an HDD but
rebuilding is quite a chore.The DVDs don't seem usable for
upgrading an existing FreeBSD installation,only for making
new ones?)

 
Boot to single-user mode (2 in the boot menu).  When you
get to the root# prompt.
 
For UFS2 system, do
 
# fsck -y
# fsck -y
 
I don't use ZFS, so don't know if the above matters.
 
# mount -a
# vi /etc/rc.conf
<comment out kld_list="radeaon_yada" line>
# sync
# exit
 
You should end up in a console, i.e., no X11 window.
Log in as root.
 
Assuming you have a populated /usr/ports,
 
% pkg info | grep kmod
drm-515-kmod-5.15.118_3

 
what's on my system is
drm-510-kmod-5.10.163_9

...and I see that 515 is for 14.x
and as noted I just installed 13.3.

and
drm-kmod-20220907_2
 

gpu-firmware-amd-kmod
...
gpu-firmware-radeon-kmod-verde
% portmaster -Byd drm-515-kmod
% portmaster -Byd gpu-firmware\*
% vi /etc/rc.conf
<uncomment out kld_list="radeaon_yada" line>
% sync
% shutdown -r now
 

 
The fix appears to have worked,BUT
I have not received a prompt to recompile
all applications that the freebsd.org
instructions for a binary upgrade indicated
would happen at this stage.

On closer examination this was optional...

I normally upgrade applications via
 
git -C /usr/ports pull [updating ports collection]
synth status           [checking what's needed at the moment]
synth prepare-system   [updating available packages]
pkg upgrade -r Synth   [installing the new stuff]
 
and have done none of these since updating the OS except
for a synth status that tells me nothing needs upgrades
and 13 that wanted rebuilds or replacements
before the OS upgrade still do.
 
Do I have to trigger the rebuild somehow or can I update
the ports collection without screwing up?

...I've pulled in the new ports and am indexing...

...in any case my failure to launch X successfully
since the flirtation with removing llvm12 and putting
it back has NOT been solved by upgrading 13.2->3.

-=-=-
The World Trade Center towers MUST rise again,
at least as tall as before...or terror has triumphed.