>>> On Mon, Jul 30, 2007 at 1:57 PM, in message <[EMAIL PROTECTED]>, "Morris, Kevin J. (LNG-DAY)" <[EMAIL PROTECTED]> wrote: > We are running the latest RHEL4 maintenance on this guest and would > like to provide a dump to RedHat. How can we trigger/capture a dump when the > kernel panics?
You might want to see what RHEL support actually wants from you before generating a dump. It could be that the kernel messages you've got already will be all they need. > Below is the console log for this guest at the time of the panic: > > 07/30/2007 05:49:55 kernel BUG at mm/filemap.c:2245! > 07/30/2007 05:49:55 illegal operation: 0001 Ý#1* > 07/30/2007 05:49:55 CPU: 1 Not tainted > 07/30/2007 05:49:55 Process chmod (pid: 15271, task: 000000005b94ccb0, ksp: > 000000005eb1beb8) Interesting that a chmod would cause a kernel oops Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
