Re: FINALLY caught a panic

["Robert L. Harris" <Robert.L.Harris@rdlg.net>]

[-- Attachment #1: Type: text/plain, Size: 2704 bytes --]

Thus spake Zwane Mwaikambo (zwane@arm.linux.org.uk):

> On Tue, 5 Aug 2003, Robert L. Harris wrote:
> 
> > Unable to handle kernel paging request at virtual address 8011c560
> >  printing eip:
> > 8011c560
> > *pde = 00000000
> > Oops: 0000
> > CPU:    1
> > EIP:    0010:[<8011c560>]    Not tainted
> > EFLAGS: 00010286
> > eax: 8011c560   ebx: c037f754   ecx: 00000040   edx: c0357980
> > esi: 00000040   edi: c037f740   ebp: c037ef40   esp: c1e19f28
> > ds: 0018   es: 0018   ss: 0018
> > Process swapper (pid: 0, stackpage=c1e19000)
> > Stack: c011c47d 00000001 c0358180 00000001 fffffffe 00000040 c011c1ff c0358180 
> >        c037ef40 c0351800 00000000 c1e19f74 00000046 c0108bdb c0105400 c1e18000 
> >        c0105400 00000040 c02f5b44 00000000 c010ae78 c0105400 c1e18000 c1e18000 
> > Call Trace: [<c011c47d>] [<c011c1ff>] [<c0108bdb>] [<c0105400>] [<c0105400>] 
> >    [<c010ae78>] [<c0105400>] [<c0105400>] [<c010542c>] [<c01054a2>] [<c0117e7f>] 
> >    [<c0117d8e>] 
> > 
> > Code:  Bad EIP value.
> >  <0>Kernel panic: Aiee, killing interrupt handler!
> > In interrupt handler - not syncing
> 
> Could have been someone removing a module without unregistering an 
> interrupt handler. But that's just guessing.
> 
> > Can someone please tell me what this means or how to figure it out?  The
> > machine is offline for the next 12 hours unfortunately due to lack of
> > remote help.  I do have similar machines with the same kernel/hardware
> > if I need to run any commands against this output.  I don't have access
> > to any specific files on the machine though.
> 
> You don't specify which kernel this is, it appears to be 2.4 something. 
> Please run this through ksymoops (man ksymoops)
> 
> -- 
> function.linuxpower.ca


This is 2.4.18 with the 2.6.5 i2c modules.  The only modules enabled are
for the i2c and everything else is compiled in static.  There was no-one
on the box the times when it went down and no messages about modules 
being messed with either.  I have about 30 of the servers out in the
wild all 99.9% identicle and there is only 1 having this issue which is
why my first thought it hardware.

This week I'm upgrading the puppies to 2.4.21-ac4 with the 2.8 i2c.

Robert

:wq!
---------------------------------------------------------------------------
Robert L. Harris                     | GPG Key ID: E344DA3B
                                         @ x-hkp://pgp.mit.edu
DISCLAIMER:
      These are MY OPINIONS ALONE.  I speak for no-one else.

Life is not a destination, it's a journey.
  Microsoft produces 15 car pileups on the highway.
    Don't stop traffic to stand and gawk at the tragedy.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]