You are not logged in.

#1 2021-06-04 10:02:21

amr962
Member
Registered: 2021-02-11
Posts: 51

systemd-hook script multiple segmentation faults when upgrading system

Here's the full pacman output:

[amr@dell ~]$ doas netbrake -r 65536 pacman -Syu
:: Synchronizing package databases...
 core is up to date
 extra                                          1552.3 KiB  52.7 KiB/s 00:29 [############################################] 100%
 community                                         5.5 MiB  52.6 KiB/s 01:48 [############################################] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (11) colord-1.4.5-3  composer-2.1.1-1  gtk-update-icon-cache-1:4.2.1-2  gtk3-1:3.24.29-2  libcolord-1.4.5-3
              libinput-1.18.0-1  linux-5.12.9.arch1-1  poppler-21.06.1-1  poppler-glib-21.06.1-1  util-linux-2.37-1
              util-linux-libs-2.37-1

Total Download Size:   109.46 MiB
Total Installed Size:  181.55 MiB
Net Upgrade Size:       -0.17 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 util-linux-libs-2.37-1-x86_64                   411.3 KiB  52.4 KiB/s 00:08 [############################################] 100%
 libcolord-1.4.5-3-x86_64                        171.3 KiB  52.1 KiB/s 00:03 [############################################] 100%
 util-linux-2.37-1-x86_64                          2.5 MiB  52.4 KiB/s 00:49 [############################################] 100%
 colord-1.4.5-3-x86_64                          1723.4 KiB  52.3 KiB/s 00:33 [############################################] 100%
 composer-2.1.1-1-any                            441.5 KiB  51.3 KiB/s 00:09 [############################################] 100%
 gtk-update-icon-cache-1:4.2.1-2-x86_64           17.1 KiB  41.7 KiB/s 00:00 [############################################] 100%
 gtk3-1:3.24.29-2-x86_64                           7.5 MiB  51.9 KiB/s 02:28 [############################################] 100%
 libinput-1.18.0-1-x86_64                        284.7 KiB  52.3 KiB/s 00:05 [############################################] 100%
 linux-5.12.9.arch1-1-x86_64                      94.9 MiB  39.8 KiB/s 40:43 [############################################] 100%
 poppler-21.06.1-1-x86_64                       1333.8 KiB  21.7 KiB/s 01:02 [############################################] 100%
 poppler-glib-21.06.1-1-x86_64                   255.8 KiB  23.1 KiB/s 00:11 [############################################] 100%
 Total (11/11)                                   109.5 MiB  40.4 KiB/s 46:13 [############################################] 100%
(11/11) checking keys in keyring                                             [############################################] 100%
(11/11) checking package integrity                                           [############################################] 100%
(11/11) loading package files                                                [############################################] 100%
(11/11) checking for file conflicts                                          [############################################] 100%
(11/11) checking available disk space                                        [############################################] 100%
:: Running pre-transaction hooks...
(1/1) Removing linux initcpios...
:: Processing package changes...
( 1/11) upgrading util-linux-libs                                            [############################################] 100%
( 2/11) installing libcolord                                                 [############################################] 100%
( 3/11) upgrading util-linux                                                 [############################################] 100%
( 4/11) upgrading colord                                                     [############################################] 100%
( 5/11) upgrading composer                                                   [############################################] 100%
( 6/11) upgrading gtk-update-icon-cache                                      [############################################] 100%
( 7/11) upgrading gtk3                                                       [############################################] 100%
( 8/11) upgrading libinput                                                   [############################################] 100%
( 9/11) upgrading linux                                                      [############################################] 100%
(10/11) upgrading poppler                                                    [############################################] 100%
(11/11) upgrading poppler-glib                                               [############################################] 100%
:: Running post-transaction hooks...
( 1/10) Creating system user accounts...
/usr/share/libalpm/scripts/systemd-hook: line 28: 91319 Segmentation fault      (core dumped) /usr/bin/systemd-sysusers
error: command failed to execute correctly
( 2/10) Reloading system manager configuration...
/usr/share/libalpm/scripts/systemd-hook: line 3: 91331 Segmentation fault      (core dumped) systemd-detect-virt --chroot
/usr/share/libalpm/scripts/systemd-hook: line 28: 91359 Segmentation fault      (core dumped) /usr/bin/systemctl daemon-reload
error: command failed to execute correctly
( 3/10) Creating temporary files...
/usr/share/libalpm/scripts/systemd-hook: line 28: 91377 Segmentation fault      (core dumped) /usr/bin/systemd-tmpfiles --create
error: command failed to execute correctly
( 4/10) Reloading device manager configuration...
/usr/share/libalpm/scripts/systemd-hook: line 3: 91388 Segmentation fault      (core dumped) systemd-detect-virt --chroot
/usr/share/libalpm/scripts/systemd-hook: line 28: 91406 Segmentation fault      (core dumped) /usr/bin/udevadm control --reload
error: command failed to execute correctly
( 5/10) Arming ConditionNeedsUpdate...
( 6/10) Updating module dependencies...
( 7/10) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 5.12.9-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [resume]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 5.12.9-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [resume]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
( 8/10) Reloading system bus configuration...
/usr/share/libalpm/scripts/systemd-hook: line 3: 94653 Segmentation fault      (core dumped) systemd-detect-virt --chroot
/usr/share/libalpm/scripts/systemd-hook: line 28: 94657 Segmentation fault      (core dumped) /usr/bin/systemctl try-reload-or-restart "$@"
error: command failed to execute correctly
( 9/10) Compiling GSettings XML schema files...
(10/10) Probing GTK3 input method modules...

What's the problem? Do I need to fix something manually?

Offline

#2 2021-06-04 14:04:38

equalizer876
Member
Registered: 2018-09-11
Posts: 78

Re: systemd-hook script multiple segmentation faults when upgrading system

Try sudo next time?

Offline

#3 2021-06-04 14:28:33

amr962
Member
Registered: 2021-02-11
Posts: 51

Re: systemd-hook script multiple segmentation faults when upgrading system

Does it matter? Not trying to be a smart-ass but I've been using doas in place of sudo for a while now and never had issues, the only difference about this update is that I'm using netbrake, I also don't know if that could cause issues, if you have any ideas to how it could mess things up please let me know.

Also let me know if you need to look at any extra logs etc..

Offline

#4 2021-06-04 18:49:37

eschwartz
Fellow
Registered: 2014-08-08
Posts: 4,097

Re: systemd-hook script multiple segmentation faults when upgrading system

There is absolutely no reason for it to matter whether you use sudo or doas or su or login on tty2 with the username "root" and the relevant password, to open a root session.

A segfault is a weird error to get here. Do you have the same problem if you try running these systemd commands directly (via doas since they need to be run as root) rather than having pacman run them for you?


Managing AUR repos The Right Way -- aurpublish (now a standalone tool)

Offline

#5 2021-06-05 11:12:52

amr962
Member
Registered: 2021-02-11
Posts: 51

Re: systemd-hook script multiple segmentation faults when upgrading system

I've tried running the failed commands via the script doing:

doas ./systemd-hook x
x = sysusers, tmpfiles, daemon-reload, udev-reload

And everything seemed to work fine (I didn't get any error messages), although I tried this after a restart since I've shut down my laptop before seeing your reply.

Offline

#6 2021-06-09 10:06:11

redmaniac
Member
Registered: 2013-02-21
Posts: 2

Re: systemd-hook script multiple segmentation faults when upgrading system

I have the same issue. Lenovo P14s. Reboot "fixed" this.

In my case it was

udevadm control --reload

that segfaulted. I was able to reproduce this by running sudo udevadm control --reload. Running sudo on other binaries worked just fine. Unfortunately, I did not have the presence of mind to check what happens if I run udevadm control --reload from a root shell.

sudo itself terminates with the segfault and there is a coredump for it. By debugging that I could see that it follows a code path where it attempts to die in the same way as the binary it launched in order to make the shell happy. There is no coredump for udevadm, though (probably some sort of safeguard against leaking sensitive memory content).
-> No luck there.

It's a long shot, but I started having trouble after installing TLP. This coincided with some other weird errors. I am not saying those are necessarily related, but they all occurred in a very narrow time window and only after I installed TLP. Basically I am wondering, if you might be using TLP as well and if some of these are happening on your end as well...

  • Invalid checksum of ext4 inodes (could have been from an ungraceful shutdown - nvme diskk reports 4 - but I do not remember having had one; This NB is one week old.)

  • Then this (it's obvious why I think this might be related to TLP; unsure if it has anything to do with this):

    Jun 09 07:43:05 xxxx kernel: Dazed and confused, but trying to continue
    Jun 09 07:43:05 xxxx kernel: Do you have a strange power saving mode enabled?
    Jun 09 07:43:05 xxxx kernel: Uhhuh. NMI received for unknown reason 2d on CPU 0.

Offline

#7 2021-06-14 06:53:55

redmaniac
Member
Registered: 2013-02-21
Posts: 2

Re: systemd-hook script multiple segmentation faults when upgrading system

Just to wrap this up from my end: I am still not sure what caused this particular problem on my machine, but since I uninstalled TLP I have not had any further issues. In the interest of full disclosure: I have also updated the UEFI firmware on my laptop, albeit a couple of days after uninstalling TLP. All those weird errors I saw went away the moment I uninstalled TLP.

It could be that TLP did some weird power-save magic to my NVME disk and that this caused  problems. But that's just guesswork and I have no way to debug this right now.

Offline

Board footer

Powered by FluxBB