linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: linux-wireless@vger.kernel.org,
	linux-pm@lists.linux-foundation.org,
	USB list <linux-usb@vger.kernel.org>
Subject: Re: rtl8187 usb wifi adaptor causes suspend hang
Date: Tue, 30 Dec 2008 13:10:32 +0000	[thread overview]
Message-ID: <495A1DC8.1050609@tuffmail.co.uk> (raw)
In-Reply-To: <4959FD3F.1060306@tuffmail.co.uk>

Alan Jenkins wrote:
> [lsusb: ID 0bda:8187 Realtek Semiconductor Corp]
>
>
> I'd like to use this wireless adaptor I have, but the driver doesn't
> play nice with suspend.  It hangs after switching to the console,
> without printing anything.  This happens even if I haven't used the
> adaptor (i.e. ifconfig shows 0 bytes rx/tx).  Interestingly the numlock
> key on my USB keyboard still works.
>
> I tried "no_console_suspend nmi_watchdog=1", but it didn't show any more
> output.  (I waited 3 minutes for the watchdog to trigger).
>
> However, I can insert panic() calls, and see whether I hit the hang
> first, or go into a panic with flashing keyboard LEDs.  I used this to
> confirm that the hang happens inside the rtl8187_disconnect() function.
>
> There's a good chance I can track this down myself, using panic()
> again.  Before I start, does anyone have an idea what might be happening?
>   
Ok, I think I got it.

The hang is in ieee80211_unregister_hw(), on this line:

destroy_workqueue(local->hw.workqueue);


local->hw.workqueue is created using create_freezeable_workqueue().  So
presumably destroy_workqueue() deadlocks because the workqueue has
already been frozen.

Is it possible to fix this without suspend support in mac80211?  If not,
I vote we change rtl8187 (and zd_usb) to prevent suspend.  I.e. set USB
suspend callbacks which return an error.

Thanks
Alan


  reply	other threads:[~2008-12-30 13:10 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-30 10:51 rtl8187 usb wifi adaptor causes suspend hang Alan Jenkins
2008-12-30 13:10 ` Alan Jenkins [this message]
2008-12-30 15:45   ` [linux-pm] " Alan Stern
2008-12-30 16:45     ` Bob Copeland
2008-12-30 16:48       ` Alan Jenkins
2008-12-30 17:25       ` Alan Stern
2008-12-30 17:31         ` Alan Jenkins
2008-12-30 17:52           ` Larry Finger
2008-12-30 18:05             ` Hin-Tak Leung
2008-12-30 18:05             ` Oliver Neukum
2008-12-30 18:09               ` Larry Finger
2008-12-31  0:59             ` Hin-Tak Leung
2008-12-31 14:33               ` Alan Jenkins
2008-12-31 15:57                 ` Bob Copeland
2008-12-31 17:10                   ` Alan Jenkins
2008-12-31 17:16                 ` Oliver Neukum
2008-12-31 19:33                 ` Larry Finger
2008-12-31 23:00                   ` Larry Finger
2008-12-31 23:26                     ` Bob Copeland
2009-01-01  0:16                     ` Alan Stern
2009-01-01  6:06                   ` Hin-Tak Leung
2009-01-01 22:25                     ` Alan Stern
2009-01-01 23:42                       ` Hin-Tak Leung
2009-01-02  2:24                         ` Alan Stern
2009-01-01  6:18                 ` Hin-Tak Leung
2009-01-01 13:07                   ` Alan Jenkins
2009-01-01 13:40                     ` Stefanik Gábor
2009-01-01 14:39                       ` Hin-Tak Leung
2009-01-01 16:38                         ` Larry Finger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=495A1DC8.1050609@tuffmail.co.uk \
    --to=alan-jenkins@tuffmail.co.uk \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).