Ticket #6586 (closed defect: fixed)
SCAN command fails, timer doesn't fire
|Reported by:||dwmw2||Owned by:||dwmw2|
|Keywords:||release?||Cc:||mblestas, yani, carrano, kim, jg, cscott, dwmw2, ashish, mstone, mtd|
|Deployments affected:||Blocked By:|
In testing we've seen that sometimes the command queue gets full. This shouldn't happen -- we set a timer to resubmit commands, and then reset the device completely, when commands don't complete. But for some reason it doesn't fire.
We think it's a SCAN command because when we unload the module, we get a 'SCAN failed' message as it's cancelled.
Obviously there's an underlying firmware bug, but there's also a driver bug -- I don't understand why the timer isn't firing. Have added some debugging messages when the timer is armed and cancelled; would like to see debug output while this happens.