lkml.org 
[lkml]   [2003]   [Mar]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Kernel Bug at spinlock.h ?!
On Mon, 3 Mar 2003, ChristopherHuhn wrote:

> Hi again,
>
> >>Sounds like possible memory corruption (can you vouch for the reliability
> >>of your RAM?) Might be worthwhile posting the oops in it's entirety. Is
> >>EIP normally in __run_timers? Do you run a heavy networking load?
> >>
> as apparently every machine in our farm is affected, I cannot believe in
> a corrupted memory. I've started to run memtest86 on a machine that just
> oopsed though, but it didn't find any errors (yet).
>
> >Feb 24 14:45:34 lxb006 kernel: ICH3: BIOS setup was incomplete.
> >
> Does this mean we should upgrade to 2.5?
>
> Kind regards,
>
> Christopher
>
>
> Here comes a complete oops that just occured:
>
> Unable to handle kernel NULL pointer dereference at virtual address 00000002
> priniting eip:
> e40e5cfc
> *pde: 00000000
> Oops: 0002
> Cpu: 0
> EIP: 0010:[<e40e5cfc>] Not tainted
> EFLAGS: 00010246
> eax: 00000002 ebx: e40e5cfc ecx: c03f9208 edx: 00000000
> esi: e40e5cb0 edi: 00000001 ebp: d5d15cd0 esp: d5d15cbc
> ds: 0018 es: 0018 ss: 0018
> Process adsmcli (pid: 13223, stackpage=d5d15000)
> Stack: c02c6783 e40e5cb0 e40e4cb0 c02c66a0 0ac9682a d5d15d08 c012564b
> e40e5cb0
> 00000000 00000000 00000000 00000001 00000000 c03f9600 c041c30c c041c30c
> ...
> Call Trace: [<c02c6783>] [<c02c66a0>] [<c0125646>] [<c012139a>] [<c0121263>]
> [<c0120fdd>] [<c02a50dc>] [<c02a3c68>] [<c02abc50>] [<c027eec2>]
> [<c029c877>]
> ...
>
> Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 68 c9 0a
> <0> Kernel panic: Aiee, killing interrupt handler!
> In interrupt handler - not syncing
>

What does "Process adsmcli" do? Does it make any special system-calls
or does in interface with a particular driver? Whatever it's doing
may have triggered the event.

> Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 68 c9 0a
This code is not valid. Either some hardware burped or a pointer to
a function got corrupted, both quite likely RAM related.

The "Re: Kernel Bug at spinlock.h ?!" is an eye-catcher because this
inline code cannot have any bugs or you wouldn't even have booted.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.18 on an i686 machine (797.90 BogoMips).
Why is the government concerned about the lunatic fringe? Think about it.


-
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/

\
 
 \ /
  Last update: 2005-03-22 13:33    [W:0.122 / U:0.568 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site