Bug 60612
| Summary: | Kernel crashes after resume from ram, takes about an hour after resume | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | John Yost (AlleyTrotter) |
| Component: | Other | Assignee: | Tomas Winkler (tomas.winkler) |
| Status: | CLOSED CODE_FIX | ||
| Severity: | blocking | CC: | aaron.lu, tomasw |
| Priority: | P1 | ||
| Hardware: | x86-64 | ||
| OS: | Linux | ||
| Kernel Version: | 3.10.0 3.10.1 3.10.2 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
my .config file
my lspci |
||
|
Description
John Yost
2013-07-23 18:37:19 UTC
The kernel crashes after a resume from "suspend to ram" in KDE. It takes about an hour after the resume, consistently The photos can be reviewed on my G+ page "AlleyTrotter" some additional info after resume my syslog fills with the following two lines Jul 23 18:45:37 linux kernel: [ 911.287719] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 1. Jul 23 18:45:37 linux kernel: [ 911.287726] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING sorry I don't have more info John Looks like problem related to MEI, I suppose MEI here means: Intel Management Engine Interface (Intel MEI) Linux driver. Can you please unload that module before S3 and see if problem solved? Aaron thanks for the response Per your question. CONFIG_INTEL_MEI=y CONFIG_INTEL_MEI_ME=y if this is what you mean by MEI, both are built onto kernel What is the reference to S3? John On Wednesday, July 24, 2013 09:20:55 PM you wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=60612
>
> --- Comment #5 from John Yost <AlleyTrotter@gmail.com> ---
> Aaron thanks for the response
> Per your question.
>
> CONFIG_INTEL_MEI=y
> CONFIG_INTEL_MEI_ME=y
>
> if this is what you mean by MEI, both are built onto kernel
> What is the reference to S3?
This driver may cause problems to happen if you use suspend/resume.
Please try to unset CONFIG_INTEL_MEI in your .config, rebuild the kernel and see if you still experience the problem as described.
S3 means suspend to ram. Please follow Rafael's suggestion in comment #6, thanks. Rafael & Aaron I have changed the kernel configuration as per your recommendation : # CONFIG_INTEL_MEI is not set # CONFIG_INTEL_MEI_ME is not set and rebuilt My system has been running successfully with several suspend and resume cycles I believe that my 'bug' has been solved Please advise if you require any additional information from me. Thanks John On Thursday, July 25, 2013 12:44:58 PM bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=60612 > > --- Comment #8 from John Yost <AlleyTrotter@gmail.com> --- > Rafael & Aaron > I have changed the kernel configuration as per your recommendation : > # CONFIG_INTEL_MEI is not set > # CONFIG_INTEL_MEI_ME is not set > and rebuilt > My system has been running successfully with several suspend and resume > cycles > I believe that my 'bug' has been solved > Please advise if you require any additional information from me. Tomas, I wonder if this is a known issue? Rafael > > Aaron I have changed the kernel configuration as per your > > recommendation : > > # CONFIG_INTEL_MEI is not set > > # CONFIG_INTEL_MEI_ME is not set > > and rebuilt > > My system has been running successfully with several suspend and > > resume cycles I believe that my 'bug' has been solved Please advise if > > you require any additional information from me. > > Tomas, I wonder if this is a known issue? Yes, I've posted few patches that should resolved that, we got mixed answer to so I continue to investigate. https://lkml.org/lkml/2013/7/24/599 Thanks Tomas Something which may be interesting I rebuilt the kernel with MEI as modules My system does indeed use the modules as they are indicated to be loaded by lsmod. The system still crashes but only after the second resume from S3. on the first resume everthing is fine. After the second resume I get the repeated messages in syslog. after rmmod mei_me and rmmod mei the system returns to normal. Hopefully this info will be of use to you thanks john One additional piece of data the crash does not occur in 3.9 Sorry to be such a bother john Problem still exists in 3.10.3 john When you apply this patch on 3.10.X does it solve the issue https://lkml.org/lkml/2013/7/17/219 Thanks Tomas Created attachment 107042 [details]
my .config file
Created attachment 107043 [details]
my lspci
when I built kernel 3.10.4 with your patch and MEI & MEI-ME as built ins the system on the second resume from S3 would not function. When trying to start any program from the KDE desktop a window would open but would be filled with alternate horizontal lines. Completely unusable. I had to use [control-alternate F2] to open a second terminal and kill kwin to get control. The only usable information in syslog was """ Jul 30 11:55:11 linux kernel: [ 603.360126] Restarting tasks ... done. Jul 30 11:57:31 linux kernel: [ 743.356520] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung """ Then I tried building the same kernel with MEI & MEI-ME built as modules. After starting the KDE desktop all seemed normal. I then tried to suspend to ram and the computer locked up. My only possible action was to do a hard reset on the system. I added my .config and my lspci in hope it will help John Just a reminder The MEI-ME flood still occurs in 3.10.7 On a better note. All my external USB devices are properly enumerated during bootup, for a while they were regularly missing some of them. John Just to stay current the bug is still there in 3.10.9 John Just a quick report. 3.10.10 fixes the mei-me flood after resume from S3 I built it back into 3.10.10 as modules (mei-me) (mei) Removed the Blacklist I can S3 suspend and resume as many times as I like and no flood. I still don't know what it is used for even though my i5 lists it under lspci John |