On 11/05/2013 03:49 PM, Winkler, Tomas wrote:
This patches only catch the error, our goal is to discover why it is failing.
I have just applied these error-handling-related patches to kernel 3.10.15 (without commenting out schedule_delayed_work(&dev->timer_work, HZ) yet) and checked the system again.
The full log is attached, the config is the same as I sent before. Here are MEI-related messages from there: --------------------------------------- [ 1.011579] mei_me 0000:00:16.0: setting latency timer to 64 [ 1.011616] mei_me 0000:00:16.0: irq 40 for MSI/MSI-X [ 215.552616] mei_me 0000:00:16.0: suspend [ 216.675402] mei_me 0000:00:16.0: irq 40 for MSI/MSI-X [ 250.390001] mei_me 0000:00:16.0: suspend [ 251.519709] mei_me 0000:00:16.0: irq 40 for MSI/MSI-X [ 289.780943] mei_me 0000:00:16.0: suspend [ 290.781338] mei_me 0000:00:16.0: irq 40 for MSI/MSI-X [ 319.506298] mei_me 0000:00:16.0: suspend [ 320.503153] mei_me 0000:00:16.0: irq 40 for MSI/MSI-X [ 348.110390] mei_me 0000:00:16.0: suspend [ 348.958731] mei_me 0000:00:16.0: irq 40 for MSI/MSI-X [ 386.344351] mei_me 0000:00:16.0: suspend [ 387.461297] mei_me 0000:00:16.0: irq 40 for MSI/MSI-X[ 387.513101] mei_me 0000:00:16.0: reset: properties response hbm wrong status. [ 387.513104] mei_me 0000:00:16.0: unexpected reset: dev_state = INIT_CLIENTS
[ 394.514883] mei_me 0000:00:16.0: wait hw ready failed. status = -110 [ 394.514890] mei_me 0000:00:16.0: hw_start failed disabling the device ---------------------------------------No message flood anymore, which is good, but you are right, the problem seems to be somewhere deeper.
As far as kernel 3.11.6 is concerned, I see no message flood there but "wait hw ready failed. status = -110" is in the log, same as for 3.10.15.
Regards, Eugene -- Eugene Shatokhin, ROSA Laboratory. www.rosalab.com
system_log_20131105.tar.bz2
Description: application/bzip