1 Dec 03:58
Re: [Ipw2100-devel] [PATCH] ipw2200: rework scan handling while associated
On Fri, 2008-11-28 at 17:31 +0800, Helmut Schaa wrote: > Hmm, I was able to reproduce the firmware looping endlessly reasonably > reliable (turned off the beacon-miss-cancels-scan-behaviour and increased the > scan watchdog timeout) and the ABORT_SCAN command was processed in that case > and canceled the scan which resulted in a > HOST_NOTIFICATION_STATUS_SCAN_COMPLETED notification with status 2 (not sure > if it really was 2). '2' is SCAN_COMPLETED_STATUS_ABORTED. > So, at least the failure I noticed here could be corrected > by aborting the scan instead of restarting the adapter. > > What about the following: > After the first scan timeout we try to cancel the scan and if that does not > succeed in a few seconds we can still restart the fw. A watchdog is used to prevent unpredictable firmware hangs. In your report, the firmware hang has a predictable pattern. We should focus on resolving the real problem than workaround this issue. > I see the timeout because the firmware will never stop scanning until either > the beacon miss notification cancels the scan or the IPW_SCAN_CHECK_WATCHDOG > timeout restarts the adapter. I already tried a scan timeout of 25 seconds but > the firmware insists on scanning the first passive channel (in my setup 52) > over and over again. >From what you are saying, it looks like we have a real bug here. Why the firmware keep sticking in the passive channel if dwell > beacon_interval? I didn't see this in our testing environment. Normally(Continue reading)
RSS Feed