When I was seeing this issue before I made the bios config change, I did notice that when the wifi and/or bluetooth died it'd need a hard power down and start up rather than a reboot to get it properly working.
To test your query I just rebooted three times in a row, wireless came up, authenticated and got an IP each time, bluetooth was also visible and available to be used (though, as I'm on the train, I have no bluetooth device on hand to actually test it with) whereas, usually if it were broken, wifi & bluetooth would not show as available in the gnome interface or the terminal.
When I was seeing this issue before I made the bios config change, I did notice that when the wifi and/or bluetooth died it'd need a hard power down and start up rather than a reboot to get it properly working.
To test your query I just rebooted three times in a row, wireless came up, authenticated and got an IP each time, bluetooth was also visible and available to be used (though, as I'm on the train, I have no bluetooth device on hand to actually test it with) whereas, usually if it were broken, wifi & bluetooth would not show as available in the gnome interface or the terminal.