Gave up waiting for root device.

Yestoday, in order to analysis the core dump information which is a result of my bugged device driver, I configurate and make the kernel according to "Documentation/kdump/kdump.txt" in linux source code and today, I reboot the system with "crashkernel=64M@16M". The system cannot boot now and display the following information:

Gave up waiting for root device. Common problems:
-Boot args (cat /proc/cmdline)
-Check rootdelay= (did the system wait long enough?)
-Check root= (did the system wait for the right device?)
-Missing modules (cat /proc/modules; ls /dev)
Alert! /dev/disk/by-uuid/99339357-923a-4cfb-a288-6336c7499359 does not exist. Dorpping to a shell!

BusyBox v1.13.3 (ubuntu 1:1.13.3-1ubuntu11) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)

what should I do to boot the system?
what do these information mean?

thanks!
li,kunlun

---------- Post updated at 01:35 AM ---------- Previous update was at 01:23 AM ----------

Hi, all:

Additionally, my system is linux 3.0.4 on x86.

li,kunlun

---------- Post updated 11-12-11 at 12:44 AM ---------- Previous update was 11-11-11 at 01:35 AM ----------

I have already recovered the system successfully!
How should I boot the system kernel with the boot parameter "crashkernel=64M@16M"? Is this like :
"reboot crashkernel=64M@16M"
Whether can it lead to a system crash or not? How should I avoid the system crash?

li,kunlun

---------- Post updated at 12:44 AM ---------- Previous update was at 12:44 AM ----------

I have already recovered the system successfully!
How should I boot the system kernel with the boot parameter "crashkernel=64M@16M"? Is this like :
"reboot crashkernel=64M@16M"
Whether can it lead to a system crash or not? How should I avoid the system crash?

li,kunlun

---------- Post updated at 12:44 AM ---------- Previous update was at 12:44 AM ----------

I have already recovered the system successfully!
How should I boot the system kernel with the boot parameter "crashkernel=64M@16M"? Is this like :
"reboot crashkernel=64M@16M"
Whether can it lead to a system crash or not? How should I avoid the system crash?

li,kunlun