Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267840AbUIGL0Q (ORCPT ); Tue, 7 Sep 2004 07:26:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267841AbUIGL0Q (ORCPT ); Tue, 7 Sep 2004 07:26:16 -0400 Received: from MAIL.13thfloor.at ([212.16.62.51]:63973 "EHLO mail.13thfloor.at") by vger.kernel.org with ESMTP id S267840AbUIGL0N (ORCPT ); Tue, 7 Sep 2004 07:26:13 -0400 Date: Tue, 7 Sep 2004 13:26:12 +0200 From: Herbert Poetzl To: "Randy.Dunlap" Cc: Nathan , keepalived-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org, Denis Vlasenko Subject: Re: Kernel panic issues Message-ID: <20040907112612.GA16199@MAIL.13thfloor.at> Mail-Followup-To: "Randy.Dunlap" , Nathan , keepalived-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org, Denis Vlasenko References: <1094411544.413b65185bdba@mail.dreamtoy.net> <20040905170527.4d2e079c.rddunlap@osdl.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040905170527.4d2e079c.rddunlap@osdl.org> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2919 Lines: 69 On Sun, Sep 05, 2004 at 05:05:27PM -0700, Randy.Dunlap wrote: > On Sun, 5 Sep 2004 12:12:24 -0700 Nathan wrote: > > | Hi, I have a server running debian 3.0r1 kernel 2.4.25 and I get these kernel > | panic about 5 times this week. If anyone can tell me what it means it would be > | greatly appreciated. Any additional instructions on how to read kernel panic > | dumps would also be appreciated. > > Denis Vlasenko recently did a "howto find oops location" for 2.6.x, > but it's probably the best reference for you to look at. > It's here: > http://marc.theaimsgroup.com/?l=linux-kernel&m=109257016020612&w=2 hmm, very interesting and sure fun to do, but usually you can get away with doing addr2line -e vmlinux c012609d (might require CONFIG_DEBUG_KERNEL and recompile) HTH, Herbert > | asdasdkernel BUG as slab.c:1263! > | Invalid operand: 0000 > | CPU: 0 > | EIP: 0010:[] Not tainted > | EFLAGS: 00010012 > | eax: f31eafff ebx: c19ad700 ecx: 00000001 edx: 00000001 > | esi: f31ea800 edi: f31eabd3 ebp: c02cfca8 esp: c02cfc8c > | ds: 0018 es: 0018 ss: 0018 > | Process swapper (pid: 0, stackpage=c02cf000) > | Stack: f69657fc c03397e0 00000020 00000800 00012800 f31eabd3 00000246 c02cfcc4 > | c01f6b5e 0000065c 00000020 00000008 0000001c f74ec160 c02cfcf f887afe3 > | 00000620 00000020 00000008 0000001c f74ec160 c01fa090 00000000 f6ebec > | Call Trace: [] [] [] [] [] > | [] [] [] [] [] > | [] > | [] [] [] [] [] > | [] > | [] [] [] [] [] > | [] > | [] [] [] [] [] > | [] > | [] [] > | > | Code: 0f 0b ef 04 60 33 26 c0 8b 7d f4 f7 c7 00 04 00 00 74 36 b8 > | <0>Kernel panic: Aiee, Killing interrupt handler! > | In interrupt handler - not syncing > > The stack addresses are useless without associating some of (your) > kernel symbols with them. Please read REPORTING-BUGS in the top > level of the kernel source tree for full bug-reporting info, and see > Documentation/Changes on where to get 'ksymoops' if you don't > already have it, then run this panic message text thru ksymoops. > That should tell the function call chain to get to slab.c. > > -- > ~Randy > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/