From owner-freebsd-current Wed Aug 30 15:41: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id D838037B424; Wed, 30 Aug 2000 15:41:02 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id SAA18775; Wed, 30 Aug 2000 18:41:02 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e7UMf2A08134; Wed, 30 Aug 2000 18:41:02 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 30 Aug 2000 18:41:02 -0400 (EDT) To: Robert Watson Cc: freebsd-current@FreeBSD.org Subject: Re: recent -CURRENT: hangs on incoming network connections In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14765.36076.240673.862899@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Watson writes: > > As of this afternoon, I seem to be having problems with machines hanging > on incoming TCP connections. As soon as some process attempts to do > useful TCP stuff (incoming telnet, ssh, et al), all process hang. If I > break to ddb, a ps shows that telnetd has no wmesg. If I begin tapping on > various virtual consoles, gradually those processes also show no wmesg. > If I do a trace while in ddb, it whos that the active process is the > telnetd, but that it is hung in write(): > > ... > --- interrupt, eip = 0xc0195337, esp = 0xc5ea8ddc, ebp = 0xc5ea8df0 --- > sbappend(c554caf4,c057000) at sbappend+0x4b > tcp_usr_send(c554ca80,0,c0578000,0,0) at tcp_usr_send+0xc0 > sosend(c554ca80,0,c5ea8edc,c0578000,0) at sosend+0x61b > soo_write(c0c5f380,c5ea8edc,c0543780,0,c4d1f560) at soo_write+0x24 > dofilewrite(c4d1f560,c0c5f80,0,805b120,3) at dofilewrite+0xb1 > write(c4d1f560,c5ea8f80,3ffffffff,805bcc8) at write+0x33 > syscall2(2f,2f,2f,805bcc8,ffffffff) at syscall2+0x1f1 > Xint80x80_syscall() at Xint80x80_syscall+0x25 > > So it looks like it might have to do with the recent socket buffer > patches, et al, and isn't a result of my recent commits. However, I'm not > in front of a machine with a serial debugger right now, so won't be able > to follow up on this for a few hours. It seems to affect both machines > I've tried it on. ex cpl returns 63109a. > > So as a word of warning: if you're thinking about cvsup'ing, don't :-) Not a terribly good day to upgrade in -stable either -- RELENG4 is currently broken with exactly the same symptoms. See my post in the "4.1 STABLE broken since today!" thread on -stable.. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message