From owner-freebsd-current Fri Feb 13 14:49:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24516 for freebsd-current-outgoing; Fri, 13 Feb 1998 14:49:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ady.warpnet.ro (ady.warpnet.ro [193.230.201.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24499 for ; Fri, 13 Feb 1998 14:48:55 -0800 (PST) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.8.8/8.8.8) with SMTP id AAA00385; Sat, 14 Feb 1998 00:48:30 +0200 (EET) (envelope-from ady@warpnet.ro) Date: Sat, 14 Feb 1998 00:48:29 +0200 (EET) From: Penisoara Adrian To: "Stephane E. Potvin" cc: current@FreeBSD.ORG Subject: Re: Current dying horribly when using lp0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi again, On Fri, 13 Feb 1998, Penisoara Adrian wrote: > BTW, the problem is manifesting pretty rarely and it's hard to catch... > The system could go OK for days, but when it goes down it's really nasty > -- I mean you can't blame anything, the logs look very clean. > > I'd say give it time and you'll it's going to byte (the dust ?) again... > Well, today I hammered the server with FTP downloads (2 concurent wget's, half Gb worth of data) -- and after some time it has fallen on its knees. Please notice that I took care to eliminate everything it could have upset the beast: PPP daemons, squid daemon, nntpcache daemon; kernel still did have IPFW, but, as I told you, problems were showing even before adding IPFW. One thing I observed is that the panic is manifestig mostly when network traffic is in progress and another process is started in the mean time, but this is just a presumption somehow. It's getting harder and harder for me to nail this one down... Ady (@warpnet.ro), hoping I'll get my hands on a stable SNAP real soon... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message