Cooperative Linux

Paradise, dando pulos de alegria, escreveu :
> Hi all, 
> coLinux v.0.6.2 pre1 crashed (blue screen) on my windows xp pro sp2 (32 bit ver)
> however it doesnt crash on my athlonxp....
> 
> anyone is same as me? or anyone run it on athlon 64 with no problem? 

I guess you installed SP2. It's a known issue and will be corrected.
In the meanwhile, just disable DEP/NX if you intend to run colinux with
the Amd64 machine.

This can be accomplished by adding a /noexecute=AlwaysOff in your
boot.ini, as documented here:
http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2mempr.mspx

Note that it's probable that it's not related to DEP/NX but with the
enabling of PAE (Physical Address Extensions), required by DEP/NX.
What it's not proved yet is if after fixing PAE it will run OK.

About not crashing on your Athlon XP (or any Pentium), please add /PAE
in your boot.ini so it can have the same behavior :D

Regards,
~Nuno Lucas

hi, thanks for reply, after running windows xp sp2 with /noexecute=AlwaysOff
colinux is still crashing when "colinux-daemon.exe -c xxx.xml", but
windows xp doesn't crash at this time.


On Fri, 24 Sep 2004 16:20:03 +0100, Nuno Lucas <lucas@...> wrote:
> Paradise, dando pulos de alegria, escreveu :
> > Hi all,
> > coLinux v.0.6.2 pre1 crashed (blue screen) on my windows xp pro sp2 (32 bit ver)
> > however it doesnt crash on my athlonxp....
> >
> > anyone is same as me? or anyone run it on athlon 64 with no problem?
> 
> I guess you installed SP2. It's a known issue and will be corrected.
> In the meanwhile, just disable DEP/NX if you intend to run colinux with
> the Amd64 machine.
> 
> This can be accomplished by adding a /noexecute=AlwaysOff in your
> boot.ini, as documented here:
> http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2mempr.mspx
> 
> Note that it's probable that it's not related to DEP/NX but with the
> enabling of PAE (Physical Address Extensions), required by DEP/NX.
> What it's not proved yet is if after fixing PAE it will run OK.
> 
> About not crashing on your Athlon XP (or any Pentium), please add /PAE
> in your boot.ini so it can have the same behavior :D
> 
> Regards,
> ~Nuno Lucas
> 
> 



-- 
Regards,
Paradise

Paradise, dando pulos de alegria, escreveu :
> hi, thanks for reply, after running windows xp sp2 with /noexecute=AlwaysOff
> colinux is still crashing when "colinux-daemon.exe -c xxx.xml", but
> windows xp doesn't crash at this time.

Have you tried to re-install colinux?
The binaries could have become corrupt after the crashes...

If it continues after reinstalling, it would be good if you could
provide the event log of the crash, for further examination.


Regards,
~Nuno Lucas

Hi, I found the problem cause coLinux crash when startup is that I put
Chinese on the "name"..

e.g.
<network index=3D"0" type=3D"bridged" name=3D"=E5=8D=80=E5=9F=9F=E9=80=A3=
=E7=B7=9A" />


On Sat, 25 Sep 2004 08:42:04 +0100, Nuno Lucas <lucas@...> wr=
ote:
>=20
>=20
> Paradise, dando pulos de alegria, escreveu :
> > hi, thanks for reply, after running windows xp sp2 with /noexecute=3DAl=
waysOff
> > colinux is still crashing when "colinux-daemon.exe -c xxx.xml", but
> > windows xp doesn't crash at this time.
>=20
> Have you tried to re-install colinux?
> The binaries could have become corrupt after the crashes...
>=20
> If it continues after reinstalling, it would be good if you could
> provide the event log of the crash, for further examination.
>=20
> Regards,
> ~Nuno Lucas
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM.
> Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
> _______________________________________________
> coLinux-devel mailing list
> coLinux-devel@...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>=20



--=20
Regards,
Paradise

Nuno Lucas <lucas@...> writes:

> Paradise, dando pulos de alegria, escreveu :
> > Hi all, coLinux v.0.6.2 pre1 crashed (blue screen) on my windows xp
> > pro sp2 (32 bit ver)
> > however it doesnt crash on my athlonxp....
> > anyone is same as me? or anyone run it on athlon 64 with no problem?
> 
> I guess you installed SP2. It's a known issue and will be corrected.
> In the meanwhile, just disable DEP/NX if you intend to run colinux with
> the Amd64 machine.
>
> This can be accomplished by adding a /noexecute=AlwaysOff in your
> boot.ini, as documented here:
> http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2mempr.mspx
> 
> Note that it's probable that it's not related to DEP/NX but with the
> enabling of PAE (Physical Address Extensions), required by DEP/NX.
> What it's not proved yet is if after fixing PAE it will run OK.
> 
> About not crashing on your Athlon XP (or any Pentium), please add /PAE
> in your boot.ini so it can have the same behavior :D

Is this an issue only for AMD CPUs or does it also affect some Intel
CPUs?

I've tried to follow this thread on the mailing lists and it is not
clear to me what conclusion to draw.

-- 
Joe

Joe Wells, dando pulos de alegria, escreveu :
> 
> Is this an issue only for AMD CPUs or does it also affect some Intel
> CPUs?
> 
> I've tried to follow this thread on the mailing lists and it is not
> clear to me what conclusion to draw.
> 

To make it clearer, the problem can be triggered with any Pentium
II/III/IV and the old Pentium Pro. And any compatible AMD that
implements the PAE mechanism (Physical Address Extensions).

Windows doesn't enable PAE unless explicitely ordered to (with the /PAE
switch), but in order to use DEP/NX, the processor needs to be run with
PAE enabled (to have 64 bits page tables, instead of 32 bits).

So, on Amd64 processors (and maybe Intel Ithanium, not sure about this),
the bug will be triggered as soon as one enables the SP2 DEP/NX feature,
but because PAE is also enabled.

What is not tested yet is if, after correcting the PAE issue, it will
have problems with the DEP/NX one. But the second should be easy enough
to solve.


Regards,
~Nuno Lucas

Nuno Lucas <lucas@...> writes:

> Joe Wells, dando pulos de alegria, escreveu :
> > Is this an issue only for AMD CPUs or does it also affect some Intel
> > CPUs?
> > I've tried to follow this thread on the mailing lists and it is not
> > clear to me what conclusion to draw.
> >
> 
> To make it clearer, the problem can be triggered with any Pentium
> II/III/IV and the old Pentium Pro. And any compatible AMD that
> implements the PAE mechanism (Physical Address Extensions).
> 
> Windows doesn't enable PAE unless explicitely ordered to (with the /PAE
> switch), but in order to use DEP/NX, the processor needs to be run with
> PAE enabled (to have 64 bits page tables, instead of 32 bits).

Where is the "/PAE" switch supplied?  How can I tell if it is on?  How
can I tell if my machine has DEP/NX (and what is this anyway?)?

I'm currently afraid to upgrade to SP2 (it's just sitting on my hard
disk waiting for me to click on the little icon in the tray) because I
don't understand the implications of this issue.

Thanks for any advice you can supply!

-- 
Joe

> So, on Amd64 processors (and maybe Intel Ithanium, not sure about this),
> the bug will be triggered as soon as one enables the SP2 DEP/NX feature,
> but because PAE is also enabled.
> 
> What is not tested yet is if, after correcting the PAE issue, it will
> have problems with the DEP/NX one. But the second should be easy enough
> to solve.
> 
> 
> Regards,
> ~Nuno Lucas
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM.
> Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
> _______________________________________________
> coLinux-users mailing list
> coLinux-users@...
> https://lists.sourceforge.net/lists/listinfo/colinux-users

Paradise wrote:
> Hi, I found the problem cause coLinux crash when startup is that I put
> Chinese on the "name"..
> 
> e.g.
> <network index="0" type="bridged" name="區域連線" />
> 


Just for fun; when I was developing some homescreen plugins for the SPV1 
smartphone, HTC (Taiwan) were reporting some deep-down errors that were 
being caused by our plugin.

It turned out to be a bug in the MSFT xml parser that reads the 
homescreen definition, that was choking on chinese characters in the xml 
that had become mangled after editing in notepad.

Sam

Joe Wells, dando pulos de alegria, escreveu :
> Where is the "/PAE" switch supplied?  How can I tell if it is on?  How
> can I tell if my machine has DEP/NX (and what is this anyway?)?

As Steve Frank said, the "/PAE" switch is a boot.ini configuration
switch. They are for servers usage, not normal users, so not documented
in normal user documentation.

DEP is the new SP2 security feature that protects from some virus, by
using the NX feature that some new processors have. Basically, it avoids
some buffer overflow exploits, by not allowing to execute code from
normal memory. This feature is mostly only present on AMD64 processors.

> I'm currently afraid to upgrade to SP2 (it's just sitting on my hard
> disk waiting for me to click on the little icon in the tray) because I
> don't understand the implications of this issue.

You should be safe to upgrade (and I would recommend you, as many other
security fixes are included).
If you don't have an AMD64, PAE will not be enabled by default, so
current colinux versions will work ok.


Regards,
~Nuno Lucas

On Mon, Sep 27, 2004 at 10:43:28PM +0100, Nuno Lucas wrote:
> Joe Wells, dando pulos de alegria, escreveu :
> >
> >Is this an issue only for AMD CPUs or does it also affect some Intel
> >CPUs?
> >
> >I've tried to follow this thread on the mailing lists and it is not
> >clear to me what conclusion to draw.
> >
> 
> To make it clearer, the problem can be triggered with any Pentium
> II/III/IV and the old Pentium Pro. And any compatible AMD that
> implements the PAE mechanism (Physical Address Extensions).
> 
> Windows doesn't enable PAE unless explicitely ordered to (with the /PAE
> switch), but in order to use DEP/NX, the processor needs to be run with
> PAE enabled (to have 64 bits page tables, instead of 32 bits).
> 
> So, on Amd64 processors (and maybe Intel Ithanium, not sure about this),
> the bug will be triggered as soon as one enables the SP2 DEP/NX feature,
> but because PAE is also enabled.
> 
> What is not tested yet is if, after correcting the PAE issue, it will
> have problems with the DEP/NX one. But the second should be easy enough
> to solve.

I've just finished committing a fix for the PAE issue. It took the whole day,
and there were more extensive changes than I thought. The context switch code 
is a bit larger now (and also works differently than what you read in the 
slides and OLS paper) but expect no notable overhead like before.

Anyway, it appears to be stable on my PAE enabled XP SP2 and also on
my Linux boxes and Windows 2000 in QEMU. Users can test it by compiling
the binaries or wait until I release a snapshot this weekend.

-- 
Dan Aloni
da-x@...