From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: reinette chatre <reinette.chatre@intel.com>,
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: Tue, 12 May 2009 23:54:03 +0300 [thread overview]
Message-ID: <1242161643.26484.2.camel@maxim-laptop> (raw)
In-Reply-To: <1241421545.6866.2.camel@johannes.local>
On Mon, 2009-05-04 at 09:19 +0200, Johannes Berg wrote:
> On Mon, 2009-05-04 at 00:46 +0300, Maxim Levitsky wrote:
> > Yes, sure
> > For record I use iwlwifi.git commit
> > 5a94b6d38100b7056a5a347e5c51359d924d305d
>
> Ok.
>
> > Logs attached.
> > This bug can be reliably reproduced, happens every 5~10 times when I
> > turn rfkill on/off, but today again this happened after resume from
> > disk.
>
> Ah, rfkill. Hmm, unfortunately I don't have a system with rfkill. I
> looked at ieee80211_scan_work but can't see how it would abort the
> scan... Could you put some debugging into that function? Especially
> printing out the state when it enters, whether it calls
Hi,
I can't seem to reproduce that ether.
Maybe this got fixed (I have seen few suspicios commits in
wireless-testing... althought I think this is a wishfull thinking)
Anyway, I I have put printks in ieee80211_scan_work.
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2009-05-12 20:54 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
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 [this message]
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=1242161643.26484.2.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=johannes@sipsolutions.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