Skip to contentSkip to conversation

Sockets on 64 bit Linux

DISCUSSION Alain Mouette 3 participants 8 messages Dec 14, 2012 – Dec 18, 2012 2 messages not in the archive

lore
Share & tools
lore
#0 lore raw

Hi,

I am having a problem with dosemu (svn2080 just downloaded) on a Ubuntu 64 bit machine. (eveything else is working perfectly)

I have an unusual and ramdom delay to receive packets, verying from a few miliseconds to a few seconds.

I checked with wireshark and the packet is there on tap0 with sub-milisecon response delay. I tried many different bridge configurations, including with eth0 down. Just ping is representative as a test, but it happens with other protocols too, as expected.

Please tell me if there is a way to make it work... I dont't want to reinstall everything because I cannot use one essencial item in 64 bits...

Thanks, anyone,

Alain

#1 lore raw

14.12.2012 22:36, Alain Mouette пишет:

Quoted 3 lines

Hi,

I am having a problem with dosemu (svn2080 just downloaded)

dosemu isnt using svn for quite some time, so
get it from git instead.

Quoted 1 line

I have an unusual and ramdom delay to receive packets, verying from a few miliseconds to a few seconds.

I have no idea whether or not this will help you, but
one guy is saying he had solved the similar problem
with
ethtool -K eth0 rx off tx off
which disables the tcp offload engine delays, and then bridging to tap0 started to work fine for him.
--
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#2 lore raw

Ok, nice to know, but that git is not github, where is it? Please send me a link or some information

And BTW, it seems that www.dosemu.org is offline...

Alain

Em 14-12-2012 17:42, Stas Sergeev escreveu:

Quoted 7 lines

14.12.2012 22:36, Alain Mouette пишет:

Quoted 3 lines

Hi,

I am having a problem with dosemu (svn2080 just downloaded)

dosemu isnt using svn for quite some time, so get it from git instead.

Quoted 9 lines
Quoted 2 lines

I have an unusual and ramdom delay to receive packets, verying from a few miliseconds to a few seconds.

I have no idea whether or not this will help you, but one guy is saying he had solved the similar problem with
ethtool -K eth0 rx off tx off
which disables the tcp offload engine delays, and then bridging to tap0 started to work fine for him.

--
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#3 lore raw

works fine for me. BTW, if you click "code" on the sourceforge.net page, it shows this: git clone git://git.code.sf.net/p/dosemu/code
dosemu-code

Quoted 28 lines · Alain Mouette

Ok, nice to know, but that git is not github, where is it? Please send me a link or some information

And BTW, it seems that www.dosemu.org is offline...

Alain

Em 14-12-2012 17:42, Stas Sergeev escreveu:

Quoted 13 lines

14.12.2012 22:36, Alain Mouette пишет:

Quoted 4 lines

Hi,

I am having a problem with dosemu (svn2080 just downloaded)

dosemu isnt using svn for quite some time, so get it from git instead.

Quoted 2 lines

I have an unusual and ramdom delay to receive packets, verying from a few miliseconds to a few seconds.

Quoted 7 lines

I have no idea whether or not this will help you, but one guy is saying he had solved the similar problem with
ethtool -K eth0 rx off tx off
which disables the tcp offload engine delays, and then bridging to tap0 started to work fine for him.

Quoted 4 lines

--
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#4 lore raw

thanks, as it happens, many sites were not responding at the time. 1/2 an hour later everything came back :)

I downloaded from git, but I having some problems:

1) I had some ^M erros messages, solved with
dos2unix -f configure
dos2unix default-configure
dos2unic getversion
(I had to force to convet congigure, it was recognized as binary...)

2) now, running ./configure, I am getting an error about clang checking for clang...... no

=> I installed: clang and libclang-dev
=> I changed llvm-3.0 to llvm-3.1
nothing made any difference
I had already compiled the svn version of dosemu on the same machine there are no such messages related to dosemu on google

Using Ubuntu 12.10 amd_64 (which is the same as x86_64)

please help
Alain

Em 14-12-2012 19:25, solarflow99 escreveu:

Quoted 5 lines

works fine for me. BTW, if you click "code" on the sourceforge.net page, it shows this: git clone git://git.code.sf.net/p/dosemu/code
dosemu-code

Quoted 34 lines
Quoted 32 lines · Alain Mouette

Ok, nice to know, but that git is not github, where is it? Please send me a link or some information

And BTW, it seems that www.dosemu.org is offline...

Alain

Em 14-12-2012 17:42, Stas Sergeev escreveu:

Quoted 13 lines

14.12.2012 22:36, Alain Mouette пишет:

Quoted 4 lines

Hi,

I am having a problem with dosemu (svn2080 just downloaded)

dosemu isnt using svn for quite some time, so get it from git instead.

Quoted 2 lines

I have an unusual and ramdom delay to receive packets, verying from a few miliseconds to a few seconds.

Quoted 7 lines

I have no idea whether or not this will help you, but one guy is saying he had solved the similar problem with
ethtool -K eth0 rx off tx off
which disables the tcp offload engine delays, and then bridging to tap0 started to work fine for him.

--
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#5 lore raw

15.12.2012 03:12, Alain Mouette пишет:

Quoted 1 line

thanks, as it happens, many sites were not responding at the time. 1/2 an hour later everything came back :)

You've got problems.

Quoted 7 lines

I downloaded from git, but I having some problems:

1) I had some ^M erros messages, solved with
dos2unix -f configure
dos2unix default-configure
dos2unic getversion
(I had to force to convet congigure, it was recognized as binary...)

You've got real problems...
I've just checked and there are no ^M in configure, and "dos2unix -f" doesn't change it.

Quoted 2 lines

2) now, running ./configure, I am getting an error about clang checking for clang...... no

That's not an error!

Quoted 2 lines

=> I installed: clang and libclang-dev
=> I changed llvm-3.0 to llvm-3.1

No need to.

Quoted 3 lines

nothing made any difference
I had already compiled the svn version of dosemu on the same machine there are no such messages related to dosemu on google

You've got problems. Viruses?
Oh, but that's not windows... :)
--
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#8 lore raw

Thanks Stas for your patience...

so if thet was not an error but a good thing, i suggest that the message should be changed... it may help others in the future. (I know next-to-nothing about seting up automake, but it is just a suggestion)

So the prblem is in the compilation itself: I get an error in the first file (removing all the make messages):
-------------
gcc -c -MP -MMD -I../../src/include -I../../src/plugin/include -Wall -Wstrict-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -mtune=a -pipe -O2 -fomit-frame-pointer -o tools86.o tools86.c ) for -mtune= switch: bad value (auto
-------------
And that looks wrong! According do man gcc, "-mtune=cpu-type" and auto or a is not an option...

Has gcc changed, or is there some regresion in dosemu? I have gcc 4.7.2 from ubuntu 12.10 64 bits

BTW, direct downolad in raw mode worked fine :)

Thanks,
Alain

Em 17-12-2012 18:56, Stas Sergeev escreveu:

Quoted 19 lines

17.12.2012 20:28, Alain Mouette пишет:

Quoted 8 lines
Quoted 5 lines
Quoted 2 lines

(I had to force to convet congigure, it was recognized as binary...)

You've got real problems...
I've just checked and there are no ^M in configure, and "dos2unix -f" doesn't change it.

IIrC git has some embedded function that may be doing that, it is suposed to eliminate ^M when cloning to linux...

Great, then get it from here:
http://sourceforge.net/p/dosemu/code/ci/3633a28059a495f563e549e9e0d135e0190e31ce/tree/configure?format=raw

and see if there are ^M or not.

Quoted 5 lines
Quoted 4 lines
Quoted 3 lines

2) now, running ./configure, I am getting an error about clang checking for clang...... no

That's not an error!

Quoted 8 lines
Quoted 2 lines

Ok, but please, what is the error? requiring clang, not detecting it, or something else?

I clarified the massage. Now it will write
---
checking for gcc actually being clang...... no
---
which will hopefully make you feel better. :)

--
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#9 lore raw

Aha! compiling now....

I just had to add a git option to not-change the LFs:

git -c core.autocrlf=false clone http://git.code.sf.net/p/dosemu/code dosemu-code

now it compiles without any glitch...

BUT, SADDLY the socket problem remains: I have an unusual and random delay to receive packets, verying from a few miliseconds to a few seconds.

Does anyone have any other idea, please... or will I have to reinstall 32bits?

Thanks for your help so far,
Alain

Em 17-12-2012 22:42, Alain Mouette escreveu:

Quoted 25 lines

Thanks Stas for your patience...

so if thet was not an error but a good thing, i suggest that the message should be changed... it may help others in the future. (I know next-to-nothing about seting up automake, but it is just a suggestion)

So the prblem is in the compilation itself: I get an error in the first file (removing all the make messages):
-------------
gcc -c -MP -MMD -I../../src/include -I../../src/plugin/include -Wall

(quoted diff) +0 -2
-Wstrict-prototypes -Wmissing-declarations -Wnested-externs
-fno-strict-aliasing -mtune=a -pipe -O2 -fomit-frame-pointer -o

tools86.o tools86.c
) for -mtune= switch: bad value (auto
-------------
And that looks wrong! According do man gcc, "-mtune=cpu-type" and auto or a is not an option...

Has gcc changed, or is there some regresion in dosemu? I have gcc 4.7.2 from ubuntu 12.10 64 bits

BTW, direct downolad in raw mode worked fine :)

Thanks,
Alain