Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: seventh guardian <seventhguardian@gmail.com>,
	netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: d80211 deadlock with wpa_supplicant and rmmod
Date: Thu, 12 Jul 2007 12:02:18 +0200	[thread overview]
Message-ID: <1184234538.6669.30.camel@johannes.berg> (raw)
In-Reply-To: <20070711234153.GB5099@tuxdriver.com>

[-- Attachment #1: Type: text/plain, Size: 698 bytes --]

On Wed, 2007-07-11 at 19:41 -0400, John W. Linville wrote:

> > >I believe we have a deadlock in d80211.
> > 
> > I have it too. But I'm using iwl3945 driver, in-kernel mac80211, and a
> > gentoo kernel (basically a patched vanilla-2.6.22.1). My machine is a
> > x86_64 core 2 duo.
> > 
> > >The following triggers it on my 2way SMT machine with preempt.
> > >
> > >modprobe bcm43xx-d80211
> > >add sta0
> > >ifconfig sta0 up
> > >start wpa_supplicant on the interface
> > >rmmod bcm43xx-d80211

Sounds like the bug with the scheduled work locking. See the
"mac80211/bcm43xx deadlock" thread, there's a patch, report back if you
can/can not reproduce with the patch.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  parent reply	other threads:[~2007-07-12 10:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1caff7430707111617o70a534a5x2cf6b611a91f301a@mail.gmail.com>
2007-07-11 23:41 ` d80211 deadlock with wpa_supplicant and rmmod John W. Linville
2007-07-12  2:20   ` seventh guardian
2007-07-12 10:02   ` Johannes Berg [this message]
2007-07-13 12:05     ` seventh guardian
2007-07-13 21:45       ` Johannes Berg
2007-07-14 13:24         ` Jiri Benc

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=1184234538.6669.30.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=seventhguardian@gmail.com \
    /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