[SOLVED] how to troubleshoot v e r y s l o w shutdown/reboot?

[hooly]

@ phd21 : thanks for the suggestions. i'll keep the grub mods regarding ACPI and APIC in mind though i'm reluctant to go ahead with those until i have some reason to believe that one or both are related to the problems i'm actually having.

[phd21]

Hi hooly,

I added the "acpi=force reboot=acpi" to my Grub file, rebooted, and it seemed to help a lot. You can always try them and see if it works, if not just remove them from the Grub file in the same way, and reboot.

[diesel79]

I'm pretty sure this is a problem with the nvidia drivers. I have the problem in both Mint 19 Beta and in Ubuntu 18.04.

[Pakha]

I'm pretty sure this is a problem with the nvidia drivers. I have the problem in both Mint 19 Beta and in Ubuntu 18.04.

Not. I am having Intel HD Graphics and had such problem, after I uncomment DefaultTimeoutStopSec=10s in /etc/systemd/system.conf the system began shutdown very quickly.

[wpshooter]

...1) try pressing ESC while it shutdowns, take note of any messages displayed...
...2) open Log File Viewer, check past logs at around the time the shutdown was initiated...

Is there a log specifically related to the shutdown process or are the logs related to shutdown
included in the system log ? I don't see a log named shutdown.

Thanks.

[thx-1138]

Nope, there's no log specifically for shutdown - you just dig through kern.log at around the time you initiated the shutdown,
and then try to understand / decode the flow of it roughly before the shutdown procedure itself started misbehaving...

[wpshooter]

Nope, there's no log specifically for shutdown - you just dig through kern.log at around the time you initiated the shutdown,
and then try to understand / decode the flow of it roughly before the shutdown procedure itself started misbehaving...

Would the problem be likely to be found in the kernel log or the log named syslog ?

Thanks.

[thx-1138]

...i usually check kern.log first myself, but it doesn't hurt checking both...
There isn't always a one-to-one 100% straight answer: it might be a kernel version quirk, a misbehaving process, or a combination of both...