From owner-freebsd-questions@FreeBSD.ORG Tue Jan 11 18:36:48 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 103EF16A4CE for ; Tue, 11 Jan 2005 18:36:48 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E9CF43D2D for ; Tue, 11 Jan 2005 18:36:47 +0000 (GMT) (envelope-from fehwalker@gmail.com) Received: by wproxy.gmail.com with SMTP id 40so751878wri for ; Tue, 11 Jan 2005 10:36:47 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=CvTWHbS2ys/SJbDpSGxYw4uyPWFBAxY6JE5zKmlU2Z1dUeZy2Bxn7l9/X9ZZaFTciBZsHoWwUKtQ+jJtCF8W1H4PcHh2TCfXgO34+Jeu8I2ulVJqhKo4QHDB/m1kbJJgsNJ+8lQ2xhBTTiLqrUAmcHGxSQvPizMr3H4S4bNV52I= Received: by 10.54.20.45 with SMTP id 45mr133316wrt; Tue, 11 Jan 2005 10:36:46 -0800 (PST) Received: by 10.54.19.59 with HTTP; Tue, 11 Jan 2005 10:36:46 -0800 (PST) Message-ID: <35de0c30050111103669af05e1@mail.gmail.com> Date: Tue, 11 Jan 2005 13:36:46 -0500 From: Bryan Fullerton To: freebsd-questions@freebsd.org In-Reply-To: <20050111044742.GA90081@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <35de0c3005010510582e3738fb@mail.gmail.com> <35de0c3005011019476b7b8e1c@mail.gmail.com> <20050111044742.GA90081@xor.obsecurity.org> Subject: Re: FreeBSD 5.3-R, postfix smtp dying with sig11 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Bryan Fullerton List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jan 2005 18:36:48 -0000 On Mon, 10 Jan 2005 20:47:44 -0800, Kris Kennaway wrote: > On Mon, Jan 10, 2005 at 10:47:24PM -0500, Bryan Fullerton wrote: > > > So... what could cause this? Is the sig 11 causing the failure, or is > > master killing off smtp as a result of some other issue? Anything I > > can poke at? > > Usually hardware failure. Consult the mailing list archives > or google for extensive discussion. If it was hardware failure I'd expect to see sig11's elsewhere -- I've never seen anything else sig11 on the box except postfix smtp processes, including repeatedly building world and kernel and dozens of other ports (it's a jail system, so I build package updates on the host OS and deploy them to the jails). I suspected yesterday that the problem might be controller write cache and softupdates combining to return success on writes before the data actually hit the drives, which could cause a short read of the on-disk queue file if it was accessed before the write completed. But I disabled the controller cache using the tw_cli command and I'm still seeing the same thing (unless tw_cli isn't really disabling all the write caching and I need to do something in the controller BIOS). I've also tried running a non-SMP kernel (it's a HTT system), but that didn't help. I'll try disabling APIC/ACPI today (which will of course also kill SMP) and see if that helps. Thanks, Bryan