Arch Linux

Tharbad

Member

Registered: 2016-02-27

Posts: 329

[SOLVED] Faulty modules loaded

Hi,

I'm maintaining the ck virtualbox host dkms package in AUR and I had a strange bug:
For some unknown reason, systemd or dkms inserted faulty modules after the vbox 6 update. I had to manually remove them with modprobe and then reload them again.
Checked pacman log, everything is OK there.

Edit:
That's what I did:
1) Updated the system using yay. Log is bellow.
2) Tried to run a vm and failed.
3) Run a script that re-installs ck host dkms package and then calls  systemd-modules-load. Still didn't work.
4) Started debug (including making sure the PKGBUILD and my script is OK), then I check systemd-modules-load log and noticed something is missing.
5) Removed the modules and re added them.

Since I rebuild-ed the modules before removing them, I can't tell u what they were (versions and so). All I know is that they didn't work and there was no error message.

Thanks

Last edited by Tharbad (2019-01-01 21:46:42)

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,456

Website

Re: [SOLVED] Faulty modules loaded

Is there a question here?  Do you need help with something?  If so, you'll need to provide a lot more (specific) information.

---

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Tharbad

Member

Registered: 2016-02-27

Posts: 329

Re: [SOLVED] Faulty modules loaded

I'm trying to understand if it's a dkms bug or systemd bug or it's normal.

If you need more info, just ask.

Last edited by Tharbad (2018-12-31 20:13:51)

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,426

Website

Re: [SOLVED] Faulty modules loaded

Post exact error messages, not vague descriptions: https://bbs.archlinux.org/viewtopic.php?id=57855

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

loqs

Member

Registered: 2014-03-06

Posts: 18,859

Re: [SOLVED] Faulty modules loaded

Post the pacman.log showing the update and the kernel messages and messages from systemd-modules-load.service for that boot.

Tharbad

Member

Registered: 2016-02-27

Posts: 329

Re: [SOLVED] Faulty modules loaded

Post exact error messages, not vague descriptions: https://bbs.archlinux.org/viewtopic.php?id=57855

There weren't any. The only clue I had came from comparing old working logs with new ones. When I did that I found out that the following entries were missing:

systemd-modules-load[395]: Inserted module 'vboxguest'
systemd-modules-load[395]: Inserted module 'vboxvideo'
systemd-modules-load[395]: Inserted module 'vboxdrv'
systemd-modules-load[395]: Inserted module 'vboxpci'
systemd-modules-load[395]: Inserted module 'vboxnetadp'
systemd-modules-load[395]: Inserted module 'vboxnetflt'

Post the pacman.log showing the update and the kernel messages and messages from systemd-modules-load.service for that boot.

systemd-modules-load.service above.

pacman:

[2018-12-31 00:56] [PACMAN] Running 'pacman -S -y -u --config /etc/pacman.conf --'
[2018-12-31 00:56] [PACMAN] synchronizing package lists
[2018-12-31 00:56] [PACMAN] starting full system upgrade
[2018-12-31 00:59] [ALPM] running '05-etckeeper-pre-install.hook'...
[2018-12-31 00:59] [ALPM] running '70-dkms-remove.hook'...
[2018-12-31 00:59] [ALPM-SCRIPTLET] ==> dkms remove vboxsf/5.2.22_OSE -k 4.19.12-arch1-1-ARCH
[2018-12-31 00:59] [ALPM-SCRIPTLET] ==> dkms remove vboxhost/5.2.22_OSE -k 4.19.12-1-ck-ivybridge
[2018-12-31 01:00] [ALPM-SCRIPTLET] ==> dkms remove vboxhost/5.2.22_OSE -k 4.14.90-1-lts
[2018-12-31 01:00] [ALPM-SCRIPTLET] ==> dkms remove vboxsf/5.2.22_OSE -k 4.19.12-1-ck-ivybridge
[2018-12-31 01:00] [ALPM-SCRIPTLET] ==> dkms remove rtl8192eu/1.0 -k 4.19.12-arch1-1-ARCH
[2018-12-31 01:00] [ALPM-SCRIPTLET] ==> dkms remove vboxguest/5.2.22_OSE -k 4.14.90-1-lts
[2018-12-31 01:00] [ALPM-SCRIPTLET] ==> dkms remove vboxhost/5.2.22_OSE -k 4.19.12-arch1-1-ARCH
[2018-12-31 01:00] [ALPM] running 'ghc-unregister.hook'...
[2018-12-31 01:00] [ALPM] transaction started
[2018-12-31 01:00] [ALPM] upgraded librsvg (2:2.44.10-1 -> 2:2.44.11-1)
[2018-12-31 01:00] [ALPM] upgraded atom (1.33.1-2 -> 1.33.1-3)
[2018-12-31 01:00] [ALPM] upgraded fmt (5.2.1-3 -> 5.3.0-1)
[2018-12-31 01:00] [ALPM] upgraded gobject-introspection-runtime (1.58.2-1 -> 1.58.3-1)
[2018-12-31 01:00] [ALPM] upgraded gobject-introspection (1.58.2-1 -> 1.58.3-1)
[2018-12-31 01:00] [ALPM] upgraded haskell-mono-traversable (1.0.10.0-1 -> 1.0.10.0-2)
[2018-12-31 01:00] [ALPM] upgraded haskell-conduit (1.3.1-14 -> 1.3.1-15)
[2018-12-31 01:00] [ALPM] upgraded haskell-sandi (0.4.3-8 -> 0.4.3-9)
[2018-12-31 01:00] [ALPM] upgraded hedgewars (0.9.24.1-80 -> 0.9.24.1-81)
[2018-12-31 01:00] [ALPM] upgraded lib32-librsvg (2.44.10-1 -> 2.44.11-1)
[2018-12-31 01:00] [ALPM] upgraded linux (4.19.12.arch1-1 -> 4.20.arch1-1)
[2018-12-31 01:00] [ALPM] upgraded linux-docs (4.19.12.arch1-1 -> 4.20.arch1-1)
[2018-12-31 01:00] [ALPM] upgraded linux-headers (4.19.12.arch1-1 -> 4.20.arch1-1)
[2018-12-31 01:00] [ALPM] upgraded nvidia (415.25-4 -> 415.25-5)
[2018-12-31 01:00] [ALPM] upgraded perl-carp-clan (6.06-4 -> 6.07-1)
[2018-12-31 01:00] [ALPM] upgraded python-jedi (0.13.1-2 -> 0.13.2-1)
[2018-12-31 01:00] [ALPM] upgraded vhba-module (20170610-123 -> 20170610-124)
[2018-12-31 01:00] [ALPM] upgraded virtualbox-host-dkms (5.2.22-3 -> 6.0.0-1)
[2018-12-31 01:01] [ALPM] upgraded virtualbox (5.2.22-3 -> 6.0.0-1)
[2018-12-31 01:01] [ALPM] upgraded virtualbox-guest-dkms (5.2.22-3 -> 6.0.0-1)
[2018-12-31 01:01] [ALPM] upgraded virtualbox-guest-iso (5.2.22-1 -> 6.0.0-1)
[2018-12-31 01:01] [ALPM-SCRIPTLET] ldconfig: /usr/lib/libbitcoinconsensus.so.0 is not a symbolic link
[2018-12-31 01:01] [ALPM-SCRIPTLET] 
[2018-12-31 01:01] [ALPM] transaction completed
[2018-12-31 01:01] [ALPM] running '60-linux.hook'...
[2018-12-31 01:01] [ALPM] running '70-dkms-install.hook'...
[2018-12-31 01:01] [ALPM-SCRIPTLET] ==> dkms install vboxguest/6.0.0_OSE -k 4.14.90-1-lts
[2018-12-31 01:01] [ALPM-SCRIPTLET] ==> dkms install douane/0.8.2 -k 4.20.0-arch1-1-ARCH
[2018-12-31 01:01] [ALPM-SCRIPTLET] Error! Bad return status for module build on kernel: 4.20.0-arch1-1-ARCH (x86_64)
[2018-12-31 01:01] [ALPM-SCRIPTLET] Consult /var/lib/dkms/douane/0.8.2/build/make.log for more information.
[2018-12-31 01:01] [ALPM-SCRIPTLET] ==> dkms install vboxhost/6.0.0_OSE -k 4.14.90-1-lts
[2018-12-31 01:02] [ALPM-SCRIPTLET] ==> dkms install vboxsf/6.0.0_OSE -k 4.19.12-1-ck-ivybridge
[2018-12-31 01:02] [ALPM-SCRIPTLET] ==> dkms install vboxhost/6.0.0_OSE -k 4.19.12-1-ck-ivybridge
[2018-12-31 01:02] [ALPM-SCRIPTLET] ==> dkms install vboxhost/6.0.0_OSE -k 4.20.0-arch1-1-ARCH
[2018-12-31 01:02] [ALPM-SCRIPTLET] ==> dkms install vboxsf/6.0.0_OSE -k 4.20.0-arch1-1-ARCH
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> dkms install rtl8192eu/1.0 -k 4.20.0-arch1-1-ARCH
[2018-12-31 01:03] [ALPM-SCRIPTLET] Error! Bad return status for module build on kernel: 4.20.0-arch1-1-ARCH (x86_64)
[2018-12-31 01:03] [ALPM-SCRIPTLET] Consult /var/lib/dkms/rtl8192eu/1.0/build/make.log for more information.
[2018-12-31 01:03] [ALPM] running '90-linux.hook'...
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> Starting build: 4.20.0-arch1-1-ARCH
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [bcache]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> Creating lz4-compressed initcpio image: /boot/initramfs-linux.img
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> Starting build: 4.20.0-arch1-1-ARCH
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [bcache]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> Creating lz4-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-12-31 01:03] [ALPM] running 'detect-old-perl-modules.hook'...
[2018-12-31 01:03] [ALPM-SCRIPTLET] WARNING: '/usr/lib/perl5/5.26' contains data from at least 3 packages which will NOT be used by the installed perl interpreter.
[2018-12-31 01:03] [ALPM-SCRIPTLET]  -> Run the following command to get a list of affected packages: pacman -Qqo '/usr/lib/perl5/5.26'
[2018-12-31 01:03] [ALPM-SCRIPTLET] WARNING: '/usr/lib/perl5/site_perl' contains data from at least 1 packages which will NOT be used by the installed perl interpreter.
[2018-12-31 01:03] [ALPM-SCRIPTLET]  -> Run the following command to get a list of affected packages: pacman -Qqo '/usr/lib/perl5/site_perl'
[2018-12-31 01:03] [ALPM-SCRIPTLET] WARNING: '/usr/lib/perl5/vendor_perl' contains data from at least 3 packages which will NOT be used by the installed perl interpreter.
[2018-12-31 01:03] [ALPM-SCRIPTLET]  -> Run the following command to get a list of affected packages: pacman -Qqo '/usr/lib/perl5/vendor_perl'
[2018-12-31 01:03] [ALPM] running 'gdk-pixbuf-query-loaders-32.hook'...
[2018-12-31 01:03] [ALPM] running 'gdk-pixbuf-query-loaders.hook'...
[2018-12-31 01:03] [ALPM] running 'ghc-register.hook'...
[2018-12-31 01:03] [ALPM] running 'gtk-update-icon-cache.hook'...
[2018-12-31 01:03] [ALPM] running 'nvidia.hook'...
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> Starting build: 4.20.0-arch1-1-ARCH
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [bcache]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> Creating lz4-compressed initcpio image: /boot/initramfs-linux.img
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> Starting build: 4.20.0-arch1-1-ARCH
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [bcache]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-12-31 01:03] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> Creating lz4-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2018-12-31 01:03] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-12-31 01:03] [ALPM] running 'systemd-daemon-reload.hook'...
[2018-12-31 01:04] [ALPM] running 'systemd-sysusers.hook'...
[2018-12-31 01:04] [ALPM] running 'systemd-udev-reload.hook'...
[2018-12-31 01:04] [ALPM] running 'systemd-update.hook'...
[2018-12-31 01:04] [ALPM] running 'update-desktop-database.hook'...
[2018-12-31 01:04] [ALPM] running 'update-mime-database.hook'...
[2018-12-31 01:04] [ALPM] running 'zz-etckeeper-post-install.hook'...

loqs

Member

Registered: 2014-03-06

Posts: 18,859

Re: [SOLVED] Faulty modules loaded

You are sure the virtualbox modules from virtualbox-host-dkms 5.2.22-3 were loaded after the upgrade to 6.0.0-1 instead of already being loaded so on the update they were not updated as they were already loaded?

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,456

Website

Re: [SOLVED] Faulty modules loaded

The only clue I had came from comparing old working logs with new ones...

Note that this is precisely one more clue than you provided us in your first post.  For future reference, you first post should contain actual / concrete / objective symptoms and any "clues" that led you to post your question.  All your first post contained was your inference or suspicion that "faulty" modules were loaded.  I couldn't even make heads or tails of what that would mean.  And now the evidence presented still doesn't support that inference.  The problem is/was that the virtualbox modules were simply not loaded as expected.

In otherwords, describe the problem's symptoms, not your guesses.

---

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Tharbad

Member

Registered: 2016-02-27

Posts: 329

Re: [SOLVED] Faulty modules loaded

You are sure the virtualbox modules from virtualbox-host-dkms 5.2.22-3 were loaded after the upgrade to 6.0.0-1 instead of already being loaded so on the update they were not updated as they were already loaded?

No. All I know that faulty ones were loaded. I don't know their version. I'll edit the post to include more details.

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,456

Website

Re: [SOLVED] Faulty modules loaded

All I know that faulty ones were loaded.

What does this mean?  How do you know this?  There is no evidence of this anywhere in the thread.

Failing to load modules properly is not evidence that faulty modules have been loaded, let alone exist.

Last edited by Trilby (2019-01-01 18:42:56)

---

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Tharbad

Member

Registered: 2016-02-27

Posts: 329

Re: [SOLVED] Faulty modules loaded

All I know that faulty ones were loaded.

What does this mean?  How do you know this?  There is no evidence of this anywhere in the thread.

Failing to load modules properly is not evidence that faulty modules have been loaded, let alone exist.

OK. Then it's another possibility.
I assumed that if there is no errors in the loading logs, that the case.

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,325

Re: [SOLVED] Faulty modules loaded

https://bbs.archlinux.org/viewtopic.php … 2#p1824072 is the BY FAR most likely case. Unless you can rule this out, it is what happened. And yes: that's normal. If you rebuild a module, you've to re-load it, which implies to unload it first.
(This can be pretty unreliable, depending on whether the module is currently in use)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Tharbad

Member

Registered: 2016-02-27

Posts: 329

Re: [SOLVED] Faulty modules loaded

https://bbs.archlinux.org/viewtopic.php … 2#p1824072 is the BY FAR most likely case. Unless you can rule this out, it is what happened. And yes: that's normal. If you rebuild a module, you've to re-load it, which implies to unload it first.
(This can be pretty unreliable, depending on whether the module is currently in use)

Thanks, I'll add to my script.