[nmglug] Hibernate failure + Buggy BIOS?, etc.

[Tom Ashcraft]

On 3/12/22 12:44, Akkana Peck wrote:
> Ted Pomeroy writes:
>> My routine is to suspend during the day, if I go out or take an hour off
>> for non-computer work. Over night I switch off after saving work and
>> closing all apps.
I do the same thing, though occasionally I leave it sleeping
> overnight, if I'm in the middle of something complicated with a
> lot of windows open, or if I just never got back to the machine
> after suspending it.
>
> With some machines, though, you have to keep an eye on them. My
> current Lenovo tends to randomly wake up a minute or two after I
> suspend it. If I suspend again immediately, usually it'll stay
> asleep the second time. My previous Lenovo didn't do that, but
> it would randomly come out of sleep hours later, so I'd go out for
> hours, come back and discover it up and running instead of sleeping.
>
> I've never had problems with non-Lenovo machines staying asleep,
> so I think Lenovo might just have something buggy in their BIOS
> that makes them wake up when they shouldn't. (Wake on LAN is
> disabled in the BIOS, and it happens when the laptop isn't even
> connected to a LAN, so it's not that.)

Ditto all above except that in addition to encountering this behavior 
with Debian 11 Xfce installed on a Toshiba Satellite L505 laptop (maybe 
twelve years old?), I first observed it on the same machine during my 
first experiences of Linux on a dual-boot installation of Linux Mint 
17.  But mostly I'd just wake up in the middle of the night to hear the 
fan running and wonder why it would need to be on, i.e. the screen would 
not light up, though with Debian 11 Xfce it seems most often that the 
screen lights up too.  Also, one of the funny things about Debian 11 
Xfce going into 'suspend' is that the computer often seems to fall into 
and be stuck in a state where the fan keeps running.  Which is a clear 
indicator that something is wrong with 'suspend' again...

I expect that Wesley Robbins 12:46 pm post to "Edit 
|/etc/default/grub| and add |mem_sleep_default=deep| to the default, 
i.e.: |GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" 
"|may turn out to be the most productive suggestion for me to try out 
the next time I use that machine.

However, as I remain a perennial Linux naif and am also prone to enjoy 
the occasional frisson of some instance of poorly-founded or 
anti-establishment paranoia, I sometimes wonder about possibilities like 
bots, spyware, criminal hackers, the NSO Group, NSA, FBI, local police, 
crypto miners, etc.  The last time I mentioned that someone mentioned 
the possibility of a cron job. As I remember, I figured out how to check 
and it didn't pan out. Any thoughts along those lines?

> ________________________________________
> nmglug mailing list
> nmglug at lists.nmglug.org
> http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nmglug.org/pipermail/nmglug-nmglug.org/attachments/20220312/200e8ea2/attachment.html>