[SOLVED] laptop immediately turns on after suspend/hibernate

aksilarch · 2021-11-10 20:39:09

hi,

so after going through some of the similar problems on here and trying some of these solutions:

https://bbs.archlinux.org/viewtopic.php?id=93957 && https://bbs.archlinux.org/viewtopic.php?id=261252

i still can't get suspend/hibernate to work properly, as soon as i hit suspend or hibernate laptop immediately resumes and turns on, after the resume the desktop hangs and after a few minutes i can see the lockscreen and login again, i don't understand why this happens.

running archlinux w/ xfce desktop environement and dual booting with windows 7.

Last edited by aksilarch (2021-11-19 00:27:41)

seth · 2021-11-10 22:47:05

So what's the output of

cat /proc/acpi/wakeup

on your system?

aksilarch · 2021-11-10 23:23:54

seth wrote:

So what's the output of
cat /proc/acpi/wakeup
on your system?

Here's the output:

 cat /proc/acpi/wakeup
Device	S-state	  Status   Sysfs node
P0P2	  S4	*disabled
PEGP	  S4	*disabled
P0P1	  S4	*disabled  pci:0000:00:1e.0
EHC1	  S3	*enabled   pci:0000:00:1d.0
EHC2	  S3	*enabled   pci:0000:00:1a.0
HDEF	  S0	*disabled  pci:0000:00:1b.0
RP01	  S4	*disabled  pci:0000:00:1c.0
PXSX	  S4	*disabled  pci:0000:02:00.0
RP02	  S4	*disabled
PXSX	  S4	*disabled
RP03	  S4	*disabled  pci:0000:00:1c.2
PXSX	  S4	*disabled  pci:0000:03:00.0
		*disabled  gpio:gpiochip0
RP04	  S4	*disabled
PXSX	  S4	*disabled
RP05	  S4	*disabled
PXSX	  S4	*disabled
RP07	  S4	*disabled
PXSX	  S4	*disabled
RP08	  S4	*disabled
PXSX	  S4	*disabled
PEG3	  S4	*disabled
PEG5	  S4	*disabled
PEG6	  S4	*disabled

I did echo on:

EHC1	  S3	*enabled   pci:0000:00:1d.0
EHC2	  S3	*enabled   pci:0000:00:1a.0

tried to suspend so that I could see if it worked first then proceed with making it on each reboot, still the same problem. (I rebooted my laptop so the disabled value became enabled again)

seth · 2021-11-11 07:53:28

Windows 7 unlike 8 & 10 doesn't do this implicitly, but are you possibly actively hibernating windows?
Also what's the output of "cat /sys/power/mem_sleep"?

aksilarch · 2021-11-11 08:44:07

seth wrote:

Windows 7 unlike 8 & 10 doesn't do this implicitly, but are you possibly actively hibernating windows?

no, i never really do no

i'll post the command output once i'm home

aksilarch · 2021-11-11 16:05:56

seth wrote:

Also what's the output of "cat /sys/power/mem_sleep"?

Sorry for the late reply @seth, here's the output:

$ cat /sys/power/mem_sleep
s2idle [deep]

seth · 2021-11-11 16:11:23

No need to apologize - your problem, your schedule.
Unfortunately that doesn't indicate a problem either

as i hit suspend or hibernate

What exactly does that mean? Can you

systemctl suspend

? Can you from the multi-user.target (2nd link below)?

aksilarch · 2021-11-11 16:51:59

So,

What exactly does that mean?

It simply means that I click on the sleep or hibernate button from the xfce desktop environment.

Can you
systemctl suspend
?

This gave the same result, laptop and mouse turn off (even when nothing is plugged into the laptop), less than a second after, laptop wakes up immediately hangs a little bit then goes to lockscreen.

Can you from the multi-user.target (2nd link below)?

Same thing w/ this.

And by the way, it happens on my Windows 7 as well, the exact same problem. Could it be that the problem is from the suspend-to-ram way? Can we try to suspend another way?

Last edited by aksilarch (2021-11-11 16:58:47)

seth · 2021-11-11 16:54:10

More BIOS/UEFI than RAM - do you mind a CMOS reset?
Is there a BIOS update available for the system? (though "windows 7" sounds like "probably not")

aksilarch · 2021-11-11 16:57:16

seth wrote:

More BIOS/UEFI than RAM - do you mind a CMOS reset?
Is there a BIOS update available for the system? (though "windows 7" sounds like "probably not")

Did a CMOS reset less than an hour ago and no there is no BIOS update.

I want to point out that at a certain point I was dual booting Windows 7 with Manjaro archlinux and this problem wasn't present. I think since I switched to raw archlinux, this started to happen. I was also thinking maybe this was a clock-related problem, but my clocks are all good.

Last edited by aksilarch (2021-11-11 16:58:13)

seth · 2021-11-11 17:03:23

The only way the OS could mess up the ACPI behavior (ie. arch affecting windows et vv.) was if it's hibernating - and a CMOS reset should™ remedy even that.
So if you reset the CMOS, booted windows and still cannot successfully suspend, there's little chance that this has anything to do w/ arch, manjaro or whatever.

aksilarch · 2021-11-11 17:12:24

It's really frustrating, I don't know if I should point out this too (because it didn't really affect anything in the past), my laptop's battery life is practically dead, I'm most of the time plugged-in, when I remove the plug, laptop only survives for a few minutes before shutdown.

aksilarch · 2021-11-11 17:19:11

Oh wait, I just remembered that I'm still using a faulty keyboard (that I'll probably switch by sunday), could it be that this is what's making the system wake up? In a previous post of mine here I mention that (I didn't mark it as solved as I didn't get the spare part yet): https://bbs.archlinux.org/viewtopic.php?id=269675

Last edited by aksilarch (2021-11-11 17:20:30)

seth · 2021-11-11 20:20:49

If it's firing spurious events… sure.
Does it produce spooky input in evtest?

aksilarch · 2021-11-11 22:23:00

seth wrote:

If it's firing spurious events… sure.
Does it produce spooky input in evtest?

...

Event: time 1636668983.405542, type 1 (EV_KEY), code 57 (KEY_SPACE), value 1
Event: time 1636668983.405542, -------------- SYN_REPORT ------------
Event: time 1636668983.510690, type 4 (EV_MSC), code 4 (MSC_SCAN), value 39
Event: time 1636668983.510690, type 1 (EV_KEY), code 57 (KEY_SPACE), value 0
Event: time 1636668983.510690, -------------- SYN_REPORT ------------
Event: time 1636668983.694683, type 4 (EV_MSC), code 4 (MSC_SCAN), value 23
Event: time 1636668983.694683, type 1 (EV_KEY), code 35 (KEY_H), value 1
Event: time 1636668983.694683, -------------- SYN_REPORT ------------
Event: time 1636668983.756396, type 4 (EV_MSC), code 4 (MSC_SCAN), value 10
Event: time 1636668983.756396, type 1 (EV_KEY), code 16 (KEY_Q), value 1
Event: time 1636668983.756396, -------------- SYN_REPORT ------------
Event: time 1636668983.785458, type 4 (EV_MSC), code 4 (MSC_SCAN), value 23
Event: time 1636668983.785458, type 1 (EV_KEY), code 35 (KEY_H), value 0
Event: time 1636668983.785458, -------------- SYN_REPORT ------------
Event: time 1636668983.870486, type 4 (EV_MSC), code 4 (MSC_SCAN), value 20
Event: time 1636668983.870486, type 1 (EV_KEY), code 32 (KEY_D), value 1
Event: time 1636668983.870486, -------------- SYN_REPORT ------------
Event: time 1636668983.890045, type 4 (EV_MSC), code 4 (MSC_SCAN), value 10
Event: time 1636668983.890045, type 1 (EV_KEY), code 16 (KEY_Q), value 0
Event: time 1636668983.890045, -------------- SYN_REPORT ------------
Event: time 1636668983.969965, type 4 (EV_MSC), code 4 (MSC_SCAN), value 18
Event: time 1636668983.969965, type 1 (EV_KEY), code 24 (KEY_O), value 1
Event: time 1636668983.969965, -------------- SYN_REPORT ------------
Event: time 1636668983.984635, type 4 (EV_MSC), code 4 (MSC_SCAN), value 20
Event: time 1636668983.984635, type 1 (EV_KEY), code 32 (KEY_D), value 0
Event: time 1636668983.984635, -------------- SYN_REPORT ------------
Event: time 1636668984.035970, type 4 (EV_MSC), code 4 (MSC_SCAN), value 16
Event: time 1636668984.035970, type 1 (EV_KEY), code 22 (KEY_U), value 1
Event: time 1636668984.035970, -------------- SYN_REPORT ------------
Event: time 1636668984.125780, type 4 (EV_MSC), code 4 (MSC_SCAN), value 18
Event: time 1636668984.125780, type 1 (EV_KEY), code 24 (KEY_O), value 0
Event: time 1636668984.125780, -------------- SYN_REPORT ------------
Event: time 1636668984.141110, type 4 (EV_MSC), code 4 (MSC_SCAN), value 39
Event: time 1636668984.141110, type 1 (EV_KEY), code 57 (KEY_SPACE), value 1
Event: time 1636668984.141110, -------------- SYN_REPORT ------------
Event: time 1636668984.156782, type 4 (EV_MSC), code 4 (MSC_SCAN), value 16
Event: time 1636668984.156782, type 1 (EV_KEY), code 22 (KEY_U), value 0
Event: time 1636668984.156782, -------------- SYN_REPORT ------------
Event: time 1636668984.219326, type 4 (EV_MSC), code 4 (MSC_SCAN), value 39
Event: time 1636668984.219326, type 1 (EV_KEY), code 57 (KEY_SPACE), value 0
Event: time 1636668984.219326, -------------- SYN_REPORT ------------
Event: time 1636668984.270626, type 4 (EV_MSC), code 4 (MSC_SCAN), value 31
Event: time 1636668984.270626, type 1 (EV_KEY), code 49 (KEY_N), value 1
Event: time 1636668984.270626, -------------- SYN_REPORT ------------
Event: time 1636668984.344070, type 4 (EV_MSC), code 4 (MSC_SCAN), value 31
Event: time 1636668984.344070, type 1 (EV_KEY), code 49 (KEY_N), value 0
Event: time 1636668984.344070, -------------- SYN_REPORT ------------
Event: time 1636668984.375339, type 4 (EV_MSC), code 4 (MSC_SCAN), value 05
Event: time 1636668984.375339, type 1 (EV_KEY), code 5 (KEY_4), value 1
Event: time 1636668984.375339, -------------- SYN_REPORT ------------
Event: time 1636668984.434697, type 4 (EV_MSC), code 4 (MSC_SCAN), value 17
Event: time 1636668984.434697, type 1 (EV_KEY), code 23 (KEY_I), value 1
Event: time 1636668984.434697, -------------- SYN_REPORT ------------
Event: time 1636668984.473570, type 4 (EV_MSC), code 4 (MSC_SCAN), value 05
Event: time 1636668984.473570, type 1 (EV_KEY), code 5 (KEY_4), value 0
Event: time 1636668984.473570, -------------- SYN_REPORT ------------
Event: time 1636668984.494077, type 4 (EV_MSC), code 4 (MSC_SCAN), value 17
Event: time 1636668984.494077, type 1 (EV_KEY), code 23 (KEY_I), value 0
Event: time 1636668984.494077, -------------- SYN_REPORT ------------
Event: time 1636668984.624954, type 4 (EV_MSC), code 4 (MSC_SCAN), value 27
Event: time 1636668984.624954, type 1 (EV_KEY), code 39 (KEY_SEMICOLON), value 1
Event: time 1636668984.624954, -------------- SYN_REPORT ------------
Event: time 1636668984.673610, type 4 (EV_MSC), code 4 (MSC_SCAN), value 27
Event: time 1636668984.673610, type 1 (EV_KEY), code 39 (KEY_SEMICOLON), value 0
Event: time 1636668984.673610, -------------- SYN_REPORT ------------
Event: time 1636668984.758451, type 4 (EV_MSC), code 4 (MSC_SCAN), value 19
Event: time 1636668984.758451, type 1 (EV_KEY), code 25 (KEY_P), value 1
Event: time 1636668984.758451, -------------- SYN_REPORT ------------
Event: time 1636668984.799191, type 4 (EV_MSC), code 4 (MSC_SCAN), value 18
Event: time 1636668984.799191, type 1 (EV_KEY), code 24 (KEY_O), value 1
Event: time 1636668984.799191, -------------- SYN_REPORT ------------
Event: time 1636668984.860002, type 4 (EV_MSC), code 4 (MSC_SCAN), value 13
Event: time 1636668984.860002, type 1 (EV_KEY), code 19 (KEY_R), value 1
Event: time 1636668984.860002, -------------- SYN_REPORT ------------
Event: time 1636668984.877506, type 4 (EV_MSC), code 4 (MSC_SCAN), value 19
Event: time 1636668984.877506, type 1 (EV_KEY), code 25 (KEY_P), value 0
Event: time 1636668984.877506, -------------- SYN_REPORT ------------
Event: time 1636668984.893753, type 4 (EV_MSC), code 4 (MSC_SCAN), value 18
Event: time 1636668984.893753, type 1 (EV_KEY), code 24 (KEY_O), value 0
Event: time 1636668984.893753, -------------- SYN_REPORT ------------
Event: time 1636668984.943440, type 4 (EV_MSC), code 4 (MSC_SCAN), value 13
Event: time 1636668984.943440, type 1 (EV_KEY), code 19 (KEY_R), value 0
Event: time 1636668984.943440, -------------- SYN_REPORT ------------
Event: time 1636668985.033815, type 4 (EV_MSC), code 4 (MSC_SCAN), value 14
Event: time 1636668985.033815, type 1 (EV_KEY), code 20 (KEY_T), value 1
Event: time 1636668985.033815, -------------- SYN_REPORT ------------
Event: time 1636668985.048962, type 4 (EV_MSC), code 4 (MSC_SCAN), value 12
Event: time 1636668985.048962, type 1 (EV_KEY), code 18 (KEY_E), value 1
Event: time 1636668985.048962, -------------- SYN_REPORT ------------
Event: time 1636668985.097616, type 4 (EV_MSC), code 4 (MSC_SCAN), value 14
Event: time 1636668985.097616, type 1 (EV_KEY), code 20 (KEY_T), value 0
Event: time 1636668985.097616, -------------- SYN_REPORT ------------
Event: time 1636668985.143115, type 4 (EV_MSC), code 4 (MSC_SCAN), value 39
Event: time 1636668985.143115, type 1 (EV_KEY), code 57 (KEY_SPACE), value 1
Event: time 1636668985.143115, -------------- SYN_REPORT ------------
Event: time 1636668985.162398, type 4 (EV_MSC), code 4 (MSC_SCAN), value 12
Event: time 1636668985.162398, type 1 (EV_KEY), code 18 (KEY_E), value 0
Event: time 1636668985.162398, -------------- SYN_REPORT ------------
Event: time 1636668985.243262, type 4 (EV_MSC), code 4 (MSC_SCAN), value 39
Event: time 1636668985.243262, type 1 (EV_KEY), code 57 (KEY_SPACE), value 0
Event: time 1636668985.243262, -------------- SYN_REPORT ------------
Event: time 1636668985.254165, type 4 (EV_MSC), code 4 (MSC_SCAN), value 1e
Event: time 1636668985.254165, type 1 (EV_KEY), code 30 (KEY_A), value 1

...

EDIT: Nevermind, I executed the command, I guess no spooky input but I have a dead key. As I said, I'll try the spare part and see where to go from there.

And the list goes on until I interrupt.

Last edited by aksilarch (2021-11-11 22:48:49)

aksilarch · 2021-11-19 00:27:17

Marking this thread as solved.

Replaced the laptop's keyboard with a spare part.

Last edited by aksilarch (2021-11-19 00:28:23)

Arch Linux

#1 2021-11-10 20:39:09

[SOLVED] laptop immediately turns on after suspend/hibernate

#2 2021-11-10 22:47:05

Re: [SOLVED] laptop immediately turns on after suspend/hibernate

#3 2021-11-10 23:23:54

Re: [SOLVED] laptop immediately turns on after suspend/hibernate

#4 2021-11-11 07:53:28

Re: [SOLVED] laptop immediately turns on after suspend/hibernate

#5 2021-11-11 08:44:07

Re: [SOLVED] laptop immediately turns on after suspend/hibernate

#6 2021-11-11 16:05:56

Re: [SOLVED] laptop immediately turns on after suspend/hibernate

#7 2021-11-11 16:11:23

Re: [SOLVED] laptop immediately turns on after suspend/hibernate

#8 2021-11-11 16:51:59

Re: [SOLVED] laptop immediately turns on after suspend/hibernate

#9 2021-11-11 16:54:10

Re: [SOLVED] laptop immediately turns on after suspend/hibernate

#10 2021-11-11 16:57:16

Re: [SOLVED] laptop immediately turns on after suspend/hibernate

#11 2021-11-11 17:03:23

Re: [SOLVED] laptop immediately turns on after suspend/hibernate

#12 2021-11-11 17:12:24

Re: [SOLVED] laptop immediately turns on after suspend/hibernate

#13 2021-11-11 17:19:11

Re: [SOLVED] laptop immediately turns on after suspend/hibernate

#14 2021-11-11 20:20:49

Re: [SOLVED] laptop immediately turns on after suspend/hibernate

#15 2021-11-11 22:23:00

Re: [SOLVED] laptop immediately turns on after suspend/hibernate

#16 2021-11-19 00:27:17

Re: [SOLVED] laptop immediately turns on after suspend/hibernate

Board footer