On 06/26/2013 04:12 PM, Winkler, Tomas wrote: > > >>> Can you please send me the log part when this starts? >>> >>> Thanks >>> >> >> It rolled over and I don't have prior messages. I tried reproducing twice and >> didn't see it again. I will try a few more times and see if I can get it to happen >> again. >> >> This is what I could save before dmesg rolled over: >> >> [ 78.709014] mei_me 0000:00:16.0: reset: wrong host start response >> [ 78.709016] mei_me 0000:00:16.0: unexpected reset: dev_state = >> RESETTING >> [ 78.709029] mei_me 0000:00:16.0: reset: unexpected enumeration >> response hbm. >> [ 78.709031] mei_me 0000:00:16.0: unexpected reset: dev_state = >> RESETTING >> [ 78.709069] mei_me 0000:00:16.0: reset: wrong host start response >> > So far I was able to positively reproduce it with 3.10-rc5 but not with 3.10-rc7 and above. > > There are 3 patches that went in to fix this issue > > 42f132f mei: me: clear interrupts on the resume path > 2753ff5 mei: nfc: fix nfc device freeing > 5e85b36 mei: init: Flush scheduled work before resetting the device > > Are you sure you have these 3 in? > Checked the git log and yes I have all three commits. It appears this problem is intermittent and hard to reproduce at least on 3.10-rc7. I tried several times yesterday to capture the log and couldn't reproduce. -- Shuah Shuah Khan, Linux Kernel Developer - Open Source Group Samsung Research America (Silicon Valley) shuah.kh at samsung.com | (970) 672-0658
