You are not logged in.

Pages: 1

#1 2014-10-07 15:56:25

LyCC
Member
Registered: 2012-09-05
Posts: 174

Kernel update 3.16.4 unable to boot

Hi everyone,

latest kernel update (yesterday, linux-3.16.4-1-x86_64.pkg.tar.xz) crashed the whole system, i re-installed the old package (linux-3.16.3-1-x86_64.pkg.tar.xz) and i managed to boot up, beyond recovery mod.
Here is a log from journal, any ideas what could cause this? Thanks in advance.

.... 
Oct 07 18:26:22 ArchPC kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Oct 07 18:26:22 ArchPC systemd[1]: RTC configured in localtime, applying delta of 180 minutes to system time.
Oct 07 18:26:22 ArchPC kernel: random: nonblocking pool is initialized
Oct 07 18:26:22 ArchPC systemd[1]: Cannot add dependency job for unit networkmanager.service, ignoring: Unit networkmanager.service failed to load: No such file or directo
Oct 07 18:26:22 ArchPC systemd[1]: Cannot add dependency job for unit alsa.service, ignoring: Unit alsa.service failed to load: No such file or directory.
Oct 07 18:26:22 ArchPC systemd[1]: Cannot add dependency job for unit crond.service, ignoring: Unit crond.service failed to load: No such file or directory.
Oct 07 18:26:22 ArchPC systemd-journal[162]: Journal started
Oct 07 18:26:22 ArchPC systemd-modules-load[156]: Failed to lookup alias 'acpi_cpufreq': Function not implemented
Oct 07 18:26:22 ArchPC systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
Oct 07 18:26:22 ArchPC systemd[1]: Failed to start Load Kernel Modules.
Oct 07 18:26:22 ArchPC systemd[1]: Unit systemd-modules-load.service entered failed state.
Oct 07 18:26:22 ArchPC systemd-fsck[150]: /dev/sda1: Superblock last write time is in the future.
Oct 07 18:26:22 ArchPC systemd-fsck[150]: (by less than a day, probably due to the hardware clock being incorrectly set).  FIXED.
Oct 07 18:26:25 ArchPC systemd-fsck[150]: /dev/sda1: 325062/1835008 files (1.0% non-contiguous), 4513585/7340032 blocks
Oct 07 18:26:25 ArchPC kernel: EXT4-fs (sda1): re-mounted. Opts: discard,data=ordered
Oct 07 18:26:25 ArchPC systemd-udevd[180]: starting version 216
Oct 07 18:26:25 ArchPC systemd-udevd[180]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/9-cdrom.rules:12
Oct 07 18:26:25 ArchPC systemd-udevd[180]: invalid rule '/etc/udev/rules.d/9-cdrom.rules:12'
Oct 07 18:26:25 ArchPC systemd-udevd[180]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/9-cdrom.rules:13
Oct 07 18:26:25 ArchPC systemd-udevd[180]: invalid rule '/etc/udev/rules.d/9-cdrom.rules:13'
Oct 07 18:26:25 ArchPC systemd-udevd[180]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/9-cdrom.rules:26
Oct 07 18:26:25 ArchPC systemd-udevd[180]: invalid rule '/etc/udev/rules.d/9-cdrom.rules:26'
Oct 07 18:26:25 ArchPC systemd-udevd[180]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/9-cdrom.rules:32
Oct 07 18:26:25 ArchPC systemd-udevd[180]: invalid rule '/etc/udev/rules.d/9-cdrom.rules:32'
Oct 07 18:26:25 ArchPC systemd-udevd[180]: unknown key 'BUS' in /etc/udev/rules.d/9-cdrom.rules:40
Oct 07 18:26:25 ArchPC systemd-udevd[180]: invalid rule '/etc/udev/rules.d/9-cdrom.rules:40'
Oct 07 18:26:25 ArchPC systemd-udevd[180]: unknown key 'BUS' in /etc/udev/rules.d/9-cdrom.rules:41
Oct 07 18:26:25 ArchPC systemd-udevd[180]: invalid rule '/etc/udev/rules.d/9-cdrom.rules:41'
Oct 07 18:26:25 ArchPC systemd[1]: media-SSD.mount: Directory /media/SSD to mount over is not empty, mounting anyway.
Oct 07 18:26:25 ArchPC mtp-probe[231]: checking bus 7, device 2: "/sys/devices/pci0000:00/0000:00:1d.2/usb7/7-2"
Oct 07 18:26:25 ArchPC mtp-probe[231]: bus: 7, device: 2 was not an MTP device
Oct 07 18:26:25 ArchPC mtp-probe[243]: checking bus 8, device 2: "/sys/devices/pci0000:00/0000:00:1d.7/usb8/8-3"
Oct 07 18:26:25 ArchPC mtp-probe[243]: bus: 8, device: 2 was not an MTP device
Oct 07 18:26:26 ArchPC mount[227]: fuse: device not found, try 'modprobe fuse' first
Oct 07 18:26:26 ArchPC systemd[1]: media-SSD.mount mount process exited, code=exited status=21
Oct 07 18:26:26 ArchPC systemd[1]: Failed to mount /media/SSD.
Oct 07 18:26:26 ArchPC systemd[1]: Dependency failed for Local File Systems.
Oct 07 18:26:26 ArchPC systemd[1]: Unit media-SSD.mount entered failed state.
Oct 07 18:26:26 ArchPC alsactl[278]: /usr/bin/alsactl: state_lock:114: file /var/lib/alsa/asound.state lock error: No such file or directory
Oct 07 18:26:26 ArchPC alsactl[278]: /usr/bin/alsactl: load_state:1677: Cannot open /var/lib/alsa/asound.state for reading: No such file or directory
Oct 07 18:26:27 ArchPC mount[236]: fuse: device not found, try 'modprobe fuse' first
Oct 07 18:26:27 ArchPC systemd[1]: media-Work.mount mount process exited, code=exited status=21
Oct 07 18:26:27 ArchPC systemd[1]: Failed to mount /media/Work.
Oct 07 18:26:27 ArchPC systemd[1]: Unit media-Work.mount entered failed state.
Oct 07 18:26:27 ArchPC systemd-journal[162]: Permanent journal is using 88.0M (max allowed 64.0M, trying to leave 4.0G free of 9.4G available → current limit 88.0M).
Oct 07 18:26:27 ArchPC systemd-journal[162]: Time spent on flushing to /var is 25.734ms for 721 entries.
Oct 07 18:26:27 ArchPC systemd-modules-load[290]: Failed to lookup alias 'acpi_cpufreq': Function not implemented
Oct 07 18:26:27 ArchPC systemd[1]: media-SSD.mount: Directory /media/SSD to mount over is not empty, mounting anyway.
Oct 07 18:26:27 ArchPC systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
Oct 07 18:26:27 ArchPC systemd[1]: Failed to start Load Kernel Modules.
Oct 07 18:26:27 ArchPC systemd[1]: Unit systemd-modules-load.service entered failed state.
Oct 07 18:26:27 ArchPC mount[244]: fuse: device not found, try 'modprobe fuse' first
Oct 07 18:26:27 ArchPC systemd[1]: media-Data.mount mount process exited, code=exited status=21
Oct 07 18:26:27 ArchPC systemd[1]: Failed to mount /media/Data.
Oct 07 18:26:27 ArchPC systemd[1]: Dependency failed for Local File Systems.
Oct 07 18:26:27 ArchPC systemd[1]: Unit media-Data.mount entered failed state.
Oct 07 18:26:27 ArchPC systemd[1]: Requested transaction contradicts existing jobs: Transaction is destructive.
Oct 07 18:26:27 ArchPC systemd[1]: syslog.socket failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Transaction is destru
Oct 07 18:26:27 ArchPC systemd[1]: Unit syslog.socket entered failed state.
Oct 07 18:26:27 ArchPC alsactl[305]: /usr/bin/alsactl: load_state:1729: No soundcards found...
Oct 07 18:26:28 ArchPC mount[292]: fuse: device not found, try 'modprobe fuse' first
Oct 07 18:26:28 ArchPC systemd[1]: media-SSD.mount mount process exited, code=exited status=21
Oct 07 18:26:28 ArchPC systemd[1]: Failed to mount /media/SSD.
Oct 07 18:26:28 ArchPC systemd[1]: Unit media-SSD.mount entered failed state.
Oct 07 18:26:28 ArchPC mount[295]: fuse: device not found, try 'modprobe fuse' first
Oct 07 18:26:28 ArchPC systemd[1]: media-Work.mount mount process exited, code=exited status=21
Oct 07 18:26:28 ArchPC systemd[1]: Failed to mount /media/Work.
Oct 07 18:26:28 ArchPC systemd[1]: Unit media-Work.mount entered failed state.
Oct 07 18:26:32 ArchPC systemd[315]: Failed at step EXEC spawning /bin/plymouth: No such file or directory
Oct 07 18:27:33 ArchPC mount[329]: fuse: device not found, try 'modprobe fuse' first
Oct 07 18:27:33 ArchPC systemd[1]: media-Data.mount mount process exited, code=exited status=21
Oct 07 18:27:33 ArchPC systemd[1]: Failed to mount /media/Data.
Oct 07 18:27:33 ArchPC systemd[1]: Unit media-Data.mount entered failed state.
Oct 07 18:27:52 ArchPC systemd[1]: Job sys-subsystem-net-devices-eth0.device/start timed out.
Oct 07 18:27:52 ArchPC systemd[1]: Timed out waiting for device sys-subsystem-net-devices-eth0.device.
Oct 07 18:32:32 ArchPC kernel: [drm] Initialized drm 1.1.0 20060810
Oct 07 18:32:32 ArchPC kernel: nvidia: disagrees about version of symbol module_layout
Oct 07 18:32:53 ArchPC kernel: nvidia: disagrees about version of symbol module_layout

Last edited by LyCC (2014-10-07 16:01:48)

Offline

#2 2014-10-07 16:00:54

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,727

Re: Kernel update 3.16.4 unable to boot

Do you have a separate /usr partition?

Offline

#3 2014-10-07 16:03:15

LyCC
Member
Registered: 2012-09-05
Posts: 174

Re: Kernel update 3.16.4 unable to boot

Scimmia wrote:

Do you have a separate /usr partition?

No, i have a 32GB partition that contains everything.

EDIT: if i update the kernel again, the same thing happens all over.

Last edited by LyCC (2014-10-07 16:09:41)

Offline

#4 2014-10-07 20:30:02

mrunion
Member
From: Jonesborough, TN
Registered: 2007-01-26
Posts: 1,938
Website

Re: Kernel update 3.16.4 unable to boot

Going out on a limb here, but is your /boot partition mounted when you update the Kernel? What is the output of

uname -a

and 

pacman -Qs linux

both BEFORE the installed Kernel that breaks, and AFTER installing the Kernel that breaks (and you've rebooted). If you can get that far at least. If not, can we see your pacman.log?

Matt

"It is very difficult to educate the educated."

Offline

#5 2014-10-07 22:03:54

Pse
Member
Registered: 2008-03-15
Posts: 415

Re: Kernel update 3.16.4 unable to boot

Did you try masking the nvidia kernel module? (Just to confirm it is not interfering?)

Last edited by Pse (2014-10-07 22:04:10)

Offline

#6 2014-10-08 17:16:15

LyCC
Member
Registered: 2012-09-05
Posts: 174

Re: Kernel update 3.16.4 unable to boot

mrunion wrote:

Going out on a limb here, but is your /boot partition mounted when you update the Kernel? What is the output of

uname -a

and 

pacman -Qs linux

both BEFORE the installed Kernel that breaks, and AFTER installing the Kernel that breaks (and you've rebooted). If you can get that far at least. If not, can we see your pacman.log?

Hi, i don't have a seperate boot partition, however i tried reinstalling the kernel and it gives no error.

uname -a
Linux ArchPC 3.16.3-1-ARCH #1 SMP PREEMPT Wed Sep 17 21:54:13 CEST 2014 x86_64 GNU/Linux
local/linux 3.16.3-1 (base)
    The Linux kernel and modules
local/linux-api-headers 3.16.2-1
    Kernel headers sanitized for use in userspace
local/linux-firmware 20140828.13eb208-1
    Firmware files for Linux
local/linux-headers 3.16.4-1
    Header files and scripts for building modules for Linux kernel

Pacman log:

[2014-10-06 21:02] [PACKAGEKIT] synchronizing package lists
[2014-10-06 21:20] [PACKAGEKIT] upgraded bash (4.3.029-1 -> 4.3.030-1)
[2014-10-06 21:20] [PACKAGEKIT] upgraded cpupower (3.16-1 -> 3.17-1)
[2014-10-06 21:20] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2014-10-06 21:20] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio.  Please wait...
[2014-10-06 21:20] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2014-10-06 21:20] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2014-10-06 21:20] [ALPM-SCRIPTLET] ==> Starting build: 3.16.4-1-ARCH
[2014-10-06 21:20] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2014-10-06 21:20] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2014-10-06 21:20] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2014-10-06 21:20] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2014-10-06 21:20] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2014-10-06 21:20] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2014-10-06 21:20] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2014-10-06 21:20] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2014-10-06 21:20] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-10-06 21:20] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2014-10-06 21:20] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-10-06 21:20] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2014-10-06 21:20] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2014-10-06 21:20] [ALPM-SCRIPTLET] ==> Starting build: 3.16.4-1-ARCH
[2014-10-06 21:20] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2014-10-06 21:20] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2014-10-06 21:20] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2014-10-06 21:20] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2014-10-06 21:20] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2014-10-06 21:20] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2014-10-06 21:20] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2014-10-06 21:20] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2014-10-06 21:20] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2014-10-06 21:20] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-10-06 21:20] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2014-10-06 21:20] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-10-06 21:20] [PACKAGEKIT] upgraded linux (3.16.3-1 -> 3.16.4-1)
[2014-10-06 21:20] [ALPM-SCRIPTLET] In order to use the new version, reload all virtualbox modules manually.
[2014-10-06 21:20] [PACKAGEKIT] upgraded virtualbox-host-modules (4.3.16-2 -> 4.3.16-3)
[2014-10-06 21:20] [PACKAGEKIT] upgraded lirc-utils (1:0.9.1.a-4 -> 1:0.9.1.a-5)
[2014-10-06 21:20] [PACKAGEKIT] upgraded python2-pillow (2.5.3-2 -> 2.6.0-1)
[2014-10-06 21:20] [PACKAGEKIT] upgraded linux-headers (3.16.3-1 -> 3.16.4-1)
[2014-10-07 00:26] [PACKAGEKIT] synchronizing package lists

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Pse wrote:

Did you try masking the nvidia kernel module? (Just to confirm it is not interfering?)

Hi, no, i haven't tried this, i switched the nvidia driver to the 340.xx legacy branch before the 3.16.3 kernel, meaning (to my knowlage) i have the latest driver installed:

pacman -Qs nvidia
local/lib32-libcl 1.1-1
    OpenCL library and ICD loader from NVIDIA (32-bit)
local/lib32-libvdpau 0.8-1
    Nvidia VDPAU library
local/lib32-nvidia-340xx-libgl 340.46-1
    NVIDIA drivers libraries symlinks (32-bit)
local/lib32-nvidia-340xx-utils 340.46-1
    NVIDIA drivers utilities (32-bit)
local/lib32-nvidia-cg-toolkit 3.1-4
    NVIDIA Cg libraries
local/lib32-opencl-nvidia-340xx 340.46-1
    OpenCL implemention for NVIDIA (32-bit)
local/libcl 1.1-4
    OpenCL library and ICD loader from NVIDIA
local/libvdpau 0.8-1
    Nvidia VDPAU library
local/nvidia-340xx 340.46-2
    NVIDIA drivers for linux, 340xx legacy branch
local/nvidia-340xx-libgl 340.46-2
    NVIDIA drivers libraries symlinks
local/nvidia-340xx-utils 340.46-2
    NVIDIA drivers utilities
local/nvidia-cg-toolkit 3.1-3
    NVIDIA Cg libraries
local/opacman -Qs nvidia
local/lib32-libcl 1.1-1
    OpenCL library and ICD loader from NVIDIA (32-bit)
local/lib32-libvdpau 0.8-1
    Nvidia VDPAU library
local/lib32-nvidia-340xx-libgl 340.46-1
    NVIDIA drivers libraries symlinks (32-bit)
local/lib32-nvidia-340xx-utils 340.46-1
    NVIDIA drivers utilities (32-bit)
local/lib32-nvidia-cg-toolkit 3.1-4
    NVIDIA Cg libraries
local/lib32-opencl-nvidia-340xx 340.46-1
    OpenCL implemention for NVIDIA (32-bit)
local/libcl 1.1-4
    OpenCL library and ICD loader from NVIDIA
local/libvdpau 0.8-1
    Nvidia VDPAU library
local/nvidia-340xx 340.46-2
    NVIDIA drivers for linux, 340xx legacy branch
local/nvidia-340xx-libgl 340.46-2
    NVIDIA drivers libraries symlinks
local/nvidia-340xx-utils 340.46-2
    NVIDIA drivers utilities
local/nvidia-cg-toolkit 3.1-3
    NVIDIA Cg libraries
local/opencl-nvidia-340xx 340.46-2
    OpenCL implemention for NVIDIA
pencl-nvidia-340xx 340.46-2
    OpenCL implemention for NVIDIA

However, i will try to remove it before my next attempt, just to be sure.

Last edited by LyCC (2014-10-08 17:21:42)

Offline

#7 2014-10-08 23:28:43

mrunion
Member
From: Jonesborough, TN
Registered: 2007-01-26
Posts: 1,938
Website

Re: Kernel update 3.16.4 unable to boot

Hmmmm. I have no idea then. I acts like something is not matching the newest Kernel when you upgrade. Are you using UEFI boot? If so, are you SURE you're not mounting a /boot partition over the UEFI boot partition? I;ve done that before myself. It's easy to do.

But if you've sure that the proper /boot is updated, then I have no idea what the problem is. Have you tried upgrading using "pacman" instead of "packagekit" or whatever pacman helper you appear to be using?

Matt

"It is very difficult to educate the educated."

Offline

#8 2014-10-09 05:15:12

LyCC
Member
Registered: 2012-09-05
Posts: 174

Re: Kernel update 3.16.4 unable to boot

Hi,

thanks for the support, i applied the latest bunch of updates, now it works just fine. I have no idea either ... however there was an nvidia utils update (maybe what Pse suggested) ... strange indeed, i have the 3.16.4 kernel now.

Linux ArchPC 3.16.4-1-ARCH #1 SMP PREEMPT Mon Oct 6 08:22:27 CEST 2014 x86_64 GNU/LinuxLinux ArchPC 3.16.4-1-ARCH #1 SMP PREEMPT Mon Oct 6 08:22:27 CEST 2014 x86_64 GNU/Linux

My arch installation is about 1.5 - 2 years old, i kind of worried since this is now windows, i shouldn't have to reinstalled it from time to time, plus all my settings, etc ... anyway i find it strange how systemd can die out like that "systemd[1]: Failed to start Load Kernel Modules." , unable to load any kernel module and going into recovery mode, where with modprobe i can manually load the modules.

Anyway, thank you guys for your support.

PS: should i mark the topic as "solved" since the problem is actually not solved, but rather has gone away.

Offline

#9 2014-10-09 07:46:52

sfbi
Member
From: Bergen
Registered: 2008-03-13
Posts: 36

Re: Kernel update 3.16.4 unable to boot

I have the same problem, and it is still unsolved.. I cannot boot into graphical interface even after downgrading linux and nvidia packages..

Offline

#10 2014-10-09 11:34:02

Aitch
Member
From: Norway
Registered: 2008-02-19
Posts: 43

Re: Kernel update 3.16.4 unable to boot

Newish installation I ran -Syu last night and didn't pay too much attention to what was updated (I know, slapped wrists) but when I tried to boot this morning I go to a blinking cursor.  Could be 3.16.4 or Nvidia (I haven't yet installed 340xx).  Will try to find out more this evening.

UPDATE: Sorry folks, this turned out to be a problem with nvidia-343.22.  Updated to 340xx and everything back to normal.

Last edited by Aitch (2014-10-09 16:53:08)

Offline

#11 2014-10-09 17:51:59

LyCC
Member
Registered: 2012-09-05
Posts: 174

Re: Kernel update 3.16.4 unable to boot

Yep, everyone with G8x, G9x, and GT2xx GPUs replace existing nvidia package with 340xx legacy pack, like suggested here:

https://www.archlinux.org/news/nvidia-340xx-and-nvidia/

Who has the same problem as i did, make sure that (or use the official) mirror is up to date. My problem was that i could not boot beyond emergency (recovery) mode. If you have this problem that i have, go to /var/cache/pacman/pkg, reinstall the old kernel (if you still have it),

pacman -U linux-3.16.3-1-x86_64.pkg.tar.xz

and boot up normally and do a full system update with a fully updated mirror (pacman -Syyu). At least this worked for me, but i have no idea what the actual problem was that systemd could not load any kernel modules and i just got the emergency mode.
Good luck everyone.

Last edited by LyCC (2014-10-09 17:54:03)

Offline

#12 2014-10-09 20:19:34

subatomic
Member
From: Berlin
Registered: 2005-06-26
Posts: 180

Re: Kernel update 3.16.4 unable to boot

What a scare! Installed 340xx and we're good to go!

Offline

Pages: 1

Board footer

Powered by FluxBB