Created an attachment (id=332) [details]
dmesg

dmesg when enable debug=0x3fff

From scrub: 

logics_sbux	let's retry 625 w/ 1.0.3 final and see if Mohamed's re-entry 
patches helped.

Tried ipw2200 1.0.3, didn't see this bug. Seems it is fixed with re-entry 
patches. 

Mark the bug as fixed: verified.

the problem is still exist is 1.0.4.
FC3, 2.6.11

while true; do modprobe -r ipw2200;modprobe ipw2200;sleep 1;done

"failed to send SCAN_REQUEST_EXT command sometimes" will appear.

Can you try to reproduce with these scripts, and if you see the problem turn
debug level to 0x43fff and capture the debug log of the sequence that fails:

In console 1: Run the test
In console 2: rm output; touch output; tail -f output & while true; do dmesg -c
| tee -a output | grep failed && break; sleep 0.5; done

Created an attachment (id=396) [details]
dmesg for "fail to send SCAN_REQUEST_EXT" command

dmesg for commmand:
dmesg -c; while true;do modprobe -r ipw2200;modprobe ipw2200 debug=0x43fff;
sleep 1; dmesg -c >> dmesg.output; done

while this command executing, not only "fail to send SCAN_REQUEST_EXT",
sometimes "fail to send SSID command" and "fail to send TX_POWER command" etc.
will come out.

Created an attachment (id=405) [details]
Stop scan request during shutdown

A scan request was being scheduled during module unload; this patch attempts to
stop that from occurring by setting the STATUS_EXIT_PENDING bit on shutdown,
and keeping ipw_link_down() from rescheduling a scan if that bit is set.

The problem is fixed with James's patch.
Mark as fixed.

Has this patch been merged in?

Please don't mark as FIXED before the patch has been included upstream.

Patch is in 1.0.6

Mark as verified.