Red Hat Bugzilla – Bug 842444
Need staging mei module to resume from suspend sucessfully
Last modified: 2012-08-05 10:20:15 EDT
Description of problem:
For the last few 3.4 kernel versions, I've had trouble with resuming from suspend. Resuming seemed to work completely successfully, however approximately 30 seconds after resuming, my system would cold reboot. This did not happen if I hibinated the machine instead.
I'm aware my system has Intel Active Management Technology (AMT), that it has a hardware watchdog, and that the staging mei module is a driver for it. I guessed that the watchdog may have been firing, as there was no evidence of a hardware fault. I installed the staging kernel modules so that the mei module was available. After installing the mei module, my system now successfully resumes from suspend.
It would seem that in recent kernels, resuming without the mei module installed is not putting the AMT hardware back into the same state that the system boot does, and that causes the watchdog timer to go off.
Version-Release number of selected component (if applicable):
Various 3.4 kernels, including current 3.4.6-2.
Every time I suspend the machine.
Steps to Reproduce:
1. Suspend the machine
3. Wait approximately 30 seconds, and then observe the machine cold reboot
System apparently reboots for no reason.
System does not reboot.
Work around is to install the staging modules (via the meta package, so that kernel upgrades drag in the corresponding kernel staging module). The mei module is loaded automatically at boot.
looks like this just moved out of staging/, so this doesn't seem unreasonable.
That's good news. I figured I'd report it more because I didn't think I should need to have staging modules available to have reliable suspend/resume. If the mei module is going to be a non-staging module in 3.5, and that isn't too far away as a fedora kernel, then this bug could probably be closed as there is a work around.
F17 is probably going to be rebased to 3.5 later this week. We'll leave this bug open though to remember why we enabled the mei module.
MEI has been enabled in rawhide. We'll enable it in F17 when the 3.5 rebase goes in, as previously mentioned.
should have the MEI module enabled.
Upgrade to 3.5.0-2.fc17.x86_64 fixed this, so this bug can be closed. Thanks very much.