From: Jason K. <ja...@cs...> - 2006-02-23 01:20:50
|
Will the version 1 of mkdump work on Linux 2.4.32? I'm faced with a problem where-by one of our Linux systems running 2.4.32 is crashing either every day (somtimes more than once in the day) or every second or third day. We replaced the hardware with an almost identical box while we did testing on the original hardware. We found the original hardware to be free from problems, and to our surprise the replacement hardware exhibited the same crashing behaviour! We have several other boxes running exactly the same kernel with slightly different hardware, and they don't seem to be crashing. This box is a time sharing server, so many users are running their programs here. We have identical boxes to this one running as back-end servers, and they don't crash. When the system "dies", the console is black and does not respond to keyboard input (screen blanking on the console is disabled), serial console gets no output, a process that we have running on the system capturing a "ps" every minute stops running. However, the system is pingable, and while it does not respond to ssh/telnet, we notice that an nmap of the server still lists the ports running services (and though you can connect to any of the ports, you don't get back anything). We were really hoping to be able to use mkdump somehow to solve our problems. The documentation for mkdump seemed to imply at least some compatibility with vanilla 2.4.27 which isn't much different from 2.4.32. If you, or anyone else has any suggestions on what we might do to resolve this problem, or how we could use any version of mkdump to do that, we would really appreciate it! Jason. On Thu, 23 Feb 2006, Itsuro Oda wrote: > Hi, > >> The comment: /* only support RHEL currently */ > right. > >> Will mkexec not work on stock 2.4.32? > no. > > Thanks. > > On Wed, 22 Feb 2006 14:44:52 -0500 > Jason Keltz <ja...@cs...> wrote: > >> Hi. >> I'm running Linux Kernel 2.4.32, and I would like to use mkdump to >> analyze why my system is crashing on a regular basis. I've downloaded >> the 2.1 package and got to the point where I'm building the mkexec >> kernel module, and I'm running into a problem where-by the code in >> mkexec_main.c in the mkexec_unload function ends up doing... >> >> #ifdef MKEXEC_NO_PATCH >> /* only support RHEL currently */ >> cmpxchg(&netdump_func, (unsigned long)do_minik_dump, (unsigned >> long)NULL >> ); >> >> ... but there is no netdump_func on the system. >> >> The comment: /* only support RHEL currently */ >> >> Will mkexec not work on stock 2.4.32? >> >> jas. >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files >> for problems? Stop! Download the new AJAX search engine that makes >> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 >> _______________________________________________ >> Mkdump-devel mailing list >> Mkd...@li... >> https://lists.sourceforge.net/lists/listinfo/mkdump-devel > > -- > Itsuro ODA <od...@va...> > > |