[SOLVED] Mint 18.3 Shutdown & Restart freeze

weinelb · 02-06-2018, 04:47 AM

Both Shutdown and Restart "freeze". My config:

Code:

System:   

Host:
 nancyn-Vostro-1000 
Kernel:
 4.10.0-38-generic x86_64 (64 bit gcc: 5.4.0)
Desktop:
 Cinnamon 3.6.6 (Gtk 3.18.9-1ubuntu3.3)
Distro:
 Linux Mint 18.3 Sylvia

Machine:  

System:
 Dell 
product:
 Vostro 1000
Mobo:
 Dell 
model:
 0WY383 
Bios:
 Dell v: 2.6.2 
date:
 10/17/2006

CPU:      

Dual core
 AMD Athlon 64 X2 TK-55 (-MCP-)
cache:
 512 KB
flags:
 (lm nx sse sse2 sse3 svm) 
bmips:
 3200
          
clock speeds:

max:
 1800 MHz 
1:
 800 MHz 
2:
 800 MHz

Graphics: 

Card:
 Advanced Micro Devices [AMD/ATI] RS482M [Mobility Radeon Xpress 200]
bus-ID:
 01:05.0
Display Server:
 X.Org 1.18.4 
drivers:
 ati,radeon (unloaded: fbdev,vesa)
Resolution:
 1280x800@60.02hz
GLX Renderer:
 Gallium 0.4 on ATI RS480
GLX Version:
 2.1 Mesa 17.0.7 
Direct Rendering:
 Yes

Audio:    

Card
 Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA)
driver:
 snd_hda_intel 
bus-ID:
 00:14.2
Sound:
 Advanced Linux Sound Architecture v: k4.10.0-38-generic


Network:  

Card-1:
 Broadcom BCM4311 802.11b/g WLAN
driver:
 b43-pci-bridge 
bus-ID:
 05:00.0
IF:
 N/A 
state:
 N/A 
mac:
 N/A

Card-2:
 Broadcom BCM4401-B0 100Base-TX
driver:
 b44 v: 2.0 
bus-ID:
 08:00.0
IF:
 eth0 
state:
 down 
mac:
 <filter>


Drives:   

HDD Total Size:
ID-1:
 /dev/sda 
model:
 FUJITSU_MHY2120B 
size:
 120.0GB


Partition:

ID-1:
 / 
size:
 107G 
used:
 25G (25%) 
fs:
 ext4 
dev:
 /dev/sda1

ID-2:
 swap-1 
size:
 4.16GB 
used:
 0.00GB (0%) 
fs:
 swap 
dev:
 /dev/sda5
RAID:     
 No RAID devices: /proc/mdstat, md_mod kernel module present


Sensors:  

System Temperatures: cpu:
 44.0C 
mobo:
Fan Speeds (in rpm): cpu:
 N/A

Info:     

Processes:
 171 
Uptime:
 10 min 
Memory:
 533.8/3822.8MB
Init:
 systemd 
runlevel:
 5 
Gcc sys:
 5.4.0
Client:
 Shell (bash 4.3.481) 
inxi:
 2.2.35

After forced power off startup is normal.

business_kid · 02-06-2018, 10:38 AM

Hi.

You will see from This_Thread that acpi is ropey on 10 year old boxes in the kernel. These older machines have a Northbridge/Southbridge design before the days of APUs which have different hardware requirements. Kernel-4.15.0 booted on my box, but it is very unhappy complaining of the dsdt. It crashes Hazel's.

Why don't you look in the logs to see what errors it is throwing? Does it get to reboot and freeze on startup, or does it fail on shutdown? /var/log/dmesg and /var/log/syslog are worth checking. Can you add a boot choice with the option "acpi=off" and see if that solves it? Don't stay running on this as the box might overheat. Also, in case Mint has some clever script that's invoked, you can suspend, hibernate, & restart with these three commands

Code:

# echo mem > /sys/power/state
# echo disk > /sys/power/state
# shutdown -r now

weinelb · 02-06-2018, 11:58 AM

Business Hid,

Problem is in shutdown; boot after forced power off is normal. The dlog says "Nothing has been logged yet." and syslog has no entry from shutdown; it begins with 'KLogPermitNonKernelFacility not permitted' (which may be why) then boot entries.

The "echo"s you suggest do not work in user or root mode. And in root the first causes an immediate crash to black screen. The "shutdown -r now" command has same freeze issue as any other shutdown.

weinelb · 02-06-2018, 12:01 PM

Business Kid,

Problem is in shutdown; boot after forced power off is normal. The dlog says "Nothing has been logged yet." and syslog has no entry from shutdown; it begins with 'KLogPermitNonKernelFacility not permitted' (which may be why) then boot entries.

The "echo"s you suggest do not work in user or root mode. And in root the first causes an immediate crash to black screen. The "shutdown -r now" command has same freeze issue as any other shutdown.

ADDENDUM: After forced power off Mint does not "auto login" after booting.

business_kid · 02-07-2018, 05:24 AM

Hmmm.

The first should suspend. Mine does. The second is hibernate, the third a reboot. It looks like a problem with your box, bios or acpi. One thing to try is to kill acpid, and immediately restart it as 'acpid -l' which should log acpi requests to syslog. We can at least see if acpi is being asked to do stuff. I would also see if there is a bios update.

weinelb · 02-07-2018, 07:27 AM

Business Kid,

Killing "apcid" before "shutdown" had no effect (still hangs after 2nd dot under logo). As a newbie I'm not sure how to shutdown or restart or boot without apci. Can you provide terminal code?

hydrurga · 02-07-2018, 08:42 AM

Quote:

Originally Posted by weinelb

Business Kid,

Killing "apcid" before "shutdown" had no effect (still hangs after 2nd dot under logo). As a newbie I'm not sure how to shutdown or restart or boot without apci. Can you provide terminal code?

Just a note that it is acpid and acpi (Advanced Configuration and Power Interface), not apcid and apci.

weinelb · 02-07-2018, 08:45 AM

Hydrurga,

Yes, I know that, but my fingers don't always obey.

roy_lt_69 · 02-07-2018, 08:00 PM

For older systems, you might have to also specify other boot options, like turning off acpi and / or apic. For example specifying acpi=off noapic during boot.

BW-userx · 02-07-2018, 08:07 PM

what happened it just went blank screen and hung? was you running anything, make some changes the did a quick reboot, just start up something then did a quick reboot?

mine hangs sometime when I do this or whatever, and hard power button off, then goes back to normal, I'd say is normal.

weinelb · 02-08-2018, 04:22 AM

BW-userx,

Machine is a Dell Vostro 1000 I'm setting up for an amateur (who won't want to hard power off every time she uses machine). Notebook starts the Shutdown (or first part of Restart) displays the Mint logo with 5 dots below and changes color of the first [leftmost] 2 dots then hangs forever. It doesn't matter if I use power from Menu or use console commands—result is always the same (but haven't tried from root as I don't want to show her how to act as root).

Right now am looking for a way to log the shutdown so I can identify what is hanging...

weinelb · 02-08-2018, 06:45 AM

Found it. Although the Vostro BIOS does not have any ACPI specific settings it does have a "PowerNow Control" setting under Advanced which sounded suspicious. Disabling this BIOS Advanced option did the trick! Now both Shutdown and Restart work fine from the Menu.

BW-userx · 02-08-2018, 07:53 AM

Quote:

Originally Posted by weinelb

Found it. Although the Vostro BIOS does not have any ACPI specific settings it does have a "PowerNow Control" setting under Advanced which sounded suspicious. Disabling this BIOS Advanced option did the trick! Now both Shutdown and Restart work fine from the Menu.

good investigatory skills. The way you posted it sounds like a one of them glitchy things where the user did something and didn't give the OS time to catch up to it, then shut down so it tossed it into a state of confusion where it just ends up hanging, sometimes trying to resolve the situation, but all you see it the same thing, it not doing what you're expecting it to do.

weinelb · 02-08-2018, 08:12 AM

BW-userx,

I suspected ACPI on this old laptop, but a quick browse through BIOS did not see any ACPI settings. It was only when I suspected anything related to “power” (which ACPI handles) that I thought to turn off the “PowerNow Control” setting.

I should have good “investigative” skills since I've been doing that for over 40 years, but the new Mint and Ubuntu are unfamiliar (the only Ubuntu I ran was server 6, but in the 70s I was a “Unix SVR4 wizard” though Linux has only superficial resemblance after 40 years of evolution). E.g. where has "/var/log/" shutdown log gone?

BW-userx · 02-08-2018, 08:26 AM

I'm not a big "Linux" know a lot, but syslog? if it does not have one got a find out why.

I have found that because Linux is open source and with all of the "knock offs" and original Linux/GNUs Distros, the ones that are knock off try to put there own spin on it.

So where one may find similarities between all of the different distros, their are times where one distro will not have what the other one did in order to do what it was you were doing when one was using that other distro. Even with setting up desktops, even though I like what Plasma has with desktop switching effects, I tend to stay with the less gui intense WM link WindowMaker, FLuxbox, and I've currently went back to openbox for a bit of a stay.

As a saying loosely goes, if you want to learn Linux use Slackware, if you want to learn whatever other distro that is out there, then use that one.

So depending on what Distro you are using you'd have to look it up for that distro for some of the stuff on Linux/GNU.

There is something called "snoopy logger" Snoopy is a tiny library that logs all executed commands (+ arguments) on your system. so you can see what "they" did to screw it up, and whatever.
just a little fyi. https://github.com/a2o/snoopy
could be in a repo, but look at your syslog see what you can see.