linux-kernel - Re: INTEL_MEI_ME=y breaks suspend on 3.10-rc3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <51ACD600.2020805@message-id.googlemail.com>
Date:	Mon, 03 Jun 2013 19:44:32 +0200
From:	Stefan Seyfried <stefan.seyfried@...glemail.com>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: INTEL_MEI_ME=y breaks suspend on 3.10-rc3

Am 03.06.2013 19:38, schrieb Stefan Seyfried:
> Or, to be more precise: it breaks resume.
> 
> The machine seems to lock up hard after resume, then after a few seconds
> it panics (caps lock blinking).
> 
> Reproduced on ThinkPad X200s
> 
> 00:03.0 0780: 8086:2a44 (rev 07)
> Intel Corporation Mobile 4 Series Chipset MEI Controller
> 
> Debugged with "init=/bin/bash no_console_suspend", I see lots of errors
> from the mei_me driver, then finally the panic (some overflow maybe?).
> 
> Unbinding the device before suspend fixes resume.

I just noticed that I get the following message on unbinding:

$ echo 0000:00:03.0 > /sys/bus/pci/drivers/mei_me/unbind
$ dmesg|tail -2
[ 1216.830034] mei_me 0000:00:03.0: stop
[ 1216.837018] mei_me 0000:00:03.0: wait hw ready failed. status = 0x0

not sure if this is related.

Best regards,

	Stefan
-- 
Stefan Seyfried
Linux Consultant & Developer -- GPG Key: 0x731B665B

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/