I've got a laptop that has started misbehaving on suspend.

About 1 in 10 suspends the laptop fails to fully suspend.  It switches
mostly off (screen off, etc.) but some of the motherboard keeps
running.  I know some of the motherboard keeps running because:
- the wifi light remains on
- the laptop will get hot because the fans don't start

The laptop does not respond to the power button to wake up.  It's
necessary to force halt & reboot the laptop by holding the power button
down for a few seconds.

9 out of 10 times suspend works fine.

This appears to be a BIOS or kernel issue, since the last entries in
the logs are:

May 29 09:02:17 sieve-deschouwer-co-za systemd[1]: Reached target
Sleep.
May 29 09:02:17 sieve-deschouwer-co-za systemd[1]: Starting Suspend...
May 29 09:02:17 sieve-deschouwer-co-za systemd-sleep[21435]: Suspending
system...
May 29 09:02:17 sieve-deschouwer-co-za kernel: PM: suspend entry (deep)
-- Reboot --

On a successful suspend I will additionally get:

May 29 08:21:32 sieve-deschouwer-co-za kernel: PM: Syncing filesystems
... done.

This started at the same time as I upgraded to F28.  The laptop has
previously worked fine since F24 or F25, or maybe earlier.

It's happened with a few different F28 kernel patchlevels.

product: HP ProBook 450 G2 (L8A81ES#ACQ)
model name      : Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz
00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI
(rev 09)
Linux sieve-deschouwer-co-za 4.16.11-300.fc28.x86_64 #1 SMP Tue May 22
18:29:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Can anyone help me debug before I enter a bugzilla?

Berend
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/25RW7VHY4O7OOXPK44LZKLIL6WIRCTTQ/

Reply via email to