After some time suffering this bug and some additional investigation, this issue has been solved by loading the defaults of the laptop's firmware configuration.
It looks like that the kernel started paying attention to what was configured in the UEFI, and the UEFI config was hosed. I hope this bug report can help other people with similar issues. Cheers!
