Paul on Wed, 26 Feb 2003 02:21:04 -0500


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] ARGH!!!!!!!!!


How much Googling have you done on this problem?

I tend to think it's a hardware problem. Start with the RAM; swap it out, or least reseat it, as a test. Then, I would suspect a drive or a drive controller, but it would be easier to check the removable cards such as NICs. Basically, you will need to do trial-and-error hardware removal until you find the problem.

What changed before the PC started to crash?


----- Original Message -----
From: "Dan Roberts" <fboston@hotmail.com>
To: <plug@lists.phillylinux.org>
Sent: Tuesday, February 25, 2003 7:44 PM
Subject: [PLUG] ARGH!!!!!!!!!




Ok folks, Im going to lay it out for you. My linux box is teetering on the
edge of getting thrown out the damn window with this freaking problem.
Lately it's been acting really strange. Randomly just not letting me log


on


(the screen goes black, screen saver like, and then never comes back, nor
can i log on remotely through ssh/telnet). Or, it will just crap out in


the


middle of a session. Or the kicker is this error message, which seems to
come at no particular time or for any conceivable reason. Brace
yourselves...

unable to handle kernel null pointer dereference at virtual address
000000000
current -> tss.cr3 = 00101000, %cr2 = 00101000
*pde = 00000000
Oops: 0002
CPU: 0
EIP: 0010:[<c01087e1>]
EFLAGS: 00010246
eax: 00000000 ebx: 00000000 ecx: c0234000 edx: 00000000
esi: c0234000 edi: 0000489b ebp: 000058e3 esp: c0235fa4
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 0, process nr: 0, stackpage=c0235000
Stack c0106000 c0108804 00000000 c0109f58 00000000 00000000 00000001
0009b800
     c0106000 000058e3 00000070 00000018 00000018 00000070 c010607b
00000010
     00000296 c0236d4f 00000000 c0106000 0fae21d8 c0216cc0 c0100175
Call trace: [<c0106000>] [<c01088004>] [<c0109f58>] [<c0106000>]
[<c010607h>]
[<c0106000>] [<c0100175>]
Code: 8b 5e 14 e8 7f 8a 00 00 e8 4a 22 01 00 eb b4 b8 00 e0 ff ff
Kernel panic: Attempted to kill the idle task!
In swapper task - not syncing


------------------------------------------

I have not a clue as to what the hell any of this means. I am running a
stock redhat 7.0 system, same kernel 2.2.16-22 on my Athlon 850, 256MB


ram,


2 3c905C 3com ethernet cards... I have reinstalled from discs, completely
formatting partitions, and the same result. I have experimented running
every service imaginable or barebones, and one of the above still takes
place. It even has happened after a very painful upgrade to 8.0. So now I


am


back to 7.0 again. Prior to this, the machine worked perfectly with the
exact same hardware setup, so I am at a loss.

If any of you out there either 1. know what the F this means and would


like


to tell me, or 2. just like computers so much that seeing mine fly out the
second story window would be more painful them comical, your assistance
would be much appreciated. My frustration is reaching "Falling Down"
level...............



_________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.netisland.net/mailman/listinfo/plug-announce General Discussion -- http://lists.netisland.net/mailman/listinfo/plug