From owner-freebsd-current@FreeBSD.ORG Tue Jun 1 07:48:18 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF96B16A4CE for ; Tue, 1 Jun 2004 07:48:18 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E60143D46 for ; Tue, 1 Jun 2004 07:48:18 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (junior-wifi.samsco.home [192.168.0.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i51EtDAf010930; Tue, 1 Jun 2004 08:55:13 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40BC9717.4010103@freebsd.org> Date: Tue, 01 Jun 2004 08:47:51 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Don Bowman References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: "'current@freebsd.org'" Subject: Re: hang with raid, postgresql X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jun 2004 14:48:18 -0000 Please try the latest aac driver sources. Scott Don Bowman wrote: > I have a system with 2x 2.8GHz XEON (P4), intel e7501 chipset, > 4GB of ram, aac [adaptec 2200s] raid with 4 scsi > disks. I have also tried asr (adaptec 2015). > I have tried two different motherboards. > The only application the machine runs is postgresql, > with about ~30 databases, about ~250GB of data. > > I'm finding the machine locks up solid once a day > or so (sometimes more, sometimes less, no pattern > of time of day). I know its not a hardware issue, it > is reliable with FreeBSD 4.7. I've run through memory > test, disk test, etc. > > There appears to be a correlation between > disk activity (postgresql vacuum) and the lockup, > but i can't be sure. > > I've just reproduced it with a cvsup from head today > [2004-05-30 12:00 EDT], so its still present. > I've got a serial console, and the break to > debugger (which works under normal circumstances). > > In the lockup case, i cannot drop into db, and > no output appears anywhere. I have enabled > the following options, but still no affect, no > messages come out (other than erroneous LOR > issues). > > options ALT_BREAK_TO_DEBUGGER > options DDB > options INVARIANTS > options INVARIANT_SUPPORT > options WITNESS > options WITNESS_SKIPSPIN > options MUTEX_DEBUG > options DIAGNOSTIC > > i've tried both with and without ACPI. It > does not have PAE configured in. > > The fact that i can't drop into the debugger > using the CR ~ ^B sequence when its locked up > implies that its no longer servicing the serial > interrupt. > > Does anyone have any suggestions? postgresql > makes use of disk, sysv semaphores, shared memory, > etc. > > I don't have sound, vga, X, ... any of the > 'complicated' things, its just a server. > There is no ATA. > > I tried setting kern.smp.active to 0, but > it still locked up. > > I'm looking for any suggestions. I have > attached the config file from it if anyone > has any comments on that. > > --don > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"