From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Nathan <lists@netdigix.com>
Cc: keepalived-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Kernel panic issues
Date: Sun, 5 Sep 2004 17:05:27 -0700 [thread overview]
Message-ID: <20040905170527.4d2e079c.rddunlap@osdl.org> (raw)
In-Reply-To: <1094411544.413b65185bdba@mail.dreamtoy.net>
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:[<c012609d>] 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: [<c01f6b5e>] [<f887afe3>] [<c01fa090>] [<f887ae58>] [<f887ae58>]
| [<c0107ee0>] [<c010806f>] [<c0125f2c>] [<c0231d11>] [<c02320c8>]
| [<c0207b60>]
| [<f887b4ef>] [<c010806f>] [<c0207b60>] [<c02010b7>] [<c0207b60>]
| [<c02079f5>]
| [<c0207b60>] [<c01fa40b>] [<c01fa4ad>] [<c01fa5bf>] [<c011552b>]
| [<c010809d>]
| [<c0105260>] [<c0105260>] [<c0105260>] [<c0105260>] [<c0105286>]
| [<c01052f9>]
| [<c0105000>] [<c010502a>]
|
| 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
next prev parent reply other threads:[~2004-09-06 0:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 19:12 Nathan
2004-09-06 0:05 ` Randy.Dunlap [this message]
2004-09-06 23:40 ` Marcelo Tosatti
2004-10-15 14:44 ` Marcelo Tosatti
2004-09-07 11:26 ` Herbert Poetzl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040905170527.4d2e079c.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=keepalived-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@netdigix.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®