Return-path: Received: from mail-wy0-f174.google.com ([74.125.82.174]:62755 "EHLO mail-wy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753768Ab0DZQb3 (ORCPT ); Mon, 26 Apr 2010 12:31:29 -0400 Received: by wyb42 with SMTP id 42so29628wyb.19 for ; Mon, 26 Apr 2010 09:31:28 -0700 (PDT) MIME-Version: 1.0 Reply-To: sedat.dilek@gmail.com In-Reply-To: <1272298097.4381.8765.camel@rchatre-DESK> References: <1271782442.14052.19698.camel@rchatre-DESK> <1271883056.4381.1743.camel@rchatre-DESK> <1272298097.4381.8765.camel@rchatre-DESK> Date: Mon, 26 Apr 2010 18:31:27 +0200 Message-ID: Subject: Re: iwl3945: Error sending REPLY_{RXON|SCAN_CMD|TX_PWR_TABLE_CMD} time out after 500ms From: Sedat Dilek To: reinette chatre Cc: wireless , John Linville , "Berg, Johannes" Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: 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 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 > > >