Re: RHEL4 Kernel Panic - capture dump?
On Mon, 2007-07-30 at 15:34 -0400, Brad Hinson wrote: Check out this presentation on linuxvm.org: Help! My (Virtual) Penguin Is Sick! http://linuxvm.org/present/SHARE108/S9248ps.pdf There's a section on VMDUMP, which will give you a kernel memory dump. You'll need to convert it using 'vmconvert', which is available in the s390utils package. This is assuming you're using DASD. If it's a zFCP-only setup, the process is a little different. Alternatively you can use DASD dump, which is included in zipl. To prepare a DASD dump disk you have to do the following: 1. Find/Create a DASD partition, which at least as big as your guest memory 2. Issue zipl: # zipl -d /dev/dasdxxxpartnumber To create the dump, you have to do the following on the VM console: 1. #cp cpu all stop 2. #cp store status 3. #cp i devno of DASD dump device -- Wait for disabled wait psw message, which indicates that the dump process completed. Then ipl your Linux again. To copy the dump into your filesystem issue: # zgetdump /dev/dasdxxxpartnumber mydump You can find more information in the dump tools book under: http://download.boulder.ibm.com/ibmdl/pub/software/dw/linux390/docu/l26bdt01.pdf Michael -- 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
Re: RHEL4 Kernel Panic - capture dump?
Yep, I get a need a disk object or some such similar error message. This is with Adobe Reader 7. K -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Morris, Kevin J. (LNG-DAY) Sent: Monday, July 30, 2007 5:09 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: RHEL4 Kernel Panic - capture dump? Hi Brad. Thanks for the response. When I try to open your link/pdf, I get error opening the document with adobe. Anyone else having this problem? -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Brad Hinson Sent: Monday, July 30, 2007 3:34 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: RHEL4 Kernel Panic - capture dump? Check out this presentation on linuxvm.org: Help! My (Virtual) Penguin Is Sick! http://linuxvm.org/present/SHARE108/S9248ps.pdf There's a section on VMDUMP, which will give you a kernel memory dump. You'll need to convert it using 'vmconvert', which is available in the s390utils package. This is assuming you're using DASD. If it's a zFCP-only setup, the process is a little different. -Brad On Mon, 2007-07-30 at 13:57 -0400, Morris, Kevin J. (LNG-DAY) wrote: We have a linux guest that frequently encounters a kernel panic, effectively killing the box. Thankfully, we have IBM Operations Manager and can trap the HCP message and instantly reboot the box once it hits the disabled wait state. 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? 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:1Not tainted 07/30/2007 05:49:55 Process chmod (pid: 15271, task: 5b94ccb0, ksp: 5eb1beb8) 07/30/2007 05:49:55 Krnl PSW : 07018000 0006cf98 (generic_file_aio_write+0x60/0x134 07/30/2007 05:49:55 07/30/2007 05:49:55 Ý0002ff7e¨ sysc_noemu+0x10/0x16 07/30/2007 05:49:55 Ý020c0700¨ 0x20c0700 07/30/2007 05:49:55 07/30/2007 05:49:55 0Kernel panic - not syncing: Fatal exception: panic_on_oops 07/30/2007 05:49:55 00: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop from CPU 01. 07/30/2007 05:49:55 01: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 00018A66 07/30/2007 05:49:55 CP SEND TPC3675 IPL CMS PARM AUTOCR Thanks, Kevin Morris LexisNexis, a division of Reed Elsevier Inc. z/OS System Engineering -- 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 -- Brad Hinson [EMAIL PROTECTED] Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 -- 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 -- 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 -- 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
RHEL4 Kernel Panic - capture dump?
We have a linux guest that frequently encounters a kernel panic, effectively killing the box. Thankfully, we have IBM Operations Manager and can trap the HCP message and instantly reboot the box once it hits the disabled wait state. 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? 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:1Not tainted 07/30/2007 05:49:55 Process chmod (pid: 15271, task: 5b94ccb0, ksp: 5eb1beb8) 07/30/2007 05:49:55 Krnl PSW : 07018000 0006cf98 (generic_file_aio_write+0x60/0x134 07/30/2007 05:49:55 07/30/2007 05:49:55 Ý0002ff7e¨ sysc_noemu+0x10/0x16 07/30/2007 05:49:55 Ý020c0700¨ 0x20c0700 07/30/2007 05:49:55 07/30/2007 05:49:55 0Kernel panic - not syncing: Fatal exception: panic_on_oops 07/30/2007 05:49:55 00: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop from CPU 01. 07/30/2007 05:49:55 01: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 00018A66 07/30/2007 05:49:55 CP SEND TPC3675 IPL CMS PARM AUTOCR Thanks, Kevin Morris LexisNexis, a division of Reed Elsevier Inc. z/OS System Engineering -- 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
Re: RHEL4 Kernel Panic - capture dump?
Check out this presentation on linuxvm.org: Help! My (Virtual) Penguin Is Sick! http://linuxvm.org/present/SHARE108/S9248ps.pdf There's a section on VMDUMP, which will give you a kernel memory dump. You'll need to convert it using 'vmconvert', which is available in the s390utils package. This is assuming you're using DASD. If it's a zFCP-only setup, the process is a little different. -Brad On Mon, 2007-07-30 at 13:57 -0400, Morris, Kevin J. (LNG-DAY) wrote: We have a linux guest that frequently encounters a kernel panic, effectively killing the box. Thankfully, we have IBM Operations Manager and can trap the HCP message and instantly reboot the box once it hits the disabled wait state. 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? 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:1Not tainted 07/30/2007 05:49:55 Process chmod (pid: 15271, task: 5b94ccb0, ksp: 5eb1beb8) 07/30/2007 05:49:55 Krnl PSW : 07018000 0006cf98 (generic_file_aio_write+0x60/0x134 07/30/2007 05:49:55 07/30/2007 05:49:55 Ý0002ff7e¨ sysc_noemu+0x10/0x16 07/30/2007 05:49:55 Ý020c0700¨ 0x20c0700 07/30/2007 05:49:55 07/30/2007 05:49:55 0Kernel panic - not syncing: Fatal exception: panic_on_oops 07/30/2007 05:49:55 00: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop from CPU 01. 07/30/2007 05:49:55 01: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 00018A66 07/30/2007 05:49:55 CP SEND TPC3675 IPL CMS PARM AUTOCR Thanks, Kevin Morris LexisNexis, a division of Reed Elsevier Inc. z/OS System Engineering -- 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 -- Brad Hinson [EMAIL PROTECTED] Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 -- 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
Re: RHEL4 Kernel Panic - capture dump?
Hi Brad. Thanks for the response. When I try to open your link/pdf, I get error opening the document with adobe. Anyone else having this problem? -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Brad Hinson Sent: Monday, July 30, 2007 3:34 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: RHEL4 Kernel Panic - capture dump? Check out this presentation on linuxvm.org: Help! My (Virtual) Penguin Is Sick! http://linuxvm.org/present/SHARE108/S9248ps.pdf There's a section on VMDUMP, which will give you a kernel memory dump. You'll need to convert it using 'vmconvert', which is available in the s390utils package. This is assuming you're using DASD. If it's a zFCP-only setup, the process is a little different. -Brad On Mon, 2007-07-30 at 13:57 -0400, Morris, Kevin J. (LNG-DAY) wrote: We have a linux guest that frequently encounters a kernel panic, effectively killing the box. Thankfully, we have IBM Operations Manager and can trap the HCP message and instantly reboot the box once it hits the disabled wait state. 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? 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:1Not tainted 07/30/2007 05:49:55 Process chmod (pid: 15271, task: 5b94ccb0, ksp: 5eb1beb8) 07/30/2007 05:49:55 Krnl PSW : 07018000 0006cf98 (generic_file_aio_write+0x60/0x134 07/30/2007 05:49:55 07/30/2007 05:49:55 Ý0002ff7e¨ sysc_noemu+0x10/0x16 07/30/2007 05:49:55 Ý020c0700¨ 0x20c0700 07/30/2007 05:49:55 07/30/2007 05:49:55 0Kernel panic - not syncing: Fatal exception: panic_on_oops 07/30/2007 05:49:55 00: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop from CPU 01. 07/30/2007 05:49:55 01: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 00018A66 07/30/2007 05:49:55 CP SEND TPC3675 IPL CMS PARM AUTOCR Thanks, Kevin Morris LexisNexis, a division of Reed Elsevier Inc. z/OS System Engineering -- 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 -- Brad Hinson [EMAIL PROTECTED] Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 -- 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 -- 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
Re: RHEL4 Kernel Panic - capture dump?
Weird...working now... Thanks for the help. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Brad Hinson Sent: Monday, July 30, 2007 3:34 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: RHEL4 Kernel Panic - capture dump? Check out this presentation on linuxvm.org: Help! My (Virtual) Penguin Is Sick! http://linuxvm.org/present/SHARE108/S9248ps.pdf There's a section on VMDUMP, which will give you a kernel memory dump. You'll need to convert it using 'vmconvert', which is available in the s390utils package. This is assuming you're using DASD. If it's a zFCP-only setup, the process is a little different. -Brad On Mon, 2007-07-30 at 13:57 -0400, Morris, Kevin J. (LNG-DAY) wrote: We have a linux guest that frequently encounters a kernel panic, effectively killing the box. Thankfully, we have IBM Operations Manager and can trap the HCP message and instantly reboot the box once it hits the disabled wait state. 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? 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:1Not tainted 07/30/2007 05:49:55 Process chmod (pid: 15271, task: 5b94ccb0, ksp: 5eb1beb8) 07/30/2007 05:49:55 Krnl PSW : 07018000 0006cf98 (generic_file_aio_write+0x60/0x134 07/30/2007 05:49:55 07/30/2007 05:49:55 Ý0002ff7e¨ sysc_noemu+0x10/0x16 07/30/2007 05:49:55 Ý020c0700¨ 0x20c0700 07/30/2007 05:49:55 07/30/2007 05:49:55 0Kernel panic - not syncing: Fatal exception: panic_on_oops 07/30/2007 05:49:55 00: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop from CPU 01. 07/30/2007 05:49:55 01: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 00018A66 07/30/2007 05:49:55 CP SEND TPC3675 IPL CMS PARM AUTOCR Thanks, Kevin Morris LexisNexis, a division of Reed Elsevier Inc. z/OS System Engineering -- 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 -- Brad Hinson [EMAIL PROTECTED] Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 -- 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 -- 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
Re: RHEL4 Kernel Panic - capture dump?
I was able to see/print the pdf. Betsie -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Morris, Kevin J. (LNG-DAY) Sent: Monday, July 30, 2007 2:09 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: RHEL4 Kernel Panic - capture dump? Hi Brad. Thanks for the response. When I try to open your link/pdf, I get error opening the document with adobe. Anyone else having this problem? -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Brad Hinson Sent: Monday, July 30, 2007 3:34 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: RHEL4 Kernel Panic - capture dump? Check out this presentation on linuxvm.org: Help! My (Virtual) Penguin Is Sick! http://linuxvm.org/present/SHARE108/S9248ps.pdf There's a section on VMDUMP, which will give you a kernel memory dump. You'll need to convert it using 'vmconvert', which is available in the s390utils package. This is assuming you're using DASD. If it's a zFCP-only setup, the process is a little different. -Brad On Mon, 2007-07-30 at 13:57 -0400, Morris, Kevin J. (LNG-DAY) wrote: We have a linux guest that frequently encounters a kernel panic, effectively killing the box. Thankfully, we have IBM Operations Manager and can trap the HCP message and instantly reboot the box once it hits the disabled wait state. 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? 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:1Not tainted 07/30/2007 05:49:55 Process chmod (pid: 15271, task: 5b94ccb0, ksp: 5eb1beb8) 07/30/2007 05:49:55 Krnl PSW : 07018000 0006cf98 (generic_file_aio_write+0x60/0x134 07/30/2007 05:49:55 07/30/2007 05:49:55 Ý0002ff7e¨ sysc_noemu+0x10/0x16 07/30/2007 05:49:55 Ý020c0700¨ 0x20c0700 07/30/2007 05:49:55 07/30/2007 05:49:55 0Kernel panic - not syncing: Fatal exception: panic_on_oops 07/30/2007 05:49:55 00: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop from CPU 01. 07/30/2007 05:49:55 01: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 00018A66 07/30/2007 05:49:55 CP SEND TPC3675 IPL CMS PARM AUTOCR Thanks, Kevin Morris LexisNexis, a division of Reed Elsevier Inc. z/OS System Engineering -- 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 -- Brad Hinson [EMAIL PROTECTED] Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 -- 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 -- 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 -- 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
Re: RHEL4 Kernel Panic - capture dump?
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:1Not tainted 07/30/2007 05:49:55 Process chmod (pid: 15271, task: 5b94ccb0, ksp: 5eb1beb8) 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
