[SOLVED]Kernel 4.14 freezes during boot

momu · 2018-02-03 08:40:41

I upgraded yesterday from 4.9 to 4.14 and now Arch Linux freezes during boot.

Here is some basic info about laptop:

System:    Host: leviathan Kernel: 4.9.78-1-lts x86_64 bits: 64
           Desktop: i3 4.14.1 Distro: Arch Linux
Machine:   Device: laptop System: ASUSTeK product: E502MA v: 1.0 serial: N/A
           Mobo: ASUSTeK model: E502MA v: 1.0 serial: N/A
           UEFI [Legacy]: American Megatrends v: E502MA.206 date: 07/30/2015
Battery    BAT0: charge: 17.8 Wh 69.0% condition: 25.8/32.2 Wh (80%)
CPU:       Quad core Intel Celeron N2940 (-MCP-) speed/max: 637/2249 MHz
Graphics:  Card: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display
           Display Server: x11 (X.Org 1.19.6 ) driver: intel
           Resolution: 1366x768@60.00hz
           OpenGL: renderer: Mesa DRI Intel Bay Trail version: 4.2 Mesa 17.3.3
Network:   Card-1: Realtek RTL8723BE PCIe Wireless Network Adapter
           driver: rtl8723be
           Card-2: Realtek RTL8101/2/6E PCIE Fast/Gigabit Ethernet controller
           driver: r8169
Drives:    HDD Total Size: 500.1GB (48.5% used)
Info:      Processes: 139 Uptime: 2 min Memory: 607.0/3835.4MB
           Client: Shell (bash) inxi: 2.3.56

I downgraded from 4.14 to 4.9, but I want to fix this and use 4.14.
Before downgrading, when I booted into live cd, mounted partitions and chrooted, I tried to start Xorg but, when I did screen froze again, just like during boot, so maybe the problem is with graphics (I use plymouth).

I had to use Arch Linux ISO from May 2017, because it's the latest ISO that doesn't freeze at "Triggering uevents"

.If more info is needed, just ask and I'll post it here.

Last edited by momu (2018-02-10 21:53:15)

loqs · 2018-02-03 08:49:33

Post the journal log from a boot with the issue. Try booting with plymouth disabled and any display manager or auto launching graphical session disabled without the boot parameter quiet.

momu · 2018-02-03 10:32:39

loqs wrote:

Post the journal log from a boot with the issue. Try booting with plymouth disabled and any display manager or auto launching graphical session disabled without the boot parameter quiet.

This is what I tried:
1. Disable plymouth
2. Disable display manager
3. Set loglevel=7, remove quiet and splash parameters and rebuild grub.cfg
4. Verify that no graphical software starts at boot with kernel 4.9
5. Upgrade to 4.14
6. Reboot

And it freezes again. So I can't post journal.
But I did see that where it freezes. It freezes when it loads saved information about backlight:

Starting Load/Save Screen Backlight Brightness of backlight:intel_backlight
Starting Load/Save Screen Backlight Brightness of backlight:acpi_video0

First time it froze at second acpi_video0, but second time (after I modified kernel parameters to contain only "loglevel=7") at intel_backlight.

Last edited by momu (2018-02-03 10:34:13)

seth · 2018-02-03 11:06:13

Tried to disable the systemd-backlight service(s) then?

loqs · 2018-02-03 11:15:09

Under 4.9 there is nothing in the journal from the previous boot attempts under 4.14?

momu · 2018-02-03 11:33:29

seth wrote:

Tried to disable the systemd-backlight service(s) then?

I just tried that, but it doesn't help much. Now boot screen shows just a few messages more, the last one being "Started Load/Save Screen Backlight Brightness of backlight:acpi_video0".

But I also tried to remove all boot parameters leaving only "loglevel=7" and it shows lines "Starting Load/Save Screen Backlight...", but it doesn't show "Started Load/Save Screen Backlight...", and it freezes at "Activating swap...".

Edit: Actually, I think I disabled the wrong systemd unit. Can you (or someone else) specify what unit(s) should I disable?

Last edited by momu (2018-02-03 11:43:17)

momu · 2018-02-03 12:26:25

loqs wrote:

Under 4.9 there is nothing in the journal from the previous boot attempts under 4.14?

Yes, but how can I post it? It's too big.

Last edited by momu (2018-02-03 12:29:31)

loqs · 2018-02-03 12:46:32

List_of_applications#Pastebin_clients see the tip box. Also please only paste the log from one boot and do not use the -x option.

seth · 2018-02-03 12:50:18

No, it's still enabled and actually that's the service name, but it's @device

systemctl list-unit-files --state=enabled

momu · 2018-02-03 13:00:40

loqs wrote:

List_of_applications#Pastebin_clients see the tip box. Also please only paste the log from one boot and do not use the -x option.

This is the latest boot with 4.14: here.

momu · 2018-02-03 13:03:35

seth wrote:

No, it's still enabled and actually that's the service name, but it's @device
systemctl list-unit-files --state=enabled

UNIT FILE                STATE  
acpid.service            enabled
autovt@.service          enabled
bluetooth.service        enabled
cronie.service           enabled
dbus-org.bluez.service   enabled
dhcpcd.service           enabled
display-manager.service  enabled
getty@.service           enabled
lightdm-plymouth.service enabled
lm_sensors.service       enabled
sshd.service             enabled
tlp-sleep.service        enabled
tlp.service              enabled
remote-fs.target         enabled

14 unit files listed.

Which one should I disable? Maybe acpid?

R00KIE · 2018-02-03 13:36:04

Are you using early or late modesetting? You could try to switch and see if it helps. Given that for now the problem seems to be connected to graphics, another thing you could try is adding nomodeset to the kernel line, mind you that without modesetting you will not be able to start a graphical environment.

momu · 2018-02-03 14:16:58

R00KIE wrote:

Are you using early or late modesetting? You could try to switch and see if it helps. Given that for now the problem seems to be connected to graphics, another thing you could try is adding nomodeset to the kernel line, mind you that without modesetting you will not be able to start a graphical environment.

Early modesetting. I already tried nomodeset without success.

Maybe it will help if I post my kernel parameters:

GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=0 i915.modeset=1 rd.udev.log-priority=0 modprobe.blacklist=iTCO_wdt rd.systemd.show_status=no vt.global_cursor_default=0 splash pcie_aspm=force acpi_osi="

Last edited by momu (2018-02-03 14:18:03)

seth · 2018-02-03 14:27:33

Seems the backlight service is pulled indirectly.

For the beginning just disable:
acpid.service, lightdm-plymouth.service, lm_sensors.service, tlp-sleep.service and tlp.service

quiet loglevel=0 ... splash

?

pcie_aspm=force acpi_osi=

Why are those there?

i915.modeset=1

That's superfluous, modesetting is on by default.

momu · 2018-02-03 15:28:23

seth wrote:

Seems the backlight service is pulled indirectly.
For the beginning just disable:
acpid.service, lightdm-plymouth.service, lm_sensors.service, tlp-sleep.service and tlp.service

I disabled them, but 4.14 still freezes. log

seth wrote:

quiet loglevel=0 ... splash
?

Plymouth used to be buggy if quiet and splash are side by side. But not anymore (checked right now).

seth wrote:

pcie_aspm=force acpi_osi=
Why are those there?

link

Last edited by momu (2018-02-03 15:31:31)

seth · 2018-02-03 16:19:25

For "quiet loglevel=0 ... splash" I meant: that's not exactly get you more debug output.

On the matter: you added "pcie_aspm=force acpi_osi=" because "Brightness function keys not working" and now apparently stall at "Starting Load/Save Screen Backlight Brightness of backlight:acpi_video0"
Does this not raise your suspicion??

momu · 2018-02-03 16:43:19

seth wrote:

For "quiet loglevel=0 ... splash" I meant: that's not exactly get you more debug output.
On the matter: you added "pcie_aspm=force acpi_osi=" because "Brightness function keys not working" and now apparently stall at "Starting Load/Save Screen Backlight Brightness of backlight:acpi_video0"
Does this not raise your suspicion??

When I need more output, I change it loglevel=7 via GRUB when booting.

I already tried removing "pcie_aspm=force acpi_osi=". No effect.

momu · 2018-02-03 17:14:07

I tried

systemctl mask systemd-backlight\@.service

and loading asus-nb-wmi. Unfortunately, that does not work either. log

seth · 2018-02-03 17:38:00

From your logs it seems the network starts, also the log is synced to disk and you get a clean reboot, iow: nothing "freezes".
It'll be more likely that you just fail to reach the graphical target - try to ping the system (and/or ssh into it)
Keep TLP disabled and pass "i915.enable_rc6=0 i915.enable_psr=0 i915.enable_fbc=0" to the kernel parameters.

I'm not sure though whether the above could also be a despite w/ "nomodeset".

momu · 2018-02-03 18:38:31

seth wrote:

From your logs it seems the network starts, also the log is synced to disk and you get a clean reboot, iow: nothing "freezes".
It'll be more likely that you just fail to reach the graphical target - try to ping the system (and/or ssh into it)
Keep TLP disabled and pass "i915.enable_rc6=0 i915.enable_psr=0 i915.enable_fbc=0" to the kernel parameters.
I'm not sure though whether the above could also be a despite w/ "nomodeset".

I don't know why. I always post the latest boot with 4.14, and it's definitely not a clean reboot. I have to turn off the laptop by holding down power button for a few seconds.

I added those kernel parameters, but nothing changed. I also tried to ssh via hostname but another PC couldn't find this one. So I tried to get the IP address of this PC via Nmap (since this and that PC are on the same network) but no luck. Nmap was stalled, until I turned off the laptop.

log

Last edited by momu (2018-02-03 18:39:13)

R00KIE · 2018-02-03 23:39:56

I would remove all kernel options you have added, forget about having the brightness keys working for now. Like seth says disable tlp or laptop mode tools or whatever other power saving daemons or tweaks you may have done.

If say you are using early modesetting, try using late modesetting, if that doesn't work try only with nomodeset, also try blacklisting i915 completely (don't forget to regenerate the initramfs), that should take the gpu driver completely out of the equation.

Try booting with the install media and see if it hangs, if it doesn't there is a good chance that it is some configuration you have changed that is causing trouble.

Make sure you are not trying to start any DE or WM, you don't want anything to be trying to fiddle with system settings.

momu · 2018-02-04 07:14:09

R00KIE wrote:

If say you are using early modesetting, try using late modesetting, if that doesn't work try only with nomodeset, also try blacklisting i915 completely (don't forget to regenerate the initramfs), that should take the gpu driver completely out of the equation.

What do you mean by "blacklisting"? This?

Last edited by momu (2018-02-04 07:14:38)

R00KIE · 2018-02-04 11:39:30

momu wrote:

What do you mean by "blacklisting"? This?

Yes, that's what I had in mind.

seth · 2018-02-04 14:17:10

I'm not sure this is IGP related, see

Nmap was stalled, until I turned off the laptop.

So the system establishes a network connection and registers with the LAN but then afterwards the kernel halts.
Due to the claim this also happens w/ the multi-user.target it would be sth. before that and after the network target.
I doubt it's sshd, but remote-fs sounds suspicious enough...

momu · 2018-02-04 19:42:49

seth wrote:

I'm not sure this is IGP related, see
Nmap was stalled, until I turned off the laptop.
So the system establishes a network connection and registers with the LAN but then afterwards the kernel halts.
Due to the claim this also happens w/ the multi-user.target it would be sth. before that and after the network target.
I doubt it's sshd, but remote-fs sounds suspicious enough...

I disabled both sshd.service and remote-fs.target, but it makes no difference. There is no log for 4.14 this time (there is for boot before it, and boot after it, but not for that boot... ???). Also, will it be ok to disable everything that is enable and try 4.14 then?

I'll now try what R00KIE suggested.

Edit:There was no log because remote-fs was disabled.

Last edited by momu (2018-02-04 21:17:45)

Arch Linux

#1 2018-02-03 08:40:41

[SOLVED]Kernel 4.14 freezes during boot

#2 2018-02-03 08:49:33

Re: [SOLVED]Kernel 4.14 freezes during boot

#3 2018-02-03 10:32:39

Re: [SOLVED]Kernel 4.14 freezes during boot

#4 2018-02-03 11:06:13

Re: [SOLVED]Kernel 4.14 freezes during boot

#5 2018-02-03 11:15:09

Re: [SOLVED]Kernel 4.14 freezes during boot

#6 2018-02-03 11:33:29

Re: [SOLVED]Kernel 4.14 freezes during boot

#7 2018-02-03 12:26:25

Re: [SOLVED]Kernel 4.14 freezes during boot

#8 2018-02-03 12:46:32

Re: [SOLVED]Kernel 4.14 freezes during boot

#9 2018-02-03 12:50:18

Re: [SOLVED]Kernel 4.14 freezes during boot

#10 2018-02-03 13:00:40

Re: [SOLVED]Kernel 4.14 freezes during boot

#11 2018-02-03 13:03:35

Re: [SOLVED]Kernel 4.14 freezes during boot

#12 2018-02-03 13:36:04

Re: [SOLVED]Kernel 4.14 freezes during boot

#13 2018-02-03 14:16:58

Re: [SOLVED]Kernel 4.14 freezes during boot

#14 2018-02-03 14:27:33

Re: [SOLVED]Kernel 4.14 freezes during boot

#15 2018-02-03 15:28:23

Re: [SOLVED]Kernel 4.14 freezes during boot

#16 2018-02-03 16:19:25

Re: [SOLVED]Kernel 4.14 freezes during boot

#17 2018-02-03 16:43:19

Re: [SOLVED]Kernel 4.14 freezes during boot

#18 2018-02-03 17:14:07

Re: [SOLVED]Kernel 4.14 freezes during boot

#19 2018-02-03 17:38:00

Re: [SOLVED]Kernel 4.14 freezes during boot

#20 2018-02-03 18:38:31

Re: [SOLVED]Kernel 4.14 freezes during boot

#21 2018-02-03 23:39:56

Re: [SOLVED]Kernel 4.14 freezes during boot

#22 2018-02-04 07:14:09

Re: [SOLVED]Kernel 4.14 freezes during boot

#23 2018-02-04 11:39:30

Re: [SOLVED]Kernel 4.14 freezes during boot

#24 2018-02-04 14:17:10

Re: [SOLVED]Kernel 4.14 freezes during boot

#25 2018-02-04 19:42:49

Re: [SOLVED]Kernel 4.14 freezes during boot

Board footer