Kernel crashes on GeForce 8200 diskless client during boot

[Chris]

I am using mythbuntu and trying to boot an Intrepid client. Previously (in Hardy) the client would not boot at all since the eth0 link did not come up. This has been fixed in the new kernel version but shows a new bug.

During the boot sequence everything goes well and the NFS root is mounted. The message "Activating swapfile swap" is displayed then [OK] then the kernel panics.

"BUG: unable to handle kernel NULL pointer dereference at 0000000010"
"IP: [<f89dbeed>] :sunrpc:rpcauth_bindcred+0x1d/0f0"
"*pde = 00000000"
"Oops: 0000 [#1] SMP"
*stack trace*

I know this is a kernel bug, but I'm unsure where to report that exactly. Since this is a diskless client there is no way to retrieve the syslog without copying it from the screen so if any more information is required please request what you need as it takes ages to type out.

Hopefully someone can help with this nfs bug.

[Chris (chris-yourdreamnet)]

I have narrowed down the process now. Basically the error occurs when "mv" is called by the boot scripts. The strange thing is that the command works correctly and copies the log file over to the server and then it fails. It's very strange.

[Chris (chris-yourdreamnet)]

Ok, I commented out all the mv commands. This caused the system to boot past them without issue. Now it reached a gzip command and did the same kind of thing. This is definatly an issue with the nfs core. This time with nfs3_proc_setattr, so I'm not sure if the issue is lower level?

[laga (laga)]

This could also be a bug with AUFS.

Can you take a picture of the screen with a camera?

[Chris (chris-yourdreamnet)]

Here it is, but it's a terrible photo... sorry.

[laga (laga)]

Chris schrieb:
> Here it is, but it's a terrible photo... sorry.
>
> ** Attachment added: "DSC00183.JPG"
> http://launchpadlibrarian.net/18342118/DSC00183.JPG
>
>
Good enough for me. Can you find out the exact kernel version in the chroot?

[Chris (chris-yourdreamnet)]

2.6.27-6-generic

[laga (laga)]

Chris,

please try the latest kernel in your chroot. You will have to run sudo ltsp-update-kernels outside the chroot afterwards. Or just re-create your chroot :)