> Thanks for your prompt response. So it is not possible a driver or FW bug? > We will recheck our test. It could definitely still be a driver or FW bug. But a real CQ overrun seems the most likely cause to me right now... without the test code it's really hard to say.