RE : RE : [coLinux-devel] SMP system freeze completely

[Florent C. <flo...@un...>]

As I said in my previous post, the problem comes not from the TAP
drivers, because I had the problem on my P4 3.0 HT and I used a bridged
win pcap network (not TAP driver installed).

Hope it helps.

Florent

-----Message d'origine-----
De=A0: Dan Aloni [mailto:da...@co...]=20
Envoy=E9=A0: lundi 12 avril 2004 19:14
=C0=A0: Clemmitt M. Sigler
Cc=A0: Florent CUETO; col...@li...
Objet=A0: Re: RE : [coLinux-devel] SMP system freeze completely

On Mon, Apr 12, 2004 at 11:55:36AM -0400, Clemmitt M. Sigler wrote:
> Hi,
>=20
> On Fri, 2 Apr 2004, Florent CUETO wrote:
> > I have applied the imagecfg patch on the executables, now colinux
works
> > perfectly on my P4 3.0C HT.
> > Like Alejandro, I've patched all .exe (I did not try to apply the
patch
> > on colinux-deamon only).
>=20
> [..snips..]
>=20
> Case E is interesting.  Running either c-n-d or c-c-f as an MP
> .exe seems to boot OK, but running them *both* as MP .exe's caused
> boots/shutdowns to hang after a few tries.

Your test cases are interesting. The one that I find most bizarre is the
C case. It's the only case that involves a daemon communicating with a=20
kernel driver (this case, the TAP driver), whose executable is not
marked
UP *and* it doesn't incur hangs. The only diff between C and E is only
the UP
flag of the FLTK console, and it's weird that only that change causes=20
hangs, as the FLTK console process doesn't communicate with any driver.

Please test it without networking at all, so in case where the TAP=20
driver is faulty on SMP, it doesn't gets in our way when we try to find=20
the problem with coLinux.

--=20
Dan Aloni
da...@co...