Ubuntu
linux package

mei_me resets spamming dmesg

Bug #1196155 reported by Herb McNew on 2013-06-29

This bug affects 13 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Fix Released	Medium	Andy Whitcroft

Bug Description

As you can see from the dmesg attached I'm getting the following every 5-10 seconds:
[11332.456035] mei_me 0000:00:03.0: reset: connect/disconnect timeout.
[11332.456044] mei_me 0000:00:03.0: unexpected reset: dev_state = RESETTING

This was happening with raring but I blacklisted the mei module. With saucy it seems mei is included directly and is no longer loaded as a module.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.10.0-1-generic 3.10.0-1.8
ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7
Uname: Linux 3.10.0-1-generic x86_64
ApportVersion: 2.10.2-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: herb 2330 F.... pulseaudio
/dev/snd/controlC0: herb 2330 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Sat Jun 29 18:57:30 2013
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=878dad1b-8d2b-4879-8dea-862befaf67b9
InstallationDate: Installed on 2013-01-23 (157 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
IwConfig:
eth0 no wireless extensions.

lo no wireless extensions.
MachineType: Hewlett-Packard HP Compaq dc7700p Convertible Minitower
MarkForUpload: True
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-1-generic root=UUID=bcaf6352-17f6-4fa2-af31-127c04f60e6e ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.10.0-1-generic N/A
linux-backports-modules-3.10.0-1-generic N/A
linux-firmware 1.110
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to saucy on 2013-06-29 (0 days ago)
dmi.bios.date: 08/14/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786E1 v03.03
dmi.board.name: 0A58h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: 2UA741121G
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v03.03:bd08/14/2007:svnHewlett-Packard:pnHPCompaqdc7700pConvertibleMinitower:pvr:rvnHewlett-Packard:rn0A58h:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP Compaq dc7700p Convertible Minitower
dmi.sys.vendor: Hewlett-Packard

Tags:

Revision history for this message

Herb McNew (herb) wrote on 2013-06-29:

AlsaInfo.txt Edit (32.3 KiB, text/plain; charset="utf-8")
BootDmesg.txt Edit (55.5 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (164.9 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.8 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (9.9 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (634 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.3 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (20.6 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (135.4 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (283.5 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (633.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Brad Figg (brad-figg) wrote on 2013-06-29: Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2013-07-01:

I confirm that the option is no longer a module, but built into the kernel for Saucy:
config.common.ubuntu:CONFIG_INTEL_MEI=y
config.common.ubuntu:CONFIG_INTEL_MEI_ME=y

Changed in linux (Ubuntu):
importance:	Undecided → Medium
status:	Confirmed → Triaged

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2013-07-01:

This is also causing suspend/resume issues, which are being discussed upstream:
https://lkml.org/lkml/2013/6/29/98

Revision history for this message

Andy Whitcroft (apw) wrote on 2013-07-02:

This seems to have been picked up when turning on the INTEL_MEI_ME option on during the rebase to v3.10-rc2, it does not appear to have been a deliberate act as such. For now I will shove it back to and M and see if anyone notices.

Andy Whitcroft (apw) on 2013-07-02

Changed in linux (Ubuntu):
assignee:	nobody → Andy Whitcroft (apw)
status:	Triaged → Fix Committed

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-07-06:

This bug was fixed in the package linux - 3.10.0-2.10

---------------
linux (3.10.0-2.10) saucy; urgency=low

[ Andy Whitcroft ]

  * [Config] CONFIG_INTEL_MEI*=m
    - LP: #1196155
  * [Config] CONFIG_DEBUG_INFO=y

[ Stephen Warren ]

* [Config] fix Calxeda xgmac module filename

[ Upstream Kernel Changes ]

  * Revert "serial: 8250_pci: add support for another kind of NetMos
    Technology PCI 9835 Multi-I/O Controller"
    - LP: #1190967
  * mfd: lpc_ich: Add support for Intel Avoton SoC
    - LP: #1196658
-- Andy Whitcroft <email address hidden> Fri, 05 Jul 2013 18:08:02 +0100

Changed in linux (Ubuntu):
status:	Fix Committed → Fix Released

Revision history for this message

Rayan (sudo-rayan) wrote on 2013-11-14:

how can I apply the fix on my machine? please help

Revision history for this message

Christian S. (christian-stein2) wrote on 2013-11-15:

Its happen again

[ 111.128181] mei_me 0000:00:03.0: unexpected reset: dev_state = RESETTING
[ 117.140090] mei_me 0000:00:03.0: reset: connect/disconnect timeout.
[ 117.140111] mei_me 0000:00:03.0: unexpected reset: dev_state = RESETTING
[ 123.152100] mei_me 0000:00:03.0: reset: connect/disconnect timeout.
[ 123.152119] mei_me 0000:00:03.0: unexpected reset: dev_state = RESETTING
christian@t61-ubuntu:~$ uname -a
Linux t61-ubuntu 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message

Kees Cook (kees) wrote on 2013-12-15:

"sudo rmmod mei_me mei" should stop the messages. Usually means AMT has been disabled in the BIOS.

Revision history for this message

Marko Pynnönen (marko-pynnonen) wrote on 2014-02-05:

#10

I got rid of the startup error message by blacklisting the mei_me driver. To do that, you can add the following two lines at the end of the blacklist.conf file located in /etc/modprobe.d. Here are the steps just in case:

1. Open terminal
2. Type sudo gedit /etc/modprobe.d/blacklist.conf
3. Scroll to the bottom of the file and add the following two lines:
# Intel VPRO remote access technology driver
blacklist mei_me

4. Save the file
5. Restart the computer
--> Now, you should not get the error messages anymore on startup of the computer.

Revision history for this message

Alvin (alvind) wrote on 2014-04-22:

#11

What about Trusty?

mei_me 0000:00:03.0: timer: connect/disconnect timeout.
mei_me 0000:00:03.0: unexpected reset: dev_state = ENABLED

Revision history for this message

Cedric Bhihe (cedric-bhihe) wrote on 2014-06-19:

#12

Yes, what about Trusty ?
I am affected by this as well on a Intel T9300 Core Duo with :
Linux XXX 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
As you can see my install is recent.

Revision history for this message

Tim Gardner (timg-tpi) wrote on 2014-06-20:

#13

The quickest way to stop the log spamming is to blacklist the drivers since your platform obviously doesn't need them. I have a server with the same problem.

echo "blacklist mei" | sudo tee -a /etc/modprobe.d/mei.conf
echo "blacklist mei_me" | sudo tee -a /etc/modprobe.d/mei.conf

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntulinux package

mei_me resets spamming dmesg

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package