Arch Linux

jackpot

Member

From: Riyadh, Saudi Arabia

Registered: 2014-08-18

Posts: 86

[Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

Hi,

System does not boot to desktop manager after updating to Kernel 4.12.3-1. Grub seems to be working fine, but boot process halts at 'starting version 234'.

I had to downgrade kernels to be able to get back in DE.

Kernels used:

[2017-07-31 20:15] [ALPM] upgraded linux (4.11.9-1 -> 4.12.3-1)
[2017-07-31 20:15] [ALPM] upgraded linux-zen (4.11.8-1 -> 4.12.3-1)

My gut feeling it could be graphics driver but can't think beyond that. Boot debugging does not seem to give me any clue to track problem and find solution.

Appreciate if anyone can help.

Thanks.

Last edited by jackpot (2017-08-03 18:13:55)

---

KDE is all good bloated, try to trim away from K*.apps... whatever it leaves behind equals "Kuck yourself!"
nVidia.... fsck sdy0

ooo

Member

Registered: 2013-04-10

Posts: 1,638

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

Without any logs, your gut feeling is just as good as anyone elses.
You should see at least some messages from the failed boot in your journal.

If you've enabled systemd hook in your mkinitcpio.conf, this could also be initramfs related.

jackpot

Member

From: Riyadh, Saudi Arabia

Registered: 2014-08-18

Posts: 86

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

Thanks for comment.

I don't have any changes to default mkinitcpio (since last install I don't remember when) but journald log and dmesg didnot returned anything useful after successful & downgraded boot (except some BIOS/PAM related stuff). It was something similar (except time difference):

journalctl -p 3 -xb

Aug 01 17:06:28 my kernel: acpi LNXCPU:00: Invalid PBLK length [7]
Aug 01 17:06:28 my kernel: acpi LNXCPU:01: Invalid PBLK length [7]
Aug 01 17:06:28 my kernel: acpi LNXCPU:02: Invalid PBLK length [7]
Aug 01 17:06:28 my kernel: acpi LNXCPU:03: Invalid PBLK length [7]
Aug 01 17:06:28 my kernel: ACPI BIOS Error (bug): \_SB.PCI0._OSC: Excess arguments - ASL declare
Aug 01 17:06:28 my kernel: ACPI Error: [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS (20170
Aug 01 17:06:28 my kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0._OSC] (Node ffff
Aug 01 19:22:37 my sudo[18644]: pam_unix(sudo:auth): conversation failed
Aug 01 19:22:37 my sudo[18644]: pam_unix(sudo:auth): auth could not identify password for [me]
Aug 01 19:30:27 my kernel: usb 1-1-port1: disabled by hub (EMI?), re-enabling...

If there is a better way to look at 'last failed boot' errors then please let me know.

Thank you.

Last edited by jackpot (2017-08-01 17:10:04)

---

KDE is all good bloated, try to trim away from K*.apps... whatever it leaves behind equals "Kuck yourself!"
nVidia.... fsck sdy0

Azured

Member

Registered: 2014-02-08

Posts: 9

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

Use journalctl --list-boots to view the list of boots available in the logs.

Use journalctl -b <boot ID> to view the logs from the specified boot ID.

E.g.:

[azured@archdesktop ~]$ journalctl --list-boots
-207 3cfd69cc398f418d9a16fcd15461cb1f Sat 2017-01-14 21:19:44 GMT—Sat 2017-01-14
-206 fcceb6d99bef421b95ba1d8d8f259e42 Sat 2017-01-14 21:22:50 GMT—Sat 2017-01-14
-205 c88d0cc3058c456e9d4e669328302909 Sat 2017-01-14 21:42:34 GMT—Sat 2017-01-14
-204 6dd11ec3845245b29b95007416193103 Sat 2017-01-14 21:47:42 GMT—Sat 2017-01-14
-203 9164b2f903084093ab7029860371cf22 Sat 2017-01-14 21:56:40 GMT—Sat 2017-01-14
...

[azured@archdesktop ~]$ journalctl -b -206
-- Logs begin at Sat 2017-01-14 21:19:44 GMT
....

loqs

Member

Registered: 2014-03-06

Posts: 18,055

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

Does a different 4.12 kernel work such as linux 4.12.3-1 or linux-hardened 4.12.4.a-1?

seth

Member

Registered: 2012-09-03

Posts: 58,807

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

The OP seems to indicate he tested "linux 4.12.3-1", nevertheless and because of

[2017-07-31 20:15] [ALPM] upgraded linux-zen (4.11.8-1 -> 4.12.3-1)

i'd look at https://bugs.archlinux.org/task/54964 as well ;-)

---

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

loqs

Member

Registered: 2014-03-06

Posts: 18,055

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

@seth thanks missed that.
@jackpot Does the error still occur if you boot to a recovery shell?

jackpot

Member

From: Riyadh, Saudi Arabia

Registered: 2014-08-18

Posts: 86

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

Sorry all for disappearance. It seems the culprit is elevator=bfq as mentioned in bug referred by seth. Thank you!

FYI:
1. I was able to boot linux-lts or any version prior to 4.12
2. Was not able to boot recovery shell.
3. Had to resort to linux-lts (4.9.40) until figured out the problem.

Thank you all specially seth.

PS:
Although thread is solved, boot log (below) did not show anything unusual. How the culprit was identified?

-- Logs begin at Wed 2017-08-02 17:52:48 +03, end at Thu 2017-08-03 20:37:11 +03. --
Aug 02 17:52:48 my dbus-daemon[798]: Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service'
Aug 02 17:52:48 my systemd[777]: Starting GNOME Terminal Server...
Aug 02 17:52:48 my gnome-terminal-server[17095]: /usr/lib/gnome-terminal/gnome-terminal-migration: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory
Aug 02 17:52:48 my gnome-terminal-server[17095]: Profile migrator exited with status 127
Aug 02 17:52:48 my dbus-daemon[798]: Successfully activated service 'org.gnome.Terminal'
Aug 02 17:52:48 my systemd[777]: Started GNOME Terminal Server.
Aug 02 17:53:08 my systemd-logind[278]: System is rebooting.
Aug 02 17:53:08 my systemd[1]: Starting Generate shutdown-ramfs...
Aug 02 17:53:08 my systemd[1]: Stopping RealtimeKit Scheduling Policy Service...
Aug 02 17:53:08 my systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Aug 02 17:53:08 my gnome-session[494]: gnome-session-binary[494]: WARNING: Child process 648 was already dead.
Aug 02 17:53:08 my gnome-session-binary[494]: WARNING: Child process 648 was already dead.
Aug 02 17:53:08 my systemd[1]: Stopping Session c1 of user gdm.
Aug 02 17:53:08 my gdm[393]: Tried to look up non-existent conversation gdm-launch-environment
Aug 02 17:53:08 my gdm[393]: Freeing conversation 'gdm-launch-environment' with active job
Aug 02 17:53:08 my systemd[1]: Stopping Disk Manager...
Aug 02 17:53:08 my udisksd[902]: udisks daemon version 2.7.1 exiting
Aug 02 17:53:08 my systemd[1]: Stopping Session c2 of user me.
Aug 02 17:53:08 my systemd[1]: Stopping User Manager for UID 1000...
Aug 02 17:53:08 my systemd[1]: Stopping Location Lookup Service...
Aug 02 17:53:08 my systemd[1]: Stopped target Sound Card.
Aug 02 17:53:08 my systemd[1]: Stopped target Graphical Interface.
Aug 02 17:53:08 my systemd[1]: Stopping GNOME Display Manager...
Aug 02 17:53:08 my systemd[1]: Removed slice system-getty.slice.
Aug 02 17:53:08 my systemd[1]: Stopping Accounts Service...
Aug 02 17:53:08 my pulseaudio[866]: ICE default IO error handler doing an exit(), pid = 866, errno = 11
Aug 02 17:53:08 my systemd[1]: Stopping Manage, Install and Generate Color Profiles...
Aug 02 17:53:08 my systemd[1]: Stopping User Manager for UID 120...
Aug 02 17:53:08 my systemd[1]: Stopped target Multi-User System.
Aug 02 17:53:08 my systemd[1]: Stopped target Login Prompts.
Aug 02 17:53:08 my systemd[1]: Stopping CUPS Scheduler...
Aug 02 17:53:08 my systemd[1]: Stopped target Timers.
Aug 02 17:53:08 my systemd[1]: Stopped Daily verification of password and group files.
Aug 02 17:53:08 my systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Aug 02 17:53:08 my systemd[1]: Stopped Daily man-db cache update.
Aug 02 17:53:08 my systemd[1]: Stopped Daily rotation of log files.
Aug 02 17:53:08 my systemd[1]: Stopping Daemon for power management...
Aug 02 17:53:08 my systemd[1]: Stopped CUPS Scheduler.
Aug 02 17:53:08 my systemd[1]: Stopped Accounts Service.
Aug 02 17:53:08 my org.a11y.atspi.Registry[821]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Aug 02 17:53:08 my org.a11y.atspi.Registry[821]:       after 5279 requests (5279 known processed) with 0 events remaining.
Aug 02 17:53:08 my systemd[1]: Stopped Daemon for power management.
Aug 02 17:53:08 my /usr/lib/gdm/gdm-x-session[790]: (**) Option "fd" "24"
Aug 02 17:53:08 my /usr/lib/gdm/gdm-x-session[790]: (II) event4  - (II) Power Button: (II) device removed
Aug 02 17:53:08 my /usr/lib/gdm/gdm-x-session[790]: (**) Option "fd" "27"
Aug 02 17:53:08 my /usr/lib/gdm/gdm-x-session[790]: (II) event3  - (II) Power Button: (II) device removed
Aug 02 17:53:08 my /usr/lib/gdm/gdm-x-session[790]: (**) Option "fd" "31"
Aug 02 17:53:08 my /usr/lib/gdm/gdm-x-session[790]: (II) event11 - (II) HP WMI hotkeys: (II) device removed
Aug 02 17:53:08 my /usr/lib/gdm/gdm-x-session[790]: (**) Option "fd" "47"
Aug 02 17:53:08 my /usr/lib/gdm/gdm-x-session[790]: (II) event2  - (II) USB OPTICAL MOUSE : (II) device removed
Aug 02 17:53:08 my /usr/lib/gdm/gdm-x-session[790]: (**) Option "fd" "29"
Aug 02 17:53:08 my /usr/lib/gdm/gdm-x-session[790]: (II) event0  - (II)   USB Keyboard: (II) device removed
Aug 02 17:53:08 my /usr/lib/gdm/gdm-x-session[790]: (**) Option "fd" "63"
Aug 02 17:53:08 my /usr/lib/gdm/gdm-x-session[790]: (II) event1  - (II)   USB Keyboard: (II) device removed
Aug 02 17:53:08 my /usr/lib/gdm/gdm-x-session[790]: (II) UnloadModule: "libinput"
Aug 02 17:53:08 my /usr/lib/gdm/gdm-x-session[790]: (II) systemd-logind: releasing fd for 13:65
Aug 02 17:53:08 my systemd[1]: Stopped RealtimeKit Scheduling Policy Service.
Aug 02 17:53:08 my systemd[1]: Stopped Location Lookup Service.
Aug 02 17:53:08 my systemd[1]: Stopped Disk Manager.
Aug 02 17:53:08 my gnome-terminal-[17095]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Aug 02 17:53:08 my polkitd[405]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.18, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Aug 02 17:53:08 my org.gnome.Shell.desktop[577]: (EE)
Aug 02 17:53:08 my org.gnome.Shell.desktop[577]: Fatal server error:
Aug 02 17:53:08 my org.gnome.Shell.desktop[577]: (EE) failed to read Wayland events: Broken pipe
Aug 02 17:53:08 my org.gnome.Shell.desktop[577]: (EE)
Aug 02 17:53:08 my org.a11y.atspi.Registry[618]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":1024"
Aug 02 17:53:08 my org.a11y.atspi.Registry[618]:       after 21 requests (21 known processed) with 0 events remaining.
Aug 02 17:53:08 my systemd[1]: Stopped Session c1 of user gdm.
Aug 02 17:53:08 my systemd[1]: Stopped Manage, Install and Generate Color Profiles.
Aug 02 17:53:08 my systemd-logind[278]: Removed session c1.
Aug 02 17:53:08 my dbus[279]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service'
Aug 02 17:53:08 my dbus[279]: [system] Activation via systemd failed for unit 'accounts-daemon.service': Refusing activation, D-Bus is shutting down.
Aug 02 17:53:08 my gdm[393]: Failed to contact accountsservice: Error calling StartServiceByName for org.freedesktop.Accounts: GDBus.Error:org.freedesktop.systemd1.ShuttingDown: Refusing activation, D-Bus is shutting down.
Aug 02 17:53:08 my gdm[393]: Freeing conversation 'gdm-password' with active job
Aug 02 17:53:08 my polkitd[405]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.69, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Aug 02 17:53:08 my /usr/lib/gdm/gdm-x-session[790]: (II) UnloadModule: "libinput"
Aug 02 17:53:08 my /usr/lib/gdm/gdm-x-session[790]: (II) systemd-logind: releasing fd for 13:64
Aug 02 17:53:08 my /usr/lib/gdm/gdm-x-session[790]: (II) UnloadModule: "libinput"
Aug 02 17:53:08 my /usr/lib/gdm/gdm-x-session[790]: (II) systemd-logind: releasing fd for 13:66
Aug 02 17:53:08 my systemd[777]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE
Aug 02 17:53:08 my systemd[471]: Stopping D-Bus User Message Bus...
Aug 02 17:53:08 my systemd[471]: Stopping Sound Service...
Aug 02 17:53:08 my systemd[471]: Stopping Accessibility services bus...
Aug 02 17:53:08 my systemd[471]: Stopped target Default.
Aug 02 17:53:08 my systemd[777]: Stopped Sound Service.
Aug 02 17:53:08 my systemd[777]: pulseaudio.service: Unit entered failed state.
Aug 02 17:53:08 my systemd[777]: pulseaudio.service: Failed with result 'exit-code'.
Aug 02 17:53:08 my systemd[777]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE
Aug 02 17:53:08 my systemd[777]: Stopped GNOME Terminal Server.
Aug 02 17:53:08 my systemd[777]: gnome-terminal-server.service: Unit entered failed state.
Aug 02 17:53:08 my systemd[777]: gnome-terminal-server.service: Failed with result 'exit-code'.
Aug 02 17:53:08 my systemd[777]: Stopping Virtual filesystem service - Media Transfer Protocol monitor...
Aug 02 17:53:08 my systemd[777]: Stopped target Default.
Aug 02 17:53:08 my systemd[777]: Stopping Tracker metadata database store and lookup manager...
Aug 02 17:53:08 my systemd[777]: Stopping D-Bus User Message Bus...
Aug 02 17:53:08 my systemd[777]: Stopping Virtual filesystem service - disk device monitor...
Aug 02 17:53:08 my systemd[777]: Stopping Virtual filesystem service - GNOME Online Accounts monitor...
Aug 02 17:53:08 my systemd[777]: Stopping Evolution source registry...
Aug 02 17:53:08 my systemd[777]: Stopping Accessibility services bus...
Aug 02 17:53:08 my systemd[777]: Stopping Evolution calendar service...
Aug 02 17:53:08 my systemd[777]: Stopping Virtual filesystem service - digital camera monitor...
Aug 02 17:53:08 my systemd[777]: Stopping Virtual filesystem service...
Aug 02 17:53:08 my systemd[777]: Stopping Virtual filesystem service - Apple File Conduit monitor...
Aug 02 17:53:08 my systemd[777]: Stopping Virtual filesystem metadata service...
Aug 02 17:53:08 my systemd[777]: Stopping Evolution address book service...
Aug 02 17:53:08 my tracker-store[1108]: Received signal:15->'Terminated'
Aug 02 17:53:08 my tracker-store[1108]: OK
Aug 02 17:53:08 my systemd[777]: Stopped Virtual filesystem service - disk device monitor.
Aug 02 17:53:08 my systemd[777]: Stopped Virtual filesystem service - digital camera monitor.
Aug 02 17:53:08 my systemd[777]: Stopped Virtual filesystem service - Media Transfer Protocol monitor.
Aug 02 17:53:08 my systemd[777]: Stopped Virtual filesystem service - GNOME Online Accounts monitor.
Aug 02 17:53:08 my systemd[777]: Stopped Virtual filesystem service - Apple File Conduit monitor.
Aug 02 17:53:08 my systemd[777]: Stopped Virtual filesystem metadata service.
Aug 02 17:53:08 my systemd[471]: Stopped Accessibility services bus.
Aug 02 17:53:08 my systemd[471]: Stopped Sound Service.
Aug 02 17:53:08 my systemd[471]: Stopped D-Bus User Message Bus.
Aug 02 17:53:08 my systemd[471]: Stopped target Basic System.
Aug 02 17:53:08 my systemd[471]: Stopped target Sockets.
Aug 02 17:53:08 my systemd[471]: Closed GnuPG cryptographic agent and passphrase cache.
Aug 02 17:53:08 my systemd[471]: Closed D-Bus User Message Bus Socket.
Aug 02 17:53:08 my systemd[471]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Aug 02 17:53:08 my systemd[471]: Closed GnuPG network certificate management daemon.
Aug 02 17:53:08 my systemd[471]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Aug 02 17:53:08 my systemd[471]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Aug 02 17:53:08 my systemd[471]: Stopped target Timers.
Aug 02 17:53:08 my systemd[471]: Stopped target Paths.
Aug 02 17:53:08 my systemd[471]: Closed Sound System.
Aug 02 17:53:08 my systemd[1]: Unmounted /run/user/1000/gvfs.
Aug 02 17:53:08 my systemd[471]: Reached target Shutdown.
Aug 02 17:53:08 my systemd[471]: Starting Exit the Session...
Aug 02 17:53:08 my dbus[279]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service'
Aug 02 17:53:08 my dbus[279]: [system] Activation via systemd failed for unit 'accounts-daemon.service': Refusing activation, D-Bus is shutting down.
Aug 02 17:53:08 my systemd[777]: Stopped Evolution source registry.
Aug 02 17:53:08 my gdm[393]: Failed to contact accountsservice: Error calling StartServiceByName for org.freedesktop.Accounts: GDBus.Error:org.freedesktop.systemd1.ShuttingDown: Refusing activation, D-Bus is shutting down.
Aug 02 17:53:08 my gdm[393]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed
Aug 02 17:53:08 my systemd[777]: Stopped Evolution calendar service.
Aug 02 17:53:08 my systemd[777]: Stopped Tracker metadata database store and lookup manager.
Aug 02 17:53:08 my systemd[777]: Stopped Evolution address book service.
Aug 02 17:53:08 my systemd[1]: Stopped GNOME Display Manager.
Aug 02 17:53:08 my systemd[777]: Stopped D-Bus User Message Bus.
Aug 02 17:53:08 my systemd[777]: Stopped Virtual filesystem service.
Aug 02 17:53:08 my systemd[471]: Received SIGRTMIN+24 from PID 17228 (kill).
Aug 02 17:53:08 my systemd[480]: pam_unix(systemd-user:session): session closed for user gdm
Aug 02 17:53:08 my systemd[1]: Stopped User Manager for UID 120.
Aug 02 17:53:08 my systemd[1]: Removed slice User Slice of gdm.
Aug 02 17:53:08 my systemd[1]: Unmounted /run/user/120.
Aug 02 17:53:08 my /usr/lib/gdm/gdm-x-session[790]: (II) UnloadModule: "libinput"
Aug 02 17:53:08 my /usr/lib/gdm/gdm-x-session[790]: (II) systemd-logind: releasing fd for 13:75
Aug 02 17:53:08 my mkinitcpio[17213]: ==> Starting build: none
Aug 02 17:53:08 my mkinitcpio[17213]:   -> Running build hook: [sd-shutdown]
Aug 02 17:53:08 my /usr/lib/gdm/gdm-x-session[790]: (II) UnloadModule: "libinput"
Aug 02 17:53:08 my /usr/lib/gdm/gdm-x-session[790]: (II) systemd-logind: releasing fd for 13:67
Aug 02 17:53:08 my systemd[777]: pulseaudio.service: Service hold-off time over, scheduling restart.
Aug 02 17:53:08 my systemd[777]: Requested transaction contradicts existing jobs: Transaction is destructive.
Aug 02 17:53:08 my systemd[777]: pulseaudio.service: Failed to schedule restart job: Transaction is destructive.
Aug 02 17:53:08 my systemd[777]: pulseaudio.service: Unit entered failed state.
Aug 02 17:53:08 my systemd[777]: pulseaudio.service: Failed with result 'exit-code'.
Aug 02 17:53:09 my /usr/lib/gdm/gdm-x-session[790]: (II) UnloadModule: "libinput"
Aug 02 17:53:09 my /usr/lib/gdm/gdm-x-session[790]: (II) systemd-logind: releasing fd for 13:68
Aug 02 17:53:09 my /usr/lib/gdm/gdm-x-session[790]: (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
Aug 02 17:53:09 my /usr/lib/gdm/gdm-x-session[790]: (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
Aug 02 17:53:09 my /usr/lib/gdm/gdm-x-session[790]: (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
Aug 02 17:53:09 my systemd[777]: Stopped Accessibility services bus.
Aug 02 17:53:09 my systemd[777]: Stopped target Basic System.
Aug 02 17:53:09 my systemd[777]: Stopped target Sockets.
Aug 02 17:53:09 my systemd[777]: Closed GnuPG network certificate management daemon.
Aug 02 17:53:09 my systemd[777]: Closed D-Bus User Message Bus Socket.
Aug 02 17:53:09 my systemd[777]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Aug 02 17:53:09 my systemd[777]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Aug 02 17:53:09 my systemd[777]: Closed Sound System.
Aug 02 17:53:09 my systemd[777]: Closed GnuPG cryptographic agent and passphrase cache.
Aug 02 17:53:09 my systemd[777]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Aug 02 17:53:09 my systemd[777]: Stopped target Timers.
Aug 02 17:53:09 my systemd[777]: Stopped target Paths.
Aug 02 17:53:09 my systemd[777]: Reached target Shutdown.
Aug 02 17:53:09 my systemd[777]: Starting Exit the Session...
Aug 02 17:53:09 my systemd[777]: Received SIGRTMIN+24 from PID 17285 (kill).
Aug 02 17:53:09 my systemd[778]: pam_unix(systemd-user:session): session closed for user me
Aug 02 17:53:09 my systemd[1]: Stopped User Manager for UID 1000.
Aug 02 17:53:09 my /usr/lib/gdm/gdm-x-session[790]: (II) Server terminated successfully (0). Closing log file.
Aug 02 17:53:09 my systemd[1]: Stopped Session c2 of user me.
Aug 02 17:53:09 my systemd[1]: Removed slice User Slice of me.
Aug 02 17:53:09 my systemd[1]: Stopping Login Service...
Aug 02 17:53:09 my systemd[1]: Stopping Permit User Sessions...
Aug 02 17:53:09 my systemd[1]: Stopped Permit User Sessions.
Aug 02 17:53:09 my systemd[1]: Stopped target Remote File Systems.
Aug 02 17:53:09 my systemd[1]: Stopped target Network.
Aug 02 17:53:09 my systemd[1]: Stopping WPA supplicant...
Aug 02 17:53:09 my systemd[1]: Stopping Network Manager...
Aug 02 17:53:09 my NetworkManager[286]: <info>  [1501685589.1086] caught SIGTERM, shutting down normally.
Aug 02 17:53:09 my systemd[1]: Stopped WPA supplicant.
Aug 02 17:53:09 my NetworkManager[286]: <info>  [1501685589.2454] dns-mgr: Writing DNS information to /usr/bin/resolvconf
Aug 02 17:53:09 my NetworkManager[286]: <info>  [1501685589.2768] exiting (success)
Aug 02 17:53:09 my mkinitcpio[17213]: ==> Build complete.
Aug 02 17:53:09 my systemd[1]: Started Generate shutdown-ramfs.
Aug 02 17:53:09 my systemd[1]: Stopped Network Manager.
Aug 02 17:53:09 my systemd[1]: Stopped target Network (Pre).
Aug 02 17:53:09 my systemd[1]: Stopping firewalld - dynamic firewall daemon...
Aug 02 17:53:09 my systemd[1]: Stopped Login Service.
Aug 02 17:53:09 my systemd[1]: Stopped target User and Group Name Lookups.
Aug 02 17:53:14 my kernel: Ebtables v2.0 unregistered
Aug 02 17:53:15 my systemd[1]: Stopped firewalld - dynamic firewall daemon.
Aug 02 17:53:15 my systemd[1]: Stopping D-Bus System Message Bus...
Aug 02 17:53:15 my systemd[1]: Stopping Authorization Manager...
Aug 02 17:53:15 my systemd[1]: Stopped D-Bus System Message Bus.
Aug 02 17:53:15 my systemd[1]: Stopped Authorization Manager.
Aug 02 17:53:15 my systemd[1]: Stopped target Basic System.
Aug 02 17:53:15 my systemd[1]: Stopped target Slices.
Aug 02 17:53:15 my systemd[1]: Removed slice User and Session Slice.
Aug 02 17:53:15 my systemd[1]: Stopped target Sockets.
Aug 02 17:53:15 my systemd[1]: Closed CUPS Scheduler.
Aug 02 17:53:15 my systemd[1]: Closed D-Bus System Message Bus Socket.
Aug 02 17:53:15 my systemd[1]: Stopped target Paths.
Aug 02 17:53:15 my systemd[1]: Stopped CUPS Scheduler.
Aug 02 17:53:15 my systemd[1]: Stopped target System Initialization.
Aug 02 17:53:15 my systemd[1]: Stopped target Encrypted Volumes.
Aug 02 17:53:15 my systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
Aug 02 17:53:15 my systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
Aug 02 17:53:15 my systemd[1]: Stopping Update UTMP about System Boot/Shutdown...
Aug 02 17:53:15 my systemd[1]: Stopped Apply Kernel Variables.
Aug 02 17:53:15 my systemd[1]: Stopped Load Kernel Modules.
Aug 02 17:53:15 my systemd[1]: Stopping Load/Save Random Seed...
Aug 02 17:53:15 my systemd[1]: Stopped Update is Completed.
Aug 02 17:53:15 my systemd[1]: Stopped Rebuild Journal Catalog.
Aug 02 17:53:15 my systemd[1]: Stopped Rebuild Dynamic Linker Cache.
Aug 02 17:53:15 my systemd[1]: Stopped Load/Save Random Seed.
Aug 02 17:53:15 my systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
Aug 02 17:53:15 my systemd[1]: Stopped Create Volatile Files and Directories.
Aug 02 17:53:15 my systemd[1]: Stopped target Local File Systems.
Aug 02 17:53:15 my systemd[1]: Unmounting Temporary Directory (/tmp)...
Aug 02 17:53:15 my systemd[1]: Unmounting /run/user/1000...
Aug 02 17:53:15 my systemd[1]: Unmounting /home...
Aug 02 17:53:15 my systemd[1]: Unmounted Temporary Directory (/tmp).
Aug 02 17:53:15 my systemd[1]: Unmounted /run/user/1000.
Aug 02 17:53:15 my systemd[1]: Stopped target Swap.
Aug 02 17:53:15 my systemd[1]: Deactivating swap /dev/disk/by-uuid/d14d9a0e-6ed6-482c-ba01-57ae2c17d18f...
Aug 02 17:53:15 my systemd[1]: Deactivated swap /dev/disk/by-path/pci-0000:00:1f.2-ata-1-part2.
Aug 02 17:53:15 my systemd[1]: Deactivated swap /dev/disk/by-partuuid/d5972c0d-7684-4430-9a08-a75b7dca915a.
Aug 02 17:53:15 my systemd[1]: Deactivated swap /dev/disk/by-partlabel/swap.
Aug 02 17:53:15 my systemd[1]: Deactivated swap /dev/disk/by-id/wwn-0x50014ee103460f10-part2.
Aug 02 17:53:15 my systemd[1]: Deactivated swap /dev/disk/by-id/ata-WDC_WD5000AAKS-60Z1A0_WD-WCAWF8931467-part2.
Aug 02 17:53:15 my systemd[1]: Deactivated swap /dev/sda2.
Aug 02 17:53:15 my systemd[1]: Deactivated swap /dev/disk/by-uuid/d14d9a0e-6ed6-482c-ba01-57ae2c17d18f.
Aug 02 17:53:16 my systemd[1]: Unmounted /home.
Aug 02 17:53:16 my systemd[1]: Reached target Unmount All Filesystems.
Aug 02 17:53:16 my systemd[1]: Stopped File System Check on /dev/disk/by-uuid/c267b816-0425-485f-aa48-db3c0c3846a3.
Aug 02 17:53:16 my systemd[1]: Removed slice system-systemd\x2dfsck.slice.
Aug 02 17:53:16 my systemd[1]: Stopped target Local File Systems (Pre).
Aug 02 17:53:16 my systemd[1]: Stopped Create Static Device Nodes in /dev.
Aug 02 17:53:16 my systemd[1]: Stopped Create System Users.
Aug 02 17:53:16 my systemd[1]: Stopped Remount Root and Kernel File Systems.
Aug 02 17:53:16 my systemd[1]: Reached target Shutdown.
Aug 02 17:53:16 my systemd[1]: Reached target Final Step.
Aug 02 17:53:16 my systemd[1]: Starting Reboot...
Aug 02 17:53:16 my systemd[1]: Shutting down.
Aug 02 17:53:16 my systemd[1]: Hardware watchdog 'iTCO_wdt', version 0
Aug 02 17:53:16 my systemd[1]: Set hardware watchdog to 10min.
Aug 02 17:53:16 my kernel: watchdog: watchdog0: watchdog did not stop!
Aug 02 17:53:16 my kernel: systemd-shutdow: 24 output lines suppressed due to ratelimiting
Aug 02 17:53:16 my systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Aug 02 17:53:16 my systemd-journald[180]: Journal stopped

---

KDE is all good bloated, try to trim away from K*.apps... whatever it leaves behind equals "Kuck yourself!"
nVidia.... fsck sdy0

seth

Member

Registered: 2012-09-03

Posts: 58,807

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

Handing down the thanks to loqs (because I would not have been aware of the bug without him) who will have to hand it down to the Chris Meyer who probably figured that by taking a sharp look at his kernel parameters ;-)

If at all, there will be an error in the kernel messages.

---

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

jackpot

Member

From: Riyadh, Saudi Arabia

Registered: 2014-08-18

Posts: 86

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

Thanks but, dmesg and journald log above, had nothing for my eyes. Just curious to learn (again if there is a better way to read kernel messages than dmesg)!

---

KDE is all good bloated, try to trim away from K*.apps... whatever it leaves behind equals "Kuck yourself!"
nVidia.... fsck sdy0

loqs

Member

Registered: 2014-03-06

Posts: 18,055

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

Should note in addition to what I posted here this appears to be an upstream issue.
Using linux-stable 4.12.4 scsi_mod.use_blk_mq=0 elevator=bfq prevents boot,   scsi_mod.use_blk_mq=0 elevator=foobar boots with dmesg error 'I/O scheduler foobar not found'
Edit:
scsi_mod.use_blk_mq=0 elevator=kyber causes a kernel oops and prevents boot

Last edited by loqs (2017-08-03 19:04:35)

seth

Member

Registered: 2012-09-03

Posts: 58,807

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

The ringbuffer from the former boot? Not sure whether that's actually possible - notably in this case, because you'll have trouble with the disk, ie. storage.
You could forward the journal to the console and see whether that gets you immediate output. Not booting quiet or even booting debug might get you an error message about the elevator.

---

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

loqs

Member

Registered: 2014-03-06

Posts: 18,055

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

@seth can you reproduce the issue?
Using General_troubleshooting#Recovery_shells
rescue,emergency,rd.rescue just end in a hang, init=/bin/sh can not find bin/sh rd.emergency does not provide a shell possibly an issue with using the systemd hook under systemd 224.
edit:
rd.emergency not red.emergency

Last edited by loqs (2017-08-03 19:24:36)

seth

Member

Registered: 2012-09-03

Posts: 58,807

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

$ uptime 
<time> up 20 days, 11:49,  3 users,  load average: 0,20, 0,16, 0,34

... later ;-)
Just the rescue shells init replacement or alongside the broken elevator?

---

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

loqs

Member

Registered: 2014-03-06

Posts: 18,055

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

The lack of rescue shell appears an independent issue, removal of the elevator and scsi_mod options does not produce a functioning shell.

$ bsdcpio -it  < /boot/initramfs-linux.img | grep /usr/bin/sh
56423 blocks

Edit:

# pacman -U /var/cache/pacman/pkg/systemd-233.75-3-x86_64.pkg.tar.xz /var/cache/pacman/pkg/libsystemd-233.75-3-x86_64.pkg.tar.xz /var/cache/pacman/pkg/systemd-sysvcompat-233.75-3-x86_64.pkg.tar.xz

Now the systemd targets produce a rescue shell.

Last edited by loqs (2017-08-03 20:01:46)

seth

Member

Registered: 2012-09-03

Posts: 58,807

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

Got a rescue shell and /init/sh w/ 233 as well, now going for an update (and expecting a failure)

---

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

seth

Member

Registered: 2012-09-03

Posts: 58,807

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

234.11-4 works, but this is a 32bit installation (yeah I know - I'm too lazy ;-)
Both versions trigger mkinitcpio

Try (notice the absent leading slash)

$ bsdcpio -it  < /boot/initramfs-linux.img | grep usr/bin/sh

---

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

loqs

Member

Registered: 2014-03-06

Posts: 18,055

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

$ bsdcpio -it  < /boot/initramfs-linux.img | grep usr/bin/shusr/bin/shuf
usr/bin/sha512sum
usr/bin/sha256sum
usr/bin/sha1sum
usr/bin/sh

So that is not the issue.

seth

Member

Registered: 2012-09-03

Posts: 58,807

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

Not sure whether that's relevant, but I did fix the LC_* vars in /etc/profile.d, root uses zsh here and I actually only tried rescue and not emergency (because you suggested they all act the same) - I guess I'll better try an actual busybox as well?

(because your rescue will have struggled with the bad elevator - just as /bin/sh)

---

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

loqs

Member

Registered: 2014-03-06

Posts: 18,055

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

Back to systemd 234 rd.ermegency and rd.rescue no shell , emergency and rescue give a shell ,
init=/bin/sh (I suspect I was using initrd= in the previous test) gives a shell seems to be after running the systemd hook and at the point it would switch root.
Apologies for all the bad information.
Edit:
Think I have found the reason rd.emergency and rd.rescue do not work with 234
https://github.com/systemd/systemd/comm … a8908460c8

$ bsdcpio -it  < /boot/initramfs-linux.img | grep shell
57076 blocks

So no usr/lib/systemd/systemd-sulogin-shell
Does that seem plausible?  Starting to doubt myself after all these mistakes.

Last edited by loqs (2017-08-04 23:08:51)

seth

Member

Registered: 2012-09-03

Posts: 58,807

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

The binaries are on the disk and this doesn't look related to the busybox shell.
rd.emergency and rd.rescue are simply ignored here, emergency and rescue set the targets and work as expected.
busybox is in initramfs-linux.img - I'm gonna "damage" my root device on the next reboot to see whether I can get into a busybox if there's no installed system to use - off to the basement for a HUGE hammer ;-)

---

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

loqs

Member

Registered: 2014-03-06

Posts: 18,055

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

https://bugs.archlinux.org/task/55042 for rd.emergency and rd.rescue failing under systemd 234 if the systemd hook is used.
Back to the elevator issue:
mq elevators = mq-deadline kyber bfq none
none mq elevators = cfq deadline noop (bfq in the case of linux-zen)
setting the elevator to any one of the mq elevators name when mq is not in use (scsi_mod.use_blk_mq=0) triggers the issue.
setting the elevator to any value when mq is in use (scsi_mod.use_blk_mq=1) will have no effect.
Intentional behavior or bug I have no idea.
Even if I set up a virtual machine to try and catch the kernel output I am not sure I want to pursue it upstream.

seth

Member

Registered: 2012-09-03

Posts: 58,807

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

Ok, sorry - I somehow missed that you're not on busybox but systemd (busybox still works w/ a broken root device and since the systemd introduction i'm keeping grml with me anyway ;-)

The part where you can pass anything as elevator w/o effect because you're using the multiqueue is fine, seems intended. Could yell a warning redirecting to udev or so but doesn't really matter.
bfq collision is sth. linux-zen needs to resolve (renaming the non-mq scheduler or triggering mq) - bfq is an official mq scheduler (now)

for the rest: could be intended (so you don't accidentally change only one value) but if it's not handled gracefully (did you get a warning on non-quiet boots?) that sounds more like a bug (blindly trying to use the scheduler)
Nobody *wants* to report possible bugs to lkml - you feel the duty and take one for the team ;-)

---

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

loqs

Member

Registered: 2014-03-06

Posts: 18,055

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

Think the issue is the logic in this area http://elixir.free-electrons.com/linux/ … tor.c#L216

seth

Member

Registered: 2012-09-03

Posts: 58,807

Re: [Solved] Stuck at 'starting version 234' after upgrade to Kernel 4.12

Use the default elevator specified by config boot param for non-mq devices, or by config option.

Only non-mq elevators are valid kernel parameters

This is suboptimal.
Since the elevator isn't attempted in that branch, an mq elevator will just be used (if passed as parameter) even for non-mq devices, causing (probably uncaught) errors.

This is
a) an uncaught input error (eg. if the user tries to configure the mq elevator this way)
b) a source for ambiguity/name conflicts (zen/bfq, in this case)

=> bug in input handling.
The (only) valid values for "elevator" are covered in the parameter doc, but invalid ones are let through. That's a bug. Period. ;-)

Zen needs to rename the scheduler to sq-bfq or something regardless, though - or the mq bfq to mq-bfq (for backwards compatibility, but bears more maintainance costs)

---

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