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

Re: Unable to handle kernel paging request at virtual address c3018000



Hello Nick,

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

actually himem.sys is an executable file and it should look like
garbled text

NEM> debian:~# Unable to handle kernel paging request at virtual address c3018000 current->tss.cr3 = 00101000, %cr3 = 00101000
NEM> *pde = 00000000
NEM> Oops: 0002
NEM> CPU:        0
NEM> EIP:         0010:[<c01128f0>]
NEM> EFLAGS:    00010046
NEM> eax: c3018000    ebx: c2019f20    ecx: 00000246    edx: c3018000
NEM> esi: c0112928    edi: c02dbf40    ebp: c02dbf18    esp: c02dbf20
NEM> ds: 0018    es: 0018    ss: 0018
NEM> Process swapper (pid: 0, process nr: 0, stackpage=c02db000)
NEM> Stack: c02dbf44    c01139a5    c3018000    00000001    c0322f34    00000000    00000001    00000000
NEM> 00000000    c02dvf5c    c011a8a9    00000000    c02da000    00002916    c010b325    aaaaffe0
NEM> c010aff0    00000000    c02da000    00000000    c02da000    00002916    aaaaffe0    00000000
NEM> Call Trace: [<c01139a5>] [<c011a8a9>] [<c010b325>] [<c010aff8>] [<c010893d>] [<c0106008>] [<c0108960>]
NEM>         [<c010a1e0>] [<c0106000>] [<c010607b>] [<c0106000>] [<c0100175>]
NEM> Code: c7 02 00 00 00 00 83 7a 3c 00 75 28 a1 3c a0 2d c0 c7 42 40
NEM> Aiee, killing interrupt handler
NEM> Kernel panic: Attempted to kill the idle tast!
NEM> In swapper task - not syncing

this seems to be a low level error

I have only just started learning about this stuff but it appears to
be having trouble swapping memory pages (maybe) a corrupt kernel or
damaged ram could cause this.

a new mother board isnt likely to help

im quite possibly wrong, as i said i only just started with this stuff
so please let me know if im off the mark



-- 
Best regards,
 Michael
 
Subtlety is the art of saying what you think and getting out of the way before it is understood.


-- 
To UNSUBSCRIBE, email to debian-laptop-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: