Hi there,

I just found that two strange behaviors in my laptop M9, I produce them 
after do enable/disable iwk0 and add/remove iwk0 from User ncp several 
times:
1) WLAN_SCAN_REPORT emits after iwk0 is destroyed. This is not a big 
issue since I can ignore wlan info if I can find the related NCU.

WLAN_SCAN_REPORT        
-                        1: -- ESSID OSD01 BSSID 
0:1f:33:b9:37:f6               
-                        2: -- ESSID sunwifi BSSID 
0:b:e:9c:d6:80               
-                        3: -- ESSID sunwifi BSSID 
0:b:e:9c:d8:0                
-                        4: -- ESSID CERNET BSSID 
0:5:12:c:4:d3                 
-                        5: -- ESSID HotZone Duo - 1 BSSID 
6:5:12:c:4:d3        
-                        6: -- ESSID  BSSID 
0:15:c7:82:76:40                    
-                        7: -- ESSID sunwifi BSSID 
0:b:e:9c:db:80               
-                        8: -- ESSID OSD03 BSSID 
0:1f:33:b5:9b:c4               
-                        9: -- ESSID ap10-3 BSSID 
0:f:24:19:b:80                
-                        10: -- ESSID abc BSSID 
2:19:d2:0:0:9a                  
-                        11: -- ESSID NECCN BSSID 
0:17:94:3b:84:d0              
-                        12: -- ESSID WLAN-01 BSSID 
fe:1d:45:1b:20:bf           
-                        13: S- ESSID linksys BSSID 
0:c:41:cc:cb:e3             
-                        14: -- ESSID  BSSID 
0:18:39:a5:12:f6                   
OBJECT_STATE             ncu link:iwk0 -> state offline*, connecting to 
WiFi net
OBJECT_ACTION            ncu link:e1000g0 -> action 
refresh                     
OBJECT_ACTION            ncu interface:iwk0 -> action 
destroy                   
OBJECT_ACTION            ncu link:iwk0 -> action 
destroy                        
WLAN_SCAN_REPORT        
-                        1: -- ESSID OSD01 BSSID 
0:1f:33:b9:37:f6               
-                        2: -- ESSID sunwifi BSSID 
0:b:e:9c:d6:80               
-                        3: -- ESSID sunwifi BSSID 
0:b:e:9c:d8:0                
-                        4: -- ESSID CERNET BSSID 
0:5:12:c:4:d3                 
-                        5: -- ESSID HotZone Duo - 1 BSSID 
6:5:12:c:4:d3        
-                        6: -- ESSID  BSSID 
0:15:c7:82:76:40                    
-                        7: -- ESSID sunwifi BSSID 
0:b:e:9c:db:80               
-                        8: -- ESSID OSD03 BSSID 
0:1f:33:b5:9b:c4               
-                        9: -- ESSID ap10-3 BSSID 
0:f:24:19:b:80                
-                        10: -- ESSID abc BSSID 
2:19:d2:0:0:9a                  
-                        11: -- ESSID NECCN BSSID 
0:17:94:3b:84:d0              
-                        12: -- ESSID WLAN-01 BSSID 
fe:1d:45:1b:20:bf           
-                        13: -- ESSID linksys BSSID 
0:c:41:cc:cb:e3             
-                        14: -- ESSID  BSSID 
0:18:39:a5:12:f6                   
OBJECT_ACTION            ncu link:e1000g0 -> action 
refresh                     

2) I found sometimes iwk0 will keep in the connecting state, e.g. 
connecting sunwifi. When it is in that state, after I disable iwk0 and 
re-enable iwk0 and re-launch GUI dialog (now there are two GUI 
processes, panel icon and dialog), I can see that they both block on 
something, I guess it's scanning wlan function call. And then one of 
them *can not* get the selected flag of sunwifi. So the two GUIs will 
show incompatible state for the same NCU. e.g. one is showing connecting 
to sunwifi, the other is unknown or whatever.

I'm not sure if 2 is GUI related bug currently, just ask first :-)

Any ideas about that?

Thanks,
lin

Reply via email to