[Bug 51950] New: Iperf 2.0.8 hangs in parallel dual mode on localhost
https://bugs.winehq.org/show_bug.cgi?id=51950 Bug ID: 51950 Summary: Iperf 2.0.8 hangs in parallel dual mode on localhost Product: Wine Version: 6.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: rpisl(a)seznam.cz Distribution: --- I found a problem in Wine winsock that may also be related to bug 51442 but I'm opening a new bug report since this is not a regression. On Windows, it is possible to run iperf 2.0.8 in dual mode on localhost in parallel mode, so the following command works: iperf -c 127.0.0.1 -d -t 1 -P 5 However, the same command freezes iperf completely on Wine, few messages "connect failed: Connection refused" appear and Ctrl+C for terminating iperf does not work. This behavior is valid for all Wine versions (tested on 6.0.2, 6.11 and 6.20). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51950 Roman Pišl <rpisl(a)seznam.cz> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |https://web.archive.org/web | |/20190523161058/https://ipe | |rf.fr/download/windows/iper | |f-2.0.8-win32.zip -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51950 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO Component|winsock |-unknown --- Comment #1 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- [236] local 127.0.0.1 port 5001 connected with 127.0.0.1 port 51350 [236] 0.0-71.5 sec 12.8 GBytes 1.53 Gbits/sec This works perfectly for me in Wine 6.20. Tried connecting from Linux and Wine and both work fine and tests complete with no issue. Are you saying that iperf hangs immediately on running that command? A console log would help. https://wiki.winehq.org/FAQ#How_can_I_get_a_debugging_log_.28a.k.a._terminal...
From https://iperf.fr/download/windows/iperf-2.0.8-win32.zip f312bf6ab7de3b1921cae7f4953aed0ce6b17afa iperf-2.0.8-win32.zip 6be507e9a9785e0a5511483d596b5dd6b6e717a3 iperf.exe
-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51950 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|1 |0 Status|NEEDINFO |UNCONFIRMED --- Comment #2 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Never mind I ran it incorrectly. connect failed: Connection refused connect failed: Connection refused connect failed: Connection refused -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51950 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #3 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Confirming in Wine 6.20. Linux iperf 2.0.10 sometimes segfaults on me so testing that was more successful, but there's still something wrong there. I still think there's a bug in Wine somewhere though. Nothing useful in the console. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51950 --- Comment #4 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Though I should add that iperf doesn't hang until I try to close it (CTRL+C), and then it remains in the background running around 2% CPU. If I don't do that then the server component, at least, continues to work as per Comment #1. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51950 --- Comment #5 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Created attachment 70931 --> https://bugs.winehq.org/attachment.cgi?id=70931 Wine 6.20 +winsock -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51950 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- There's no freeze on Wine 8.12 and all tests complete successfully.
connect failed: Connection refused
This still occurs, but doesn't seem to affect the results.
Ctrl+C for terminating iperf does not work
Yes, that is a bug. I'll open a new report for that. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51950 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #7 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 8.13. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla