From owner-freebsd-current@FreeBSD.ORG  Sun Oct  3 20:10:26 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 90FB916A4D0
	for <freebsd-current@freebsd.org>;
	Sun,  3 Oct 2004 20:10:26 +0000 (GMT)
Received: from chatserv.de (p15119030.pureserver.info [217.160.175.43])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A21DA43D2F
	for <freebsd-current@freebsd.org>;
	Sun,  3 Oct 2004 20:10:23 +0000 (GMT)
	(envelope-from sascha@schumann.cx)
Received: from lx.foo (chatserv [217.160.175.43])
	by chatserv.de (Postfix) with ESMTP id 9ACD611009D
	for <freebsd-current@freebsd.org>;
	Sun,  3 Oct 2004 22:10:21 +0200 (CEST)
Date: Sun, 3 Oct 2004 22:10:21 +0200 (CEST)
From: Sascha Schumann <sascha@schumann.cx>
X-X-Sender: sas@lx
To: freebsd-current@freebsd.org
In-Reply-To: <20041002210024.GA55807@xor.obsecurity.org>
Message-ID: <Pine.LNX.4.60.0410032156300.10247@lx>
References: <Pine.LNX.4.60.0410022154210.1355@localhost>
	<Pine.LNX.4.60.0410022223070.1355@localhost>
	<20041002210024.GA55807@xor.obsecurity.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: Conclusion of thread "Deadlocks with recent SMP current"?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Oct 2004 20:10:26 -0000

    Just to give an update on our progress.

    db server: Was upgraded to RELENG_5 with conservative
    settings (no CPUTYPE, kernel config basically GENERIC except
    an increased MAXDSIZ).  Worked ok until we put some load onto
    it.  Crashed hard after about an hour of doing some work.

    www server: Booted cleanly into 5.3 kernel, but would not
    boot anymore after the following installworld.  Deadlocks
    during boot with all tested kernels - even those from a 5.2
    install medium and the previously successfully running 5.2.1
    kernel.  
    
    vga0: <bla>
    adv1: Invalid baseport of <bla> specified. Nearest etc.
    <deadlock>

    Both machines are 4xP4 Xeons with 4GB of RAM.  If anyone is
    interested in details, let me know.

    - Sascha