It must be normal. Server rebooted with no issues and vmcore file created.
For reference the server is a Dell R900 with 64GB RAM. >From initiating the kdump with "echo c > /proc/sysrq-trigger" to server back up and running with a vmcore file took a total of 35 minutes. Kind Regards Nick Lunt Managed Services and O/S Analyst Patech Solutions Limited Tel: 01543 444 707 Fax: 01543 444 709 Tame House, Fradley Park, Lichfield, Staffordshire, WS13 8RZ <http://www.patech-solutions.com/home.htm> www.patech-solutions.com From: [email protected] [mailto:[email protected]] On Behalf Of Nick Lunt Sent: 18 May 2009 15:40 To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list Subject: [rhelv5-list] Urgent: Kdump Hi We've had issues recently with kswapd consuming massive cpu resources. Redhat asked us to setup kdump to create a vmcore file for them. The system has just become unresponsive due to kswapd so I've initiated a kdump. Kdump kicked in fine, it started counting how much it had done, got to 40% and then the console screen went blank. And that's how it is now. Anyone run kdump before and know if this is normal ? Cheers Nick. __________ Information from ESET NOD32 Antivirus, version of virus signature database 4083 (20090518) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 4083 (20090518) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
_______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
