From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 7 12:39:37 2006 Return-Path: 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 0F49116A422; Tue, 7 Feb 2006 12:39:37 +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 44DA643D49; Tue, 7 Feb 2006 12:39:33 +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 k17CdADJ017765; Tue, 7 Feb 2006 14:39:17 +0200 Received: by flame.pc (Postfix, from userid 1001) id D93045C8C; Tue, 7 Feb 2006 14:38:29 +0200 (EET) Date: Tue, 7 Feb 2006 14:38:29 +0200 From: Giorgos Keramidas To: Gary Jennejohn Message-ID: <20060207123829.GA29307@flame.pc> References: <20060207104411.GA1067@flame.pc> <200602071228.k17CSLUQ005222@peedub.jennejohn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200602071228.k17CSLUQ005222@peedub.jennejohn.org> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.438, 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 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2006 12:39:37 -0000 On 2006-02-07 13:28, Gary Jennejohn wrote: >Giorgos Keramidas writes: >> On 2006-02-01 15:55, Steve Kargl 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. >> >> I just rebuilt a HEAD snapshot from today's latest CVSup, installed it >> in /dev/ad0s1a (my test partition), and the behavior is still the same >> as a few days ago: >> >> - single user mode shell works fine >> >> - in multiuser mode, when syscons reaches a login prompt >> i have to press RET twice to see the last line >> >> It seems that something is broken in the way syscons detects whether an >> output line should be flushed out, but I'm not sure. >> >> 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.