Date: Mon, 1 Jul 2002 17:39:48 -0400 (EDT) From: Wesley Morgan <morganw@chemikals.org> To: <julian@elischer.org> Cc: <eischen@pcnet1.pcnet.com>, <ache@nagual.pp.ru>, <nakaji@boggy.acest.tutrp.tut.ac.jp>, <freebsd-current@FreeBSD.ORG> Subject: Re: Post-KSE disaster with libc_r Message-ID: <17419.148.175.49.1.1025559588.squirrel@www.chemikals.org> In-Reply-To: <Pine.BSF.4.21.0207011321250.91887-100000@InterJet.elischer.org> References: <Pine.GSO.4.10.10207011556130.26890-100000@pcnet1.pcnet.com> <Pine.BSF.4.21.0207011321250.91887-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Reverting proc.h and queue.h do nothing. Booting a kernel from 20020624, still crashes all threaded systems. Same behavior on a 20020620 kernel. > I don't change any of those. > > On Mon, 1 Jul 2002, Daniel Eischen wrote: >> >> I'd suspect that it is something to do with the layout of >> the fpregs, mcontext or something like that. Libc_r mucks >> about in jmp_buf (userland) and ucontext/mcontext, so anything >> that changed those would cause problems. >> > > > It's still unclear if a KSE kernel works with an old libc_r or visa > versa. > > I'd like to see if a new libc_r works with an old kernel (someone who > can boot kernel.back and test...) > > to check if you have a non KSE kernel, > sysctl kern.threads will only succeed in a new kernel. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17419.148.175.49.1.1025559588.squirrel>