You are not logged in.

#1 2019-09-29 07:05:36

developerbmw
Member
Registered: 2019-09-29
Posts: 7

Strange Reboot Issue

I'm running Arch on my laptop (Asus N552VW).
Shutdown works fine but reboot doesn't quite work properly.
When I reboot, the system seems to reset (screen turns off, keyboard lights flash, optical drive makes a noise like it usually does when turning PC on) but the screen stays off, and I have to hold the power button down to force it to turn it off.
I'm not sure if it's actually booting and it's just the display that isn't working, or whether the system is hung.

- I discovered that if I suspend/wake the system before rebooting it seems to correct the issue and the reboot works fine for that session.
- I have tried all the different reboot kernel parameters (reboot=...) to no avail.
- Running Arch from the live USB has the same issue, but a Ubuntu 19.04 live USB reboots correctly (without needing to do a suspend first), and I've never had any issues with Windows.
- "Fast boot" is disabled in the BIOS and also in Windows.

Any advice on how I should go about debugging the issue would be much appreciated.

Last edited by developerbmw (2019-09-29 07:06:42)

Offline

#2 2019-09-29 15:08:59

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 16,816

Re: Strange Reboot Issue

When you say "Keyboard lights flash", does that mean one time as the system restarts, or does that mean continuously flashing until you power off?


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#3 2019-09-29 17:54:57

developerbmw
Member
Registered: 2019-09-29
Posts: 7

Re: Strange Reboot Issue

ewaller wrote:

When you say "Keyboard lights flash", does that mean one time as the system restarts, or does that mean continuously flashing until you power off?

Just once.

Offline

#4 2019-09-29 17:56:31

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 16,816

Re: Strange Reboot Issue

Okay, I would consider that to be normal.  My concern was as to whether the kernel was panicing.  It seems not.

Edit:  Anything interesting being logged in the journal?

Last edited by ewaller (2019-09-29 17:57:30)


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#5 2019-09-30 05:49:51

developerbmw
Member
Registered: 2019-09-29
Posts: 7

Re: Strange Reboot Issue

Final few lines in the journal are below. Nothing interesting as far as I can see.

Sep 30 18:44:48 arch systemd[1]: Started Reboot.
Sep 30 18:44:48 arch systemd[1]: Reached target Reboot.
Sep 30 18:44:48 arch systemd[1]: Shutting down.
Sep 30 18:44:48 arch systemd[1]: Hardware watchdog 'iTCO_wdt', version 0
Sep 30 18:44:48 arch systemd[1]: Set hardware watchdog to 10min.
Sep 30 18:44:48 arch kernel: watchdog: watchdog0: watchdog did not stop!
Sep 30 18:44:48 arch kernel: printk: systemd-shutdow: 44 output lines suppressed due to ratelimiting
Sep 30 18:44:48 arch systemd-shutdown[1]: Syncing filesystems and block devices.
Sep 30 18:44:48 arch systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Sep 30 18:44:48 arch systemd-journald[320]: Journal stopped
-- Reboot --

I left the system for around a minute after it hung, and there's no entries in the journal until around the time at which I turned it off and booted properly, which means that it's not just booting without the display working.

Last edited by developerbmw (2019-09-30 05:52:10)

Offline

#6 2019-09-30 07:00:29

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 7,814

Re: Strange Reboot Issue

This reads like it's already outside of the OS and stuck in firmware, do you have a firmware/UEFI/BIOS update available you could apply? (Note on many vendors this will wipe your NVRAM so you might want to have Live stick handy to reinstall bootloader/EFI variables)

Last edited by V1del (2019-09-30 07:01:44)

Offline

#7 2019-09-30 07:23:20

developerbmw
Member
Registered: 2019-09-29
Posts: 7

Re: Strange Reboot Issue

Yeah I'm pretty sure it's rebooting correctly as far as the OS is concerned, but Arch must be doing something different to Ubuntu since Ubuntu works.

I already tried installing the latest BIOS and it didn't change anything.

Offline

#8 2019-10-02 07:48:28

Al.Piotrowicz
Member
Registered: 2017-08-07
Posts: 74

Re: Strange Reboot Issue

I had a similar issue few years ago with the nvidia proprietary driver. Please post a full systemd-journal of the affected boot.

Offline

#9 2019-10-03 06:00:19

developerbmw
Member
Registered: 2019-09-29
Posts: 7

Re: Strange Reboot Issue

Offline

#10 2019-10-04 14:26:18

Al.Piotrowicz
Member
Registered: 2017-08-07
Posts: 74

Re: Strange Reboot Issue

Does the problem persist if you totally disable an Intel integrated GPU in the optimus-manager?

Last edited by Al.Piotrowicz (2019-10-04 14:29:22)

Offline

#11 2019-10-04 20:00:27

developerbmw
Member
Registered: 2019-09-29
Posts: 7

Re: Strange Reboot Issue

I'm not sure if I can 'totally disable' the Intel graphics.

I tried setting the optimus-manager startup mode to Nvidia, then shutdown/booted again so it was running with Nvidia, then rebooted. The problem persists and there doesn't seem to be anything interesting in the journal.

The issue was there before I installed optimus-manager (the problem exists when running Arch live USB).

Offline

#12 2019-10-04 20:36:35

Al.Piotrowicz
Member
Registered: 2017-08-07
Posts: 74

Re: Strange Reboot Issue

There is the only need to relogging according to the wiki page. Is it possible to turn off an intergrated GPU in the system bios by any chance?

Last edited by Al.Piotrowicz (2019-10-04 20:55:18)

Offline

#13 2019-10-04 21:05:32

developerbmw
Member
Registered: 2019-09-29
Posts: 7

Re: Strange Reboot Issue

There isn't any way to disable the integrated graphics in the BIOS. I think the Nvidia GPU still requires the integrated graphics to function, see https://devtalk.nvidia.com/default/topi … onization/

Offline

#14 2019-10-08 11:55:24

Al.Piotrowicz
Member
Registered: 2017-08-07
Posts: 74

Re: Strange Reboot Issue

My main suspect is a hardware watchdog (iTCO_wdt) more info. Lets wait for some smarter minds opinions. Peace.

Offline

#15 2019-10-10 23:38:12

v2vm
Member
Registered: 2018-03-03
Posts: 12

Re: Strange Reboot Issue

I have exactly the same problem. Our company sells some computers and we test customer returns vigorously before selling the good ones as used.

All units of a particular model started to show the same problem: it hangs during shutdown or reboot, after having "Reached target Power-off", it shows:

printk: shutdown: 4 output lines suppressed due to ratelimiting.

and hangs there, which is pretty much the second to last line of message you would see before a normal shutdown.

Changing /etc/systemd/journald.conf  with:

RateLimitIntervalSec=0s
RateLimitBurst=0

has no effects

Changing kernels to linux-lts has no effects.

Arch live iso and Endevour live iso also have the same issue.

In contrast, another model of our computers shuts down okay; and both models running ubuntu 18.04 shut down with no problems.

Offline

#16 2019-10-11 23:17:46

grinner
Member
Registered: 2019-06-28
Posts: 23

Re: Strange Reboot Issue

developerbmw wrote:

I left the system for around a minute after it hung, and there's no entries in the journal until around the time at which I turned it off and booted properly, which means that it's not just booting without the display working.

Try leaving it longer to see if it will finally reboot.  I had an issue maybe a year ago (on another distro...) where it took upwards of 15 minutes to reboot - in that case it was a problem with a broken mount command, issued earlier, that was still attempting and failing in the background.

Following from the above it might be worth investigating the processes still running during reboot/shutdown (for example with task manager) to see if any candidates stand out - of course this will only go so far but might throw up a process that looks strange to be still running at that point in the reboot proceeding. Wiser heads around here might be able to suggest a better way to go about this.

Last edited by grinner (2019-10-11 23:19:03)

Offline

Board footer

Powered by FluxBB