From owner-freebsd-alpha Sun Mar 12 2:21:33 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 90A7137BDCF for ; Sun, 12 Mar 2000 02:21:26 -0800 (PST) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id LAA20893; Sun, 12 Mar 2000 11:20:15 +0100 (MET) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.3/8.9.0) with ESMTP id LAA52557; Sun, 12 Mar 2000 11:21:46 +0100 (CET) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id LAA75397; Sun, 12 Mar 2000 11:21:33 +0100 (CET) (envelope-from ticso) Date: Sun, 12 Mar 2000 11:21:33 +0100 From: Bernd Walter To: Doug Rabson Cc: Bernd Walter , freebsd-alpha@freebsd.org Subject: Re: 64bit address space on alpha Message-ID: <20000312112132.A75380@cicely8.cicely.de> References: <19990718123721.A88813@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Jul 18, 1999 at 03:41:12PM +0100, Doug Rabson wrote: > On Sun, 18 Jul 1999, Bernd Walter wrote: > > > On Sun, Jul 18, 1999 at 09:27:14AM +0100, Doug Rabson wrote: > > > On Sat, 17 Jul 1999, Bernd Walter wrote: > > > > > > > I would like to mmap a large file into a single process address space. > > > > Is it save to increase MAXDSIZ to more than 4G? > > > > If not is there already work in progress? > > > > > > It should be safe to increase MAXDSIZ. The maximum user address space is > > > about 4T on FreeBSD/alpha. I have programs which mmap about 12G of device > > > addresses. > > I tried to compile a kernel with MAXDSIZ set to 128G and got several overflow > > compiler warnings: > > > > Are these realy save to ignore? > > I'll check. Just to get you informed about this point: It was completely my fault and it took me realy a half year to recheck and find this stupid thing :( I put (128*1024*1024*1024) in config following the example in LINT. The point is that gcc uses an int to calculate the number behind. Now that I'm using a constant everything is fine... -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 12 3:15:12 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id 0E16937BDD7 for ; Sun, 12 Mar 2000 03:14:22 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 12U6Jx-0008Sp-0A; Sun, 12 Mar 2000 11:14:06 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA14685; Sun, 12 Mar 2000 11:20:54 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 12 Mar 2000 11:16:17 +0000 (GMT) From: Doug Rabson To: Bernd Walter Cc: freebsd-alpha@freebsd.org Subject: Re: 64bit address space on alpha In-Reply-To: <20000312112132.A75380@cicely8.cicely.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 12 Mar 2000, Bernd Walter wrote: > Just to get you informed about this point: > It was completely my fault and it took me realy a half year to recheck and > find this stupid thing :( > I put (128*1024*1024*1024) in config following the example in LINT. > The point is that gcc uses an int to calculate the number behind. > Now that I'm using a constant everything is fine... Good. Thanks for checking this out. You might have been able to try something like (128*1024*1024*1024L) to force gcc to use the right types for its arithmetic. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 12 13:54: 7 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id CFEDE37B553 for ; Sun, 12 Mar 2000 13:54:02 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115827>; Mon, 13 Mar 2000 08:54:51 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: 64bit address space on alpha In-reply-to: <20000312112132.A75380@cicely8.cicely.de>; from ticso@cicely.de on Sun, Mar 12, 2000 at 09:22:58PM +1100 To: Bernd Walter Cc: freebsd-alpha@FreeBSD.ORG Message-Id: <00Mar13.085451est.115827@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <19990718123721.A88813@cicely8.cicely.de> <20000312112132.A75380@cicely8.cicely.de> Date: Mon, 13 Mar 2000 08:54:50 +1100 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 2000-Mar-12 21:22:58 +1100, Bernd Walter wrote: >I put (128*1024*1024*1024) in config following the example in LINT. >The point is that gcc uses an int to calculate the number behind. As would any other C compiler. (128*1024*1024*1024) is an expression comprising 4 int constants. According to the ANSI C rules, that means the expression should be evaluated as an int. If you stuck an `L' after one of the constants, the expression would be evaluated as `long'. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 14 15: 4:27 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mailext04.compaq.com (mailext04.compaq.com [207.18.199.42]) by hub.freebsd.org (Postfix) with ESMTP id 81B8237B835 for ; Tue, 14 Mar 2000 15:04:24 -0800 (PST) (envelope-from michael.waite@compaq.com) Received: by mailext04.compaq.com (Postfix, from userid 12345) id 8EB43104BA1; Tue, 14 Mar 2000 17:04:23 -0600 (CST) Received: from mailint02.im.hou.compaq.com (mailint02.compaq.com [207.18.199.35]) by mailext04.compaq.com (Postfix) with ESMTP id 8AEE8FB101 for ; Tue, 14 Mar 2000 17:04:23 -0600 (CST) Received: by mailint02.im.hou.compaq.com (Postfix, from userid 12345) id 1FE7B4D405; Tue, 14 Mar 2000 17:04:17 -0600 (CST) Received: from exctay-gh01.tay.cpqcorp.net (exctay-gh01.tay.cpqcorp.net [16.103.129.42]) by mailint02.im.hou.compaq.com (Postfix) with ESMTP id E9AC843981 for ; Tue, 14 Mar 2000 17:04:16 -0600 (CST) Received: by exctay-gh01.tay.cpqcorp.net with Internet Mail Service (5.5.2650.21) id ; Tue, 14 Mar 2000 18:04:22 -0500 Message-ID: <212CC57E84B8D111AD780000F84AA049083C2DA7@mroexc2.tay.dec.com> From: "Waite, Michael" To: freebsd-alpha@FreeBSD.ORG Subject: slate testdrives are ready Date: Tue, 14 Mar 2000 18:04:19 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org If you are interested in being the first kid on your block to try the new Compaq "1U" AlphaServer I now have them on the Internet for you to try out. get your own shell account at http://www.testdrive.compaq.com I have just put three of them on the network yet they are not added to the web pages yet, so you can telnet to 192.233.54.116 when you get your account by registering above. For those of you that already have your account it will authenticat you right now. Let me know what you think. Oh and by the way there are two more at 192.233.54.68....Tru64 UNIX 5.0 192.233.54.107........RedHat Linux 6.1 Please let me know what you think. If you want to see what it looks like you can go to http://www.testdrive.compaq.com/slate As I said. You wont see it in the sign up form as I won't make the web changes till tomorrow. Consider this your chance to use it before the masses do. ------Mike Michael Waite Global Partnering Solutions Services Compaq Computer Corporation 200 Forest Street MRO1-3 /E4 Marlboro, Ma 01752 508-467-2289 michael.waite@compaq.com email pager: 6350361@skytel.com skytel pager 1-888-635-0361 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 14 16:49:52 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from tibor.org (cable-117-5-237-24.anchorageak.net [24.237.5.117]) by hub.freebsd.org (Postfix) with ESMTP id 0CE6437B859 for ; Tue, 14 Mar 2000 16:49:49 -0800 (PST) (envelope-from tibor@tibor.org) Received: from localhost (localhost [127.0.0.1]) by tibor.org (Postfix) with ESMTP id CE8D723805 for ; Tue, 14 Mar 2000 15:49:47 -0900 (AKST) Date: Tue, 14 Mar 2000 15:49:47 -0900 (AKST) From: Mike Tibor To: freebsd-alpha@freebsd.org Subject: Booting on Alpha After Install Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I had no problems whatsoever installing either 3.4-RELEASE or the 4.0-20000307 snapshot on a pc164 alpha system, however I can't get the new system to boot (I'm using the most recent SRM firmware from gatekeeper.dec.com). Doing a "show dev" in SRM confirms that my hard disk is DKA0, but I've tried the following without success: boot dka0 boot dka0 -fi /kernel Both of the above commands yield the following error: ====================================================== block 0 of dka0.0.0.9.0 is a valid boot block reading 15 blocks from dka0.0.0.9.0 bootstrap code read in base = 180000, image_start = 0, image_bytes = 1e00 initializing HWRPB at 2000 initializing page table at 172000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code Loading /boot/loader halted CPU 0 halt code = 2 kernel stack not valid halt PC = 1004080391d248 ====================================================== Searching the archives brings up a couple of similar messages, but unfortunately no answers that I could see. I come from the Linux world and have no experience with FreeBSD, so I don't know for certain if my boot commands are correct (ie, missing flags or the wrong kernel filename--please be gentle if that's the case :-) ) Thanks, Mike -- Mike Tibor Univ. of Alaska Anchorage (907) 786-1001 voice Network Technician Consortium Library (907) 786-6050 fax tibor@lib.uaa.alaska.edu http://www.lib.uaa.alaska.edu/~tibor/ http://www.lib.uaa.alaska.edu/~tibor/pgpkey for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 15 11:44:33 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from account.abs.net (account.abs.net [207.114.5.70]) by hub.freebsd.org (Postfix) with ESMTP id 5AD4037BA26; Wed, 15 Mar 2000 11:44:25 -0800 (PST) (envelope-from howardl@account.abs.net) Received: (from howardl@localhost) by account.abs.net (8.9.3/8.9.3+RBL+DUL+RSS+ORBS) id OAA56309; Wed, 15 Mar 2000 14:44:23 -0500 (EST) (envelope-from howardl) From: Howard Leadmon Message-Id: <200003151944.OAA56309@account.abs.net> Subject: Trouble with CVSUP to 4.0 Release, any ideas?? To: freebsd-alpha@freebsd.org, freebsd-current@freebsd.org Date: Wed, 15 Mar 2000 14:44:23 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL72 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Not really sure where to start, but here goes. I have several DEC PC164SX machines running FreeBSD-Current, and my last cvsup was like Feb 28. While I had the chance yesterday I decided to change my cvs tag to RELENG_4 and bring things up to release. All seemed simple enough as I have sup'ed this box many times in the past with no problems. So I ran the sup's and then built a new kernel, as well as did a make world to make sure everything was at the release level. That all went fine, then I rebooted, and many things just were not working right. I can get on the console, but not remotely and things like sendmail and procmail processes all seemed to be hanging. I then thought maybe I should build a new kernel after the installworld, so went to try that. To my surprise I got the errors I'll include below. I then also just tried to do another buildworld, and that also blew up (errors below). As I mentioned, I was just trying to sup from Feb 28 to RELEASE, not all that far of a jump. Finally I took another Alpha I had sitting around, I think it's last sup was like Feb 21, and tried to upgrade it to RELEASE. Again that machine is now in total shambles and basically unusable unless I reload from scratch. Heck I even tried running an rm -rf on one of them under the /usr/src dir and grabbing a fresh cvs tree, but still can't compile. Any ideas how to fix this, or to get to 4.0 RELEASE on my other alphas do I have to do a clean reload?? MAKE KERNEL DEPEND: cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 ../../alpha/alpha/genassym.c In file included from ../../alpha/alpha/genassym.c:43: ../../sys/systm.h:331: invalid #-line In file included from ../../alpha/alpha/genassym.c:45, from ../../alpha/alpha/genassym.c:43: ../../sys/proc.h:47: invalid #-line In file included from ../../sys/signal.h:245, from ../../sys/proc.h:50, from ../../alpha/alpha/genassym.c:43: ../../sys/ucontext.h:34: invalid #-line ../../alpha/alpha/genassym.c:44: #-lines for entering and leaving files don't match In file included from ../../alpha/alpha/genassym.c:50: ../../sys/socket.h:232: invalid #-line In file included from ../../alpha/alpha/genassym.c:51: ../../sys/resource.h:101: invalid #-line ../../sys/resource.h:123: invalid #-line In file included from ../../alpha/alpha/genassym.c:52: ../../sys/resourcevar.h:98: invalid #-line In file included from ../../alpha/alpha/genassym.c:59, from ../../alpha/alpha/genassym.c:52: ../../vm/vm_map.h:380: invalid #-line In file included from from from from ../../netinet6/in6.h:453: invalid #-line In file included from from from ../../nfs/nfs.h:728: invalid #-line *** Error code 1 Stop in /usr/src/sys/compile/U3. MAKE BUILDWORLD: -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- rm -rf /usr/obj/usr/src/alpha mkdir -p /usr/obj/usr/src/alpha/usr/bin mkdir -p /usr/obj/usr/src/alpha/usr/lib/compat/aout mkdir -p /usr/obj/usr/src/alpha/usr/games mkdir -p /usr/obj/usr/src/alpha/usr/libdata/ldscripts mkdir -p /usr/obj/usr/src/alpha/usr/libexec/elf mkdir -p /usr/obj/usr/src/alpha/usr/sbin mkdir -p /usr/obj/usr/src/alpha/usr/share/misc mkdir -p /usr/obj/usr/src/alpha/usr/include/arpa mkdir -p /usr/obj/usr/src/alpha/usr/include/g++/std mkdir -p /usr/obj/usr/src/alpha/usr/include/objc mkdir -p /usr/obj/usr/src/alpha/usr/include/protocols mkdir -p /usr/obj/usr/src/alpha/usr/include/readline mkdir -p /usr/obj/usr/src/alpha/usr/include/rpc mkdir -p /usr/obj/usr/src/alpha/usr/include/rpcsvc mkdir -p /usr/obj/usr/src/alpha/usr/include/openssl mkdir -p /usr/obj/usr/src/alpha/usr/include/security mkdir -p /usr/obj/usr/src/alpha/usr/include/ss ln -sf /usr/src/sys /usr/obj/usr/src/alpha/sys -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/alpha DESTDIR=/usr/obj/usr/src/alpha INSTALL="sh /usr/src/tools/install.sh" MACHINE_ARCH=alpha TOOLS_PREFIX=/usr/obj/usr/src/alpha PATH=/usr/obj/usr/src/alpha/usr/sbin:/usr/obj/usr/src/alpha/usr/bin:/usr/obj/usr/src/alpha/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make -f Makefile.inc1 -DNOMAN -DNOINFO -DNOHTML bootstrap-tools cd /usr/src/games/fortune/strfile; make obj; make depend; make all; make install /usr/obj/usr/src/alpha/usr/src/games/fortune/strfile created for /usr/src/games/fortune/strfile rm -f .depend mkdep -f .depend -a -I/usr/obj/usr/src/alpha/usr/include /usr/src/games/fortune/strfile/strfile.c cd /usr/src/games/fortune/strfile; make _EXTRADEPEND echo strfile: /usr/obj/usr/src/alpha/usr/lib/libc.a >> .depend cc -O2 -pipe -Wall -I/usr/obj/usr/src/alpha/usr/include -c /usr/src/games/fortune/strfile/strfile.c In file included from /usr/src/games/fortune/strfile/strfile.c:56: /usr/include/stdlib.h:182: invalid #-line In file included from /usr/src/games/fortune/strfile/strfile.c:58, from /usr/src/games/fortune/strfile/strfile.c:56: /usr/include/string.h:98: invalid #-line *** Error code 1 Stop in /usr/src/games/fortune/strfile. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. As you can see they are dead, and I am at a loss as to why, but this happened exactly the same to two Alpha 164SX machine when I tried to go to RELEASE.. :( --- Howard Leadmon - howardl@abs.net - http://www.abs.net ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 15 13:28:44 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from anchor-post-30.mail.demon.net (anchor-post-30.mail.demon.net [194.217.242.88]) by hub.freebsd.org (Postfix) with ESMTP id 2C8B537BF2C; Wed, 15 Mar 2000 13:28:26 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-30.mail.demon.net with esmtp (Exim 2.12 #1) id 12VLKX-0005hu-0U; Wed, 15 Mar 2000 21:27:49 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id VAA16736; Wed, 15 Mar 2000 21:28:24 GMT (envelope-from dfr@nlsystems.com) Date: Wed, 15 Mar 2000 21:35:05 +0000 (GMT) From: Doug Rabson To: Howard Leadmon Cc: freebsd-alpha@freebsd.org, freebsd-current@freebsd.org Subject: Re: Trouble with CVSUP to 4.0 Release, any ideas?? In-Reply-To: <200003151944.OAA56309@account.abs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 15 Mar 2000, Howard Leadmon wrote: > Any ideas how to fix this, or to get to 4.0 RELEASE on my other alphas do > I have to do a clean reload?? > > ../../sys/ucontext.h:34: invalid #-line > ../../alpha/alpha/genassym.c:44: #-lines for entering and leaving files don't match Can I see the contents of /usr/src/sys/ucontext.h -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 15 17:29:49 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 9511937B881 for ; Wed, 15 Mar 2000 17:29:46 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA04165; Wed, 15 Mar 2000 17:31:49 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003160131.RAA04165@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Tibor Cc: freebsd-alpha@freebsd.org Subject: Re: Booting on Alpha After Install In-reply-to: Your message of "Tue, 14 Mar 2000 15:49:47 -0900." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Mar 2000 17:31:49 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This generally suggests that the loader (/boot/loader) is corrupt. Unfortunately SRM isn't very kind about alternate media; you might want to try booting the install media again and drop into 'fixit' mode and then go look at /boot and see whether things are all there. > I had no problems whatsoever installing either 3.4-RELEASE or the > 4.0-20000307 snapshot on a pc164 alpha system, however I can't get the > new system to boot (I'm using the most recent SRM firmware from > gatekeeper.dec.com). > > Doing a "show dev" in SRM confirms that my hard disk is DKA0, but I've > tried the following without success: > > boot dka0 > boot dka0 -fi /kernel > > Both of the above commands yield the following error: > > ====================================================== > block 0 of dka0.0.0.9.0 is a valid boot block > reading 15 blocks from dka0.0.0.9.0 > bootstrap code read in > base = 180000, image_start = 0, image_bytes = 1e00 > initializing HWRPB at 2000 > initializing page table at 172000 > initializing machine state > setting affinity to the primary CPU > jumping to bootstrap code > Loading /boot/loader > > halted CPU 0 > > halt code = 2 > kernel stack not valid halt > PC = 1004080391d248 > ====================================================== > > Searching the archives brings up a couple of similar messages, but > unfortunately no answers that I could see. > > I come from the Linux world and have no experience with FreeBSD, so I > don't know for certain if my boot commands are correct (ie, missing > flags or the wrong kernel filename--please be gentle if that's the case > :-) ) > > Thanks, > Mike > -- > Mike Tibor Univ. of Alaska Anchorage (907) 786-1001 voice > Network Technician Consortium Library (907) 786-6050 fax > tibor@lib.uaa.alaska.edu http://www.lib.uaa.alaska.edu/~tibor/ > http://www.lib.uaa.alaska.edu/~tibor/pgpkey for PGP public key > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 15 21:33:13 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dll.abs.net (dll.abs.net [207.114.24.10]) by hub.freebsd.org (Postfix) with ESMTP id 2C37E37B88B; Wed, 15 Mar 2000 21:33:08 -0800 (PST) (envelope-from howardl@abs.net) Received: from hdl (hdl@hdl.abs.net [207.114.24.1]) by dll.abs.net (8.9.3/8.9.3+RBL+DUL+RSS+ORBS) with SMTP id AAA34745; Thu, 16 Mar 2000 00:32:54 -0500 (EST) (envelope-from howardl@abs.net) Message-Id: <200003160532.AAA34745@dll.abs.net> From: howardl@abs.net (Howard Leadmon) To: dfr@nlsystems.com Subject: Re: Trouble with CVSUP to 4.0 Release, any ideas?? Organization: Babylon-5 War Council Cc: freebsd-alpha@freebsd.org, freebsd-current@freebsd.org Date: Thu, 16 Mar 2000 05:32:54 GMT Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >On Wed, 15 Mar 2000, Howard Leadmon wrote: > >> Any ideas how to fix this, or to get to 4.0 RELEASE on my other alphas do >> I have to do a clean reload?? >> >> ../../sys/ucontext.h:34: invalid #-line >> ../../alpha/alpha/genassym.c:44: #-lines for entering and leaving files don't match > >Can I see the contents of /usr/src/sys/ucontext.h Sure, here is it is: u3$ cat ../../sys/ucontext.h /*- * Copyright (c) 1999 Marcel Moolenaar * All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer * in this position and unchanged. * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * 3. The name of the author may not be used to endorse or promote products * derived from this software without specific prior written permission. * * THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR * IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. * IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. * * $FreeBSD: src/sys/sys/ucontext.h,v 1.4 1999/10/11 20:33:17 luoqi Exp $ */ #ifndef _SYS_UCONTEXT_H_ #define _SYS_UCONTEXT_H_ #include typedef struct __ucontext { /* * Keep the order of the first two fields. Also, * keep them the first two fields in the structure. * This way we can have a union with struct * sigcontext and ucontext_t. This allows us to * support them both at the same time. * note: the union is not defined, though. */ sigset_t uc_sigmask; mcontext_t uc_mcontext; struct __ucontext *uc_link; stack_t uc_stack; int __spare__[8]; } ucontext_t; #endif /* !_SYS_UCONTEXT_H_ */ u3$ Looks normal enough to me.. :) -Howard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 16 1: 7:21 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by hub.freebsd.org (Postfix) with ESMTP id E596037BB54; Thu, 16 Mar 2000 01:07:16 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1) id 12VWFG-000IY3-0X; Thu, 16 Mar 2000 09:07:07 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA49525; Thu, 16 Mar 2000 09:07:55 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 16 Mar 2000 09:14:28 +0000 (GMT) From: Doug Rabson To: Howard Leadmon Cc: freebsd-alpha@freebsd.org, freebsd-current@freebsd.org Subject: Re: Trouble with CVSUP to 4.0 Release, any ideas?? In-Reply-To: <200003160532.AAA34745@dll.abs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 16 Mar 2000, Howard Leadmon wrote: > >On Wed, 15 Mar 2000, Howard Leadmon wrote: > > > >> Any ideas how to fix this, or to get to 4.0 RELEASE on my other alphas do > >> I have to do a clean reload?? > >> > >> ../../sys/ucontext.h:34: invalid #-line > >> ../../alpha/alpha/genassym.c:44: #-lines for entering and leaving files don't match > > > >Can I see the contents of /usr/src/sys/ucontext.h > > > Sure, here is it is: It does look reasonable. I'm suspicious about your compiler binaries - you might have to reinstall after all. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 16 3:25:36 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from account.abs.net (account.abs.net [207.114.5.70]) by hub.freebsd.org (Postfix) with ESMTP id 4F14937B911; Thu, 16 Mar 2000 03:25:32 -0800 (PST) (envelope-from howardl@account.abs.net) Received: (from howardl@localhost) by account.abs.net (8.9.3/8.9.3+RBL+DUL+RSS+ORBS) id GAA56610; Thu, 16 Mar 2000 06:25:28 -0500 (EST) (envelope-from howardl) From: Howard Leadmon Message-Id: <200003161125.GAA56610@account.abs.net> Subject: Re: Trouble with CVSUP to 4.0 Release, any ideas?? In-Reply-To: from Doug Rabson at "Mar 16, 2000 09:14:28 am" To: Doug Rabson Date: Thu, 16 Mar 2000 06:25:28 -0500 (EST) Cc: Howard Leadmon , freebsd-alpha@freebsd.org, freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL72 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > >> Any ideas how to fix this, or to get to 4.0 RELEASE on my other alphas do > > >> I have to do a clean reload?? > > >> > > >> ../../sys/ucontext.h:34: invalid #-line > > >> ../../alpha/alpha/genassym.c:44: #-lines for entering and leaving files don't match > > > > > >Can I see the contents of /usr/src/sys/ucontext.h > > > > > > Sure, here is it is: > > It does look reasonable. I'm suspicious about your compiler binaries - you > might have to reinstall after all. > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 The strange part is that I have done this on two different Alpha machines, neither of which were more than a month behind on the CVS tree. I tried to update both to 4.0-RELEASE (RELENG_4 tag) and both are now in that state, so now I am totally afraid to even consider upgrading the other two to the release code. So whatever happened, was very easily reproduceable as I did it two times in a row. :( Has anyone updated a mid-febuary 4.0 to the RELEASE code on Alpha via CVS and had it go smooth, and if so what steps did you use to get there?? --- Howard Leadmon - howardl@abs.net - http://www.abs.net ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 16 6:47:29 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from nimbus.skycache.com (nimbus.skycache.com [207.239.230.67]) by hub.freebsd.org (Postfix) with ESMTP id 8CBFB37B865 for ; Thu, 16 Mar 2000 06:47:17 -0800 (PST) (envelope-from rharris@nimbus.skycache.com) Received: from localhost (localhost [[UNIX: localhost]]) by nimbus.skycache.com (8.10.0.Beta12/8.10.0.Beta12) with ESMTP id e2GElFE10429 for ; Thu, 16 Mar 2000 09:47:16 -0500 (EST) Date: Thu, 16 Mar 2000 09:47:15 -0500 (EST) From: Rob Harris To: freebsd-alpha@freebsd.org Subject: ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is there a way to check whether or not processor/system correctable error reporting is turned on in a kernel/system/etc? I loaded a box with 4.0 and I see no errors on RAM that I thought was suspect and that reports errors when using an earlier kernel. As always, Thanks. --Rob ____________________________________________________________________________ Rob Harris 8037 Laurel Lakes Court, Laurel MD 301.598.0500 x2236 Cidera, Inc. rharris@cidera.com fax: 301.598.0837 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ "Penfold... Shush." --Dangermouse To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 16 6:56:37 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 4908537B82D; Thu, 16 Mar 2000 06:56:32 -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.9.3/8.9.3) with ESMTP id JAA04003; Thu, 16 Mar 2000 09:56:24 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id JAA00491; Thu, 16 Mar 2000 09:55:54 -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 Date: Thu, 16 Mar 2000 09:55:54 -0500 (EST) To: Howard Leadmon Cc: Doug Rabson , freebsd-alpha@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Trouble with CVSUP to 4.0 Release, any ideas?? In-Reply-To: <200003161125.GAA56610@account.abs.net> References: <200003161125.GAA56610@account.abs.net> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14544.62658.595704.938141@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Howard Leadmon writes: > > Has anyone updated a mid-febuary 4.0 to the RELEASE code on Alpha via CVS > and had it go smooth, and if so what steps did you use to get there?? Yes, at least 3. But my methods are rather unconventional. On my build machine, which is running a 4.0-current box from mid January, I updated my source tree to 4.0-RELEASE via: cvs -R -d /home/ncvs up -r RELENG_4_0_0_RELEASE I then built the world on this machine via make buildworld, and nfs-exported /usr/src and /usr/obj. On each target machine, I mount buildhost:/usr /usr and buildhost:/usr/obj /usr/obj & do a make installworld. I've had no problems at all. One thing to check would be: did your installworld acutally complete? At one point the installworld was falling over in h2ph when a crypto-related header file was being perl'ified. If this is your problem, try doing a 'make -i installworld' Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 16 6:58: 4 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id B539337BBA1 for ; Thu, 16 Mar 2000 06:58:01 -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.9.3/8.9.3) with ESMTP id JAA04030; Thu, 16 Mar 2000 09:57:57 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id JAA00508; Thu, 16 Mar 2000 09:57:27 -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 Date: Thu, 16 Mar 2000 09:57:27 -0500 (EST) To: Rob Harris Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: ? In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14544.63024.924360.611228@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Rob Harris writes: > > Is there a way to check whether or not processor/system correctable error > reporting is turned on in a kernel/system/etc? > > I loaded a box with 4.0 and I see no errors on RAM that I thought was > suspect and that reports errors when using an earlier kernel. It is just a printf: /* Processor correctable errors. */ if (mces & ALPHA_MCES_PCE) printf("Warning: received processor correctable error.\n"); I don't see how it could get turned off.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 16 10:46:49 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from grunt.stupid.net (hc6526add.dhcp.vt.edu [198.82.106.221]) by hub.freebsd.org (Postfix) with ESMTP id AE89437BCC7 for ; Thu, 16 Mar 2000 10:46:34 -0800 (PST) (envelope-from fb@nomad.stupid.net) Received: from nomad.stupid.net (207-172-62-94.s94.tnt2.rcm.va.dialup.rcn.com [207.172.62.94]) by grunt.stupid.net (8.8.8/8.8.8) with ESMTP id NAA26153 for ; Thu, 16 Mar 2000 13:44:43 -0500 (EST) Received: (from fb@localhost) by nomad.stupid.net (8.8.8+Sun/8.8.8) id NAA04713 for freebsd-alpha@freebsd.org; Thu, 16 Mar 2000 13:43:46 -0500 (EST) Message-ID: <20000316134341.A4699@vt.edu> Date: Thu, 16 Mar 2000 13:43:41 -0500 From: fb@vt.edu To: freebsd-alpha@freebsd.org Subject: query for X success Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well I put a matrox millenium in my AS200 in the hopes that I will be able to run XFree in 24/32 bit color. Has anyone successfully run XFree in 24/32 bit color with a matrox millenium (I)? Is it stable? If so, re-installing will be on the top of my to do list :) Thanks, Nick Maniscalco nmanisca@vt.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 16 10:54:18 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from future.kissswiss.com (future.kissswiss.com [194.209.230.200]) by hub.freebsd.org (Postfix) with SMTP id DE07837BCCA for ; Thu, 16 Mar 2000 10:54:14 -0800 (PST) (envelope-from tom@knienieder.com) Received: (qmail 20489 invoked from network); 14 Mar 2000 19:40:36 +0100 Received: from unknown (HELO knienieder.com) (knie@192.168.1.199) by 192.168.1.41 with SMTP; 14 Mar 2000 19:40:36 +0100 Message-ID: <38D12DC9.D8BB7194@knienieder.com> Date: Thu, 16 Mar 2000 19:54:02 +0100 From: Tom Knienieder X-Mailer: Mozilla 4.72 [en] (X11; I; OpenBSD 2.6 i386) X-Accept-Language: de-AT, en MIME-Version: 1.0 To: fb@vt.edu Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: query for X success References: <20000316134341.A4699@vt.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org fb@vt.edu wrote: > > Well I put a matrox millenium in my AS200 in the hopes that > I will be able to run XFree in 24/32 bit color. > > Has anyone successfully run XFree in 24/32 bit color with a > matrox millenium (I)? Is it stable? If so, re-installing > will be on the top of my to do list :) > > Thanks, > > Nick Maniscalco > nmanisca@vt.edu > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message yes. i have a millenium 1 in a 164sx running X11. Works nice. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 16 10:56: 3 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mailext12.compaq.com (mailext12.compaq.com [207.18.199.188]) by hub.freebsd.org (Postfix) with ESMTP id CB56A37BCBE for ; Thu, 16 Mar 2000 10:56:01 -0800 (PST) (envelope-from michael.waite@compaq.com) Received: by mailext12.compaq.com (Postfix, from userid 12345) id 5D8845783D; Thu, 16 Mar 2000 12:56:00 -0600 (CST) Received: from mailint02.im.hou.compaq.com (mailint02.compaq.com [207.18.199.35]) by mailext12.compaq.com (Postfix) with ESMTP id 58A6354603; Thu, 16 Mar 2000 12:56:00 -0600 (CST) Received: by mailint02.im.hou.compaq.com (Postfix, from userid 12345) id EE12C4D40E; Thu, 16 Mar 2000 12:55:53 -0600 (CST) Received: from exctay-gh01.tay.cpqcorp.net (exctay-gh01.tay.cpqcorp.net [16.103.129.42]) by mailint02.im.hou.compaq.com (Postfix) with ESMTP id A77D943986; Thu, 16 Mar 2000 12:55:53 -0600 (CST) Received: by exctay-gh01.tay.cpqcorp.net with Internet Mail Service (5.5.2650.21) id ; Thu, 16 Mar 2000 13:55:59 -0500 Message-ID: <212CC57E84B8D111AD780000F84AA049083C2E17@mroexc2.tay.dec.com> From: "Waite, Michael" To: "'fb@vt.edu'" , freebsd-alpha@freebsd.org Subject: RE: query for X success Date: Thu, 16 Mar 2000 13:55:49 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have never used a matrox card in any alphas as Tru64 UNIX doesn't support is. But Elsa Gloria cards work just fine. I have 4.0CURRENT running X just fine on my XP1000a. -----Mike -----Original Message----- From: fb@vt.edu [mailto:fb@vt.edu] Sent: Thursday, March 16, 2000 1:44 PM To: freebsd-alpha@freebsd.org Subject: query for X success Well I put a matrox millenium in my AS200 in the hopes that I will be able to run XFree in 24/32 bit color. Has anyone successfully run XFree in 24/32 bit color with a matrox millenium (I)? Is it stable? If so, re-installing will be on the top of my to do list :) Thanks, Nick Maniscalco nmanisca@vt.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 16 11:10:13 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 3934C37BCF6 for ; Thu, 16 Mar 2000 11:10:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id LAA56183; Thu, 16 Mar 2000 11:10:00 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 9F38937C0BE for ; Thu, 16 Mar 2000 11:00:34 -0800 (PST) (envelope-from nobody@FreeBSD.org) Received: (from nobody@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id LAA53890; Thu, 16 Mar 2000 11:00:34 -0800 (PST) (envelope-from nobody@FreeBSD.org) Message-Id: <200003161900.LAA53890@freefall.freebsd.org> Date: Thu, 16 Mar 2000 11:00:34 -0800 (PST) From: matt@thebiz.net To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: alpha/17410: Bad tag on Alpha boot floppies Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 17410 >Category: alpha >Synopsis: Bad tag on Alpha boot floppies >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-alpha >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Mar 16 11:10:00 PST 2000 >Closed-Date: >Last-Modified: >Originator: Matthew Zahorik >Release: 4.0-RELEASE >Organization: BiznessOnline.com >Environment: n/a >Description: The installation floppies for 4.0-RELEASE (kern.flp, mfsroot.flp) found in /pub/FreeBSD/releases/alpha/4.0-RELEASE/floppies have 4.0-CURRENT in the options. This naturally makes it a bit harder to install FreeBSD 4.0-RELEASE since the base bin/doc/etc files aren't in that directory. >How-To-Repeat: >Fix: Workaround is to go into options from sysinstall and change the OS version tag from 4.0-CURRENT to 4.0-RELEASE. The install works as expected from that point onwards. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 16 11:20: 7 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id AB80737C0B2 for ; Thu, 16 Mar 2000 11:20:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id LAA58959; Thu, 16 Mar 2000 11:20:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 2161637C14E for ; Thu, 16 Mar 2000 11:16:24 -0800 (PST) (envelope-from nobody@FreeBSD.org) Received: (from nobody@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id LAA58128; Thu, 16 Mar 2000 11:16:24 -0800 (PST) (envelope-from nobody@FreeBSD.org) Message-Id: <200003161916.LAA58128@freefall.freebsd.org> Date: Thu, 16 Mar 2000 11:16:24 -0800 (PST) From: matt@thebiz.net To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: alpha/17411: No link/activity lights Alpha ethernet cards (dc0/dc1) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 17411 >Category: alpha >Synopsis: No link/activity lights Alpha ethernet cards (dc0/dc1) >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-alpha >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Mar 16 11:20:01 PST 2000 >Closed-Date: >Last-Modified: >Originator: Matthew Zahorik >Release: 4.0-RELEASE >Organization: BiznessOnline.com >Environment: FreeBSD basealpha.thebiz.net 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Mar 16 12:24:56 EST 2000 maz@basealpha.thebiz.net:/usr/src/sys/compile/MZ-DS10 alpha >Description: The box bootp's off a master FreeBSD NFS server. When the Alpha box first starts, link and activity lights work. The box bootp's, starts netboot, then loads the kernel. As soon as the kernel starts, the link and activity lights dissapear. The dc driver detects the dual onboard 21143 based 10/100 Ethernet: dc0: port 0x1100-0x117f mem 0x20c2000-0x20c23ff irq 29 at device 9.0 on pci0 dc0: interrupting at TSUNAMI irq 29 dc0: Ethernet address: 08:00:2b:86:28:54 miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto The link lights never come back on, nor any activity lights. We have stacks of these boxes, and link lights are necessary for first level debugging. (bad cabling, etc) This is not exclusive to a box booted via. bootp. A box started via. local disk also exhibits this problem. >How-To-Repeat: Boot the kernel. >Fix: No known cure. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 16 12: 0:13 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 0AB4F37C406 for ; Thu, 16 Mar 2000 12:00:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id MAA68575; Thu, 16 Mar 2000 12:00:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Thu, 16 Mar 2000 12:00:02 -0800 (PST) Message-Id: <200003162000.MAA68575@freefall.freebsd.org> To: freebsd-alpha@freebsd.org Cc: From: "Jordan K. Hubbard" Subject: Re: alpha/17410: Bad tag on Alpha boot floppies Reply-To: "Jordan K. Hubbard" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR alpha/17410; it has been noted by GNATS. From: "Jordan K. Hubbard" To: matt@thebiz.net Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: alpha/17410: Bad tag on Alpha boot floppies Date: Thu, 16 Mar 2000 11:51:57 -0800 Thanks, I'll investigate this immediately and fix it. > > >Number: 17410 > >Category: alpha > >Synopsis: Bad tag on Alpha boot floppies > >Confidential: no > >Severity: serious > >Priority: medium > >Responsible: freebsd-alpha > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Thu Mar 16 11:10:00 PST 2000 > >Closed-Date: > >Last-Modified: > >Originator: Matthew Zahorik > >Release: 4.0-RELEASE > >Organization: > BiznessOnline.com > >Environment: > n/a > >Description: > The installation floppies for 4.0-RELEASE (kern.flp, mfsroot.flp) found in /p ub/FreeBSD/releases/alpha/4.0-RELEASE/floppies have 4.0-CURRENT in the options. This naturally makes it a bit harder to install FreeBSD 4.0-RELEASE since the base bin/doc/etc files aren't in that directory. > >How-To-Repeat: > > >Fix: > Workaround is to go into options from sysinstall and change the OS version ta g from 4.0-CURRENT to 4.0-RELEASE. The install works as expected from that poi nt onwards. > > >Release-Note: > >Audit-Trail: > >Unformatted: > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 16 12: 9:50 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id A553537C0BA; Thu, 16 Mar 2000 12:09:47 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id MAA70759; Thu, 16 Mar 2000 12:09:47 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 16 Mar 2000 12:09:47 -0800 (PST) From: Kris Kennaway To: Andrew Gallatin Cc: Howard Leadmon , Doug Rabson , freebsd-alpha@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Trouble with CVSUP to 4.0 Release, any ideas?? In-Reply-To: <14544.62658.595704.938141@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 16 Mar 2000, Andrew Gallatin wrote: > One thing to check would be: did your installworld acutally > complete? At one point the installworld was falling over in h2ph > when a crypto-related header file was being perl'ified. If this is > your problem, try doing a 'make -i installworld' Yep; the problem can be fixed by doing 'make includes; make installworld' - it's caused by a dangling link (des.h) having nothing to point to at the time the perlification runs. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Mar 18 13:57:22 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id AD97437B536; Sat, 18 Mar 2000 13:57:19 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA23476; Sat, 18 Mar 2000 13:57:19 -0800 Date: Sat, 18 Mar 2000 13:57:19 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: wilko@freebsd.org Cc: freebsd-alpha@freebsd.org Subject: Initial Alpha 8200 support is integrated- Alpha Hardware.txt update? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The initial pass at the Alpha 8200 (aka TurboLaser) has been checked in. I've run this on machines up to 2GB in size (some with 2 processors, but we're not using those yet). There's still a lot to do, and the following should be noted: 1. Console For serial console usage (pretty much mostly what the 8200 has, although I hear that newer versions *do* support some kind of frame buffer), either change /etc/ttys to have: console "/usr/libexec/getty std.9600" unknown on secure as the console entry, or add zs0 "/usr/libexec/getty std.9600" unknown on secure and make the zs node: mknod /dev/zs0 c 135 0 [ I would like, in fact, to see console *always* be enabled - that way the real console device will always have a getty, but that's a separate issue ] 2. PCI cards I've tried a variety of cards, but I haven't sat down and checked out type 1 cycles, so I suspect that any card with a bridge will just not work right now. I also, haha, tried the FDDI driver and that's not working, but that's more due to it likely not working on alpha period. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Mar 18 19: 2:47 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 3A20537B5FF; Sat, 18 Mar 2000 19:02:44 -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.9.3/8.9.3) with ESMTP id WAA24397; Sat, 18 Mar 2000 22:02:43 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id WAA14868; Sat, 18 Mar 2000 22:02:13 -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 Date: Sat, 18 Mar 2000 22:02:13 -0500 (EST) To: mjacob@feral.com Cc: wilko@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG Subject: Re: Initial Alpha 8200 support is integrated- Alpha Hardware.txt update? In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14548.17173.404856.658703@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > > The initial pass at the Alpha 8200 (aka TurboLaser) has been checked in. Hurray! And the crowd goes wild! Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message