This could be a udev bug, since the Saucy kernel boots fine on a Raring install. Adding that bug task. We would like to see if there is a kernel oops or error when the failure happens. From the BusyBox prompt, can you run the dmesg command and post the output?
This could be a udev bug, since the Saucy kernel boots fine on a Raring install. Adding that bug task. We would like to see if there is a kernel oops or error when the failure happens. From the BusyBox prompt, can you run the dmesg command and post the output?