From owner-freebsd-stable Wed Mar 22 20:15:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id A54C737C232 for ; Wed, 22 Mar 2000 20:15:28 -0800 (PST) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id XAA05794; Wed, 22 Mar 2000 23:15:43 -0500 (EST) (envelope-from bandix@looksharp.net) Date: Wed, 22 Mar 2000 23:15:43 -0500 (EST) From: "Brandon D. Valentine" To: Christian Jachmann Cc: Carroll Kong , "stable@freebsd.org" Subject: Re: 3.4-Stable crashes..(heavy diskio+networking) In-Reply-To: <38D954BC.4D49C9FA@gigabell.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Mar 2000, Christian Jachmann wrote: >It has been working in 2.2.* Release for about half a year, whithout any >problem. >After upgrading to 3.* (now 3.4) we got those crashes.... You may want to try rebuilding INN from the port again. Do a make deinstall and then delete the distfile and make install again. Chances are you are using an outdated version of INN which was probably built aout during your 2.2.x days. That's certainly no definitive answer, but it should help things and certainly cannot hurt. The panic log you quoted said the panic occured while innfeed was the current process. ------------------------------------------------------------- | -Brandon D. Valentine bandix at looksharp.net | bandix on EFnet IRC BVRiker on AIM ------------------------------------------------------------- | "...and as for hackers, we note that all of those known to | The Register are so strapped financially that seizing their | property would be tantamount to squeezing blood from a | stone." -- The Register, 02/17/2000 ------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message