Solved Pkg upgrade ate my Thinkpad

Yesterday I 'upgraded' my thinkpad for the last time without first creating a new boot environment. You learn, eventually.

I did the pkg update then pkg upgrade.

The following info was displayed:

Code:
# pkg upgrade
Updating FreeBSD-ports repository catalogue...
FreeBSD-ports repository is up to date.
Updating FreeBSD-ports-kmods repository catalogue...
Fetching data: 100%    46 KiB  46.9 kB/s    00:01   
Processing entries: 100%
FreeBSD-ports-kmods repository update completed. 294 packages processed.
All repositories are up to date.
Checking for upgrades (46 candidates): 100%
Processing candidates (46 candidates): 100%
The following 45 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
    adwaita-qt5: 1.4.2 -> 1.4.2_1 [FreeBSD-ports]
    chromium: 156.0.8078.47 -> 156.0.8078.47_1 [FreeBSD-ports] (vulnerable!)
    doas: 6.4 -> 6.4_1 [FreeBSD-ports]
    drm-612-kmod: 6.12.85.1501000_2 -> 6.12.110.1501000_3 [FreeBSD-ports]
    git: 2.56.0 -> 2.56.1 [FreeBSD-ports]
    go126: 1.26.10 -> 1.26.11 [FreeBSD-ports]
    graphviz: 16.1.0_2 -> 16.1.0_3 [FreeBSD-ports]
    gstreamer1: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-libav: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-a52dec: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-bad: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-core: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-dts: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-dvdread: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-faac: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-faad: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-flac: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-gl: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-good: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-lame: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-mpg123: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-ogg: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-pango: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-png: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-pulse: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-resindvd: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-soup: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-theora: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-ugly: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-vorbis: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-wavpack: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    gstreamer1-plugins-x: 1.28.8 -> 1.28.9 [FreeBSD-ports]
    libjxl: 0.12.0 -> 0.12.0_1 [FreeBSD-ports]
    linux-chrome: 157.0.8103.38 -> 157.0.8103.50 [FreeBSD-ports]
    micro: 2.0.15_12 -> 2.0.15_13 [FreeBSD-ports]
    openexr: 3.4.17 -> 3.4.18 [FreeBSD-ports]
    py312-certifi: 2026.7.22 -> 2026.10.23 [FreeBSD-ports]
    py312-sqlite3: 3.12.15_10 -> 3.12.16_10 [FreeBSD-ports]
    py312-tkinter: 3.12.15_11 -> 3.12.16_11 [FreeBSD-ports]
    python311: 3.11.17 -> 3.11.18 [FreeBSD-ports] (vulnerable!)
    python312: 3.12.15 -> 3.12.16 [FreeBSD-ports] (vulnerable!)
    syncthing: 2.1.5_2 -> 2.1.5_3 [FreeBSD-ports]
    xfce4-datetime-plugin: 0.8.3_3 -> 0.8.3_5 [FreeBSD-ports]
    xorg-server: 21.1.25,1 -> 21.1.26,1 [FreeBSD-ports]

Number of packages to be upgraded: 45

470 MiB to be downloaded.

WARNING: 3 package(s) have known vulnerabilities

Proceed with this action? [y/N]: y

When I rebooted I was greeted with the blank black screen with solid white cursor at the top left of the screen. Oh f@#k, not again!

I used my other FreeBSD machine, which was at the same 15.1-RELEASE-p6 patch level, to work out which packages may have caused this issue by re-issuing the two update/upgrade commands, but not following through with the upgrade part.

It was obviously video system-related I thought, so I identified the two video-related packages that had been upgraded to newer versions. They were:

Code:
Suspected package(s) causing problem
====================================
drm-612-kmod:
old package version: 6.12.85.1501000_2   (before upgrade: system worked)
new package version: 6.12.110.1501000_3  (after upgrade: system doesn't work)

xorg-server
old package version: 21.1.25,1           (before upgrade: system worked)
new package version: 21.1.26,1           (after upgrade: system doesn't work - segmentation fault in Xorg when booting - see /var/log/Xorg.0.log)

I tried deleting these two newer package versions for drm-612-kmod and xorg-server using pkg delete but then discovered there appeared to be no way to install a specific package version, so back they went.

I thought if I could restore the two package versions that were known to work then I could return to a system where graphics were restored.

I then looked at dmesg output and saw:
Code:
pid 3590 (Xorg), jid 0, uid 0: exited on signal 6 (core dumped)

Next I looked into /var/log/Xorg.0.log output and found the following:
Code:
[    18.678] (EE)
[    18.678] (EE) Backtrace:
[    18.681] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    18.681] (EE) 0: /usr/local/libexec/Xorg (?+0x0) [0x3b1f9a]
[    18.683] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    18.683] (EE) 1: /lib/libthr.so.3 (?+0x0) [0x828b6945a]
[    18.685] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    18.685] (EE) 2: /lib/libthr.so.3 (?+0x0) [0x828b68a5b]
[    18.686] (EE) 3: [vdso] (?+0x0) [0x8215c32d3]
[    18.688] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    18.688] (EE) 4: /usr/local/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) [0x835ddf4cd]
[    18.689] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    18.690] (EE) 5: /usr/local/libexec/Xorg (?+0x0) [0x31f234]
[    18.691] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    18.691] (EE) 6: /usr/local/libexec/Xorg (?+0x0) [0x322df7]
[    18.692] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    18.692] (EE) 7: /usr/local/libexec/Xorg (?+0x0) [0x29c306]
[    18.694] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    18.694] (EE) 8: /usr/local/libexec/Xorg (?+0x0) [0x2aa37d]
[    18.695] (EE) 9: /usr/local/libexec/Xorg (miPointerUpdateSprite+0x1f6) [0x2a5cc6]
[    18.697] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    18.697] (EE) 10: /usr/local/libexec/Xorg (?+0x0) [0x2a5151]
[    18.698] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    18.698] (EE) 11: /usr/local/libexec/Xorg (?+0x0) [0x358fc7]
[    18.700] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    18.700] (EE) 12: /usr/local/libexec/Xorg (?+0x0) [0x3234b4]
[    18.701] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    18.701] (EE) 13: /usr/local/libexec/Xorg (?+0x0) [0x2dd96d]
[    18.703] (EE) 14: /usr/local/libexec/Xorg (WindowHasNewCursor+0x3e) [0x2d85ce]
[    18.704] (EE) 15: /usr/local/libexec/Xorg (ChangeWindowAttributes+0x109f) [0x2fcf2f]
[    18.705] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    18.705] (EE) 16: /usr/local/libexec/Xorg (?+0x0) [0x2c4904]
[    18.707] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    18.707] (EE) 17: /usr/local/libexec/Xorg (?+0x0) [0x2c3e20]
[    18.708] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    18.708] (EE) 18: /usr/local/libexec/Xorg (?+0x0) [0x2ce28c]
[    18.710] (EE) 19: /lib/libc.so.7 (__libc_start1+0x12f) [0x82b5d228f]
[    18.712] (EE) 20: /usr/local/libexec/Xorg (_start+0x24) [0x28fa44]
[    18.712] (EE)
[    18.712] (EE) Segmentation fault at address 0x100000000
[    18.712] (EE)
Fatal server error:
[    18.712] (EE) Caught signal 11 (Segmentation fault). Server aborting
[    18.712] (EE)
[    18.712] (EE)
Please consult the The X.Org Foundation support
     at http://wiki.x.org
 for help.
[    18.712] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    18.712] (EE)
[    18.712] (II) AIGLX: Suspending AIGLX clients for VT switch
[    18.727] (EE) Server terminated with error (1). Closing log file.

From that, it looks like the upgraded xorg-server has a problem.

1. Has anyone else seen this problem?
2. How can I restore my system to boot normally again - by restoring the old package versions, I suppose? If so, how?
 
then discovered there appeared to be no way to install a specific package version
pkg install something-1.0.1 does exactly what would be expected, it specifically installs version 1.0.1 of 'something', if it's a downgrade you're going to need to add -f though. But the big caveat here is that older versions of packages aren't kept in the FreeBSD repositories.

by restoring the old package versions, I suppose?
Unless you pkg-clean(8) you might find older versions of your packages cached in /var/cache/pkg.
 
pkg install something-1.0.1 does exactly what would be expected, it specifically installs version 1.0.1 of 'something', if it's a downgrade you're going to need to add -f though. But the big caveat here is that older versions of packages aren't kept in the FreeBSD repositories.
Thank you!
Yes, I tried installing the specific version and I used the '-f' option but to no avail, seemingly because, as you say, older package versions are not kept in the respositories.

Unless you pkg-clean(8) you might find older versions of your packages cached in /var/cache/pkg.
Luckily, I didn't do a clean and I just checked in /var/cache/pkg and found the following:

Code:
drm-612-kmod package:

lrwxr-xr-x  1 root wheel      46 Nov 16 23:07 drm-612-kmod-6.12.110.1501000_3.pkg -> drm-612-kmod-6.12.110.1501000_3~2$136jqoa6.pkg
-rw-r--r--  1 root wheel 4543156 Nov 14 01:31 drm-612-kmod-6.12.110.1501000_3~2$136jqoa6.pkg
lrwxr-xr-x  1 root wheel      45 Nov 10 18:44 drm-612-kmod-6.12.85.1501000_2.pkg -> drm-612-kmod-6.12.85.1501000_2~2$kjzyhnz4.pkg
-rw-r--r--  1 root wheel 4539489 Oct 24 02:28 drm-612-kmod-6.12.85.1501000_2~2$kjzyhnz4.pkg

and

Code:
xorg-server package:

lrwxr-xr-x  1 root wheel      36 Nov 10 17:54 xorg-server-21.1.25,1.pkg -> xorg-server-21.1.25,1~2$5oray14r.pkg
-rw-r--r--  1 root wheel 1629365 Oct 31 19:40 xorg-server-21.1.25,1~2$5oray14r.pkg
lrwxr-xr-x  1 root wheel      36 Nov 16 23:07 xorg-server-21.1.26,1.pkg -> xorg-server-21.1.26,1~2$s4ps453f.pkg
-rw-r--r--  1 root wheel 1629136 Nov 14 01:09 xorg-server-21.1.26,1~2$s4ps453f.pkg

First pkg delete the two currently installed packages I suppose?

Then something like:
Code:
# pkg install --local-only -f /var/cache/pkg/drm-612-kmod-6.12.85.1501000_2.pkg
# pkg install --local-only -f /var/cache/pkg/xorg-server-21.1.25,1.pkg
 
First pkg delete the two currently installed packages I suppose?
No, that's likely also going to delete everything that depends on those packages. pkg delete -f will delete them without removing everything that depends on them. But there's no need to delete anything beforehand. A pkg install -f will do the downgrade for you. For local packages (without a repository, like the files in the package cache) you could use pkg-add(8) instead of pkg-install(8).

For downgrades you'll need to add -f or it's going to complain the same or newer version is already installed and refuse to do anything.
 
No, that's likely also going to delete everything that depends on those packages. pkg delete -f will delete them without removing everything that depends on them. But there's no need to delete anything beforehand. A pkg install -f will do the downgrade for you. For local packages (without a repository, like the files in the package cache) you could use pkg-add(8) instead of pkg-install(8).

For downgrades you'll need to add -f or it's going to complain the same or newer version is already installed and refuse to do anything.
Magic, it worked, you are a star, thank you! :)
 
I wonder if this is a known bug in the xorg-server package version 21.1.26,1 or if this is just due to some misconfiguration of my machine?
However, the address in the segmentation fault looks suspect - a very round number, no? ---> [ 18.712] (EE) Segmentation fault at address 0x100000000
I will see if I can find where these bugs are listed.
 
Yeah, my lxqt/plasma broke after running pkg upgrade. No idea what went wrong. I just installed plasma again and it works now. But logging in with lxqt just went to a wayland session with black screen and mouse pointer. So...dunno. Didn't really care enough to look into what broke just reinstalled plasma and am using plasma. :D
 
Yeah, my lxqt/plasma broke after running pkg upgrade. No idea what went wrong. I just installed plasma again and it works now. But logging in with lxqt just went to a wayland session with black screen and mouse pointer. So...dunno. Didn't really care enough to look into what broke just reinstalled plasma and am using plasma. :D
I take it you are running Wayland and not X11/Xorg then?
 
Back
Top