Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#35857 - New kernel 3.9.6-1 breaks module loading

Attached to Project: Arch Linux
Opened by Martin Dratva (raqua) - Wednesday, 19 June 2013, 21:36 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Thursday, 20 June 2013, 23:29 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

Kernel upgrade causes module loading to fail. System boots to display manager, but keyboard and mouse do not work.
These messages are displayed during boot sequence and in logs:

Jun 18 00:08:33 Phenom_LXDE_copy [ 5.510604] systemd-modules-load[163]: Failed to lookup alias 'vboxdrv': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [ 5.510655] systemd-modules-load[163]: Failed to lookup alias 'vboxnetadp': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [ 5.510705] systemd-modules-load[163]: Failed to lookup alias 'vboxnetflt': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [ 5.510746] systemd-modules-load[163]: Failed to lookup alias 'loop': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [ 5.510786] systemd-modules-load[163]: Failed to lookup alias 'acpi-cpufreq': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [ 5.510828] systemd-modules-load[163]: Failed to lookup alias 'tpm_bios': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [ 5.510868] systemd-modules-load[163]: Failed to lookup alias 'tpm': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [ 5.510907] systemd-modules-load[163]: Failed to lookup alias 'tpm_tis': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [ 5.510947] systemd-modules-load[163]: Failed to lookup alias 'pci_hotplug': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [ 5.511931] systemd-modules-load[163]: Failed to lookup alias 'shpchp': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [ 5.512946] systemd-modules-load[163]: Failed to lookup alias 'ppp_generic': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [ 5.513948] systemd-modules-load[163]: Failed to lookup alias 'slhc': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [ 5.514961] systemd-modules-load[163]: Failed to lookup alias 'sg': Function not implemented
Jun 18 00:08:33 Phenom_LXDE_copy [ 5.904711] systemd[1]: Unit systemd-modules-load.service entered failed state.


Looking at failed systemd process won't give much information:

systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
Active: failed (Result: exit-code) since Wed 2013-06-19 23:03:37 CEST; 1min 25s ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 156 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

Reverting to previous kernel solves the issue.

Let me know if you want me to provide any additional logs/info.


Steps to reproduce:
Upgrade to 3.6.9-1 kernel.
This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Thursday, 20 June 2013, 23:29 GMT
Reason for closing:  Not a bug
Additional comments about closing:  User error, fixed
Comment by Tobias Powalowski (tpowa) - Thursday, 20 June 2013, 10:31 GMT
You need to update everything not only the kernel.
Comment by Martin Dratva (raqua) - Thursday, 20 June 2013, 10:32 GMT
I did update everything, kernel-headers, kernel-firmware, kernel-docs.
I did pacman -Syu.

Everything was updated to current latest versions.
Comment by Tobias Powalowski (tpowa) - Thursday, 20 June 2013, 12:06 GMT
Failed to lookup alias 'vboxdrv'
This indicated virtualbox modules, these must be updated too.
Comment by Martin Dratva (raqua) - Thursday, 20 June 2013, 12:14 GMT
virtualbox modules were also upgraded. As I said, ALL was up to date. And as you can see, also bunch of other modules failed to load.
If there was only VirtualBox modules missing, system would be perfectly usable, just VB would not run.
Comment by Tobias Powalowski (tpowa) - Thursday, 20 June 2013, 12:15 GMT
You have reboot your pc?
Comment by Martin Dratva (raqua) - Thursday, 20 June 2013, 12:22 GMT
Sure, the module loading fails during the reboot.
Comment by Tobias Powalowski (tpowa) - Thursday, 20 June 2013, 12:26 GMT
Perhaps stupid question, during update your /usr/lib was available?
If you use UEFI to boot you checked that your kernel was synced with your efi partition?
what does depmod -a report?
Comment by Martin Dratva (raqua) - Thursday, 20 June 2013, 12:30 GMT
my /usr/lib should be available as I have not done anything with it. I only have one root partition, not fancy partitioning is in use. I have upgraded/downgraded several times to check if there was any problem, but I have not found anything and I get the same result every time.

Besides, if my /usr/lib was unavailable, that should cause the problem also during downgrade I guess. Right?

I am not at the machine now, but will post depmod when I come home.
Shall I provide depmod also with downgraded kernel or only this failing one?
Comment by Tobias Powalowski (tpowa) - Thursday, 20 June 2013, 14:41 GMT
Your system seems pretty messed up, you are the only one having issues so something is really wrong on your machine.
Also check if enough disk space is available.
Comment by Martin Dratva (raqua) - Thursday, 20 June 2013, 14:46 GMT
I have this issue on two different computers and 4 different installations. Although they all are very similar. Everything worked fine for months at least. :/
But ok, there might be something specific to my system.

There is enough disk space.
Comment by Martin Dratva (raqua) - Thursday, 20 June 2013, 21:46 GMT
Ok, I found the problem.

I used to have grub-legacy and switched to syslinux with recent changes with merging /bin /sbin etc. folders.
But I have multiboot and did not noticed that although I had different root I was still booting the same kernel on all 3 partitions. So when I upgraded one partition to 3.9.6, this went fine, but I still booted 3.9.5 kernel from the partition that was not yet upgraded.
Stupid me. I did not realized that syslinux worked differently in this regard.

I tried to make it work with multiple partitions, but specifiing partition with mbr:identifier as wiki says did not work so in the end I switched to grub 2 and now it works.

Sorry that I wasted your time. But you pointed me in the right direction to find the problem.

Loading...