19 Nov
2012
19 Nov
'12
2:56 p.m.
Could you try the patch below instead?
The patch did not apply against 3.7-rc6 but the patch below applied and let the trace disappear.
OK, then at least it can be added as a workaround.
But the spurious response still appears, right?
Yes, the spurious response still appears.
Hm, then something screwed up the communication...
At which moment do you see such a message? In other words, how to trigger the bug?
I suspend my system to ram or to disk. Then I resume it, everthing comes up again and then, aprrox 4s after the resume was initiated, the spurious response messages hit the dmesg for approx. 0.07s as you can see in my first message. Hopefully this answer the question.
With best regards, Julian