Comment 33 for bug 1040557

The conclusion from the kernel team is already that it's not possible to work around this bug; and shim is *definitely* not the place for such a workaround to live because each revision of shim involves a round-trip to Microsoft. If anything's going to block the boot, it needs to be the kernel itself.

Since this bug is already assigned to the release notes, it's already on the release team radar AFAICS. But in any case, our best firmware people have already concluded there's nothing we can reasonably do here and the firmware just needs to get fixed.