From owner-freebsd-alpha Sun Mar 14 5:59:52 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from fep10-svc.tin.it (mta10-acc.tin.it [212.216.176.41]) by hub.freebsd.org (Postfix) with ESMTP id 97FAE14C30 for ; Sun, 14 Mar 1999 05:59:49 -0800 (PST) (envelope-from paipai@box4.tin.it) Received: from harlock ([212.216.237.53]) by fep10-svc.tin.it (InterMail v4.0 201-221-105) with SMTP id <19990314135928.QDMI3438.fep10-svc@harlock> for ; Sun, 14 Mar 1999 14:59:28 +0100 From: "Paolo Di Francesco" To: freebsd-alpha@FreeBSD.ORG Date: Sun, 14 Mar 1999 15:07:50 -0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Base kernel package. X-mailer: Pegasus Mail for Win32 (v3.01d) Message-Id: <19990314135928.QDMI3438.fep10-svc@harlock> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I would have some infos about where to find the latest kernel sources. What I need is the basic kernel package for generic platforms to play with. I don't need specific alpha package (I have no Alpha box) but a more generic package to start playing with and to understand the porting path. I have written this mex here, 'coz maybe (probably) this topic has been discussed. 8) Thanks. Ciao Ciao Paolo Di Francesco _ ->B<- All Recycled Bytes Message ... ~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 14 7:48:35 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id F26A51503F for ; Sun, 14 Mar 1999 07:48:32 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id PAA45126; Sun, 14 Mar 1999 15:50:09 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 14 Mar 1999 15:50:09 +0000 (GMT) From: Doug Rabson To: Paolo Di Francesco Cc: freebsd-alpha@freebsd.org Subject: Re: Base kernel package. In-Reply-To: <19990314135928.QDMI3438.fep10-svc@harlock> 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, 14 Mar 1999, Paolo Di Francesco wrote: > Hi, > > I would have some infos about where to find the latest kernel sources. > What I need is the basic kernel package for generic platforms to play > with. I don't need specific alpha package (I have no Alpha box) but a > more generic package to start playing with and to understand the porting > path. > > I have written this mex here, 'coz maybe (probably) this topic has been > discussed. 8) > > Thanks. You can always find the latest kernel sources at ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/src. A very efficient way of tracking this is to mirror the CVS repository using cvsup. This also gives you the complete revision history of all files which is an invaluable resource when working in the kernel (and elsewhere). -- 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 Mon Mar 15 4:49:37 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from octopus.originative (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (Postfix) with ESMTP id A8A5914D74 for ; Mon, 15 Mar 1999 04:49:34 -0800 (PST) (envelope-from paul@originative.co.uk) Received: by octopus with Internet Mail Service (5.5.2232.9) id ; Mon, 15 Mar 1999 12:47:38 -0000 Message-ID: From: paul@originative.co.uk To: alpha@freebsd.org Subject: New bootblocks Date: Mon, 15 Mar 1999 12:47:28 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The new bootblocks have killed my Multia twice over the weekend. Booting [kernel]... /kernel data=0x23e378+0x297a0 syms=[0x8+0x49068+0x8+0x30ee6] halted CPU 0 halt code = 2 kernel stack not valid halt PC = 184ec After the first time this happened I did a fresh install using a snapshot from mirrors.rcn.com, 19990304-SNAP. I then did a clean build of /boot, installed then did disklabel -B -b /boot/boot1 da0 rebooted and the problem was back. The lack of a fixit disk is a real pain :-( Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 15 7:28: 4 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from po9.andrew.cmu.edu (PO9.ANDREW.CMU.EDU [128.2.10.109]) by hub.freebsd.org (Postfix) with ESMTP id E01BF14E06 for ; Mon, 15 Mar 1999 07:27:52 -0800 (PST) (envelope-from tcrimi+@andrew.cmu.edu) Received: (from postman@localhost) by po9.andrew.cmu.edu (8.8.5/8.8.2) id KAA22419; Mon, 15 Mar 1999 10:27:32 -0500 (EST) Received: via switchmail; Mon, 15 Mar 1999 10:27:31 -0500 (EST) Received: from unix6.andrew.cmu.edu via qmail ID ; Mon, 15 Mar 1999 10:26:47 -0500 (EST) Received: from unix6.andrew.cmu.edu via qmail ID ; Mon, 15 Mar 1999 10:26:47 -0500 (EST) Received: from mms.4.60.Jun.27.1996.03.02.53.sun4.51.EzMail.2.0.CUILIB.3.45.SNAP.NOT.LINKED.unix6.andrew.cmu.edu.sun4m.54 via MS.5.6.unix6.andrew.cmu.edu.sun4_51; Mon, 15 Mar 1999 10:26:47 -0500 (EST) Message-ID: Date: Mon, 15 Mar 1999 10:26:47 -0500 (EST) From: Thomas Valentino Crimi To: alpha@freebsd.org, paul@originative.co.uk Subject: Re: New bootblocks In-Reply-To: References: Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Excerpts from FreeBSD-Alpha: 15-Mar-99 New bootblocks by paul@originative.co.uk > halt code = 2 > kernel stack not valid halt > PC = 184ec > I had this same problem, too, making it worse was that I had played around with my boot.conf and guess what, unload was halting (in the older bootblocks, wasn't this recently fixed?) One good replacement to fixit disks I found was that the emergecy shell, while lacking ls (use echo *) did have ifconfig, ppp and mount_nfs if you happen to have a machine nearby to stick an alpha dist on for binaries. The way I got my machine to boot doens't seem like more than luck (replaced bootblocks and booted of an old kernel). Just wanted to share the fixit trick for all who may come to need it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 15 7:42:30 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (Postfix) with ESMTP id 79BFC15306 for ; Mon, 15 Mar 1999 07:42:28 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from bb-b1-11a (pm3a-25.cybcon.com [205.147.75.154]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id HAA06483; Mon, 15 Mar 1999 07:42:06 -0800 (PST) Message-Id: <199903151542.HAA06483@mail.cybcon.com> From: "William Woods" To: "Thomas Valentino Crimi" , , Subject: Alpha and ports..... Date: Mon, 15 Mar 1999 07:40:41 -0800 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am in the process of buying an alpha multia.....just to play with and learn on. I already have FreeBSD on a PPII200 and all is well there. The question I have is this....how are the ports on the alpha distro, specifically, I am interested in Netscape, WP8. How well do these compile? And maby StarOffice 4.0 also. Are there any special cavieats(sp) I should be aware of when compiling ports on an alpha? Thanks Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 15 7:43:48 1999 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 768141537E for ; Mon, 15 Mar 1999 07:43:40 -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.1/8.9.1) with ESMTP id KAA08390; Mon, 15 Mar 1999 10:43:21 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.2/8.9.1) id KAA90477; Mon, 15 Mar 1999 10:43:07 -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: Mon, 15 Mar 1999 10:43:06 -0500 (EST) To: Thomas Valentino Crimi Cc: alpha@FreeBSD.ORG, paul@originative.co.uk Subject: Re: New bootblocks In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14061.10536.602675.696939@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thomas Valentino Crimi writes: > Excerpts from FreeBSD-Alpha: 15-Mar-99 New bootblocks by > paul@originative.co.uk > > halt code = 2 > > kernel stack not valid halt > > PC = 184ec > > > > > I had this same problem, too, making it worse was that I had played > around with my boot.conf and guess what, unload was halting (in the > older bootblocks, wasn't this recently fixed?) > > One good replacement to fixit disks I found was that the emergecy > shell, while lacking ls (use echo *) did have ifconfig, ppp and > mount_nfs if you happen to have a machine nearby to stick an alpha dist > on for binaries. The way I got my machine to boot doens't seem like > more than luck (replaced bootblocks and booted of an old kernel). Just > wanted to share the fixit trick for all who may come to need it. > In addition to the bootblocks, there's also some breakage in revision 1.24 of kern/kern_lock.c which causes alphas to crash in strange ways just after they print the copyright & before they size memory. I've pointed this out to Julian, and he committed a fix last night. Make sure that you have the latest revision of kern_lock.c. If, for whatever reason, you cannot update your sources the fix was: diff -u -b -B -c -r1.24 kern_lock.c *** kern_lock.c 1999/03/12 03:09:29 1.24 --- kern_lock.c 1999/03/15 00:43:37 *************** *** 215,221 **** * lock itself ). */ if (lkp->lk_lockholder != pid) { ! if (p->p_flag & P_DEADLKTREAT) { error = acquire( lkp, extflags, --- 215,221 ---- * lock itself ). */ if (lkp->lk_lockholder != pid) { ! if (p && (p->p_flag & P_DEADLKTREAT)) { error = acquire( lkp, extflags, Cheers, 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 Mon Mar 15 7:44:37 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from octopus.originative (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (Postfix) with ESMTP id 4A0201546D for ; Mon, 15 Mar 1999 07:44:14 -0800 (PST) (envelope-from paul@originative.co.uk) Received: by octopus with Internet Mail Service (5.5.2232.9) id ; Mon, 15 Mar 1999 15:42:18 -0000 Message-ID: From: paul@originative.co.uk To: tcrimi+@andrew.cmu.edu, alpha@freebsd.org, paul@originative.co.uk Subject: RE: New bootblocks Date: Mon, 15 Mar 1999 15:42:15 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > -----Original Message----- > From: Thomas Valentino Crimi [mailto:tcrimi+@andrew.cmu.edu] > Sent: 15 March 1999 15:27 > To: alpha@freebsd.org; paul@originative.co.uk > Subject: Re: New bootblocks > > > Excerpts from FreeBSD-Alpha: 15-Mar-99 New bootblocks by > paul@originative.co.uk > > halt code = 2 > > kernel stack not valid halt > > PC = 184ec > > > > > I had this same problem, too, making it worse was that I had played > around with my boot.conf and guess what, unload was halting (in the > older bootblocks, wasn't this recently fixed?) > > One good replacement to fixit disks I found was that the emergecy > shell, while lacking ls (use echo *) did have ifconfig, ppp and > mount_nfs if you happen to have a machine nearby to stick an > alpha dist > on for binaries. The way I got my machine to boot doens't seem like > more than luck (replaced bootblocks and booted of an old > kernel). Just > wanted to share the fixit trick for all who may come to need it. > Only problem there is that on the Multia there's no vga support so there's no emergency shell either :-( Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 15 8:11:35 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from po9.andrew.cmu.edu (PO9.ANDREW.CMU.EDU [128.2.10.109]) by hub.freebsd.org (Postfix) with ESMTP id 3EA9D14E25 for ; Mon, 15 Mar 1999 08:11:25 -0800 (PST) (envelope-from tcrimi+@andrew.cmu.edu) Received: (from postman@localhost) by po9.andrew.cmu.edu (8.8.5/8.8.2) id LAA26449; Mon, 15 Mar 1999 11:11:04 -0500 (EST) Received: via switchmail; Mon, 15 Mar 1999 11:11:04 -0500 (EST) Received: from unix6.andrew.cmu.edu via qmail ID ; Mon, 15 Mar 1999 11:09:38 -0500 (EST) Received: from unix6.andrew.cmu.edu via qmail ID ; Mon, 15 Mar 1999 11:09:37 -0500 (EST) Received: from mms.4.60.Jun.27.1996.03.02.53.sun4.51.EzMail.2.0.CUILIB.3.45.SNAP.NOT.LINKED.unix6.andrew.cmu.edu.sun4m.54 via MS.5.6.unix6.andrew.cmu.edu.sun4_51; Mon, 15 Mar 1999 11:09:37 -0500 (EST) Message-ID: Date: Mon, 15 Mar 1999 11:09:37 -0500 (EST) From: Thomas Valentino Crimi To: alpha@FreeBSD.ORG, "William Woods" Subject: Re: Alpha and ports..... In-Reply-To: <199903151542.HAA06483@mail.cybcon.com> References: <199903151542.HAA06483@mail.cybcon.com> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Excerpts from mail: 15-Mar-99 Alpha and ports..... by "William Woods"@cybcon.c > The question I have is this....how are the ports on the alpha distro, > specifically, I am interested in Netscape, WP8. How well do these compile? > And maby StarOffice 4.0 also. You picked the exact ports which don't work on the alpha ;) The main problem is, of course, that none of them compile, they are all third party binaries (although there was a post about someone on this list compiling Netscape, is that progressing well?). Netscape has shown great interest in providing an alpha binary, I can't say anything for WP8 and StarOffice, but would speculate that if there begin to exist alpha-linux binaries we would want, that'd be a good direction to move it. As things stand I'll bet compaies which only natively support linux wouldn't support alpha-linux for the same reasons, too small a market. From my experience, just about anything that compiles either works natively, or can be made to work on the alpha unixies. A few things, such as Emacs, gdb, and sml/nj dig a little more 'into the guts' of executables and also need patches to work; patches for the first two exist. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 15 8:13:46 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from octopus.originative (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (Postfix) with ESMTP id EFB5714CE1 for ; Mon, 15 Mar 1999 08:13:43 -0800 (PST) (envelope-from paul@originative.co.uk) Received: by octopus with Internet Mail Service (5.5.2232.9) id ; Mon, 15 Mar 1999 16:11:48 -0000 Message-ID: From: paul@originative.co.uk To: wwoods@cybcon.com, tcrimi+@andrew.cmu.edu, alpha@FreeBSD.ORG, paul@originative.co.uk Subject: RE: Alpha and ports..... Date: Mon, 15 Mar 1999 16:11:38 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > -----Original Message----- > From: William Woods [mailto:wwoods@cybcon.com] > Sent: 15 March 1999 15:41 > To: Thomas Valentino Crimi; alpha@FreeBSD.ORG; paul@originative.co.uk > Subject: Alpha and ports..... > > > I am in the process of buying an alpha multia.....just to > play with and > learn on. I already have FreeBSD on a PPII200 and all is well there. > > The question I have is this....how are the ports on the alpha distro, > specifically, I am interested in Netscape, WP8. How well do > these compile? > And maby StarOffice 4.0 also. Those are all binary only ports so they won't run on the alpha. Even if they did, the chances of them running on a Multia are pretty slim. It's a very slow box, I'd guess 486-pentium era performance from the general feel of the one's I've got. They're ok for playing with, even have some quirks that means there's lots of things to do on the porting front. I bought a couple a few years ago just for the fun of porting FreeBSD to them but I don't think I'll find much serious use for them other than that. I'd only buy a Multia at this point in time if it was very cheap and you have an interest in helping the porting effort since it will not do you much good as an useable desktop machine. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 15 10: 8:50 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from piglet.ucsf.edu (piglet.ucsf.EDU [128.218.67.20]) by hub.freebsd.org (Postfix) with ESMTP id E0F7114F96 for ; Mon, 15 Mar 1999 10:08:12 -0800 (PST) (envelope-from steve@piglet.ucsf.edu) Received: (from steve@localhost) by piglet.ucsf.edu (980427.SGI.8.8.8/970903.SGI.AUTOCF) id KAA87567 for alpha@FreeBSD.ORG; Mon, 15 Mar 1999 10:07:54 -0800 (PST) Date: Mon, 15 Mar 1999 10:07:53 -0800 From: Steve Sizemore To: alpha@FreeBSD.ORG Subject: Which version to run Message-ID: <19990315100753.A87394@cmpharm.ucsf.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, all. Now that I've finally managed to get FreeBSD running on one of my alphas, I'm wondering which version I should be tracking. In order to install, I had to use a 4.0 snapshot. However, I'd really rather track stable (since that's what I use on my intel machines), if that is possible. Is 3.1 stable really stable for the alpha platform, or do I need to use current? Thanks. Steve -- ----------------------------------------------#-----#--#####--------------- # # # # Steve Sizemore # # # Dept. of Cellular and Molecular Pharmacology # # # Box 0450, Room HSE-1285 # # # University of California Medical Center # # # # 513 Parnassus Avenue ##### ##### ##### ####### San Francisco CA 94143-0450 # # # # # steve@cmpharm.ucsf.edu ##### ##### (415) 476-6987 FAX: (415) 476-6515 # # # # # -------------------------------------------------------------#####--#------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 15 10:19: 3 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 89A8215457 for ; Mon, 15 Mar 1999 10:19:01 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id KAA08378; Mon, 15 Mar 1999 10:18:37 -0800 Date: Mon, 15 Mar 1999 10:18:37 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: alpha@FreeBSD.ORG Subject: revisiting...old business...Alpha I/O vs. Mem Mapping In-Reply-To: <14043.64310.216520.299580@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 > Gary Palmer writes: > > found-> vendor=0x1077, dev=0x1020, revid=0x02 > > class=01-00-00, hdrtype=0x00, mfdev=0 > > subordinatebus=0 secondarybus=0 > > intpin=a, irq=17 > > map[0]: type 4, range 32, base 00000000, size 8 > > map[1]: type 1, range 32, base 82221000, size 12 > > Qlogic ISP Driver, FreeBSD CAM Version 0.98, Core Version 1.6 > > isp0: rev 0x02 int a irq 17 on pci1.1.0 > > isp0: using I/O space register mapping > > If I remember right, the 20152 in an AS600 doesn't support I/O space > mapping of devices behind it. That address of 00000000 sure looks > bogus to me anyway.. For devices behind a ppb, we should be checking > that PCIM_CMD_PORTEN is set on the bridge its behind.. I don't really > know how to architect that though.. > > At any rate, try setting SCSI_ISP_PREFER_MEM_MAP to 1 in isp_pci.c & > see if that helps. > > Drew Drew- you wanted to make MEM map the default for all alpha platforms, but I've had a reluctance to do so. If I/O mapping is broken here, perhaps the best place to fix this is in the PCI code? What do you think? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 15 11: 7:42 1999 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 B81D214BDE for ; Mon, 15 Mar 1999 11:07:40 -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.1/8.9.1) with ESMTP id OAA12273; Mon, 15 Mar 1999 14:07:20 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.2/8.9.1) id OAA92284; Mon, 15 Mar 1999 14:07:06 -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: Mon, 15 Mar 1999 14:07:05 -0500 (EST) To: mjacob@feral.com Cc: alpha@FreeBSD.ORG Subject: Re: revisiting...old business...Alpha I/O vs. Mem Mapping In-Reply-To: References: <14043.64310.216520.299580@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14061.22721.176843.417064@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > > If I remember right, the 20152 in an AS600 doesn't support I/O space > > mapping of devices behind it. That address of 00000000 sure looks > > bogus to me anyway.. For devices behind a ppb, we should be checking > > that PCIM_CMD_PORTEN is set on the bridge its behind.. I don't really > > know how to architect that though.. > > > > At any rate, try setting SCSI_ISP_PREFER_MEM_MAP to 1 in isp_pci.c & > > see if that helps. > > > > Drew > > Drew- you wanted to make MEM map the default for all alpha platforms, but > I've had a reluctance to do so. If I/O mapping is broken here, perhaps the > best place to fix this is in the PCI code? What do you think? That's certainly the right thing to do. I don't think I understand the code well enough to do this myself though.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 15 11:12:20 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from po7.andrew.cmu.edu (PO7.ANDREW.CMU.EDU [128.2.10.107]) by hub.freebsd.org (Postfix) with ESMTP id 0350B15121 for ; Mon, 15 Mar 1999 11:12:18 -0800 (PST) (envelope-from tcrimi+@andrew.cmu.edu) Received: (from postman@localhost) by po7.andrew.cmu.edu (8.8.5/8.8.2) id OAA12221 for alpha@freebsd.org; Mon, 15 Mar 1999 14:11:56 -0500 (EST) Received: via switchmail; Mon, 15 Mar 1999 14:11:56 -0500 (EST) Received: from unix6.andrew.cmu.edu via qmail ID ; Mon, 15 Mar 1999 14:11:45 -0500 (EST) Received: from unix6.andrew.cmu.edu via qmail ID ; Mon, 15 Mar 1999 14:11:45 -0500 (EST) Received: from mms.4.60.Jun.27.1996.03.02.53.sun4.51.EzMail.2.0.CUILIB.3.45.SNAP.NOT.LINKED.unix6.andrew.cmu.edu.sun4m.54 via MS.5.6.unix6.andrew.cmu.edu.sun4_51; Mon, 15 Mar 1999 14:11:45 -0500 (EST) Message-ID: Date: Mon, 15 Mar 1999 14:11:45 -0500 (EST) From: Thomas Valentino Crimi To: alpha@freebsd.org Subject: Re: New bootblocks In-Reply-To: References: Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Speaking of which, it seems the new bootblocks are slightly larger (8k up from around 6k), could this be causing this problem: > disklabel -B -b /boot/boot1 da0 boot overlaps used partition a boot overlaps used partition b Warning, boot overlaps partition c, marked as FS_BOOT boot overlaps used partition d disklabel: cannot install boot program i.e. Am I going to have to wipe a partition to get the new bootblocks, as well? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 15 14:41:48 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 8F40015112 for ; Mon, 15 Mar 1999 14:41:43 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id OAA01098 for ; Mon, 15 Mar 1999 14:36:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903152236.OAA01098@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: alpha@freebsd.org Subject: Interesting trap Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Mar 1999 14:36:01 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On a system where the sleepy admin entered: route add the console was filled with arplookup 204.216.28.129 failed, host is not on local network arpresolve: can't allocate llinfo for 204.216.28.129rt (where 204.216.28.129 is the default gateway) followed eventually by a fatal trap (handwritten notes here sorry): trap entry 0x4 (unaligned access) a0 0xfffffe00003111be a1 0x28 a2 0x1 pc 0xfffffc00003e9c28 ra 0xfffffc00003e9a38 ... trap+0x694 XentUna+0x20 ip_input+0x290 -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mon Mar 15 15:30: 3 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 3238B14DDF for ; Mon, 15 Mar 1999 15:29:59 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with SMTP id RAA00191 for ; Mon, 15 Mar 1999 17:29:41 -0600 (CST) Date: Mon, 15 Mar 1999 17:29:41 -0600 (CST) From: Steve Price To: freebsd-alpha@freebsd.org Subject: Ok to set __FreeBSD__=4? 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 Does anyone have any objections to the following patch? I haven't done a full make world with it yet, but it seems harmless enough in -current and brings cc(1) inline with the i386 version. -steve Index: freebsd.h =================================================================== RCS file: /home/ncvs/src/contrib/gcc/config/alpha/freebsd.h,v retrieving revision 1.3 diff -u -r1.3 freebsd.h --- freebsd.h 1998/06/08 10:58:36 1.3 +++ freebsd.h 1999/03/15 23:18:54 @@ -102,7 +102,7 @@ ((len > 1 && !strncmp (str, "gsdb", len)) ? SDB_DEBUG : DBX_DEBUG) #undef CPP_PREDEFINES -#define CPP_PREDEFINES "-Dunix -D__alpha -D__alpha__ -D__ELF__ -D__FreeBSD__=3 -Asystem(unix) -Asystem(FreeBSD) -Acpu(alpha) -Amachine(alpha)" +#define CPP_PREDEFINES "-Dunix -D__alpha -D__alpha__ -D__ELF__ -D__FreeBSD__=4 -D__FreeBSD_cc_version=400001 -Asystem(unix) -Asystem(FreeBSD) -Acpu(alpha) -Amachine(alpha)" #undef LINK_SPEC #define LINK_SPEC "-m elf64alpha \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 15 17:29:36 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 6E67715585 for ; Mon, 15 Mar 1999 17:28:14 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id BAA51250; Tue, 16 Mar 1999 01:30:08 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 16 Mar 1999 01:29:58 +0000 (GMT) From: Doug Rabson To: Thomas Valentino Crimi Cc: alpha@freebsd.org Subject: Re: New bootblocks In-Reply-To: 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 Mon, 15 Mar 1999, Thomas Valentino Crimi wrote: > > Speaking of which, it seems the new bootblocks are slightly larger (8k > up from around 6k), could this be causing this problem: > > > disklabel -B -b /boot/boot1 da0 > boot overlaps used partition a > boot overlaps used partition b > Warning, boot overlaps partition c, marked as FS_BOOT > boot overlaps used partition d > disklabel: cannot install boot program > > > i.e. Am I going to have to wipe a partition to get the new bootblocks, as well? Ouch. It looks like I am going to have to spend some time hacking the bootstrap again. This time, I will try to make it possible to fall back to loader.old. -- 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 Mon Mar 15 18: 2:51 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (Postfix) with ESMTP id 27F4E14CD4 for ; Mon, 15 Mar 1999 18:02:49 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from william (usr1-42.cybcon.com [205.147.76.43]) by mail.cybcon.com (8.9.0/8.9.0) with SMTP id SAA15489 for ; Mon, 15 Mar 1999 18:02:30 -0800 (PST) From: "William Woods" To: Subject: Instructions to install on an Alpha....where ? Date: Mon, 15 Mar 1999 18:02:02 -0800 Message-ID: <000001be6f50$fbf92ab0$2b4c93cd@william> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am in the process of purchasing an Alpha. I am fairly decent with FreeBSD (I have 2 other systems here running it) and all is well with them. My questions is this, where on the net can I find instructions for installing FreeBSD on the Alpha? I know I will need to do it via ftp, that is fine, but where will I find the instructions/directions? Thanks, Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 15 19:25:31 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from bertyboy.sma.uq.edu.au (bertyboy.sma.uq.edu.au [130.102.41.88]) by hub.freebsd.org (Postfix) with ESMTP id E6DA214BFE for ; Mon, 15 Mar 1999 19:25:25 -0800 (PST) (envelope-from talbotn@bertyboy.sma.uq.edu.au) Received: from localhost (talbotn@localhost) by bertyboy.sma.uq.edu.au (8.8.7/8.8.7) with SMTP id NAA01505; Tue, 16 Mar 1999 13:25:18 +1000 (EST) (envelope-from talbotn@bertyboy.sma.uq.edu.au) Date: Tue, 16 Mar 1999 13:25:18 +1000 (EST) From: Talbot NEIL To: William Woods Cc: alpha@FreeBSD.ORG Subject: Re: Instructions to install on an Alpha....where ? In-Reply-To: <000001be6f50$fbf92ab0$2b4c93cd@william> 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 Bill, You will need to get the Boot disks from ftp://ftp.freebsd.org/pub/FreeBSD/releases/snapshots/alpha then you will need to install via ftp URL and put in the address above or your closest mirror. Talbot NEIL On Mon, 15 Mar 1999, William Woods wrote: |I am in the process of purchasing an Alpha. I am fairly decent with FreeBSD |(I have 2 other systems here running it) and all is well with them. My |questions is this, where on the net can I find instructions for installing |FreeBSD on the Alpha? I know I will need to do it via ftp, that is fine, but |where will I find the instructions/directions? | |Thanks, | |Bill | | | |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 Tue Mar 16 3:25: 6 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from itp.ac.ru (itp.ac.ru [193.233.32.4]) by hub.freebsd.org (Postfix) with ESMTP id 07D041518F for ; Tue, 16 Mar 1999 03:24:33 -0800 (PST) (envelope-from ks@itp.ac.ru) Received: from speecart.chg.ru (speecart.chg.ru [193.233.46.2]) by itp.ac.ru (8.9.1/8.9.1) with ESMTP id OAA26830 for ; Tue, 16 Mar 1999 14:31:34 +0300 (MSK) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 16 Mar 1999 14:24:22 +0300 (MSK) Organization: Landau Institute for Theoretical Physics From: "Sergey S. Kosyakov" To: freebsd-alpha@freebsd.org Subject: vidcontrol Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, "vidcontrol -f ..." fails to load screen fonts in 3.1-RELEASE with "device not configured". What does it mean? Sergey. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 16 4:17:51 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 96545154E6 for ; Tue, 16 Mar 1999 04:17:45 -0800 (PST) (envelope-from rene@canyon.demon.nl) Received: from [212.238.15.212] (helo=canyon.demon.nl) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 10Msmk-0000Ee-00 for freebsd-alpha@FreeBSD.ORG; Tue, 16 Mar 1999 12:17:27 +0000 Received: (from rene@localhost) by canyon.demon.nl (8.9.2/8.9.2) id MAA00429 for freebsd-alpha@FreeBSD.ORG; Tue, 16 Mar 1999 12:37:30 +0100 (CET) (envelope-from rene) From: Rene de Vries Message-Id: <199903161137.MAA00429@canyon.demon.nl> Subject: Installing FreeBSD 3.1R To: freebsd-alpha@FreeBSD.ORG Date: Tue, 16 Mar 1999 12:37:30 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL43 (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 Hi, Today I tried to install FreeBSD 3.1 on my small alpha system. It failed ;-( I copied the kern.flp and mfsroot.flp (with fdwrite) to two floppies. I booted the kern.flp and it asked for the mfsroot.flp, so far no problem. Then I get to chose the kind of display I am on (which is an xterm via cu, so I chose ANSI). Then the trouble starts; Labeling the disks somehow failes (it does not say why) and as a result the filesystems don't get mounted. The install still tries to proceed (although it woun't work). The system previously had a netbsd boot block and freebsd 3.0 (pre release) installed. Can anyone explain me what I am doing wrong? Rene -- Rene de Vries http://www.tcja.nl/~rene; mailto:rene@tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 16 11:55:35 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from aries.fortean.com (aries.fortean.com [209.42.229.210]) by hub.freebsd.org (Postfix) with ESMTP id 680C01509C for ; Tue, 16 Mar 1999 11:55:21 -0800 (PST) (envelope-from walter@fortean.com) Received: from localhost (walter@localhost) by aries.fortean.com (8.8.8/8.8.8) with SMTP id OAA29585 for ; Tue, 16 Mar 1999 14:53:39 -0500 (EST) (envelope-from walter@fortean.com) X-Authentication-Warning: aries.fortean.com: walter owned process doing -bs Date: Tue, 16 Mar 1999 14:53:39 -0500 (EST) From: "Bruce M. Walter" Reply-To: "Bruce M. Walter" To: freebsd-alpha@freebsd.org Subject: Multia X-Files... 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 Hello all, This is not a complaint or request for help... Merely a report of my recent experiences with FreeBSD/alpha. I have a Personal Workstation 500au which I will eventually move into a role as my development server and thought it best to also pick up a Multia or two to act as frontline machines for tracking current, stable and such. 3.1-R seemed quite happy on my Miata (once I had labeled the disks with the 4.0-C utility ;) so I figured it was the place to start for the Multia as well. I've pretty much found that older Quantum drives + the NCR controller = CCB already dequeued problems, so I picked up an el-cheapo Fireball ST. It's working, although the tagged openings have a tendency to decrease and I can't turn off tagged queueing from camcontrol without freezing the drive. Unfortunately, I was unable to get the 4.0-C kernel from the 2/6 snap to load because of the kern_lock problems Julian fixed last night (thanks!), so I wound up using a 3.1-R kern.flp along with a 3.1-S mfsroot.flp to partition and install the 3.1-R distributions. This worked and produced a complete 3.1-R system I was able to build a kernel from. Now we get into the X-Files part ;) The system, under both 3.1-R and 3.1-S, would reboot without warning, apparently at random. This condition persisted. After several attempts at building world I assumed it to be faulty hardware, most likely memory. Since I had access to another Multia NCR controller, I popped it in... Still problems. Finally, the machine dropped into the the debugger instead of rebooting with no messages. The message was panic: ffs_valloc: dup inode In doing some searching, I found alot of similarities between my situation and the 'Dave Rivers memorial panic.' This in and of itself didn't seem strange, as I thought Dave's problems to be hardware related at the time. What *IS* a mystery to me is now that I can boot a 4.0-C kernel, the problems appear to be gone. With sources cvsupped as of late last night, I've built world successfully twice. I realize this is probably not very helpful, but wanted to post my observations. This could be either: 1) Matt's recent fixes to the VM stuff has produced VM code which doesn't exercise the faults in my hardware -or- 2) Matt's recent fixes to the VM stuff 'exorcised' the bugs causing my problems and possibly one of the more elusive, recurring panics in recent releases. I wonder if Dave still runs that old news server ;) Hopefully the second is true. Now, if I can just figure out how to get rid of those annoying dec_axppci_33_intr_map: bad interrupt pin 30 messages during the Multia's PCI probe, I'd be a happy man. Ideas anyone? - Bruce ______________________ Bruce M. Walter, Principal NIXdesign Group Inc. 426 S. Dawson Street Raleigh NC 27601 USA 919.829.4901 Tel (ext 11) 919.829.4993 Fax http://www.nixdesign.com Visual communications | concept + code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 16 13:20:43 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id D3BB915230 for ; Tue, 16 Mar 1999 13:20:08 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id VAA53561; Tue, 16 Mar 1999 21:22:04 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 16 Mar 1999 21:22:04 +0000 (GMT) From: Doug Rabson To: "Bruce M. Walter" Cc: freebsd-alpha@freebsd.org Subject: Re: Multia X-Files... In-Reply-To: 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 Tue, 16 Mar 1999, Bruce M. Walter wrote: > Hello all, > > This is not a complaint or request for help... Merely a report of my > recent experiences with FreeBSD/alpha. I have a Personal Workstation > 500au which I will eventually move into a role as my development server > and thought it best to also pick up a Multia or two to act as frontline > machines for tracking current, stable and such. > > 3.1-R seemed quite happy on my Miata (once I had labeled the disks with > the 4.0-C utility ;) so I figured it was the place to start for the Multia > as well. I've pretty much found that older Quantum drives + the NCR > controller = CCB already dequeued problems, so I picked up an el-cheapo > Fireball ST. It's working, although the tagged openings have a tendency > to decrease and I can't turn off tagged queueing from camcontrol without > freezing the drive. > > Unfortunately, I was unable to get the 4.0-C kernel from the 2/6 snap to > load because of the kern_lock problems Julian fixed last night (thanks!), > so I wound up using a 3.1-R kern.flp along with a 3.1-S mfsroot.flp to > partition and install the 3.1-R distributions. This worked and produced a > complete 3.1-R system I was able to build a kernel from. > > Now we get into the X-Files part ;) The system, under both 3.1-R and > 3.1-S, would reboot without warning, apparently at random. This condition > persisted. After several attempts at building world I assumed it to be > faulty hardware, most likely memory. Since I had access to another Multia > NCR controller, I popped it in... Still problems. Finally, the machine > dropped into the the debugger instead of rebooting with no messages. The > message was I don't know what the exact reason for the spontaneous reboots might be but I suspect dodgy hardware. Do these multias run any other operating systems successfully? > > panic: ffs_valloc: dup inode > > In doing some searching, I found alot of similarities between my situation > and the 'Dave Rivers memorial panic.' This in and of itself didn't seem > strange, as I thought Dave's problems to be hardware related at the time. > What *IS* a mystery to me is now that I can boot a 4.0-C kernel, the > problems appear to be gone. With sources cvsupped as of late last night, > I've built world successfully twice. I have often seen this after rebooting from a crash. It is caused by fsck not picking up some inconsistency of the disk I think. > > I realize this is probably not very helpful, but wanted to post my > observations. This could be either: > > 1) Matt's recent fixes to the VM stuff has produced VM code which doesn't > exercise the faults in my hardware -or- > > 2) Matt's recent fixes to the VM stuff 'exorcised' the bugs causing my > problems and possibly one of the more elusive, recurring panics in > recent releases. I wonder if Dave still runs that old news server ;) > > Hopefully the second is true. Now, if I can just figure out how to get rid > of those annoying > > dec_axppci_33_intr_map: bad interrupt pin 30 > > messages during the Multia's PCI probe, I'd be a happy man. Ideas anyone? Possibly dodgy firmware? -- 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 Tue Mar 16 13:51:12 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from aries.fortean.com (aries.fortean.com [209.42.229.210]) by hub.freebsd.org (Postfix) with ESMTP id 23B2515143 for ; Tue, 16 Mar 1999 13:50:46 -0800 (PST) (envelope-from walter@fortean.com) Received: from localhost (walter@localhost) by aries.fortean.com (8.8.8/8.8.8) with SMTP id QAA00336; Tue, 16 Mar 1999 16:49:05 -0500 (EST) (envelope-from walter@fortean.com) X-Authentication-Warning: aries.fortean.com: walter owned process doing -bs Date: Tue, 16 Mar 1999 16:49:05 -0500 (EST) From: "Bruce M. Walter" To: Doug Rabson Cc: freebsd-alpha@freebsd.org Subject: Re: Multia X-Files... In-Reply-To: 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 don't know what the exact reason for the spontaneous reboots might be > but I suspect dodgy hardware. Do these multias run any other operating > systems successfully? NT successfully, but that's not to say I actually consider it an OS ;) Since this is exactly why I have these boxes, I'll try to burn one down asap and try Linux or NetBSD on it. > > panic: ffs_valloc: dup inode [ SNIP ] > I have often seen this after rebooting from a crash. It is caused by fsck > not picking up some inconsistency of the disk I think. That could be... Maybe I was just hoping that the VM is finally past the 'Dave Rivers panic' stage. I could believe it's the hardware, except that under 4.0-C it seems bulletproof. I'm going to continue hammering one of these boxes and see what results. > > dec_axppci_33_intr_map: bad interrupt pin 30 > Possibly dodgy firmware? I saw in the archives another Multia person had these messages. They appear to be harmless. This message appears on Multia's but not UDB's. I've flashed the SRM console/firmware to the latest available from DEC. Hmmmm. Is there a pattern here? On boot I get 6 pin 30's right after the probe message Probing for devices on PCI bus 0: 6 times ncr0: rev 0x01 inta irq 11 on pci0.6.0 chip0: rev 0x03 on pci0.7.0 de0: rev 0x23 int a irq 15 on pci0.8.0 1 time 16 times Is the fact I get 6 messages then find a device at pci0.6.0 a coincidence? Also, some (warm?) warm boots under the 3.1-S kernel finds the following before the isa probe and it's associated pin 30 messages: vga0: rev 0x00 on pci0.14.0 (There's no vga device in there... Not even an expansion slot until recently) So, is it possible these messages are a result of the pci probe code stepping through all of the non-connected PCI addresses on the bus? Could it be that because there is no possible way a device could ever show up there (ie: no expansion bus) the chip just fires back interrupts on pin 30? (Forgive my ignorance of the PCI code if this is not the way things work... I've not had a chance to become aquainted adequately with the PCI code ;) - Bruce ______________________ Bruce M. Walter, Principal NIXdesign Group Inc. 426 S. Dawson Street Raleigh NC 27601 USA 919.829.4901 Tel (ext 11) 919.829.4993 Fax http://www.nixdesign.com Visual communications | concept + code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 16 14: 0:32 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id C43FC151B5 for ; Tue, 16 Mar 1999 14:00:27 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id WAA53760; Tue, 16 Mar 1999 22:02:37 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 16 Mar 1999 22:02:37 +0000 (GMT) From: Doug Rabson To: "Bruce M. Walter" Cc: freebsd-alpha@freebsd.org Subject: Re: Multia X-Files... In-Reply-To: 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 Tue, 16 Mar 1999, Bruce M. Walter wrote: > > I don't know what the exact reason for the spontaneous reboots might be > > but I suspect dodgy hardware. Do these multias run any other operating > > systems successfully? > > NT successfully, but that's not to say I actually consider it an OS ;) > Since this is exactly why I have these boxes, I'll try to burn one down > asap and try Linux or NetBSD on it. > > > > panic: ffs_valloc: dup inode > [ SNIP ] > > I have often seen this after rebooting from a crash. It is caused by fsck > > not picking up some inconsistency of the disk I think. > > That could be... Maybe I was just hoping that the VM is finally past the > 'Dave Rivers panic' stage. I could believe it's the hardware, except that > under 4.0-C it seems bulletproof. I'm going to continue hammering one of > these boxes and see what results. > > > > dec_axppci_33_intr_map: bad interrupt pin 30 > > Possibly dodgy firmware? > > I saw in the archives another Multia person had these messages. They > appear to be harmless. This message appears on Multia's but not UDB's. > I've flashed the SRM console/firmware to the latest available from DEC. > > Hmmmm. Is there a pattern here? > > On boot I get 6 pin 30's right after the probe message > > Probing for devices on PCI bus 0: > 6 times > ncr0: rev 0x01 inta irq 11 on pci0.6.0 > chip0: rev 0x03 on pci0.7.0 > de0: rev 0x23 int a irq 15 on pci0.8.0 > 1 time > 16 times > > > Is the fact I get 6 messages then find a device at pci0.6.0 a coincidence? > Also, some (warm?) warm boots under the 3.1-S kernel finds the following > before the isa probe and it's associated pin 30 messages: > > vga0: rev 0x00 on pci0.14.0 > (There's no vga device in there... Not even an expansion slot until > recently) > > So, is it possible these messages are a result of the pci probe code > stepping through all of the non-connected PCI addresses on the bus? Could > it be that because there is no possible way a device could ever show up > there (ie: no expansion bus) the chip just fires back interrupts on pin > 30? > > (Forgive my ignorance of the PCI code if this is not the way things > work... I've not had a chance to become aquainted adequately with the > PCI code ;) Possibly the code is seeing some sort of phantom device? Does it print anything more interesting for a verbose boot (boot -flags v from SRM)? -- 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 Tue Mar 16 14:11: 6 1999 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 5509A151A2 for ; Tue, 16 Mar 1999 14:10:50 -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.1/8.9.1) with ESMTP id RAA02161; Tue, 16 Mar 1999 17:09:54 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.2/8.9.1) id RAA96764; Tue, 16 Mar 1999 17:09:37 -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: Tue, 16 Mar 1999 17:09:36 -0500 (EST) To: Dave Cherkus Cc: port-alpha@netbsd.org, freebsd-alpha@freebsd.org Subject: Re: multia/tga console In-Reply-To: <199903162133.QAA06420@homerun.unimaster.com> References: <199903142022.PAA16947@js.ne.mediaone.net> <199903162133.QAA06420@homerun.unimaster.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14062.54354.294597.390180@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dave Cherkus writes: > > So, wasn't someone mentioning kernel profiling before? > > Anyone up for porting IPROBE? > I've ported it to FreeBSD/alpha. That might make a good starting point for somebody doing a NetBSD port. I've submitted my (FreeBSD) changes to the maintainer, but I'm not sure if there's a new release out yet which includes them. If not, you can grab my sources from: ftp://ftp.cs.duke.edu/pub/gallatin/freebsd_iprobe.tar.gz 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 Tue Mar 16 21:54:17 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CFB4F150CD for ; Tue, 16 Mar 1999 21:54:08 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id VAA16388 for ; Tue, 16 Mar 1999 21:53:46 -0800 Date: Tue, 16 Mar 1999 21:53:46 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: alpha@freebsd.org Subject: Alpha FreeBSD badness (fwd) 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 Wierd. I was running NetBSD-alpha/current on this machine. Then I halted it and booted FreeBSD-alpha. It blew up in cia_bwx_inw. It only worked again after I did an 'init' at the SRM prompt. It looks like state is a bit sticky! ---------- Forwarded message ---------- Date: Tue, 16 Mar 1999 21:49:06 -0800 (PST) From: Matthew Jacob To: Matthew Jacob Subject: Alpha FreeBSD badness (fwd) even more: isp1: rev 0x02 int a irq 3 on pci0.9.0 isp1: using I/O space register mapping unexpected machine check: mces = 0x1 vector = 0x660 param = 0xfffffc0000006060 pc = 0xfffffc00004d7638 ra = 0xfffffc00004d7610 curproc = 0 panic: machine check panic Stopped at Debugger..ng+0x24: ldq ra,0(sp) <0xfffffc0000621990> ---------- Forwarded message ---------- Date: Tue, 16 Mar 1999 21:43:51 -0800 From: Matthew Jacob To: mjacob@feral.com Subject: Alpha FreeBSD badness unexpected machine check: mces = 0x1 vector = 0x660 param = 0xfffffc0000006060 pc = 0xfffffc00004d7838 ra = 0xfffffc00004d7810 curproc = 0 panic: machine check panic Stopped at Debugger..ng+0x24: ldq ra,0(sp) <0xfffffc00006210e0> db> db> db> db> t Debugger..ng() at Debugger..ng+0x24 panic..ng() at panic..ng+0xf0 machine_check..ng() at machine_check..ng+0x1fc interrupt..ng() at interrupt..ng+0x150 XentInt() at XentInt+0x1c cia_bwx_inw..ng() at cia_bwx_inw..ng+0x18 (null)() at 0x4 db> machine halt No such command --- - \ Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel]... /kernel data=0x2682c0+0x2e8c8 syms=[0x8+0x4d820+0x8+0x341ca] Entering kernel at 0xfffffc00003233a0... Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #6: Thu Mar 4 09:45:40 PST 1999 mjacob@farrago.feral.com:/space/sys/compile/FARRAGO EB164 Digital AlphaPC 164 432 MHz, 432MHz 8192 byte page size, 1 processor. CPU: EV56 (21164A) major=7 minor=1 extensions=0x1 OSF PAL rev: 0x1000800020115 real memory = 265961472 (259728K bytes) avail memory = 253714432 (247768K bytes) Preloaded elf kernel "kernel" at 0xfffffc000061c000. ccd0-3: Concatenated disk drivers cia0: <2117x PCI adapter> cia0: ALCOR/ALCOR2, pass 3 cia0: extended capabilities: 21 isa0 Probing for devices on PCI bus 0: Qlogic ISP Driver, FreeBSD CAM Version 0.98, Core Version 1.6 isp0: rev 0x05 int a irq 2 on pci0.5.0 isp0: using I/O space register mapping isp0: set PCI line size to 16 isp0: Ultra Mode Capable isp0: Board Revision 1040B, loaded F/W Revision 7.55 isp0: Last F/W revision was 2.10 ncr0: rev 0x02 int a irq 0 on pci0.6.0 de0: rev 0x20 int a irq 1 on pci0.7.0 de0: 21140A [10-100Mb/s] pass 2.0 de0: address 00:c0:f0:16:2d:7c chip0: rev 0x43 on pci0.8.0 isp1: rev 0x02 int a irq 3 on pci0.9.0 isp1: using I/O space register mapping isp1: set PCI line size to 16 isp1: Board Revision 2100, loaded F/W Revision 1.15 isp1: Adapter WWN 0x200000e08b00e100 isp1: Firmware State Config Wait -> Waiting for AL/PA isp1: Firmware State Waiting for AL/PA -> Wait Login isp1: Firmware State Wait Login -> Waiting for AL/PA isp1: isp_mboxcmd timeout #1 isp1: but we'll try again, isr=8008 isp1: Port Database Changed isp1: Firmware State Waiting for AL/PA -> Ready isp1: Loop ID 113, ALPA 0x23 mcclock0: at port 0x70-0x71 on isa0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A, console atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 struct nfssvc_sock bloated (> 256bytes) Try reducing NFS_UIDHASHSIZ struct nfsuid bloated (> 128bytes) Try unionizing the nu_nickname and nu_flag fields Timecounter "alpha" frequency 432900432 Hz de0 XXX: driver didn't set ifq_maxlen Waiting 2 seconds for SCSI devices to settle isp0: driver initiated bus reset isp1: driver initiated bus reset de0: enabling 100baseTX port isp1: Loop DOWN (noperiph:isp1:0:-1:-1): freezing SIMQ until loop comes up (probe59:isp1:0:29:0): isp_done releasing SIMQ da2 at ncr0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 2040MB (4178874 512 byte sectors: 255H 63S/T 260C) da1 at isp0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4095MB (8386733 512 byte sectors: 255H 63S/T 522C) da0 at isp0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) WARNING: clock gained 12 days -- CHECK AND RESET THE DATE! Start pid=2 Start pid=3 Start pid=4 swapon: adding /dev/da1b as swap device Automatic reboot in progress... /dev/rda1a: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/rda1a: clean, 3227299 free (34115 frags, 399148 blocks, 0.9% fragmentation) Doing initial network setup: hostname domain. de0: flags=8843 mtu 1500 inet 192.67.166.23 netmask 0xffffff00 broadcast 192.67.166.255 ether 00:c0:f0:16:2d:7c media: autoselect (100baseTX) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 add net default: gateway 192.67.166.126 Additional routing options: tcp extensions=NO. routing daemons:. Mounting NFS file systems. recording kernel -c changes additional daemons: syslogd. Doing additional network setup: ntpdate xntpd portmap ypbind. Starting final network daemons: nfsiod. setting ELF ldconfig path: /usr/lib /usr/lib/compat /usr/local/lib setting a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout ldconfig: illegal option -- a usage: ldconfig [-Rmrsv] [-f hints_file] [dir | file ...] starting standard daemons: inetd cron. Initial rc.alpha initialization:. rc.alpha configuring syscons: blank_time/etc/rc.alpha: cannot open /dev/ttyv0: no such device or address . Local package initialization:. starting local daemons:. vfs.ffs.doreallocblks: 1 -> 0 Tue Mar 16 21:51:33 PST 1999 FreeBSD/alpha (farrago.feral.com) (ttyd0) login: isp1: LIP occurred isp1: Loop UP (noperiph:isp1:0:-1:-1): isp1: Port Database Changed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 16 22: 0:13 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B810414F50 for ; Tue, 16 Mar 1999 22:00:10 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id FAA81357; Wed, 17 Mar 1999 05:59:50 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA07585; Tue, 16 Mar 1999 22:59:38 -0700 (MST) Message-Id: <199903170559.WAA07585@harmony.village.org> To: "Bruce M. Walter" Subject: Re: Multia X-Files... Cc: freebsd-alpha@FreeBSD.ORG In-reply-to: Your message of "Tue, 16 Mar 1999 16:49:05 EST." References: Date: Tue, 16 Mar 1999 22:59:38 -0700 From: Warner Losh Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message "Bruce M. Walter" writes: : That could be... Maybe I was just hoping that the VM is finally past the : 'Dave Rivers panic' stage. I could believe it's the hardware, except that Don't you mean the 'David Rivers Memorial Panic'[tm] :-) I thought that died in the 3.x branch a long time ago... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 16 22: 6:47 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from callisto.fortean.com (callisto.fortean.com [209.42.229.241]) by hub.freebsd.org (Postfix) with ESMTP id 89E6315185 for ; Tue, 16 Mar 1999 22:06:30 -0800 (PST) (envelope-from walter@fortean.com) Received: from localhost (walter@localhost) by callisto.fortean.com (8.8.8/8.8.5) with SMTP id BAA11040; Wed, 17 Mar 1999 01:04:53 -0500 (EST) X-Authentication-Warning: callisto.fortean.com: walter owned process doing -bs Date: Wed, 17 Mar 1999 01:04:52 -0500 (EST) From: "Bruce M. Walter" To: Warner Losh Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Multia X-Files... In-Reply-To: <199903170559.WAA07585@harmony.village.org> 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 > Don't you mean the 'David Rivers Memorial Panic'[tm] :-) I thought > that died in the 3.x branch a long time ago... The one and only... I had hoped it did. Poking around the archives showed a few cases with strong similarities, but I really think the majority are dodgy hardware. I wouldn't be surprised if my own Multia problems were hardware as well. At least in regards to the spontaneous reboots. As for the dec_axppci_33 messages, booting verbose does in fact show the detection of a bogus phantom device for each pin 30 message. I don't think this is flaky hardware as much as it is a Multia-specific quirk. It happens on both of mine, and I remember seeing a message from Mike Smith that it happens on his too. (Sorry, Mike, if I'm misremembering) - Bruce PS: I'll post a dmesg with the bogus probe info as soon as I get my box back in shape. ______________________ Bruce M. Walter, Principal NIXdesign Group Inc. 426 S. Dawson Street Raleigh NC 27601 USA 919.829.4901 Tel (ext 11) 919.829.4993 Fax http://www.nixdesign.com Visual communications | concept + code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 16 23:55:37 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from callisto.fortean.com (callisto.fortean.com [209.42.229.241]) by hub.freebsd.org (Postfix) with ESMTP id 2C75215217 for ; Tue, 16 Mar 1999 23:55:25 -0800 (PST) (envelope-from walter@fortean.com) Received: from localhost (walter@localhost) by callisto.fortean.com (8.8.8/8.8.5) with SMTP id CAA11421; Wed, 17 Mar 1999 02:53:51 -0500 (EST) X-Authentication-Warning: callisto.fortean.com: walter owned process doing -bs Date: Wed, 17 Mar 1999 02:53:51 -0500 (EST) From: "Bruce M. Walter" To: Doug Rabson Cc: freebsd-alpha@FreeBSD.org Subject: dec_axppci_33_intr_map: bad interrupt pin 30 In-Reply-To: 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 > > > > dec_axppci_33_intr_map: bad interrupt pin 30 > > Possibly the code is seeing some sort of phantom device? Does it print > anything more interesting for a verbose boot (boot -flags v from SRM)? This appears to be the case. Booting verbose always seems to drop me into the debugger for all my kernels by panicing during the ifmedia_ioctl call. Debugger..ng() at Debugger..ng+0x24 panic..ng() at panic..ng+0xf0 trap..ng() at trap..ng+0x6a4 XentMM() at XentMM+0x20 ifmedia_ioctl..ng() at ifmedia_ioctl..ng+0x148 (null)() at 0x4 pciconf on the other hand produces this interesting output: none0@pci0:0:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 none1@pci0:1:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 none2@pci0:2:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 none3@pci0:3:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 none4@pci0:4:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 none5@pci0:5:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 ncr0@pci0:6:0: class=0x000000 card=0x00000000 chip=0x00011000 rev=0x01 hdr=0x00 chip0@pci0:7:0: class=0x000000 card=0x00000000 chip=0x04848086 rev=0x03 hdr=0x00 de0@pci0:8:0: class=0x020000 card=0x00000000 chip=0x00021011 rev=0x23 hdr=0x00 none6@pci0:9:0: class=0x000000 card=0x00000001 chip=0x00000001 rev=0x01 hdr=0x00 none7@pci0:10:0: class=0x000000 card=0x00000001 chip=0x00000001 rev=0x01 hdr=0x00 none8@pci0:11:0: class=0x038000 card=0x00000000 chip=0x00041011 rev=0x02 hdr=0x00 none9@pci0:12:0: class=0x000410 card=0x00000000 chip=0x00041011 rev=0x11 hdr=0x04 vga0@pci0:14:0: class=0x000100 card=0x00000000 chip=0x000000c0 rev=0x00 hdr=0x0f none10@pci0:15:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 none11@pci0:16:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 none12@pci0:17:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 none13@pci0:18:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 none14@pci0:19:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 none15@pci0:20:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 none16@pci0:21:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 none17@pci0:22:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 none18@pci0:23:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 none19@pci0:24:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 none20@pci0:25:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 none21@pci0:26:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 none22@pci0:27:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 none23@pci0:28:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 none24@pci0:29:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 none25@pci0:30:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 none26@pci0:31:0: class=0x00001e card=0x00001e03 chip=0x00001e03 rev=0x03 hdr=0x00 Since I don't have a dmesg, here's a snippet from the log: found-> vendor=0x1011, dev=0x0004, revid=0x02 class=03-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 3, range 32, base 88000000, size 25 dec_axppci_33_intr_map: bad interrupt pin 16 found-> vendor=0x1011, dev=0x0004, revid=0x11 class=00-04-10, hdrtype=0x04, mfdev=0 subordinatebus=0 secondarybus=0 intpin=p, irq=17 found-> vendor=0x00c0, dev=0x0000, revid=0x00 class=00-01-00, hdrtype=0x0f, mfdev=0 subordinatebus=0 secondarybus=0 vga0: rev 0x00 on pci0.14.0 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e03, dev=0x0000, revid=0x03 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=3 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e03, dev=0x0000, revid=0x03 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=3 And so on. - Bruce ______________________ Bruce M. Walter, Principal NIXdesign Group Inc. 426 S. Dawson Street Raleigh NC 27601 USA 919.829.4901 Tel (ext 11) 919.829.4993 Fax http://www.nixdesign.com Visual communications | concept + code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 17 0: 0: 0 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (Postfix) with ESMTP id 7BDA9152B6 for ; Tue, 16 Mar 1999 23:59:59 -0800 (PST) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id XAA03611; Tue, 16 Mar 1999 23:59:25 -0800 (PST) Message-Id: <199903170759.XAA03611@lestat.nas.nasa.gov> To: "Bruce M. Walter" Cc: Doug Rabson , freebsd-alpha@FreeBSD.ORG Subject: Re: dec_axppci_33_intr_map: bad interrupt pin 30 Reply-To: Jason Thorpe From: Jason Thorpe Date: Tue, 16 Mar 1999 23:59:24 -0800 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 17 Mar 1999 02:53:51 -0500 (EST) "Bruce M. Walter" wrote: > pciconf on the other hand produces this interesting output: You suffer from classical Buggy Multia Firmware Syndrome. -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 17 1:58:40 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 34FDF14EA7 for ; Wed, 17 Mar 1999 01:58:39 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA62461; Wed, 17 Mar 1999 01:59:00 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Steve Sizemore Cc: alpha@FreeBSD.ORG Subject: Re: Which version to run In-reply-to: Your message of "Mon, 15 Mar 1999 10:07:53 PST." <19990315100753.A87394@cmpharm.ucsf.edu> Date: Wed, 17 Mar 1999 01:59:00 -0800 Message-ID: <62436.921664740@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > install, I had to use a 4.0 snapshot. However, I'd really rather > track stable (since that's what I use on my intel machines), if that > is possible. Is 3.1 stable really stable for the alpha platform, or > do I need to use current? It might be better to track -current just for a little while, at least until 3.1-stable catches up for the alpha. I don't think it's actually diverged all that much at all; Doug? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 17 9:55:37 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.suse.de (Cantor.suse.de [194.112.123.193]) by hub.freebsd.org (Postfix) with ESMTP id 114B315271 for ; Wed, 17 Mar 1999 09:55:28 -0800 (PST) (envelope-from stepan@suse.de) Received: from Galois.suse.de (Galois.suse.de [194.112.123.130]) by mail.suse.de (Postfix) with ESMTP id 45A7732CE4; Wed, 17 Mar 1999 18:55:08 +0100 (MET) Received: by Galois.suse.de (Postfix, from userid 0) id 1160D9410; Wed, 17 Mar 1999 18:55:08 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by Galois.suse.de (Postfix) with ESMTP for id 1039C7416; Wed, 17 Mar 1999 18:55:08 +0100 (MET) Date: Wed, 17 Mar 1999 18:55:08 +0100 (MET) From: Stefan Reinauer To: freebsd-alpha@freebsd.org Subject: faked BSD disklabel to boot from SRM Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, sorry, I know that this may not be the right place to ask such questions but this list is afaik the only one whose readers may have the knowledge to answer my questions. The Alpha SRM console needs a BSD disklabel in the first block with an offset of 64 and a bootstrap in the following 8k to boot from a disk. Now I have a disk with an MSDOS disklabel from which I want to boot. I thought of having an MSDOS disklabel in the first 512 bytes (it isn't moveable) and a BSD disklabel in block 1 or later, similar to how this is handled on ia32 machines. The problem is, that SRM console won't boot from a disk with a disklabel in the second sector (at least it is so, if my patched bootstrap writer didn't do anything wrong) Is there any other method to make SRM console think it can boot from an MSDOS disklabel disk? Or do you have a theory how this could be done? If I left out any neccessary data, please tell me. Thanks for your time and help. Regards, Stefan. --=20 SuSE GmbH Can you afford *NOT* Schanz=E4ckerstr. 10 to use Linux? D-90443 N=FCrnberg =09 Germany =09=09=09AlphaPowered To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 17 11:15:52 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id C8FFC151D6 for ; Wed, 17 Mar 1999 11:15:50 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id EAA00920; Thu, 18 Mar 1999 04:15:46 +0900 (JST) Message-ID: <36EFFD39.7BAADBD3@newsguy.com> Date: Thu, 18 Mar 1999 04:06:33 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: alpha@freebsd.org Subject: [Fwd: Re: Multia X-Files...] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Since my message was prvt, I'm thus forwarding your real request to -alpha... :-) -------- Original Message -------- From: "Bruce M. Walter" Subject: Re: Multia X-Files... To: "Daniel C. Sobral" > > This is not a complaint or request for help... Merely a report of my > [...] > > messages during the Multia's PCI probe, I'd be a happy man. Ideas anyone? > > Is that a request? ;-> Nah... Actually, I'm sorry I got what I asked for. Turns out my Multia has a case of braindead firmware. Which brings me to a real request ;) Does anyone out there have a copy of the unreleased DEC Multia firmware that fixes this? The NetBSD faq say Chris Demitrio has a copy, but since I haven't heard back from him yet I'd love to know if there's a copy floating around. - Bruce ______________________ Bruce M. Walter, Principal NIXdesign Group Inc. 426 S. Dawson Street Raleigh NC 27601 USA 919.829.4901 Tel (ext 11) 919.829.4993 Fax http://www.nixdesign.com Visual communications | concept + code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 17 12:49:24 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 5A7A515339 for ; Wed, 17 Mar 1999 12:49:20 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA56182; Wed, 17 Mar 1999 20:51:23 GMT (envelope-from dfr@nlsystems.com) Date: Wed, 17 Mar 1999 20:51:23 +0000 (GMT) From: Doug Rabson To: "Jordan K. Hubbard" Cc: Steve Sizemore , alpha@freebsd.org Subject: Re: Which version to run In-Reply-To: <62436.921664740@zippy.cdrom.com> 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, 17 Mar 1999, Jordan K. Hubbard wrote: > > install, I had to use a 4.0 snapshot. However, I'd really rather > > track stable (since that's what I use on my intel machines), if that > > is possible. Is 3.1 stable really stable for the alpha platform, or > > do I need to use current? > > It might be better to track -current just for a little while, > at least until 3.1-stable catches up for the alpha. I don't > think it's actually diverged all that much at all; Doug? The main difference is that -current uses the new portable syscons. I do intend to merge that over at some point but I can't predict when. -- 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 17 12:55:22 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 2C90214D4B for ; Wed, 17 Mar 1999 12:55:19 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA56201; Wed, 17 Mar 1999 20:57:24 GMT (envelope-from dfr@nlsystems.com) Date: Wed, 17 Mar 1999 20:57:24 +0000 (GMT) From: Doug Rabson To: Stefan Reinauer Cc: freebsd-alpha@freebsd.org Subject: Re: faked BSD disklabel to boot from SRM In-Reply-To: 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, 17 Mar 1999, Stefan Reinauer wrote: > Hi, > > sorry, I know that this may not be the right place to ask such questions > but this list is afaik the only one whose readers may have the knowledge > to answer my questions. > > The Alpha SRM console needs a BSD disklabel in the first block with an > offset of 64 and a bootstrap in the following 8k to boot from a disk. > > Now I have a disk with an MSDOS disklabel from which I want to boot. I > thought of having an MSDOS disklabel in the first 512 bytes (it isn't > moveable) and a BSD disklabel in block 1 or later, similar to how this is > handled on ia32 machines. > The problem is, that SRM console won't boot from a disk with a disklabel > in the second sector (at least it is so, if my patched bootstrap writer > didn't do anything wrong) > > Is there any other method to make SRM console think it can boot from an > MSDOS disklabel disk? Or do you have a theory how this could be done? > > If I left out any neccessary data, please tell me. > > Thanks for your time and help. I thought about this too a long time ago. Unfortunately the fields in the first sector which SRM uses to point at the bootstrap overlaps with the MSDOS partition table. It just isn't possible to make a disk bootable from both SRM and AlphaBIOS (which is why I wanted to do it). -- 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 17 13:22:39 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.suse.de (Cantor.suse.de [194.112.123.193]) by hub.freebsd.org (Postfix) with ESMTP id 5F77D1548C for ; Wed, 17 Mar 1999 13:22:36 -0800 (PST) (envelope-from stepan@suse.de) Received: from Galois.suse.de (Galois.suse.de [194.112.123.130]) by mail.suse.de (Postfix) with ESMTP id AAFEF32CEB; Wed, 17 Mar 1999 22:22:16 +0100 (MET) Received: by Galois.suse.de (Postfix, from userid 0) id 6BC6A9410; Wed, 17 Mar 1999 22:22:16 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by Galois.suse.de (Postfix) with ESMTP id 6AC507416; Wed, 17 Mar 1999 22:22:16 +0100 (MET) Date: Wed, 17 Mar 1999 22:22:16 +0100 (MET) From: Stefan Reinauer To: Doug Rabson Cc: freebsd-alpha@freebsd.org Subject: Re: faked BSD disklabel to boot from SRM In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 17 Mar 1999, Doug Rabson wrote: > I thought about this too a long time ago. Unfortunately the fields in th= e > first sector which SRM uses to point at the bootstrap overlaps with the > MSDOS partition table. It just isn't possible to make a disk bootable > from both SRM and AlphaBIOS (which is why I wanted to do it). Hmm.. is there some documentation about that first sector with the pointer to bootstrap overlaps? Or is this part of the bsd disklabel structure starting with the magic number 0x82564557? I have multiple versions of this structure now but none is documented.. :) Stefan. --=20 SuSE GmbH Can you afford *NOT* Schanz=E4ckerstr. 10 to use Linux? D-90443 N=FCrnberg =09 Germany =09=09=09AlphaPowered To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 17 13:34:59 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 57DC1152AC for ; Wed, 17 Mar 1999 13:34:45 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id VAA56326; Wed, 17 Mar 1999 21:37:00 GMT (envelope-from dfr@nlsystems.com) Date: Wed, 17 Mar 1999 21:37:00 +0000 (GMT) From: Doug Rabson To: Stefan Reinauer Cc: freebsd-alpha@freebsd.org Subject: Re: faked BSD disklabel to boot from SRM In-Reply-To: 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, 17 Mar 1999, Stefan Reinauer wrote: > On Wed, 17 Mar 1999, Doug Rabson wrote: > > > I thought about this too a long time ago. Unfortunately the fields in the > > first sector which SRM uses to point at the bootstrap overlaps with the > > MSDOS partition table. It just isn't possible to make a disk bootable > > from both SRM and AlphaBIOS (which is why I wanted to do it). > > Hmm.. is there some documentation about that first sector with the pointer > to bootstrap overlaps? Or is this part of the bsd disklabel structure > starting with the magic number 0x82564557? I have multiple versions of > this structure now but none is documented.. :) The only documentation which I have to had for the disklabel structure is the code... There is documentation for the SRM bootstrap process (which includes a description of the required fields in the first disk sector) in "Alpha AXP Architecture Reference Manual 2nd Edition", Part III.3. From my copy: Reserved (VAX Compatibility) :BB Reserved (Expansion) :+136 Reserved :+472 Count (LBNs) :+480 Starting LBN :+488 Flags :+496 Checksum :+504 :+512 SRM doesn't seem to care much about the reserved fields (and the BSD disklabel lives right inside where the VAX boot block would have been I think). The main thing is that the bootstrap lives in a contiguous section of disk with the start sector given by "Starting LBN" and the size in sectors given by "Count (LBNs)". The "Flags" field must be zero and the "Checksum" field is a simple 64bit sum of the first 63 64bit words in the block. -- 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 18 2:23:56 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from octopus.originative (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (Postfix) with ESMTP id BACCC15385 for ; Thu, 18 Mar 1999 02:22:53 -0800 (PST) (envelope-from paul@originative.co.uk) Received: by octopus with Internet Mail Service (5.5.2232.9) id ; Thu, 18 Mar 1999 10:20:45 -0000 Message-ID: From: paul@originative.co.uk To: alpha@FreeBSD.org Subject: Core dumps Date: Thu, 18 Mar 1999 10:20:44 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Are core dumps working yet? Obviously mine aren't or I wouldn't be asking :-) I'm never sure when things don't work on my Multia whether it's just the Multia that they don't work on, hence the question. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 18 3: 4:16 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id F1C8C154AB for ; Thu, 18 Mar 1999 03:04:13 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA60849; Thu, 18 Mar 1999 11:06:44 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 18 Mar 1999 11:06:44 +0000 (GMT) From: Doug Rabson To: paul@originative.co.uk Cc: alpha@freebsd.org Subject: Re: Core dumps In-Reply-To: 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, 18 Mar 1999 paul@originative.co.uk wrote: > Are core dumps working yet? Obviously mine aren't or I wouldn't be asking > :-) I'm never sure when things don't work on my Multia whether it's just the > Multia that they don't work on, hence the question. > > Paul. Andrew Gallatin just committed support for crash dumps. To analyse them you will need his modified GDB which understands the dump. -- 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 18 3: 7: 7 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id D04A715385 for ; Thu, 18 Mar 1999 03:07:04 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA60853; Thu, 18 Mar 1999 11:09:31 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 18 Mar 1999 11:09:31 +0000 (GMT) From: Doug Rabson To: Thomas Valentino Crimi Cc: alpha@freebsd.org Subject: Re: New bootblocks In-Reply-To: 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 Tue, 16 Mar 1999, Doug Rabson wrote: > On Mon, 15 Mar 1999, Thomas Valentino Crimi wrote: > > > > > Speaking of which, it seems the new bootblocks are slightly larger (8k > > up from around 6k), could this be causing this problem: > > > > > disklabel -B -b /boot/boot1 da0 > > boot overlaps used partition a > > boot overlaps used partition b > > Warning, boot overlaps partition c, marked as FS_BOOT > > boot overlaps used partition d > > disklabel: cannot install boot program > > > > > > i.e. Am I going to have to wipe a partition to get the new bootblocks, as well? > > Ouch. It looks like I am going to have to spend some time hacking the > bootstrap again. This time, I will try to make it possible to fall back > to loader.old. I just committed a fix for the broken bootstrap. My stage1 bootblocks are still comfortably smaller than 7.5k. Do you have some strange build options when building sys/boot/alpha/boot1? -- 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 18 8:36:52 1999 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 4F9551544F for ; Thu, 18 Mar 1999 08:36:34 -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.1/8.9.1) with ESMTP id LAA04613; Thu, 18 Mar 1999 11:36:07 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.2/8.9.1) id LAA02727; Thu, 18 Mar 1999 11:35:45 -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, 18 Mar 1999 11:35:44 -0500 (EST) To: Doug Rabson Cc: paul@originative.co.uk, alpha@FreeBSD.ORG Subject: Re: Core dumps In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14065.11044.900392.887865@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug Rabson writes: > On Thu, 18 Mar 1999 paul@originative.co.uk wrote: > > > Are core dumps working yet? Obviously mine aren't or I wouldn't be asking > > :-) I'm never sure when things don't work on my Multia whether it's just the > > Multia that they don't work on, hence the question. > > > > Paul. > > Andrew Gallatin just committed support for crash dumps. To analyse them > you will need his modified GDB which understands the dump. You can get the gdb binary from http://www.freebsd.org/~gallatin/gdb.gz 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 18 11: 9:21 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from po8.andrew.cmu.edu (PO8.ANDREW.CMU.EDU [128.2.10.108]) by hub.freebsd.org (Postfix) with ESMTP id 1038F1527B for ; Thu, 18 Mar 1999 11:09:18 -0800 (PST) (envelope-from tcrimi+@andrew.cmu.edu) Received: (from postman@localhost) by po8.andrew.cmu.edu (8.8.5/8.8.2) id OAA04570; Thu, 18 Mar 1999 14:08:57 -0500 (EST) Received: via switchmail; Thu, 18 Mar 1999 14:08:56 -0500 (EST) Received: from unix13.andrew.cmu.edu via qmail ID ; Thu, 18 Mar 1999 14:07:24 -0500 (EST) Received: from unix13.andrew.cmu.edu via qmail ID ; Thu, 18 Mar 1999 14:07:24 -0500 (EST) Received: from mms.4.60.Jun.27.1996.03.02.53.sun4.51.EzMail.2.0.CUILIB.3.45.SNAP.NOT.LINKED.unix13.andrew.cmu.edu.sun4m.54 via MS.5.6.unix13.andrew.cmu.edu.sun4_51; Thu, 18 Mar 1999 14:07:24 -0500 (EST) Message-ID: Date: Thu, 18 Mar 1999 14:07:24 -0500 (EST) From: Thomas Valentino Crimi To: Doug Rabson Subject: Re: New bootblocks Cc: alpha@freebsd.org In-Reply-To: References: Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Excerpts from mail: 18-Mar-99 Re: New bootblocks by Doug Rabson@nlsystems.co >I just committed a fix for the broken bootstrap. My stage1 bootblocks are >still comfortably smaller than 7.5k. Do you have some strange build >options when building sys/boot/alpha/boot1? Ahh, found it, I turned -O in make.conf for something or other a while back, now my bootblocks are back to normal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 18 15:52:33 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from piglet.ucsf.edu (piglet.ucsf.EDU [128.218.67.20]) by hub.freebsd.org (Postfix) with ESMTP id 10523154F7 for ; Thu, 18 Mar 1999 15:52:31 -0800 (PST) (envelope-from steve@piglet.ucsf.edu) Received: (from steve@localhost) by piglet.ucsf.edu (980427.SGI.8.8.8/970903.SGI.AUTOCF) id PAA07379 for alpha@FreeBSD.ORG; Thu, 18 Mar 1999 15:52:08 -0800 (PST) Date: Thu, 18 Mar 1999 15:52:07 -0800 From: Steve Sizemore To: alpha@FreeBSD.ORG Subject: Java Message-ID: <19990318155207.A105455@cmpharm.ucsf.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi. I'm running 4.0-current on an AlphaPC 164LX... It seems that the existing port of jdk (1.1.7) doesn't work on the alpha. (At least for me.) The bin/alpha subdirectory isn't even created. Is this a known problem? Is it being addressed? Also, if anyone knows the status of the 1.2 port, I'd like to hear about it. Thanks. Steve -- ----------------------------------------------#-----#--#####--------------- # # # # Steve Sizemore # # # Dept. of Cellular and Molecular Pharmacology # # # Box 0450, Room HSE-1285 # # # University of California Medical Center # # # # 513 Parnassus Avenue ##### ##### ##### ####### San Francisco CA 94143-0450 # # # # # steve@cmpharm.ucsf.edu ##### ##### (415) 476-6987 FAX: (415) 476-6515 # # # # # -------------------------------------------------------------#####--#------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 18 16:14:47 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from piglet.ucsf.edu (piglet.ucsf.EDU [128.218.67.20]) by hub.freebsd.org (Postfix) with ESMTP id D9F5F1566A for ; Thu, 18 Mar 1999 16:14:42 -0800 (PST) (envelope-from steve@piglet.ucsf.edu) Received: (from steve@localhost) by piglet.ucsf.edu (980427.SGI.8.8.8/970903.SGI.AUTOCF) id QAA05336 for alpha@FreeBSD.ORG; Thu, 18 Mar 1999 16:14:23 -0800 (PST) Date: Thu, 18 Mar 1999 16:14:23 -0800 From: Steve Sizemore To: alpha@FreeBSD.ORG Subject: 21264 processor Message-ID: <19990318161423.A104994@cmpharm.ucsf.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, all. Just wondering if there is any predicted date for 21264 support in -current. My Digital Personal Workstation 500 just got upgraded to an XP1000 and it's running "Compaq Tru64 UNIX" until FreeBSD supports it. Thanks. Steve -- ----------------------------------------------#-----#--#####--------------- # # # # Steve Sizemore # # # Dept. of Cellular and Molecular Pharmacology # # # Box 0450, Room HSE-1285 # # # University of California Medical Center # # # # 513 Parnassus Avenue ##### ##### ##### ####### San Francisco CA 94143-0450 # # # # # steve@cmpharm.ucsf.edu ##### ##### (415) 476-6987 FAX: (415) 476-6515 # # # # # -------------------------------------------------------------#####--#------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 18 16:23:32 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9CAE615502 for ; Thu, 18 Mar 1999 16:23:25 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id QAA25876; Thu, 18 Mar 1999 16:22:54 -0800 Date: Thu, 18 Mar 1999 16:22:53 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Steve Sizemore Cc: alpha@FreeBSD.ORG Subject: Re: 21264 processor In-Reply-To: <19990318161423.A104994@cmpharm.ucsf.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 Well, until somebody who works on this actually gets an XP1000, it's not likely to happen. On Thu, 18 Mar 1999, Steve Sizemore wrote: > Hello, all. > > Just wondering if there is any predicted date for 21264 support in > -current. My Digital Personal Workstation 500 just got upgraded to an > XP1000 and it's running "Compaq Tru64 UNIX" until FreeBSD supports it. > > Thanks. > Steve > -- > ----------------------------------------------#-----#--#####--------------- > # # # # > Steve Sizemore # # # > Dept. of Cellular and Molecular Pharmacology # # # > Box 0450, Room HSE-1285 # # # > University of California Medical Center # # # # > 513 Parnassus Avenue ##### ##### ##### ####### > San Francisco CA 94143-0450 # # # > # # > steve@cmpharm.ucsf.edu ##### ##### > (415) 476-6987 FAX: (415) 476-6515 # # > # # # > -------------------------------------------------------------#####--#------ > > > 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 Fri Mar 19 2:45:21 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 7FF6F14CFD for ; Fri, 19 Mar 1999 02:45:11 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA63312; Fri, 19 Mar 1999 10:47:20 GMT (envelope-from dfr@nlsystems.com) Date: Fri, 19 Mar 1999 10:47:19 +0000 (GMT) From: Doug Rabson To: Steve Sizemore Cc: alpha@freebsd.org Subject: Re: Java In-Reply-To: <19990318155207.A105455@cmpharm.ucsf.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, 18 Mar 1999, Steve Sizemore wrote: > Hi. > > I'm running 4.0-current on an AlphaPC 164LX... > > It seems that the existing port of jdk (1.1.7) doesn't work on the > alpha. (At least for me.) The bin/alpha subdirectory isn't even created. > Is this a known problem? Is it being addressed? > > Also, if anyone knows the status of the 1.2 port, I'd like to hear > about it. The best place to ask is the freebsd-java list. There is no support for alpha at the moment that I know of (the 1.1.7 version has only recently been ported to ELF as far as I know). -- 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 Fri Mar 19 2:50:40 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 251D714BF4 for ; Fri, 19 Mar 1999 02:49:35 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA63327; Fri, 19 Mar 1999 10:52:13 GMT (envelope-from dfr@nlsystems.com) Date: Fri, 19 Mar 1999 10:52:13 +0000 (GMT) From: Doug Rabson To: Steve Sizemore Cc: alpha@freebsd.org Subject: Re: 21264 processor In-Reply-To: <19990318161423.A104994@cmpharm.ucsf.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, 18 Mar 1999, Steve Sizemore wrote: > Hello, all. > > Just wondering if there is any predicted date for 21264 support in > -current. My Digital Personal Workstation 500 just got upgraded to an > XP1000 and it's running "Compaq Tru64 UNIX" until FreeBSD supports it. To port FreeBSD to any machine, I need one of them here. If someone lends me a box for a while, I will port to it. If the box is given (or loaned long term) to the project then the code will be regularly tested on that platform ensuring continuing support. So.. If anyone feels like sending me a top of the line SMP alpha box with 21264 processors please get in touch. -- 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