Date: Tue, 7 Feb 2006 06:44:09 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Robert Watson <rwatson@FreeBSD.org> Cc: Giorgos Keramidas <keramida@ceid.upatras.gr>, freebsd-current@FreeBSD.org, Olivier Houchard <cognet@FreeBSD.org>, freebsd-amd64@FreeBSD.org Subject: Re: HEADSUP: New pts code triggers panics on amd64 systems. Message-ID: <20060207144409.GA48597@troutmask.apl.washington.edu> In-Reply-To: <20060207132335.W37594@fledge.watson.org> References: <20060201235556.GA708@troutmask.apl.washington.edu> <20060207104411.GA1067@flame.pc> <20060207132335.W37594@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 07, 2006 at 01:26:24PM +0000, Robert Watson wrote: > > Does the instability occur if kern.pts.enable=0, or only when > kern.pts.enable=1? If 0, if you back out the user space changes but leave > tty_pts.c compiled into the kernel, do the instability issues persist? How > about with the kernel code compiled out, but the user space code in place? > I opened a critial PR about this problem. There is a backtrace from a kernel panic that shows that there is either a latent bug in devfs uncovered by pts code or the pts code is stomping on memory. I still have the vmcore.0 file and I may have the matching kernel. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060207144409.GA48597>