[SOLVED] Can't reboot or shutdown when using 4.19 kernel or 4.20

I just installed Manjaro i3 edition on my brand new laptop (a Dell Latitude 5591). The big issue is that when I’m running the 4.19 or 4.20 kernel I can’t reboot or shutdown or even exit i3. As soon as I try any of those the whole computer locks up! In the end I have to forcefully shutdown the computer by holding the power button.

The 4.14 kernel seems to be working fine but I get a bunch of ACPI errors everytime I boot up.

Any idea what it could be?

The newer kernels are obviously incompatible with your computer ATM. Simply use 4.14 for now. ACPI errors are usually inconsequential. Test the new kernels every month or so for improvements.

1 Like

Would this issue be similar to mine?
I have a Dell as well.

I have no troubles with booting up. The problem is exiting i3, rebooting or shuting down.

I am able to boot but can’t shut down or reboot either.
And this only with kernel 4.19 and 4.20, 4.14 runs fine.

That is actually bad advice as the issue gets more difficult to locate the longer you wait.

Did you by chance check kernels 4.15 - 4.18 while they still were in the repository if they show the same behaviour? It would be a lot easier to locate the issue with knowing which kernel exactly introduced that behaviour. 4.18rt could be used for that purpose
@sillen102 Please post your output of inxi -Fxxx, too

Sure, if you bisect the new kernel you could possibly track down the cause, but how many commits have there been between 4.14 and 4.19/20.

This is not something the average user asking this type of question is going to do. The average user in this situation is probably best to do as I advised.

A difference of opinion here, not bad advice to my way of thinking is all.

Bisecting kernel 4.14-4.15 changes is one thing, but there have been 6 kernel updates since 4.14. It is probably more than the average user could do to track down the cause at this late stage of kernel updates. So… what is your alternative?

1 Like

I think we would start by checking the logs from the previous boot (one where the reboot/shutdown did not work and had to be forced off).

So a good first step would be to look at
journalctl -b-1 -p3
Or if that does not reveal anything the lines near the bottom of a full journalctl -b-1.
Maybe more would be needed dmesg or providing inxi -Fxz to see if perhaps it is a hardware issue.

Basically troubleshooting the issue. (A good thread for those unfamiliar with troubleshooting on Manjaro: How to provide good information in your posts .) If a user having the problem does not do it, who will? :wink:

And as forum busybody’s there is certainly no harm in suggesting this, even if for one of various reasons, it may all come to nothing. But there is a chance that such an investigation might throw up a clue that someone on the forum, or an internet search, knows something about. :rainbow:

2 Likes

That’s almost insulting. Unless you have a proposition for a possible solution please don’t respond. I’ve been running Linux for over 10 years and even compiled my own kernels a few years ago so to just say “not compatible” is both insulting and actually stupid (sorry for the harsh language).

No I just installed the i3 edition clean yesterday on my new laptop.

Output from inxi -Fxxx:

           v: 8.2.1 Desktop: i3 4.16 info: i3bar dm: LightDM 1.28.0 Distro: Manjaro Linux 
Machine:   Type: Laptop System: Dell product: Latitude 5591 v: N/A serial: <root required> 
           Chassis: type: 10 serial: <root required> 
           Mobo: Dell model: 0DVVG1 v: A00 serial: <root required> UEFI: Dell v: 1.5.1 
           date: 12/04/2018 
Battery:   ID-1: BAT0 charge: 61.2 Wh condition: 61.2/68.0 Wh (90%) volts: 8.7/7.6 
           model: SMP DELL GD1JP65 type: Li-poly serial: 234 status: Full 
CPU:       Topology: 6-Core model: Intel Core i7-8850H bits: 64 type: MT MCP arch: Kaby Lake 
           rev: A L2 cache: 9216 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 62232 
           Speed: 1000 MHz min/max: 800/4300 MHz Core speeds (MHz): 1: 1001 2: 1000 3: 1000 
           4: 1000 5: 1000 6: 1000 7: 1000 8: 1000 9: 1000 10: 1000 11: 1000 12: 1000 
Graphics:  Device-1: Intel UHD Graphics 630 vendor: Dell driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:3e9b 
           Device-2: NVIDIA GM108M [GeForce MX130] driver: nouveau v: kernel bus ID: 01:00.0 
           chip ID: 10de:174d 
           Display: x11 server: X.Org 1.20.3 driver: intel,nouveau unloaded: modesetting 
           alternate: fbdev,nv,vesa compositor: compton resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel UHD Graphics 630 (Coffeelake 3x8 GT2) 
           v: 4.5 Mesa 18.3.2 compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel Cannon Lake PCH cAVS vendor: Dell driver: snd_hda_intel v: kernel 
           bus ID: 00:1f.3 chip ID: 8086:a348 
           Sound Server: ALSA v: k4.19.20-1-MANJARO 
Network:   Device-1: Intel Wireless-AC 9560 [Jefferson Peak] driver: iwlwifi v: kernel 
           port: 4000 bus ID: 00:14.3 chip ID: 8086:a370 
           IF: wlo1 state: up mac: 18:56:80:e1:3c:be 
           Device-2: Intel Ethernet I219-LM vendor: Dell driver: e1000e v: 3.2.6-k port: efa0 
           bus ID: 00:1f.6 chip ID: 8086:15bb 
           IF: eno2 state: down mac: c8:f7:50:01:5b:17 
Drives:    Local Storage: total: 476.94 GiB used: 14.93 GiB (3.1%) 
           ID-1: /dev/sda vendor: Micron model: 1100 SATA 512GB size: 476.94 GiB 
           speed: 6.0 Gb/s serial: 18431EF93F53 rev: L022 scheme: GPT 
RAID:      Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 
           port: 4060 bus ID: 00:17.0 chip ID: 8086.282a rev: 10 
Partition: ID-1: / size: 273.23 GiB used: 14.88 GiB (5.4%) fs: ext4 dev: /dev/sda5 
Sensors:   System Temperatures: cpu: 42.0 C mobo: N/A 
           Fan Speeds (RPM): cpu: 0 
Info:      Processes: 294 Uptime: 2m Memory: 15.46 GiB used: 1.21 GiB (7.8%) Init: systemd 
           v: 239 target: graphical.target Compilers: gcc: 8.2.1 Shell: bash v: 5.0.0 
           running in: urxvtd inxi: 3.0.30
type or paste code here

Output from journalctl -b-1 -p3:

-- Logs begin at Mon 2019-02-18 15:36:51 CET, end at Tue 2019-02-19 09:16:00 CET. --
feb 19 09:06:41 silvio-work-pc kernel: iTCO_wdt iTCO_wdt: can't request region for resource [mem 0x00c5fffc-0x00c5ffff]
feb 19 09:06:41 silvio-work-pc kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ IBUS ]
feb 19 09:06:41 silvio-work-pc kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 10ac08 [ IBUS ]
feb 19 09:06:42 silvio-work-pc kernel: iwlwifi 0000:00:14.3: BIOS contains WGDS but no WRDS
feb 19 09:06:42 silvio-work-pc kernel: nouveau 0000:01:00.0: DRM: Pointer to TMDS table invalid
feb 19 09:06:42 silvio-work-pc kernel: iwlwifi 0000:00:14.3: BIOS contains WGDS but no WRDS
feb 19 09:06:44 silvio-work-pc kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ IBUS ]
feb 19 09:06:48 silvio-work-pc nmbd[807]: [2019/02/19 09:06:48.316014,  0] ../lib/util/become_daemon.c:149(daemon_status)
feb 19 09:06:48 silvio-work-pc nmbd[807]: daemon_status: STATUS=daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...
feb 19 09:06:48 silvio-work-pc nmbd[807]: [2019/02/19 09:06:48.316262,  0] ../source3/nmbd/nmbd_subnetdb.c:254(create_subnets)
feb 19 09:06:48 silvio-work-pc nmbd[807]: NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
feb 19 09:06:54 silvio-work-pc sudo[868]: pam_unix(sudo:auth): conversation failed
feb 19 09:06:54 silvio-work-pc sudo[868]: pam_unix(sudo:auth): auth could not identify password for [silvio]
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:56 silvio-work-pc bluetoothd[563]: bt_uhid_send: Invalid argument (22)
feb 19 09:06:58 silvio-work-pc nmbd[807]: [2019/02/19 09:06:58.317417,  0] ../lib/util/become_daemon.c:138(daemon_ready)
feb 19 09:06:58 silvio-work-pc nmbd[807]: daemon_ready: STATUS=daemon 'nmbd' finished starting up and ready to serve connections
feb 19 09:06:58 silvio-work-pc smbd[1121]: [2019/02/19 09:06:58.403462,  0] ../lib/util/become_daemon.c:138(daemon_ready)
feb 19 09:06:58 silvio-work-pc smbd[1121]: daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
feb 19 09:06:58 silvio-work-pc kernel: acpi_call: Cannot get handle: Error: AE_NOT_FOUND
feb 19 09:06:58 silvio-work-pc kernel: acpi_call: Cannot get handle: Error: AE_NOT_FOUND
feb 19 09:08:47 silvio-work-pc kernel: nouveau 0000:01:00.0: fifo: runlist 0 update timeout
feb 19 09:08:49 silvio-work-pc kernel: nouveau 0000:01:00.0: fifo: runlist 4 update timeout
feb 19 09:09:10 silvio-work-pc kernel: nouveau 0000:01:00.0: DRM: failed to idle channel 0 [DRM]
feb 19 09:14:24 silvio-work-pc kernel: nouveau 0000:01:00.0: DRM: failed to idle channel 0 [DRM]
feb 19 09:14:27 silvio-work-pc nmbd[807]: [2019/02/19 09:14:27.126170,  0] ../source3/nmbd/nmbd.c:58(terminate)
feb 19 09:14:27 silvio-work-pc nmbd[807]: Got SIGTERM: going down...
feb 19 09:14:27 silvio-work-pc nmbd[807]: [2019/02/19 09:14:27.126214,  0] ../source3/libsmb/nmblib.c:909(send_udp)
feb 19 09:14:27 silvio-work-pc nmbd[807]: Packet send failed to 10.10.9.255(138) ERRNO=Ogiltigt argument
feb 19 09:14:41 silvio-work-pc kernel: nouveau 0000:01:00.0: Xorg[614]: failed to idle channel 3 [Xorg[614]]
feb 19 09:14:42 silvio-work-pc systemd[1]: Failed unmounting /tmp.

I just tried to do a reboot from another TTY and what I get when running 4.19 compared to 4.14 is that Light DM doesn’t shut down properly apart from not being able to unmount /tmp. I get the “A stop job is running for Light DM” thing. I’ve set the timeout for stop jobs to 5s (from the 90s) that is by default so I can reboot now from a TTY it just takes a long time.

I have also tried removing the nouveau driver.

I tried disabling LightDM and starting X manually. Then I get “A stop job is running” for pretty much everything.

Just installed bumblebee together with NVIDIA drivers and this seems to have resolved the issue.

These are the packages I installed:

bumblebee
lib32-primus
primus
linux419-nvidia-390xx
linux419-bbswitch

and some other dependencies that are needed to install those above.

And I also removed the nouveau driver (xf86-video-nouveau)

The average new Manjaro user who has been registered on the forum only a brief amount of time does not have 10 years of Linux experience. It’s great you do, but most new users on the forum have little (or no) Linux experience and most are fresh off the Windows boat.

For those users my advice is perfectly applicable, as they are not going to start bisecting kernels. You may be a more advanced user, but that was not immediately apparent from your earlier posts. Your initial post did not make it appear that that you were an experienced user as you stated you just just installed Manjaro and provided zero system information. A user that is more advanced generally posts their specs or logs right off the hop, (not after a dozen posts in the thread).

I use kernel 4.14 as my daily driver and there is absolutely nothing wrong with that, as it is an LTS kernel that is supported for quite some time yet. If 4.14 runs fine on your system there is little need for you to be on the latest kernel. I could see this being a major issue if the only kernel that your computer ran on was an end of life kernel such as 4.18. Then debugging your computers problem with the newest kernels would be of major importance.

Generally major incompatibilities with mainstream hardware is resolved fairly quickly when there is a kernel breakage. For example I use a Realtek wifi adapter that broke on kernel 4.15 for a month or so. It is currently broken again on kernel 4.20. Neither breakage was a major concern, because I expected it to be rectified before too long. The important thing is to have an LTS kernel that your system runs well on (and you do).

If you are such an experienced Linux user start showing it. Put on your big boy boots and start posting some logs, (as requested) that might actually be useful. Instead of putting down forum helpers that respond to your thread with nothing but good intentions, start helping yourself.

Unless my response is off topic you really have no business telling me not to respond to your thread, and putting down my advice. If you looked at my number of solves on the forum in the last year you’d probably realize that my advice is usually pretty good. IMO your response to me was a very poor way to introduce yourself as a new member who is expecting help on the forum.

Good luck getting your issue resolved.

2 Likes

Well, to be honest I haven’t run into a whole lot of issues using Linux and most of the ones I’ve had I’ve been able to resolve without ever posting a question. So I appoligise for my inexperience with posting questions on forums.

And I am by no means a new user on the Manjaro forum. I’ve been a member on this forum for at least 3 years now.

And if you look at my last post before yours I already stated that I managed to solve the problem.

1 Like

My apologies. I thought you were a new user.

I’m glad you have things working better now.

2 Likes

I’m also using linux for 10 years but my problem still exist…
Should I wait since no one responded at my thread.

I managed to resolve it by installing Bumblebee. The easiest way to do it is by using the Manjaro Settings Manager and simply install “video-hybrid-intel-nvidia-bumblebee”. That is if you have a system with both an intel integrated graphics card and a second nvidia graphics card (which at least I do).

2 Likes

Look at my signature. :wink:

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.