From: Zhu Yi <yi.zhu@intel.com>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
"ipw2100-devel@lists.sourceforge.net"
<ipw2100-devel@lists.sourceforge.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Cahill, Ben M" <ben.m.cahill@intel.com>
Subject: Re: [Ipw2100-devel] [PATCH] ipw2200: rework scan handling while associated
Date: Wed, 03 Dec 2008 17:33:13 +0800 [thread overview]
Message-ID: <1228296794.2558.324.camel@debian.sh.intel.com> (raw)
In-Reply-To: <200812011110.02974.helmut.schaa@gmail.com>
On Mon, 2008-12-01 at 18:10 +0800, Helmut Schaa wrote:
> That only happens while associated. Scanning while not associated
> works like
> a charm.
>
> Here are some more informations:
> If I load the unmodified module with debug=0x3FFF I get the following
> log
> when triggering a scan while associated:
>
> ipw2200: U ipw_wx_set_scan Start scan
> 00000000 03 00 00 00 0D 24 28 2C 30 34 38 3C 40 95 99 9D .....$(,
> 048<@...
> 00000010 A1 A5 4A 02 03 04 05 06 07 08 09 0A 0B 00 00
> 00 ..J..... ........
> 00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 ........ ........
> 00000030 00 00 00 00 00 00 00 00 00 00 03 33 31 11 13
> 33 ........ ...31..3
> 00000040 33 03 33 33 33 33 30 00 00 00 00 00 00 00 00 00
> 3.33330. ........
> 00000050 00 00 00 00 00 00 00 00 78 00 14 00 14 00 14 00 ........
> x.......
> martian source 255.255.255.255 from 149.44.170.156, on dev eth1
> ll header: ff:ff:ff:ff:ff:ff:00:19:99:28:58:5b:08:00
> ipw2200: I ipw_rx_notification type = 12 (46 bytes)
> ipw2200: I ipw_rx_notification Scan result for channel 36
> ipw2200: I ipw_rx_notification type = 12 (46 bytes)
> ipw2200: I ipw_rx_notification Scan result for channel 40
> ipw2200: I ipw_rx_notification type = 12 (46 bytes)
> ipw2200: I ipw_rx_notification Scan result for channel 44
> ipw2200: I ipw_rx_notification type = 25 (4 bytes)
> ipw2200: I ipw_rx_notification type = 12 (46 bytes)
> ipw2200: I ipw_rx_notification Scan result for channel 48
>
> The channels 36-48 are active 11a channels. The next channel would be
> 52 which
> is a passive channel.
>
> martian source 255.255.255.255 from 149.44.170.66, on dev eth1
> ll header: ff:ff:ff:ff:ff:ff:00:0e:0c:aa:5c:c5:08:00
> ipw2200: I ipw_rx_notification type = 25 (4 bytes)
> ipw2200: I ipw_rx_notification type = 25 (4 bytes)
> ipw2200: I ipw_rx_notification type = 25 (4 bytes)
> ipw2200: I ipw_rx_notification type = 25 (4 bytes)
> ipw2200: I ipw_rx_notification type = 25 (4 bytes)
> ipw2200: I ipw_rx_notification type = 25 (4 bytes)
> ipw2200: I ipw_rx_notification type = 17 (8 bytes)
> ipw2200: I ipw_handle_missed_beacon Aborting scan with missed beacon.
> ipw2200: I ipw_handle_missed_beacon Missed beacon: 1
>
> Aha, the firmware noticed a beacon miss before the scan watchdog
> restarts the firmware (the log is without timestamps, sorry).
>
> ipw2200: I ipw_rx_notification type = 13 (4 bytes)
> ipw2200: I ipw_rx_notification Scan completed: type 1, 5 channels, 2
> status
>
> Status 2 -> Scan aborted.
We will look at this.
Thanks,
-yi
next prev parent reply other threads:[~2008-12-03 9:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 17:05 [PATCH] ipw2200: rework scan handling while associated Helmut Schaa
2008-11-28 8:51 ` [Ipw2100-devel] " Zhu Yi
2008-11-28 9:31 ` Helmut Schaa
2008-12-01 2:58 ` Zhu Yi
2008-12-01 10:10 ` Helmut Schaa
2008-12-03 9:33 ` Zhu Yi [this message]
2008-12-10 5:51 ` Zhu Yi
2008-12-10 9:11 ` Helmut Schaa
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=1228296794.2558.324.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=ben.m.cahill@intel.com \
--cc=helmut.schaa@googlemail.com \
--cc=ipw2100-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).