Crash Dump

Finally I caught the kernel panic caused by some strange bugs found in thread scheduling. Investigating the crashdump.

Before reporting this to the list, I would first gather enough information.

Alu’s server boxes is suffering in continued reboot when server is loaded. Because he is supporting FreeBSD by utilizing 5.3-RC1 in his production environment (and it’s moderately loaded as it is connected to the ChinaNet Backbone), and donated many devices for dedicated services of the FreeBSD China Community, I think we must help him to solve these out.

I have plugged a new kernel configuration on his box in order to obtain a (potential) crashdump and figure out what is happening. Maybe we will get it tomorrow.

From Microsoft’s KB:

You can configure Microsoft Windows 2000, Microsoft Windows XP, and Microsoft Windows Server 2003 to write debugging information to three different file formats (also known as memory dump files) when your computer stops unexpectedly as a result of a Stop error (also known as a “blue screen”, system crash, or bug check). You can also configure Windows not to write debugging information to a memory dump file. Windows can generate any one of the following three memory dump file types:

1. Complete memory dump
2. Kernel memory dump
3. Small memory dump (64 KB)