Just to confirm, can you boot back into v3.5.0-17 and confirm the bug is back. If it is, this issue would be due to an Ubuntu specific change in 3.5.0-17 since the 3.5.4 and 3.5.5 upstream kernels boot fine.
If the bug comes back in 3.5.0-17, I can perform a kernel bisect between 3.5.0-16 and 3.5.0-17. ** Tags added: performing-bisect -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065982 Title: [quantal] Unable to boot into 3.5.0-17 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs