Yes, and I have a log up to the crash point.
If you leave the phone stuck it will eventually reboot on its own after some seconds.
great work! i'm no expert, but this is interesting.. especially these lines:
E/wpa_supplicant( 4720): wpa_driver_nl80211_driver_cmd: failed to issue private commands E/WifiHW ( 103): Failed to open wlan fw path param (No such file or directory) E/WifiStateMachine( 473): Failed to reload STA firmware java.lang.IllegalStateException: command '168 softap fwreload wlan0 STA' failed with '400 168 Softap operation failed (No such file or directory)' W/CommandListener( 103): Failed to retrieve HW addr for wlan0 (No such device) E/WifiStateMachine( 473): Unable to change interface settings: java.lang.IllegalStateException: command '170 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 170 Failed to set address (No such device)'
it looks as though the network interface just vanishes. i've had this on a linux box years ago, the solution was to *not* rfkill/ifconfig down the interface, the kernel module was buggy and it didn't like that. i don't know about android though, and our wireless hardware. it's certainly not a solution to leave the wifi always on..