Comment # 8 on bug 1201845 from Takashi Iwai

Thanks.  The warning seems triggered when the driver starts resetting and the
driver-own failure happens during the reset.  The kernel warning itself might
be a red herring.

So rather we need to ask to upstream devs why this "driver own failed" error
happens repeatedly at all.  It could be reported to bugzilla.kernel.org, but I
suspect it's badly watched out by the upstream devs.  Maybe better to report to
linux-wireless ML instead.

Care to post to linux-wireless ML (and put Cc to me)?