iwlegacy: print how long queue was actually stuck
authorPaul Bolle <pebolle@tiscali.nl>
Wed, 27 Jun 2012 08:36:27 +0000 (10:36 +0200)
committerJohn W. Linville <linville@tuxdriver.com>
Thu, 28 Jun 2012 18:37:44 +0000 (14:37 -0400)
commit26b6da6b7829dc7cf5d21e854564be90c7928323
tree2beecc84d1d0b8f46679a9253cc11a592c5139ac
parentbf52592fe4901f486a5266fd73e4ee80205b18b4
iwlegacy: print how long queue was actually stuck

Every now and then, after resuming from suspend, the iwlegacy driver
prints
    iwl4965 0000:03:00.0: Queue 2 stuck for 2000 ms.
    iwl4965 0000:03:00.0: On demand firmware reload

I have no idea what causes these errors. But the code currently uses
wd_timeout in the first error. wd_timeout will generally be set at
IL_DEF_WD_TIMEOUT (ie, 2000). Perhaps printing for how long the queue
was actually stuck can clarify the cause of these errors.

Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
drivers/net/wireless/iwlegacy/common.c