[SOLVED] 3.10.5 kernel unstable?

AlleyTrotter · 08-29-2013, 04:54 PM

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
If anyone is still having MEI problems there is an additional fix in 3.10.11

dr.s · 09-23-2013, 05:46 PM

Marking this thread as solved (since introduction of 3.10.9).

zakame · 10-21-2013, 08:23 PM

The flood is back on 3.10.17 on Slackware 14.1 rc2, ThinkPad T420:

Code:

root@yorozuya:~# dmesg | tail
[ 1453.615498] mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
[ 1453.615500] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
[ 1453.615516] mei_me 0000:00:16.0: reset: wrong host start response
[ 1453.615518] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
[ 1453.615531] mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
[ 1453.615533] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
[ 1453.615564] mei_me 0000:00:16.0: reset: wrong host start response
[ 1453.615566] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
[ 1453.615579] mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
[ 1453.615581] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
root@yorozuya:~# uname -a
Linux yorozuya 3.10.17 #1 SMP Sun Oct 20 16:12:18 CDT 2013 x86_64 Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz GenuineIntel GNU/Linux
root@yorozuya:~# ls /var/log/packages/kernel-*
/var/log/packages/kernel-firmware-20131008git-noarch-1
/var/log/packages/kernel-generic-3.10.17-x86_64-2
/var/log/packages/kernel-headers-3.10.17-x86-2
/var/log/packages/kernel-huge-3.10.17-x86_64-2
/var/log/packages/kernel-modules-3.10.17-x86_64-2
/var/log/packages/kernel-source-3.10.17-noarch-2

Calling Master Chief...

willysr · 10-21-2013, 09:25 PM

There's no changes in mei modules in 3.10.16 and also 3.10.17 ChangeLog, however, there seems to be changes in 3.10.15 and i think this is the related commit

Quote:

commit 51d4e0771c3c69bb021d3052433e49effa6e4f65
Author: Alexander Usyskin <alexander.usyskin@intel.com>
Date: Mon Sep 2 13:29:47 2013 +0300

mei: cancel stall timers in mei_reset

commit 4a704575cc1afb3b848f096778fa9b8d7b3d5813 upstream.

Unset init_clients_timer and amthif_stall_timers
in mei_reset in order to cancel timer ticking and hence
avoid recursive reset calls.

Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

DragonWisard · 10-23-2013, 08:30 AM

Quote:

Originally Posted by zakame

The flood is back on 3.10.17 on Slackware 14.1 rc2, ThinkPad T420:
...

I'm seeing the same thing with Slackware64 14.1rc2 on a ThinkPad T520. I actually noticed this issue for the first time on 3.10.17, and this is not the first time I're resumed on this kernel. Seems like this is an intermittent issue.

I've blacklisted the mei_me module.