Hi Tomas, executive summary: it is not fixed in 3.10rc6
Am 03.06.2013 20:09, schrieb Tomas Winkler: >>> 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. >> > Thanks for the report I'm looking into it. I looked at the git log of drivers/misc/mei and it looked promising. However, it still does not work, commit 42f132febff3b7b42c6c9dbfc151f29233be3132 does not seem to help enough on my hardware. Still just unbinding and rebinding with echo 0000:00:03.0 > /sys/bus/pci/drivers/mei_me/unbind echo 0000:00:03.0 > /sys/bus/pci/drivers/mei_me/bind triggers lots of [ 318.330981] mei_me 0000:00:03.0: reset: wrong host start response [ 318.330984] mei_me 0000:00:03.0: unexpected reset: dev_state = RESETTING [ 318.330990] mei_me 0000:00:03.0: reset: unexpected enumeration response hbm. [ 318.330993] mei_me 0000:00:03.0: unexpected reset: dev_state = RESETTING [ 318.331016] mei_me 0000:00:03.0: reset: wrong host start response [ 318.331019] mei_me 0000:00:03.0: unexpected reset: dev_state = RESETTING [ 346.571031] mei_me 0000:00:03.0: reset: init clients timeout hbm_state = 1. [ 346.571047] mei_me 0000:00:03.0: unexpected reset: dev_state = RESETTING [ 376.631030] mei_me 0000:00:03.0: reset: init clients timeout hbm_state = 1. [ 376.631044] mei_me 0000:00:03.0: unexpected reset: dev_state = RESETTING It does, however, calm down after a few seconds, only to spew a few lines once every 30 seconds: [ 406.691032] mei_me 0000:00:03.0: reset: init clients timeout hbm_state = 1. [ 406.691048] mei_me 0000:00:03.0: unexpected reset: dev_state = RESETTING [ 436.751033] mei_me 0000:00:03.0: reset: init clients timeout hbm_state = 1. [ 436.751047] mei_me 0000:00:03.0: unexpected reset: dev_state = RESETTING [ 466.811030] mei_me 0000:00:03.0: reset: init clients timeout hbm_state = 1. [ 466.811044] mei_me 0000:00:03.0: unexpected reset: dev_state = RESETTING So it is not yet fixed, unfortunately. 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/