From owner-freebsd-current  Fri May 30 10:56:29 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id KAA28657
          for current-outgoing; Fri, 30 May 1997 10:56:29 -0700 (PDT)
Received: from bourbon.sfc.wide.ad.jp (bourbon.sfc.wide.ad.jp [203.178.139.171])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA28643;
          Fri, 30 May 1997 10:56:08 -0700 (PDT)
Received: from bourbon.sfc.wide.ad.jp (localhost [127.0.0.1]) by bourbon.sfc.wide.ad.jp (8.8.5/3.5Wpl104/21/97) with ESMTP id CAA00639; Sat, 31 May 1997 02:55:48 +0900 (JST)
Message-Id: <199705301755.CAA00639@bourbon.sfc.wide.ad.jp>
To: jdp@polstra.com
Cc: max@wide.ad.jp, current@freebsd.org, wollman@freebsd.org
Subject: loopback i/f bug (?) [ was Re: Some trouble with SCSI HD]
From: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= <max@wide.ad.jp>
In-Reply-To: Your message of "Fri, 30 May 1997 09:44:43 -0700"
References: <199705301644.JAA28650@austin.polstra.com>
X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Sat, 31 May 1997 02:55:46 +0900
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

    >> I'm running -current from about a week ago.  When I run cvsup
    >> to get some files from cvsupd running on localhost, the system
    >> freezes.  Many times, the system just goes quiet and no input
    >> from console is accepted.  A few other other times, it goes
    >> half dead, I mean, I can traceroute or ping to the system from
    >> another machine but nothing else can be done.
    >> 
    >> When I run cvsup and get files from remote system, this doesn't
    >> happen.

    jdp> I noticed this too when I tried to CVSup to localhost.  I
    jdp> don't think it has anything to do with SCSI.  I think it's a
    jdp> networking bug in the loopback interface, exposed by CVSup's
    jdp> unusual traffic patterns.

    jdp> If you CVSup to yourhost.domain.name instead of localhost, it
    jdp> works fine.

Looks like you are right, John.  I removed /usr/ports, and re-cvsup'ed
the ports-all collection from my machine, specifying the FQDN this
time, instead of ``localhost'' and it went OK.

So, as you say, it's more than likely that loopback interface has some
problem.

Thanks for your suggestion.  It really helped!

     Cheers,
Max