LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 08-16-2013, 03:14 PM   #31
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 836

Rep: Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620

Quote:
Originally Posted by zakame View Post
Kernels 3.10.5 to 3.10.7 are not resuming from suspend on my personal ThinkPad X200, while it runs fine on my work's T420. Seems to be an issue on Core 2 Duo ThinkPads: https://bugzilla.redhat.com/show_bug.cgi?id=989373
Can you try blacklisting mei and mei-me and see if that helps? If it does, we might blacklist those two modules by default.
 
Old 08-16-2013, 05:15 PM   #32
dr.s
Member
 
Registered: Feb 2010
Distribution: Slackware64
Posts: 126

Original Poster
Rep: Reputation: 19
Quote:
Originally Posted by volkerdi View Post
Can you try blacklisting mei and mei-me and see if that helps? If it does, we might blacklist those two modules by default.
Blacklisting mei-me fixed the crashes on 3.10.5

As of yesterday, I upgraded to 3.10.7 and re-enabled mei-me. So far this is going well. I checked syslog and it's clean, the mei-me errors that flooded syslog with millions of lines on 3.10.5 are gone now.

Anyone knows the purpose of mei/mei-me modules? this desktop worked very smoothly without them
 
Old 08-16-2013, 05:45 PM   #33
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,336

Rep: Reputation: 376Reputation: 376Reputation: 376Reputation: 376
Quote:
Originally Posted by dr.s View Post
Anyone knows the purpose of mei/mei-me modules? this desktop worked very smoothly without them
Another driver from Intel: http://lwn.net/Articles/440292/
 
1 members found this post helpful.
Old 08-17-2013, 12:35 PM   #34
AlleyTrotter
Member
 
Registered: Jun 2002
Location: Coal Township PA
Distribution: Slackware64-14.1 (3.14.0) UEFI enabled
Posts: 344

Rep: Reputation: 71
Still Here

Quote:
Originally Posted by volkerdi View Post
Can you try blacklisting mei and mei-me and see if that helps? If it does, we might blacklist those two modules by default.
On a fresh install of current (Sat Aug 17 03:30:00 UTC 2013) immediately upon resume from S3 I still get the mei-me flood to /var/log/syslog.
Blacklisting the two modules eliminates the problem, however from lspci my machine has the chip for mei
Code:
00:16.0 Communication controller: Intel Corporation Panther Point MEI Controller #1 (rev 04)
On a brighter note, Now current with 3.10.7 properly enumerates all my external USB devices in dmesg
I will be testing current further as time goes by.
John
 
Old 08-19-2013, 09:06 PM   #35
dr.s
Member
 
Registered: Feb 2010
Distribution: Slackware64
Posts: 126

Original Poster
Rep: Reputation: 19
Clean syslog and no crashes so far, marking as solved.
 
Old 08-20-2013, 04:36 AM   #36
_ZeD_
LQ Newbie
 
Registered: May 2012
Distribution: Slackware
Posts: 18

Rep: Reputation: 1
unfortunately I encountered a crash with the 3.10.7 kernel
 
Old 08-20-2013, 06:13 AM   #37
dunric
Member
 
Registered: Jul 2004
Distribution: Slackware
Posts: 411

Rep: Reputation: 39
I can also confirm kernel crash even with Linux 3.10.7 . Sometimes attempt to suspend/hibernate only kills X server followed by an immediate resume without any message in syslog that would describe the issue.
 
Old 08-20-2013, 06:28 PM   #38
dr.s
Member
 
Registered: Feb 2010
Distribution: Slackware64
Posts: 126

Original Poster
Rep: Reputation: 19
I guess I posted too soon, just had the first 3.10.7 crash on this machine with the now familiar mei-me message flood in syslog, blacklisting this module again.

Last edited by dr.s; 08-20-2013 at 06:30 PM.
 
Old 08-20-2013, 06:50 PM   #39
GazL
Senior Member
 
Registered: May 2008
Posts: 3,231

Rep: Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828
I see greg has just put out a 3.10.8 rapidly followed by a 3.10.9.
 
Old 08-20-2013, 09:11 PM   #40
AlleyTrotter
Member
 
Registered: Jun 2002
Location: Coal Township PA
Distribution: Slackware64-14.1 (3.14.0) UEFI enabled
Posts: 344

Rep: Reputation: 71
Quote:
Originally Posted by GazL View Post
I see greg has just put out a 3.10.8 rapidly followed by a 3.10.9.
A quick grep -i mei-me shows nothing in either changelog.
So my guess is I'm still waiting for a fix. Fortunately PV's recommendation to blacklist the mei-me module is a good temporary fix. I will still give the 3.10.9 a try.
john
 
Old 08-20-2013, 09:30 PM   #41
zakame
Member
 
Registered: Apr 2012
Distribution: Debian, Ubuntu, Slackware
Posts: 116

Rep: Reputation: 42
Quote:
Originally Posted by volkerdi View Post
Can you try blacklisting mei and mei-me and see if that helps? If it does, we might blacklist those two modules by default.
Hi volkerdi, sorry for the late response. Just tried blacklisting the modules and even modprobe -r them immediately to do a quick suspend, it seems to work as I'm typing this response upon resume (actually I did this a couple of times to confirm) Thanks!
 
Old 08-21-2013, 04:04 AM   #42
GazL
Senior Member
 
Registered: May 2008
Posts: 3,231

Rep: Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828
Quote:
Originally Posted by AlleyTrotter View Post
A quick grep -i mei-me shows nothing in either changelog.
So my guess is I'm still waiting for a fix. Fortunately PV's recommendation to blacklist the mei-me module is a good temporary fix. I will still give the 3.10.9 a try.
john
Yep. I guess it all depends on whether the mei--me code is the primary cause of the fault, or just a secondary victim of another bug elsewhere in the kernel. Having had a quick read through the Changelog there look to be a number of important fixes in this batch, so worth having all the same.
 
Old 08-21-2013, 06:26 PM   #43
AlleyTrotter
Member
 
Registered: Jun 2002
Location: Coal Township PA
Distribution: Slackware64-14.1 (3.14.0) UEFI enabled
Posts: 344

Rep: Reputation: 71
Yes I gave 3.10.9 a try.
Hope springs eternal.
But no cigar.
Failed after first resume from S3 with the mei-me flood
john
 
Old 08-21-2013, 08:37 PM   #44
dr.s
Member
 
Registered: Feb 2010
Distribution: Slackware64
Posts: 126

Original Poster
Rep: Reputation: 19
Looks like mei/mei-me are gone as of the latest slackware-current updates (Aug. 21 --> 3.10.9)
 
Old 08-22-2013, 08:34 PM   #45
AlleyTrotter
Member
 
Registered: Jun 2002
Location: Coal Township PA
Distribution: Slackware64-14.1 (3.14.0) UEFI enabled
Posts: 344

Rep: Reputation: 71
Quote:
Originally Posted by dr.s View Post
Looks like mei/mei-me are gone as of the latest slackware-current updates (Aug. 21 --> 3.10.9)
Your right it is gone for Slackware.
The bug is not fixed. What PV has done is no longer build the module in his .config i.e.
Code:
# CONFIG_INTEL_MEI is not set
# CONFIG_INTEL_MEI_ME is not set
which works for me as I already had it blacklisted. For now probably the best workaround unless the module is needed for something. I still don't know what it is used for even though my i5 lists it under lspci
john
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
ath9k driver unstable in kernel 2.6.38? MrCode Arch 0 04-13-2011 06:36 AM
Any later than kernel 2.6.23 stalls on boot, also quite unstable... doug2e Fedora 1 07-12-2008 05:24 PM
is ubuntu unstable less unstable than debian unstable? lefty.crupps Ubuntu 9 10-14-2005 01:38 PM
compiling kernel 2.5.70 (experimental-unstable) kazuni Slackware 12 07-11-2003 07:27 AM
unstable kernel? eagle0669 Linux - Newbie 7 08-09-2001 08:17 AM


All times are GMT -5. The time now is 02:16 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration