* iwl3945: Error sending REPLY_{RXON|SCAN_CMD|TX_PWR_TABLE_CMD} time out after 500ms
@ 2010-04-17 14:05 Sedat Dilek
2010-04-20 16:54 ` reinette chatre
0 siblings, 1 reply; 9+ messages in thread
From: Sedat Dilek @ 2010-04-17 14:05 UTC (permalink / raw)
To: wireless; +Cc: Reinette Chatre, Johannes Berg
Hi,
I have already sent an bug-report "iwl3945: Network dropouts w/
flash-stream in firefox" in [1].
Unfortunately, the problem still remains, especially when
fast-forwarding flash movies in firefox-3.6.3.
It seems the wifi-card is hanging and my system needs a coldstart.
My wifi-card is an iwl3945 and my access-point is a speedport-w701v.
I am using a Debian/sid 32-bit system.
Today, I enabled CONFIG_IWLWIFI_DEBUG=y to see what is going on.
I stopped networking, unloaded the kernel-module and re-loaded with
module-option debug=0x43fff [2].
# /etc/init.d/networking stop
# modprobe -r -v iwl3945
# modprobe -v iwl3945 debug=0x43fff
The kernel I use is a Linux-2.6.34-rc4-git4 with these 3 patches in addition:
patches/wireless-2.6:
0001-iwlwifi-work-around-bogus-active-chains-detection.patch
patches/iwlwifi-fixes-for-2.6.34:
1-2-iwlwifi-fix-scan-races.patch
2-2-iwlwifi-correct-6000-EEPROM-regulatory-address.patch
According to Johannes (on IRC) iwl3945 doesn't use internal scans yet
(see my patch below).
Thus, I am not sure if this needs to be fixed separately for iwl3945
and if I ran into a scan race condition here.
If this matters: I am using Debian's wpasupplicant (0.6.10-2) and wext
wpa-driver.
I collected all data and provide them in [3].
Hope, this helps.
Kind Regards,
- Sedat -
[1] http://marc.info/?l=linux-wireless&m=127135267301937&w=2
[2] http://intellinuxwireless.org/?n=fw_error_report
[3] http://files.iniza.org/BUG_iwl3945_20100417/
[PATCH]
$ cat iwl3945-fix-scan-races.patch
--- linux-2.6.orig/drivers/net/wireless/iwlwifi/iwl3945-base.c 2010-04-13
03:41:35.000000000 +0200
+++ linux-2.6/drivers/net/wireless/iwlwifi/iwl3945-base.c 2010-04-17
10:46:52.765166367 +0200
@@ -3792,6 +3792,7 @@ static void iwl3945_cancel_deferred_work
cancel_delayed_work_sync(&priv->init_alive_start);
cancel_delayed_work(&priv->scan_check);
+ cancel_work_sync(&priv->start_internal_scan);
cancel_delayed_work(&priv->alive_start);
cancel_work_sync(&priv->beacon_update);
}
[/PATCH]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: iwl3945: Error sending REPLY_{RXON|SCAN_CMD|TX_PWR_TABLE_CMD} time out after 500ms
2010-04-17 14:05 iwl3945: Error sending REPLY_{RXON|SCAN_CMD|TX_PWR_TABLE_CMD} time out after 500ms Sedat Dilek
@ 2010-04-20 16:54 ` reinette chatre
2010-04-21 7:06 ` Sedat Dilek
0 siblings, 1 reply; 9+ messages in thread
From: reinette chatre @ 2010-04-20 16:54 UTC (permalink / raw)
To: sedat.dilek; +Cc: wireless, Berg, Johannes
Hi,
On Sat, 2010-04-17 at 07:05 -0700, Sedat Dilek wrote:
> I have already sent an bug-report "iwl3945: Network dropouts w/
> flash-stream in firefox" in [1].
> Unfortunately, the problem still remains, especially when
> fast-forwarding flash movies in firefox-3.6.3.
> It seems the wifi-card is hanging and my system needs a coldstart.
Is this a recent problem? How regularly do you update your kernel?
>
> The kernel I use is a Linux-2.6.34-rc4-git4 with these 3 patches in addition:
Where can I access this kernel's git repo?
> According to Johannes (on IRC) iwl3945 doesn't use internal scans yet
> (see my patch below).
> Thus, I am not sure if this needs to be fixed separately for iwl3945
> and if I ran into a scan race condition here.
Does this patch make any difference for you?
> Hope, this helps.
It does. Thank you. As a sanity check, could you please try this patch?
diff --git a/net/mac80211/mlme.c b/net/mac80211/mlme.c
index c8cd169..1ad15bd 100644
--- a/net/mac80211/mlme.c
+++ b/net/mac80211/mlme.c
@@ -814,7 +814,7 @@ static void ieee80211_set_disassoc(struct ieee80211_sub_if_data *sdata)
changed |= BSS_CHANGED_ASSOC;
sdata->vif.bss_conf.assoc = false;
- ieee80211_set_wmm_default(sdata);
+ /*ieee80211_set_wmm_default(sdata);*/
/* channel(_type) changes are handled by ieee80211_hw_config */
local->oper_channel_type = NL80211_CHAN_NO_HT;
^ permalink raw reply related [flat|nested] 9+ messages in thread
* Re: iwl3945: Error sending REPLY_{RXON|SCAN_CMD|TX_PWR_TABLE_CMD} time out after 500ms
2010-04-20 16:54 ` reinette chatre
@ 2010-04-21 7:06 ` Sedat Dilek
2010-04-21 20:50 ` reinette chatre
0 siblings, 1 reply; 9+ messages in thread
From: Sedat Dilek @ 2010-04-21 7:06 UTC (permalink / raw)
To: reinette chatre; +Cc: wireless, John Linville, Johannes Berg
On Tue, Apr 20, 2010 at 6:54 PM, reinette chatre
<reinette.chatre@intel.com> wrote:
> Hi,
>
> On Sat, 2010-04-17 at 07:05 -0700, Sedat Dilek wrote:
>> I have already sent an bug-report "iwl3945: Network dropouts w/
>> flash-stream in firefox" in [1].
>> Unfortunately, the problem still remains, especially when
>> fast-forwarding flash movies in firefox-3.6.3.
>> It seems the wifi-card is hanging and my system needs a coldstart.
>
> Is this a recent problem? How regularly do you update your kernel?
>
Currently, I am using mostly upstream 2.6.34-rcX kernels.
When kernel snapshots (-gitX) have drm-2.6, ext4 or wireless-2.6
patches I jump on them.
>>
>> The kernel I use is a Linux-2.6.34-rc4-git4 with these 3 patches in addition:
>
> Where can I access this kernel's git repo?
>
As I already said it is Linus-tree - to be on 2.6.34-rc4-git4 [1], run:
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
$ git reset --hard dc57da3875f527b1cc195ea4ce5bd32e1e68433d
It would be cool, when you can check this on some iwl3945 hardware.
Do not forget the three patches from [2] to have same testing environment.
As far as I can see, wireless-2.6 (master-2010-04-20) has them included.
>> According to Johannes (on IRC) iwl3945 doesn't use internal scans yet
>> (see my patch below).
>> Thus, I am not sure if this needs to be fixed separately for iwl3945
>> and if I ran into a scan race condition here.
>
> Does this patch make any difference for you?
>
Speaking of my patch "iwl3945-fix-scan-races.patch" from [3]?
I was guessing iwl3945 has internal scans support - is that the fact?
Johannes told me someone is working on it.
To answer your question: Not sure, but it seems not to help.
Unfortunately, it is hard for me to say what exactly caused these wifi problems.
After my email I tested 2.6.34-rc4-git6 and could not reproduce it.
I tested several websites with flash streams.
Do the ash particles of the Iceland volcano disturb wlan waves here?
Wonder why John gave no restrictions to Linux wireless users and devs
to not use wifi and switch to wired connections for last weekend and
next days :-).
>> Hope, this helps.
>
> It does. Thank you. As a sanity check, could you please try this patch?
>
In general, it would be very helpful to give some comments on what
this offered patch is doing.
Not sure, if I can test it today.
To have same scenario, base is a Linux-2.6.34-rc4-git4 kernel with this series:
wireless-2.6/0001-iwlwifi-work-around-bogus-active-chains-detection.patch
iwlwifi-fixes-for-2.6.34/1-2-iwlwifi-fix-scan-races.patch
iwlwifi-fixes-for-2.6.34/2-2-iwlwifi-correct-6000-EEPROM-regulatory-address.patch
rchatre/sanity-check.patch
> diff --git a/net/mac80211/mlme.c b/net/mac80211/mlme.c
> index c8cd169..1ad15bd 100644
> --- a/net/mac80211/mlme.c
> +++ b/net/mac80211/mlme.c
> @@ -814,7 +814,7 @@ static void ieee80211_set_disassoc(struct ieee80211_sub_if_data *sdata)
> changed |= BSS_CHANGED_ASSOC;
> sdata->vif.bss_conf.assoc = false;
>
> - ieee80211_set_wmm_default(sdata);
> + /*ieee80211_set_wmm_default(sdata);*/
>
> /* channel(_type) changes are handled by ieee80211_hw_config */
> local->oper_channel_type = NL80211_CHAN_NO_HT;
>
By the way, might help to set one of the module-options for iwl3945?
parm: antenna:select antenna (1=Main, 2=Aux, default 0 [both]) (int)
parm: swcrypto:using software crypto (default 1 [software]) (int)
parm: debug:debug output mask (uint)
parm: disable_hw_scan:disable hardware scanning (default 0) (int)
parm: fw_restart3945:restart firmware in case of error (int)
Especially "fw_restart3945" in my case? On which errors it is
restarting firmware?
Kind Regards,
- Sedat -
[1] http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.34-rc4-git4.id
[2] http://files.iniza.org/BUG_iwl3945_20100417/patches/
[3] http://marc.info/?l=linux-wireless&m=127151315515173&w=2
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: iwl3945: Error sending REPLY_{RXON|SCAN_CMD|TX_PWR_TABLE_CMD} time out after 500ms
2010-04-21 7:06 ` Sedat Dilek
@ 2010-04-21 20:50 ` reinette chatre
2010-04-26 8:20 ` Sedat Dilek
0 siblings, 1 reply; 9+ messages in thread
From: reinette chatre @ 2010-04-21 20:50 UTC (permalink / raw)
To: sedat.dilek; +Cc: wireless, John Linville, Berg, Johannes
Sedat,
On Wed, 2010-04-21 at 00:06 -0700, Sedat Dilek wrote:
> >> According to Johannes (on IRC) iwl3945 doesn't use internal scans yet
> >> (see my patch below).
> >> Thus, I am not sure if this needs to be fixed separately for iwl3945
> >> and if I ran into a scan race condition here.
> >
> > Does this patch make any difference for you?
> >
>
> Speaking of my patch "iwl3945-fix-scan-races.patch" from [3]?
> I was guessing iwl3945 has internal scans support - is that the fact?
> Johannes told me someone is working on it.
It has some support ... but nothing that currently requests an internal
scan.
> To answer your question: Not sure, but it seems not to help.
Weird.
> >
> > It does. Thank you. As a sanity check, could you please try this patch?
> >
>
> In general, it would be very helpful to give some comments on what
> this offered patch is doing.
> Not sure, if I can test it today.
>
>From your logs I see that it is right after disconnecting from AP (after
loosing probe responses) that the problem occurs. I see that we send QOS
commands to the device, to which it responds, but after that you start
to get errors. I looked at when those QOS commands are sent and they are
sent in ieee80211_set_disassoc _after_ the queues have been disabled. I
am not sure if that is the right thing to do and wanted to check if it
is indeed those commands that are causing the issue. The patch I asked
you to test modified the code to not send QOS commands after queues have
been disabled.
> By the way, might help to set one of the module-options for iwl3945?
>
> parm: antenna:select antenna (1=Main, 2=Aux, default 0 [both]) (int)
> parm: swcrypto:using software crypto (default 1 [software]) (int)
> parm: debug:debug output mask (uint)
> parm: disable_hw_scan:disable hardware scanning (default 0) (int)
> parm: fw_restart3945:restart firmware in case of error (int)
>
> Especially "fw_restart3945" in my case?
It should be set by default.
> On which errors it is
> restarting firmware?
Firmware errors.
Reinette
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: iwl3945: Error sending REPLY_{RXON|SCAN_CMD|TX_PWR_TABLE_CMD} time out after 500ms
2010-04-21 20:50 ` reinette chatre
@ 2010-04-26 8:20 ` Sedat Dilek
2010-04-26 16:08 ` reinette chatre
0 siblings, 1 reply; 9+ messages in thread
From: Sedat Dilek @ 2010-04-26 8:20 UTC (permalink / raw)
To: reinette chatre; +Cc: wireless, John Linville, Berg, Johannes
Hi,
last weekend I could test a bit.
On Saturday, I tested with Linux-2.6.34-git4 and some additional
iwlwifi patches.
I used wpa_supplicant was (0.6.10-2) and wext driver.
I had only one issue with
linux-image-2.6.34-rc4-115-gdc57da3_2.6.34-rc4-115-gdc57da3.20100424~iniza.1_i386.deb
kernel:
...
/var/log/syslog.1-Apr 25 13:33:11 seduxbox wpa_supplicant[1732]: WPA:
Group rekeying completed with 00:04:0e:e4:00:3d [GTK=CCMP]
/var/log/syslog.1:Apr 25 13:59:56 seduxbox kernel: [59184.500070] No
probe response from AP 00:04:0e:e4:00:3d after 500ms, disconnecting.
/var/log/syslog.1-Apr 25 13:59:56 seduxbox kernel: [59184.505044]
cfg80211: Calling CRDA to update world regulatory domain
/var/log/syslog.1-Apr 25 13:59:56 seduxbox wpa_supplicant[1732]:
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
/var/log/syslog.1-Apr 25 13:59:57 seduxbox kernel: [59185.717331]
cfg80211: World regulatory domain updated:
/var/log/syslog.1-Apr 25 13:59:57 seduxbox kernel: [59185.717337]
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
/var/log/syslog.1-Apr 25 13:59:57 seduxbox kernel: [59185.717343]
(2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
/var/log/syslog.1-Apr 25 13:59:57 seduxbox kernel: [59185.717349]
(2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
/var/log/syslog.1-Apr 25 13:59:57 seduxbox kernel: [59185.717355]
(2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
/var/log/syslog.1-Apr 25 13:59:57 seduxbox kernel: [59185.717361]
(5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
/var/log/syslog.1-Apr 25 13:59:57 seduxbox kernel: [59185.717367]
(5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
/var/log/syslog.1-Apr 25 13:59:59 seduxbox wpa_supplicant[1732]:
Trying to associate with 00:04:0e:e4:00:3d
(SSID='g00gle-street-knows-my-SSID-and-where-I-live' freq=2442 MHz)
/var/log/syslog.1-Apr 25 13:59:59 seduxbox kernel: [59187.753888]
wlan0: authenticate with 00:04:0e:e4:00:3d (try 1)
/var/log/syslog.1-Apr 25 13:59:59 seduxbox kernel: [59187.755614]
wlan0: authenticated
/var/log/syslog.1-Apr 25 13:59:59 seduxbox kernel: [59187.755649]
wlan0: associate with 00:04:0e:e4:00:3d (try 1)
/var/log/syslog.1-Apr 25 13:59:59 seduxbox kernel: [59187.760216]
wlan0: RX AssocResp from 00:04:0e:e4:00:3d (capab=0x411 status=0
aid=1)
/var/log/syslog.1-Apr 25 13:59:59 seduxbox kernel: [59187.760221]
wlan0: associated
/var/log/syslog.1-Apr 25 13:59:59 seduxbox wpa_supplicant[1732]:
Associated with 00:04:0e:e4:00:3d
/var/log/syslog.1-Apr 25 13:59:59 seduxbox wpa_supplicant[1732]: WPA:
Key negotiation completed with 00:04:0e:e4:00:3d [PTK=CCMP GTK=CCMP]
/var/log/syslog.1-Apr 25 13:59:59 seduxbox wpa_supplicant[1732]:
CTRL-EVENT-CONNECTED - Connection to 00:04:0e:e4:00:3d completed
(reauth) [id=0 id_str=]
...
With Reinette's sanity-check patch this did not happen.
Nevertheless, it is hard for me to speak from reproducibility or even success.
I have this issue on my radar...
Flash and Linux is like fist and eye - if they come together it hurts.
Kind Regards,
- Sedat -
P.S.:
$ ls -l linux-image*2.6.34*rc4*.deb
-rw-r--r-- 1 sd sd 25436128 2010-04-24 11:20
linux-image-2.6.34-rc4-115-gdc57da3_2.6.34-rc4-115-gdc57da3.20100424~iniza.1_i386.deb
-rw-r--r-- 1 sd sd 25437636 2010-04-24 21:02
linux-image-2.6.34-rc4-115-gdc57da3-test_2.6.34-rc4-115-gdc57da3-test.20100424~iniza.2_i386.deb
[linux-image-2.6.34-rc4-115-gdc57da3_2.6.34-rc4-115-gdc57da3.20100424~iniza.1_i386.deb]
wireless-2.6/0001-iwlwifi-work-around-bogus-active-chains-detection.patch
iwlwifi-fixes-for-2.6.34/1-2-iwlwifi-fix-scan-races.patch
iwlwifi-fixes-for-2.6.34/2-2-iwlwifi-correct-6000-EEPROM-regulatory-address.patch
[linux-image-2.6.34-rc4-115-gdc57da3-test_2.6.34-rc4-115-gdc57da3-test.20100424~iniza.2_i386.deb]
wireless-2.6/0001-iwlwifi-work-around-bogus-active-chains-detection.patch
iwlwifi-fixes-for-2.6.34/1-2-iwlwifi-fix-scan-races.patch
iwlwifi-fixes-for-2.6.34/2-2-iwlwifi-correct-6000-EEPROM-regulatory-address.patch
rchatre/0001-Test-Sanity-check-by-Reinette-Chatre.patch
On Wed, Apr 21, 2010 at 10:50 PM, reinette chatre
<reinette.chatre@intel.com> wrote:
> Sedat,
>
> On Wed, 2010-04-21 at 00:06 -0700, Sedat Dilek wrote:
>> >> According to Johannes (on IRC) iwl3945 doesn't use internal scans yet
>> >> (see my patch below).
>> >> Thus, I am not sure if this needs to be fixed separately for iwl3945
>> >> and if I ran into a scan race condition here.
>> >
>> > Does this patch make any difference for you?
>> >
>>
>> Speaking of my patch "iwl3945-fix-scan-races.patch" from [3]?
>> I was guessing iwl3945 has internal scans support - is that the fact?
>> Johannes told me someone is working on it.
>
> It has some support ... but nothing that currently requests an internal
> scan.
>
>> To answer your question: Not sure, but it seems not to help.
>
> Weird.
>
>> >
>> > It does. Thank you. As a sanity check, could you please try this patch?
>> >
>>
>> In general, it would be very helpful to give some comments on what
>> this offered patch is doing.
>> Not sure, if I can test it today.
>>
>
> >From your logs I see that it is right after disconnecting from AP (after
> loosing probe responses) that the problem occurs. I see that we send QOS
> commands to the device, to which it responds, but after that you start
> to get errors. I looked at when those QOS commands are sent and they are
> sent in ieee80211_set_disassoc _after_ the queues have been disabled. I
> am not sure if that is the right thing to do and wanted to check if it
> is indeed those commands that are causing the issue. The patch I asked
> you to test modified the code to not send QOS commands after queues have
> been disabled.
>
>> By the way, might help to set one of the module-options for iwl3945?
>>
>> parm: antenna:select antenna (1=Main, 2=Aux, default 0 [both]) (int)
>> parm: swcrypto:using software crypto (default 1 [software]) (int)
>> parm: debug:debug output mask (uint)
>> parm: disable_hw_scan:disable hardware scanning (default 0) (int)
>> parm: fw_restart3945:restart firmware in case of error (int)
>>
>> Especially "fw_restart3945" in my case?
>
> It should be set by default.
>
>> On which errors it is
>> restarting firmware?
>
> Firmware errors.
>
> Reinette
>
>
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: iwl3945: Error sending REPLY_{RXON|SCAN_CMD|TX_PWR_TABLE_CMD} time out after 500ms
2010-04-26 8:20 ` Sedat Dilek
@ 2010-04-26 16:08 ` reinette chatre
2010-04-26 16:31 ` Sedat Dilek
0 siblings, 1 reply; 9+ messages in thread
From: reinette chatre @ 2010-04-26 16:08 UTC (permalink / raw)
To: sedat.dilek; +Cc: wireless, John Linville, Berg, Johannes
On Mon, 2010-04-26 at 01:20 -0700, Sedat Dilek wrote:
> I had only one issue with
> linux-image-2.6.34-rc4-115-gdc57da3_2.6.34-rc4-115-gdc57da3.20100424~iniza.1_i386.deb
> kernel:
>
> ...
> /var/log/syslog.1-Apr 25 13:33:11 seduxbox wpa_supplicant[1732]: WPA:
> Group rekeying completed with 00:04:0e:e4:00:3d [GTK=CCMP]
> /var/log/syslog.1:Apr 25 13:59:56 seduxbox kernel: [59184.500070] No
> probe response from AP 00:04:0e:e4:00:3d after 500ms, disconnecting.
> /var/log/syslog.1-Apr 25 13:59:56 seduxbox kernel: [59184.505044]
> cfg80211: Calling CRDA to update world regulatory domain
> /var/log/syslog.1-Apr 25 13:59:56 seduxbox wpa_supplicant[1732]:
> CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> /var/log/syslog.1-Apr 25 13:59:57 seduxbox kernel: [59185.717331]
> cfg80211: World regulatory domain updated:
> /var/log/syslog.1-Apr 25 13:59:57 seduxbox kernel: [59185.717337]
> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> /var/log/syslog.1-Apr 25 13:59:57 seduxbox kernel: [59185.717343]
> (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> /var/log/syslog.1-Apr 25 13:59:57 seduxbox kernel: [59185.717349]
> (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
> /var/log/syslog.1-Apr 25 13:59:57 seduxbox kernel: [59185.717355]
> (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
> /var/log/syslog.1-Apr 25 13:59:57 seduxbox kernel: [59185.717361]
> (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> /var/log/syslog.1-Apr 25 13:59:57 seduxbox kernel: [59185.717367]
> (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> /var/log/syslog.1-Apr 25 13:59:59 seduxbox wpa_supplicant[1732]:
> Trying to associate with 00:04:0e:e4:00:3d
> (SSID='g00gle-street-knows-my-SSID-and-where-I-live' freq=2442 MHz)
> /var/log/syslog.1-Apr 25 13:59:59 seduxbox kernel: [59187.753888]
> wlan0: authenticate with 00:04:0e:e4:00:3d (try 1)
> /var/log/syslog.1-Apr 25 13:59:59 seduxbox kernel: [59187.755614]
> wlan0: authenticated
> /var/log/syslog.1-Apr 25 13:59:59 seduxbox kernel: [59187.755649]
> wlan0: associate with 00:04:0e:e4:00:3d (try 1)
> /var/log/syslog.1-Apr 25 13:59:59 seduxbox kernel: [59187.760216]
> wlan0: RX AssocResp from 00:04:0e:e4:00:3d (capab=0x411 status=0
> aid=1)
> /var/log/syslog.1-Apr 25 13:59:59 seduxbox kernel: [59187.760221]
> wlan0: associated
> /var/log/syslog.1-Apr 25 13:59:59 seduxbox wpa_supplicant[1732]:
> Associated with 00:04:0e:e4:00:3d
> /var/log/syslog.1-Apr 25 13:59:59 seduxbox wpa_supplicant[1732]: WPA:
> Key negotiation completed with 00:04:0e:e4:00:3d [PTK=CCMP GTK=CCMP]
> /var/log/syslog.1-Apr 25 13:59:59 seduxbox wpa_supplicant[1732]:
> CTRL-EVENT-CONNECTED - Connection to 00:04:0e:e4:00:3d completed
> (reauth) [id=0 id_str=]
> ...
Sorry ... but could you please point out what the issue is above? I do
see that at one point the station's testing of AP communication
fails ... but that can happen for many reasons and does not indicate a
bug. Was there some other logs that pointed out an issue during this
time?
Reinette
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: iwl3945: Error sending REPLY_{RXON|SCAN_CMD|TX_PWR_TABLE_CMD} time out after 500ms
2010-04-26 16:08 ` reinette chatre
@ 2010-04-26 16:31 ` Sedat Dilek
2010-04-26 16:42 ` reinette chatre
0 siblings, 1 reply; 9+ messages in thread
From: Sedat Dilek @ 2010-04-26 16:31 UTC (permalink / raw)
To: reinette chatre; +Cc: wireless, John Linville, Berg, Johannes
I tested both .34-git4 kernels half a day and this was the only
problem I saw in the my system-logs.
BTW, the WLAN connection did not crash as described in the initial
bug-report (logs see [1]).
At that time, I had to coldstart my machine - this was not the case
last weekend while testing.
- Sedat -
[1] http://files.iniza.org/BUG_iwl3945_20100417/logs/
On Mon, Apr 26, 2010 at 6:08 PM, reinette chatre
<reinette.chatre@intel.com> wrote:
> On Mon, 2010-04-26 at 01:20 -0700, Sedat Dilek wrote:
>> I had only one issue with
>> linux-image-2.6.34-rc4-115-gdc57da3_2.6.34-rc4-115-gdc57da3.20100424~iniza.1_i386.deb
>> kernel:
>>
>> ...
>> /var/log/syslog.1-Apr 25 13:33:11 seduxbox wpa_supplicant[1732]: WPA:
>> Group rekeying completed with 00:04:0e:e4:00:3d [GTK=CCMP]
>> /var/log/syslog.1:Apr 25 13:59:56 seduxbox kernel: [59184.500070] No
>> probe response from AP 00:04:0e:e4:00:3d after 500ms, disconnecting.
>> /var/log/syslog.1-Apr 25 13:59:56 seduxbox kernel: [59184.505044]
>> cfg80211: Calling CRDA to update world regulatory domain
>> /var/log/syslog.1-Apr 25 13:59:56 seduxbox wpa_supplicant[1732]:
>> CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
>> /var/log/syslog.1-Apr 25 13:59:57 seduxbox kernel: [59185.717331]
>> cfg80211: World regulatory domain updated:
>> /var/log/syslog.1-Apr 25 13:59:57 seduxbox kernel: [59185.717337]
>> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
>> /var/log/syslog.1-Apr 25 13:59:57 seduxbox kernel: [59185.717343]
>> (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
>> /var/log/syslog.1-Apr 25 13:59:57 seduxbox kernel: [59185.717349]
>> (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
>> /var/log/syslog.1-Apr 25 13:59:57 seduxbox kernel: [59185.717355]
>> (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
>> /var/log/syslog.1-Apr 25 13:59:57 seduxbox kernel: [59185.717361]
>> (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
>> /var/log/syslog.1-Apr 25 13:59:57 seduxbox kernel: [59185.717367]
>> (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
>> /var/log/syslog.1-Apr 25 13:59:59 seduxbox wpa_supplicant[1732]:
>> Trying to associate with 00:04:0e:e4:00:3d
>> (SSID='g00gle-street-knows-my-SSID-and-where-I-live' freq=2442 MHz)
>> /var/log/syslog.1-Apr 25 13:59:59 seduxbox kernel: [59187.753888]
>> wlan0: authenticate with 00:04:0e:e4:00:3d (try 1)
>> /var/log/syslog.1-Apr 25 13:59:59 seduxbox kernel: [59187.755614]
>> wlan0: authenticated
>> /var/log/syslog.1-Apr 25 13:59:59 seduxbox kernel: [59187.755649]
>> wlan0: associate with 00:04:0e:e4:00:3d (try 1)
>> /var/log/syslog.1-Apr 25 13:59:59 seduxbox kernel: [59187.760216]
>> wlan0: RX AssocResp from 00:04:0e:e4:00:3d (capab=0x411 status=0
>> aid=1)
>> /var/log/syslog.1-Apr 25 13:59:59 seduxbox kernel: [59187.760221]
>> wlan0: associated
>> /var/log/syslog.1-Apr 25 13:59:59 seduxbox wpa_supplicant[1732]:
>> Associated with 00:04:0e:e4:00:3d
>> /var/log/syslog.1-Apr 25 13:59:59 seduxbox wpa_supplicant[1732]: WPA:
>> Key negotiation completed with 00:04:0e:e4:00:3d [PTK=CCMP GTK=CCMP]
>> /var/log/syslog.1-Apr 25 13:59:59 seduxbox wpa_supplicant[1732]:
>> CTRL-EVENT-CONNECTED - Connection to 00:04:0e:e4:00:3d completed
>> (reauth) [id=0 id_str=]
>> ...
>
> Sorry ... but could you please point out what the issue is above? I do
> see that at one point the station's testing of AP communication
> fails ... but that can happen for many reasons and does not indicate a
> bug. Was there some other logs that pointed out an issue during this
> time?
>
> Reinette
>
>
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: iwl3945: Error sending REPLY_{RXON|SCAN_CMD|TX_PWR_TABLE_CMD} time out after 500ms
2010-04-26 16:31 ` Sedat Dilek
@ 2010-04-26 16:42 ` reinette chatre
2010-04-26 17:04 ` Sedat Dilek
0 siblings, 1 reply; 9+ messages in thread
From: reinette chatre @ 2010-04-26 16:42 UTC (permalink / raw)
To: sedat.dilek; +Cc: wireless, John Linville, Berg, Johannes
On Mon, 2010-04-26 at 09:31 -0700, Sedat Dilek wrote:
> I tested both .34-git4 kernels half a day and this was the only
> problem I saw in the my system-logs.
This may indicate a problem in your environment since it just says that
the station cannot communicate with the AP anymore. This occurs very
often in various environments. This does not indicate a bug.
> BTW, the WLAN connection did not crash as described in the initial
> bug-report (logs see [1]).
> At that time, I had to coldstart my machine - this was not the case
> last weekend while testing.
Either this issue is very hard to reproduce or it has been addressed
with a change introduced between the kernels you are testing. Can you
reproduce the issue when going back to earlier kernels? If so, then this
may be a candidate for a bisect for us to find out what fixed it.
Reinette
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: iwl3945: Error sending REPLY_{RXON|SCAN_CMD|TX_PWR_TABLE_CMD} time out after 500ms
2010-04-26 16:42 ` reinette chatre
@ 2010-04-26 17:04 ` Sedat Dilek
0 siblings, 0 replies; 9+ messages in thread
From: Sedat Dilek @ 2010-04-26 17:04 UTC (permalink / raw)
To: reinette chatre; +Cc: wireless, John Linville, Berg, Johannes
On Mon, Apr 26, 2010 at 6:42 PM, reinette chatre
<reinette.chatre@intel.com> wrote:
> On Mon, 2010-04-26 at 09:31 -0700, Sedat Dilek wrote:
>> I tested both .34-git4 kernels half a day and this was the only
>> problem I saw in the my system-logs.
>
> This may indicate a problem in your environment since it just says that
> the station cannot communicate with the AP anymore. This occurs very
> often in various environments. This does not indicate a bug.
>
>> BTW, the WLAN connection did not crash as described in the initial
>> bug-report (logs see [1]).
>> At that time, I had to coldstart my machine - this was not the case
>> last weekend while testing.
>
> Either this issue is very hard to reproduce or it has been addressed
> with a change introduced between the kernels you are testing. Can you
> reproduce the issue when going back to earlier kernels? If so, then this
> may be a candidate for a bisect for us to find out what fixed it.
>
The kernel (with patches) is identical to the one from 20100417, so
what shall I bisect?
With same kernel-config, etc.
But in the meantime I upgraded my system - it could be that some other
package(s) fixed the magic.
Other idea could be some temporarily occured disturbance in WLAN
connection and/or in streaming on the websites I visited.
- Sedat -
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2010-04-26 17:04 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-04-17 14:05 iwl3945: Error sending REPLY_{RXON|SCAN_CMD|TX_PWR_TABLE_CMD} time out after 500ms Sedat Dilek
2010-04-20 16:54 ` reinette chatre
2010-04-21 7:06 ` Sedat Dilek
2010-04-21 20:50 ` reinette chatre
2010-04-26 8:20 ` Sedat Dilek
2010-04-26 16:08 ` reinette chatre
2010-04-26 16:31 ` Sedat Dilek
2010-04-26 16:42 ` reinette chatre
2010-04-26 17:04 ` Sedat Dilek
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).