Subject: | |
From: | |
Reply To: | |
Date: | Thu, 9 Mar 2017 19:49:14 +0100 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On Mar 9, 2017, at 19:44 , 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 ...
Given that the issue starts with NetworkManager reporting "sleep requested": is there such a thing as "sleep-on-lan"?
We're not encountering this problem. Maybe because we're still not using NetworkManager...
|
|
|