SCIENTIFIC-LINUX-USERS Archives

March 2017

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Mark Stodola <[log in to unmask]>
Reply To:
Mark Stodola <[log in to unmask]>
Date:
Thu, 9 Mar 2017 13:32:39 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
On 03/09/2017 12:44 PM, Andrew C Aitchison wrote:
> On Thu, 9 Mar 2017, Konstantin Olchanski wrote:
>
>> Hi, there. I wonder if anybody else is seeing the same problem with el7:
>>
>> The symptoms are: no ping, dead video, dead keyboard. After power cycle,
>> syslog shows that the system has attempted to go into sleep or suspend
>> or whatever they call it.
>>
>> This is very strange, usualy a system will go into suspend mode when you
>> close the laptop lid, but these are not laptops. They are normal desktop
>> machines (and at least in one case, there is no local user to blame for
>> pressing the "sleep" button).
>>
>> So what's in the syslog:
>> - normal activity (systemd spam)
>> - network manager reports "sleep requested"
>> - some kind of nm_dispatcher activity
>> - systemd reaches sleep and suspend targets.
>> - continues spewing sundry messages, never recovers (never goes into
>> actual sleep).
>>
>> The machine is effectively dead after network manager put the network
>> interfaces to sleep.
>
> Can the machine be made to respond to wake-on-lan ?
> If so, setting that up *might* reduce the pain when this happens again ...

What does hostnamectl report for chassis type?  I haven't had a sleep 
issue, but I do find desktop boards get set to laptop incorrectly.  I 
tend to force this to server in my kickstarts.

ATOM RSS1 RSS2