Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267358AbUIFAGD (ORCPT ); Sun, 5 Sep 2004 20:06:03 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267354AbUIFAFt (ORCPT ); Sun, 5 Sep 2004 20:05:49 -0400 Received: from fw.osdl.org ([65.172.181.6]:23465 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S267367AbUIFAF0 (ORCPT ); Sun, 5 Sep 2004 20:05:26 -0400 Date: Sun, 5 Sep 2004 17:05:27 -0700 From: "Randy.Dunlap" To: Nathan Cc: keepalived-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org Subject: Re: Kernel panic issues Message-Id: <20040905170527.4d2e079c.rddunlap@osdl.org> In-Reply-To: <1094411544.413b65185bdba@mail.dreamtoy.net> References: <1094411544.413b65185bdba@mail.dreamtoy.net> Organization: OSDL X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; i386-vine-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2331 Lines: 54 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 | 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/