From: Maxim Levitsky <maximlevitsky@gmail.com>
To: reinette chatre <reinette.chatre@intel.com>
Cc: iwlwifi maling list <ipw3945-devel@lists.sourceforge.net>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [BUG] scans can still hang with -EBUSY on iwl3945
Date: Fri, 01 May 2009 23:13:12 +0300 [thread overview]
Message-ID: <1241208792.7082.47.camel@maxim-laptop> (raw)
In-Reply-To: <1241193513.10498.97.camel@rc-desk>
On Fri, 2009-05-01 at 08:58 -0700, reinette chatre wrote:
> Maxim,
>
> On Fri, 2009-05-01 at 05:00 -0700, Maxim Levitsky wrote:
> > Don't know if this is new regression, or just exposed race condition,
> > but currently using rfkill, and/or s2disk sometimes leaves the card in
> > state in which it can't scan.
>
> Could you please provide more details of this scenario?
OK, lets focus on my current setup:
* iwlwifi.git - very close to current head, yesterday HEAD
* disable_hw_scan=1 - this bug is present regardless of this setting,
yet this rules out firmware interactions during rfkill.
* Network Manager - ubuntu 9.04 unmodified.
* wpa_supplicant - close to git HEAD, with one local change:
It is known that on first attempt scans always fail, with same -EBUSY
iwlst scan shows 'Device is busy', supplicant complains about scan
requested (ret=-1), ... When this happens supplicant waits for 10
seconds, and I reduced that wait to 1 second.
When this happens, I can't make the card scan, scans always fail, and I
can only reload the module.
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2009-05-01 20:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 12:00 [BUG] scans can still hang with -EBUSY on iwl3945 Maxim Levitsky
2009-05-01 15:58 ` reinette chatre
2009-05-01 20:13 ` Maxim Levitsky [this message]
2009-05-02 1:32 ` Maxim Levitsky
2009-05-03 18:05 ` Johannes Berg
2009-05-03 18:07 ` Johannes Berg
2009-05-03 21:46 ` Maxim Levitsky
2009-05-04 7:19 ` Johannes Berg
2009-05-12 20:54 ` Maxim Levitsky
2009-05-12 23:10 ` Maxim Levitsky
2009-05-12 23:12 ` Johannes Berg
2009-05-12 23:14 ` Maxim Levitsky
2009-05-12 23:20 ` Johannes Berg
2009-05-13 0:50 ` Maxim Levitsky
2009-05-13 8:29 ` Johannes Berg
2009-05-14 21:14 ` reinette chatre
2009-05-14 21:14 ` Johannes Berg
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=1241208792.7082.47.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@intel.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