colinux-users — coLinux users mailing list

RE: [coLinux-users] colinux 0.6.2 with pcap (snapshot coLinux-200 40710)

[Claude L. (QB/EMC) <cla...@er...>]

Hi,

However, I suspect the interface selection code has some problems. By =
example, on my system, I have multiple "Local Area Connection" entries. =
Something like this:

	Local Area Connection
	Local Area Connection 2
	Local Area Connection 3

I needed my system to bridge on "Local Area Connection". I have =
modified my xml file accordingly but coLinux never got attached to the =
proper interface. If I recall well, it has attached to the "Local Area =
Connection 3" instead.

So, to work around this problem, I have renamed the "Local Area =
Connection" to "Local Area Connection Broadcom" and after the proper =
modification has been done to the xml file, coLinux has attached to the =
correct interface.

Thanks,

Claude.

Claude LeFran=E7ois=20
cla...@er...


-----Original Message-----
From: col...@li...
[mailto:col...@li...]On Behalf Of Andreas
Brand
Sent: Friday, August 20, 2004 4:20 AM
To: gboutwel
Cc: col...@li...
Subject: Re: [coLinux-users] colinux 0.6.2 with pcap (snapshot
coLinux-20040710)


> > If I understand your situation correcly, It would seem that the
> > partial naming is playing a role here.  It"s finding the TAP
> > adatper, which is named Local Area  Connection 2, first as it"s
> > the one it encounters first, and since what you specified partially
> > matches it chooses it, before it hits the Local Area Connection
> > and sees it.  I suppose we could change the logic to go through
> > all partial matches, then go through them again to find one that
> > matches exactly, and if one doesn"t go with the first one. =20
> > But You"re best bet is to name them something less simliar.=20
> > I use Local Araa Connection for my REAL NIC, and Virtual Connection
> > for the TAP that I have.  That seems to work fine.
=20
=20
> I changed the adapters name from "Local Area Connection 2" to =
something
> else and tried to start colinux 0.6.2, well after I hit enter I got =
the=20
> blue sceen with STOP 0x1111777A and the hard disk and all data has
> gone :-( I  don"t know if this is happened by mischange. I have to =
wait=20
> for a new disk maybe after that I try again, but I am unsure, it is =
my=20
> office laptop and if it really would happen a second time I"ll get =
some
> troubles.

Hi George

I installed colinux 0.6.2 again, without tap, only with pcap, so I have =
only
one Adapter starting with the name "Local Area Adapter ..." . This =
works
very fine. No blue screen :-)=20

As you said, it seems colinux 0.6.2 takes the first adapter that =
correspond
partial to the name in the xml.

Greetings and thanks for your help!
Andreas

--=20
NEU: Bis zu 10 GB Speicher f=FCr e-mails & Dateien!
1 GB bereits bei GMX FreeMail http://www.gmx.net/de/go/mail



-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users

Re: [coLinux-users] colinux 0.6.2 with pcap (snapshot coLinux-20040710)

[Andreas B. <and...@gm...>]

> > If I understand your situation correcly, It would seem that the
> > partial naming is playing a role here.  It"s finding the TAP
> > adatper, which is named Local Area  Connection 2, first as it"s
> > the one it encounters first, and since what you specified partially
> > matches it chooses it, before it hits the Local Area Connection
> > and sees it.  I suppose we could change the logic to go through
> > all partial matches, then go through them again to find one that
> > matches exactly, and if one doesn"t go with the first one.  
> > But You"re best bet is to name them something less simliar. 
> > I use Local Araa Connection for my REAL NIC, and Virtual Connection
> > for the TAP that I have.  That seems to work fine.
 
 
> I changed the adapters name from "Local Area Connection 2" to something
> else and tried to start colinux 0.6.2, well after I hit enter I got the 
> blue sceen with STOP 0x1111777A and the hard disk and all data has
> gone :-( I  don"t know if this is happened by mischange. I have to wait 
> for a new disk maybe after that I try again, but I am unsure, it is my 
> office laptop and if it really would happen a second time I"ll get some
> troubles.

Hi George

I installed colinux 0.6.2 again, without tap, only with pcap, so I have only
one Adapter starting with the name "Local Area Adapter ..." . This works
very fine. No blue screen :-) 

As you said, it seems colinux 0.6.2 takes the first adapter that correspond
partial to the name in the xml.

Greetings and thanks for your help!
Andreas

-- 
NEU: Bis zu 10 GB Speicher für e-mails & Dateien!
1 GB bereits bei GMX FreeMail http://www.gmx.net/de/go/mail

[coLinux-users] NFS performance and colinux

[Claude L. (QB/EMC) <cla...@er...>]

Hi George,

I have installed snapshot-20040710. I have made the modification to the x=
ml file to attach to my Broadcom interface. I have booted my Fedora Core =
1 distribution with the 2.6.7 kernel without a problem. This snapshot doe=
s not contain the nfsd support. So, I have recompiled the colinux kernel =
with the appropriate settings. I have also learned that the NFS daemon se=
rvice has changed in the 2.6 kernels. So, I had to make a little adaptati=
on (mount -t nfsd nfsd /proc/fs/nfs). Finally, I got my colinux working f=
ine. :)

However, my Solaris jumpstart does not work yet. I hit the same problem. =
It seems the IP fragmentation problem is still there but I have noticed a=
n good improvement. It looks like the jumpstart client (the Solaris box) =
sends a bunch of large NFS read packets at the same time. Colinux is not =
able to reply to all of them in time and the jumpstart client sends ICMP =
packets with TTL exceeded to colinux. At this moment the jumpstart client=
 gives "NFS server not responding". The only way I have to improve this s=
ituation is to set the block size to 1024 which avoids the fragmentation.=
 The bad stuff is that only the root fs benefits from this settings all t=
he other NFS mounts from the client are 4K blocks.

The jumpstart client is point-to-point connected with my laptop using a c=
ross-over cable.

To solve this situation, I see two options:

1. Hard code the NFS packet size to 1024 in the kernel
2. Try the new feature: NFS over TCP

But, the fragmentation problem in colinux is not solved... I am a bit con=
fused now. I don't know what to do at this point. I am using the bridged =
networking configuration. I guess it has nothing to do with the TAP drive=
rs, isn't it ? I am using win2k so there is no way to enable bridging thr=
ough the TAP interface because it appears this is only supported in XP. I=
 absolutely need to use bridging because the jumpstart client initiates t=
he jumpstart process by a RARP request. Then, I cannot use NAT because th=
ese packets won't be redirected to my colinux distribution unless a port =
forwarding mechanism exists.

My system is a HP NC8000 laptop. It has 512 MB RAM and 1.5 GHz Pentium M =
CPU. The network interface is a Broadcom NetXtreme Gigabit adapter. I hav=
e already disabled TCP checksums and flow control on this interface.

Any suggestions are really welcome !

Here is the output of my latest ping test:

PING 192.168.0.101 (192.168.0.101) 4096(4124) bytes of data.
4104 bytes from 192.168.0.101: icmp_seq=3D1 ttl=3D255 time=3D2.24 ms
4104 bytes from 192.168.0.101: icmp_seq=3D2 ttl=3D255 time=3D2.10 ms
4104 bytes from 192.168.0.101: icmp_seq=3D3 ttl=3D255 time=3D2.23 ms
4104 bytes from 192.168.0.101: icmp_seq=3D7 ttl=3D255 time=3D2.09 ms
4104 bytes from 192.168.0.101: icmp_seq=3D8 ttl=3D255 time=3D2.22 ms
4104 bytes from 192.168.0.101: icmp_seq=3D10 ttl=3D255 time=3D2.10 ms
4104 bytes from 192.168.0.101: icmp_seq=3D12 ttl=3D255 time=3D2.23 ms
4104 bytes from 192.168.0.101: icmp_seq=3D13 ttl=3D255 time=3D2.22 ms
4104 bytes from 192.168.0.101: icmp_seq=3D15 ttl=3D255 time=3D2.22 ms
4104 bytes from 192.168.0.101: icmp_seq=3D17 ttl=3D255 time=3D2.06 ms
4104 bytes from 192.168.0.101: icmp_seq=3D20 ttl=3D255 time=3D2.23 ms
4104 bytes from 192.168.0.101: icmp_seq=3D23 ttl=3D255 time=3D2.22 ms
4104 bytes from 192.168.0.101: icmp_seq=3D24 ttl=3D255 time=3D2.23 ms
4104 bytes from 192.168.0.101: icmp_seq=3D26 ttl=3D255 time=3D2.09 ms
4104 bytes from 192.168.0.101: icmp_seq=3D27 ttl=3D255 time=3D2.11 ms
4104 bytes from 192.168.0.101: icmp_seq=3D30 ttl=3D255 time=3D2.22 ms
4104 bytes from 192.168.0.101: icmp_seq=3D32 ttl=3D255 time=3D1.97 ms
4104 bytes from 192.168.0.101: icmp_seq=3D33 ttl=3D255 time=3D2.09 ms
4104 bytes from 192.168.0.101: icmp_seq=3D34 ttl=3D255 time=3D2.07 ms

--- 192.168.0.101 ping statistics ---
35 packets transmitted, 19 received, 45% packet loss, time 34196ms
rtt min/avg/max/mdev =3D 1.974/2.158/2.242/0.087 ms, pipe 2

Thanks,

Claude.

Claude LeFran=E7ois=20
cla...@er...

-----Original Message-----
From: col...@li...
[mailto:col...@li...]On Behalf Of gboutwel
Sent: Wednesday, August 18, 2004 9:32 AM
To: col...@li...
Cc: Claude LeFrancois (QB/EMC)
Subject: Re: [coLinux-users] NFS performance and colinux




> > One question: are you using bridged networking ?

>

> I'm using the tap adapter, bridged by WinXP with my network
card.



I use both.  On the PCAP bridging there is, also, 0% loss of
packets using latest sources.



> Not sure about that (I made no tests), but it seems the tap-win32

> adapter is somewhat faster and reliable than the bridged adapter.
Also,

> the code was revised lately to accomodate larger packets transfers.



Yeah, most the tests that Dan has done shows TAP to be the faster
interface.



George



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

Praize? Enter In...

http://www.praize.com/



-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users

Re: [coLinux-users] Problems with 20040710 snapshot

[<sl...@bl...>]

Ronald Pijnacker <pij...@ds...> writes:

> This week I installed snapshot 20040710. I ran into a couple of problems:
> 
> - When logging in (vnc + XDMCP) WindowMaker now gets a floating point
>   exception. This doesn't happen with the previous snapshots or in
>   native linux.

Can you check with gdb if it is failing for the same reason as Firefox
and Xdvi fail for me?  See

  http://www.macs.hw.ac.uk/~jbw/colinux-floating-point.mbox

for my messages containing details of how to check a core dump with
gdb.  If you are seeing the same kind of failure I am seeing, then
some instruction to transfer a value into a floating point register
will have yielded a wacky value in the register, perhaps a few
instructions before the crash.  For me, I always see the programs
crash when they use cvttsd2si to convert the content of a floating
point register to an integer, but it seems something has already gone
wrong a few steps before the crash.

Also, what precise CPU do you have?  I have an Intel Pentium M
(mobile) CPU.

> - /dev/cobd1 is mapped to the first partition, which holds a ext3 fs.
>   Until now I could mount it with no problems. However, in this snapshot
>   I cannot anymore: "no such device".

If you are using devfs (e.g., if you are using Gentoo), then the
pseudo file /dev/cobd1 will not be created.  Instead, devfs will
create /dev/cobd/1.  See the earlier messages on the mailing list
about this.

-- 
Joe

[coLinux-users] FPE and CFLAGS

[Peng <rin...@gm...>]

After experimenting for a day with the 0710 snapshot and my Pentium M
machine running gentoo linux, it seems that the following CFLAGS is
safe and reasonably optimized: "-Os -march=i686 -mcpu=pentium3". It
generates code compatible with all i686 machines but optimized for
pentium3.

When I previously used "-Os -march=pentium3", xdvi crashed with FPEs. 
This CFLAGS generates instructions that *only* run on pentium3 (i.e.
not compatible with other CPUs), and it seems broken with the 0710
colinux snapshot.  Re-emerging xfree with a safer CFLAGS solved the
xdvi FPE problem.

Re: [coLinux-users] Problems with 20040710 snapshot

[Peng <rin...@gm...>]

Which distribution are you using?

On Thu, 19 Aug 2004 21:34:35 +0200, Ronald Pijnacker <pij...@ds...> wrote:
> Hi all,
> 
> This week I installed snapshot 20040710. I ran into a couple of problems:
> 
> - When logging in (vnc + XDMCP) WindowMaker now gets a floating point
>   exception. This doesn't happen with the previous snapshots or in
>   native linux.
> 
> - /dev/cobd1 is mapped to the first partition, which holds a ext3 fs.
>   Until now I could mount it with no problems. However, in this snapshot
>   I cannot anymore: "no such device".
>W 
> Just my two cents...
> 
> Oh, by the way, I saw some announcements of "other" snapshots in the mailing
> list. What is the status of these snapshots compared with the ones on the
> official site (colinux.org/snapshots) ? The latest snapshot seems quite old.
> 
> Regards,
> 
>   Ronald.
> 
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

[coLinux-users] Problems with 20040710 snapshot

[Ronald P. <pij...@ds...>]

Hi all,

This week I installed snapshot 20040710. I ran into a couple of problems:

- When logging in (vnc + XDMCP) WindowMaker now gets a floating point
  exception. This doesn't happen with the previous snapshots or in
  native linux.

- /dev/cobd1 is mapped to the first partition, which holds a ext3 fs.
  Until now I could mount it with no problems. However, in this snapshot
  I cannot anymore: "no such device".

Just my two cents...

Oh, by the way, I saw some announcements of "other" snapshots in the mailing
list. What is the status of these snapshots compared with the ones on the
official site (colinux.org/snapshots) ? The latest snapshot seems quite old.

Regards,

  Ronald.

Re: [coLinux-users] Re: floating point problems (was: using 2.6 kernels, moving to latest coLinux snapshot, etc.)

[Peng <rin...@gm...>]

I also had the xdvi crash problem with my Pentium M machine using the
0710 snapshot.  I re-emerged tetex and the problem was still there. 
Then, I re-emerged xfree and the problem is gone!! Here's what I did:

(don't put "mmx" or "sse" in the USE flags)
USE="X -kde -gnome -qt"
CFLAGS="-Os -march=i686 -pipe"

These flags are certainly conservative, but they seem to work.  At
least xdvi doesn't crash anymore.

-- Peng

On 19 Aug 2004 14:42:26 +0100, Joe Wells (reverse mailbox letters to
reply) <sl...@bl...> wrote:
> "gboutwel" <gbo...@pr...> writes:
> 
> > sl...@bl... wrote:
> >
> > > What is puzzling me is that I don't understand why only Firefox is
> > > affected by this.  I am running many other programs that use
> > > floating point and none of them have this problem.  Gnumeric uses
> > > many of the same libraries as Firefox (I am building Firefox
> > > against GTK2) and it seems to run.  (Actually, it crashes the
> > > first time I run it (no idea why because the Gnome software
> > > helpfully hides the cause and pops up a window saying it has
> > > crashed but without giving the signal), but then if I run it
> > > immediately afterward it runs fine.  This is new since the upgrade
> > > to the coLinux 2004-07-19 snapshot.  Strange.)  GV also runs fine,
> > > and it surely is doing a lot of floating point operations to scale
> > > and render fonts.
> > >
> > > Comments?
> >
> >   Did you emerge or re-emerge firefox after updating to the new
> > snapshot?
> 
> No and yes.  "No" in the sense that the old build of Firefox (from
> before switching from coLinux 0.6.1 to the new snapshot) exhibits the
> problem.  "Yes" in the sense that I then tried building a new version
> of Firefox to see if the problem might go away.  Both the old version
> and the new version fail in the same way.  I still have them both on
> my system.
> 
> By the way, I have discovered that Xdvi also has the problem.  It was
> built before I switched to the coLinux snapshot.
> 
> > We have another person on IRC who reported getting
> > FPEs all of a sudden.  He changed his cflags to something a little
> > safer and re-emerged his system with the new cflags and he no
> > longer gets FPEs.
> 
> I recompiled the .o files where Firefox was crashing with "-O0" (no
> optimization at all, only using i386 features and not extra features
> of Pentium 4) and it didn't help.  The only thing that helped was
> recompiling those .o files with "-msoft-float -mno-fp-ret-in-387
> -lfp-bit" (where libfp-bit.a is a library for doing floating point
> operations in software).  However, even recompiling all of the .o
> files of Firefox didn't seem to be enough because it still crashed in
> ..o files from shared libraries.
> 
> Did the person you mention re-emerge his *entire* system?  Firefox
> uses these shared libraries:
> 
>   linux-gate.so.1 libmozjs.so libxpcom.so libplds4.so libplc4.so
>   libnspr4.so libpthread.so.0 libdl.so.2 libgtk-x11-2.0.so.0
>   libgdk-x11-2.0.so.0 libatk-1.0.so.0 libgdk_pixbuf-2.0.so.0
>   libpangoxft-1.0.so.0 libpangox-1.0.so.0 libpango-1.0.so.0
>   libgobject-2.0.so.0 libgmodule-2.0.so.0 libglib-2.0.so.0 libX11.so.6
>   libm.so.6 libstdc++.so.5 libgcc_s.so.1 libc.so.6 /lib/ld-linux.so.2
>   libXrandr.so.2 libXi.so.6 libXinerama.so.1 libXext.so.6 libXft.so.2
>   libfreetype.so.6 libXrender.so.1 libfontconfig.so.1 libXcursor.so.1
>   libpangoft2-1.0.so.0 libexpat.so.0 libz.so.1
> 
> I'd rather not have to recompile all of these libraries, especially
> since they worked fine with coLinux 0.6.1 and Linux kernel 2.4.
> 
> > I've been using the latest sources including
> > the changes in the 07/19 snapshot for like a month now, on Gentoo
> > with out a single FPE.  I just emerged firefox and I don't see
> > any FPE while I'm using it at all.
> 
> What is your CPU?  On my system, /proc/cpuinfo reveals:
> 
>   processor       : 0
>   vendor_id       : GenuineIntel
>   cpu family      : 6
>   model           : 9
>   model name      : Intel(R) Pentium(R) M processor 1100MHz
>   stepping        : 5
>   cpu MHz         : 0.000
>   cache size      : 1024 KB
>   fdiv_bug        : no
>   hlt_bug         : no
>   f00f_bug        : no
>   coma_bug        : no
>   fpu             : yes
>   fpu_exception   : yes
>   cpuid level     : 2
>   wp              : yes
>   flags           : fpu vme de pse tsc msr mce cx8 sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 tm pbe tm2 est
>   bogomips        : 766.77
> 
> I find it interesting that the other person who recently sent e-mail
> about problems also has a "Intel Pentium M processor 1100MHz".
> 
> > Is it possible that the prior versions of coLinux allowed FP
> > operations that shouldn't have been allowed and now that we've
> > fixed that, it's identifying a situation that was being allowed
> > but shouldn't have been in FireFox?
> 
> This seems doubtful.  Under the debugger, it is clear that things are
> going horribly wrong with straightforward instructions to merely load
> floating point values into floating point registers from memory or
> convert values in floating point registers into integers and store
> them into memory.  I don't think movsd or cvttsd2si are extra or
> unusual operations.
> 
> > The only significant change
> > between 0.6.1 and 0719 in regards to FP operations was that flop20
> > didn't pass and now does.
> 
> Where do I get flops20 so I can try it on my machine?  Is it available
> as a Gentoo ebuild?  "emerge search flops" and "emerge search float"
> do not reveal it.
> 
> Thanks a lot for your advice!
> 
> --
> Joe
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

Re: [coLinux-users] Re: floating point problems (was: using 2.6 kernels, moving to latest coLinux snapshot, etc.)

[<sl...@bl...>]

"gboutwel" <gbo...@pr...> writes:

> sl...@bl... wrote:
> 
> > What is puzzling me is that I don't understand why only Firefox is
> > affected by this.  I am running many other programs that use
> > floating point and none of them have this problem.  Gnumeric uses
> > many of the same libraries as Firefox (I am building Firefox
> > against GTK2) and it seems to run.  (Actually, it crashes the
> > first time I run it (no idea why because the Gnome software
> > helpfully hides the cause and pops up a window saying it has
> > crashed but without giving the signal), but then if I run it
> > immediately afterward it runs fine.  This is new since the upgrade
> > to the coLinux 2004-07-19 snapshot.  Strange.)  GV also runs fine,
> > and it surely is doing a lot of floating point operations to scale
> > and render fonts.
> >
> > Comments?
>
>   Did you emerge or re-emerge firefox after updating to the new
> snapshot?

No and yes.  "No" in the sense that the old build of Firefox (from
before switching from coLinux 0.6.1 to the new snapshot) exhibits the
problem.  "Yes" in the sense that I then tried building a new version
of Firefox to see if the problem might go away.  Both the old version
and the new version fail in the same way.  I still have them both on
my system.

By the way, I have discovered that Xdvi also has the problem.  It was
built before I switched to the coLinux snapshot.

> We have another person on IRC who reported getting
> FPEs all of a sudden.  He changed his cflags to something a little
> safer and re-emerged his system with the new cflags and he no
> longer gets FPEs.

I recompiled the .o files where Firefox was crashing with "-O0" (no
optimization at all, only using i386 features and not extra features
of Pentium 4) and it didn't help.  The only thing that helped was
recompiling those .o files with "-msoft-float -mno-fp-ret-in-387
-lfp-bit" (where libfp-bit.a is a library for doing floating point
operations in software).  However, even recompiling all of the .o
files of Firefox didn't seem to be enough because it still crashed in
.o files from shared libraries.

Did the person you mention re-emerge his *entire* system?  Firefox
uses these shared libraries:

  linux-gate.so.1 libmozjs.so libxpcom.so libplds4.so libplc4.so
  libnspr4.so libpthread.so.0 libdl.so.2 libgtk-x11-2.0.so.0
  libgdk-x11-2.0.so.0 libatk-1.0.so.0 libgdk_pixbuf-2.0.so.0
  libpangoxft-1.0.so.0 libpangox-1.0.so.0 libpango-1.0.so.0
  libgobject-2.0.so.0 libgmodule-2.0.so.0 libglib-2.0.so.0 libX11.so.6
  libm.so.6 libstdc++.so.5 libgcc_s.so.1 libc.so.6 /lib/ld-linux.so.2
  libXrandr.so.2 libXi.so.6 libXinerama.so.1 libXext.so.6 libXft.so.2
  libfreetype.so.6 libXrender.so.1 libfontconfig.so.1 libXcursor.so.1
  libpangoft2-1.0.so.0 libexpat.so.0 libz.so.1

I'd rather not have to recompile all of these libraries, especially
since they worked fine with coLinux 0.6.1 and Linux kernel 2.4.

> I've been using the latest sources including
> the changes in the 07/19 snapshot for like a month now, on Gentoo
> with out a single FPE.  I just emerged firefox and I don't see
> any FPE while I'm using it at all.

What is your CPU?  On my system, /proc/cpuinfo reveals:

  processor       : 0
  vendor_id       : GenuineIntel
  cpu family      : 6
  model           : 9
  model name      : Intel(R) Pentium(R) M processor 1100MHz
  stepping        : 5
  cpu MHz         : 0.000
  cache size      : 1024 KB
  fdiv_bug        : no
  hlt_bug         : no
  f00f_bug        : no
  coma_bug        : no
  fpu             : yes
  fpu_exception   : yes
  cpuid level     : 2
  wp              : yes
  flags           : fpu vme de pse tsc msr mce cx8 sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 tm pbe tm2 est
  bogomips        : 766.77

I find it interesting that the other person who recently sent e-mail
about problems also has a "Intel Pentium M processor 1100MHz".

> Is it possible that the prior versions of coLinux allowed FP
> operations that shouldn't have been allowed and now that we've
> fixed that, it's identifying a situation that was being allowed
> but shouldn't have been in FireFox?

This seems doubtful.  Under the debugger, it is clear that things are
going horribly wrong with straightforward instructions to merely load
floating point values into floating point registers from memory or
convert values in floating point registers into integers and store
them into memory.  I don't think movsd or cvttsd2si are extra or
unusual operations.

> The only significant change
> between 0.6.1 and 0719 in regards to FP operations was that flop20
> didn't pass and now does.

Where do I get flops20 so I can try it on my machine?  Is it available
as a Gentoo ebuild?  "emerge search flops" and "emerge search float"
do not reveal it.

Thanks a lot for your advice!

-- 
Joe

Re: [coLinux-users] floating point exsception trouble.

[z0d <bz...@ma...>]

Henry Nestler wrote:

> z0d wrote:
>
>> hello.
>> i use some scientific modeling software on my linux box, and need 
>> allow my boss use
>> results visualization software on his windows laptop. But this 
>> software running only on linux. i use colinux for running it but in 
>> some cases have "floating point exception" error. After that xdm, 
>> xfs, and all X programs die, and can not running again. After colinux 
>> reboot all work but floating point exception may be again and may be 
>> not about 50/50. All our scientific software compiled for IntEl 
>> pentium III. My boss laptop have IntEl pentium 4 mobile. I do not 
>> know, may be mobile p4 processor have not some fpu instructions, but 
>> in some cases all software fully work on it.
>>
>> coLinux 6.1 with slackware 9.1 distribution.
>
>
> Please update to new version 0.6.2, this has fix for floating point.
>     http://www.colinux.org/snapshots/coLinux-20040710.exe
>
>> When i use vmware i have not any troubles, but vmware extreme slow. 
>> May be i can use XEN VM monitor, but my boss want native windows.
>>
>> Second question about memory for coLinux:
>>
>> I can change coLinux memory usage in its config file, and start 
>> coLinux. Can i config coLinux for dynamic usage windows memory, as a 
>> windows application?
>
>
> Not directly.
> Please create a swap file for coLinux. This will save some memory for 
> your Windows. Windows hold this file in Chache so it's "dynamic" for 
> coLinux.
>
> Henry
>
>
Thank you. But about dynamic memory. I don't now about windows disk 
buffers, but when
 colinux write to swap windows must save it blocks to disk from cache 
fast as possible,  if
 colinux have low memory and highly  swap usage, it increase disk usage, 
and highly decrease
 performance of slow laptop disk system for other applications.  I don't 
now much about  windows,
 but why colinux can not use  windows memory manager and windows paging? 
if i can allocate memory for colinux as windows application, i can use 
it on all pc in our lab, and use lot of user pc's free cpu time.

What about mosix port for colinux?

Re: [coLinux-users] Re: floating point problems (was: using 2.6 kernels, moving to latest coLinux snapshot, etc.)

[Peng <rin...@gm...>]

Could you please let me know what is the safe CFLAGS for gentoo you mentioned?

Thanks,

-- Peng

On 18 Aug 2004 13:24:21 -0000, gboutwel <gbo...@pr...> wrote:
>   Did you emerge or re-emerge firefox after updating to the new
> snapshot?  We have another person on IRC who reported getting
> FPEs all of a sudden.  He changed his cflags to something a little
> safer and re-emerged his system with the new cflags and he no
> longer gets FPEs.  I've been using the latest sources including
> the changes in the 07/19 snapshot for like a month now, on Gentoo
> with out a single FPE.  I just emerged firefox and I don't see
> any FPE while I'm using it at all.
>

[coLinux-users] coLinux-users -- confirmation of subscription -- confirm 783553

[Bamboo <n0k...@ya...>]

 
 


	
		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail 

RE: [coLinux-users] NFS performance and colinux

[Claude L. (QB/EMC) <cla...@er...>]

Hi George,

I have installed snapshot-20040710. I have made the modification to the x=
ml file to attach to my Broadcom interface. I have booted my Fedora Core =
1 distribution with the 2.6.7 kernel without a problem. This snapshot doe=
s not contain the nfsd support. So, I have recompiled the colinux kernel =
with the appropriate settings. I have also learned that the NFS daemon se=
rvice has changed in the 2.6 kernels. So, I had to make a little adaptati=
on (mount -t nfsd nfsd /proc/fs/nfs). Finally, I got my colinux working f=
ine. :)

However, my Solaris jumpstart does not work yet. I hit the same problem. =
It seems the IP fragmentation problem is still there but I have noticed a=
n good improvement. It looks like the jumpstart client (the Solaris box) =
sends a bunch of large NFS read packets at the same time. Colinux is not =
able to reply to all of them in time and the jumpstart client sends ICMP =
packets with TTL exceeded to colinux. At this moment the jumpstart client=
 gives "NFS server not responding". The only way I have to improve this s=
ituation is to set the block size to 1024 which avoids the fragmentation.=
 The bad stuff is that only the root fs benefits from this settings all t=
he other NFS mounts from the client are 4K blocks.

The jumpstart client is point-to-point connected with my laptop using a c=
ross-over cable.

To solve this situation, I see two options:

1. Hard code the NFS packet size to 1024 in the kernel
2. Try the new feature: NFS over TCP

But, the fragmentation problem in colinux is not solved... I am a bit con=
fused now. I don't know what to do at this point. I am using the bridged =
networking configuration. I guess it has nothing to do with the TAP drive=
rs, isn't it ? I am using win2k so there is no way to enable bridging thr=
ough the TAP interface because it appears this is only supported in XP. I=
 absolutely need to use bridging because the jumpstart client initiates t=
he jumpstart process by a RARP request. Then, I cannot use NAT because th=
ese packets won't be redirected to my colinux distribution unless a port =
forwarding mechanism exists.

My system is a HP NC8000 laptop. It has 512 MB RAM and 1.5 GHz Pentium M =
CPU. The network interface is a Broadcom NetXtreme Gigabit adapter. I hav=
e already disabled TCP checksums and flow control on this interface.

Any suggestions are really welcome !

Here is the output of my latest ping test:

PING 192.168.0.101 (192.168.0.101) 4096(4124) bytes of data.
4104 bytes from 192.168.0.101: icmp_seq=3D1 ttl=3D255 time=3D2.24 ms
4104 bytes from 192.168.0.101: icmp_seq=3D2 ttl=3D255 time=3D2.10 ms
4104 bytes from 192.168.0.101: icmp_seq=3D3 ttl=3D255 time=3D2.23 ms
4104 bytes from 192.168.0.101: icmp_seq=3D7 ttl=3D255 time=3D2.09 ms
4104 bytes from 192.168.0.101: icmp_seq=3D8 ttl=3D255 time=3D2.22 ms
4104 bytes from 192.168.0.101: icmp_seq=3D10 ttl=3D255 time=3D2.10 ms
4104 bytes from 192.168.0.101: icmp_seq=3D12 ttl=3D255 time=3D2.23 ms
4104 bytes from 192.168.0.101: icmp_seq=3D13 ttl=3D255 time=3D2.22 ms
4104 bytes from 192.168.0.101: icmp_seq=3D15 ttl=3D255 time=3D2.22 ms
4104 bytes from 192.168.0.101: icmp_seq=3D17 ttl=3D255 time=3D2.06 ms
4104 bytes from 192.168.0.101: icmp_seq=3D20 ttl=3D255 time=3D2.23 ms
4104 bytes from 192.168.0.101: icmp_seq=3D23 ttl=3D255 time=3D2.22 ms
4104 bytes from 192.168.0.101: icmp_seq=3D24 ttl=3D255 time=3D2.23 ms
4104 bytes from 192.168.0.101: icmp_seq=3D26 ttl=3D255 time=3D2.09 ms
4104 bytes from 192.168.0.101: icmp_seq=3D27 ttl=3D255 time=3D2.11 ms
4104 bytes from 192.168.0.101: icmp_seq=3D30 ttl=3D255 time=3D2.22 ms
4104 bytes from 192.168.0.101: icmp_seq=3D32 ttl=3D255 time=3D1.97 ms
4104 bytes from 192.168.0.101: icmp_seq=3D33 ttl=3D255 time=3D2.09 ms
4104 bytes from 192.168.0.101: icmp_seq=3D34 ttl=3D255 time=3D2.07 ms

--- 192.168.0.101 ping statistics ---
35 packets transmitted, 19 received, 45% packet loss, time 34196ms
rtt min/avg/max/mdev =3D 1.974/2.158/2.242/0.087 ms, pipe 2

Thanks,

Claude.

Claude LeFran=E7ois=20
cla...@er...

-----Original Message-----
From: col...@li...
[mailto:col...@li...]On Behalf Of gboutwel
Sent: Wednesday, August 18, 2004 9:32 AM
To: col...@li...
Cc: Claude LeFrancois (QB/EMC)
Subject: Re: [coLinux-users] NFS performance and colinux




> > One question: are you using bridged networking ?

>

> I'm using the tap adapter, bridged by WinXP with my network
card.



I use both.  On the PCAP bridging there is, also, 0% loss of
packets using latest sources.



> Not sure about that (I made no tests), but it seems the tap-win32

> adapter is somewhat faster and reliable than the bridged adapter.
Also,

> the code was revised lately to accomodate larger packets transfers.



Yeah, most the tests that Dan has done shows TAP to be the faster
interface.



George



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

Praize? Enter In...

http://www.praize.com/



-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users

Re: [coLinux-users] floating point exsception trouble.

[Henry N. <Hen...@ar...>]

z0d wrote:
> hello.
> i use some scientific modeling software on my linux box, and need allow 
> my boss use
> results visualization software on his windows laptop. But this software 
> running only on linux. i use colinux for running it but in some cases 
> have "floating point exception" error. After that xdm, xfs, and all X 
> programs die, and can not running again. After colinux reboot all work 
> but floating point exception may be again and may be not about 50/50. 
> All our scientific software compiled for IntEl pentium III. My boss 
> laptop have IntEl pentium 4 mobile. I do not know, may be mobile p4 
> processor have not some fpu instructions, but in some cases all software 
> fully work on it.
> 
> coLinux 6.1 with slackware 9.1 distribution.

Please update to new version 0.6.2, this has fix for floating point.
	http://www.colinux.org/snapshots/coLinux-20040710.exe

> When i use vmware i have not any troubles, but vmware extreme slow. May 
> be i can use XEN VM monitor, but my boss want native windows.
> 
> Second question about memory for coLinux:
> 
> I can change coLinux memory usage in its config file, and start coLinux. 
> Can i config coLinux for dynamic usage windows memory, as a windows 
> application?

Not directly.
Please create a swap-file for coLinux. This will save some memory for 
your Windows. Windows hold this file in Chache so it's "dynamic" for 
coLinux.

Henry

[coLinux-users] Can udev be used in colinux (with debian)

[Milind K. <mb...@ya...>]

Hi. I have been successfully using colinux with Debian
unstable for the last 5-6 months. I am presently using
the 20040710 snapshot.

I have also installed Archlinux as the second OS,
which is used when I boot native linux.

I have been toying with the idea of booting colinux
with ArchLinux. Archlinux uses udev. And udev requires
hotplug to be enabled in the kernel (CONFIG_HOTPLUG).
Looking at the default linux-config present in the 
colinux-20040710.tar.gz,CONFIG_HOTPLUG is disabled.

Before rebuilding the kernel, I thought it would be a
good idea to get feedback from someone who migth have
already tried. 

Can the colinux kernel be rebuilt with CONFIG_HOTPLUG
enabled?

Going a step further, has someone successfully used
udev inside colinux? If Gentoo uses udev by default,
the answer might be a big YES, but I am unfamiliar
about Gentoo details.

Thanks.

Milind



	
		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail 

Re: [coLinux-users] NFS performance and colinux

[gboutwel <gbo...@pr...>]

> > One question: are you using bridged networking ?

>

> I'm using the tap adapter, bridged by WinXP with my network
card.



I use both.  On the PCAP bridging there is, also, 0% loss of
packets using latest sources.



> Not sure about that (I made no tests), but it seems the tap-win32

> adapter is somewhat faster and reliable than the bridged adapter.
Also,

> the code was revised lately to accomodate larger packets transfers.



Yeah, most the tests that Dan has done shows TAP to be the faster
interface.



George



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

Praize? Enter In...

http://www.praize.com/

[coLinux-users] Re: floating point problems (was: using 2.6 kernels, moving to latest coLinux snapshot, etc.)

[gboutwel <gbo...@pr...>]

sl...@bl... wrote:

> Joe Wells  writes:



> What is puzzling me is that I don't understand why only Firefox

> is affected by this.  I am running many other programs that
use floating

> point and none of them have this problem.  Gnumeric uses many
of

> the  same libraries as Firefox (I am building Firefox against
GTK2)

> and it seems to run.  (Actually, it crashes the first time
I run it (no

> idea why because the Gnome software helpfully hides the cause
and pops

> up a window saying it has crashed but without giving the signal),
but

> then if I run it immediately afterward it runs fine.  This
is new since

> the upgrade to the coLinux 2004-07-19 snapshot.  Strange.)
 GV also

> runs fine, and it surely is doing a lot of floating point operations

> to scale and render fonts.

> 

> Comments?



Joe,



  Did you emerge or re-emerge firefox after updating to the new
snapshot?  We have another person on IRC who reported getting
FPEs all of a sudden.  He changed his cflags to something a little
safer and re-emerged his system with the new cflags and he no
longer gets FPEs.  I've been using the latest sources including
the changes in the 07/19 snapshot for like a month now, on Gentoo
with out a single FPE.  I just emerged firefox and I don't see
any FPE while I'm using it at all.



  Is it possible that the prior versions of coLinux allowed FP
operations that shouldn't have been allowed and now that we've
fixed that, it's identifying a situation that was being allowed
but shouldn't have been in FireFox?  The only significant change
between 0.6.1 and 0719 in regards to FP operations was that flop20
didn't pass and now does.



George



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

Looking for that favorite verse?

Search for it in Praize Bible

http://www.praize.com/bible/

[coLinux-users] floating point exsception trouble.

[z0d <bz...@ma...>]

hello.
i use some scientific modeling software on my linux box, and need allow 
my boss use
results visualization software on his windows laptop. But this software 
running only on linux. i use colinux for running it but in some cases 
have "floating point exception" error. After that xdm, xfs, and all X 
programs die, and can not running again. After colinux reboot all work 
but floating point exception may be again and may be not about 50/50. 
All our scientific software compiled for IntEl pentium III. My boss 
laptop have IntEl pentium 4 mobile. I do not know, may be mobile p4 
processor have not some fpu instructions, but in some cases all software 
fully work on it.

coLinux 6.1 with slackware 9.1 distribution.

When i use vmware i have not any troubles, but vmware extreme slow. May 
be i can use XEN VM monitor, but my boss want native windows.

Second question about memory for coLinux:

I can change coLinux memory usage in its config file, and start coLinux. 
Can i config coLinux for dynamic usage windows memory, as a windows 
application?

[coLinux-users] floating point exsception trouble.

[z0d <p0...@ne...>]

hello.
i use some scientific modeling software on my linux box, and need allow 
my boss use
results visualization software on his windows laptop. But this software 
running only on linux. i use colinux for running it but in some cases 
have "floating point exception" error. After that xdm, xfs, and all X 
programs die, and can not running again. After colinux reboot all work 
but floating point exception may be again and may be not about 50/50. 
All our scientific software compiled for IntEl pentium III. My boss 
laptop have IntEl pentium 4 mobile. I do not know, may be mobile p4 
processor have not some fpu instructions, but in some cases all software 
fully work on it.

coLinux 6.1 with slackware 9.1 distribution.

When i use vmware i have not any troubles, but vmware extreme slow. May 
be i can use XEN VM monitor, but my boss want native windows.

Second question about memory for coLinux:

I can change coLinux memory usage in its config file, and start coLinux. 
Can i config coLinux for dynamic usage windows memory, as a windows 
application?

Re: [coLinux-users] installing kernel 2.6 on Gentoo CoLinux with kernel 2.4

[Joe W. <jb...@ma...>]

Tiago Freire <tmp...@te...> writes:

> I am using Gentoo colinux with kernel 2.4, but now I want to cahnge to
> kernel 2.6.
> Can anyone show me way?

There is some information about this on the coLinux wiki at this
location:

  http://www.colinux.org/wiki/index.php/gentoo26modules

I wrote the story of my experience on this mailing list and you can
find the message at this location:

  http://sourceforge.net/mailarchive/message.php?msg_id=9217868

When you upgrade, it would be useful if you could add your experiences
to mine and use them to improve the explanation on the wiki.

I hope this helps.

-- 
Joe

Re: [coLinux-users] NFS performance and colinux

[Nuno L. <lu...@nl...>]

Claude LeFrancois (QB/EMC), dando pulos de alegria, escreveu :
> Thanks for the info, Nuno.
> 
> I will try a more recent build asap.
> 
> One question: are you using bridged networking ?

I'm using the tap adapter, bridged by WinXP with my network card.

 >
 > The IP fragmentation problem was produced under the bridged 
networking configuration under Win2K.

Not sure about that (I made no tests), but it seems the tap-win32 
adapter is somewhat faster and reliable than the bridged adapter. Also, 
the code was revised lately to accomodate larger packets transfers.

I made some basic tests to measure the network performance. This tests 
are not reliable, just a simple timed copy between systems of a 34 MB file.

Using samba:

lan --> colinux : ~2.0 MB/s
colinux --> lan : ~1.5 MB/s
xp --> colinux  : ~0.5 MB/s
colinux <-- xp  : (didn't had a easy way of testing this)
lan <--> xp     : ~3.3 MB/s

Using nfsd/portmap on my router:

lan --> colinux : ~2.5 MB/s

I started nfsd with default parameters (sync), in a Gentoo machine, just 
for this test.

Regards,
~Nuno Lucas

RE: [coLinux-users] NFS performance and colinux

[Claude L. (QB/EMC) <cla...@er...>]

Thanks for the info, Nuno.

I will try a more recent build asap.

One question: are you using bridged networking ?

The IP fragmentation problem was produced under the bridged networking =
configuration under Win2K.

Regards,

Claude.

Claude LeFran=E7ois=20
cla...@er...

-----Original Message-----
From: Nuno Lucas [mailto:lu...@nl...]
Sent: Monday, August 16, 2004 7:44 PM
To: Claude LeFrancois (QB/EMC)
Cc: col...@li...
Subject: Re: [coLinux-users] NFS performance and colinux


192.168.1.1 is my router in the internal network, not the host OS.

colinux root # ping -s 4096 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 4096(4124) bytes of data.
4104 bytes from 192.168.1.1: icmp_seq=3D1 ttl=3D64 time=3D4.50 ms
4104 bytes from 192.168.1.1: icmp_seq=3D2 ttl=3D64 time=3D3.53 ms
4104 bytes from 192.168.1.1: icmp_seq=3D3 ttl=3D64 time=3D3.48 ms
4104 bytes from 192.168.1.1: icmp_seq=3D4 ttl=3D64 time=3D4.11 ms
4104 bytes from 192.168.1.1: icmp_seq=3D5 ttl=3D64 time=3D3.61 ms
4104 bytes from 192.168.1.1: icmp_seq=3D6 ttl=3D64 time=3D3.33 ms
4104 bytes from 192.168.1.1: icmp_seq=3D7 ttl=3D64 time=3D3.72 ms
4104 bytes from 192.168.1.1: icmp_seq=3D8 ttl=3D64 time=3D3.44 ms
4104 bytes from 192.168.1.1: icmp_seq=3D9 ttl=3D64 time=3D3.36 ms
4104 bytes from 192.168.1.1: icmp_seq=3D10 ttl=3D64 time=3D3.63 ms
[....]
--- 192.168.1.1 ping statistics ---
120 packets transmitted, 120 received, 0% packet loss, time 120280ms
rtt min/avg/max/mdev =3D 3.280/3.761/9.236/0.951 ms

And a really remote host:

colinux root # ping -s 4096 www.colinux.org
PING www.colinux.org (66.35.250.210) 4096(4124) bytes of data.
4104 bytes from vhost.sourceforge.net (66.35.250.210): icmp_seq=3D1 =
ttl=3D45=20
time=3D599 ms
4104 bytes from vhost.sourceforge.net (66.35.250.210): icmp_seq=3D2 =
ttl=3D45=20
time=3D595 ms
4104 bytes from vhost.sourceforge.net (66.35.250.210): icmp_seq=3D3 =
ttl=3D45=20
time=3D595 ms
4104 bytes from vhost.sourceforge.net (66.35.250.210): icmp_seq=3D4 =
ttl=3D45=20
time=3D594 ms
4104 bytes from vhost.sourceforge.net (66.35.250.210): icmp_seq=3D5 =
ttl=3D45=20
time=3D596 ms
4104 bytes from vhost.sourceforge.net (66.35.250.210): icmp_seq=3D6 =
ttl=3D45=20
time=3D595 ms
4104 bytes from vhost.sourceforge.net (66.35.250.210): icmp_seq=3D7 =
ttl=3D45=20
time=3D595 ms
4104 bytes from vhost.sourceforge.net (66.35.250.210): icmp_seq=3D8 =
ttl=3D45=20
time=3D595 ms
4104 bytes from vhost.sourceforge.net (66.35.250.210): icmp_seq=3D9 =
ttl=3D45=20
time=3D625 ms
4104 bytes from vhost.sourceforge.net (66.35.250.210): icmp_seq=3D10=20
ttl=3D45 time=3D597 ms
[....]
--- www.colinux.org ping statistics ---
31 packets transmitted, 30 received, 3% packet loss, time 30386ms
rtt min/avg/max/mdev =3D 593.580/598.933/654.012/11.610 ms


I used a special build using the latest source, on a 2.6.8.1 kernel.

colinux root # uname -a
Linux colinux 2.6.8.1-co-0.6.2 #1 Sun Aug 15 04:33:48 WEST 2004 i686=20
Intel(R) Pentium(R) 4 CPU 1.70GHz GenuineIntel GNU/Linux


Regards,
~Nuno Lucas


Claude LeFrancois (QB/EMC), dando pulos de alegria, escreveu :
> Hi George,
>=20
> Thanks for your reply. I will give a try to the new release as soon =
as possible.
>=20
> However, I have made some NFS troubleshooting and I have finally been =
able to go a bit further with the jumpstart and I have been able to =
narrow down the problem. The NFS performance problem seems to be =
produced by the IP fragmentation.
>=20
> The default NFS block size on Linux is set to 4096 bytes (4K). When I =
set the rootopts value to 1024, the jumpstart process goes a lot =
better. This parameter set the rsize (read block size) option of the =
NFS mount request of the root filesystem coming from the jumpstart =
client. Unfortunately, all the other NFS mounted filesystems are not =
using this parameter and suffer from the fragmentation problem. So, the =
jumpstart fails later.
>=20
> Basically, there is no fragmentation at 1024 but, at 4096, the =
fragmentation is very important. To verify that the fragmentation is =
responsible of the bad NFS performance, I have tested ping of 4K to a =
remote system from colinux:
>=20
> PING 142.133.81.2 (142.133.81.2) 4096(4124) bytes of data.
> 4104 bytes from 142.133.81.2: icmp_seq=3D9 ttl=3D255 time=3D82.4 ms
> 4104 bytes from 142.133.81.2: icmp_seq=3D14 ttl=3D255 time=3D4.17 ms
> 4104 bytes from 142.133.81.2: icmp_seq=3D22 ttl=3D255 time=3D4.04 ms
> 4104 bytes from 142.133.81.2: icmp_seq=3D24 ttl=3D255 time=3D5.05 ms
> 4104 bytes from 142.133.81.2: icmp_seq=3D25 ttl=3D255 time=3D4.15 ms
> 4104 bytes from 142.133.81.2: icmp_seq=3D32 ttl=3D255 time=3D21.0 ms
> 4104 bytes from 142.133.81.2: icmp_seq=3D34 ttl=3D255 time=3D4.16 ms
> 4104 bytes from 142.133.81.2: icmp_seq=3D78 ttl=3D255 time=3D4.17 ms
>=20
> --- 142.133.81.2 ping statistics ---
> 121 packets transmitted, 8 received, 93% packet loss, time 120805ms
> rtt min/avg/max/mdev =3D 4.048/16.165/82.463/25.656 ms, pipe 2
>=20
> The ping test shows the 93% of packet drops... It looks like the =
colinux network adapter suffers from an IP fragmentation/reassembly =
performance problem.
>=20
> Please, can you try the same ping on a later colinux version (ping -s =
4096 <remote_ip_address>) if you have time and if you can ? So, we =
could already know if this problem is addressed with the new releases.
>=20
> Thanks,
>=20
> Claude LeFran=E7ois=20
> cla...@er...

[coLinux-users] installing kernel 2.6 on Gentoo CoLinux with kernel 2.4

[Tiago F. <tmp...@te...>]

hi all,

I am using Gentoo colinux with kernel 2.4, but now I want to cahnge to 
kernel 2.6.
Can anyone show me way?

Thanks

Re: [coLinux-users] NFS performance and colinux

[Nuno L. <lu...@nl...>]

192.168.1.1 is my router in the internal network, not the host OS.

colinux root # ping -s 4096 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 4096(4124) bytes of data.
4104 bytes from 192.168.1.1: icmp_seq=3D1 ttl=3D64 time=3D4.50 ms
4104 bytes from 192.168.1.1: icmp_seq=3D2 ttl=3D64 time=3D3.53 ms
4104 bytes from 192.168.1.1: icmp_seq=3D3 ttl=3D64 time=3D3.48 ms
4104 bytes from 192.168.1.1: icmp_seq=3D4 ttl=3D64 time=3D4.11 ms
4104 bytes from 192.168.1.1: icmp_seq=3D5 ttl=3D64 time=3D3.61 ms
4104 bytes from 192.168.1.1: icmp_seq=3D6 ttl=3D64 time=3D3.33 ms
4104 bytes from 192.168.1.1: icmp_seq=3D7 ttl=3D64 time=3D3.72 ms
4104 bytes from 192.168.1.1: icmp_seq=3D8 ttl=3D64 time=3D3.44 ms
4104 bytes from 192.168.1.1: icmp_seq=3D9 ttl=3D64 time=3D3.36 ms
4104 bytes from 192.168.1.1: icmp_seq=3D10 ttl=3D64 time=3D3.63 ms
[....]
--- 192.168.1.1 ping statistics ---
120 packets transmitted, 120 received, 0% packet loss, time 120280ms
rtt min/avg/max/mdev =3D 3.280/3.761/9.236/0.951 ms

And a really remote host:

colinux root # ping -s 4096 www.colinux.org
PING www.colinux.org (66.35.250.210) 4096(4124) bytes of data.
4104 bytes from vhost.sourceforge.net (66.35.250.210): icmp_seq=3D1 ttl=3D=
45=20
time=3D599 ms
4104 bytes from vhost.sourceforge.net (66.35.250.210): icmp_seq=3D2 ttl=3D=
45=20
time=3D595 ms
4104 bytes from vhost.sourceforge.net (66.35.250.210): icmp_seq=3D3 ttl=3D=
45=20
time=3D595 ms
4104 bytes from vhost.sourceforge.net (66.35.250.210): icmp_seq=3D4 ttl=3D=
45=20
time=3D594 ms
4104 bytes from vhost.sourceforge.net (66.35.250.210): icmp_seq=3D5 ttl=3D=
45=20
time=3D596 ms
4104 bytes from vhost.sourceforge.net (66.35.250.210): icmp_seq=3D6 ttl=3D=
45=20
time=3D595 ms
4104 bytes from vhost.sourceforge.net (66.35.250.210): icmp_seq=3D7 ttl=3D=
45=20
time=3D595 ms
4104 bytes from vhost.sourceforge.net (66.35.250.210): icmp_seq=3D8 ttl=3D=
45=20
time=3D595 ms
4104 bytes from vhost.sourceforge.net (66.35.250.210): icmp_seq=3D9 ttl=3D=
45=20
time=3D625 ms
4104 bytes from vhost.sourceforge.net (66.35.250.210): icmp_seq=3D10=20
ttl=3D45 time=3D597 ms
[....]
--- www.colinux.org ping statistics ---
31 packets transmitted, 30 received, 3% packet loss, time 30386ms
rtt min/avg/max/mdev =3D 593.580/598.933/654.012/11.610 ms


I used a special build using the latest source, on a 2.6.8.1 kernel.

colinux root # uname -a
Linux colinux 2.6.8.1-co-0.6.2 #1 Sun Aug 15 04:33:48 WEST 2004 i686=20
Intel(R) Pentium(R) 4 CPU 1.70GHz GenuineIntel GNU/Linux


Regards,
~Nuno Lucas


Claude LeFrancois (QB/EMC), dando pulos de alegria, escreveu :
> Hi George,
>=20
> Thanks for your reply. I will give a try to the new release as soon as =
possible.
>=20
> However, I have made some NFS troubleshooting and I have finally been a=
ble to go a bit further with the jumpstart and I have been able to narrow=
 down the problem. The NFS performance problem seems to be produced by th=
e IP fragmentation.
>=20
> The default NFS block size on Linux is set to 4096 bytes (4K). When I s=
et the rootopts value to 1024, the jumpstart process goes a lot better. T=
his parameter set the rsize (read block size) option of the NFS mount req=
uest of the root filesystem coming from the jumpstart client. Unfortunate=
ly, all the other NFS mounted filesystems are not using this parameter an=
d suffer from the fragmentation problem. So, the jumpstart fails later.
>=20
> Basically, there is no fragmentation at 1024 but, at 4096, the fragment=
ation is very important. To verify that the fragmentation is responsible =
of the bad NFS performance, I have tested ping of 4K to a remote system f=
rom colinux:
>=20
> PING 142.133.81.2 (142.133.81.2) 4096(4124) bytes of data.
> 4104 bytes from 142.133.81.2: icmp_seq=3D9 ttl=3D255 time=3D82.4 ms
> 4104 bytes from 142.133.81.2: icmp_seq=3D14 ttl=3D255 time=3D4.17 ms
> 4104 bytes from 142.133.81.2: icmp_seq=3D22 ttl=3D255 time=3D4.04 ms
> 4104 bytes from 142.133.81.2: icmp_seq=3D24 ttl=3D255 time=3D5.05 ms
> 4104 bytes from 142.133.81.2: icmp_seq=3D25 ttl=3D255 time=3D4.15 ms
> 4104 bytes from 142.133.81.2: icmp_seq=3D32 ttl=3D255 time=3D21.0 ms
> 4104 bytes from 142.133.81.2: icmp_seq=3D34 ttl=3D255 time=3D4.16 ms
> 4104 bytes from 142.133.81.2: icmp_seq=3D78 ttl=3D255 time=3D4.17 ms
>=20
> --- 142.133.81.2 ping statistics ---
> 121 packets transmitted, 8 received, 93% packet loss, time 120805ms
> rtt min/avg/max/mdev =3D 4.048/16.165/82.463/25.656 ms, pipe 2
>=20
> The ping test shows the 93% of packet drops... It looks like the colinu=
x network adapter suffers from an IP fragmentation/reassembly performance=
 problem.
>=20
> Please, can you try the same ping on a later colinux version (ping -s 4=
096 <remote_ip_address>) if you have time and if you can ? So, we could a=
lready know if this problem is addressed with the new releases.
>=20
> Thanks,
>=20
> Claude LeFran=E7ois=20
> cla...@er...

RE: [coLinux-users] NFS performance and colinux

[Claude L. (QB/EMC) <cla...@er...>]

Hi George,

Thanks for your reply. I will give a try to the new release as soon as =
possible.

However, I have made some NFS troubleshooting and I have finally been =
able to go a bit further with the jumpstart and I have been able to =
narrow down the problem. The NFS performance problem seems to be =
produced by the IP fragmentation.

The default NFS block size on Linux is set to 4096 bytes (4K). When I =
set the rootopts value to 1024, the jumpstart process goes a lot =
better. This parameter set the rsize (read block size) option of the =
NFS mount request of the root filesystem coming from the jumpstart =
client. Unfortunately, all the other NFS mounted filesystems are not =
using this parameter and suffer from the fragmentation problem. So, the =
jumpstart fails later.

Basically, there is no fragmentation at 1024 but, at 4096, the =
fragmentation is very important. To verify that the fragmentation is =
responsible of the bad NFS performance, I have tested ping of 4K to a =
remote system from colinux:

PING 142.133.81.2 (142.133.81.2) 4096(4124) bytes of data.
4104 bytes from 142.133.81.2: icmp_seq=3D9 ttl=3D255 time=3D82.4 ms
4104 bytes from 142.133.81.2: icmp_seq=3D14 ttl=3D255 time=3D4.17 ms
4104 bytes from 142.133.81.2: icmp_seq=3D22 ttl=3D255 time=3D4.04 ms
4104 bytes from 142.133.81.2: icmp_seq=3D24 ttl=3D255 time=3D5.05 ms
4104 bytes from 142.133.81.2: icmp_seq=3D25 ttl=3D255 time=3D4.15 ms
4104 bytes from 142.133.81.2: icmp_seq=3D32 ttl=3D255 time=3D21.0 ms
4104 bytes from 142.133.81.2: icmp_seq=3D34 ttl=3D255 time=3D4.16 ms
4104 bytes from 142.133.81.2: icmp_seq=3D78 ttl=3D255 time=3D4.17 ms

--- 142.133.81.2 ping statistics ---
121 packets transmitted, 8 received, 93% packet loss, time 120805ms
rtt min/avg/max/mdev =3D 4.048/16.165/82.463/25.656 ms, pipe 2

The ping test shows the 93% of packet drops... It looks like the =
colinux network adapter suffers from an IP fragmentation/reassembly =
performance problem.

Please, can you try the same ping on a later colinux version (ping -s =
4096 <remote_ip_address>) if you have time and if you can ? So, we =
could already know if this problem is addressed with the new releases.

Thanks,

Claude LeFran=E7ois=20
cla...@er...


-----Original Message-----
From: col...@li...
[mailto:col...@li...]On Behalf Of gboutwel
Sent: Saturday, August 14, 2004 7:57 PM
To: col...@li...
Subject: Re: [coLinux-users] NFS performance and colinux


> I am using colinux 0.6.1 over kernel 2.4.26. The original =
distribution
=3D



Only advice I can give is to try the more recent snapshots.=20
Especially the 20040710 snapshot.  It will involve and upgrade
to an 2.6 kernel and all that that may entail for the distro
of your your choice.  It probalby take rebulding the kernel with
NFS settings, but it might not.  But network performance has
been something that has been worked and has gotten comments about
it betting better in recent snapshots.



> If somebody has an idea why the NFS service is so slow, please,
do not =3D

> hesitate to contact me.



If after trying the recent snapshots, you still have problems
we can perhaps look at them to see fi there is more we can do.
 Additionally, If you find that we could enable something more
in the kernels for recent snapshots to make NFS support better,
let us know.



George