Are you sure you got the latest Slackware-current updates? dunno if the root cause was fixed but the mei/mei-me config entries have been disabled since the Aug. 21 Slackware update (3.10.9 kernel) so there's no mei/mei-me modules to blacklist.
http://www.linuxquestions.org/questi...le-4175472734/

To add upon that, one thing to check is what is blacklisted in your slackpkg...

Maybe you didn't have kernel upgrade...

I see from the changelog that Pat put these things in yesterday, which I did not get:

However, I have everything before that EXCEPT for the most recent gcc and glibc packages, because when I upgraded those, it broke my multilib and I reverted. I know Eric has the new ones on his site now, but I have not had time to take care of that yet.

Nope, I upgrade my kernels to whatever Pat puts in -current

I just checked, and the absolute only thing I have blacklisted is aaa_elflibs. To be honest I'm not sure how that happened, though, because I did have a few more things blacklisted (like Alien's multilib packages and adobe-reader), but they mysteriously disappeared. A few days ago before the last upgrade I got a message from Slackpkg saying it was the first time I had run it, so I'd better choose a mirror. I though that was strange, but I did not try to see if anything else was wrong.

So what does that mean?

That means that slackpkg itself was upgraded. Probably, when asked what to do with the .new files (e.g. /etc/slackpkg/blacklist and /etc/slackpkg/mirrors) you chose to overwrite the old ones with the new ones, thus you lost your previous settings.

1 members found this post helpful.

Thank you, that explains it then. I did overwrite those files. I just didn't know what I was overwriting.

Anyway, about what dr.s and NoStressHQ are saying, if the mei/mei-me modules are gone, then I am not sure I understand what is happening here or what to do. I have kernel 3.10.12, and the errors in my syslog seem to be coming from mei-me. Is this not correct? What should I do then?

P.S. I have already blacklisted the kernel modules (even if it will not help), but before I did, I waited until I suspended again for a long time and then resumed. I was still monitoring /var/log/syslog with "tail -f". A few minutes later, I heard my laptop fan start running at full speed, and I looked at the terminal to see, and sure enough, hundreds of errors lines just like the ones I posted were flooding out. The other day I posted a thread about thinking I needed to downgrade my kernel because my laptop fan was running all the time after suspend, but I didn't know why. I guess this is what was causing it. It's good to know that, at least!

Just as an update, blacklisting the mei-me modules did the trick. So I checked, and the Slackware64-current kernel .config says:

I don't know what kernel you were looking at above or if Pat changed it back maybe, but the way it is now I think you still need to blacklist them. Or I do anyway.

Also, I have not been able to find a particularly good explanation of what the me module is, beyond the fact that it's an Intel driver for some sort of "coprocessor," but I have noticed that blacklisting it along with mei (which is the me interface, whatever me is) has the consequence of slowing down my network reconnection via Network Manager after resume, as well as causing intermittent disconnects. Small price to pay if you have the flood problem, though.

But I hope the kernel guys fix it soon.

Thanks to everyone who helped--you guys are great. I'm happy to be a slacker.