[14:29] <srp> sometime ago, a new kernel was automatically installed which did not boot. I resorted to booting the previous kernel version, but when 14.04 comes out I'd like to do a dist-upgrade and I'm concerned the upgrade will also render my machine unbootable under the new Ubuntu. Can anyone help me figure out what's wrong with the kernel? . So far, I have looked at the syslogs when booting both the broken and the working kernel, but could not spot the reason why it
[14:29] <srp>  does not boot. Any hints on what to look for?
[15:59] <lfrlucas> Hi. I had experiencied this NFS error 3 or 4 times, after some weeks of uptime: lockd: server zeus not responding, still trying
[15:59] <lfrlucas> ubuntu 14.04
[16:00] <lfrlucas> nfs clients show this message, and the only solution is to reboot nfs server (zeus)
[16:00] <lfrlucas> any idea? it seems an kernel related bug...
[19:35] <dannas> http://pastebin.com/qW3chdas
[19:36] <dannas> I'm trying to build a custom kernel from the the latest change in Torvalds tree,
[19:36] <dannas> End up with "Unable to mount root fs",
[19:36] <dannas> (see pastebin above for the instructions I've executed)
[19:37] <dannas> Question 1: Is there some obvious step missing when I try to build the kernel?
[19:37] <dannas> I've followed the instructions in https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
[19:38] <dannas> My first theory: initramfs image missing. But I it's present in /boot (see pastebin above).
[19:40] <dannas> Second theory: wrong boot-opts are passed to the initramfs script (trying to figure out how to troubleshoot that, I had hoped that I would be given a rescue shell by the initramfs enviroment, but that doesn't happen).
[19:55] <dannas> Hm, CONFIG_BLK_DEV_INITRD is not set. (but a initrd is still present in /boot) I'll redo the steps once more; this time copying my current config instead of using make localmodconfig