From owner-freebsd-current Tue Apr 23 19:25:20 2002 Delivered-To: freebsd-current@freebsd.org Received: from ion.gank.org (ion.gank.org [64.81.113.130]) by hub.freebsd.org (Postfix) with ESMTP id CD94D37B41A for ; Tue, 23 Apr 2002 19:25:12 -0700 (PDT) Received: from aldaris (dsl081-113-221.dfw1.dsl.speakeasy.net [64.81.113.221]) by ion.gank.org (GankMail) with ESMTP id 052E71C for ; Tue, 23 Apr 2002 21:25:18 -0500 (CDT) Message-ID: <00ed01c1eb37$426ccdc0$5f45a8c0@auir.gank.org> Reply-To: "Craig Boston" From: "Craig Boston" To: References: <001901c1eb11$9abdb5a0$594bfea9@bender> <87d6wpn9ii.wl@kylebutt.dorms.usu.edu> Subject: Re: upgrade from 4.5 to current fails Date: Tue, 23 Apr 2002 21:25:08 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 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 Kyle Butt said: >To upgrade from 4.x-stable to current >------------------------------------- ----snip---- >reboot in single user [3] >Did you do this? IIRC, Sig 12 is unimplemented syscall, which would occur >when userland and the kernel are out of sync. I don't recall seeing this in any of the docs, nor has anyone else (to my knowledge) brought it up on the lists before, so I thought it was a local problem, but it's happened to me a couple times when jumping from -stable to -current. It seems after I do the installkernel and reboot to go to single user mode (like I always do with source upgrades), loader(8) still tries to load the /kernel left over from -stable instead of the new one that I just installed. I'm guessing that maybe loader(8) is installed as part of the installworld, and hence the -stable loader is still there and defaults to /kernel instead of /boot/kernel/kernel. A simple sequence of interrupting the loader and typing: unload kernel load /boot/kernel/kernel (load any applicable modules if you need them) boot -s Does the trick. After the installworld everything seems to work fine. Might this be the problem here? If so, perhaps it should be documented somewhere (yes I am volunteering, if somebody has any pointers for who to send the patch to :) Craig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message