From owner-freebsd-alpha Sun Jun 20 2:22:30 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 063B914D7F
for <freebsd-alpha@freebsd.org>; Sun, 20 Jun 1999 02:22:23 -0700 (PDT)
(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 426DB75
for <freebsd-alpha@freebsd.org>; Sun, 20 Jun 1999 17:22:22 +0800 (WST)
(envelope-from peter@netplex.com.au)
X-Mailer: exmh version 2.0.2 2/24/98
To: freebsd-alpha@freebsd.org
Subject: Re: OK, any pointers on how to use SRM? :-)
In-reply-to: Your message of "19 Jun 1999 16:10:06 +0200."
<7kg8bu$dmn$1@mips.rhein-neckar.de>
Date: Sun, 20 Jun 1999 17:22:22 +0800
From: Peter Wemm <peter@netplex.com.au>
Message-Id: <19990620092222.426DB75@overcee.netplex.com.au>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Christian Weisgerber wrote:
> Peter Wemm <peter@netplex.com.au> wrote:
>
> > How the hell do you use srm? :-)
>
> http://ftp.digital.com/pub/Digital/info/semiconductor/literature/srmcons.pdf
Thanks, I think this is what Doug mailed to me.
However, I have another problem that I could do with some advice on.
Basically at the moment I'm short of an ATX power supply and case (damn
weekends). So, itching to get going, I took my workstation apart and
mounted the AlphaPC 164SX motherboard. However, the power supply promptly
expired. (!)
Apon investigation, with the old motherboard back in, the +3.3V power lines
from the power supply was supplying 1.9V instead and the hardware monitoring
was having a fit and making ambulance siren sounds from the speaker. (!!).
After checking the 164SX motherboard again, I find the +3V-to-gnd
resistance is very close to 0.0 ohms, sometimes it sits at 0.2 ohms for a
few seconds after first attaching the DMM leads.
Taking out the CPU brings the +3.3V-to-gnd resistance to over 1K ohms, which
is in line with the other supply pins on the motherboard.
Now, is this normal? Did the power supply just expire when getting a heavy
3.3V load at startup? Or is it more likely that the CPU has expired and
killed the power supply? (The ratings look OK, the 164SX manual says it's
supposed to only draw 5 amps from the 3.3V line, while the power supply was
rated at 14 amps). This motherboard was running a few days ago (at Usenix)
and the cpu has not been removed from it's socket for the duration. There
is no sign of over-current or heat damage under the PCB or on the CPU pins.
Needless to say, I'm not keen to experiment just yet to find out, I've
borrowed the power supply from my wife's computer, if I kill that too I will
be in big trouble. :-)
(PS: Doug and Drew: the DIP switches were set for neither 400 or 533 clocking
at Usenix)
Cheers,
-Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Sun Jun 20 8:23:35 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 70A6C14E03
for <alpha@FreeBSD.ORG>; Sun, 20 Jun 1999 08:23:31 -0700 (PDT)
(envelope-from walter@fortean.com)
Received: from localhost (walter@localhost)
by callisto.fortean.com (8.9.3/8.9.3) with SMTP id LAA03745;
Sun, 20 Jun 1999 11:23:23 -0400 (EDT)
(envelope-from walter@fortean.com)
X-Authentication-Warning: callisto.fortean.com: walter owned process doing -bs
Date: Sun, 20 Jun 1999 11:23:23 -0400 (EDT)
From: Bruce Walter <walter@fortean.com>
To: John Birrell <jb@cimlogic.com.au>
Cc: alpha@FreeBSD.ORG
Subject: PALcode (was: Anyone up for an exorcism?)
In-Reply-To: <199906200656.QAA05392@cimlogic.com.au>
Message-ID: <Pine.BSF.3.96.990620111856.3730A-100000@callisto.fortean.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
> Obtaining up-to-date-for-each-system sources for the palcode is
> problematic. It would be nice if Compaq would just release the sources
> and let us maintain them after they make boards/systems obsolete.
Has anyone spoken to them about this? With rumours that Compaq may ditch
the whole alpha lot (to Samsung maybe?), I wonder if it may become possible.
MILO sources are distributed with older PALcode sources, and given their
close ties to Linux...
- 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 Sun Jun 20 14:59:59 1999
Delivered-To: freebsd-alpha@freebsd.org
Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31])
by hub.freebsd.org (Postfix) with ESMTP id C4A8114CA3
for <alpha@FreeBSD.ORG>; Sun, 20 Jun 1999 14:59:49 -0700 (PDT)
(envelope-from jb@cimlogic.com.au)
Received: (from jb@localhost)
by cimlogic.com.au (8.9.1/8.9.1) id IAA06848;
Mon, 21 Jun 1999 08:25:04 +1000 (EST)
(envelope-from jb)
From: John Birrell <jb@cimlogic.com.au>
Message-Id: <199906202225.IAA06848@cimlogic.com.au>
Subject: Re: PALcode (was: Anyone up for an exorcism?)
In-Reply-To: <Pine.BSF.3.96.990620111856.3730A-100000@callisto.fortean.com> from Bruce Walter at "Jun 20, 1999 11:23:23 am"
To: walter@fortean.com (Bruce Walter)
Date: Mon, 21 Jun 1999 08:25:04 +1000 (EST)
Cc: jb@cimlogic.com.au, alpha@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
Bruce Walter wrote:
> > Obtaining up-to-date-for-each-system sources for the palcode is
> > problematic. It would be nice if Compaq would just release the sources
> > and let us maintain them after they make boards/systems obsolete.
>
> Has anyone spoken to them about this? With rumours that Compaq may ditch
> the whole alpha lot (to Samsung maybe?), I wonder if it may become possible.
> MILO sources are distributed with older PALcode sources, and given their
> close ties to Linux...
If anyone can persuade the right person in Compaq, we'd all be grateful.
--
John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Mon Jun 21 1: 6:22 1999
Delivered-To: freebsd-alpha@freebsd.org
Received: from post.bgnett.no (post.bgnett.no [194.54.96.133])
by hub.freebsd.org (Postfix) with ESMTP id 84A2F14F3A
for <alpha@FreeBSD.ORG>; Mon, 21 Jun 1999 01:06:10 -0700 (PDT)
(envelope-from erik@habatech.no)
Received: from erik (4pogc-gw.online.no [194.248.199.142])
by post.bgnett.no (8.8.8/8.8.8) with SMTP id KAA11044;
Mon, 21 Jun 1999 10:05:11 +0200 (CEST)
(envelope-from erik@habatech.no)
Message-ID: <00e601bebbbd$109a18e0$6c01a8c0@erik.reinelinjer.no>
From: "Erik H. Bakke" <erik@habatech.no>
To: "John Birrell" <jb@cimlogic.com.au>,
"Peter Wemm" <peter@netplex.com.au>
Cc: <alpha@FreeBSD.ORG>
Subject: SV: OK, any pointers on how to use SRM? :-)
Date: Mon, 21 Jun 1999 10:07:00 +0200
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
>Peter Wemm wrote:
>Normally the SRM documentation is in the hardware reference manual for
>the board/system you are using. I guess you don't have that?!
>
It's probably not in there if the board was delivered with AlphaBIOS
and flashed to SRM :)
I believe most of the 164SX boards came preconfigured to run
Windows NT.
Digital also have som excellent manuals on their FTP site. The URL has =
already been mentioned, so I will skip it.
Regards.
---
Erik H. Bakke
Habatech AS
erik@habatech.no
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Mon Jun 21 1:10:12 1999
Delivered-To: freebsd-alpha@freebsd.org
Received: from mail.toplink.net (mail.toplink.net [195.2.171.8])
by hub.freebsd.org (Postfix) with ESMTP id A0EA514DAA
for <freebsd-alpha@FreeBSD.ORG>; Mon, 21 Jun 1999 01:10:02 -0700 (PDT)
(envelope-from ks@hirvi.net)
Received: (from uucp@localhost)
by mail.toplink.net (8.9.3/8.9.3) with UUCP id KAA24717
for freebsd-alpha@FreeBSD.ORG; Mon, 21 Jun 1999 10:10:01 +0200 (CEST)
Received: from hirvi.net (poro.hirvi.net [195.2.174.103])
by karhu.hirvi.net (8.8.7/8.8.8) with SMTP id IAA07981
for <freebsd-alpha@FreeBSD.ORG>; Mon, 21 Jun 1999 08:54:18 +0200
Message-Id: <199906210654.IAA07981@karhu.hirvi.net>
Date: Mon, 21 Jun 1999 09:58:59 +0200
From: Kai Schmidt <ks@hirvi.net>
Reply-To: Kai Schmidt <ks@hirvi.net>
To: freebsd-alpha@FreeBSD.ORG
Subject: Multia heat death
X-Mailer: Kai Schmidt's registered AK-Mail 3.1pb1 [ger]
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
Hello,
one of my multia died, the famous heat death, now I am facing another
pronlem, I can't get hold of the new chip. I tried varios sources in the UK,
the Netherlands and Germany without any success, I would like to have two of
these chips, is there any reseller somewhere, accepting credit cards and
ships to germany?
--
Bye!
- Kai Schmidt -
"That's why we are on this ship to begin with! It becomes our problem
when the machines can't handle it!" Capt. Dallas, USCSS Nostromo
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Mon Jun 21 8:12:59 1999
Delivered-To: freebsd-alpha@freebsd.org
Received: from tad.cetlink.net (tad.cetlink.net [209.198.2.10])
by hub.freebsd.org (Postfix) with ESMTP id 88BBA14CFD
for <freebsd-alpha@freebsd.org>; Mon, 21 Jun 1999 08:12:57 -0700 (PDT)
(envelope-from jeff@tad.cetlink.net)
Received: (from jeff@localhost)
by tad.cetlink.net (8.9.2/8.9.1) id LAA93055
for freebsd-alpha@freebsd.org; Mon, 21 Jun 1999 11:12:56 -0400 (EDT)
(envelope-from jeff)
Message-ID: <XFMail.990621111256.jeff@cetlink.net>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Mon, 21 Jun 1999 11:12:56 -0400 (EDT)
Organization: CETLink.Net
From: Jeff Wheat <jeff@cetlink.net>
To: freebsd-alpha@freebsd.org
Subject: Alpha port Questions
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Good day everyone,
I have a few questions regarding FreeBSD-3.2 for the alpha
platform. I have the system installed and running just fine. My problem
however is with the ports collections. I am running FreeBSD on a Dec
AlphaStation 250 4/266. When I attempt to build most things in the
ports collection by typing "make" in a port directory, configure will
do something to the tune of "alpha--FreeBSD" when configure tries to
guess the system type. Going directly into the port work directory
and running configure by hand usually will return "alpha-unknown-FreeBSD".
The TCSH port and package both return the following:
alpha # set
version tcsh 6.08.00 (Astron) 1998-10-02 (i386-unknown-FreeBSD) options 8b,nls,d
l,al,sm,rh,color
alpha# file /usr/local/bin/tcsh
/usr/local/bin/tcsh: ELF 64-bit LSB executable, Alpha, version 1 (FreeBSD), stri
pped
This is of course very wrong... Are there any fixes or work arounds for this?
Many thanks in advance... Please reply directly to me as I am not yet subscribed
to any of these lists.
Best regards,
Jeff
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Mon Jun 21 8:37:22 1999
Delivered-To: freebsd-alpha@freebsd.org
Received: from search.sparks.net (search.sparks.net [208.5.188.60])
by hub.freebsd.org (Postfix) with ESMTP id D14791509A
for <freebsd-alpha@freebsd.org>; Mon, 21 Jun 1999 08:37:14 -0700 (PDT)
(envelope-from dmiller@search.sparks.net)
Received: by search.sparks.net (Postfix, from userid 100)
id 2D054247; Mon, 21 Jun 1999 11:37:09 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
by search.sparks.net (Postfix) with SMTP id 25A7220A
for <freebsd-alpha@freebsd.org>; Mon, 21 Jun 1999 11:37:09 -0400 (EDT)
Date: Mon, 21 Jun 1999 11:37:09 -0400 (EDT)
From: David Miller <dmiller@search.sparks.net>
To: freebsd-alpha@freebsd.org
Subject: General stability?
In-Reply-To: <XFMail.990621111256.jeff@cetlink.net>
Message-ID: <Pine.BSF.3.96.990621112350.5923G-100000@search.sparks.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
I've been lurking on the list for a few days now and haven't seen any
discussion of this. The status page on the freebsd.org server just says:
The alpha port status page has been removed now that the port has
progressed to the stage that anything not in proper working order can
be treated as a bug instead of work-in-progress.
So the question I'm asking is whether the aplha kernel developers feel the
alpha port is stable enough to "bet the farm on". I run a website on
which we expect to see 5-10 million hits/day (spread amongst several
servers) with database access, cgi scripts with some sql lookups - a very
dynamic site. I need the same kind of triple digit uptimes I'm used to
with FreeBSD and other unices.
Is the alpha port at this stage yet, or am I safer sticking to x86 for the
time being?
Thanks,
--- David Miller
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Mon Jun 21 9: 1: 3 1999
Delivered-To: freebsd-alpha@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
by hub.freebsd.org (Postfix) with ESMTP id 20B391504F
for <alpha@freebsd.org>; Mon, 21 Jun 1999 09:01:00 -0700 (PDT)
(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
by wall.polstra.com (8.9.3/8.9.1) with ESMTP id JAA10702
for <alpha@freebsd.org>; Mon, 21 Jun 1999 09:01:00 -0700 (PDT)
(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
by vashon.polstra.com (8.9.3/8.9.1) id JAA01223
for alpha@freebsd.org; Mon, 21 Jun 1999 09:00:59 -0700 (PDT)
(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990621090059.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Mon, 21 Jun 1999 09:00:59 -0700 (PDT)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: alpha@freebsd.org
Subject: Significant speedups from -mcpu=ev56
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
I spent a little time over the weekend trying to make my Alpha go
faster. I found that adding "-mcpu=ev56" gives a nice improvement
in "make buildworld" times. In all cases, CFLAGS also contained the
usual "-O -pipe".
Without -mcpu=ev56: 6570.76 real 4855.53 user 963.15 sys
With -mcpu=ev56: 5913.08 real 4156.91 user 991.84 sys
These builds were under the same kernel, which was compiled without
"-mcpu=ev56". Using the option to build the kernel might help even
more.
The ~30-second increase in sys time seems to be repeatable. I don't
understand it, and wonder if it might be caused by a tallying error of
some kind.
Here are the hardware details:
FreeBSD 4.0-CURRENT #1: Fri May 28 11:09:40 PDT 1999
jdp@alpha.polstra.com:/a/src/sys/compile/ALPHA
EB164
Digital AlphaPC 164LX 533 MHz, 531MHz
8192 byte page size, 1 processor.
CPU: EV56 (21164A) major=7 minor=2 extensions=0x1<BWX>
OSF PAL rev: 0x1000100020116
real memory = 132276224 (129176K bytes)
avail memory = 124207104 (121296K bytes)
...
ncr0: <ncr 53c875 fast20 wide scsi> irq 1 at device 7.0 on pci0
ncr0: interrupting at CIA irq 1
...
da0 at ncr0 bus 0 target 0 lun 0
da0: <IBM DDRS-39130D DC1B> Fixed Direct Access SCSI-2 device
da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled
da0: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C)
The src and obj trees are in the same filesystem, and soft-updates
is enabled there.
It's still a _lot_ slower than my PII/400 (3394.29 real 2370.84 user
506.85 sys).
John
---
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Self-interest is the aphrodisiac of belief." -- James V. DeLong
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Mon Jun 21 9:23: 4 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 9920914FB5
for <alpha@FreeBSD.ORG>; Mon, 21 Jun 1999 09:22:52 -0700 (PDT)
(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 JAA17658; Mon, 21 Jun 1999 09:22:43 -0700 (PDT)
Message-Id: <199906211622.JAA17658@lestat.nas.nasa.gov>
To: John Polstra <jdp@polstra.com>
Cc: alpha@FreeBSD.ORG
Subject: Re: Significant speedups from -mcpu=ev56
Reply-To: Jason Thorpe <thorpej@nas.nasa.gov>
From: Jason Thorpe <thorpej@nas.nasa.gov>
Date: Mon, 21 Jun 1999 09:22:42 -0700
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Mon, 21 Jun 1999 09:00:59 -0700 (PDT)
John Polstra <jdp@polstra.com> wrote:
> It's still a _lot_ slower than my PII/400 (3394.29 real 2370.84 user
> 506.85 sys).
Building a source tree is a really poor measure of relative performance
when you're comparing CISC to RISC. In the latter case, the compiler
does a whole lot more work at compile time.
-- Jason R. Thorpe <thorpej@nas.nasa.gov>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Mon Jun 21 9:32: 2 1999
Delivered-To: freebsd-alpha@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
by hub.freebsd.org (Postfix) with ESMTP id CF34D14FB5
for <alpha@FreeBSD.ORG>; Mon, 21 Jun 1999 09:31:59 -0700 (PDT)
(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
by wall.polstra.com (8.9.3/8.9.1) with ESMTP id JAA10881;
Mon, 21 Jun 1999 09:31:58 -0700 (PDT)
(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
by vashon.polstra.com (8.9.3/8.9.1) id JAA01280;
Mon, 21 Jun 1999 09:31:58 -0700 (PDT)
(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990621093158.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199906211622.JAA17658@lestat.nas.nasa.gov>
Date: Mon, 21 Jun 1999 09:31:58 -0700 (PDT)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: Jason Thorpe <thorpej@nas.nasa.gov>
Subject: Re: Significant speedups from -mcpu=ev56
Cc: alpha@FreeBSD.ORG
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Jason Thorpe wrote:
> On Mon, 21 Jun 1999 09:00:59 -0700 (PDT)
> John Polstra <jdp@polstra.com> wrote:
>
> > It's still a _lot_ slower than my PII/400 (3394.29 real 2370.84 user
> > 506.85 sys).
>
> Building a source tree is a really poor measure of relative performance
> when you're comparing CISC to RISC. In the latter case, the compiler
> does a whole lot more work at compile time.
Excellent point. Too bad that's practically all I use the Alpha for ...
John
---
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Self-interest is the aphrodisiac of belief." -- James V. DeLong
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Mon Jun 21 9:38:36 1999
Delivered-To: freebsd-alpha@freebsd.org
Received: from puh.swox.se (puh.swox.se [212.247.3.130])
by hub.freebsd.org (Postfix) with ESMTP id 32A7414FB5
for <alpha@FreeBSD.ORG>; Mon, 21 Jun 1999 09:38:30 -0700 (PDT)
(envelope-from tege@swox.se)
Received: by puh.swox.se (Postfix, from userid 1001)
id 279B516997; Mon, 21 Jun 1999 18:38:31 +0200 (CEST)
To: Jason Thorpe <thorpej@nas.nasa.gov>
Cc: John Polstra <jdp@polstra.com>, alpha@FreeBSD.ORG
Subject: Re: Significant speedups from -mcpu=ev56
References: <199906211622.JAA17658@lestat.nas.nasa.gov>
From: Torbjorn Granlund <tege@swox.com>
Date: 21 Jun 1999 18:38:31 +0200
In-Reply-To: Jason Thorpe's message of "Mon, 21 Jun 1999 09:22:42 -0700"
Message-ID: <861zf5tsoo.fsf@puh.swox.se>
Lines: 29
User-Agent: Gnus/5.070084 (Pterodactyl Gnus v0.84) Emacs/20.3
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Jason Thorpe <thorpej@nas.nasa.gov> writes:
On Mon, 21 Jun 1999 09:00:59 -0700 (PDT)
John Polstra <jdp@polstra.com> wrote:
> It's still a _lot_ slower than my PII/400 (3394.29 real 2370.84 user
> 506.85 sys).
Building a source tree is a really poor measure of relative performance
when you're comparing CISC to RISC. In the latter case, the compiler
does a whole lot more work at compile time.
Agreed. If you build some cross compilers for various targets on the same
host, you'll notice that the speed difference between GCC backends is very
significant. I measured a factor of ~5 once between x86 and a RISC target
(HPPA).
The reasons are complex, but one thing that makes GCC run slow is a large
number of registers. There are thousands of loops in GCC that loops over
the register numbers. But that is just part of the explanation. There have
been cases in the past where some silly code in a backend has taken most of
the compile time!
If you unvoke cc1 directly (`gcc -v foo.c' will show you how to do that) but
leave out the -quiet option, you'll see a timing profile for the various GCC
passes. Doing that for different backends gives an idea of the variation.
--
Torbjörn
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Mon Jun 21 9:52:27 1999
Delivered-To: freebsd-alpha@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
by hub.freebsd.org (Postfix) with ESMTP id 73D2D14A14
for <alpha@freebsd.org>; Mon, 21 Jun 1999 09:52:23 -0700 (PDT)
(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
by wall.polstra.com (8.9.3/8.9.1) with ESMTP id JAA11004
for <alpha@freebsd.org>; Mon, 21 Jun 1999 09:52:23 -0700 (PDT)
(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
by vashon.polstra.com (8.9.3/8.9.1) id JAA01318
for alpha@freebsd.org; Mon, 21 Jun 1999 09:52:23 -0700 (PDT)
(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990621095223.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Mon, 21 Jun 1999 09:52:23 -0700 (PDT)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: alpha@freebsd.org
Subject: ld-elf.so.1 performance fix for large programs on Alpha
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Yesterday I implemented a fix for the problem reported by Hidetoshi
Shimokawa <simokawa@sat.t.u-tokyo.ac.jp>, in which very large programs
(e.g., gdb) ran very slowly on the Alpha due to a dynamic linker
problem. It passed the make world test, but I'd feel better if
somebody could review it before I commit it. If any of you are
willing to do that, please drop me a line and I'll send you the
diffs.
A brief description of the problem: Large programs on the Alpha exceed
the maximum GOT size of 64K. In that case, the linker uses multiple
GOTs. Thus two or more GOT entries might point to the same lazy
binding stub in the PLT. But on the first call to a lazily bound
function, it is only possible for the dynamic linker to find the first
GOT entry and fix it up to point directly at the target function.
Calls through the other GOT entries still go to the stub code in the
PLT. As a result, the dynamic linker goes through the entire lazy
binding process on every call that goes through an auxiliary GOT
entry. Since that involves searching a bunch of symbol tables, it's
very slow.
The fix was to rewrite the stubs in the PLT itself during lazy
binding. The dynamic linker overwrites the original stub with code
that jumps to the target function. With that change, even calls
through the auxiliary GOT entries can bypass the lazy binding code.
Each PLT entry has room for 3 instructions, and I was able to find a
way to generate a jump to the target function in that amount of space,
no matter how far away the function is. I believe the rewriting is
done in a threadsafe and MP-safe manner, and an IMB instruction is
executed after the rewriting is finished to flush the instruction
cache.
It was a major change, and breaking the dynamic linker is a one-way
journey to the fixit floppy. I'd appreciate a review if any of you
have the time.
John
---
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Self-interest is the aphrodisiac of belief." -- James V. DeLong
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Mon Jun 21 10:46:54 1999
Delivered-To: freebsd-alpha@freebsd.org
Received: from student.lssu.edu (student.lssu.edu [198.110.216.219])
by hub.freebsd.org (Postfix) with ESMTP
id 2EBDD15110; Mon, 21 Jun 1999 10:46:51 -0700 (PDT)
(envelope-from pe@student.lssu.edu)
Received: from localhost (pe@localhost)
by student.lssu.edu (8.9.3/8.9.3) with ESMTP id NAA24627;
Mon, 21 Jun 1999 13:47:32 -0400 (EDT)
Date: Mon, 21 Jun 1999 13:47:32 -0400 (EDT)
From: "System Admin." <pe@student.lssu.edu>
To: freebsd-questions@freebsd.org, freebsd-alpha@freebsd.org
Subject: pcnfsd
Message-ID: <Pine.GSO.4.05.9906211346130.24600-100000@student.lssu.edu>
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,
is there any documentation on how to setup pcnfs on FreeBSD-3.2?
TIA
pe'
------------------------------
UNIX System Admin.
Distributed Computing Services
Lake Superior State University
650 W. Easterday Ave.
Sault Ste. Marie. MI
49783 USA.
------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Mon Jun 21 18:40:36 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 7919315180
for <freebsd-alpha@FreeBSD.ORG>; Mon, 21 Jun 1999 18:40:29 -0700 (PDT)
(envelope-from sprice@hiwaay.net)
Received: from localhost (sprice@localhost)
by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id UAA09676;
Mon, 21 Jun 1999 20:40:27 -0500 (CDT)
Date: Mon, 21 Jun 1999 20:40:27 -0500 (CDT)
From: Steve Price <sprice@hiwaay.net>
To: Jeff Wheat <jeff@cetlink.net>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: Alpha port Questions
In-Reply-To: <XFMail.990621111256.jeff@cetlink.net>
Message-ID: <Pine.OSF.4.10.9906212021350.28278-100000@fly.HiWAAY.net>
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, 21 Jun 1999, Jeff Wheat wrote:
# Good day everyone,
#
# I have a few questions regarding FreeBSD-3.2 for the alpha
# platform. I have the system installed and running just fine. My problem
# however is with the ports collections. I am running FreeBSD on a Dec
# AlphaStation 250 4/266. When I attempt to build most things in the
# ports collection by typing "make" in a port directory, configure will
# do something to the tune of "alpha--FreeBSD" when configure tries to
# guess the system type. Going directly into the port work directory
# and running configure by hand usually will return "alpha-unknown-FreeBSD".
# The TCSH port and package both return the following:
This is because is build from the port's Makefile, bsd.port.mk
forces the target host to alpha--freebsd4.0. When left to its own
accord the ./configure script will find it can't determine the
vendor and replaces it with unknown instead of leaving it blank.
It is completely harmless. :)
# alpha # set
# version tcsh 6.08.00 (Astron) 1998-10-02 (i386-unknown-FreeBSD) options 8b,nls,d
# l,al,sm,rh,color
# alpha# file /usr/local/bin/tcsh
# /usr/local/bin/tcsh: ELF 64-bit LSB executable, Alpha, version 1 (FreeBSD), stri
# pped
#
# This is of course very wrong... Are there any fixes or work arounds for this?
There wasn't until now. :-) Add the following as patch-ad and
try it again.
----- cut here 8<--------------------------------------------------
--- host.defs.orig Mon Jun 21 20:11:51 1999
+++ host.defs Mon Jun 21 20:14:16 1999
@@ -494,10 +494,12 @@
newdef : defined(__FreeBSD__)
comment : FreeBSD
+vendor : defined(__alpha) : "digital"
vendor : defined(M_intel) : "intel"
hosttype: : "FreeBSD"
ostype : : "FreeBSD"
-machtype: : "i386"
+machtype: defined(__alpha) : "alpha"
+machtype: defined(M_i386) : "i386"
enddef :
----- cut here 8<--------------------------------------------------
BTW, thanks for catching this. The Alpha ports collection is still
in its infancy. My first build only about a month ago had a meager
1200 out of 2400 possible ports represented. With the last build I
was able to get this number up to 1820 or so. There are still quite
a few (~600) that are just plain broken and no doubt also quite a
few of the 1820 that run but have minor nits to fix. This turned
out to be one of the latter.
Anyone else that has noticed problems, has patches, or would like
to lend a hand, please let me know. ;)
Thanks.
-steve
# Many thanks in advance... Please reply directly to me as I am not yet subscribed
# to any of these lists.
#
# Best regards,
# Jeff
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Mon Jun 21 19:27:56 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 029F414DC9
for <freebsd-alpha@freebsd.org>; Mon, 21 Jun 1999 19:27:36 -0700 (PDT)
(envelope-from sprice@hiwaay.net)
Received: from localhost (sprice@localhost)
by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id VAA11044
for <freebsd-alpha@freebsd.org>; Mon, 21 Jun 1999 21:27:35 -0500 (CDT)
Date: Mon, 21 Jun 1999 21:27:34 -0500 (CDT)
From: Steve Price <sprice@hiwaay.net>
To: freebsd-alpha@freebsd.org
Subject: fpsetmask from C++ program on Alpha
Message-ID: <Pine.OSF.4.10.9906212124110.28278-100000@fly.HiWAAY.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Anyone have an objection to me committing something along
the lines of the following patch so that one can use
fpsetmask(3) and friends from a C++ program on the Alpha?
Thanks.
-steve
Index: ieeefp.h
===================================================================
RCS file: /home/ncvs/src/include/ieeefp.h,v
retrieving revision 1.2
diff -u -r1.2 ieeefp.h
--- ieeefp.h 1999/03/05 18:15:05 1.2
+++ ieeefp.h 1999/06/22 02:22:21
@@ -14,12 +14,14 @@
#ifdef __i386__
#include <machine/floatingpoint.h>
#else /* !__i386__ */
+__BEGIN_DECLS
extern fp_rnd fpgetround __P((void));
extern fp_rnd fpsetround __P((fp_rnd));
extern fp_except fpgetmask __P((void));
extern fp_except fpsetmask __P((fp_except));
extern fp_except fpgetsticky __P((void));
extern fp_except fpsetsticky __P((fp_except));
+__END_DECLS
#endif /* __i386__ */
#endif /* _IEEEFP_H_ */
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Tue Jun 22 1:49:18 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 4322015286
for <freebsd-alpha@freebsd.org>; Tue, 22 Jun 1999 01:49:12 -0700 (PDT)
(envelope-from dfr@nlsystems.com)
Received: from localhost (dfr@localhost)
by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA51685;
Tue, 22 Jun 1999 09:50:38 +0100 (BST)
(envelope-from dfr@nlsystems.com)
Date: Tue, 22 Jun 1999 09:50:37 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: David Miller <dmiller@search.sparks.net>
Cc: freebsd-alpha@freebsd.org
Subject: Re: General stability?
In-Reply-To: <Pine.BSF.3.96.990621112350.5923G-100000@search.sparks.net>
Message-ID: <Pine.BSF.4.05.9906220948190.80685-100000@herring.nlsystems.com>
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, 21 Jun 1999, David Miller wrote:
> I've been lurking on the list for a few days now and haven't seen any
> discussion of this. The status page on the freebsd.org server just says:
>
> The alpha port status page has been removed now that the port has
> progressed to the stage that anything not in proper working order can
> be treated as a bug instead of work-in-progress.
>
> So the question I'm asking is whether the aplha kernel developers feel the
> alpha port is stable enough to "bet the farm on". I run a website on
> which we expect to see 5-10 million hits/day (spread amongst several
> servers) with database access, cgi scripts with some sql lookups - a very
> dynamic site. I need the same kind of triple digit uptimes I'm used to
> with FreeBSD and other unices.
>
> Is the alpha port at this stage yet, or am I safer sticking to x86 for the
> time being?
I think that the alpha port is pretty solid right now but I haven't run
any systems under this kind of load. I would be very interested in hearing
about how the port stands up in this situation.
--
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 Jun 22 1:53:58 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 8FF36151CF
for <freebsd-alpha@freebsd.org>; Tue, 22 Jun 1999 01:53:54 -0700 (PDT)
(envelope-from dfr@nlsystems.com)
Received: from localhost (dfr@localhost)
by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA52856;
Tue, 22 Jun 1999 09:55:39 +0100 (BST)
(envelope-from dfr@nlsystems.com)
Date: Tue, 22 Jun 1999 09:55:39 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: Steve Price <sprice@hiwaay.net>
Cc: freebsd-alpha@freebsd.org
Subject: Re: fpsetmask from C++ program on Alpha
In-Reply-To: <Pine.OSF.4.10.9906212124110.28278-100000@fly.HiWAAY.net>
Message-ID: <Pine.BSF.4.05.9906220955080.80685-100000@herring.nlsystems.com>
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, 21 Jun 1999, Steve Price wrote:
> Anyone have an objection to me committing something along
> the lines of the following patch so that one can use
> fpsetmask(3) and friends from a C++ program on the Alpha?
This is certainly the right thing to do. Please commit the patch.
--
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 Jun 23 2:18: 7 1999
Delivered-To: freebsd-alpha@freebsd.org
Received: from smtp2.xs4all.nl (smtp2.xs4all.nl [194.109.6.52])
by hub.freebsd.org (Postfix) with ESMTP id D6DFA14E53
for <freebsd-alpha@freebsd.org>; Wed, 23 Jun 1999 02:18:04 -0700 (PDT)
(envelope-from bram@nuson.nl)
Received: (from root@localhost)
by smtp2.xs4all.nl (8.8.8/8.8.8) id LAA23785;
Wed, 23 Jun 1999 11:18:01 +0200 (CEST)
From: Bram Stolk <bram@nuson.nl>
To: freebsd-alpha@freebsd.org
X-Via: imploder /usr/local/lib/mail/news2mail/news2mail at smtp2.xs4all.nl
Subject: Re: Significant speedups from -mcpu=ev56
Date: Wed, 23 Jun 1999 11:21:23 +0200
Organization: XS4ALL Internet BV
Message-ID: <3770A713.60311213@nuson.nl>
In-Reply-To: <XFMail.990621090059.jdp@polstra.com>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Hi,
Will code compiled with -mcpu=ev56 still run on ancient alphas?
Or will there be made use of instructions that are only available
on the ev56 machines?
Added performance is great, but if it hurts compatibility, I am
not so sure I want it.
Thanks,
Bram
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Wed Jun 23 2:28: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 8C43714CE2
for <freebsd-alpha@freebsd.org>; Wed, 23 Jun 1999 02:28:21 -0700 (PDT)
(envelope-from dfr@nlsystems.com)
Received: from localhost (dfr@localhost)
by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA20662;
Wed, 23 Jun 1999 10:30:20 +0100 (BST)
(envelope-from dfr@nlsystems.com)
Date: Wed, 23 Jun 1999 10:30:20 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: Bram Stolk <bram@nuson.nl>
Cc: freebsd-alpha@freebsd.org
Subject: Re: Significant speedups from -mcpu=ev56
In-Reply-To: <3770A713.60311213@nuson.nl>
Message-ID: <Pine.BSF.4.05.9906231029280.80685-100000@herring.nlsystems.com>
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, 23 Jun 1999, Bram Stolk wrote:
> Hi,
>
> Will code compiled with -mcpu=ev56 still run on ancient alphas?
> Or will there be made use of instructions that are only available
> on the ev56 machines?
>
> Added performance is great, but if it hurts compatibility, I am
> not so sure I want it.
It will break on old alphas. I think NetBSD recently added code to their
kernel to emulate these instructions which would allow them to work (with
a performance penalty).
--
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 Jun 23 3: 7:10 1999
Delivered-To: freebsd-alpha@freebsd.org
Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162])
by hub.freebsd.org (Postfix) with SMTP id D21CE14BB8
for <freebsd-alpha@freebsd.org>; Wed, 23 Jun 1999 03:07:04 -0700 (PDT)
(envelope-from sthaug@nethelp.no)
Received: (qmail 48443 invoked by uid 1001); 23 Jun 1999 10:04:36 +0000 (GMT)
To: dfr@nlsystems.com
Cc: freebsd-alpha@freebsd.org
Subject: Re: Significant speedups from -mcpu=ev56
From: sthaug@nethelp.no
In-Reply-To: Your message of "Wed, 23 Jun 1999 10:30:20 +0100 (BST)"
References: <Pine.BSF.4.05.9906231029280.80685-100000@herring.nlsystems.com>
X-Mailer: Mew version 1.05+ on Emacs 19.34.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Wed, 23 Jun 1999 12:04:35 +0200
Message-ID: <48441.930132275@verdi.nethelp.no>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
> It will break on old alphas. I think NetBSD recently added code to their
> kernel to emulate these instructions which would allow them to work (with
> a performance penalty).
A little question about old Alphas: I have an Alphastation 200 4/100 here,
100 Mhz 21064. It feels "slow as molasses" compared to e.g. a P-133. Is
there any possibility of overclocking these machines? (Yes, I know, one
shouldn't overclock, and it can break things. I don't care - this is not
a critical machine...)
Steinar Haug, Nethelp consulting, sthaug@nethelp.no
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Wed Jun 23 8:17:45 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 87CB1152E3
for <freebsd-alpha@FreeBSD.ORG>; Wed, 23 Jun 1999 08:17:39 -0700 (PDT)
(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 IAA22409; Wed, 23 Jun 1999 08:17:32 -0700 (PDT)
Message-Id: <199906231517.IAA22409@lestat.nas.nasa.gov>
To: Bram Stolk <bram@nuson.nl>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: Significant speedups from -mcpu=ev56
Reply-To: Jason Thorpe <thorpej@nas.nasa.gov>
From: Jason Thorpe <thorpej@nas.nasa.gov>
Date: Wed, 23 Jun 1999 08:17:31 -0700
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Wed, 23 Jun 1999 11:21:23 +0200
Bram Stolk <bram@nuson.nl> wrote:
> Will code compiled with -mcpu=ev56 still run on ancient alphas?
> Or will there be made use of instructions that are only available
> on the ev56 machines?
It will, no doubt, use BWX instructions.
However, it's worth noting that programs which use BWX can expect the
operating system to trap and emulate those instructions in the event
they don't exist on the CPU the program is running on. This is described
in an Alpha ABI document, but I don't recall exactly which one.
NetBSD/alpha supports all of this, of course.
-- Jason R. Thorpe <thorpej@nas.nasa.gov>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Thu Jun 24 0:45: 4 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 1931A14EE7
for <freebsd-alpha@freebsd.org>; Thu, 24 Jun 1999 00:44:59 -0700 (PDT)
(envelope-from dfr@nlsystems.com)
Received: from localhost (dfr@localhost)
by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA35515;
Thu, 24 Jun 1999 08:47:03 +0100 (BST)
(envelope-from dfr@nlsystems.com)
Date: Thu, 24 Jun 1999 08:47:03 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: sthaug@nethelp.no
Cc: freebsd-alpha@freebsd.org
Subject: Re: Significant speedups from -mcpu=ev56
In-Reply-To: <48441.930132275@verdi.nethelp.no>
Message-ID: <Pine.BSF.4.05.9906240846250.80685-100000@herring.nlsystems.com>
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, 23 Jun 1999 sthaug@nethelp.no wrote:
> > It will break on old alphas. I think NetBSD recently added code to their
> > kernel to emulate these instructions which would allow them to work (with
> > a performance penalty).
>
> A little question about old Alphas: I have an Alphastation 200 4/100 here,
> 100 Mhz 21064. It feels "slow as molasses" compared to e.g. a P-133. Is
> there any possibility of overclocking these machines? (Yes, I know, one
> shouldn't overclock, and it can break things. I don't care - this is not
> a critical machine...)
I have absolutely no idea.
--
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 Jun 25 7:34:49 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 61ADA14FBD; Fri, 25 Jun 1999 07:34:31 -0700 (PDT)
(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 6214475; Fri, 25 Jun 1999 22:34:28 +0800 (WST)
(envelope-from peter@netplex.com.au)
X-Mailer: exmh version 2.0.2 2/24/98
To: freebsd-alpha@freebsd.org
Cc: msmith@freebsd.org
Subject: AARGH!! "dead" Alpha 164SX (Was: Re: OK, any pointers on how to use SRM? :-))
In-reply-to: Your message of "Sun, 20 Jun 1999 17:22:22 +0800."
<19990620092222.426DB75@overcee.netplex.com.au>
Date: Fri, 25 Jun 1999 22:34:28 +0800
From: Peter Wemm <peter@netplex.com.au>
Message-Id: <19990625143428.6214475@overcee.netplex.com.au>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Peter Wemm wrote:
> Christian Weisgerber wrote:
> > Peter Wemm <peter@netplex.com.au> wrote:
[..]
> However, I have another problem that I could do with some advice on.
> Basically at the moment I'm short of an ATX power supply and case (damn
> weekends). So, itching to get going, I took my workstation apart and
> mounted the AlphaPC 164SX motherboard. However, the power supply promptly
> expired. (!)
>
> Apon investigation, with the old motherboard back in, the +3.3V power lines
> from the power supply was supplying 1.9V instead and the hardware monitoring
> was having a fit and making ambulance siren sounds from the speaker. (!!).
>
> After checking the 164SX motherboard again, I find the +3V-to-gnd
> resistance is very close to 0.0 ohms, sometimes it sits at 0.2 ohms for a
> few seconds after first attaching the DMM leads.
>
> Taking out the CPU brings the +3.3V-to-gnd resistance to over 1K ohms, which
> is in line with the other supply pins on the motherboard.
Well, the problem has been found.. Mike Smith gave me a new graphoil pad
to use since the heatsink was taken off for transit.. But the new one was
bigger than required and the thought never occurred that it might have been
rather conductive and that it was going to short out those 12 capacitors on
the top of the CPU surface, which, BTW, were between 3.3V and ground.
So, the thing had pulled more than 14 amps of 3.3V through the graphoil/
heatsink and killed the first ATX power supply.... The second one I got
had some sort of current limiter and was happily pumping 14+ amps through
the motherboard to the cpu and loosing regulation (dropping to 1.2V).
It all makes sense now. "Aargh Shit!" certainly seems appropriate.
Anyway, after some careful trimming of the pad, I've now got it running to
the point of SRM startup... (And there was I thinking I'd found a hairline
crack in one of the mounts for a component from transit damage in my
luggage..)
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 Jun 25 8:48:39 1999
Delivered-To: freebsd-alpha@freebsd.org
Received: from gateway.vsec.com.br (unknown [200.252.114.230])
by hub.freebsd.org (Postfix) with SMTP id 8B3AD14D6F
for <freebsd-alpha@freebsd.org>; Fri, 25 Jun 1999 08:48:25 -0700 (PDT)
(envelope-from freebsd@gateway.virtualsecurity.com.br)
Received: (qmail 967 invoked by uid 1004); 25 Jun 1999 12:21:29 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
by localhost with SMTP; 25 Jun 1999 12:21:29 -0000
Date: Fri, 25 Jun 1999 12:21:29 +0000 (GMT)
From: Free Alpha List <freebsd@gateway.virtualsecurity.com.br>
To: freebsd-alpha@freebsd.org
Subject: SCSI controllers
In-Reply-To: <19990625143428.6214475@overcee.netplex.com.au>
Message-ID: <Pine.BSF.4.01.9906251217520.959-100000@gateway.virtualsecurity.com.br>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
What`s SCSI controllers can I use with 164sx running Freebsd?
I tested one ADAPTEC 2940AU and one 1522 but the SRM 4.9 doesn`t
detect.
the show dev only report the floppy and the IDE controllers.
thanks
Adriano
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jun 25 9:47:55 1999
Delivered-To: freebsd-alpha@freebsd.org
Received: from dingo.cdrom.com (castles520.castles.com [208.214.165.84])
by hub.freebsd.org (Postfix) with ESMTP
id 2E9F6150CF; Fri, 25 Jun 1999 09:47:53 -0700 (PDT)
(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 JAA03228;
Fri, 25 Jun 1999 09:44:05 -0700 (PDT)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199906251644.JAA03228@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Peter Wemm <peter@netplex.com.au>
Cc: freebsd-alpha@freebsd.org, msmith@freebsd.org
Subject: Re: AARGH!! "dead" Alpha 164SX (Was: Re: OK, any pointers on how to use SRM? :-))
In-reply-to: Your message of "Fri, 25 Jun 1999 22:34:28 +0800."
<19990625143428.6214475@overcee.netplex.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 25 Jun 1999 09:44:05 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
>
> Well, the problem has been found.. Mike Smith gave me a new graphoil pad
> to use since the heatsink was taken off for transit.. But the new one was
> bigger than required and the thought never occurred that it might have been
> rather conductive and that it was going to short out those 12 capacitors on
> the top of the CPU surface, which, BTW, were between 3.3V and ground.
"Aargh shit". I never even thought to check that.
> It all makes sense now. "Aargh Shit!" certainly seems appropriate.
> Anyway, after some careful trimming of the pad, I've now got it running to
> the point of SRM startup... (And there was I thinking I'd found a hairline
> crack in one of the mounts for a component from transit damage in my
> luggage..)
Whee, happiness!
--
\\ The mind's the standard \\ Mike Smith
\\ of the man. \\ msmith@freebsd.org
\\ -- Joseph Merrick \\ 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 Fri Jun 25 10:26:21 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 5B56615011
for <freebsd-alpha@FreeBSD.ORG>; Fri, 25 Jun 1999 10:26:19 -0700 (PDT)
(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 KAA27150;
Fri, 25 Jun 1999 10:25:59 -0700
Date: Fri, 25 Jun 1999 10:24:22 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Free Alpha List <freebsd@gateway.virtualsecurity.com.br>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: SCSI controllers
In-Reply-To: <Pine.BSF.4.01.9906251217520.959-100000@gateway.virtualsecurity.com.br>
Message-ID: <Pine.BSF.4.05.9906251022590.38018-100000@semuta.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Qlogic 1020/1040, 1080, 1240 and 2100 (Fibre Channel).
The 1020/1040 can be booted from.
NCR 53c810a, 53c825, 53c875, and maybe the first channel on a 53c876.
On Fri, 25 Jun 1999, Free Alpha List wrote:
> What`s SCSI controllers can I use with 164sx running Freebsd?
> I tested one ADAPTEC 2940AU and one 1522 but the SRM 4.9 doesn`t
> detect.
> the show dev only report the floppy and the IDE controllers.
>
>
> thanks
>
>
> Adriano
>
>
>
>
> 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 Jun 25 10:39:27 1999
Delivered-To: freebsd-alpha@freebsd.org
Received: from cmpharm.ucsf.edu (cmpharm.ucsf.edu [128.218.67.18])
by hub.freebsd.org (Postfix) with ESMTP id 5886714D23
for <alpha@FreeBSD.ORG>; Fri, 25 Jun 1999 10:39:24 -0700 (PDT)
(envelope-from steve@cmpharm.ucsf.edu)
Received: from piglet.ucsf.edu (steve@piglet.ucsf.edu [128.218.67.20])
by cmpharm.ucsf.edu (8.9.3/8.9.3) with ESMTP id KAA16442
for <alpha@FreeBSD.ORG>; Fri, 25 Jun 1999 10:39:14 -0700 (PDT)
Received: (from steve@localhost)
by piglet.ucsf.edu (8.9.3/8.9.3) id KAA89356
for alpha@FreeBSD.ORG; Fri, 25 Jun 1999 10:39:23 -0700 (PDT)
Date: Fri, 25 Jun 1999 10:39:23 -0700
From: Steve Sizemore <steve@cmpharm.ucsf.edu>
To: alpha@FreeBSD.ORG
Subject: make buildworld failure
Message-ID: <19990625103923.A94872@cmpharm.ucsf.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
I have been unable to complete a "make buildworld" for over a week
now, on my 164LX system. Not being in a hurry, I figured that I'd
just wait for someone else to see this and fix it, but apparently I'm
the only one this is happening to. I've tried all my normal tricks,
including wiping out my source and re'cvsup'ing, but it always fails
at the same place -
cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -static -o yacc
closure.o error.o lalr.o lr0.o main.o mkpar.o output.o reader.o
skeleton.o symtab.o verbose.o warshall.o
install -c -o root -g wheel -m 555 /usr/src/usr.bin/yacc/yyfix.sh
/usr/obj/usr/src/tmp/usr/bin/yyfix
install -c -s -o root -g wheel -m 555 yacc /usr/obj/usr/src/tmp/usr/bin
*** Error code 70
Stop.
*** Error code 1
If I cd to that directory, and run install manually, it fails. If I
cd to the corresponding directory in the obj hierarchy, and run
install manually, it succeeds. I suspect that something broke
install, since this occurs right after xinstall gets built, but I
can't believe that no one else would have noticed it.
Ideas?
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 Fri Jun 25 14:46:19 1999
Delivered-To: freebsd-alpha@freebsd.org
Received: from gateway.vsec.com.br (unknown [200.252.114.230])
by hub.freebsd.org (Postfix) with SMTP id 821E015891
for <freebsd-alpha@freebsd.org>; Fri, 25 Jun 1999 14:46:16 -0700 (PDT)
(envelope-from freebsd@gateway.virtualsecurity.com.br)
Received: (qmail 1232 invoked by uid 1004); 25 Jun 1999 18:19:18 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
by localhost with SMTP; 25 Jun 1999 18:19:18 -0000
Date: Fri, 25 Jun 1999 18:19:18 +0000 (GMT)
From: Free Alpha List <freebsd@gateway.virtualsecurity.com.br>
To: freebsd-alpha@freebsd.org
Subject: IDE Disks Now
Message-ID: <Pine.BSF.4.01.9906251816230.959-100000@gateway.virtualsecurity.com.br>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
I didn`t found any way to put my 164sx running with one Adaptec
2940 SCSI controller.
what I need to do to install freeBSD 3.1 using the EIDE onboard
controller on the 164sx?
adriano
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jun 25 19: 7:41 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 DBF7115799
for <freebsd-alpha@freebsd.org>; Fri, 25 Jun 1999 19:07:33 -0700 (PDT)
(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 WAA25963;
Fri, 25 Jun 1999 22:07:23 -0400 (EDT)
Received: (from gallatin@localhost)
by grasshopper.cs.duke.edu (8.9.3/8.9.1) id WAA16808;
Fri, 25 Jun 1999 22:07:23 -0400 (EDT)
(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Fri, 25 Jun 1999 22:07:23 -0400 (EDT)
To: freebsd-alpha@freebsd.org
Cc: port-alpha@netbsd.org
Subject: DEC Server 530x?
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid
Message-ID: <14196.12866.714386.831497@grasshopper.cs.duke.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Anybody know what the heck an AlphaServer1200 is? Is it a scaled down
rawhide? I ask because a NECX is selling something called the 'Digital
Server 5300' with a 400Mhz 21164 for $800USD.
According to some of the old DEC info, the 5300 was formerly known as
the 'AlphaServer 1200 for Windows NT.' And according to some linux
documentation I've seen, a 1200 is the 'TINCUP' variation of the
rawhide family. (http://www.redhat.com/support/docs/rhl/alpha/rh52-hardware-alpha-3.html)
Anybody know if
a) SRM will run on a 5300
b) NetBSD will run on a 5300 (or a 1200) as if it were a normal rawhide?
c) the 5300, like the AS1200, can accept a second CPU?
Thanks,
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 Sat Jun 26 2:43:26 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 87F9B14BE9; Sat, 26 Jun 1999 02:43:15 -0700 (PDT)
(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 68C0775; Sat, 26 Jun 1999 17:43:14 +0800 (WST)
(envelope-from peter@netplex.com.au)
X-Mailer: exmh version 2.0.2 2/24/98
To: Mike Smith <mike@smith.net.au>
Cc: freebsd-alpha@freebsd.org, msmith@freebsd.org
Subject: Re: AARGH!! "dead" Alpha 164SX (Was: Re: OK, any pointers on how to use SRM? :-))
In-reply-to: Your message of "Fri, 25 Jun 1999 09:44:05 MST."
<199906251644.JAA03228@dingo.cdrom.com>
Date: Sat, 26 Jun 1999 17:43:14 +0800
From: Peter Wemm <peter@netplex.com.au>
Message-Id: <19990626094314.68C0775@overcee.netplex.com.au>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Mike Smith wrote:
> >
> > Well, the problem has been found.. Mike Smith gave me a new graphoil pad
> > to use since the heatsink was taken off for transit.. But the new one was
> > bigger than required and the thought never occurred that it might have been
> > rather conductive and that it was going to short out those 12 capacitors on
> > the top of the CPU surface, which, BTW, were between 3.3V and ground.
>
> "Aargh shit". I never even thought to check that.
Likewise, it took me 8 hours to realize the first boot for 30 seconds that
I got the first time was with the heatsink off.. Once I realized that, then
I got one of those "Hmm, I wonder if...." kind of feelings and sure enough..
> > It all makes sense now. "Aargh Shit!" certainly seems appropriate.
> > Anyway, after some careful trimming of the pad, I've now got it running to
> > the point of SRM startup... (And there was I thinking I'd found a hairline
> > crack in one of the mounts for a component from transit damage in my
> > luggage..)
>
> Whee, happiness!
It seems to run reliably at 533MHz as well. If the kernel has softupdates
compiled in, all sorts of things fail during boot including sysctl and
sometimes mount_nfs. If softupdates are active, not just in the kernel,
then 'make world' wedges 5 seconds into the bootstrap build of make. This
is the same at both 400MHz and 533MHz. Compiling softupdates out has
resulted in an (apparently) happy system at 533.
The next good question is.. what's up with softupdates? :-] Hmm.. say,
that NCR controller you gave me, is that the one that was screwing up on
freefall by any chance?
Cheers,
-Peter
--
Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Sat Jun 26 3:50:12 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 76D4C14E8E; Sat, 26 Jun 1999 03:50:08 -0700 (PDT)
(envelope-from dfr@nlsystems.com)
Received: from localhost (dfr@localhost)
by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA59064;
Sat, 26 Jun 1999 11:51:59 +0100 (BST)
(envelope-from dfr@nlsystems.com)
Date: Sat, 26 Jun 1999 11:51:59 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: Peter Wemm <peter@netplex.com.au>
Cc: Mike Smith <mike@smith.net.au>, freebsd-alpha@freebsd.org,
msmith@freebsd.org
Subject: Re: AARGH!! "dead" Alpha 164SX (Was: Re: OK, any pointers on how to
use SRM? :-))
In-Reply-To: <19990626094314.68C0775@overcee.netplex.com.au>
Message-ID: <Pine.BSF.4.05.9906261150020.80685-100000@herring.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Sat, 26 Jun 1999, Peter Wemm wrote:
> Mike Smith wrote:
> > >
> > > Well, the problem has been found.. Mike Smith gave me a new graphoil pad
> > > to use since the heatsink was taken off for transit.. But the new one was
> > > bigger than required and the thought never occurred that it might have been
> > > rather conductive and that it was going to short out those 12 capacitors on
> > > the top of the CPU surface, which, BTW, were between 3.3V and ground.
> >
> > "Aargh shit". I never even thought to check that.
>
> Likewise, it took me 8 hours to realize the first boot for 30 seconds that
> I got the first time was with the heatsink off.. Once I realized that, then
> I got one of those "Hmm, I wonder if...." kind of feelings and sure enough..
>
> > > It all makes sense now. "Aargh Shit!" certainly seems appropriate.
> > > Anyway, after some careful trimming of the pad, I've now got it running to
> > > the point of SRM startup... (And there was I thinking I'd found a hairline
> > > crack in one of the mounts for a component from transit damage in my
> > > luggage..)
> >
> > Whee, happiness!
>
> It seems to run reliably at 533MHz as well. If the kernel has softupdates
> compiled in, all sorts of things fail during boot including sysctl and
> sometimes mount_nfs. If softupdates are active, not just in the kernel,
> then 'make world' wedges 5 seconds into the bootstrap build of make. This
> is the same at both 400MHz and 533MHz. Compiling softupdates out has
> resulted in an (apparently) happy system at 533.
>
> The next good question is.. what's up with softupdates? :-] Hmm.. say,
> that NCR controller you gave me, is that the one that was screwing up on
> freefall by any chance?
Softupdates normally works very well on my alphas. I think that there is
some kind of hardware problem with that machine. I'm just building a fresh
current kernel with softupdates so we will see.
--
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 Sat Jun 26 8:29: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 1D54114D76
for <freebsd-alpha@freebsd.org>; Sat, 26 Jun 1999 08:29:14 -0700 (PDT)
(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 RAA23397;
Sat, 26 Jun 1999 17:15:41 +0200 (MET DST)
Received: (from wilko@localhost)
by yedi.iaf.nl (8.9.3/8.9.3) id LAA98830;
Sat, 26 Jun 1999 11:48:49 +0200 (CEST)
(envelope-from wilko)
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199906260948.LAA98830@yedi.iaf.nl>
Subject: Re: DEC Server 530x?
In-Reply-To: <14196.12866.714386.831497@grasshopper.cs.duke.edu> from Andrew Gallatin at "Jun 25, 1999 10: 7:23 pm"
To: gallatin@cs.duke.edu (Andrew Gallatin)
Date: Sat, 26 Jun 1999 11:48:47 +0200 (CEST)
Cc: freebsd-alpha@freebsd.org, port-alpha@netbsd.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 ...
>
> Anybody know what the heck an AlphaServer1200 is? Is it a scaled down
> rawhide? I ask because a NECX is selling something called the 'Digital
> Server 5300' with a 400Mhz 21164 for $800USD.
>
> According to some of the old DEC info, the 5300 was formerly known as
> the 'AlphaServer 1200 for Windows NT.' And according to some linux
A, a 'whitebox' Alpha.
> documentation I've seen, a 1200 is the 'TINCUP' variation of the
> rawhide family. (http://www.redhat.com/support/docs/rhl/alpha/rh52-hardware-alpha-3.html)
>
> Anybody know if
>
> a) SRM will run on a 5300
It could very well be that it does not. It is from the days DEC tried
to seperately price NT and 'real' Alphas.
> b) NetBSD will run on a 5300 (or a 1200) as if it were a normal rawhide?
> c) the 5300, like the AS1200, can accept a second CPU?
I will check this for you with my AXP-guru colleague. Will be monday before
I can followup.
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 Sat Jun 26 13:17:20 1999
Delivered-To: freebsd-alpha@freebsd.org
Received: from burka.rdy.com (burka.rdy.com [205.149.163.30])
by hub.freebsd.org (Postfix) with ESMTP
id 999E8150B4; Sat, 26 Jun 1999 13:17:17 -0700 (PDT)
(envelope-from dima@burka.rdy.com)
Received: (from dima@localhost)
by burka.rdy.com (8.9.3/RDY&DVV) id NAA00811;
Sat, 26 Jun 1999 13:15:09 -0700 (PDT)
Message-Id: <199906262015.NAA00811@burka.rdy.com>
Subject: Re: AARGH!! "dead" Alpha 164SX (Was: Re: OK, any pointers on how to use SRM? :-))
In-Reply-To: <Pine.BSF.4.05.9906261150020.80685-100000@herring.nlsystems.com> from Doug Rabson at "Jun 26, 1999 11:51:59 am"
To: dfr@nlsystems.com (Doug Rabson)
Date: Sat, 26 Jun 1999 13:15:08 -0700 (PDT)
Cc: peter@netplex.com.au (Peter Wemm),
mike@smith.net.au (Mike Smith), freebsd-alpha@freebsd.org,
msmith@freebsd.org
X-Class: Fast
Organization: HackerDome
Reply-To: dima@best.net
From: dima@best.net (Dima Ruban)
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
Doug Rabson writes:
> Softupdates normally works very well on my alphas. I think that there is
> some kind of hardware problem with that machine. I'm just building a fresh
> current kernel with softupdates so we will see.
I don't have any problem with softupdates on my alpha as well.
>
> --
> 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
>
-- dima
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Sat Jun 26 16:29:38 1999
Delivered-To: freebsd-alpha@freebsd.org
Received: from metzelkueche.tabu.uni-bonn.de (metzelkueche.tabu.uni-bonn.de [131.220.159.242])
by hub.freebsd.org (Postfix) with ESMTP id 00BB615231
for <freebsd-alpha@FreeBSD.ORG>; Sat, 26 Jun 1999 16:29:34 -0700 (PDT)
(envelope-from armin@openBSD.de)
Received: from localhost (armin@localhost)
by metzelkueche.tabu.uni-bonn.de (8.9.1/8.8.7) with SMTP id BAA17522
for <freebsd-alpha@FreeBSD.ORG>; Sun, 27 Jun 1999 01:29:27 +0200
Date: Sun, 27 Jun 1999 01:29:27 +0200 (CEST)
From: Armin Ollig <armin@openBSD.de>
X-Sender: armin@metzelkueche.tabu.uni-bonn.de
To: freebsd-alpha@FreeBSD.ORG
Subject: postgresql on the alpha
In-Reply-To: <Pine.OSF.4.10.9906212021350.28278-100000@fly.HiWAAY.net>
Message-ID: <Pine.LNX.3.96.990627012009.17457B-100000@metzelkueche.tabu.uni-bonn.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
i'm working to get postgresql to work on the alpha.
By now i have a more-or-less working version of 6.5
up and running. It still fails some regression tests...
TAS asm stuff was a bit messy.
I do not send any diff yet because i messed up the source a bit :-)
Just wanted to ask if someone else is on that topic to share resources...
best regards,
--armin
PS: The current kernel detects all disks on my 2940UW but i cannot
access any...this normal ?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Sat Jun 26 19: 9:28 1999
Delivered-To: freebsd-alpha@freebsd.org
Received: from dingo.cdrom.com (castles527.castles.com [208.214.165.91])
by hub.freebsd.org (Postfix) with ESMTP id 1C18114E7D
for <freebsd-alpha@freebsd.org>; Sat, 26 Jun 1999 19:09:26 -0700 (PDT)
(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 QAA00454;
Sat, 26 Jun 1999 16:23:39 -0700 (PDT)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199906262323.QAA00454@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Peter Wemm <peter@netplex.com.au>
Cc: freebsd-alpha@freebsd.org
Subject: Re: AARGH!! "dead" Alpha 164SX (Was: Re: OK, any pointers on how to use SRM? :-))
In-reply-to: Your message of "Sat, 26 Jun 1999 17:43:14 +0800."
<19990626094314.68C0775@overcee.netplex.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 26 Jun 1999 16:23:39 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
>
> The next good question is.. what's up with softupdates? :-] Hmm.. say,
No idea. We were unhappy with it at Usenix too. Perhaps I should send
Kirk an Aplha?
> that NCR controller you gave me, is that the one that was screwing up on
> freefall by any chance?
Not as such, no.
--
\\ The mind's the standard \\ Mike Smith
\\ of the man. \\ msmith@freebsd.org
\\ -- Joseph Merrick \\ 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 Sat Jun 26 19:15: 6 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 9A26814EB7
for <freebsd-alpha@FreeBSD.ORG>; Sat, 26 Jun 1999 19:15:03 -0700 (PDT)
(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 TAA31757;
Sat, 26 Jun 1999 19:14:22 -0700
Date: Sat, 26 Jun 1999 19:12:25 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Mike Smith <mike@smith.net.au>
Cc: Peter Wemm <peter@netplex.com.au>, freebsd-alpha@FreeBSD.ORG
Subject: Re: AARGH!! "dead" Alpha 164SX (Was: Re: OK, any pointers on how to
use SRM? :-))
In-Reply-To: <199906262323.QAA00454@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.05.9906261911320.43763-100000@semuta.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
> >
> > The next good question is.. what's up with softupdates? :-] Hmm.. say,
>
> No idea. We were unhappy with it at Usenix too. Perhaps I should send
> Kirk an Aplha?
Soft updates have worked for me on an alpha.
>
> > that NCR controller you gave me, is that the one that was screwing up on
> > freefall by any chance?
>
> Not as such, no.
That's a very strange response. Makes me think of an Isaac Asimov story.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Sat Jun 26 21:48:12 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 E1B6414DE2
for <freebsd-alpha@FreeBSD.ORG>; Sat, 26 Jun 1999 21:48:02 -0700 (PDT)
(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 77EBD75; Sun, 27 Jun 1999 12:48:01 +0800 (WST)
(envelope-from peter@netplex.com.au)
X-Mailer: exmh version 2.0.2 2/24/98
To: Mike Smith <mike@smith.net.au>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: AARGH!! "dead" Alpha 164SX (Was: Re: OK, any pointers on how to use SRM? :-))
In-reply-to: Your message of "Sat, 26 Jun 1999 16:23:39 MST."
<199906262323.QAA00454@dingo.cdrom.com>
Date: Sun, 27 Jun 1999 12:48:01 +0800
From: Peter Wemm <peter@netplex.com.au>
Message-Id: <19990627044801.77EBD75@overcee.netplex.com.au>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Mike Smith wrote:
> >
> > The next good question is.. what's up with softupdates? :-] Hmm.. say,
>
> No idea. We were unhappy with it at Usenix too. Perhaps I should send
> Kirk an Aplha?
Heh. :-)
Todays excitement, on a kernel built after Kirk's changes:
panic: lockmgr: locking against myself
panic
Stopped at Debugger+0x2c: ldq ra,0(sp) <0xfffffe0005adda60> <ra=0xfffffc000046bfe0,sp=0xfffffe0005adda60>
db> trace
Debugger() at Debugger+0x2c
panic() at panic+0xf4
lockmgr() at lockmgr+0x340
cluster_wbuild() at cluster_wbuild+0x37c
cluster_write() at cluster_write+0x1f0
ffs_write() at ffs_write+0x474
vn_write() at vn_write+0x130
dofilewrite() at dofilewrite+0xc0
write() at write+0x54
syscall() at syscall+0x224
XentSys() at XentSys+0x50
(null)() at 0x1600c096c
db>
This has been happening pretty reliably after attempting to change a root
password.
> > that NCR controller you gave me, is that the one that was screwing up on
> > freefall by any chance?
>
> Not as such, no.
I take it that means: "Same type, not the same physical card", yes?
Cheers,
-Peter
--
Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message