The root cause is that current broadcom wifi driver may change its mac address after downloading firmware, so
the initialized mac address is always different with the working address, which caused the network-manger
behaviour.
In theory, disabling ENABLE_INSMOD_NO_FW_LOAD may fix the problem, but cause another resume failure
problem, so still not solution for the problem now.
The root cause is that current broadcom wifi driver may change its mac address after downloading firmware, so
the initialized mac address is always different with the working address, which caused the network-manger
behaviour.
In theory, disabling ENABLE_ INSMOD_ NO_FW_LOAD may fix the problem, but cause another resume failure
problem, so still not solution for the problem now.