Comment 2 for bug 1463120

As requested, I have now set package to "linux" (ie kernel) due to the point in the boot sequence at which the issue occurs. I'm far from qualified to speculate but I am reasonably sure that this is not a kernel issue but a boot script dependency issue, which was why I didn't specify a package initially. Hopefully someone can point me in the right direction?