From owner-freebsd-sparc64@FreeBSD.ORG  Sun Sep  5 03:38:44 2004
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
Delivered-To: freebsd-sparc64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7905116A4CE; Sun,  5 Sep 2004 03:38:44 +0000 (GMT)
Received: from electra.cse.Buffalo.EDU (electra.cse.Buffalo.EDU
	[128.205.32.2])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 2EAEF43D2D; Sun,  5 Sep 2004 03:38:44 +0000 (GMT)
	(envelope-from kensmith@cse.Buffalo.EDU)
Received: from electra.cse.Buffalo.EDU (kensmith@localhost [127.0.0.1])
	i853chTH027675;	Sat, 4 Sep 2004 23:38:43 -0400 (EDT)
Received: (from kensmith@localhost)
	by electra.cse.Buffalo.EDU (8.12.10/8.12.9/Submit) id i853cho2027674;
	Sat, 4 Sep 2004 23:38:43 -0400 (EDT)
Date: Sat, 4 Sep 2004 23:38:43 -0400
From: Ken Smith <kensmith@cse.Buffalo.EDU>
To: John Baldwin <jhb@freebsd.org>
Message-ID: <20040905033843.GC27293@electra.cse.Buffalo.EDU>
References: <200409031451.03623.jhb@FreeBSD.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200409031451.03623.jhb@FreeBSD.org>
User-Agent: Mutt/1.4.1i
cc: alc@freebsd.org
cc: sparc64@freebsd.org
Subject: Re: sparc64 kernels have KVM problems(?)
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Sep 2004 03:38:44 -0000

On Fri, Sep 03, 2004 at 02:51:03PM -0400, John Baldwin wrote:

> Anyone have any ideas?  (Note that this is with a 32-bit time_t still, I'm 
> still in the process of doing the 64BTT update and was trying to figure this 
> out before going on.)

I can't imagine what the time_t would have to do with the problems you
saw but if you send me your config file I can try it on a completely
up to date machine - that way we could rule out that being the problem
for sure.

I haven't seen anything like what you were getting but I tend to use
mostly GENERIC kernels...

-- 
						Ken Smith
- From there to here, from here to      |       kensmith@cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |