System will not halt

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
Post Reply
tclark
Level 1
Level 1
Posts: 20
Joined: Fri Jun 19, 2015 8:19 pm

System will not halt

Post by tclark » Mon Jul 16, 2018 9:58 am

For a few weeks now I have not been able to cleanly halt my LM 18.3 system. The system goes to a black screen, but will not shut down. I cannot open a terminal with Ctrl-Alt-F1, which would seem to indicate that Linux is no longer running at this point. I have to press and hold the power button to force a shutdown.

Sometimes -- about every fourth or fifth shutdown -- the system will go to a black screen and the fans will go to maximum. Again, I cannot get a Linux terminal at this point. It sounds like the system is running 100% on all four cores, but there's not even an operating system loaded at this point, so how can this be? I thought it might be a BIOS problem with my system, but Ubuntu MATE on another partition does not exhibit these problems.

Any ideas or suggestions are appreciated.

User avatar
karlchen
Level 19
Level 19
Posts: 9336
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: System will not halt

Post by karlchen » Mon Jul 16, 2018 10:54 am

Hello, tclark.

I suggest the following steps in order to find out what prevent syour system from shutting down completely:
  • Next time when you power on your machine, enter the Grub boot menu.
  • Navigate to the Grub menu item which will boot Linux Mint 18.3.
  • Press the letter e for edit.
  • Inside the editor which will come up, locate the line which loads vmlinuz. Locate the 2 words "quiet splash". Remove the 2 words, but leave the 2 double quotes.
  • Press the function key <F10> to boot Linux Mint 18.3.
  • Removing the word quiet and splash will have two visible effects during startup:
    + no splash screen will be displayed
    + all the informative system messages, which tell you what happens during startup, will be displayed to you.
  • Once the system is up and running, use it as you would always do.
  • When you shut down later on, the system will again display what it is doing during shutdown.
  • I assume that at some point the system will get stuck on a particular message and stop shutting down.
This last message might hold a hint why shutdown fails and gets stuck.
Please, report this message here.

Regards,
Karl
Image
Linux Mint 18.1 64-bit Cinnamon Desktop, Total Commander 9.21a 64-bit
Ubuntu 18.04.1 32-bit Mate Desktop, Total Commander 9.21a 32-bit
Windows? - 1 window in every room

tclark
Level 1
Level 1
Posts: 20
Joined: Fri Jun 19, 2015 8:19 pm

Re: System will not halt

Post by tclark » Mon Jul 16, 2018 9:21 pm

Karl,

Thanks for the help. I actually made the changes in /etc/default/grub so that they persist between reboots.

I changed

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT=""
and ran 'sudo update-grub'. I rebooted twice to verify that this is working as expected, and it is -- I get messages as the system is shutting down.

Unfortunately, when I rebooted after about 8 hours of work the system hung with a black screen again -- no messages. I noticed that the power LED on my monitor turned amber, which indicates that the system is not even sending a video signal at this point.

I used to troubleshoot by looking at /var/log/messages, but I noticed that this file no long exists. What is the replacement? There are a bunch of files in /var/log/, but I don't know what's what.

Thanks,

Ted

Update: I've gotten this to fail a couple more times, and the system writes about 30 lines of text to the screen and then immediately clears the screen before I can read any of it.

upuv
Level 1
Level 1
Posts: 12
Joined: Sun Nov 01, 2015 9:59 pm

Re: System will not halt

Post by upuv » Tue Jul 17, 2018 1:59 am

If you are not even getting a /var/log/messages file you are not booting properly.

This really sounds like a hardware fault.
When I you say the system goes to 100%, as illustrated by the fans. This makes me think you have a drive issue. The CPU is in a wait state for IO on the drive will cause this sort of behaviour.
RAM would also be on my list of suspects. Fortunately the grub boot menu lets you test that easily.
But combine the first symptom with the high CPU/FAN mode. I really think your drive is toast. Or at the very least you filesystem with Mint on it is corrupt.

Make backups ASAP.

User avatar
trytip
Level 8
Level 8
Posts: 2151
Joined: Tue Jul 05, 2016 1:20 pm

Re: System will not halt

Post by trytip » Tue Jul 17, 2018 2:43 am

try a different kernel
Image

User avatar
Pierre
Level 17
Level 17
Posts: 7426
Joined: Fri Sep 05, 2008 5:33 am
Location: Perth, AU.

Re: System will not halt

Post by Pierre » Tue Jul 17, 2018 2:58 am

yeah - - it would help to know, which kernel, it is that you are using,
you can determine this from the Boot Menu, and before you hit Enter to bypass the Boot Timer.
- assuming that you are getting some Boot Menu - - if not, hold down the Shift Key during the boot-up.
Image
Please edit your original post title to include [SOLVED] - when your problem is solved!
and DO LOOK at those Unanswered Topics - - you may be able to answer some!.

User avatar
karlchen
Level 19
Level 19
Posts: 9336
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: System will not halt

Post by karlchen » Tue Jul 17, 2018 7:10 am

Note:
The file to look at on Mint is not /var/log/messages, but /var/log/syslog.
On systems starting with Mint 18.x you can also use the commandline journalctl -b or journalctl -b number, where you replace "number" by -1, -2, -3 etc, depending on how many sessions you wish to go back. Default is 0, current session, if you do not specify a number at all.
Image
Linux Mint 18.1 64-bit Cinnamon Desktop, Total Commander 9.21a 64-bit
Ubuntu 18.04.1 32-bit Mate Desktop, Total Commander 9.21a 32-bit
Windows? - 1 window in every room

tclark
Level 1
Level 1
Posts: 20
Joined: Fri Jun 19, 2015 8:19 pm

Re: System will not halt

Post by tclark » Tue Jul 17, 2018 4:37 pm

upuv wrote:
Tue Jul 17, 2018 1:59 am
If you are not even getting a /var/log/messages file you are not booting properly.

This really sounds like a hardware fault.
When I you say the system goes to 100%, as illustrated by the fans. This makes me think you have a drive issue. The CPU is in a wait state for IO on the drive will cause this sort of behaviour.
RAM would also be on my list of suspects. Fortunately the grub boot menu lets you test that easily.
But combine the first symptom with the high CPU/FAN mode. I really think your drive is toast. Or at the very least you filesystem with Mint on it is corrupt.

Make backups ASAP.
I have Ubuntu MATE on another partition, and it works fine, so I don't think this is a hardware problem. It is possible that I have one or more corrupt system files, I suppose. I ran debsums, but this did not find any problems.
Last edited by tclark on Tue Jul 17, 2018 4:46 pm, edited 1 time in total.

tclark
Level 1
Level 1
Posts: 20
Joined: Fri Jun 19, 2015 8:19 pm

Re: System will not halt

Post by tclark » Tue Jul 17, 2018 4:39 pm

Pierre wrote:
Tue Jul 17, 2018 2:58 am
yeah - - it would help to know, which kernel, it is that you are using,
you can determine this from the Boot Menu, and before you hit Enter to bypass the Boot Timer.
- assuming that you are getting some Boot Menu - - if not, hold down the Shift Key during the boot-up.
I'm currently using 4.4.0-130-generic, but I have had the same problems with 4.4.0-128-generic. I have many previous kernels still installed on the system, going back to LM 18.1, including some 4.10 and 4.13 kernels, so I can try another if you have any suggestions of what I might try.

tclark
Level 1
Level 1
Posts: 20
Joined: Fri Jun 19, 2015 8:19 pm

Re: System will not halt

Post by tclark » Tue Jul 17, 2018 4:42 pm

karlchen wrote:
Tue Jul 17, 2018 7:10 am
Note:
The file to look at on Mint is not /var/log/messages, but /var/log/syslog.
On systems starting with Mint 18.x you can also use the commandline journalctl -b or journalctl -b number, where you replace "number" by -1, -2, -3 etc, depending on how many sessions you wish to go back. Default is 0, current session, if you do not specify a number at all.
Thanks for the information about /var/log/syslog and journalctl -- I will try this next time the system fails and see what information I can find.

User avatar
karlchen
Level 19
Level 19
Posts: 9336
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: System will not halt

Post by karlchen » Tue Jul 17, 2018 4:47 pm

tclark wrote:
Tue Jul 17, 2018 4:37 pm
I have Ubuntu MATE on another partition, and it works fine, so I don't think this is a hardware problem.
Please, from the affected system post the complete screen output of the terminal command

Code: Select all

inxi -Fxz
We need precise technical details, which inxi will provide.

Also, please, inspect /var/log/syslog (and the previous syslog /var/log/syslog.1). Alternatively use the journalctl command in order to inspect the same log entries, as I had explained in a post above.
Image
Linux Mint 18.1 64-bit Cinnamon Desktop, Total Commander 9.21a 64-bit
Ubuntu 18.04.1 32-bit Mate Desktop, Total Commander 9.21a 32-bit
Windows? - 1 window in every room

tclark
Level 1
Level 1
Posts: 20
Joined: Fri Jun 19, 2015 8:19 pm

Re: System will not halt

Post by tclark » Tue Jul 17, 2018 6:31 pm

Here's the output from inxi:

Code: Select all

System:    Host: xxxxx Kernel: 4.4.0-130-generic x86_64 (64 bit gcc: 5.4.0) Desktop: MATE 1.18.0 (Gtk 2.24.30)
           Distro: Linux Mint 18.3 Sylvia                                       
Machine:   Mobo: ASUSTeK model: PRIME H270M-PLUS v: Rev X.0x Bios: American Megatrends v: 0320 date: 11/22/2016
CPU:       Quad core Intel Core i5-7600 (-MCP-) cache: 6144 KB                  
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 28031    
           clock speeds: max: 4100 MHz 1: 967 MHz 2: 911 MHz 3: 1032 MHz 4: 882 MHz
Graphics:  Card: Intel Device 5912 bus-ID: 00:02.0                              
           Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1920x1080@60.00hz
           GLX Renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)         
           GLX Version: 3.0 Mesa 18.0.5 Direct Rendering: Yes                   
Audio:     Card Intel Device a2f0 driver: snd_hda_intel bus-ID: 00:1f.3 Sound: ALSA v: k4.4.0-130-generic
Network:   Card-1: Intel Ethernet Connection (2) I219-V driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6
           IF: enp0s31f6 state: down mac: <filter>                              
           Card-2: Edimax EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]
           driver: rtl8192cu usb-ID: 001-002                                    
           IF: wlx74da388d397c state: N/A mac: N/A                              
Drives:    HDD Total Size: 3500.7GB (4.8% used) ID-1: /dev/sda model: Samsung_SSD_850 size: 500.1GB
           ID-2: /dev/sdb model: ST3000DM008 size: 3000.6GB                     
Partition: ID-1: / size: 214G used: 127G (63%) fs: ext4 dev: /dev/sda2          
           ID-2: swap-1 size: 34.22GB used: 0.00GB (0%) fs: swap dev: /dev/sda4 
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present          
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C                          
           Fan Speeds (in rpm): cpu: 0                                          
Info:      Processes: 198 Uptime: 1:46 Memory: 1056.5/32041.2MB Init: systemd runlevel: 5 Gcc sys: 5.4.0
           Client: Shell (bash 4.3.481) inxi: 2.2.35
I will post what I find in /var/log/syslog (and syslog.1) next time the system fails, probably in a few hours.

tclark
Level 1
Level 1
Posts: 20
Joined: Fri Jun 19, 2015 8:19 pm

Re: System will not halt

Post by tclark » Wed Jul 18, 2018 10:33 am

Here's a bit of /var/log/syslog. I shut down at 09:02:00. This is a case where the fans started spinning up and I had to force a shutdown.

Code: Select all

Jul 18 08:45:01 xxxxx CRON[8266]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jul 18 08:55:01 xxxxx CRON[8925]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jul 18 09:00:46 xxxxx ntpd[1378]: 35.237.173.121 local addr 192.168.254.22 -> <null>
Jul 18 09:01:26 xxxxx kernel: [ 4977.667501] azx_single_send_cmd: 70 callbacks suppressed
Jul 18 09:02:00 xxxxx systemd[1]: Stopped Stop ureadahead data collection 45s after completed startup.
Jul 18 09:02:00 xxxxx systemd[1]: Stopping Console Manager...
Jul 18 09:02:00 xxxxx systemd[1]: Stopping ACPI event daemon...
Jul 18 09:02:00 xxxxx systemd[1]: Stopping Save/Restore Sound Card State...
Jul 18 09:02:00 xxxxx dbus[899]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service'
Jul 18 09:02:00 xxxxx systemd[1]: Stopping Authenticate and Authorize Users to Run Privileged Tasks...
Jul 18 09:02:00 xxxxx systemd[1]: Stopping Disk Manager...
Jul 18 09:02:00 xxxxx systemd[1]: Stopping User Manager for UID 1000...
Jul 18 09:02:00 xxxxx systemd[1]: Stopping Daemon for power management...
Jul 18 09:02:00 xxxxx systemd[1]: Stopped target Timers.
Jul 18 09:02:00 xxxxx systemd[1]: Stopped Daily apt upgrade and clean activities.
Jul 18 09:02:00 xxxxx systemd[1]: Stopped Daily apt download activities.
Jul 18 09:02:00 xxxxx systemd[1]: Stopped target Graphical Interface.
Jul 18 09:02:00 xxxxx systemd[1]: Stopping Accounts Service...
Jul 18 09:02:00 xxxxx systemd[1]: Stopped target Sound Card.
Jul 18 09:02:00 xxxxx systemd[1]: Stopping MDM Display Manager...
Jul 18 09:02:00 xxxxx systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jul 18 09:02:00 xxxxx systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Jul 18 09:02:00 xxxxx systemd[9583]: mdm.service: Failed at step EXEC spawning /usr/sbin/mdm-stop: No such file or directory
Jul 18 09:02:00 xxxxx systemd[2788]: Reached target Shutdown.
Jul 18 09:02:00 xxxxx systemd[2788]: Starting Exit the Session...
Jul 18 09:02:00 xxxxx systemd[2788]: Stopped target Default.
Jul 18 09:02:00 xxxxx systemd[2788]: Stopped target Basic System.
Jul 18 09:02:00 xxxxx systemd[2788]: Stopped target Sockets.
Jul 18 09:02:00 xxxxx systemd[2788]: Stopped target Paths.
Jul 18 09:02:00 xxxxx systemd[2788]: Stopped target Timers.
Jul 18 09:02:00 xxxxx systemd[2788]: Received SIGRTMIN+24 from PID 9593 (kill).
Jul 18 09:02:00 xxxxx org.gtk.vfs.Daemon[2969]: A connection to the bus can't be made
Jul 18 09:02:00 xxxxx systemd[1]: Stopping Session c1 of user tclark.
Jul 18 09:02:00 xxxxx systemd[1]: Stopped target Multi-User System.
Jul 18 09:02:00 xxxxx mdm[1375]: mdm[1375]: WARNING: mdm_cleanup_children: child 1433 crashed of signal 1
Jul 18 09:02:00 xxxxx mdm[1375]: mdm[1375]: WARNING: mdm_cleanup_children: Slave crashed, killing its children
Jul 18 09:02:00 xxxxx systemd[1]: Stopping LSB: disk temperature monitoring daemon...
Jul 18 09:02:00 xxxxx mdm[1375]: WARNING: mdm_cleanup_children: child 1433 crashed of signal 1
Jul 18 09:02:00 xxxxx systemd[1]: Stopping LSB: Start/stop sysstat's sadc...
Jul 18 09:02:00 xxxxx mdm[1375]: WARNING: mdm_cleanup_children: Slave crashed, killing its children
Jul 18 09:02:00 xxxxx systemd[1]: Stopping Modem Manager...
Jul 18 09:02:00 xxxxx systemd[1]: Stopped OpenVPN service.
Jul 18 09:02:00 xxxxx systemd[1]: Stopping LSB: Start and stop the mysql database server daemon...
Jul 18 09:02:00 xxxxx rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="926" x-info="http://www.rsyslog.com"] exiting on signal 15.
Jul 18 09:03:05 xxxxx rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="909" x-info="http://www.rsyslog.com"] start
Jul 18 09:03:05 xxxxx rsyslogd-2222: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ]
Jul 18 09:03:05 xxxxx rsyslogd: rsyslogd's groupid changed to 108
Jul 18 09:03:05 xxxxx rsyslogd: rsyslogd's userid changed to 104
On a possibly related note, journalctl does not work on my system:

Code: Select all

tclark@xxxxx ~ $ sudo journalctl -b -1                                          
[sudo] password for tclark:                                                     
Specifying boot ID has no effect, no persistent journal was found               
tclark@xxxxx ~ $ sudo journalctl -b 1                                           
Specifying boot ID has no effect, no persistent journal was found               
tclark@xxxxx ~ $ ll /var/log/syslog*                                            
-rw-r----- 1 syslog adm 196828 Jul 18 09:21 /var/log/syslog                     
-rw-r----- 1 syslog adm 938688 Jul 18 07:43 /var/log/syslog.1                   
-rw-r----- 1 syslog adm 331732 Jul 17 07:35 /var/log/syslog.2.gz                
-rw-r----- 1 syslog adm 144251 Jul 16 07:43 /var/log/syslog.3.gz                
-rw-r----- 1 syslog adm 106568 Jul 15 13:32 /var/log/syslog.4.gz                
-rw-r----- 1 syslog adm 228013 Jul 14 09:53 /var/log/syslog.5.gz                
-rw-r----- 1 syslog adm 128151 Jul 13 07:29 /var/log/syslog.6.gz                
-rw-r----- 1 syslog adm 566011 Jul 12 07:28 /var/log/syslog.7.gz                
tclark@xxxxx ~ $

tclark
Level 1
Level 1
Posts: 20
Joined: Fri Jun 19, 2015 8:19 pm

Re: System will not halt

Post by tclark » Wed Jul 18, 2018 11:39 pm

Here's another syslog from later in the day:

Code: Select all

Jul 18 22:21:56 xxxxx kernel: [ 8963.644649] [UFW BLOCK] IN=wlx74da388d397c OUT= MAC=01:00:5e:00:00:fb:b4:9c:df:77:90:71:08:00 SRC=192.168.254.16 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=60757 PROTO=2 
Jul 18 22:25:01 xxxxx CRON[13707]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jul 18 22:26:26 xxxxx kernel: [ 9233.718137] azx_single_send_cmd: 70 callbacks suppressed
Jul 18 22:26:26 xxxxx kernel: [ 9233.727799] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f0d00. -5
Jul 18 22:26:26 xxxxx kernel: [ 9233.727971] snd_hda_codec_hdmi hdaudioC0D2: HDMI: invalid ELD buf size -1
Jul 18 22:26:26 xxxxx kernel: [ 9233.728058] snd_hda_codec_hdmi hdaudioC0D2: HDMI: invalid ELD buf size -1
Jul 18 22:26:26 xxxxx kernel: [ 9234.024429] snd_hda_codec_hdmi hdaudioC0D2: HDMI: invalid ELD buf size -1
Jul 18 22:26:26 xxxxx kernel: [ 9234.324462] snd_hda_codec_hdmi hdaudioC0D2: HDMI: invalid ELD buf size -1
Jul 18 22:26:27 xxxxx kernel: [ 9234.624467] snd_hda_codec_hdmi hdaudioC0D2: HDMI: invalid ELD buf size -1
Jul 18 22:26:27 xxxxx kernel: [ 9234.924467] snd_hda_codec_hdmi hdaudioC0D2: HDMI: invalid ELD buf size -1
Jul 18 22:26:27 xxxxx kernel: [ 9235.224477] snd_hda_codec_hdmi hdaudioC0D2: HDMI: invalid ELD buf size -1
Jul 18 22:26:27 xxxxx kernel: [ 9235.524490] snd_hda_codec_hdmi hdaudioC0D2: HDMI: invalid ELD buf size -1
Jul 18 22:26:28 xxxxx kernel: [ 9235.824507] snd_hda_codec_hdmi hdaudioC0D2: HDMI: invalid ELD buf size -1
Jul 18 22:26:28 xxxxx kernel: [ 9236.124512] snd_hda_codec_hdmi hdaudioC0D2: HDMI: invalid ELD buf size -1
Jul 18 22:26:31 xxxxx kernel: [ 9239.124636] azx_single_send_cmd: 104 callbacks suppressed
Jul 18 22:26:37 xxxxx dbus[917]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Jul 18 22:26:52 xxxxx kernel: [ 9259.715819] azx_single_send_cmd: 70 callbacks suppressed
Jul 18 22:26:56 xxxxx kernel: [ 9264.097138] [UFW BLOCK] IN=wlx74da388d397c OUT= MAC=01:00:5e:00:00:fb:b4:9c:df:77:90:71:08:00 SRC=192.168.254.16 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=55097 PROTO=2 
Jul 18 22:26:57 xxxxx kernel: [ 9264.818074] azx_single_send_cmd: 245 callbacks suppressed
Jul 18 22:27:04 xxxxx systemd[1]: Stopped Stop ureadahead data collection 45s after completed startup.
Jul 18 22:27:04 xxxxx console-kit-daemon[1860]: (process:14132): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Jul 18 22:27:04 xxxxx systemd[1]: Stopping Disk Manager...
Jul 18 22:27:04 xxxxx mdm[1314]: WARNING: mdm_cleanup_children: child 1372 crashed of signal 1
Jul 18 22:27:04 xxxxx mdm[1314]: mdm[1314]: WARNING: mdm_cleanup_children: child 1372 crashed of signal 1
Jul 18 22:27:04 xxxxx mdm[1314]: mdm[1314]: WARNING: mdm_cleanup_children: Slave crashed, killing its children
Jul 18 22:27:04 xxxxx systemd[1]: Stopping Session c1 of user tclark.
Jul 18 22:27:04 xxxxx mdm[1314]: WARNING: mdm_cleanup_children: Slave crashed, killing its children
Jul 18 22:27:04 xxxxx systemd[1]: Stopping Daemon for power management...
Jul 18 22:27:04 xxxxx mate-session[1934]: Gdk-WARNING: mate-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Jul 18 22:27:04 xxxxx systemd[1]: Stopping Save/Restore Sound Card State...
Jul 18 22:27:04 xxxxx systemd[1]: Stopping User Manager for UID 1000...
Jul 18 22:27:04 xxxxx thermald[947]: Terminating ...
Jul 18 22:27:04 xxxxx systemd[1]: Stopped target Sound Card.
Jul 18 22:27:04 xxxxx systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jul 18 22:27:04 xxxxx systemd[1]: Stopped target Timers.
Jul 18 22:27:04 xxxxx systemd[1]: Stopped Daily apt upgrade and clean activities.
Jul 18 22:27:04 xxxxx rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="915" x-info="http://www.rsyslog.com"] exiting on signal 15.
Jul 18 22:27:55 xxxxx rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="910" x-info="http://www.rsyslog.com"] start
Jul 18 22:27:55 xxxxx systemd-modules-load[339]: Inserted module 'lp'
Jul 18 22:27:55 xxxxx systemd-modules-load[339]: Inserted module 'ppdev'
Jul 18 22:27:55 xxxxx systemd-modules-load[339]: Inserted module 'parport_pc'

tclark
Level 1
Level 1
Posts: 20
Joined: Fri Jun 19, 2015 8:19 pm

Re: System will not halt

Post by tclark » Thu Jul 19, 2018 6:29 pm

Another syslog. I removed and reinstalled mdm prior to this, and I am no longer getting mdm warnings, but I suppose this could be coincidence.

Code: Select all

Jul 19 17:05:01 xxxxx CRON[7408]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jul 19 17:09:01 xxxxx CRON[7660]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
Jul 19 17:10:33 xxxxx dbus[881]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Jul 19 17:14:14 xxxxx dbus[881]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Jul 19 17:14:50 xxxxx systemd[1]: Stopping User Manager for UID 1000...
Jul 19 17:14:50 xxxxx systemd[1]: Stopping Disk Manager...
Jul 19 17:14:50 xxxxx systemd[1874]: Reached target Shutdown.
Jul 19 17:14:50 xxxxx systemd[1]: Stopping Save/Restore Sound Card State...
Jul 19 17:14:50 xxxxx console-kit-daemon[1885]: (process:8830): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Jul 19 17:14:50 xxxxx systemd[1]: Stopped target Sound Card.
Jul 19 17:14:50 xxxxx systemd[1874]: Starting Exit the Session...
Jul 19 17:14:50 xxxxx systemd[1874]: Stopped target Default.
Jul 19 17:14:50 xxxxx systemd[1874]: Stopped target Basic System.
Jul 19 17:14:50 xxxxx systemd[1874]: Stopped target Sockets.
Jul 19 17:14:50 xxxxx systemd[1874]: Stopped target Paths.
Jul 19 17:14:50 xxxxx systemd[1874]: Stopped target Timers.
Jul 19 17:14:50 xxxxx org.gtk.vfs.Daemon[2051]: A connection to the bus can't be made
Jul 19 17:14:50 xxxxx org.gtk.vfs.Daemon[2051]: A connection to the bus can't be made
Jul 19 17:14:50 xxxxx org.gnome.evolution.dataserver.Calendar7[2051]: (evolution-calendar-factory-subprocess:2477): GLib-GIO-WARNING **: Error releasing name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx2463x2: The connection is closed
Jul 19 17:14:50 xxxxx systemd[1874]: Received SIGRTMIN+24 from PID 8835 (kill).
Jul 19 17:14:50 xxxxx systemd[1]: Stopping Session c1 of user tclark.
Jul 19 17:14:50 xxxxx systemd[1]: Stopping Console Manager...
Jul 19 17:14:50 xxxxx systemd[1]: Stopped Stop ureadahead data collection 45s after completed startup.
Jul 19 17:14:50 xxxxx systemd[1]: Stopped target Graphical Interface.
Jul 19 17:14:50 xxxxx rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="903" x-info="http://www.rsyslog.com"] exiting on signal 15.
Jul 19 17:15:52 xxxxx rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="928" x-info="http://www.rsyslog.com"] start
Jul 19 17:15:52 xxxxx rsyslogd-2222: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ]
Jul 19 17:15:52 xxxxx rsyslogd: rsyslogd's groupid changed to 108
Jul 19 17:15:52 xxxxx rsyslogd: rsyslogd's userid changed to 104
The system is still hanging on shutdown with the fans racing.

Post Reply

Return to “Installation & Boot”