Sorry for the crappy format (laptop is stuck). If the problem is the firmware why does it start working when I restart the router? Plus, I should be seeing this problem with other APs. And what could Windows be doing differently that doesn't exhibit this problem? On 11/2/13, Krishna Chaitanya <chaitanya.mgit@xxxxxxxxx> wrote: > On Sat, Nov 2, 2013 at 11:16 AM, Felipe Contreras > <felipe.contreras@xxxxxxxxx> wrote: >> >> On Tue, Oct 29, 2013 at 8:23 AM, Krishna Chaitanya >> <chaitanya.mgit@xxxxxxxxx> wrote: >> > On Tue, Oct 29, 2013 at 3:02 AM, Felipe Contreras >> > <felipe.contreras@xxxxxxxxx> wrote: >> >> >> Yes, but maybe I overrode the file. I've pushed a new one again. The >> >> sha-1 is 36c260d8d8c171a24eb1aa7b2ea736b06c9b55b7. >> >> >> > Thanks, able to decode now. I am not familiar with the >> > iwlwifi code, but let me give it a try. >> >> Did you find anything? > > Not Much, i could see the below pattern repeating > > wpa_supplicant-6915 [003] 5610.786592: drv_return_void: phy1 > wpa_supplicant-6915 [003] 5610.786594: drv_sta_state: phy1 > vif:wlan0(2) sta:e0:1d:3b:46:82:a0 state: 0->1 > wpa_supplicant-6915 [003] 5610.786597: iwlwifi_dev_hcmd: > [0000:02:00.0] hcmd 0x18 (sync) > irq/44-iwlwifi-6803 [001] 5610.786632: iwlwifi_dev_rx: > [0000:02:00.0] RX cmd 0x18 > wpa_supplicant-6915 [003] 5610.786639: drv_return_int: phy1 - 0 > wpa_supplicant-6915 [003] 5610.786645: drv_mgd_prepare_tx: phy1 > vif:wlan0(2) > wpa_supplicant-6915 [003] 5610.786645: drv_return_void: phy1 > wpa_supplicant-6915 [003] 5610.786663: iwlwifi_dev_tx: > [0000:02:00.0] TX 1c (90 bytes) > irq/44-iwlwifi-6803 [001] 5610.788677: iwlwifi_dev_rx: > [0000:02:00.0] RX cmd 0x1c > irq/44-iwlwifi-6803 [001] 5610.788709: iwlwifi_dev_rx: > [0000:02:00.0] RX cmd 0xc0 > irq/44-iwlwifi-6803 [001] 5610.788710: iwlwifi_dev_rx: > [0000:02:00.0] RX cmd 0xc1 > kworker/u8:0-1459 [003] 5610.788730: drv_sta_state: phy1 > vif:wlan0(2) sta:e0:1d:3b:46:82:a0 state: 1->2 > kworker/u8:0-1459 [003] 5610.788732: drv_return_int: phy1 - 0 > kworker/u8:0-1459 [003] 5610.999549: drv_sta_state: phy1 > vif:wlan0(2) sta:e0:1d:3b:46:82:a0 state: 2->1 > kworker/u8:0-1459 [003] 5610.999553: drv_return_int: phy1 - 0 > kworker/u8:0-1459 [003] 5610.999553: drv_sta_state: phy1 > vif:wlan0(2) sta:e0:1d:3b:46:82:a0 state: 1->0 > kworker/u8:0-1459 [003] 5610.999554: drv_return_int: phy1 - 0 > > So We move from NONE to AUTH and then AUTH to NONE. iwlwifi_dev_tx is > transmistting 90 bytes packets > but auth request is only 43 bytes, could that be association request?? > If yes where is that getting dropped. > > So my guess is that we are sending the association request (CMD_TX), > but its never seen OTA, its lost some where in between. > Ball goes to the FW :-). > -- Felipe Contreras -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
