From Fedora Project Wiki

No edit summary
Line 96: Line 96:
| [[User:jskladan]]
| [[User:jskladan]]
|  
|  
| Gave up after 2 hours of watching 'frozen' system
| Gave up after 2 hours of watching 'frozen' system <ref>{{bz|810881}}</ref>
 
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}  
| {{result|pass}}  

Revision as of 14:24, 9 April 2012

Fedora Test Days
Kdump Test Day

Date 27 March 2012
Time 8:00-20:00 UTC

Website QA/Fedora_17_test_days
IRC #fedora-test-day (webirc)
Mailing list test


Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

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.

Who's available

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?

Live image

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.

Test Cases

Please perform as many of the test cases below as you can, and fill out the results table at the bottom of the page:

  1. QA:Testcase_Kdump_Func_Default
  2. QA:Testcase_Kdump_Func_Halt
  3. QA:Testcase_Kdump_Func_Shell
  4. QA:Testcase_Kdump_Func_Reboot
  5. QA:Testcase_Kdump_Func_NFS
  6. QA:Testcase_Kdump_Func_SSH_Filter
  7. QA:Testcase_Kdump_Func_DebugMem
  8. QA:Testcase_Kdump_Func_CrasherBug
  9. QA:Testcase_Kdump_Func_Preextra_Bins_Modules
  10. QA:Testcase_Kdump_Func_Postextra_Bins_Modules

Test Results

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.

A minimum of 769MB of RAM is required to install Fedora 17 at present (this is a hardwired limit in the installer). If using a virtual machine, ensure that you configure it with at least this much memory.
/etc/kdump.conf,/proc/meminfo,/proc/cmdline can be pasted at http://www.pastebin.com .
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
Fail fail
[1]
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
User:jskladan Gave up after 2 hours of watching 'frozen' system [2]
Pass pass
Pass pass

References

  1. RHBZ #806251
  2. RHBZ #810881