[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...

[AllanPen]

It seems I have a similar problem periodically shutting down Mint. It hangs on the ming icon. Now I think it is after I have used the printer. On the shut down hang I hit the esc key and see a line denoting a problem shutting sown CUPS.
Edit: Just found the following showing and error yesterday:

Code: Select all

W [24/Dec/2018:15:15:06 -0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Officejet_Pro_8610_0ED74C_-Gray..\' already exists
W [24/Dec/2018:15:15:06 -0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Officejet_Pro_8610_0ED74C_-DeviceN..\' already exists
W [24/Dec/2018:16:50:46 -0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Officejet_Pro_8610_0ED74C_-Gray..\' already exists
W [24/Dec/2018:16:50:46 -0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Officejet_Pro_8610_0ED74C_-DeviceN..\' already exists
W [24/Dec/2018:16:58:27 -0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Officejet_Pro_8610_0ED74C_-Gray..\' already exists
W [24/Dec/2018:16:58:27 -0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Officejet_Pro_8610_0ED74C_-DeviceN..\' already exists
W [24/Dec/2018:17:18:53 -0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Officejet_Pro_8610_0ED74C_-Gray..\' already exists
W [24/Dec/2018:17:18:53 -0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Officejet_Pro_8610_0ED74C_-DeviceN..\' already exists
W [24/Dec/2018:20:56:10 -0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Officejet_Pro_8610_0ED74C_-Gray..\' already exists
W [24/Dec/2018:20:56:10 -0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Officejet_Pro_8610_0ED74C_-DeviceN..\' already exists
W [24/Dec/2018:21:28:58 -0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Officejet_Pro_8610_0ED74C_-Gray..\' already exists
W [24/Dec/2018:21:28:58 -0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Officejet_Pro_8610_0ED74C_-DeviceN..\' already exists
W [25/Dec/2018:10:17:13 -0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Officejet_Pro_8610_0ED74C_-Gray..\' already exists
W [25/Dec/2018:10:17:13 -0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Officejet_Pro_8610_0ED74C_-DeviceN..\' already exists
W [25/Dec/2018:10:37:29 -0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Officejet_Pro_8610_0ED74C_-Gray..\' already exists
W [25/Dec/2018:10:37:29 -0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Officejet_Pro_8610_0ED74C_-DeviceN..\' already exists
W [25/Dec/2018:13:56:26 -0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Officejet_Pro_8610_0ED74C_-Gray..\' already exists
W [25/Dec/2018:13:56:26 -0800] CreateProfile failed:cups doesn't close incups doesn't close in linux mint linux mint org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Officejet_Pro_8610_0ED74C_-DeviceN..\' already exists
W [25/Dec/2018:20:50:42 -0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Officejet_Pro_8610_0ED74C_-Gray..\' already exists
W [25/Dec/2018:20:50:42 -0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Officejet_Pro_8610_0ED74C_-DeviceN..\' already exists

[JuozasM]

Hi "hooly",

I just read your post and the good replies to it. Here are my thoughts on this as well.

I too have noticed that it does take some time to shutdown or restart.

FYI: There are also various "shutdown" applications and or key combinations (and scripts), that can accelerate shutting down. "Qshutdown" in the Software Manager or Synaptic Package Manager (SPM) is a really nice application, you can just right-click its icon to select shutdown now, or even set timed options.


Other posts:

On my ancient under-powered computer, I always get boot error messages related to "ACPI and APIC", but the system always works. After reading these articles and posts, they recommend changing the "Grub2" boot up file to either turn this off (disable it), or add "acpi=force reboot=acpi" to the Linux command line.

To edit the Grub bootloader file using the "xed" text editor

Code: Select all

sudo xed /etc/default/grub

Locate the line below
GRUB_CMDLINE_LINUX_DEFAULT="quiet"

Change it to add acpi=force reboot=acpi between the quotes
GRUB_CMDLINE_LINUX_DEFAULT="quiet acpi=force reboot=acpi"
or disable "ACPI and APIC"
GRUB_CMDLINE_LINUX_DEFAULT="quiet noapic acpi=off"


Then, save the changes and exit the text editor, and update Grub2 changes, and reboot

Code: Select all

sudo update-grub2

=================================================================================
(1) {SOLVED}My PC won't shutdown with linux mint 18.3 - Linux Mint Forums
viewtopic.php?f=90&t=270377

Why can't I restart/shutdown? - Ask Ubuntu
https://askubuntu.com/questions/7114/wh ... t-shutdown

BootOptions - Community Help Wiki
* see Common Kernel Options category
https://help.ubuntu.com/community/BootOptions

Hope this helps ...

If you have an old pc thats dont have ACPI. "acpi=force reboot=acpi" not worked, but "noapic acpi=off" worked just fine.