From owner-freebsd-amd64@FreeBSD.ORG  Tue Feb  7 12:54:27 2006
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
X-Original-To: freebsd-amd64@freebsd.org
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id CEB2C16A420;
	Tue,  7 Feb 2006 12:54:27 +0000 (GMT)
	(envelope-from keramida@ceid.upatras.gr)
Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2104043D48;
	Tue,  7 Feb 2006 12:54:25 +0000 (GMT)
	(envelope-from keramida@ceid.upatras.gr)
Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226])
	(authenticated bits=0)
	by igloo.linux.gr (8.13.5/8.13.5/Debian-3) with ESMTP id k17Cs8FS018579;
	Tue, 7 Feb 2006 14:54:12 +0200
Received: by flame.pc (Postfix, from userid 1001)
	id 59C7B5C8C; Tue,  7 Feb 2006 14:53:27 +0200 (EET)
Date: Tue, 7 Feb 2006 14:53:27 +0200
From: Giorgos Keramidas <keramida@ceid.upatras.gr>
To: Gary Jennejohn <garyj@jennejohn.org>
Message-ID: <20060207125327.GA55137@flame.pc>
References: <keramida@ceid.upatras.gr> <20060207123829.GA29307@flame.pc>
	<200602071243.k17ChJYY005474@peedub.jennejohn.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200602071243.k17ChJYY005474@peedub.jennejohn.org>
X-Hellug-MailScanner: Found to be clean
X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.44,
	required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.96,
	BAYES_00 -2.60)
X-Hellug-MailScanner-From: keramida@ceid.upatras.gr
Cc: freebsd-amd64@freebsd.org, freebsd-current@freebsd.org,
	Olivier Houchard <cognet@freebsd.org>
Subject: Re: HEADSUP: New pts code triggers panics on amd64 systems.
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2006 12:54:28 -0000

On 2006-02-07 13:43, Gary Jennejohn <garyj@jennejohn.org> wrote:
>Giorgos Keramidas writes:
>>On 2006-02-07 13:28, Gary Jennejohn <garyj@jennejohn.org> wrote:
>>>Giorgos Keramidas writes:
>>>> On 2006-02-01 15:55, Steve Kargl <sgk@troutmask.apl.washington.edu> wrote:
>>>> > After a binary search, I have determined that the new pts code is
>>>> > triggering kernel panics on an AMD64 system.
>>>>
>>>> It also makes syscons unusable here.
>>>> [...]
>>>> A snapshot from -D '2006/01/26 01:30:00 UTC' works fine (just before the
>>>> first pts change).
>>>>
>>>> I don't know how to debug this or provide more useful feedback, but I'll
>>>> look at the diffs later today, when I'm done with $REALJOB stuff.
>>>
>>> I'm running a kernel from Feb 5 09:15 (GMT+1) w/o any problems,
>>> even X works OK.
>>
>> Is this on amd64?  A kernel and userland from today (Feb 7,
>> around 07:00 UTC) is unusable on a Ferrari 3400 Lmi here.
>
> Yes, AMD64 X2 running on an ASUS A8V Deluxe.

Odd.  I'm rebuilding a fresh checkout now, but I don't see any commits
since early this morning that could have fixed this.