|Fedora Test Days|
|Kdump Test Day|
|Date||27 March 2012|
|Mail • Subscribe • Archives|
What to test?
Today's installment of Fedora Test Day will focus on the system-config-kdump tool. Kdump is a graphical user interface that allows the user to configure kernel crash dumping via kdump and kexec.
More information about Kdump can be found at the Kdump page.
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- IRC channel - #fedora-test-day
- Development - Dave Young (daveyoung)
- Quality Assurance - Chao Wang (ChaoWang)
Prerequisite for Test Day
The following prerequisites are recommended:
How to test?
If you do not wish to alter your computer's existing software, you may download a non-destructive live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here. The "Desktop" image is preferred.
Please perform as many of the test cases below as you can, and fill out the results table at the bottom of the page:
If you have problems with any of the tests, report a bug to Bugzilla usually for the system-config-kdump. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to the four required configuration files from your system as shown in the 'Sample User' entry. For each test case, use the result template to enter your result, as shown in the example result line.
|User||Configure Files||Default||Halt||Shell||Reboot||NFS||SSH Filter||Debug Mem||Crasher Bug||Pre Extra Bins Modules||Post Extra Bins Modules|
|Wang Chao||kdump.conf /proc/meminfo /proc/cmdline|
|User:jskladan||Gave up after 2 hours of watching 'frozen' system |