[coLinux-users] Colinux blue screen crashes

[Bob W. <bwh...@my...>]

Hi:

 

I have been having problems with blue screen crashes when running colinux.
They are usually  memory corruptions, irql too high, corrupt page table
list. The just started when I tried to get ndis bridge mode networking
working on Portable Ubuntu which uses colinux. I never had any crashes when
using the slirp mode networking.  Also, I never have any crashes when
colinux is not running.

 

Many dumps had Kaspersky driver active at the time of crash.

Kaspersky support has analyzed the dump and say that their driver

Is not causing the problem.  So to prove it, I uninstalled Kaspersky and
used their clean up utility to removed all components, and registry items.

It still crashed with memory corruption but this time the active module was
nt .  The windbg output of this dump is:

 

kd> !analyze -v

****************************************************************************
***

*
*

*                        Bugcheck Analysis
*

*
*

****************************************************************************
***

 

IRQL_NOT_LESS_OR_EQUAL (a)

An attempt was made to access a pageable (or completely invalid) address at
an

interrupt request level (IRQL) that is too high.  This is usually

caused by drivers using improper addresses.

If a kernel debugger is available get the stack backtrace.

Arguments:

Arg1: 9ded4804, memory referenced

Arg2: 00000002, IRQL

Arg3: 00000000, value 0 = read operation, 1 = write operation

Arg4: 804eb3b5, address which referenced memory

 

Debugging Details:

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

 

 

READ_ADDRESS:  9ded4804 

 

CURRENT_IRQL:  2

 

FAULTING_IP: 

nt!MiDeletePte+15b

804eb3b5 8b420c          mov     eax,dword ptr [edx+0Ch]

 

CUSTOMER_CRASH_COUNT:  3

 

DEFAULT_BUCKET_ID:  DRIVER_FAULT

 

BUGCHECK_STR:  0xA

 

TRAP_FRAME:  f1c03aec -- (.trap fffffffff1c03aec)

ErrCode = 00000000

eax=038202ff ebx=c000430c ecx=012b5655 edx=9ded47f8 esi=835d2fe8
edi=000fffff

eip=804eb3b5 esp=f1c03b60 ebp=f1c03b84 iopl=0         nv up ei pl nz na pe
nc

cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000
efl=00010206

nt!MiDeletePte+0x15b:

804eb3b5 8b420c          mov     eax,dword ptr [edx+0Ch]
ds:0023:9ded4804=????????

Resetting default scope

 

LAST_CONTROL_TRANSFER:  from 804eb3b5 to 804e1892

 

STACK_TEXT:  

f1c03aec 804eb3b5 badb0d00 9ded47f8 873c63e8 nt!KiTrap0E+0x233

f1c03b84 804eb6fe c000430c 010c3000 00000000 nt!MiDeletePte+0x15b

f1c03c48 804f1d7c e122a614 010c9fff 00000000
nt!MiDeleteVirtualAddresses+0x162

f1c03cf4 8057a7c3 860fcb80 861acd00 f1c03d64 nt!MiRemoveMappedView+0x212

f1c03d38 8057a86f 85f21218 85eb8ee8 00000000 nt!MiUnmapViewOfSection+0x12b

f1c03d54 804de7ec ffffffff 860fcb80 008beeec nt!NtUnmapViewOfSection+0x54

f1c03d54 7c90e514 ffffffff 860fcb80 008beeec nt!KiFastCallEntry+0xf8

WARNING: Frame IP not in any known module. Following frames may be wrong.

008beeec 00000000 00000000 00000000 00000000 0x7c90e514

 

 

STACK_COMMAND:  kb

 

FOLLOWUP_IP: 

nt!MiDeletePte+15b

804eb3b5 8b420c          mov     eax,dword ptr [edx+0Ch]

 

SYMBOL_STACK_INDEX:  1

 

FOLLOWUP_NAME:  MachineOwner

 

MODULE_NAME: nt

 

DEBUG_FLR_IMAGE_TIMESTAMP:  4ea6ba87

 

SYMBOL_NAME:  nt!MiDeletePte+15b

 

IMAGE_NAME:  memory_corruption

 

FAILURE_BUCKET_ID:  0xA_nt!MiDeletePte+15b

 

BUCKET_ID:  0xA_nt!MiDeletePte+15b

 

Followup: MachineOwner

---------

I am using the stable snapshot of colinux dated 2/16/11

Linux version 2.6.33.7-co-0.7.9 (hn@hn-dt) (gcc version 4.4.1
[gcc-4_4-branch revision 150839] (SUSE Linux) ) #1 PREEMPT Wed Feb 16
23:51:21 UTC 2011

 

The linux config file:

 

kernel=vmlinux

ro

initrd=initrd.gz

setcobd=async

cobd0="F:\P_Ubuntu\Portable_Ubuntu_V4\images\rootfs.img"

cofs0="F:\P_Ubuntu\Portable_Ubuntu_V4"

cofs1="C:\DOCUME~1\RANGER~1\LOCALS~1\Temp"

root=/dev/cobd0

cobd1="C:\DOCUME~1\RANGER~1\LOCALS~1\Temp\swap.img"

hdc=\Device\Cdrom0

cofs2=c:\

exec0="F:\P_Ubuntu\Portable_Ubuntu_V4\pulseaudio\pulseaudio.exe"

mem=384

eth0=ndis-bridge,"Local Area Connection",00:ff:75:39:D3:C2

 

This crash is fairly easy to create immediately when using XEMACS for
editing. However, it takes longer to crash if you are just surfing the web.

 

Since this is a memory corruption the program/driver active at the time of
the crash is the victim of the corruption and it is likely some other
driver/program caused it, in this case colinux.

 

How to I submit a problem report on this and what additional information
does the Colinux team need to solve this problem?  

 

Thanks for your help.

Regards

Bob