Have you tried removing one (or more) of the memory chips and/or other
hardware to see if it is the cause?  Another idea might be an IRQ
conflict between the cards within the computer.  When I've seen these
types of problems in the past it has *usually* been related to hardware
going bad or otherwise doing Something It Shouldn't Be Doing.  While
hardware issues may not be the cause here, I think they deserve some
consideration.

I've been running custom kernels with woody without problem for quite a
long time.

Steve

===========================================================
= Steve Suehring, Editor - LinuxWorld                     =
= GPG: 82CC 4404 4C45 4EE9 C5FF  B373 C3E5 D2B7 25A8 2B8D =
= Home Page:  http://www.braingia.org/                    =
===========================================================

On Sun, Sep 05, 2004 at 12:50:07PM -0700, Nathan wrote:
> Hi I am running debian 3.0r1 kernel 2.4.25.  for the last couple of weeks I 
> keep getting these kernel panic and have to reboot.  The box is running as a 
> router with keepalived and ipvs.  If anyone can help debuggint his message it 
> is greatly appreciated.  (Any help on how to read these kinds of messages 
> would 
> also be greatly appreciated)
> 
> 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
> 
> 
> Thanks
> 
> - Brandon
> - http://www.netdigix.com
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Reply via email to