Comment 86 for bug 477169

Is this with the newer -15 kernel update? Can you confirm the same problem occurs with -14? Using my method I've successfully restored normal booting ability for -14 and any kernels I've built from the sources associated with that kernel version.

I have not yet tested -15, so I'd like to rule out whether or not you're seeing this same error with -14, which would mean it has nothing to do with this newer kernel.