From owner-freebsd-alpha Mon Dec 30 6:47:22 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 168E637B401 for ; Mon, 30 Dec 2002 06:47:19 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BAF343EB2 for ; Mon, 30 Dec 2002 06:47:15 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.6/8.12.6) with ESMTP id gBUEkwro028618 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 30 Dec 2002 09:46:58 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gBUEkrn43316; Mon, 30 Dec 2002 09:46:53 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15888.23645.644351.257656@grasshopper.cs.duke.edu> Date: Mon, 30 Dec 2002 09:46:53 -0500 (EST) To: Rob B Cc: , sam@errno.com, Subject: Re: 4.7-STABLE kernel build failure with current CVS, any ideas? In-Reply-To: <5.1.1.6.2.20021230111030.01d0b880@127.0.0.1> References: <000001c2af4d$0f7da3f0$011872cf@gamer> <5.1.1.6.2.20021230111030.01d0b880@127.0.0.1> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Rob B writes: > At 02:14 30/12/2002, Howard Leadmon sent this up the stick: > > When I ran a cvsup on my Alpha of the current 4.7 code, all went well > > till I > >tried to build a new kernel. At that point it failed, and it seems like it's > >in the new crypto stuff that came down. > > > > > >I glanced back at the list, and didn't see any chatter about this, so was > >wondering if anyone has any idea how to fix this issue? All of my x86 based > >machines built and updated fine, so something specific to the Alpha. Yes, the crypto author appears to have forgotten to backport the required alpha bits. Can you try the following untested patch? I'm quite busy right now (just got back from vacation) and don't have time to take an alpha to -stable to fix this. Drew Index: alpha/alpha/ipl_funcs.c =================================================================== RCS file: /home/ncvs/src/sys/alpha/alpha/Attic/ipl_funcs.c,v retrieving revision 1.15.2.4 diff -u -r1.15.2.4 ipl_funcs.c --- alpha/alpha/ipl_funcs.c 26 Jul 2001 18:53:01 -0000 1.15.2.4 +++ alpha/alpha/ipl_funcs.c 30 Dec 2002 14:41:15 -0000 @@ -160,6 +160,7 @@ GENSET(setsoftvm, &ipending, 1 << SWI_VM) GENSET(setsofttq, &ipending, 1 << SWI_TQ) GENSET(setsoftclock, &ipending, 1 << SWI_CLOCK) +GENSET(setsoftcrypto, &ipending, 1 << SWI_CRYPTO) GENSET(schedsofttty, &idelayed, 1 << SWI_TTY) GENSET(schedsoftnet, &idelayed, 1 << SWI_NET) Index: alpha/include/ipl.h =================================================================== RCS file: /home/ncvs/src/sys/alpha/include/Attic/ipl.h,v retrieving revision 1.12.2.1 diff -u -r1.12.2.1 ipl.h --- alpha/include/ipl.h 18 Jul 2000 21:12:43 -0000 1.12.2.1 +++ alpha/include/ipl.h 30 Dec 2002 14:45:41 -0000 @@ -38,6 +38,7 @@ #define SWI_TTY 0 #define SWI_NET 1 #define SWI_CAMNET 2 +#define SWI_CRYPTO SWI_CAMNET #define SWI_CAMBIO 3 #define SWI_VM 4 #define SWI_CLOCK 5 @@ -80,6 +81,7 @@ SPLUP(splnet, IO) SPLUP(splbio, IO) SPLUP(splcam, IO) +SPLUP(splcrypto, IO) SPLUP(splimp, IO) SPLUP(spltty, IO) SPLUP(splvm, IO) @@ -113,6 +115,7 @@ extern void setsoftvm(void); extern void setsofttq(void); extern void setsoftclock(void); +extern void setsoftcrypto(void); extern void schedsofttty(void); extern void schedsoftnet(void); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message