View previous topic :: View next topic |
Author |
Message |
nielchiano Veteran
Joined: 11 Nov 2003 Posts: 1287 Location: 50N 3E
|
Posted: Mon Nov 29, 2004 6:36 pm Post subject: how bad is this? (kernel partial lockup) |
|
|
Hi,
I'm administering a (remote) server; and just got a partial lockup... dmesg gave me this:
Code: | Unable to handle kernel paging request at virtual address 081ac4f8
printing eip:
c026a9c2
*pde = 06031067
*pte = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c026a9c2>] Not tainted
EFLAGS: 00010212
eax: dc14ec60 ebx: c15b1800 ecx: 00002075 edx: 000081d5
esi: 081ac4f8 edi: c2ed7000 ebp: e086bd64 esp: c1591e64
ds: 0018 es: 0018 ss: 0018
Process kupdated (pid: 7, stackpage=c1591000)
Stack: c15b1800 000013b2 00001000 00000006 e084d890 41ab69cc e08561dc 00000004
00000002 00000000 00000016 00000032 0000001d 0000138a de10a140 cdcabaa0
ce66c000 c52d2000 e086a33c c1591ed4 00000006 c15b1800 00000001 c0269cd9
Call Trace: [<c0269cd9>] [<c02573a4>] [<c01f53c1>] [<c01f4562>] [<c01f48df>]
[<c01b6318>] [<c01f47f0>] [<c01b469e>] [<c01f47f0>]
Code: f3 a5 f6 c2 02 74 02 66 a5 f6 c2 01 74 01 a4 ff 44 24 28 8b
|
How bad is this? I tried (remote) rebooting; but the shutdown proces just crashed: Code: |
root 7327 0.0 0.1 1544 596 ? D 19:31 0:00 shutdown -r 0 w
|
Anyone some ideas? Especialy on the cause;
And maybe a solution? (I only have SSH access; so "press the reset button" won't do) |
|
Back to top |
|
|
adaptr Watchman
Joined: 06 Oct 2002 Posts: 6730 Location: Rotterdam, Netherlands
|
Posted: Mon Nov 29, 2004 7:11 pm Post subject: |
|
|
It's a kernel panic - no way out except the big red button.
And yes, it's serious - either you have some bad RAM or you have messed up something in your kernel config.
How long has this box been running without any errors (that last is important!) ? _________________ >>> emerge (3 of 7) mcse/70-293 to /
Essential tools: gentoolkit eix profuse screen |
|
Back to top |
|
|
nielchiano Veteran
Joined: 11 Nov 2003 Posts: 1287 Location: 50N 3E
|
Posted: Mon Nov 29, 2004 7:16 pm Post subject: |
|
|
adaptr wrote: | It's a kernel panic - no way out except the big red button.
And yes, it's serious - either you have some bad RAM or you have messed up something in your kernel config.
How long has this box been running without any errors (that last is important!) ? |
It has been running for weeks; without a single issue (in dmesg)
I just tried a "cp /var/www/... /tmp/..." and it suddenly hanged.
Bad ram can be a posibility; but I ran memtest86 on it and it didn't report a single error... |
|
Back to top |
|
|
nielchiano Veteran
Joined: 11 Nov 2003 Posts: 1287 Location: 50N 3E
|
Posted: Mon Nov 29, 2004 7:27 pm Post subject: |
|
|
adaptr wrote: | no way out except the big red button. |
it's gray; but anyway. Isn't there a way to convince the processor to reset (unign linux-commands)? just RESET, without shutting down anything at all? |
|
Back to top |
|
|
dsd Developer
Joined: 30 Mar 2003 Posts: 2162 Location: nr London
|
Posted: Mon Nov 29, 2004 7:29 pm Post subject: |
|
|
it could also be a kernel bug or a hardware hiccup. unfortunately as you chose not to compile any debug symbols into your kernel, nobody will be able to tell which area of the kernel started the crash
i'd suggest you upgrade to the latest kernel and compile in debug symbols incase it happens again _________________ http://dev.gentoo.org/~dsd |
|
Back to top |
|
|
|