Computer reboots when shutdown is issued for kernels 4.9.6-1

ozooha · 2017-01-31 14:20:52

The problem is that the PC reboots when its issued a shutdown from the DE or CLI.
This happens on the zen kernel as well. This issue however doesn't happen on
4.4.45-1-lts.
Below is the link for the journalctl boot when running kernel 4.9.6-1.

http://pastebin.com/QGgnqmmY

Let me know if you require anything else.
Thanks.
OZooHA

seth · 2017-01-31 14:49:04

Issued "how"?
The log indicates a normal reboot.

Does "systemctl poweroff" work as intended (assuming you were using "shutdown")?

ozooha · 2017-01-31 15:25:55

Shutdown from the Gnome interface.
shutdown -P now
and
systemctl poweroff.

They all reboot the computer.

OZooHA

ozooha · 2017-01-31 15:30:43

This is the most recent journalctl log when i issued the systemctl poweroff command.
http://pastebin.com/zVritdxc

I hope this helps.
OZooHA

PS:Just for my own edification can you tell me what you were searching for in the log?

seth · 2017-01-31 19:54:12

I looked for the term "reboot" - which is stunningly absent in your latest log (so it at least doesn't look like an intended reboot)
What if you logout gnome first, or even "systemctl isolate multi-user.target" and "systemctl poweroff" from there?

Jan 31 10:22:40 OZLinux kernel: systemd-shutdow: 44 output lines suppressed due to ratelimiting

*sigh*, journald is such useless crap.
Things end here and it's *after* the supposed poweroff

man journald.conf

but there've been complaints that ratelimit adjustment is ineffective

ozooha · 2017-01-31 23:04:27

Here is the latest log

http://pastebin.com/ws9xa1QB

And your last suggestion did not work meaning after logging out of gnome I issued systemctl poweroff command.

I uncommented the RateLimitIntervalSec=30 in the journald.conf to get the log and I believe it did not work..unless i misunderstood you.

OZooHA

seth · 2017-02-01 08:22:40

Try setting
RateLimitIntervalSec=1s
RateLimitBurst=100000

The "legal" deactivation is to set either value to 0, but apparently that's claimed broken.

IAmAArchEr · 2017-02-01 10:17:19

I'm facing the same problem too. And Yes! The LTS kernel is working for me as well. No reboot problem with that. But I noticed that if you start 4.9.6-1 kernel with "nomodeset" kernel parameter it normally shuts down but the graphics perfomance will be horrible

Last edited by IAmAArchEr (2017-02-01 10:18:08)

seth · 2017-02-01 13:03:59

"lspci"?
Nomodeset will kill X11 (but for the nvidia driver)

ozooha · 2017-02-01 18:22:02

Seth I will try your values when I get home.
Is my issue somehow related to this? - see comment #9 by me in the link below.
https://bbs.archlinux.org/viewtopic.php?id=222545
Thanks.
OZooHA

seth · 2017-02-01 19:21:15

The other thread is all about X11, ie. if it's related, "systemctl isolate multi-user.target" should avoid the problem (though there might be a common root in the amdgpu kernel module)

ozooha · 2017-02-02 00:50:44

Here you go seth
http://pastebin.com/7kgmyuF5
I hope this helps.
OZooHA

seth · 2017-02-02 07:54:58

Feb 01 19:40:35 OZLinux kernel: systemd-shutdow: 43 output lines suppressed due to ratelimiting

... "useless crap..."

Did you try stopping the display server (isolating the MU target)?

@IAmAArchEr
AMD GPU as well?

ozooha · 2017-02-02 15:37:47

seth wrote:

Feb 01 19:40:35 OZLinux kernel: systemd-shutdow: 43 output lines suppressed due to ratelimiting
... "useless crap..."
Did you try stopping the display server (isolating the MU target)?
@IAmAArchEr
AMD GPU as well?

Could you expand on this -

Did you try stopping the display server (isolating the MU target)?

What is that you want me to try?
Sorry for being dense.
OZooHA

seth · 2017-02-02 15:41:21

issue

sudo systemctl isolate multi-user.target

BE WARNED that this will exit your graphical login immediately, so ensure to have saved everything and be fine to quit.
You should then face a DOS-a-like login prompt where you can login and then try "systemctl poweroff"

ozooha · 2017-02-03 01:30:55

Here is the latest with your suggestion.
I am afraid it did not work judging from what you were looking for in the log before.
http://pastebin.com/UxFPTzpJ
Let me know eitherways.
OZooHA

seth · 2017-02-03 08:22:19

No, the idea was that unloading the X11 driver (first) would somehow have impact (given https://bbs.archlinux.org/viewtopic.php?id=222545)
What happens for "noacpi"?

ozooha · 2017-02-04 00:40:54

seth wrote:

No, the idea was that unloading the X11 driver (first) would somehow have impact (given https://bbs.archlinux.org/viewtopic.php?id=222545)
What happens for "noacpi"?

Doesn't work: its reboots when asked to shutdown.
I have decided to rollback to 4.8 coz 4.9 is broken unless you want me to try something you have on your mind for the broader good of the Arch Community then sure lemme know.
OZooHA

IAmAArchEr · 2017-02-04 05:53:42

@seth, here is the output of my lspci

lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) I/O Memory Management Unit
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D]
00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Trinity HDMI Audio Controller
00:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Root Port
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 40)
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11)
00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11)
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11)
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11)
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 14)
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 01)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11)
00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] FCH PCI Bridge (rev 40)
00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11)
00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11)
00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 5
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)

I was just saying that I edited the grub & booted with nomodeset & then I was able to shutdown the PC normally. If I'm right then amdgpu graphics will not work if I boot with nomodeset. I've heard that there are several improvements for amdgpu in kernel 4.9.xx but I think there is the graphics issue which are causing these restarts. No reboot problems with the LTS kernel.

@ozooha, I think you're using the AMD graphics with the amdgpu driver as well, isn't it?

@seth, I just wanted to say that it can possibly be the amd graphics(driver) issue. Hope that information will be helpful

ozooha · 2017-02-04 13:59:29

IAmAArchEr wrote:

@ozooha, I think you're using the AMD graphics with the amdgpu driver as well, isn't it?

No I am using radeon.
My specs:
APU: AMD A4-5300 APU 3.4Ghz Processor AD5300OKHJBOX
GPU Type: Radeon HD 7480D
I am using two monitors DVI (1680x1050) and HDMI (1920x1080).

I believe amdgpu might work as well based on this info in the wiki - https://wiki.archlinux.org/index.php/AM … ands_cards
But I haven't tried.
Should I?
Anyone please advice.
OZooHA

seth · 2017-02-05 08:26:35

Neither amdgpu nor radeon will "really" work w/o modesetting, Xorg might work (dead slow) if you've the vesa driver installed.

@ozooha
You might try the results with "nomodeset" to verify IAmAArchEr findings and possible relation to the GPU

ozooha · 2017-02-05 14:38:15

seth wrote:

@ozooha
You might try the results with "nomodeset" to verify IAmAArchEr findings and possible relation to the GPU

Xorg doesn't start up but the PC shuts down fine.
OZooHA

seth · 2017-02-05 14:59:23

Ok, what if we just don't touch it? Instead of nomodeset, pass "systemd.unit=multi-user.target" to the kernel parameters. (X won't start either, but modesetting is enabled in the kernel)

ozooha · 2017-02-05 16:29:24

seth wrote:

Ok, what if we just don't touch it? Instead of nomodeset, pass "systemd.unit=multi-user.target" to the kernel parameters. (X won't start either, but modesetting is enabled in the kernel)

It still doesn't work. It reboots when it should shutdown. The Xorg worked fine though.
OZooHA

IAmAArchEr · 2017-02-06 11:53:00

ozooha wrote:

seth wrote:
@ozooha
You might try the results with "nomodeset" to verify IAmAArchEr findings and possible relation to the GPU
Xorg doesn't start up but the PC shuts down fine.
OZooHA

If xorg is not working then you don't have the .xinitrc file.
sudo pacman -S xorg-xinit
sudo nano ~/.xinitrc
Type : exec gnome-session & save the file
Now "startx" command should start the xorg session on gnome 3 even with nomodeset [Assuming that you are using gome]

Last edited by IAmAArchEr (2017-02-06 11:57:04)

Arch Linux

#1 2017-01-31 14:20:52

Computer reboots when shutdown is issued for kernels 4.9.6-1

#2 2017-01-31 14:49:04

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#3 2017-01-31 15:25:55

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#4 2017-01-31 15:30:43

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#5 2017-01-31 19:54:12

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#6 2017-01-31 23:04:27

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#7 2017-02-01 08:22:40

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#8 2017-02-01 10:17:19

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#9 2017-02-01 13:03:59

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#10 2017-02-01 18:22:02

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#11 2017-02-01 19:21:15

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#12 2017-02-02 00:50:44

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#13 2017-02-02 07:54:58

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#14 2017-02-02 15:37:47

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#15 2017-02-02 15:41:21

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#16 2017-02-03 01:30:55

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#17 2017-02-03 08:22:19

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#18 2017-02-04 00:40:54

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#19 2017-02-04 05:53:42

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#20 2017-02-04 13:59:29

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#21 2017-02-05 08:26:35

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#22 2017-02-05 14:38:15

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#23 2017-02-05 14:59:23

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#24 2017-02-05 16:29:24

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

#25 2017-02-06 11:53:00

Re: Computer reboots when shutdown is issued for kernels 4.9.6-1

Board footer