|
Hi
I have a problem with possibly my CPU or memory on
my notebook, it wasn't caused by Debian, more likely from Windows as the problem
was there before I installed Debian. But I wanted to see if the same problem
hapenned under Debian and eventually it did.
I am using an old Toshiba Libretto 70CT
notebook with a Pentium 120MMX processor and 32MB ram and 1mb of graphics
memory. 16mb is onboard and cannot be removed.
When I first upgraded the machine from 16mb to 32mb
it immediately gave me a VxD error in Windows when shutting down with a Winmodem
in its PCMCIA socket. The only way around this was to remove the card before
shutting down or rebooting, this method worked for months and then one day the
machine would start to hang on blue screens with VxD erros when running windows
and there was no way to solve this problem unless I removed the
16mb upgrade.
From this point I assumed the 16mb upgrade was
faulty and replaced it with a new one, this seemed to be fine for about a
month then the same problem hapenned again. To loose two 16mb memory upgrades
must mean that the onboard memory is corrupt too I guess, this machine cannot be
used unless I remove the 16mb module and run it with only 16mb. In Windows himem.sys looks a mess, I have no idea what it
should look like but I guess it shouldn't be filled with garbled random
text.
Under Debian Woody I get as far as the login prompt
and then it reboots the machine. Once it got through the login and at
the prompt I got the following information when the machine
crashed.
debian:~# Unable to handle kernel paging request at
virtual address c3018000 current->tss.cr3 = 00101000, %cr3 =
00101000
*pde = 00000000
Oops: 0002
CPU:
0
EIP: 0010:[<c01128f0>]
EFLAGS: 00010046
eax: c3018000 ebx:
c2019f20 ecx: 00000246 edx:
c3018000
esi: c0112928 edi:
c02dbf40 ebp: c02dbf18 esp:
c02dbf20
ds: 0018 es:
0018 ss: 0018
Process swapper (pid: 0, process nr: 0,
stackpage=c02db000)
Stack: c02dbf44
c01139a5 c3018000 00000001
c0322f34 00000000 00000001
00000000
00000000
c02dvf5c c011a8a9 00000000
c02da000 00002916 c010b325
aaaaffe0
c010aff0
00000000 c02da000 00000000
c02da000 00002916 aaaaffe0
00000000
Call Trace: [<c01139a5>] [<c011a8a9>]
[<c010b325>] [<c010aff8>] [<c010893d>] [<c0106008>]
[<c0108960>]
[<c010a1e0>] [<c0106000>] [<c010607b>] [<c0106000>]
[<c0100175>]
Code: c7 02 00 00 00 00 83 7a 3c 00 75 28 a1 3c a0
2d c0 c7 42 40
Aiee, killing interrupt handler
Kernel panic: Attempted to kill the idle
tast!
In swapper task - not syncing
Is this a memory or CPU problem, I am no expert on
computer hardware but it does appear to be memory related. If memory becomes
unstable like this is there any way to fix it, possibly a piece of software
which can clean it out.
If not I have a replacement working
motherboard but I was hoping to find a way to fix this if there is
one.
Any thoughts or suggestions on what is going here
would be appreciated.
I know its my own fault, I should know better than
to buy second hand notebooks off ebay...duh!
Nick
|