From owner-freebsd-alpha Sun Nov 21 5:53:10 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 5341414EFC; Sun, 21 Nov 1999 05:53:03 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id OAA24866; Sun, 21 Nov 1999 14:28:53 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id NAA38134; Sun, 21 Nov 1999 13:54:05 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199911211254.NAA38134@yedi.iaf.nl> Subject: Re: strange panic on Alpha, SCSI disk *type* related In-Reply-To: <14390.62100.488036.94592@grasshopper.cs.duke.edu> from Andrew Gallatin at "Nov 20, 1999 2:21:37 pm" To: gallatin@cs.duke.edu (Andrew Gallatin) Date: Sun, 21 Nov 1999 13:54:05 +0100 (CET) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' 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 As Andrew Gallatin wrote ... > > Wilko Bulte writes: > > > > Best guess is currently that something in the isp driver changed that made > > the marriage of the IBM disk and the isp card a less than happy one. > > > <...> > > > isp0: Board Revision 1040B, resident F/W Revision 2.10.0 > > <..> > > The isp change is that due to problems with the Qlogic firmware > copyright, Matt felt he had to remove the Qlogic firmware from the > FreeBSD (and NetBSD) trees. Your card is now running with the > firmware that is loaded by the SRM console (2.10) rather than the > firmware that the isp driver was previously able to download (7.x). > This may be the cause of your problems. Argh. I followed the thread on the isp copyright stuff but never realised it might > If it is possible, try to upgrade your SRM console firmware to a more > recent version. Modern revs of the srm console tend to load 5.x of 5.57 is the current one I think. But for the EB64+ srm I am at the latest rev. :-( W/ -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 21 5:53:16 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 5FF2C1510F; Sun, 21 Nov 1999 05:53:03 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id OAA24870; Sun, 21 Nov 1999 14:28:55 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id OAA38385; Sun, 21 Nov 1999 14:18:50 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199911211318.OAA38385@yedi.iaf.nl> Subject: Re: strange panic on Alpha, SCSI disk *type* related In-Reply-To: <14390.62100.488036.94592@grasshopper.cs.duke.edu> from Andrew Gallatin at "Nov 20, 1999 2:21:37 pm" To: gallatin@cs.duke.edu (Andrew Gallatin) Date: Sun, 21 Nov 1999 14:18:50 +0100 (CET) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' 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 As Andrew Gallatin wrote ... > <...> > > > isp0: Board Revision 1040B, resident F/W Revision 2.10.0 > > <..> New evidence: It looks like the problems are Ultra SCSI related. Meaning that if I use the EEROMCFG.EXE utility*) and set everything to FAST-10 mode (as opposed to UltraSCSI) the system at least boots OK. I.e. it does not panic anymore: Mounting root from ufs:/dev/dda0 at isp0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 3.906MB/s transfers (1.953MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) a0a WARNING: preposterous clock chip time -- CHECK AND RESET THE DATE! swapon: adding /dev/da0b as swap device etc. I'm not too thrilled about the negotiated SCSI parameters, but it sure beats a panic ;-) Wilko *) run from the ARC console which was in turn booted from floppy; cute that the board does not have both ARC and SRM onboard at the same time. The ARC image can be found on the Alpha Eval Board SDK cdrom. -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 21 5:53:28 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 2E9A7157BB; Sun, 21 Nov 1999 05:53:03 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id OAA24865; Sun, 21 Nov 1999 14:28:52 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id NAA37853; Sun, 21 Nov 1999 13:28:18 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199911211228.NAA37853@yedi.iaf.nl> Subject: Re: strange panic on Alpha, SCSI disk *type* related In-Reply-To: from Matthew Jacob at "Nov 20, 1999 2:46:47 pm" To: mjacob@feral.com Date: Sun, 21 Nov 1999 13:28:18 +0100 (CET) Cc: gallatin@cs.duke.edu, freebsd-scsi@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' 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 As Matthew Jacob wrote ... > > I have an excellent case that (copyrights aside) this should be possible > > (putting the f/w in the driver): > > > > my machine is an Aspen Alpine, which has EB64+ firmware running. It runs > > the latest SRM available (which is ancient) and to add to the problem it > > has the SRM in EPROM, not in flash. > > Tsk. Right, tsk. ;-) > > > the driver supports multiple cards with multiple f/w sets, the f/w was > > > beggining to add 100KB to the driver.... completely outta hand...). > > > > Big, I agree. But I rather have a bigger kernel than a panic :-( > > We're talking 192KB big. I know... :-( > > > > recent version. Modern revs of the srm console tend to load 5.x of > > > > the qlogic firmware which might help you. I'm running with 5.54.1 on > > > > a number of machines here & have not seen problems. I think 5.57 is the current f/w for KZPBA (aka isp1040) > > Isn't it possible to flash the f/w onto the isp card itself? Or does the > > Alpha always use the f/w contained in the SRM? The same cards also run > > in a PC, so without the notion of SRM... > > It's not quite clear what the SRM does or does not do. It may or may not > download from the card. Likely not. It also probably depends on the SRM > version and the platform. Well, Tru64 5.0 tells me: Alpha 21064A Evaluation Board 274 MHz DECchip 21072 pci0 (primary bus:0) at nexus Loading SIOP: script c0000000, reg 81051000, data 410dc000 scsi0 at psiop0 slot 0 isp0 at pci0 slot 6 isp0: QLOGIC ISP1040B/V2 isp0: Firmware revision 2.10 (loaded by console) isp0: Failed to enable fast RAM timing. scsi1 at isp0 slot 0 So, in this case the SRM has loaded the f/w onto the isp card. But on the same Tru64 5.0: # strings isp.mod | grep load isp_unload DMA map_unload failed (sg_loop) DMA map unload failed isp_segment_load Bad header/payload flags set in status entry: 0x%x Fatal Error - No firmware image is present to load Error detected in isp_chip_init, firmware load failure likely RAM load failure (loaded from root filesystem) !!!!! (loaded by console) !!!!! isp_load_ram It appears the Tru64 driver can also load f/w onto the isp. > Insofar as updating the cards themselves- this is a pretty much > undocumented procedure that I would rather not become responsible for. > There are tools available from the Qlogic website which allow you to do > this (on a PC executing from DOS), but it's not really clear whether the > SRM will pull this out of the BIOS flashrom and then download it to the > SRAM on the card and set that running- I believe that SRM just downloads > the code *it* has. This is what I think happens, judging from the experiment above. > The reason the f/w will be going back in the tree is to provide a > *selection* of features such as Fabric or Target Mode support. The INSTALL > kernel should not have any of this compiled in because it makes things > probably too big to fit on floppies. Well, it's there for Alpha because > there are so few other boards supported that there is room for it. Hell, :-) I agree that this is a kind of a mess. SRM can only handle ncr and isp (for PCI machines) IIRC. > It's a hard problem to get right solution for, sorry. I'll have a little discussion with one of my colleagues to see if one can merge new isp f/w into the EB64+ SRM console binary. This guy used to write repair diagnostics etc for Alpha so he knows a lot of the console bit banging stuff. Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 21 9:53: 8 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 AED6B157D8; Sun, 21 Nov 1999 09:53:03 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id JAA01848; Sun, 21 Nov 1999 09:53:42 -0800 Date: Sun, 21 Nov 1999 09:53:42 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: Andrew Gallatin , freebsd-scsi@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG Subject: Re: strange panic on Alpha, SCSI disk *type* related In-Reply-To: <199911211318.OAA38385@yedi.iaf.nl> 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 Ah! Well, what you can also do is set the ISP_CFG_NONVRAM config option or do isp_no_nvram=1 # (1 << unit) in your loader defaults file (or at the loader prompt) and it won't 'believe' the NVRAM settings. It still might try and do Ultra though- that's a property of chip type, clock rate and (heh heh) a bit set in the Qlogic microengine's processor status register. I still would like more details (maybe in the mail to follow), but I probably can't look too closely at this until after December 1. On Sun, 21 Nov 1999, Wilko Bulte wrote: > As Andrew Gallatin wrote ... > > > <...> > > > > > isp0: Board Revision 1040B, resident F/W Revision 2.10.0 > > > > <..> > > New evidence: > > It looks like the problems are Ultra SCSI related. Meaning that if I > use the EEROMCFG.EXE utility*) and set everything to FAST-10 mode > (as opposed to UltraSCSI) the system at least boots OK. I.e. it does > not panic anymore: > > Mounting root from ufs:/dev/dda0 at isp0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 3.906MB/s transfers (1.953MHz, offset 8, 16bit), Tagged Queueing > Enabled > da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) > a0a > WARNING: preposterous clock chip time > -- CHECK AND RESET THE DATE! > swapon: adding /dev/da0b as swap device > > etc. > > I'm not too thrilled about the negotiated SCSI parameters, but it > sure beats a panic ;-) > > Wilko > > > *) run from the ARC console which was in turn booted from floppy; > cute that the board does not have both ARC and SRM onboard at the same time. > The ARC image can be found on the Alpha Eval Board SDK cdrom. > > > -- > | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - > |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org > > > 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 Sun Nov 21 10:22:31 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 49E9E14C88; Sun, 21 Nov 1999 10:22:10 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA01926; Sun, 21 Nov 1999 19:05:44 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA42068; Sun, 21 Nov 1999 19:15:45 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199911211815.TAA42068@yedi.iaf.nl> Subject: Re: strange panic on Alpha, SCSI disk *type* related In-Reply-To: <199911211228.NAA37853@yedi.iaf.nl> from Wilko Bulte at "Nov 21, 1999 1:28:18 pm" To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Sun, 21 Nov 1999 19:15:45 +0100 (CET) Cc: mjacob@feral.com, gallatin@cs.duke.edu, freebsd-scsi@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' 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 Matt, My previous email must have crossed your cvs update: I can confirm that the resurrection of the f/w into the kernel appears to solve the problems I was experiencing on my Alpha box. Thanks! Also to Qlogic for accepting a more usable copyright on the firmware. Suggestion: a couple of lines in /usr/src/UPDATING explaining the kernel options for the inclusion of the isp firmware might be practical I think. Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 21 12: 2:22 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from dingo.cdrom.com (castles519.castles.com [208.214.165.83]) by hub.freebsd.org (Postfix) with ESMTP id A86871582E; Sun, 21 Nov 1999 12:02:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA03269; Sun, 21 Nov 1999 11:52:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911211952.LAA03269@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Wilko Bulte Cc: mjacob@feral.com, gallatin@cs.duke.edu, freebsd-scsi@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG Subject: Re: strange panic on Alpha, SCSI disk *type* related In-reply-to: Your message of "Sun, 21 Nov 1999 19:15:45 +0100." <199911211815.TAA42068@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Nov 1999 11:52:26 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Suggestion: a couple of lines in /usr/src/UPDATING explaining the kernel > options for the inclusion of the isp firmware might be practical I think. Matt also proposed having the loader deal with loading the firmware; I can think of a couple of ways to do this that are consistent with the way that we plan to do module auto-loading, and which ought to work in the manual context as well. I guess I need to talk to him about this sometime when we get around to the autoloading implementation. *sigh* So much to do... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 22 14:28:42 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 8D6BF14D4C for ; Mon, 22 Nov 1999 14:28:31 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA41923 for alpha@FreeBSD.ORG; Mon, 22 Nov 1999 15:28:31 -0700 (MST) (envelope-from ken) Message-Id: <199911222228.PAA41923@panzer.kdm.org> Subject: -current build problem in gcc/cc1plus To: alpha@FreeBSD.ORG Date: Mon, 22 Nov 1999 15:28:31 -0700 (MST) From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (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 I'm trying to build -current on a 433au box with a cvsup from around 12:00 MST. The kernel, of course, is freshly built. Anyway, the build blew up here: ======================================================================== cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"alpha-unknown-freebsd\" -DHAIFA -I/usr/obj/usr/src/gnu/usr.bin/cc/cc1obj/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc1obj/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc1obj/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc1obj/../../../../contrib/gcc/config -I/usr/src/gnu/usr.bin/cc/cc1obj/../../../../contrib/gcc/objc -I/usr/obj/usr/src/tmp/usr/include -static -o cc1obj objc-parse.o objc-act.o c-aux-info.o c-common.o c-convert.o c-decl.o c-iterate.o c-lex.o c-pragma.o c-typeck.o /usr/obj/usr/src/gnu/usr.bin/cc/cc1obj/../cc_int/libcc_int.a ===> cc1plus bison --broken-undeftoken-init -d -o parse.c /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/parse.y bison: unrecognized option `--broken-undeftoken-init' Usage: bison [-dhklntvyV] [-b file-prefix] [-o outfile] [-p name-prefix] [--debug] [--defines] [--fixed-output-files] [--no-lines] [--verbose] [--version] [--help] [--yacc] [--no-parser] [--token-table] [--file-prefix=prefix] [--name-prefix=prefix] [--output=outfile] grammar-file *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. ======================================================================== Am I doing something wrong? Anyone have any clues? Thanks, Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 22 14:33:58 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 8664714C09 for ; Mon, 22 Nov 1999 14:33:52 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA53253; Mon, 22 Nov 1999 15:31:01 -0700 (MST) (envelope-from ken) Message-Id: <199911222231.PAA53253@panzer.kdm.org> Subject: Re: -current build problem in gcc/cc1plus In-Reply-To: <199911222228.PAA41923@panzer.kdm.org> from "Kenneth D. Merry" at "Nov 22, 1999 03:28:31 pm" To: ken@kdm.org (Kenneth D. Merry) Date: Mon, 22 Nov 1999 15:31:01 -0700 (MST) Cc: alpha@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (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 Kenneth D. Merry wrote... > > I'm trying to build -current on a 433au box with a cvsup from around 12:00 > MST. > > The kernel, of course, is freshly built. Anyway, the build blew up here: I forgot to add that the version of -current on the machine now (userland at least) is from August 11th. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 22 14:34:21 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 9BF8E14EC4 for ; Mon, 22 Nov 1999 14:34:15 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id RAA23722; Mon, 22 Nov 1999 17:32:53 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id RAA38762; Mon, 22 Nov 1999 17:32: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: Mon, 22 Nov 1999 17:32:37 -0500 (EST) To: "Kenneth D. Merry" Cc: alpha@FreeBSD.ORG Subject: Re: -current build problem in gcc/cc1plus In-Reply-To: <199911222228.PAA41923@panzer.kdm.org> References: <199911222228.PAA41923@panzer.kdm.org> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14393.50130.926678.672426@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenneth D. Merry writes: > > I'm trying to build -current on a 433au box with a cvsup from around 12:00 > MST. I can at least bracket this. A world cvsupp'ed during the day on Saturday builds just fine on alpha. 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 Nov 22 14:36:25 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 A23E914CC8 for ; Mon, 22 Nov 1999 14:36:19 -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 RAA23825; Mon, 22 Nov 1999 17:36:18 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id RAA38773; Mon, 22 Nov 1999 17:35:48 -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, 22 Nov 1999 17:35:47 -0500 (EST) To: "Kenneth D. Merry" Cc: alpha@FreeBSD.ORG Subject: Re: -current build problem in gcc/cc1plus In-Reply-To: <199911222231.PAA53253@panzer.kdm.org> References: <199911222228.PAA41923@panzer.kdm.org> <199911222231.PAA53253@panzer.kdm.org> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14393.50450.150825.663180@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenneth D. Merry writes: > Kenneth D. Merry wrote... > > > > I'm trying to build -current on a 433au box with a cvsup from around 12:00 > > MST. > > > > The kernel, of course, is freshly built. Anyway, the build blew up here: > > I forgot to add that the version of -current on the machine now (userland > at least) is from August 11th. The userland on this machine was from somewhere in the vicinity of September 10th. (This is from memory & could be totally wrong). Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 22 14:39: 3 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id AD96014DC3 for ; Mon, 22 Nov 1999 14:38:56 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA69052; Mon, 22 Nov 1999 15:36:41 -0700 (MST) (envelope-from ken) Message-Id: <199911222236.PAA69052@panzer.kdm.org> Subject: Re: -current build problem in gcc/cc1plus In-Reply-To: <14393.50130.926678.672426@grasshopper.cs.duke.edu> from Andrew Gallatin at "Nov 22, 1999 05:32:37 pm" To: gallatin@cs.duke.edu (Andrew Gallatin) Date: Mon, 22 Nov 1999 15:36:41 -0700 (MST) Cc: alpha@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (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 Andrew Gallatin wrote... > > Kenneth D. Merry writes: > > > > I'm trying to build -current on a 433au box with a cvsup from around 12:00 > > MST. > > I can at least bracket this. A world cvsupp'ed during the day on > Saturday builds just fine on alpha. It could be a bootstrapping issue of some sort, since I'm building on -current from August. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 22 18: 5:38 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 239A814EA0 for ; Mon, 22 Nov 1999 18:05:31 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id SAA35301; Mon, 22 Nov 1999 18:04:46 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id SAA15286; Mon, 22 Nov 1999 18:04:45 -0800 (PST) (envelope-from obrien) Date: Mon, 22 Nov 1999 18:04:45 -0800 From: "David O'Brien" To: "Kenneth D. Merry" Cc: alpha@FreeBSD.ORG Subject: Re: -current build problem in gcc/cc1plus Message-ID: <19991122180445.L80486@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <199911222228.PAA41923@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199911222228.PAA41923@panzer.kdm.org>; from ken@kdm.org on Mon, Nov 22, 1999 at 03:28:31PM -0700 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > ===> cc1plus > bison --broken-undeftoken-init -d -o parse.c /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/parse.y > bison: unrecognized option `--broken-undeftoken-init' > Usage: bison [-dhklntvyV] [-b file-prefix] [-o outfile] [-p name-prefix] > [--debug] [--defines] [--fixed-output-files] [--no-lines] > [--verbose] [--version] [--help] [--yacc] > [--no-parser] [--token-table] > [--file-prefix=prefix] [--name-prefix=prefix] > [--output=outfile] grammar-file "--broken-undeftoken-init" is a non-documented FreeBSD'ism to make Bison 1.28 bug-for-bug compatible with Bison 1.25. This was added in the the Bison 1.28 upgrade in August to allow the upgrade to happen. EGCS's cc1plus in our environment depends on the 1.25 bug. Being undocumented I did not add it to the usage(), thus it isn't shown above. Can you determine what Bison's you have installed (maybe the port?) and their versions (bison --version), and run ``strings /usr/bin/bison |grep broken''. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 22 18:12:19 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 5057114CA0 for ; Mon, 22 Nov 1999 18:12:16 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id TAA85576; Mon, 22 Nov 1999 19:12:13 -0700 (MST) (envelope-from ken) Message-Id: <199911230212.TAA85576@panzer.kdm.org> Subject: Re: -current build problem in gcc/cc1plus In-Reply-To: <19991122180445.L80486@dragon.nuxi.com> from "David O'Brien" at "Nov 22, 1999 06:04:45 pm" To: obrien@NUXI.com Date: Mon, 22 Nov 1999 19:12:13 -0700 (MST) Cc: alpha@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (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 David O'Brien wrote... > > ===> cc1plus > > bison --broken-undeftoken-init -d -o parse.c /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/parse.y > > bison: unrecognized option `--broken-undeftoken-init' > > Usage: bison [-dhklntvyV] [-b file-prefix] [-o outfile] [-p name-prefix] > > [--debug] [--defines] [--fixed-output-files] [--no-lines] > > [--verbose] [--version] [--help] [--yacc] > > [--no-parser] [--token-table] > > [--file-prefix=prefix] [--name-prefix=prefix] > > [--output=outfile] grammar-file > > > "--broken-undeftoken-init" is a non-documented FreeBSD'ism to make Bison > 1.28 bug-for-bug compatible with Bison 1.25. This was added in the the > Bison 1.28 upgrade in August to allow the upgrade to happen. EGCS's > cc1plus in our environment depends on the 1.25 bug. Being undocumented I > did not add it to the usage(), thus it isn't shown above. > > > Can you determine what Bison's you have installed (maybe the port?) and > their versions (bison --version), and run ``strings /usr/bin/bison |grep > broken''. Sure. {subway:/usr/home/ken:62:0} whence bison /usr/bin/bison {subway:/usr/home/ken:63:0} bison --version GNU Bison version 1.25 {subway:/usr/home/ken:64:0} ls -la $(whence bison) -r-xr-xr-x 1 root wheel 121408 Aug 11 09:54 /usr/bin/bison* {subway:/usr/home/ken:65:0} strings /usr/bin/bison |grep broken {subway:/usr/home/ken:66:1} My guess is that the problem is that I'm running bison 1.25, which has the bug in question, but not the undocumented option. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 22 18:29:58 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id BF02D14ED0 for ; Mon, 22 Nov 1999 18:29:56 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id SAA35426; Mon, 22 Nov 1999 18:29:55 -0800 (PST) (envelope-from obrien) Date: Mon, 22 Nov 1999 18:29:55 -0800 From: "David O'Brien" To: "Kenneth D. Merry" Cc: alpha@FreeBSD.ORG Subject: Re: -current build problem in gcc/cc1plus Message-ID: <19991122182954.K30340@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19991122180445.L80486@dragon.nuxi.com> <199911230212.TAA85576@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <199911230212.TAA85576@panzer.kdm.org> X-Operating-System: FreeBSD 3.3-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Nov 22, 1999 at 07:12:13PM -0700, Kenneth D. Merry wrote: > My guess is that the problem is that I'm running bison 1.25, which has the > bug in question, but not the undocumented option. Can you revert rev 1.92 in src/Makefile.inc1? Errr. I think we now use the installed tools rather than building them and useing the newly built ones. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 22 18:34:58 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 2AAF114F06 for ; Mon, 22 Nov 1999 18:32:49 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 839851C6D; Tue, 23 Nov 1999 10:32:22 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: "Kenneth D. Merry" Cc: obrien@NUXI.com, alpha@FreeBSD.ORG Subject: Re: -current build problem in gcc/cc1plus In-Reply-To: Message from "Kenneth D. Merry" of "Mon, 22 Nov 1999 19:12:13 MST." <199911230212.TAA85576@panzer.kdm.org> Date: Tue, 23 Nov 1999 10:32:22 +0800 From: Peter Wemm Message-Id: <19991123023222.839851C6D@overcee.netplex.com.au> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" wrote: > David O'Brien wrote... > > > ===> cc1plus > > > bison --broken-undeftoken-init -d -o parse.c /usr/src/gnu/usr.bin/cc/cc1p lus/../../../../contrib/gcc/cp/parse.y > > > bison: unrecognized option `--broken-undeftoken-init' > > > Usage: bison [-dhklntvyV] [-b file-prefix] [-o outfile] [-p name-prefix] > > > [--debug] [--defines] [--fixed-output-files] [--no-lines] > > > [--verbose] [--version] [--help] [--yacc] > > > [--no-parser] [--token-table] > > > [--file-prefix=prefix] [--name-prefix=prefix] > > > [--output=outfile] grammar-file > > > > > > "--broken-undeftoken-init" is a non-documented FreeBSD'ism to make Bison > > 1.28 bug-for-bug compatible with Bison 1.25. This was added in the the > > Bison 1.28 upgrade in August to allow the upgrade to happen. EGCS's > > cc1plus in our environment depends on the 1.25 bug. Being undocumented I > > did not add it to the usage(), thus it isn't shown above. > > > > > > Can you determine what Bison's you have installed (maybe the port?) and > > their versions (bison --version), and run ``strings /usr/bin/bison |grep > > broken''. > > Sure. > > {subway:/usr/home/ken:62:0} whence bison > /usr/bin/bison > {subway:/usr/home/ken:63:0} bison --version > GNU Bison version 1.25 > {subway:/usr/home/ken:64:0} ls -la $(whence bison) > -r-xr-xr-x 1 root wheel 121408 Aug 11 09:54 /usr/bin/bison* > {subway:/usr/home/ken:65:0} strings /usr/bin/bison |grep broken > {subway:/usr/home/ken:66:1} > > My guess is that the problem is that I'm running bison 1.25, which has the > bug in question, but not the undocumented option. Sounds right.. How about doing a cd /usr/src/gnu/usr.bin/bison; make cleandir obj depend && make all install It looks like we have a build tools dependency problem... :-/ Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 22 18:47:12 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id BE1E014E09 for ; Mon, 22 Nov 1999 18:47:09 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id SAA35507; Mon, 22 Nov 1999 18:46:47 -0800 (PST) (envelope-from obrien) Date: Mon, 22 Nov 1999 18:46:47 -0800 From: "David O'Brien" To: "Kenneth D. Merry" , alpha@FreeBSD.ORG Subject: Re: -current build problem in gcc/cc1plus Message-ID: <19991122184647.L30340@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19991123023222.839851C6D@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <19991123023222.839851C6D@overcee.netplex.com.au> X-Operating-System: FreeBSD 3.3-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Nov 23, 1999 at 10:32:22AM +0800, Peter Wemm wrote: > Sounds right.. How about doing a > cd /usr/src/gnu/usr.bin/bison; make cleandir obj depend && make all install No please don't. > It looks like we have a build tools dependency problem... :-/ Yep, and having a test case is good. :) -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 22 19: 5:41 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 7717C14E4B for ; Mon, 22 Nov 1999 19:05:38 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id UAA86305; Mon, 22 Nov 1999 20:05:36 -0700 (MST) (envelope-from ken) Message-Id: <199911230305.UAA86305@panzer.kdm.org> Subject: Re: -current build problem in gcc/cc1plus In-Reply-To: <19991122182954.K30340@relay.nuxi.com> from "David O'Brien" at "Nov 22, 1999 06:29:55 pm" To: obrien@NUXI.com Date: Mon, 22 Nov 1999 20:05:36 -0700 (MST) Cc: alpha@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (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 David O'Brien wrote... > On Mon, Nov 22, 1999 at 07:12:13PM -0700, Kenneth D. Merry wrote: > > My guess is that the problem is that I'm running bison 1.25, which has the > > bug in question, but not the undocumented option. > > Can you revert rev 1.92 in src/Makefile.inc1? Errr. I think we now use > the installed tools rather than building them and useing the newly built > ones. Okay, backed it out to 1.91. Things seem to work so far: ===> cc1plus bison --broken-undeftoken-init -d -o parse.c /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/parse.y /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/parse.y contains 30 shift/reduce conflicts and 42 reduce/reduce conflicts. grep '^#define[ ]*YYEMPTY' parse.c >>parse.h cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"alpha-unknown-freebsd\" -DHAIFA -I/usr/obj/usr/src/gnu/usr.bin/cc/cc1plus/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc1plus/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/config -I/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp -I. -I/usr/obj/usr/src/tmp/usr/include -c parse.c And it's still going. It must be using the version of bison in the tree, since the --broken-undeftoken-init switch didn't cause the build to fall over. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Nov 23 1:56:33 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 72BAA1502E for ; Tue, 23 Nov 1999 01:56:30 -0800 (PST) (envelope-from freebsd-alpha@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id KAA64303 for alpha@FreeBSD.org; Tue, 23 Nov 1999 10:37:57 +0100 (CET) (envelope-from freebsd-alpha@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for alpha@FreeBSD.org (alpha@FreeBSD.org) To: alpha@FreeBSD.org Date: Tue, 23 Nov 1999 10:37:47 +0100 From: Marcel Moolenaar Message-ID: <383A606B.E4826955@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: , <19991123023222.839851C6D@overcee.netplex.com.au> Subject: Re: -current build problem in gcc/cc1plus Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Wemm wrote: > It looks like we have a build tools dependency problem... :-/ JFYI: I'm currently working on building the tools. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Nov 23 22:24:36 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from dingo.cdrom.com (castles532.castles.com [208.214.165.96]) by hub.freebsd.org (Postfix) with ESMTP id 3E5BD15712; Tue, 23 Nov 1999 22:24:11 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id WAA01001; Tue, 23 Nov 1999 22:14:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911240614.WAA01001@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: doc@freebsd.org Cc: alpha@freebsd.org Subject: Looking for sub-webmeister for the FreeBSD/AXP pages Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Nov 1999 22:14:33 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The time has finally come for us to start putting out some alpha-specific information in earnest. In order to do this, we need to create a set of pages specific to the FreeBSD/AXP port. My page layout skills would get me shot on sight at a web-content convention, so I'm looking for an enthused sub-webmeister to do some writing and layout work. I can arrange for infodump and plenty of raw content material, but the prospective candidate will need to be able to clean it up, format it, and maintain the resulting pages in the face of new information. No specialty knowledge of the FreeBSD/AXP port or any Alpha systems is required, just the ability to write reasonable English and maintain a neat set of static pages. If you think that this is something that you'd like to take on, please let me know. Thanks! -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 24 20:11: 1 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from lh2.rdc1.sdca.home.com (ha2.rdc1.sdca.home.com [24.0.3.67]) by hub.freebsd.org (Postfix) with ESMTP id B8B9614BB7 for ; Wed, 24 Nov 1999 20:11:00 -0800 (PST) (envelope-from craig-burgess@home.com) Received: from home.com ([24.0.178.21]) by lh2.rdc1.sdca.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19991125041100.TPSI11592.lh2.rdc1.sdca.home.com@home.com> for ; Wed, 24 Nov 1999 20:11:00 -0800 Message-ID: <383CB72D.50C8D37@home.com> Date: Wed, 24 Nov 1999 20:12:29 -0800 From: Craig Burgess X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-alpha mailing list Subject: PYTHON (X11 libs) in 4.0-CURRANT (19991031) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org falls down after churning for 45 minutes with Stop in /usr/ports/x11-toolkits/tk80. *** Error code 1 Python requires tk -- which requires "shared library X11.6" An awful lot requires X11 (or shared X11 libraries) but installing X here would only be to satisfy the requirements of other applications: I don't have a supported video card and the machine is being built as a "server." Is there a way to provide Python with the X11 libraries without (unsuccessfully) installing X11? thanks, Craig Burgess To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 24 20:27: 6 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 51A2314BC8 for ; Wed, 24 Nov 1999 20:27:00 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.3/8.9.0) with ESMTP id WAA11463; Wed, 24 Nov 1999 22:16:05 -0600 (CST) Date: Wed, 24 Nov 1999 22:16:05 -0600 (CST) From: Steve Price To: Craig Burgess Cc: FreeBSD-alpha mailing list Subject: Re: PYTHON (X11 libs) in 4.0-CURRANT (19991031) In-Reply-To: <383CB72D.50C8D37@home.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 Hope about this? cd /usr/ports/lang/python /usr/bin/env WITH_TK=no make install On Wed, 24 Nov 1999, Craig Burgess wrote: # falls down after churning for 45 minutes with # # Stop in /usr/ports/x11-toolkits/tk80. # *** Error code 1 # # Python requires tk -- which requires "shared library X11.6" # # An awful lot requires X11 (or shared X11 libraries) but installing X # here would only be to satisfy the requirements of other applications: I # don't have a supported video card and the machine is being built as a # "server." # # Is there a way to provide Python with the X11 libraries without # (unsuccessfully) installing X11? # # thanks, # # Craig Burgess To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 25 6:51:54 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from york.ac.uk (pump3.york.ac.uk [144.32.128.131]) by hub.freebsd.org (Postfix) with ESMTP id 8607814E3C for ; Thu, 25 Nov 1999 06:51:36 -0800 (PST) (envelope-from abs4@york.ac.uk) Received: from davros.york.ac.uk (davros.york.ac.uk [144.32.134.16]) by york.ac.uk (8.9.3/8.9.3) with SMTP id OAA20867 for ; Thu, 25 Nov 1999 14:51:31 GMT Date: Thu, 25 Nov 1999 14:51:30 +0000 () From: abs4 Reply-To: abs4 To: freebsd-alpha@FreeBSD.ORG Subject: Booting floppy kern.flp gives errors 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 Hi, I have copied the two install floppies from the 4.0-current release but am getting errors during booting. The server sort of boots, but it looks like it is having trouble reading the floppy. The errors look like: "IDE command not successfully terminated" "IDE bad sector encountered or read unsuccessfull" Do I have a bad floppy drive, or is this release not supported on an Alpha server 800 (I read in an earlier mailing that is was). Many thank for any info, Andrew ------------ Dr Andrew Smith Computing Service, University of York, Heslington, York. YO1 5DD Telephone: 01904-433809; FAX: 01904-433740 This message has the status of a private & personal communication To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 25 9:47:30 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from hermes.mixx.net (hermes.mixx.net [194.152.58.71]) by hub.freebsd.org (Postfix) with ESMTP id C04DD14BCD for ; Thu, 25 Nov 1999 09:47:15 -0800 (PST) (envelope-from graichen@innominate.de) Received: from innominate.de (gatekeeper.innominate.de [212.5.16.129]) by hermes.mixx.net (8.9.3/8.9.3) with SMTP id SAA11070 for ; Thu, 25 Nov 1999 18:47:12 +0100 Received: (qmail 22541 invoked from network); 25 Nov 1999 17:47:09 -0000 Received: from piano.bln.innominate.de (192.168.0.213) by lingo01.bln.innominate.de with SMTP; 25 Nov 1999 17:47:09 -0000 Received: by piano.bln.innominate.de (Postfix, from userid 502) id C50C85921E; Thu, 25 Nov 1999 18:47:08 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by piano.bln.innominate.de (Postfix) with ESMTP id 537D03C77C for ; Thu, 25 Nov 1999 18:47:08 +0100 (CET) Date: Thu, 25 Nov 1999 18:47:07 +0100 (CET) From: Thomas Graichen X-Sender: graichen@piano.bln.innominate.de To: alpha@FreeBSD.org Subject: XF86_S3V on 164LX problems 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 (this is the second try - because somehow my first try did not reach the list - so please don't wonder if it appears twice) i've now finally also reached the FreeBSD/alpha land :-) i have an 164LX (533) with an S3V graphics card - installation of 3.3 went absolutely fine but after discovering some compiler optimization bugs i decided to move to -current earlier than i was planning before (i first wanted to build XFree86 on 3.3 and make it available) ... ok - also installation of the last snapshot was working fine - also XFree86 from the ports compiled fine (i only changed the optimizer flags from -O to nothing after the optimizer problems with 3.3) - even KDE built fine but now to the other part :-) ... XFree86 even runs fine - btw. on a vga-pci0: irq 3 at device 9.0 on pci0 most of the time - only if i switch from X to a console then some time later the machine crashes with: Nov 25 07:57:38 miranda /kernel: unexpected machine check: Nov 25 07:57:38 miranda /kernel: Nov 25 07:57:38 miranda /kernel: mces = 0x1 Nov 25 07:57:38 miranda /kernel: vector = 0x670 Nov 25 07:57:38 miranda /kernel: param = 0xfffffc0000006068 Nov 25 07:57:38 miranda /kernel: pc = 0x12003b508 Nov 25 07:57:38 miranda /kernel: ra = 0x12003b4cc Nov 25 07:57:38 miranda /kernel: curproc = 0xfffffe000631a120 Nov 25 07:57:38 miranda /kernel: pid = 250, comm = XF86_S3V Nov 25 07:57:38 miranda /kernel: Nov 25 07:57:38 miranda /kernel: panic: machine check Nov 25 07:57:38 miranda /kernel: Nov 25 07:57:38 miranda /kernel: syncing disks... 6 6 6 6 6 6 6 6 6 6 6 Nov 25 07:57:38 miranda /kernel: giving up on 6 buffers its absolutely reproducable - but the machine is working absolutely stable otherwise (lots of parallel compiles etc. without problems) does anyone have any idea what to do about this ? are there any other patches required for XFree86 to build fine on the alpha ? (i used the ports tree from 3.3 btw. - but i think this does not make a difference) the XFree86 sources include a file which is usually not in /usr/include/sys (but copying it from /sys/pci there makes it happy) - is there any clean way to solve this for the future ? a lot of thanks in advance t -- graichen@innominate.de innominate AG networking people fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 25 9:51:10 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from hermes.mixx.net (hermes.mixx.net [194.152.58.71]) by hub.freebsd.org (Postfix) with ESMTP id 094CB14BCD for ; Thu, 25 Nov 1999 09:50:59 -0800 (PST) (envelope-from graichen@innominate.de) Received: from innominate.de (gatekeeper.innominate.de [212.5.16.129]) by hermes.mixx.net (8.9.3/8.9.3) with SMTP id SAA11319 for ; Thu, 25 Nov 1999 18:50:52 +0100 Received: (qmail 23937 invoked from network); 25 Nov 1999 17:50:52 -0000 Received: from piano.bln.innominate.de (192.168.0.213) by lingo01.bln.innominate.de with SMTP; 25 Nov 1999 17:50:52 -0000 Received: by piano.bln.innominate.de (Postfix, from userid 502) id 6FF405921E; Thu, 25 Nov 1999 18:50:51 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by piano.bln.innominate.de (Postfix) with ESMTP id 512AC3C77F for ; Thu, 25 Nov 1999 18:50:51 +0100 (CET) Date: Thu, 25 Nov 1999 18:50:51 +0100 (CET) From: Thomas Graichen X-Sender: graichen@piano.bln.innominate.de To: alpha@FreeBSD.org Subject: FreeBSD/alpha webpages 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 in the process of rewriting all my most probably lost last messages to this list here one more: mike smith (i think) asked for someone doing some FreeBSD/alpha webpages summarizing all of the FreeBSD/alpha information - i might do this (of nobody better will be found :-) - i planed something like this anyway (now that i have an alpha here myself) - so mike - just send me the info and i will see what i can do i would for the first time keep that here on a site close to me so that i can manage it easily - i hope thats ok - as soon as it stabilizes i think we can integrate it then into the main FreeBSD pages if this is desired any interest ? t -- graichen@innominate.de innominate AG networking people fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 25 9:55: 5 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from hermes.mixx.net (hermes.mixx.net [194.152.58.71]) by hub.freebsd.org (Postfix) with ESMTP id C47B514BCD for ; Thu, 25 Nov 1999 09:54:40 -0800 (PST) (envelope-from graichen@innominate.de) Received: from innominate.de (gatekeeper.innominate.de [212.5.16.129]) by hermes.mixx.net (8.9.3/8.9.3) with SMTP id SAA11684 for ; Thu, 25 Nov 1999 18:54:38 +0100 Received: (qmail 23974 invoked from network); 25 Nov 1999 17:54:37 -0000 Received: from piano.bln.innominate.de (192.168.0.213) by lingo01.bln.innominate.de with SMTP; 25 Nov 1999 17:54:37 -0000 Received: by piano.bln.innominate.de (Postfix, from userid 502) id 05EBB5921E; Thu, 25 Nov 1999 18:54:36 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by piano.bln.innominate.de (Postfix) with ESMTP id DB08D3C77F for ; Thu, 25 Nov 1999 18:54:36 +0100 (CET) Date: Thu, 25 Nov 1999 18:54:36 +0100 (CET) From: Thomas Graichen X-Sender: graichen@piano.bln.innominate.de To: alpha@FreeBSD.org Subject: pwd_mkdb somehow broken on alpha ? 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 just noticed this one: root@miranda ~ # uname -mrs FreeBSD 4.0-19991111-CURRENT alpha root@miranda ~ # tail -n 1 /etc/master.passwd +::::::::: root@miranda ~ # pwd_mkdb -p /etc/master.passwd pwd_mkdb: no uid for user + pwd_mkdb: at line #19 pwd_mkdb: /etc/master.passwd: Inappropriate file type or format root@miranda ~ # it does not happen on FreeBSD/i386 compiled from -current sources - changing the nis line to +::*:*:::::: makes pwd_mkdb happier - but not me :-) ... is that a known problem ? do others have it too ? thanks in advance t -- graichen@innominate.de innominate AG networking people fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 25 9:57:34 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from hermes.mixx.net (hermes.mixx.net [194.152.58.71]) by hub.freebsd.org (Postfix) with ESMTP id 0221614BCD for ; Thu, 25 Nov 1999 09:57:19 -0800 (PST) (envelope-from graichen@innominate.de) Received: from innominate.de (gatekeeper.innominate.de [212.5.16.129]) by hermes.mixx.net (8.9.3/8.9.3) with SMTP id SAA11954 for ; Thu, 25 Nov 1999 18:57:17 +0100 Received: (qmail 25379 invoked from network); 25 Nov 1999 17:57:16 -0000 Received: from piano.bln.innominate.de (192.168.0.213) by lingo01.bln.innominate.de with SMTP; 25 Nov 1999 17:57:16 -0000 Received: by piano.bln.innominate.de (Postfix, from userid 502) id 6D9EE5921E; Thu, 25 Nov 1999 18:57:16 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by piano.bln.innominate.de (Postfix) with ESMTP id 4ECE93C77F for ; Thu, 25 Nov 1999 18:57:16 +0100 (CET) Date: Thu, 25 Nov 1999 18:57:16 +0100 (CET) From: Thomas Graichen X-Sender: graichen@piano.bln.innominate.de To: alpha@FreeBSD.org Subject: NFS_UIDHASHSIZ 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 and even one rewritten mail more :-) what exactly does this mean ? struct nfssvc_sock bloated (> 256bytes) Try reducing NFS_UIDHASHSIZ struct nfsuid bloated (> 128bytes) Try unionizing the nu_nickname and nu_flag fields from the archives i found that it seems to be harmless and typically related to the alpha - but if it is so - can it be fixed in a way that the values are also correctly checked on the alpha (i assume its a type lenght problem - but maybe not) ? thanks in advance t -- graichen@innominate.de innominate AG networking people fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 25 9:59: 7 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from hermes.mixx.net (hermes.mixx.net [194.152.58.71]) by hub.freebsd.org (Postfix) with ESMTP id 4880414DA4 for ; Thu, 25 Nov 1999 09:59:00 -0800 (PST) (envelope-from graichen@innominate.de) Received: from innominate.de (gatekeeper.innominate.de [212.5.16.129]) by hermes.mixx.net (8.9.3/8.9.3) with SMTP id SAA12072 for ; Thu, 25 Nov 1999 18:58:58 +0100 Received: (qmail 25395 invoked from network); 25 Nov 1999 17:58:57 -0000 Received: from piano.bln.innominate.de (192.168.0.213) by lingo01.bln.innominate.de with SMTP; 25 Nov 1999 17:58:57 -0000 Received: by piano.bln.innominate.de (Postfix, from userid 502) id 9B5165921E; Thu, 25 Nov 1999 18:58:57 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by piano.bln.innominate.de (Postfix) with ESMTP id 6F57C3C77C for ; Thu, 25 Nov 1999 18:58:57 +0100 (CET) Date: Thu, 25 Nov 1999 18:58:57 +0100 (CET) From: Thomas Graichen X-Sender: graichen@piano.bln.innominate.de To: alpha@FreeBSD.org Subject: de0: abnormal interrupt: transmit underflow 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 anyone an idea what exactly this means ? de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256) de0: abnormal interrupt: transmit underflow (raising TX threshold to 128|512) de0: abnormal interrupt: transmit underflow (raising TX threshold to 160|1024) ... but i think this has more to do with the networking here than with FreeBSD/alpha - but maybe its also related to the de driver for the alpha - any ideas ? thanks again in advance t -- graichen@innominate.de innominate AG networking people fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 25 10:17:56 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from bud.itixs.com (bud.itixs.com [216.186.144.67]) by hub.freebsd.org (Postfix) with SMTP id 7FF6714E0A for ; Thu, 25 Nov 1999 10:17:38 -0800 (PST) (envelope-from bifrost@itixs.com) Received: (qmail 60367 invoked from network); 25 Nov 1999 18:18:56 -0000 Received: from fortress.itixs.com (@10.1.1.5) by bud.itixs.com with SMTP; 25 Nov 1999 18:18:56 -0000 Date: Thu, 25 Nov 1999 10:19:12 -0800 (PST) From: Tom Sparks To: Thomas Graichen Cc: alpha@FreeBSD.ORG Subject: Re: de0: abnormal interrupt: transmit underflow 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 > anyone an idea what exactly this means ? > > de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256) > de0: abnormal interrupt: transmit underflow (raising TX threshold to 128|512) > de0: abnormal interrupt: transmit underflow (raising TX threshold to 160|1024) > > ... but i think this has more to do with the networking here > than with FreeBSD/alpha - but maybe its also related to the > de driver for the alpha - any ideas ? I've got deX cards in my PC boxes that do the same thing. It usually happens under heavy io, and I'm guessing its just allocating more memory buffers or something to the card and being noisy about it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 25 11: 2:16 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id DC0F614BCD for ; Thu, 25 Nov 1999 11:02:14 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id LAA70150; Thu, 25 Nov 1999 11:02:13 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA06091; Thu, 25 Nov 1999 11:02:13 -0800 (PST) (envelope-from obrien) Date: Thu, 25 Nov 1999 11:02:13 -0800 From: "David O'Brien" To: Thomas Graichen Cc: alpha@FreeBSD.org Subject: Re: de0: abnormal interrupt: transmit underflow Message-ID: <19991125110213.Q49362@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from graichen@innominate.de on Thu, Nov 25, 1999 at 06:58:57PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > anyone an idea what exactly this means ? > > de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256) > de0: abnormal interrupt: transmit underflow (raising TX threshold to 128|512) > de0: abnormal interrupt: transmit underflow (raising TX threshold to 160|1024) The `de' driver is very chatty. This is normal operation and many of the other Ethernet drivers do this, but don't tell you about it. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 25 11:37:57 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 6CA8B14DEF; Thu, 25 Nov 1999 11:37:52 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA32174; Thu, 25 Nov 1999 20:25:40 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA01014; Thu, 25 Nov 1999 20:00:46 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199911251900.UAA01014@yedi.iaf.nl> Subject: Re: strange panic on Alpha, SCSI disk *type* related In-Reply-To: from Matthew Jacob at "Nov 21, 1999 9:53:42 am" To: mjacob@feral.com Date: Thu, 25 Nov 1999 20:00:46 +0100 (CET) Cc: gallatin@cs.duke.edu, freebsd-scsi@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' 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 As Matthew Jacob wrote ... Hi Matt, Ever since the firmware is back in the driver the machine just works like a charm. Are you still interested in digging into my ancient isp f/w ;-) ? I'm happy with things the way they are. Wilko > Ah! Well, what you can also do is set the ISP_CFG_NONVRAM config option > or do > > isp_no_nvram=1 # (1 << unit) > > in your loader defaults file (or at the loader prompt) and it won't > 'believe' the NVRAM settings. It still might try and do Ultra though- > that's a property of chip type, clock rate and (heh heh) a bit set in the > Qlogic microengine's processor status register. > > I still would like more details (maybe in the mail to follow), but I > probably can't look too closely at this until after December 1. -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 25 12:10:41 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id E31AC14DF2 for ; Thu, 25 Nov 1999 12:10:37 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40323>; Fri, 26 Nov 1999 07:03:33 +1100 Content-return: prohibited Date: Fri, 26 Nov 1999 07:10:31 +1100 From: Peter Jeremy Subject: Re: de0: abnormal interrupt: transmit underflow In-reply-to: To: Thomas Graichen Cc: alpha@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Nov26.070333est.40323@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1999-Nov-26 04:58:57 +1100, Thomas Graichen wrote: >anyone an idea what exactly this means ? > >de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256) >de0: abnormal interrupt: transmit underflow (raising TX threshold to 128|512) >de0: abnormal interrupt: transmit underflow (raising TX threshold to 160|1024) > >... but i think this has more to do with the networking here >than with FreeBSD/alpha - but maybe its also related to the >de driver for the alpha - any ideas ? The Tulip driver in Digital UNIX does the same as well. I thought I'd seen an explanation for it somewhere, but can't find it right now. (I think it's related to the DMA buffer thresholds). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Nov 26 5:15:32 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id AF15714F9F for ; Fri, 26 Nov 1999 05:15:16 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id C2EB21C6D; Fri, 26 Nov 1999 21:15:15 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: peter.jeremy@alcatel.com.au Cc: Thomas Graichen , alpha@FreeBSD.ORG Subject: Re: de0: abnormal interrupt: transmit underflow In-Reply-To: Message from Peter Jeremy of "Fri, 26 Nov 1999 07:10:31 +1100." <99Nov26.070333est.40323@border.alcanet.com.au> Date: Fri, 26 Nov 1999 21:15:15 +0800 From: Peter Wemm Message-Id: <19991126131515.C2EB21C6D@overcee.netplex.com.au> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Jeremy wrote: > On 1999-Nov-26 04:58:57 +1100, Thomas Graichen wrote: > >anyone an idea what exactly this means ? > > > >de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256) > >de0: abnormal interrupt: transmit underflow (raising TX threshold to 128|512 ) > >de0: abnormal interrupt: transmit underflow (raising TX threshold to 160|102 4) > > > >... but i think this has more to do with the networking here > >than with FreeBSD/alpha - but maybe its also related to the > >de driver for the alpha - any ideas ? > > The Tulip driver in Digital UNIX does the same as well. I thought I'd > seen an explanation for it somewhere, but can't find it right now. (I > think it's related to the DMA buffer thresholds). OK, the Tulip series chips have a recieve and transmit FIFO that has the busmaster DMA interface on one side and the ethernet engine on the other. Recieving is not so much of a problem as the fifo is big enough to hold at least an entire frame, and it's emptied to main memory as soon as practical. Transmission however is another problem. The busmaster engine starts filling the fifo as soon as it's given the go-ahead. As soon as it reaches the threshhold, the ethernet engine begins transmission on the wire. Obviously you want to do this as quickly as possible to get the latency down. But.. if the busmaster engine can't (for some reason) get data from memory quick enough, and the fifo runs out of data while the ethernet engine is transmitting, that is a problem as the packet is already partly on the wire and suddenly is stopped mid flight leading to a corrupt packet. A recieve overflow wouldn't be so bad as it doesn't cause debris on the wire. A transmitter underflow does cause corrupt packets though. Here's where it gets interesting.. The tulip series (and a few others, but not all of the 100mbit cards) suffer from underflows. Main memory should be plenty fast enough to keep up, as it's a good 500+mbyte/sec, and we only need in the order of 12kbyte/sec to keep the transmitter busy. The PCI busmaster latency timers and so on could cause starvation but I've seen this problem on machines with one sole PCI busmaster active and no (obvious) PCI configuration problems. It's as though the chips have a bug and "forget" about keeping the fifo full. I half thought I saw Bill Paul say he was suspicious that it's something to do with the descriptor layout and that keeping the transmitter running from a contiguous mbuf cluster rather than collecting the frame from multiple mbuf fragments might be the solution. I don't know if my interpretation was right or if I was imagining it, or if it's been found not to be the case. BTW, 'switching to store and forward mode' which is the last step of the underflow correction means that it dma's the entire frame into the fifo before going near the wire. It's kinda suspicious when it's set to "1024" byte though... it fills the fifo to 1024 bytes (out of 1500) and starts transmission. Even given this much of a head-start, it's still not been able to keep up... Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Nov 26 12:13:10 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id D1444151AB for ; Fri, 26 Nov 1999 12:13:08 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id LAA45864 for ; Fri, 26 Nov 1999 11:57:00 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA83669 for alpha@freebsd.org; Fri, 26 Nov 1999 11:57:00 -0800 (PST) (envelope-from obrien) Date: Fri, 26 Nov 1999 11:56:59 -0800 From: "David O'Brien" To: alpha@freebsd.org Subject: Fscking disklabel crap Message-ID: <19991126115659.A83643@dragon.nuxi.com> Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok, what I need to do on an Alpha to `dd' one disk to another? (yes they are identical drives) # dd if=/dev/rda0c of=/dev/rda2c dd: /dev/rda2c: Read-only file system 1+0 records in 0+0 records out 0 bytes transferred in 0.005558 secs (0 bytes/sec) Fine, maybe I just need to find the device name it likes... # dd if=/dev/rda0 of=/dev/rda2 dd: /dev/rda2c: Read-only file system 1+0 records in 0+0 records out 0 bytes transferred in 0.007808 secs (0 bytes/sec) Lets read disklabel(8). Hum.. -W, lets try that and then `dd'. Nope brain-damage still exists. This kind of crap does *not* happen on a Sun. Uggg... And I'd really rather not have to open the box up to get da0 out to do this under Solaris. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Nov 26 12:37:19 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 07C8315368 for ; Fri, 26 Nov 1999 12:37:12 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id VAA01944 for freebsd-alpha@freebsd.org; Fri, 26 Nov 1999 21:26:37 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id VAA08257 for freebsd-alpha@freebsd.org; Fri, 26 Nov 1999 21:37:01 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199911262037.VAA08257@yedi.iaf.nl> Subject: Miata support To: freebsd-alpha@freebsd.org (FreeBSD-alpha mailing list) Date: Fri, 26 Nov 1999 21:37:01 +0100 (CET) X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' 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 I'm looking for opinions on the Miata machines. PWS433a to be exact. Any good/bad experiences to report? TIA, Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Nov 26 12:57: 4 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 2B4CD15234 for ; Fri, 26 Nov 1999 12:55: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 PAA14026; Fri, 26 Nov 1999 15:55:45 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id PAA46628; Fri, 26 Nov 1999 15:55:15 -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: Fri, 26 Nov 1999 15:55:14 -0500 (EST) To: Wilko Bulte Cc: freebsd-alpha@FreeBSD.ORG (FreeBSD-alpha mailing list) Subject: Re: Miata support In-Reply-To: <199911262037.VAA08257@yedi.iaf.nl> References: <199911262037.VAA08257@yedi.iaf.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14398.61799.797803.755607@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte writes: > I'm looking for opinions on the Miata machines. PWS433a to be exact. > Any good/bad experiences to report? > > TIA, > Wilko Yes. Both good and bad. There are at least 2 revs of Miatas, but there is no labeling difference for you to be able to tell them apart. The fact that they have identical model numbers is due to Microsoft -- they would have had to re-certify the the platform for NT with Microsoft if they had changed the model number. The earlier miatas have a horribly buggy pci chipset which cannot do DMA Reads across page boundaries and which is prone to lockup under heavy PCI I/O. They do not allow 'unknown' PCI cards into the 64-bit PCI slot (you can override this, but it is a pain). They are very picky about what graphics cards they will accept. However, if you have a graphics card which works in the machine & are not planning on running anything very I/O intesive (gig ether, myrinet, multiple U/W SCSI channels, etc), then you'll probably be OK. These earlier miatas are characterized by having the Qlogic SCSI adaptor as an actual PCI card. They have an Intel PCI/ISA bridge & a CMD IDE adapter. They do not have USB ports. The later models have a much improved rev of the chipset & most PCI problems are gone. They have onboard Qlogic SCSI, a Cypress PCI/ISA bridge, a Cypress IDE controller, and have USB support. The only disadvantage to these machines is that we don't support the Cypress IDE chipset very well. I have failed (but not tried very hard) to make it do busmaster DMA using the ATA drivers. Cheers, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Nov 26 14:37:22 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 0B678151C8 for ; Fri, 26 Nov 1999 14:37:19 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA07051; Fri, 26 Nov 1999 23:22:42 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA09138; Fri, 26 Nov 1999 22:44:12 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199911262144.WAA09138@yedi.iaf.nl> Subject: Re: Miata support In-Reply-To: <14398.61799.797803.755607@grasshopper.cs.duke.edu> from Andrew Gallatin at "Nov 26, 1999 3:55:14 pm" To: gallatin@cs.duke.edu (Andrew Gallatin) Date: Fri, 26 Nov 1999 22:44:12 +0100 (CET) Cc: freebsd-alpha@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' 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 As Andrew Gallatin wrote ... > Wilko Bulte writes: > > I'm looking for opinions on the Miata machines. PWS433a to be exact. > > Any good/bad experiences to report? > > > > TIA, > > Wilko > > Yes. Both good and bad. > > There are at least 2 revs of Miatas, but there is no labeling > difference for you to be able to tell them apart. The fact that they > have identical model numbers is due to Microsoft -- they would have > had to re-certify the the platform for NT with Microsoft if they had > changed the model number. Well... the newer ones should have a trailing -Px (x is a number) and the early ones a trailing -Rx on their part# sticker (should be on the cabinet somewhere). At least that is what I once found somewhere on the WWW (I think). Maybe you can check if that matches with your machine? > The earlier miatas have a horribly buggy pci chipset which cannot do Is that an early Pyxis chipset? > DMA Reads across page boundaries and which is prone to lockup under heavy > PCI I/O. They do not allow 'unknown' PCI cards into the 64-bit PCI > slot (you can override this, but it is a pain). They are very picky > about what graphics cards they will accept. However, if you have a > graphics card which works in the machine & are not planning on running > anything very I/O intesive (gig ether, myrinet, multiple U/W SCSI > channels, etc), then you'll probably be OK. Hmm. > These earlier miatas are characterized by having the Qlogic SCSI > adaptor as an actual PCI card. They have an Intel PCI/ISA bridge & a > CMD IDE adapter. They do not have USB ports. Hmm (again). > The later models have a much improved rev of the chipset & most PCI > problems are gone. They have onboard Qlogic SCSI, a Cypress PCI/ISA > bridge, a Cypress IDE controller, and have USB support. The only > disadvantage to these machines is that we don't support the Cypress > IDE chipset very well. I have failed (but not tried very hard) to > make it do busmaster DMA using the ATA drivers. I'm a SCSI addict so I don't care too much about IDE. Thanks, -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Nov 26 14:53: 5 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 7F3C91529E for ; Fri, 26 Nov 1999 14:53:03 -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 RAA15379; Fri, 26 Nov 1999 17:53:02 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id RAA46835; Fri, 26 Nov 1999 17:52:31 -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: Fri, 26 Nov 1999 17:52:31 -0500 (EST) To: Wilko Bulte Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Miata support In-Reply-To: <199911262144.WAA09138@yedi.iaf.nl> References: <14398.61799.797803.755607@grasshopper.cs.duke.edu> <199911262144.WAA09138@yedi.iaf.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14399.3430.157707.36604@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte writes: > As Andrew Gallatin wrote ... <...> > Well... the newer ones should have a trailing -Px (x is a number) and > the early ones a trailing -Rx on their part# sticker (should be on the > cabinet somewhere). At least that is what I once found somewhere on > the WWW (I think). > > Maybe you can check if that matches with your machine? Yes, it does! You learn something new every day ;-) However -- We pressured Digital into giving us motherboard upgrades for our old buggy machines (we had a performance clause in our purchase order). We actually received a rather polished "upgrade kit" complete with documentation on how to do the board swap, so I have a feeling that a fairly substantial number of machines were upgraded. If this is the case, a machine may have a "bad" part number, but may really have newer guts. > > The earlier miatas have a horribly buggy pci chipset which cannot do > > Is that an early Pyxis chipset? Yes. 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 Fri Nov 26 16: 7:23 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 9635315207 for ; Fri, 26 Nov 1999 16:07:20 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA10720; Sat, 27 Nov 1999 00:54:25 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id BAA50907; Sat, 27 Nov 1999 01:04:18 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199911270004.BAA50907@yedi.iaf.nl> Subject: Re: Miata support In-Reply-To: <14399.3430.157707.36604@grasshopper.cs.duke.edu> from Andrew Gallatin at "Nov 26, 1999 5:52:31 pm" To: gallatin@cs.duke.edu (Andrew Gallatin) Date: Sat, 27 Nov 1999 01:04:18 +0100 (CET) Cc: freebsd-alpha@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' 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 As Andrew Gallatin wrote ... > However -- We pressured Digital into giving us motherboard upgrades > for our old buggy machines (we had a performance clause in our > purchase order). We actually received a rather polished "upgrade kit" > complete with documentation on how to do the board swap, so I have a > feeling that a fairly substantial number of machines were upgraded. > If this is the case, a machine may have a "bad" part number, but may > really have newer guts. BTW: what would be the going price for a 64Mb PWS433 incl 4.5G USCSI? Guestimate is just fine. -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Nov 26 16: 7:27 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 8204D1523E for ; Fri, 26 Nov 1999 16:07:20 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA10719; Sat, 27 Nov 1999 00:54:24 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id BAA50893; Sat, 27 Nov 1999 01:02:51 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199911270002.BAA50893@yedi.iaf.nl> Subject: Re: Miata support In-Reply-To: <14399.3430.157707.36604@grasshopper.cs.duke.edu> from Andrew Gallatin at "Nov 26, 1999 5:52:31 pm" To: gallatin@cs.duke.edu (Andrew Gallatin) Date: Sat, 27 Nov 1999 01:02:51 +0100 (CET) Cc: freebsd-alpha@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' 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 As Andrew Gallatin wrote ... > > Wilko Bulte writes: > > As Andrew Gallatin wrote ... > > <...> > > Well... the newer ones should have a trailing -Px (x is a number) and > > the early ones a trailing -Rx on their part# sticker (should be on the > > cabinet somewhere). At least that is what I once found somewhere on > > the WWW (I think). > > > > Maybe you can check if that matches with your machine? > > Yes, it does! You learn something new every day ;-) Cool.. Don't remember were I found the info though. Anyway, it might help. > However -- We pressured Digital into giving us motherboard upgrades > for our old buggy machines (we had a performance clause in our > purchase order). We actually received a rather polished "upgrade kit" > complete with documentation on how to do the board swap, so I have a > feeling that a fairly substantial number of machines were upgraded. > If this is the case, a machine may have a "bad" part number, but may > really have newer guts. Hmmm. Have not heared that story before. Like you said "something new every day ;-) -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Nov 26 17:35:55 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 F3ED514C24 for ; Fri, 26 Nov 1999 17:35:51 -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 UAA16871; Fri, 26 Nov 1999 20:35:50 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id UAA47110; Fri, 26 Nov 1999 20:35:20 -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: Fri, 26 Nov 1999 20:35:19 -0500 (EST) To: Wilko Bulte Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Miata support In-Reply-To: <199911270004.BAA50907@yedi.iaf.nl> References: <14399.3430.157707.36604@grasshopper.cs.duke.edu> <199911270004.BAA50907@yedi.iaf.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14399.13210.950566.851116@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte writes: > As Andrew Gallatin wrote ... > > > However -- We pressured Digital into giving us motherboard upgrades > > for our old buggy machines (we had a performance clause in our > > purchase order). We actually received a rather polished "upgrade kit" > > complete with documentation on how to do the board swap, so I have a > > feeling that a fairly substantial number of machines were upgraded. > > If this is the case, a machine may have a "bad" part number, but may > > really have newer guts. > > BTW: what would be the going price for a 64Mb PWS433 incl 4.5G USCSI? > Guestimate is just fine. I'm not sure. I've seen them going for somewhere in the neighborhood of $1,000 - $1500 (USD). If the machine has a UNIX (or VMS, I suppose..) license, then expect to pay more. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Nov 27 4: 1:47 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from grootstal.nijmegen.inter.nl.net (grootstal.nijmegen.inter.nl.net [193.67.237.11]) by hub.freebsd.org (Postfix) with ESMTP id F1EA514C9B for ; Sat, 27 Nov 1999 04:01:44 -0800 (PST) (envelope-from Peter.Blok@inter.NL.net) Received: from ntpc by grootstal.nijmegen.inter.nl.net via ztm51-78.Zoetermeer.NL.net [195.108.245.243] with SMTP for id NAA01603 (8.8.8/1.19); Sat, 27 Nov 1999 13:01:43 +0100 (MET) Reply-To: From: "Peter Blok" To: Subject: AXPCI33 & IDE Date: Sat, 27 Nov 1999 13:02:56 +0100 Message-ID: <000301bf38cf$581f5f60$8aac9f0a@homebrew> 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 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I bought an AXPPCI33 board and i'm running freebsd on it now. However i can't find information how to configure ISA boards. I know isacfg exists, but how am i able to use plug-and-prey boards with it? I don't know the resources used? Do i have to configure it fixed in an i386 pc and then isacfg it in the alpha? Also, how can i use the on-board IDE? It doesn't seem to recognize it? TIA, Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message