From owner-freebsd-current Mon Jul 1 16: 4:33 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF74E37B400 for ; Mon, 1 Jul 2002 16:04:30 -0700 (PDT) Received: from volatile.chemikals.org (cae88-49-048.sc.rr.com [24.88.49.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 043AD43E09 for ; Mon, 1 Jul 2002 16:04:30 -0700 (PDT) (envelope-from morganw@chemikals.org) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.12.3/8.12.3) with ESMTP id g61N4F7C017813; Mon, 1 Jul 2002 19:04:15 -0400 (EDT) (envelope-from morganw@chemikals.org) Date: Mon, 1 Jul 2002 19:04:15 -0400 (EDT) From: Wesley Morgan To: Julian Elischer Cc: eischen@pcnet1.pcnet.com, , , Subject: Re: Post-KSE disaster with libc_r In-Reply-To: Message-ID: <20020701190330.G17798-100000@volatile.chemikals.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I already tried that this morning, it had no effect ... Unless you would like me to try an old kernel with it On Mon, 1 Jul 2002, Julian Elischer wrote: > can you try compiling a new libc_r with th efollowing change suggested by > Dan Eischen: > > ------begin quote: > > I also made changes to uthread_sigpending.c and uthread_sigsuspend.c > 3 days ago (lib/libc_r/uthread/...). You can try reverting those > changes and go back to revisions 1.18 and 1.11 respectively. > > ------end quote.. > > so that is uthread_sigpending.c version 1.18 > and > uthread_sigsuspend.c version 1.11 > > Thanks > > Julian > > > > > On Mon, 1 Jul 2002, Wesley Morgan wrote: > > > 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 > > > > > > > > > -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ morganw@chemikals.org _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message