Send Crash-utility mailing list submissions to crash-utility(a)redhat.com To subscribe or unsubscribe via the World Wide Web, visit https://www.redhat.com/mailman/listinfo/crash-utility or, via email, send a message with subject or body 'help' to crash-utility-request(a)redhat.com You can reach the person managing the list at crash-utility-owner(a)redhat.com When replying, please edit your Subject line so it is more specific than "Re: Contents of Crash-utility digest..." Today's Topics: 1. netdump issue (Anirudh Srinivasan) 2. RE: netdump issue (Vaughn Clinton) 3. Re: netdump issue (Dave Anderson) 4. Re: netdump issue (Jeff Moyer) 5. [PATCH] crash: unwind with LKCD_KERNTYPES (Cliff Wickman) 6. Re: [PATCH] crash: unwind with LKCD_KERNTYPES (Dave Anderson) 7. Fwd: [PATCH] crash: unwind with LKCD_KERNTYPES (Dave Anderson) ---------------------------------------------------------------------- Message: 1 Date: Thu, 22 Jan 2009 16:23:19 -0500 From: Anirudh Srinivasan <srianirudh(a)gmail.com&gt; Subject: [Crash-utility] netdump issue To: crash-utility(a)redhat.com Message-ID: <699b436a0901221323h2d6f0c13u1490a27235a7f776(a)mail.gmail.com&gt; Content-Type: text/plain; charset="iso-8859-1" I am implementing a netdump . I crashed one sever and got the vmcore file in /var/crash/vmcore , then i checked the kernel version through strings vmcore | fgrep -m1 'Linux' Linux version 2.4.21-40.ELsmp (bhcompile(a)hs20-bc1-7.build.redhat.com) (gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-54)) #1 SMP Thu Feb 2 22:22:39 EST 2006 So now while installing the kernel-debuginfo , it should match the version above i.e something like "kernel-debuginfo.2.4.21.40.ELsmp.i368.rpm" But i installed the closest one and that was kernel-debuginfo.2.4.21.40.EL.i386.rpm but after installing them i should have /usr/lib/debug/module/vmlinux , which i could'nt see them . Can anyone give me the link to the rpm i am looking for , or suggest some idea. ( the server that i am dumping vmcore is version 5 ) I have bunch of server with version 2 and version 3 and version 4 in my production environment for which i have to configure netdump to collect the vmcore in version 5 server . -- Regards Anirudh Srinivasan -------------- next part -------------- An HTML attachment was scrubbed... URL: https://www.redhat.com/archives/crash-utility/attachments/20090122/45ea77... ------------------------------ Message: 2 Date: Thu, 22 Jan 2009 14:27:56 -0700 From: Vaughn Clinton <vclinton(a)msn.com&gt; Subject: RE: [Crash-utility] netdump issue To: <crash-utility(a)redhat.com&gt; Message-ID: <BAY103-W660A296BC102A4E779286CECE0(a)phx.gbl&gt; Content-Type: text/plain; charset="iso-8859-1" Version 5 servers now use kexec with a kdump facility mechanism that will allow for remote dumping of the core. I'm not sure if netdump is functionally supported in your version of the kernel. Cheers, Date: Thu, 22 Jan 2009 16:23:19 -0500 From: srianirudh(a)gmail.com To: crash-utility(a)redhat.com Subject: [Crash-utility] netdump issue I am implementing a netdump . I crashed one sever and got the vmcore file in /var/crash/vmcore , then i checked the kernel version through strings vmcore | fgrep -m1 'Linux' Linux version 2.4.21-40.ELsmp (bhcompile(a)hs20-bc1-7.build.redhat.com) (gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-54)) #1 SMP Thu Feb 2 22:22:39 EST 2006 So now while installing the kernel-debuginfo , it should match the version above i.e something like "kernel-debuginfo.2.4.21.40.ELsmp.i368.rpm" But i installed the closest one and that was kernel-debuginfo.2.4.21.40.EL.i386.rpm but after installing them i should have /usr/lib/debug/module/vmlinux , which i could'nt see them . Can anyone give me the link to the rpm i am looking for , or suggest some idea. ( the server that i am dumping vmcore is version 5 ) I have bunch of server with version 2 and version 3 and version 4 in my production environment for which i have to configure netdump to collect the vmcore in version 5 server . -- Regards Anirudh Srinivasan _________________________________________________________________ Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friend... -------------- next part -------------- An HTML attachment was scrubbed... URL: https://www.redhat.com/archives/crash-utility/attachments/20090122/d22dc3... ------------------------------ Message: 3 Date: Thu, 22 Jan 2009 17:01:34 -0500 (EST) From: Dave Anderson <anderson(a)redhat.com&gt; Subject: Re: [Crash-utility] netdump issue To: "Discussion list for crash utility usage, maintenance and development" <crash-utility(a)redhat.com&gt; Message-ID: < 393446605.1264831232661693989.JavaMail.root(a)zmail02.collab.prod.int.phx2.redhat.com > Content-Type: text/plain; charset=utf-8 ----- "Anirudh Srinivasan" <srianirudh(a)gmail.com&gt; wrote: > I am implementing a netdump . I crashed one sever and got the vmcore > file in /var/crash/vmcore , then i checked the kernel version through > > strings vmcore | fgrep -m1 'Linux' > Linux version 2.4.21-40.ELsmp ( bhcompile(a)hs20-bc1-7.build.redhat.com > ) (gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-54)) #1 SMP Thu Feb > 2 22:22:39 EST 2006 > > So now while installing the kernel-debuginfo , it should match the > version above i.e something like > "kernel-debuginfo.2.4.21.40.ELsmp.i368.rpm" > > But i installed the closest one and that was > kernel-debuginfo.2.4.21.40.EL.i386.rpm but after installing them i > should have /usr/lib/debug/module/vmlinux , which i could'nt see them > . OK, so you're running -- and have crashed -- a RHEL3 i686 smp kernel, and the vmcore pinpoints the version as version 2.4.21-40.ELsmp. So you need to install the kernel-debuginfo-2.4.21-40.EL.i686.rpm (not the "i386" version), which contains the vmlinux debug files for that kernel version: $ rpm -qpl kernel-debuginfo-2.4.21-40.EL.i686.rpm | grep vmlinux /usr/lib/debug/boot/vmlinux-2.4.21-40.EL.debug /usr/lib/debug/boot/vmlinux-2.4.21-40.ELhugemem.debug /usr/lib/debug/boot/vmlinux-2.4.21-40.ELsmp.debug $ And the relevant file in your case would be located in /usr/lib/debug/boot/vmlinux-2.4.21-40.ELsmp.debug. > > Can anyone give me the link to the rpm i am looking for , or suggest > some idea. ( the server that i am dumping vmcore is version 5 ) > > I have bunch of server with version 2 and version 3 and version 4 in > my production environment for which i have to configure netdump to > collect the vmcore in version 5 server . That's fine -- one way you can get the specific debuginfo package you need is by going to my people page: http://people.redhat.com/anderson 1. Click on the "Red Hat Enterprise Linux debuginfo RPMs" link. 2. On that next page, in the "Red Hat Enterprise Linux 3" box, click on the "AS: i386" link. That will bring you to the ftp site that contains *all* RHEL3 packages, so you have to search for: kernel-debuginfo-2.4.21-40.EL.i686.rpm Again, make sure you get the "i686" version. Hope this helps, Dave ------------------------------ Message: 4 Date: Thu, 22 Jan 2009 17:09:57 -0500 From: Jeff Moyer <jmoyer(a)redhat.com&gt; Subject: Re: [Crash-utility] netdump issue To: "Discussion list for crash utility usage\, maintenance and development" <crash-utility(a)redhat.com&gt; Message-ID: <x49sknbdmbu.fsf(a)segfault.boston.devel.redhat.com&gt; Content-Type: text/plain; charset=us-ascii Anirudh Srinivasan <srianirudh(a)gmail.com&gt; writes: > I am implementing a netdump . I crashed one sever and got the vmcore file in > /var/crash/vmcore , then i checked the kernel version through > > strings vmcore | fgrep -m1 'Linux' > Linux version 2.4.21-40.ELsmp (bhcompile(a)hs20-bc1-7.build.redhat.com) (gcc > version 3.2.3 20030502 (Red Hat Linux 3.2.3-54)) #1 SMP Thu Feb 2 22:22:39 > EST 2006 > So now while installing the kernel-debuginfo , it should match the version > above i.e something like "kernel-debuginfo.2.4.21.40.ELsmp.i368.rpm" > > But i installed the closest one and that was > kernel-debuginfo.2.4.21.40.EL.i386.rpm but after installing them i should > have /usr/lib/debug/module/vmlinux , which i could'nt see them . Not quite right. If you do: # rpm -qpl kernel-debuginfo-2.4.21-40.EL.i686.rpm | grep vmlinux you'll see: /usr/lib/debug/boot/vmlinux-2.4.21-40.EL.debug /usr/lib/debug/boot/vmlinux-2.4.21-40.ELhugemem.debug /usr/lib/debug/boot/vmlinux-2.4.21-40.ELsmp.debug You, of course, want the smp version. I'm assuming you want to examine the core file with crash. If so, something like the following should work: crash /usr/lib/debug/boot/vmlinux-2.4.21-40.ELsmp.debug /path/to/vmcore > Can anyone give me the link to the rpm i am looking for , or suggest some > idea. ( the server that i am dumping vmcore is version 5 ) You mean the netdump server is running on a RHEL 5 system? That is fine. > I have bunch of server with version 2 and version 3 and version 4 in my > production environment for which i have to configure netdump to collect the > vmcore in version 5 server . Right, running the netdump server on a RHEL 5 system is fine. You should have no problems collecting vmcores from your AS 2.1, RHEL 3 and RHEL 4 systems. Cheers, Jeff ------------------------------ Message: 5 Date: Thu, 22 Jan 2009 17:23:44 -0600 From: Cliff Wickman <cpw(a)sgi.com&gt; Subject: [Crash-utility] [PATCH] crash: unwind with LKCD_KERNTYPES To: crash-utility(a)redhat.com Message-ID: <E1LQ8tk-0002yp-6Q(a)eag09.americas.sgi.com&gt; This patch enables stack unwind (on ia64) when using a kerntypes file for a namelist. When using a kerntypes file, we have just the address of variable unw and the definition of an unw structure. As you can see, I didn't change the indentation of the normal code. Simple to do, but I didn't want to clutter this patch for a first pass. I tested this against a live 2.6.16 (sles) kernel. Diffed against crash-4.0-7.6 Signed-off-by: Cliff Wickman <cpw(a)sgi.com&gt; --- unwind.c | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) Index: crash-4.0-7.6.ia64/unwind.c =================================================================== --- crash-4.0-7.6.ia64.orig/unwind.c +++ crash-4.0-7.6.ia64/unwind.c @@ -1395,10 +1395,43 @@ unwind_init_v2(void) unwind_init_v3(void) #endif { + int len; struct gnu_request request, *req; req = &request; + if (LKCD_KERNTYPES()) { + if ((len = STRUCT_SIZE("unw")) == 0) { + error(WARNING, + "cannot determine unw.tables offset; no struct unw\n"); + machdep->flags |= UNW_OUT_OF_SYNC; + return; + } + machdep->machspec->unw_tables_offset = + MEMBER_OFFSET("unw", "tables"); + if (MEMBER_EXISTS("unw", "r0")) + machdep->flags |= UNW_R0; + /* + * no verification of save_order, sw_off, preg_index as + * we're purely depending on the structure definition. + */ + if (MEMBER_EXISTS("unw", "pt_regs_offsets")) { + machdep->machspec->unw_pt_regs_offsets = + MEMBER_OFFSET("unw", "pt_regs_offsets") - + machdep->machspec->unw_tables_offset; + machdep->machspec->unw_kernel_table_offset = + MEMBER_OFFSET("unw", "kernel_table") - + machdep->machspec->unw_tables_offset; + machdep->flags |= UNW_PTREGS; + } + if (!load_unw_table(CLEAR_SCRIPT_CACHE)) { + error(WARNING, + "unwind_init: cannot read kernel unw table\n"); + machdep->flags |= UNW_OUT_OF_SYNC; + } + machdep->machspec->unw = (void *)&unw; + /* fall to common structure size verifications */ + } else { if (get_symbol_type("unw", "tables", req) == TYPE_CODE_UNDEF) { /* * KLUDGE ALERT: @@ -1449,6 +1482,7 @@ unwind_init_v3(void) machdep->machspec->unw = (void *)&unw; } + } verify_common_struct("unw_frame_info", sizeof(struct unw_frame_info)); verify_common_struct("unw_table", sizeof(struct unw_table)); ------------------------------ Message: 6 Date: Fri, 23 Jan 2009 10:09:30 -0500 (EST) From: Dave Anderson <anderson(a)redhat.com&gt; Subject: [Crash-utility] Re: [PATCH] crash: unwind with LKCD_KERNTYPES To: Cliff Wickman <cpw(a)sgi.com&gt; Cc: crash-utility(a)redhat.com Message-ID: < 2143976042.1441431232723370347.JavaMail.root(a)zmail02.collab.prod.int.phx2.redhat.com > Content-Type: text/plain; charset=utf-8 ----- "Cliff Wickman" <cpw(a)sgi.com&gt; wrote: > This patch enables stack unwind (on ia64) when using a kerntypes > file for a namelist. > > When using a kerntypes file, we have just the address of variable unw > and the definition of an unw structure. > > As you can see, I didn't change the indentation of the normal code. Nicely segregated. But instead of leaving the indentation screwed up, I just inserted a "goto verify" at the bottom of your if statement and put the label at the proper location. > Simple to do, but I didn't want to clutter this patch for a first > pass. With that in place, should I just take the patch for the next release, or did you have something else you want to add? Dave > > --- > unwind.c | 34 ++++++++++++++++++++++++++++++++++ > 1 file changed, 34 insertions(+) > > Index: crash-4.0-7.6.ia64/unwind.c > =================================================================== > --- crash-4.0-7.6.ia64.orig/unwind.c > +++ crash-4.0-7.6.ia64/unwind.c > @@ -1395,10 +1395,43 @@ unwind_init_v2(void) > unwind_init_v3(void) > #endif > { > + int len; > struct gnu_request request, *req; > > req = &request; > > + if (LKCD_KERNTYPES()) { > + if ((len = STRUCT_SIZE("unw")) == 0) { > + error(WARNING, > + "cannot determine unw.tables offset; no struct unw\n"); > + machdep->flags |= UNW_OUT_OF_SYNC; > + return; > + } > + machdep->machspec->unw_tables_offset = > + MEMBER_OFFSET("unw", "tables"); > + if (MEMBER_EXISTS("unw", "r0")) > + machdep->flags |= UNW_R0; > + /* > + * no verification of save_order, sw_off, preg_index as > + * we're purely depending on the structure definition. > + */ > + if (MEMBER_EXISTS("unw", "pt_regs_offsets")) { > + machdep->machspec->unw_pt_regs_offsets = > + MEMBER_OFFSET("unw", "pt_regs_offsets") - > + machdep->machspec->unw_tables_offset; > + machdep->machspec->unw_kernel_table_offset = > + MEMBER_OFFSET("unw", "kernel_table") - > + machdep->machspec->unw_tables_offset; > + machdep->flags |= UNW_PTREGS; > + } > + if (!load_unw_table(CLEAR_SCRIPT_CACHE)) { > + error(WARNING, > + "unwind_init: cannot read kernel unw table\n"); > + machdep->flags |= UNW_OUT_OF_SYNC; > + } > + machdep->machspec->unw = (void *)&unw; > + /* fall to common structure size verifications */ > + } else { > if (get_symbol_type("unw", "tables", req) == TYPE_CODE_UNDEF) > { > /* > * KLUDGE ALERT: > @@ -1449,6 +1482,7 @@ unwind_init_v3(void) > > machdep->machspec->unw = (void *)&unw; > } > + } > > verify_common_struct("unw_frame_info", sizeof(struct > unw_frame_info)); > verify_common_struct("unw_table", sizeof(struct unw_table)); ------------------------------ Message: 7 Date: Fri, 23 Jan 2009 10:35:06 -0500 (EST) From: Dave Anderson <anderson(a)redhat.com&gt; Subject: [Crash-utility] Fwd: [PATCH] crash: unwind with LKCD_KERNTYPES To: "Discussion list for crash utility usage, maintenance and development" <crash-utility(a)redhat.com&gt; Message-ID: < 947707277.1449411232724906430.JavaMail.root(a)zmail02.collab.prod.int.phx2.redhat.com > Content-Type: text/plain; charset=utf-8 ----- Forwarded Message ----- From: "Cliff Wickman" <cpw(a)sgi.com&gt; To: "Dave Anderson" <anderson(a)redhat.com&gt; Sent: Friday, January 23, 2009 10:30:49 AM GMT -05:00 US/Canada Eastern Subject: Re: [PATCH] crash: unwind with LKCD_KERNTYPES Hi Dave, On Fri, Jan 23, 2009 at 10:09:30AM -0500, Dave Anderson wrote: > > ----- "Cliff Wickman" <cpw(a)sgi.com&gt; wrote: > > > This patch enables stack unwind (on ia64) when using a kerntypes > > file for a namelist. > > > > When using a kerntypes file, we have just the address of variable unw > > and the definition of an unw structure. > > > > As you can see, I didn't change the indentation of the normal code. > > Nicely segregated. But instead of leaving the indentation screwed up, > I just inserted a "goto verify" at the bottom of your if statement and > put the label at the proper location. > > > Simple to do, but I didn't want to clutter this patch for a first > > pass. > > With that in place, should I just take the patch for the next release, > or did you have something else you want to add? Sounds good. I have nothing more to add. Thanks. -Cliff > > Dave > > > > > > --- > > unwind.c | 34 ++++++++++++++++++++++++++++++++++ > > 1 file changed, 34 insertions(+) > > > > Index: crash-4.0-7.6.ia64/unwind.c > > =================================================================== > > --- crash-4.0-7.6.ia64.orig/unwind.c > > +++ crash-4.0-7.6.ia64/unwind.c > > @@ -1395,10 +1395,43 @@ unwind_init_v2(void) > > unwind_init_v3(void) > > #endif > > { > > + int len; > > struct gnu_request request, *req; > > > > req = &request; > > > > + if (LKCD_KERNTYPES()) { > > + if ((len = STRUCT_SIZE("unw")) == 0) { > > + error(WARNING, > > + "cannot determine unw.tables offset; no struct unw\n"); > > + machdep->flags |= UNW_OUT_OF_SYNC; > > + return; > > + } > > + machdep->machspec->unw_tables_offset = > > + MEMBER_OFFSET("unw", "tables"); > > + if (MEMBER_EXISTS("unw", "r0")) > > + machdep->flags |= UNW_R0; > > + /* > > + * no verification of save_order, sw_off, preg_index as > > + * we're purely depending on the structure definition. > > + */ > > + if (MEMBER_EXISTS("unw", "pt_regs_offsets")) { > > + machdep->machspec->unw_pt_regs_offsets = > > + MEMBER_OFFSET("unw", "pt_regs_offsets") - > > + machdep->machspec->unw_tables_offset; > > + machdep->machspec->unw_kernel_table_offset = > > + MEMBER_OFFSET("unw", "kernel_table") - > > + machdep->machspec->unw_tables_offset; > > + machdep->flags |= UNW_PTREGS; > > + } > > + if (!load_unw_table(CLEAR_SCRIPT_CACHE)) { > > + error(WARNING, > > + "unwind_init: cannot read kernel unw table\n"); > > + machdep->flags |= UNW_OUT_OF_SYNC; > > + } > > + machdep->machspec->unw = (void *)&unw; > > + /* fall to common structure size verifications */ > > + } else { > > if (get_symbol_type("unw", "tables", req) == TYPE_CODE_UNDEF) > > { > > /* > > * KLUDGE ALERT: > > @@ -1449,6 +1482,7 @@ unwind_init_v3(void) > > > > machdep->machspec->unw = (void *)&unw; > > } > > + } > > > > verify_common_struct("unw_frame_info", sizeof(struct > > unw_frame_info)); > > verify_common_struct("unw_table", sizeof(struct unw_table)); -- Cliff Wickman Silicon Graphics, Inc. cpw(a)sgi.com (651) 683-3824 ------------------------------ -- Crash-utility mailing list Crash-utility(a)redhat.com https://www.redhat.com/mailman/listinfo/crash-utility End of Crash-utility Digest, Vol 40, Issue 11 *********************************************