From owner-freebsd-hackers Fri Aug 15 09:20:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA04521 for hackers-outgoing; Fri, 15 Aug 1997 09:20:26 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA04515 for ; Fri, 15 Aug 1997 09:20:19 -0700 (PDT) Received: (from pallenby@localhost) by zibbi.mikom.csir.co.za (8.8.6/8.8.5) id SAA25856; Fri, 15 Aug 1997 18:20:01 +0200 (SAT) From: Paul Allenby Message-Id: <199708151620.SAA25856@zibbi.mikom.csir.co.za> Subject: Re: Signal 11's.. In-Reply-To: <97Aug15.151826+0000_gmt.26400-77+45@engelska.se> from =?ISO-8859-1?Q?Thomas_Str=94mberg_=28Nobody=29?= at "Aug 15, 97 04:14:59 pm" To: nobody@engelska.se (=?iso-8859-1?Q?Thomas_Str=94mberg_=28Nobody=29?=) Date: Fri, 15 Aug 1997 18:20:01 +0200 (SAT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "Thomas Str”mberg (Nobody) wrote:" > On my FreeBSD-testing machine, I've been having problems installing the > 0812, 0813, and 0815 SNAP's (no problem with 2.2.2-RELEASE, 0618 SNAP, or > 0731 SNAP, at least during the install). Over an FTP install, it seems to > suddenly stop in random spots, with Write (-1 of 1024 bytes) and other odd > errors. I'll have to re-enable debug to give you a more technical post, but > this is what it says in the "emergency shell" window (debug not enabled): > > DEBUG: FTP Shutdown called. OpenConn = 1e94d0 > DEBUG: Signal 11 Caught - that's bad! > > This is from an FTP server inside the lan (tried using both IIS and WarFTPD > on two servers). > > If relevant: > > Kernel Enabled: 3C509 (10/340), SysCon, Floppy, both IDE selections. > Packages Selected: bin, doc, ports, man (has crashed in both bin, doc) > Hardware: AMD K5/133 (166+), 3C509 Ethernet, S3 video. > We had a very similar problem here at one stage. We traced it down to two machines running Windoze and very old versions of Winsock. That version of Winsock would close TCP connections between other machines. Probably that's not the cause of what you're seeing, though? Paul