From: bugzilla-daemon@bugzilla.kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 211977] New: System fails to resume the second time with 5.10.17, resumes fine with 5.10.13
Date: Sat, 27 Feb 2021 13:10:36 +0000 [thread overview]
Message-ID: <bug-211977-215701@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=211977
Bug ID: 211977
Summary: System fails to resume the second time with 5.10.17,
resumes fine with 5.10.13
Product: Drivers
Version: 2.5
Kernel Version: 5.10.17
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Platform_x86
Assignee: drivers_platform_x86@kernel-bugs.osdl.org
Reporter: aros@gmx.com
Regression: No
Steps to reproduce the issue: suspend and resume.
How often does the steps listed above trigger the issue? 5.10.13 - resumes OK
as many times as you want, 5.10.17 - randomly fails to resume on the second
time, sometimes it's the third or the fourth time - anyways it some point it
fails to resume.
When it fails to resume, the system is completely dead: CAPS lock doesn't work,
the power button which normally shuts down my laptop also doesn't work.
System info:
Linux localhost 5.10.13-200.fc33.x86_64 #1 SMP Thu Feb 4 14:54:51 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
Fedora 33 x64
HP Pavilion x360 Convertible (P1F10UA#ABA)
CPU/GPU: Intel Core i5 6200U/HD Graphics 520, rev 07
Display connector: eDP
I _really_ wouldn't want to bisect the issue because it will involve building
Fedora's kernel on my quite feeble laptop.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2021-02-27 13:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 13:10 bugzilla-daemon [this message]
2021-02-27 13:11 ` [Bug 211977] System fails to resume the second time with 5.10.17, resumes fine with 5.10.13 bugzilla-daemon
2021-03-12 7:22 ` bugzilla-daemon
2021-03-15 16:04 ` bugzilla-daemon
2021-10-23 10:23 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-211977-215701@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.