Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 2 Dec 2009 09:25:21 GMT
From:      Yoshiaki Kasahara <kasahara@nc.kyushu-u.ac.jp>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   ports/141103: net/stone strange behavior on 8.0-RELEASE
Message-ID:  <200912020925.nB29PLD7084901@www.freebsd.org>
Resent-Message-ID: <200912020930.nB29U2vl021826@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         141103
>Category:       ports
>Synopsis:       net/stone strange behavior on 8.0-RELEASE
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Dec 02 09:30:02 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Yoshiaki Kasahara
>Release:        8.0-RELEASE
>Organization:
Kyushu University
>Environment:
FreeBSD elvenbow.cc.kyushu-u.ac.jp 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Thu Nov 26 14:33:01 JST 2009     root@elvenbow.cc.kyushu-u.ac.jp:/usr/obj/usr/src/sys/GENERIC  amd64
>Description:
After I upgraded my PC to 8.0R, net/stone proxy starts to emit error messages indefinitely after processed single HTTP request.  It never happened during using 7.x series.

% stone proxy 3128 localhost
Dec  2 18:15:33.961539 34374427072 start (2.3e) [76674]
Dec  2 18:15:33.964027 34374427072 stone 3: proxy <- 0.0.0.0:3128
Dec  2 18:15:45.978878 34374454848 3 TCP 4: close 5 01031601, reopen 6 as family=28
Dec  2 18:15:47.036333 34374453504 18:15:45 2 GET http://www.freebsd.org/ HTTP/1.0
Dec  2 18:15:47.036627 34374453504 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.036647 34374453504 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.036663 34374453504 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.036677 34374453504 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.036692 34374453504 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.036707 34374453504 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.036721 34374453504 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.036736 34374453504 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.036751 34374453504 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.036765 34374453504 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.036780 34374453504 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.036795 34374453504 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.036809 34374453504 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.036824 34374453504 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.036838 34374453504 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.036853 34374453504 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.036868 34374453504 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.036882 34374453504 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.036897 34374453504 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.036908 34374453504 3 TCP 4, 6: doReadWrite Can't happen spin occured tx/rx: 173/40, 18/173
Dec  2 18:15:47.138184 34374820288 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.138234 34374820288 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.138250 34374820288 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.138265 34374820288 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.138279 34374820288 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.138295 34374820288 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.138309 34374820288 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.138324 34374820288 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.138338 34374820288 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.138353 34374820288 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.138368 34374820288 3 TCP 4: recv MSG_OOB ret=-1, err=54
Dec  2 18:15:47.138379 34374820288 3 TCP 4, 6: doReadWrite Can't happen spin occured tx/rx: 173/40, 18/173

(repeats indefinitely)

The accessed URL doesn't matter.  I also tried net/stone on another machine running 8.0-RC2 (i386), and the same problem occurred.

Actually I'm not really sure if it is stone's problem, or TCP stack of 8.0R has some regressions.

>How-To-Repeat:
Install net/stone as usual.

1. execute "stone proxy 3128 localhost"
2. connect to the process from other terminal of the same host by "telnet localhost 3128"
3. send "GET http://www.freebsd.org/ HTTP/1.0" and enter twice
4. see the first terminal where stone is running

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200912020925.nB29PLD7084901>