2

The following lines are getting displayed while Ubuntu is booting.

[   27.981086] mei_me 0000:00:16.0: irq 60 for MSI/MSI-X
[   27.985007] mei_me 0000:00:16.0: version message write failed: ret = -5
[   27.985071] mei_me 0000:00:16.0: hbm_start failed ret = -5
[   27.985123] mei_me 0000:00:16.0: reset failed
[   27.985166] mei_me 0000:00:16.0: link layer initialization failed.
[   27.985224] mei_me 0000:00:16.0: init hw failure.
[   27.987404] mei_me 0000:00:16.0: initialization failed.

I've been using it for around 4-5 months now and this is the first time I got this message. I'm able to log in and everything seems to be working fine. But this error message is bugging me.

Is there a way to fix this.

I'm using Ubuntu 14.04 LTS.

Thanks in advance.


UPDATE #1

Added blacklist mei to /etc/modprobe.d/blacklist.conf but the error is still being displayed on boot.

3

Added blacklist mei_me line to /etc/modprobe.d/blacklist.conf.

The error message is not showing while booting. The speed of booting hasn't increased; it is taking the same amount of time as before(when the error message was being shown).

| improve this answer | |
0

The module mei is the driver for Intel(R) Management Engine Interface.

Some examples of Intel AMT usage are:

  • Monitoring hardware state and platform components
  • Remote power off/on (useful for green computing or overnight IT maintenance)
  • OS updates
  • Storage of useful platform information such as software assets
  • Built-in hardware KVM
  • Selective network isolation of Ethernet and IP protocol flows based on policies set by a remote management console
  • IDE device redirection from remote management console

To get rid of the error just blacklist the module with

sudo echo  "blacklist mei_me" >> /etc/modprobe.d/blacklist.conf

source and more info

| improve this answer | |
  • It's still showing the error. – UrsinusTheStrong May 1 '15 at 8:14
  • check the edit. /etc/modprobe.d/blacklist.conf – Maythux May 1 '15 at 8:16
  • Checked. 'blacklist mei' is there. – UrsinusTheStrong May 1 '15 at 8:17
  • 1
    Actually the module name you need to blacklist is mei_me not mei. – Big McLargeHuge May 3 '15 at 18:57
  • 1
    Using > redirection is a REALLY bad idea. You're overwriting everything in /etc/modprobe.d/blacklist.conf and then writing that single line. Like the other commenter noted, this can have disastrous effects. – Seth May 7 '15 at 0:00

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.