You are not logged in.
I upgraded my kernel on a server from 4.10.4-1 to 4.10.6-1, and suddenly I lost all of my network interfaces, as well as other devices. Basically systemd-modules-load.service totally failed and the machine was unusable. I reinstalled the kernel, just in case, but no improvement. Downgrading to 4.10.4 fixed the problem.
Here's the sha256sum of the kernel package I tried:
639f0ce57ff2621d944c1e3e4c9084d8abddcb608dd85e7f7acd7d44056e7259 /var/cache/pacman/pkg/linux-4.10.6-1-x86_64.pkg.tar.xz
Has anyone else experienced similar issues?
Last edited by aweb (2017-04-02 05:41:42)
Offline
Yup, had the same issue going from 4.10.5 to 4.10.6 and downgrading did the trick.
Offline
Your best bet is to bisect the kernel and report the commit that breaks things in the upstream bug tracker.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Run lsmod under 4.10.4 and redirect to a text file. Do the same under 4.10.6. Sort each list them diff them. Are there any differences? In other words, did a module or more than one not get loaded? That can help you narrow it down if the fit bisect is too much for you.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Does the journal output from a 4.10.6 boot for systemd-modules-load.service not contain the names of modules that fail to load?
Offline
As a sanity check, did you run uname -a with the new kernel installed? Did the reported version match that of the installed version?
Checking to see if your boot loader managed to pick up an old kernel for which there are no longer drivers installed.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Does the journal output from a 4.10.6 boot for systemd-modules-load.service not contain the names of modules that fail to load?
Unfortunately, it doesn't print this out, and journalctl is not useful because somehow it resets all the logs after booting. But the problem is obviously modules failing to load.
Offline
So I just upgraded again to investigate further, and this time everything was fine. I can't reproduce the problem any more, even though the sha256 hash of my kernel file has not changed. I'm not sure what else changed, but before I did try reinstalling my kernel to no avail.
Offline