Comment 77 for bug 414560

yeah, it's the same here - it seems to be stable for some time; but after a while, it disconnects and refuses to connect again - even after rmmod + modprobe'ing the driver.
This indicates that it must be messing up the internal state of the h/w somewhere during one of the resets (possibly, the last one) for scan. I could be wrong though.

This is why I said that the driver borks for some unknown reason in my previous comment.