Bug 1161491 - Suspend-to-ram/resume causes "Replace system board" beep code on Thinkpad S1 Yoga [NEEDINFO]
Summary: Suspend-to-ram/resume causes "Replace system board" beep code on Thinkpad S1 ...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 21
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-07 08:50 UTC by Julius B.
Modified: 2015-02-24 16:13 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-24 16:13:51 UTC
Type: Bug
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)

Description Julius B. 2014-11-07 08:50:28 UTC
Description of problem:
Resuming from suspend-to-ram doesn't work on Thinkpad S1 Yoga. Instead of resuming, the BIOS outputs four cycles of four short beeps, which is a signal for "Replace system board".

Power-cycling by long-pressing the power buttons then allows rebooting normally.

Version-Release number of selected component (if applicable):
$ uname -r
3.17.2-300.fc21.x86_64

How reproducible:
Everytime the system is suspended.

Steps to Reproduce:
1. Close lid or select Standby from GNOME's menu. 
2. Wait for Suspend
3. Resume by opening the lid or pressing any key.

Actual results:
BIOS beep code, and the LED is continuing to flash like it's suspended.

Expected results:
Normal resume

Additional info:
This didn't happen with a F21 nightly ISO from ~mid October 2014.

Comment 1 Julius B. 2014-11-07 22:27:34 UTC
I just did further test to see when it works and when it doesn't.

I freshly installed from the following F21 live images:

Fedora-Live-Workstation-x86_64-21-20141016.iso
Fedora-Live-Workstation-x86_64-21-20141020.iso
Fedora-Live-Workstation-x86_64-21-20141027.iso
Fedora-Live-Workstation-x86_64-21_Alpha-1.iso
Fedora-Live-Workstation-x86_64-21_Beta-4.iso

None of them worked.

I then freshly installed Fedora 20 and tested some kernels:

3.17.2-300.fc21 on updated F20                : doesn't work
3.17.0-1.vanilla.mainline.knurd.1.fc20.x86_64 : doesn't work
3.17.2-200.vanilla.stable.knurd.1.fc20.x86_64 : works

I then tested vanilla kernels on a new F21 installation, with the following results:

3.17.1-302.fc21.x86_64                        : doesn't work
3.17.2-300.fc21.x86_64                        : doesn't work
3.17.0-1.vanilla.mainline.knurd.1.fc21.x86_64 : doesn't work
3.17.2-300.vanilla.stable.knurd.1.fc21.x86_64 : doesn't work

I don't exactly know what to do with this information, especially since 3.17.1 and 3.17.2-300 don't seem to work, but 3.17.2-200.vanilla.stable does.

Comment 2 Valent Turkovic 2014-11-18 19:38:09 UTC
I have gotten my Lenovo 440s to suspend and resume without issues just by choosing debugging kernel from Fedora 21 Beta GRUB menu.

With regular kernel I get suspend to work but resume fails.

Here is a link to my bug report if it helps with additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1162793

Comment 3 Valent Turkovic 2014-11-18 20:00:50 UTC
I have found the reason why Fedora 21 doesn't resume by default on my Laptop, check out my bugreport to see details.

But try installing kernel-modules-extra package and see if that helps. If it does then your laptop is also missing TPM modules and this is the reason why if fails to resume.

Comment 4 Justin M. Forbes 2015-01-27 15:01:13 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 21 kernel bugs.

Fedora 21 has now been rebased to 3.18.3-201.fc21.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 5 Fedora Kernel Team 2015-02-24 16:13:51 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


Note You need to log in before you can comment on or make changes to this bug.