Date: Tue, 7 Feb 2006 14:38:29 +0200 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Gary Jennejohn <garyj@jennejohn.org> Cc: freebsd-amd64@freebsd.org, freebsd-current@freebsd.org, Olivier Houchard <cognet@freebsd.org>, Steve Kargl <sgk@troutmask.apl.washington.edu> Subject: Re: HEADSUP: New pts code triggers panics on amd64 systems. Message-ID: <20060207123829.GA29307@flame.pc> In-Reply-To: <200602071228.k17CSLUQ005222@peedub.jennejohn.org> References: <keramida@ceid.upatras.gr> <20060207104411.GA1067@flame.pc> <200602071228.k17CSLUQ005222@peedub.jennejohn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. >> >> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060207123829.GA29307>