Fedora Linux Support Community & Resources Center
  #1  
Old 21st April 2017, 02:38 AM
tempest766 Offline
Registered User
 
Join Date: Jul 2010
Location: western PA
Posts: 71
linuxfedorafirefox
glitch appears about when systemd was forced on us

I turn off my workstation and go away for at least 24 hours.

I come back and boot it up (to runlevel 3), then log in and manually start X11 using a very minimalist window manager (FVWM2).

When uptime hits 15 minutes the system locks up and requires a hard reset. Often times widgets on screen are continuing to update but there is no input capability (mouse and keyboard are dead).

If I boot the workstation after it being off for more than 24 hours, but do not immediately fire up X11 (wait more than 15 minutes before starting X11) then the system is fine and I can then run X11 and keep the system up for months at a time.

and it's not like this is something I can easily design a test harness for since the behaviour only shows up when at least 24 hours of downtime has passed.

dual E5620 Xeon CPUS
24GB RAM
much software RAID-5 via motherboard and add-on SATA controller
Fedora 24
kernel 4.8.11-200
NVIDIA GPU driver 375.39 (happens with all available NVIDIA drivers)

Having been at the UNIX game for over 30 years my sensibilities tell me to blame systemd. What might systemd be doing 15 minutes after a cold boot when the system hasn't been powered for at least a day, that it wouldn't do if the system was kept running nearly constantly?
Reply With Quote
  #2  
Old 21st April 2017, 05:01 AM
tempest766 Offline
Registered User
 
Join Date: Jul 2010
Location: western PA
Posts: 71
linuxfedorafirefox
Re: glitch appears about when systemd was forced on us

Yep. It's the fault of systemd. 15 minutes after reboot it kicks off systemd-tmpfiles-clean and that is somehow destroying the volatile X11 files/sockets/pipes that my initial "startx /bin/fvwm2" created.

No idea how to fix it though, without fully disabling the unit, and probably breaking a ton of other stuff being held together with spit and bubblegum.
Reply With Quote
  #3  
Old 21st April 2017, 09:17 PM
bobx001 Offline
Registered User
 
Join Date: Dec 2012
Location: santa barbara, CA
Posts: 388
linuxfedorafirefox
Re: glitch appears about when systemd was forced on us

Very interesting, I will investigate.

I either have comps always on, or use hibernate for my home laptops.

But I will test your way and see what's going on.
Reply With Quote
  #4  
Old 21st April 2017, 10:43 PM
dd_wizard Offline
Registered User
 
Join Date: Sep 2009
Posts: 1,996
linuxfedorafirefox
Re: glitch appears about when systemd was forced on us

Have you changed the contents of /usr/lib/tmpfiles.d/x11.conf, or created /etc/tmpfiles.d/x11.conf? That controls what happens to the x11 lock files in /tmp. Here's mine. The ! is important in the last line; it specifies to do the unlink only during boot.
Code:
$ cat /usr/lib/tmpfiles.d/x11.conf
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

# See tmpfiles.d(5) for details

# Make sure these are created by default so that nobody else can
d /tmp/.X11-unix 1777 root root 10d
d /tmp/.ICE-unix 1777 root root 10d
d /tmp/.XIM-unix 1777 root root 10d
d /tmp/.font-unix 1777 root root 10d
d /tmp/.Test-unix 1777 root root 10d

# Unlink the X11 lock files
r! /tmp/.X[0-9]*-lock
From the tmpfiiles.d man page:
Code:
       For example:

           # Make sure these are created by default so that nobody else can
                 d /tmp/.X11-unix 1777 root root 10d

                 # Unlink the X11 lock files
                 r! /tmp/.X[0-9]*-lock

       The second line in contrast to the first one would break a running system, and will
       only be executed with --boot.
dd_wizard
Reply With Quote
  #5  
Old 23rd April 2017, 03:12 AM
tempest766 Offline
Registered User
 
Join Date: Jul 2010
Location: western PA
Posts: 71
linuxfedorafirefox
Re: glitch appears about when systemd was forced on us

have not changed any of the systemd config files on any of my machines other than through the "systemctl [enable|disable]" command.

Thx!
Reply With Quote
Reply

Tags
appears, crash, forced, glitch, systemd, x11

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Is systemd x-systemd.device-timeout broken? matth45 Hardware & Laptops 3 12th July 2016 03:53 AM
Why is systemd set to retain such old /var/tmp/systemd-* dirs? marko Using Fedora 7 29th June 2014 06:33 PM
systemd user service manager support (systemd --user) survient Using Fedora 2 5th December 2013 03:52 PM
systemd and systemd-ask-password cheerio158 Installation, Upgrades and Live Media 0 23rd September 2012 03:03 PM
forced to run headless... Zigzagcom Servers & Networking 5 3rd November 2005 08:42 PM


Current GMT-time: 20:32 (Sunday, 28-05-2017)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat