Bug 1036810
Summary: | suspend fails intermittently: wakes immediately | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | dhardy <redhat> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 20 | CC: | gansalmon, hugh, itamar, jaskerx, jonathan, kernel-maint, madhu.chinakonda |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-02-25 22:56:19 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
dhardy
2013-12-02 16:27:42 UTC
It seems that the laptop suspends fine when told to do so via another method (e.g. KDE menu). But I see this in journalctl, could this be the problem? New laptop :-( Dec 06 11:04:52 yoga.dhardy kernel: mei_me 0000:00:16.0: suspend Dec 06 11:04:52 yoga.dhardy mcelog[647]: Hardware event. This is not a software error. Dec 06 11:04:52 yoga.dhardy mcelog[647]: MCE 0 Dec 06 11:04:52 yoga.dhardy mcelog[647]: CPU 0 BANK 6 Dec 06 11:04:52 yoga.dhardy mcelog[647]: MISC f8a0000086 ADDR ffb03840 Dec 06 11:04:52 yoga.dhardy mcelog[647]: TIME 1386324290 Fri Dec 6 11:04:50 2013 Dec 06 11:04:52 yoga.dhardy mcelog[647]: MCG status: Dec 06 11:04:52 yoga.dhardy mcelog[647]: MCi status: Dec 06 11:04:52 yoga.dhardy mcelog[647]: Uncorrected error Dec 06 11:04:52 yoga.dhardy mcelog[647]: MCi_MISC register valid Dec 06 11:04:52 yoga.dhardy mcelog[647]: MCi_ADDR register valid Dec 06 11:04:52 yoga.dhardy mcelog[647]: Processor context corrupt Dec 06 11:04:52 yoga.dhardy mcelog[647]: MCA: corrected filtering (some unreported errors in same region) Dec 06 11:04:52 yoga.dhardy mcelog[647]: Generic CACHE Level-2 Generic Error Dec 06 11:04:52 yoga.dhardy mcelog[647]: STATUS ae0000000040110a MCGSTATUS 0 Dec 06 11:04:52 yoga.dhardy mcelog[647]: MCGCAP c07 APICID 0 SOCKETID 0 Dec 06 11:04:52 yoga.dhardy mcelog[647]: CPUID Vendor Intel Family 6 Model 69 I can attest to this bug as well am using: Yoga 2 Pro (i5, 8gb) Kde 4.11.4 Kernel 3.12.3 I am not using fedora/red hat though just wanted to post a link to the kde forums: http://forum.kde.org/viewtopic.php?f=225&t=118745 My experience with this issue. Might help, might not. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is 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 20 kernel bugs. Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update 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. note: with the Yoga 2 pro, it seems that it is important to blacklist the ideapad_laptop module. Apparently the Y2p looks like an Ideapad to that module but it then does some inappropriate things. My Y2p sleeps well with current Fedora 20 (I have blacklisted that module). The 3.13.4-200.fc20 kernel seems to fix this issue (3.12.3-1.fc21 still has it). Redelmeier: I also have ideapad_laptop disabled. Even with 3.12.4 it breaks wifi. dhardy: OK. My Yoga 2 pro had a WiFi firmware problem that https://admin.fedoraproject.org/updates/kernel-3.13.5-200.fc20 fixes. See https://bugzilla.redhat.com/show_bug.cgi?id=1069403 Hugh: Awesome, even if for me this mostly just means less log noise. The linked bug doesn't mention ideapad_laptop — is that related? dhardy: I haven't heard of any linkage. (I'm just a user and a googler.) The new kernel made a screen problem go away for me. And made booting faster. I don't know why. My superstitious explanation is that firmware crashes disrupted booting. ABRT told me I had unreportable kernel crashes, with hardware errors (Machine Check Error). Not very comforting! I think that my previous kernel was 3.13.3-201.fc20.x86_64 based on the second choice in the grub menu. It was the latest version in Fedora Updates a couple of days ago. Could be the case. I haven't really paid attention to boot time, but I definitely have had MCE errors in my log. dhardy: the MCE errors are concerning. It is useful to know that I'm not alone. I've created a new bz about this. Please report your observations. https://bugzilla.redhat.com/show_bug.cgi?id=1082211 |