From owner-freebsd-alpha Sun Mar 31 9:35:57 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mao.stokely.org (mao.stokely.org [65.84.64.228]) by hub.freebsd.org (Postfix) with ESMTP id 3A3A437B427 for ; Sun, 31 Mar 2002 09:35:42 -0800 (PST) Received: by mao.stokely.org (Postfix, from userid 2074) id F40994B669; Sun, 31 Mar 2002 09:35:41 -0800 (PST) Date: Sun, 31 Mar 2002 09:35:41 -0800 From: Murray Stokely To: freebsd-alpha@FreeBSD.org Subject: New 5.0-CURRENT / Alpha snapshot available Message-ID: <20020331173541.GO21906@freebsdmall.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2/5bycvrmDh4d1IB" Content-Disposition: inline User-Agent: Mutt/1.3.25i X-GPG-Key-ID: 1024D/0E451F7D X-GPG-Key-Fingerprint: E2CA 411D DD44 53FD BB4B 3CB5 B4D7 10A2 0E45 1F7D Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --2/5bycvrmDh4d1IB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I've uploaded a recent snapshot to ftp-master. The bits are available now from ftp2.freebsd.org, and the other mirrors should pick them up soon : /pub/FreeBSD/snapshots/alpha/5.0-20020330-SNAP /pub/FreeBSD/snapshots/alpha/ISO-IMAGES/5.0-20020330-SNAP-install.iso I've been running the results of this build for several days on 3 different machines without any problems. YMMV. - Murray --2/5bycvrmDh4d1IB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (SunOS) Comment: For info see http://www.gnupg.org iD4DBQE8p0jttNcQog5FH30RAhhZAJjgsFSU/GMfePIldPkUaiwgHJF+AKCkVBqv dE2wrNFDKu7Qg2sX72iNBw== =x2DF -----END PGP SIGNATURE----- --2/5bycvrmDh4d1IB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 31 20: 3:21 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from rahl.dorm.duke.edu (rahl.dorm.duke.edu [152.16.249.139]) by hub.freebsd.org (Postfix) with ESMTP id 59F1737B41F for ; Sun, 31 Mar 2002 20:03:19 -0800 (PST) Received: (from scott@localhost) by rahl.dorm.duke.edu (8.11.6/8.11.6) id g3143OL65779 for freebsd-alpha@FreeBSD.org; Sun, 31 Mar 2002 23:03:24 -0500 (EST) (envelope-from scott) Message-Id: <200204010403.g3143OL65779@rahl.dorm.duke.edu> Content-Type: text/plain; charset="iso-8859-1" From: Scott Sipe To: freebsd-alpha@FreeBSD.org Subject: Stable->Current Date: Sun, 31 Mar 2002 23:03:24 -0500 X-Mailer: KMail [version 1.3.2] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Are there any special steps that need to be taken to update an Alpha from -Stable to -Current (beyond what's in UPDATING)? thanks, Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Apr 1 2:33: 5 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from rahl.dorm.duke.edu (rahl.dorm.duke.edu [152.16.249.139]) by hub.freebsd.org (Postfix) with ESMTP id 3886137B417 for ; Mon, 1 Apr 2002 02:33:02 -0800 (PST) Received: (from scott@localhost) by rahl.dorm.duke.edu (8.11.6/8.11.6) id g31AXBV67235 for freebsd-alpha@freebsd.org; Mon, 1 Apr 2002 05:33:11 -0500 (EST) (envelope-from scott) Message-Id: <200204011033.g31AXBV67235@rahl.dorm.duke.edu> Content-Type: text/plain; charset="iso-8859-1" From: Scott Sipe To: freebsd-alpha@freebsd.org Subject: Problem with AS600 and network card Date: Mon, 1 Apr 2002 05:33:11 -0500 X-Mailer: KMail [version 1.3.2] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm running STABLE at present on an AS600 (this is Squall for Drew). It has two network cards, one that has a coaxial connector, the plug kind (AUI or something?) and a standard 10bt jack. This card also has SCSI stuff on it (it's de0). A second card is a digital (brand) NIC that is 10/100 and is de1. I had de0 disabled down, and de1 plugging directly into my wall jack (100bt). Then, I got an old Netgear 4 port hub (10mbps only) and plug de1 into it. Even if de1 is the only thing plugged into the hub the collision light comes on. If I plug my other FreeBSD computer into the hub, (and the hub uplinked to walljack), I can't access anything from either computer, or either computer from the internet. (also as a sidenote, whenever dhclient was running, it was giving Unaligned access errors). By switching the network connection to de0 all is well, the collision light goes off, and network access works. Any suggestions for why this is happening? I'm upgrading Squall to CURRENT right now, and will try again once that's done. thanks, Scott Sipe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Apr 1 2:56:47 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 2424B37B417 for ; Mon, 1 Apr 2002 02:56:43 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g31AueZ37389; Mon, 1 Apr 2002 12:56:40 +0200 (CEST) (envelope-from wkb) Date: Mon, 1 Apr 2002 12:56:39 +0200 From: Wilko Bulte To: Scott Sipe Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Stable->Current Message-ID: <20020401125639.A37363@freebie.xs4all.nl> References: <200204010403.g3143OL65779@rahl.dorm.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200204010403.g3143OL65779@rahl.dorm.duke.edu>; from cscotts@mindspring.com on Sun, Mar 31, 2002 at 11:03:24PM -0500 X-OS: FreeBSD 4.5-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, Mar 31, 2002 at 11:03:24PM -0500, Scott Sipe wrote: No, not in my experience at least. > Are there any special steps that need to be taken to update an Alpha from > -Stable to -Current (beyond what's in UPDATING)? > > thanks, > Scott > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message ---end of quoted text--- -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands We are FreeBSD. Resistance is futile. Prepare to be committed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Apr 1 6: 3:41 2002 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 07EB737B41E for ; Mon, 1 Apr 2002 06:03:33 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA26210; Mon, 1 Apr 2002 09:03:32 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g31E32Q91269; Mon, 1 Apr 2002 09:03:02 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15528.26774.310260.978924@grasshopper.cs.duke.edu> Date: Mon, 1 Apr 2002 09:03:02 -0500 (EST) To: Scott Sipe Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Problem with AS600 and network card In-Reply-To: <200204011033.g31AXBV67235@rahl.dorm.duke.edu> References: <200204011033.g31AXBV67235@rahl.dorm.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Scott Sipe writes: > I had de0 disabled down, and de1 plugging directly into my wall jack (100bt). > Then, I got an old Netgear 4 port hub (10mbps only) and plug de1 into it. > Even if de1 is the only thing plugged into the hub the collision light comes > on. If I plug my other FreeBSD computer into the hub, (and the hub uplinked > to walljack), I can't access anything from either computer, or either > computer from the internet. (also as a sidenote, whenever dhclient was > running, it was giving Unaligned access errors). > These machines were originally configured with ancient synoptics 100Mb switches built before there was a 100Mb autoneg standard. Very few things would autoneg with them, so I hardcoded everything to 100Mb/full duplex in the SRM console on all the old machines. Since FreeBSD obeys the SRM console's duplex settings for tulip nics, it may have that setting hardcoded as well & be refusing to autosense 10Mb with your 10Mb hub. Try setting the ewa1_mode to "auto". (its probably at FastFD now). If that doesn't work, back it down to 10mb (I think its called "twisted"). Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Apr 1 6:47:19 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id F232E37B417 for ; Mon, 1 Apr 2002 06:47:14 -0800 (PST) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 16s35V-0005IG-00; Mon, 1 Apr 2002 16:47:13 +0200 Received: from kemoauc.mips.inka.de (localhost [127.0.0.1]) by kemoauc.mips.inka.de (8.12.2/8.12.2) with ESMTP id g31EkDiM098029 for ; Mon, 1 Apr 2002 16:46:13 +0200 (CEST) (envelope-from mailnull@localhost.mips.inka.de) Received: (from mailnull@localhost) by kemoauc.mips.inka.de (8.12.2/8.12.2/Submit) id g31EkDTf098028 for freebsd-alpha@freebsd.org; Mon, 1 Apr 2002 16:46:13 +0200 (CEST) (envelope-from mailnull) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Source of "processor correctable error"? Date: Mon, 1 Apr 2002 14:46:13 +0000 (UTC) Message-ID: Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Since the weekend my PC164 has taken to almost continuously spewing gobs of Warning: received processor correctable error. In fact I first noticed this because writing the error messages to the serial console took so much time the machine became sluggish. I've switched to a graphics console now. Anyway, is there a way to narrow down the source of the underlying hardware problem? What are the candidates anyway? On-chip cache, off-chip cache, main memory? The machine has eight SIMMs (for a total of 256M). I guess, I'll start by taking out half (and setting the memory width back to 128 bits) and see whether this has any effect. Suggestions? -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Apr 1 7:24: 3 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id 17FEB37B41D for ; Mon, 1 Apr 2002 07:23:50 -0800 (PST) Received: (from uucp@localhost) by srv1.cosmo-project.de (8.11.6/8.11.6) with UUCP id g31FNkk38754; Mon, 1 Apr 2002 17:23:47 +0200 (CEST) (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.1.10]) by cicely5.cicely.de (8.12.1/8.12.1) with ESMTP id g31FMm6e071321; Mon, 1 Apr 2002 17:22:49 +0200 (CEST)?g (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (localhost [127.0.0.1]) by cicely8.cicely.de (8.12.2/8.12.2) with ESMTP id g31FMlnU041834; Mon, 1 Apr 2002 17:22:48 +0200 (CEST) (envelope-from ticso@cicely8.cicely.de) Received: (from ticso@localhost) by cicely8.cicely.de (8.12.2/8.12.2/Submit) id g31FMkur041833; Mon, 1 Apr 2002 17:22:47 +0200 (CEST) Date: Mon, 1 Apr 2002 17:22:44 +0200 From: Bernd Walter To: Christian Weisgerber Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Source of "processor correctable error"? Message-ID: <20020401152244.GE41357@cicely8.cicely.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.26i X-Operating-System: FreeBSD cicely8.cicely.de 5.0-CURRENT i386 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Apr 01, 2002 at 02:46:13PM +0000, Christian Weisgerber wrote: > Since the weekend my PC164 has taken to almost continuously spewing > gobs of > > Warning: received processor correctable error. These are most likely main memory errors. > In fact I first noticed this because writing the error messages to > the serial console took so much time the machine became sluggish. > I've switched to a graphics console now. > > Anyway, is there a way to narrow down the source of the underlying > hardware problem? What are the candidates anyway? On-chip cache, > off-chip cache, main memory? > > The machine has eight SIMMs (for a total of 256M). I guess, I'll > start by taking out half (and setting the memory width back to 128 > bits) and see whether this has any effect. It's a good start. You might also remove and reinsert the simms as the contacts get bad over time. If you can get such an error while in SRM it will print you a more usefull message. Theoreticaly you could get the simm slot number but FreeBSD doesn't support it because there is no documentation for most boards. Well the PC164 as an OEM board has a better documentation so it may worth to think about implementing such a feature. I often thought about hacking this board as the chipset could handle up to 8G memory with 16 banks while the board only can do with up to 512M in a single bank. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Apr 1 7:29:29 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 3990437B419 for ; Mon, 1 Apr 2002 07:29:08 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g31FT5U38122; Mon, 1 Apr 2002 17:29:05 +0200 (CEST) (envelope-from wkb) Date: Mon, 1 Apr 2002 17:29:05 +0200 From: Wilko Bulte To: Christian Weisgerber Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Source of "processor correctable error"? Message-ID: <20020401172905.A38101@freebie.xs4all.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from naddy@mips.inka.de on Mon, Apr 01, 2002 at 02:46:13PM +0000 X-OS: FreeBSD 4.5-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Apr 01, 2002 at 02:46:13PM +0000, Christian Weisgerber wrote: > Since the weekend my PC164 has taken to almost continuously spewing > gobs of > > Warning: received processor correctable error. > > In fact I first noticed this because writing the error messages to > the serial console took so much time the machine became sluggish. > I've switched to a graphics console now. > > Anyway, is there a way to narrow down the source of the underlying > hardware problem? What are the candidates anyway? On-chip cache, > off-chip cache, main memory? Main memory would be my #1 guess. -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands We are FreeBSD. Resistance is futile. Prepare to be committed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Apr 1 9:31: 0 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id D7ECE37B41E for ; Mon, 1 Apr 2002 09:30:40 -0800 (PST) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 16s5df-0004Fj-00; Mon, 1 Apr 2002 19:30:39 +0200 Received: from kemoauc.mips.inka.de (localhost [127.0.0.1]) by kemoauc.mips.inka.de (8.12.2/8.12.2) with ESMTP id g31HJAiY000650 for ; Mon, 1 Apr 2002 19:19:10 +0200 (CEST) (envelope-from mailnull@localhost.mips.inka.de) Received: (from mailnull@localhost) by kemoauc.mips.inka.de (8.12.2/8.12.2/Submit) id g31HJA1t000649 for freebsd-alpha@freebsd.org; Mon, 1 Apr 2002 19:19:10 +0200 (CEST) (envelope-from mailnull) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: Source of "processor correctable error"? Date: Mon, 1 Apr 2002 17:19:09 +0000 (UTC) Message-ID: References: <20020401152244.GE41357@cicely8.cicely.de> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Bernd Walter wrote: > If you can get such an error while in SRM it will print you a more > usefull message. Unfortunately I don't. I get errors all the way through shutdown, but the moment control is passed back to SRM they stop. SRM has a memtest command, but it complains that address 0 is an invalid zone, and I have no idea what address range to specify. memtest says I should consult the dynamic command, but the output of that one looks like a range of memory SRM uses. Well, we'll see what the SIMM shuffling produces. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Apr 1 10: 0:15 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from web14506.mail.yahoo.com (web14506.mail.yahoo.com [216.136.224.69]) by hub.freebsd.org (Postfix) with SMTP id 1A20537B419 for ; Mon, 1 Apr 2002 10:00:10 -0800 (PST) Message-ID: <20020401180009.70772.qmail@web14506.mail.yahoo.com> Received: from [198.95.226.224] by web14506.mail.yahoo.com via HTTP; Mon, 01 Apr 2002 10:00:09 PST Date: Mon, 1 Apr 2002 10:00:09 -0800 (PST) From: Jeffrey Katcher Subject: Where is linux-base and/or ccc? To: freebsd-alpha@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Someone made me an offer I couldn't refuse on an XP1000. While I like Tru64, the installation on my machine had its authorization codes messed up and life's too short for vendor license debugging. I happily installed FreeBSD (4.5-RELEASE cvsupped to STABLE), but can't seem to find either linux_base (6.1 or 7) on any mirror site much less the ccc package. Where are these located? Many thanks in advance, Jeff Katcher jmkatcher @ yahoo . com __________________________________________________ Do You Yahoo!? Yahoo! Greetings - send holiday greetings for Easter, Passover http://greetings.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Apr 1 10:24:35 2002 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 69C6537B42C for ; Mon, 1 Apr 2002 10:24:10 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA05225; Mon, 1 Apr 2002 13:24:09 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g31INdb91589; Mon, 1 Apr 2002 13:23:39 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15528.42411.730440.132295@grasshopper.cs.duke.edu> Date: Mon, 1 Apr 2002 13:23:39 -0500 (EST) To: Jeffrey Katcher Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Where is linux-base and/or ccc? In-Reply-To: <20020401180009.70772.qmail@web14506.mail.yahoo.com> References: <20020401180009.70772.qmail@web14506.mail.yahoo.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Jeffrey Katcher writes: > Someone made me an offer I couldn't refuse on an > XP1000. While I like Tru64, the installation on my > machine had its authorization codes messed up and > life's too short for vendor license debugging. > > I happily installed FreeBSD (4.5-RELEASE cvsupped to > STABLE), but can't seem to find either linux_base (6.1 > or 7) on any mirror site much less the ccc package. > > Where are these located? Install ports & build the port for each. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Apr 1 15:19:29 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from harrier.prod.itd.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12]) by hub.freebsd.org (Postfix) with ESMTP id 7834937B417 for ; Mon, 1 Apr 2002 15:19:19 -0800 (PST) Received: from pool0467.cvx40-bradley.dialup.earthlink.net ([216.244.43.212] helo=mindspring.com) by harrier.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16sB52-0007Dh-00; Mon, 01 Apr 2002 15:19:17 -0800 Message-ID: <3CA8EADE.C11C8DF7@mindspring.com> Date: Mon, 01 Apr 2002 15:18:54 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Christian Weisgerber Cc: freebsd-alpha@freebsd.org Subject: Re: Source of "processor correctable error"? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Christian Weisgerber wrote: > > Since the weekend my PC164 has taken to almost continuously spewing > gobs of > > Warning: received processor correctable error. > > In fact I first noticed this because writing the error messages to > the serial console took so much time the machine became sluggish. > I've switched to a graphics console now. > > Anyway, is there a way to narrow down the source of the underlying > hardware problem? What are the candidates anyway? On-chip cache, > off-chip cache, main memory? FWIW, if they are correctable, it's complaining about memory errors which are correctable using the ECC bits, in the use of ECC memory. There are generally three causes of this problem which I have seen in natures: 1) Thermal cooling of the system is insufficient, which introduces thermal related errors (fix: better cooling). 2) The memory was being clocked faster than the speed it was rated to run at (fix: clock it slower or buy more expensive memory). 3) The "ECC" memory was face ECC instead of real ECC, so the correction codes were incorrect, either as a result of a cheap vendor ripping a buyer off, or a cheap buyer not jumpering the system to not use ECC... or the system not having the option to be jumpered that way (fix: use real ECC memory, and not forgeries). It's always possible that you have bad RAM, or that the PCI bus-on time is set to high in the PCI chipset for the amount of rAM in the system, such that the DRAM referesh is delayed enough under load that your memory starts losing bits, Etc.. But while there are other possibilities, I have never seen them personally in nature (with ECC; I've seen the DRAM refresh starvation with an improperly BIOS programmed Cyrix Media GX chipset [5532?]). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Apr 1 16:30:28 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id 0430B37B41A for ; Mon, 1 Apr 2002 16:30:24 -0800 (PST) Received: (from uucp@localhost) by srv1.cosmo-project.de (8.11.6/8.11.6) with UUCP id g320UKg47414; Tue, 2 Apr 2002 02:30:20 +0200 (CEST) (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.1.10]) by cicely5.cicely.de (8.12.1/8.12.1) with ESMTP id g320N76e075852; Tue, 2 Apr 2002 02:23:07 +0200 (CEST)?g (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (localhost [127.0.0.1]) by cicely8.cicely.de (8.12.2/8.12.2) with ESMTP id g320N7nU043042; Tue, 2 Apr 2002 02:23:07 +0200 (CEST) (envelope-from ticso@cicely8.cicely.de) Received: (from ticso@localhost) by cicely8.cicely.de (8.12.2/8.12.2/Submit) id g320N5UK043041; Tue, 2 Apr 2002 02:23:05 +0200 (CEST) Date: Tue, 2 Apr 2002 02:23:04 +0200 From: Bernd Walter To: Terry Lambert Cc: Christian Weisgerber , freebsd-alpha@FreeBSD.ORG Subject: Re: Source of "processor correctable error"? Message-ID: <20020402002303.GH41357@cicely8.cicely.de> References: <3CA8EADE.C11C8DF7@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3CA8EADE.C11C8DF7@mindspring.com> User-Agent: Mutt/1.3.26i X-Operating-System: FreeBSD cicely8.cicely.de 5.0-CURRENT i386 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Apr 01, 2002 at 03:18:54PM -0800, Terry Lambert wrote: > Christian Weisgerber wrote: > > > > Since the weekend my PC164 has taken to almost continuously spewing > > gobs of > > > > Warning: received processor correctable error. > > > > In fact I first noticed this because writing the error messages to > > the serial console took so much time the machine became sluggish. > > I've switched to a graphics console now. > > > > Anyway, is there a way to narrow down the source of the underlying > > hardware problem? What are the candidates anyway? On-chip cache, > > off-chip cache, main memory? > > FWIW, if they are correctable, it's complaining about memory > errors which are correctable using the ECC bits, in the use of > ECC memory. Right - it also hasn't to be main memory as D, I and B caches and some data paths are ECC protected too. But I never saw a message about cache failures so they might look different. > There are generally three causes of this problem which I have > seen in natures: > > 1) Thermal cooling of the system is insufficient, which > introduces thermal related errors (fix: better cooling). Possible, but I would first guess in bad simm or bad contact. > 2) The memory was being clocked faster than the speed it > was rated to run at (fix: clock it slower or buy more > expensive memory). Unlikely as overclocked memory tend to multibit errors in my expirience. > 3) The "ECC" memory was face ECC instead of real ECC, so > the correction codes were incorrect, either as a result > of a cheap vendor ripping a buyer off, or a cheap buyer > not jumpering the system to not use ECC... or the system > not having the option to be jumpered that way (fix: use > real ECC memory, and not forgeries). Beleave me - these boards don't let you even boot with such a kind of ram as you never get a chance to come over SRM because of all those error messages. I can speak from expirience here as I had an unsoldered pin on a simm which my stupid x86 box silently corrected for years... > It's always possible that you have bad RAM, or that the PCI > bus-on time is set to high in the PCI chipset for the amount > of rAM in the system, such that the DRAM referesh is delayed > enough under load that your memory starts losing bits, Etc.. I doubt that this is a refresh problem, as the chipset has well designed datapaths. > But while there are other possibilities, I have never seen them > personally in nature (with ECC; I've seen the DRAM refresh > starvation with an improperly BIOS programmed Cyrix Media GX > chipset [5532?]). Phew that's bad. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Apr 1 22: 6:15 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 467D237B416 for ; Mon, 1 Apr 2002 22:06:08 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g32663h41675; Tue, 2 Apr 2002 08:06:03 +0200 (CEST) (envelope-from wkb) Date: Tue, 2 Apr 2002 08:06:03 +0200 From: Wilko Bulte To: Terry Lambert Cc: Christian Weisgerber , freebsd-alpha@FreeBSD.ORG Subject: Re: Source of "processor correctable error"? Message-ID: <20020402080603.D41537@freebie.xs4all.nl> References: <3CA8EADE.C11C8DF7@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3CA8EADE.C11C8DF7@mindspring.com>; from tlambert2@mindspring.com on Mon, Apr 01, 2002 at 03:18:54PM -0800 X-OS: FreeBSD 4.5-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Apr 01, 2002 at 03:18:54PM -0800, Terry Lambert wrote: > Christian Weisgerber wrote: > > Since the weekend my PC164 has taken to almost continuously spewing > > gobs of > > > > Warning: received processor correctable error. > > > > In fact I first noticed this because writing the error messages to > > the serial console took so much time the machine became sluggish. > > I've switched to a graphics console now. > > > > Anyway, is there a way to narrow down the source of the underlying > > hardware problem? What are the candidates anyway? On-chip cache, > > off-chip cache, main memory? > > FWIW, if they are correctable, it's complaining about memory > errors which are correctable using the ECC bits, in the use of > ECC memory. The PC164 has ECC throughout, also on the caches etc. > There are generally three causes of this problem which I have > seen in natures: > > 1) Thermal cooling of the system is insufficient, which > introduces thermal related errors (fix: better cooling). Possible. I've seen a overheating Alpha CPU do warped things. > 3) The "ECC" memory was face ECC instead of real ECC, so > the correction codes were incorrect, either as a result > of a cheap vendor ripping a buyer off, or a cheap buyer > not jumpering the system to not use ECC... or the system > not having the option to be jumpered that way (fix: use > real ECC memory, and not forgeries). Fake parity won't even allow you to get a SRM console prompt on Alphas who need ECC. They want the real stuff. > It's always possible that you have bad RAM, or that the PCI > bus-on time is set to high in the PCI chipset for the amount > of rAM in the system, such that the DRAM referesh is delayed > enough under load that your memory starts losing bits, Etc.. Alphas don't allow you to figgle with this in the BIOS as they don't have a BIOS setup like that :) -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands We are FreeBSD. Resistance is futile. Prepare to be committed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Apr 1 22:38:15 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from aromo.spock.cl (aromo.spock.cl [200.27.125.98]) by hub.freebsd.org (Postfix) with ESMTP id 90B0837B417 for ; Mon, 1 Apr 2002 22:38:05 -0800 (PST) Received: from aromo.spock.cl (aromo.spock.cl [200.27.125.98]) by aromo.spock.cl (8.11.1/8.9.3) with ESMTP id g326bwa78502 for ; Tue, 2 Apr 2002 02:37:58 -0400 (CLT) Date: Tue, 2 Apr 2002 02:37:58 -0400 (CLT) From: Roberto de Iriarte To: freebsd-alpha@FreeBSD.org Subject: Alphaserver 2100A success with 4.5-Release and GCC whoes. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Dear FreeBSD-ers Just wanted to let you know that 4.5-Release installs and runs perfectly on the much discredited AS2100A (aka Lynx) Stability and performance running apache with mod-ssl, php, mysql 4 and postgresql 7.2 has been exellent so far. Owners of simmilar machines will be well served by this release Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.5-RELEASE #0: Tue Jan 29 07:52:50 GMT 2002 murray@axpbuilder.freebsdmall.com:/usr/src/sys/compile/GENERIC DEC AlphaServer 2100A AlphaServer 2100A 5/375, 374MHz 8192 byte page size, 1 processor. CPU: EV56 (21164A) major=7 minor=1 extensions=0x1 OSF PAL rev: 0x4000100020116 real memory = 1071570944 (1046456K bytes) avail memory = 1036943360 (1012640K bytes) Preloaded elf kernel "kernel" at 0xfffffc00007bc000. md0: Malloc disk t20: using interrupt type 1 on pci bus 0 pci0: on pcib0 isab0: at device 2.0 on pci0 isa0: on isab0 pcib1: at device 3.0 on pci0 pci2: on pcib1 sym0: <810a> port 0x5000-0x50ff mem 0x81040000-0x810400ff irq 28 at device 1.0 on pci2 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking dc0: port 0x5400-0x547f mem 0x81040100-0x8104017f irq 48 at device 6.0 on pci2 dc0: Ethernet address: 00:00:f8:1f:f6:2a miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto mlx0: port 0x10000-0x1007f irq 32 at device 6.0 on pci0 mlx0: DAC960P/PD, 1 channel, firmware 2.73-0-00, 16MB RAM mlxd0: on mlx0 mlxd0: on mlx0 mlxd0: 12042MB (24662016 sectors) RAID 5 (online) pci0: (vendor=0x0000, dev=0x0000) at 12.0 irq 0 pci0: (vendor=0x0000, dev=0x0000) at 12.4 pci0: (vendor=0x0000, dev=0x0000) at 13.0 irq 0 pci0: (vendor=0x0000, dev=0x0000) at 13.4 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 mcclock0: at port 0x70-0x71 on isa0 sio0: configured irq 4 not in bitmap of probed irqs 0x1 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A, console sio1: reserved for low-level i/o ppc0: at port 0x3bc-0x3c3 irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: cannot reserve interrupt, failed. lpt0: on ppbus0 lpt0: Polled port ppi0: on ppbus0 Timecounter "alpha" frequency 374662600 Hz Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/mlxd0a On a completely unrelated subject that might be of interest to Andrew i've been doing some experiments with DRM for an ATI Rage 128 on linux, that worked exellently on an AS800 with a 500Mhz 21164a, but only if the modules where compiled with -O -mcpu=ev56, -O2 -mcpu=ev56 locking the machine completely. So, it seems the problems are not completely alleviated by -mcpu=ev56. Regards. Thanks for all the good work Roberto To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 2 0:20:14 2002 Delivered-To: freebsd-alpha@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E00FD37B41C for ; Tue, 2 Apr 2002 00:20:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g328K4621542; Tue, 2 Apr 2002 00:20:04 -0800 (PST) (envelope-from gnats) Date: Tue, 2 Apr 2002 00:20:04 -0800 (PST) Message-Id: <200204020820.g328K4621542@freefall.freebsd.org> To: freebsd-alpha@FreeBSD.org Cc: From: Loren James Rittle Subject: Re: alpha/36327: trap within cvt() while attempting to printf() an FP number Reply-To: Loren James Rittle Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR alpha/36327; it has been noted by GNATS. From: Loren James Rittle To: gallatin@cs.duke.edu Cc: ljrittle@freebsd.org, freebsd-gnats-submit@freebsd.org Subject: Re: alpha/36327: trap within cvt() while attempting to printf() an FP number Date: Tue, 2 Apr 2002 02:13:21 -0600 (CST) > I beleive this only works for floating point operations which have > software completion enabled. Eg, -mieee. OK. > Have you tried adding -mieee to CFLAGS? Yes, I see that I failed to report it, but I did try the test case with -mieee and without it. As far as I can see, the mechanism documented to disable underflow traps is not working on alpha*-*-freebsd4.2 or alpha*-*-freebsd5.0 OR there is a bug in the handling of some FP numbers in cvt() which causes a non-maskable FP trap. Sorry I should have posted a complete example. Here is one that fails: ; cat tq.c #include #include #include main() { double d = DBL_MIN; fpsetmask(0); printf (" = %.17g;\n", d); printf (" = %.17g;\n", d/10); printf (" = %.17g;\n", (DBL_MIN/10)*10); printf (" = %.17g;\n", (DBL_MIN/10)); } ; /usr/bin/gcc -mieee tq.c ; a.out = 2.2250738585072014e-308; floating point exception--core dumped Exact same output when compiled without -mieee. In any event, it is not the code for d/10 that traps. It is code inside cvt() which is called from vfprintf(). Two issues: Should a library routine ever internally trap; no matter what the mask setting? Shouldn't there be some way to disable the trap? Regards, Loren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 2 1:25:42 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from gnah.bolet.org (gnah.bolet.org [80.65.226.87]) by hub.freebsd.org (Postfix) with ESMTP id 5F15837B425 for ; Tue, 2 Apr 2002 01:25:33 -0800 (PST) Received: (from pornin@localhost) by gnah.bolet.org (8.11.6/8.11.6) id g329PT406366 for freebsd-alpha@FreeBSD.ORG; Tue, 2 Apr 2002 11:25:29 +0200 (CEST) (envelope-from pornin) Date: Tue, 2 Apr 2002 11:25:28 +0200 From: Thomas Pornin To: freebsd-alpha@FreeBSD.ORG Subject: Re: Source of "processor correctable error"? Message-ID: <20020402112528.A6188@gnah.bolet.org> References: <3CA8EADE.C11C8DF7@mindspring.com> <20020402002303.GH41357@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20020402002303.GH41357@cicely8.cicely.de>; from ticso@cicely8.cicely.de on Tue, Apr 02, 2002 at 02:23:04AM +0200 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Apr 02, 2002 at 02:23:04AM +0200, Bernd Walter wrote: > Right - it also hasn't to be main memory as D, I and B caches > and some data paths are ECC protected too. For what it's worth: one of the Multia box I once owned died with such "correctable errors". Those would appear upon booting an OS, but SRM was juste fine. There was an error code displayed with the error message; after some in-depth searching through technical documentations and mailing-lists, it turned out to be an error inside the TLB, which is pretty bad since it is inside the CPU. Since the messages would appear at a very high rate, booting would take forever (especially since I had to use a serial console). --Thomas Pornin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 2 3:10:44 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id 6221737B419 for ; Tue, 2 Apr 2002 03:10:37 -0800 (PST) Received: (from uucp@localhost) by srv1.cosmo-project.de (8.11.6/8.11.6) with UUCP id g32BAUI57663; Tue, 2 Apr 2002 13:10:31 +0200 (CEST) (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.1.10]) by cicely5.cicely.de (8.12.1/8.12.1) with ESMTP id g32B4T6e080385; Tue, 2 Apr 2002 13:04:29 +0200 (CEST)?g (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (localhost [127.0.0.1]) by cicely8.cicely.de (8.12.2/8.12.2) with ESMTP id g32B4SnU044595; Tue, 2 Apr 2002 13:04:29 +0200 (CEST) (envelope-from ticso@cicely8.cicely.de) Received: (from ticso@localhost) by cicely8.cicely.de (8.12.2/8.12.2/Submit) id g32B4McH044594; Tue, 2 Apr 2002 13:04:22 +0200 (CEST) Date: Tue, 2 Apr 2002 13:04:21 +0200 From: Bernd Walter To: Thomas Pornin Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Source of "processor correctable error"? Message-ID: <20020402110420.GI41357@cicely8.cicely.de> References: <3CA8EADE.C11C8DF7@mindspring.com> <20020402002303.GH41357@cicely8.cicely.de> <20020402112528.A6188@gnah.bolet.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020402112528.A6188@gnah.bolet.org> User-Agent: Mutt/1.3.26i X-Operating-System: FreeBSD cicely8.cicely.de 5.0-CURRENT i386 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Apr 02, 2002 at 11:25:28AM +0200, Thomas Pornin wrote: > On Tue, Apr 02, 2002 at 02:23:04AM +0200, Bernd Walter wrote: > > Right - it also hasn't to be main memory as D, I and B caches > > and some data paths are ECC protected too. > > For what it's worth: one of the Multia box I once owned died with such > "correctable errors". Those would appear upon booting an OS, but SRM was > juste fine. There was an error code displayed with the error message; > after some in-depth searching through technical documentations and > mailing-lists, it turned out to be an error inside the TLB, which is > pretty bad since it is inside the CPU. Since the messages would appear > at a very high rate, booting would take forever (especially since I had > to use a serial console). A Multia is very different from a PC164. CPU overheating and breaking is not uncommon for LCA based systems like Multias. Btw.: At least some if not all Multias have powermanagement features. If anyone is willing to test a -current patch I will implement it. You need a Multia or NoName with an 21066A CPU. Be aware that NoNames are usualy shiped (e.g. mine) with plain 21066 CPUs which don't have these features. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 2 3:17: 0 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mta03.mail.mel.aone.net.au (mta03.mail.au.uu.net [203.2.192.83]) by hub.freebsd.org (Postfix) with ESMTP id 77DDE37B416 for ; Tue, 2 Apr 2002 03:16:56 -0800 (PST) Received: from becca ([63.34.224.2]) by mta03.mail.mel.aone.net.au with SMTP id <20020402111654.EUXK12296.mta03.mail.mel.aone.net.au@becca> for ; Tue, 2 Apr 2002 21:16:54 +1000 Message-ID: <00d801c1da37$50e313c0$0b64a8c0@becca> From: "Rob B" To: References: <3CA8EADE.C11C8DF7@mindspring.com> <20020402002303.GH41357@cicely8.cicely.de> <20020402112528.A6188@gnah.bolet.org> <20020402110420.GI41357@cicely8.cicely.de> Subject: Re: Source of "processor correctable error"? Date: Tue, 2 Apr 2002 21:12:44 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org ----- Original Message ----- From: "Bernd Walter" To: "Thomas Pornin" Cc: Sent: Tuesday, April 02, 2002 9:04 PM Subject: Re: Source of "processor correctable error"? > Btw.: > At least some if not all Multias have powermanagement features. > If anyone is willing to test a -current patch I will implement it. > You need a Multia or NoName with an 21066A CPU. > Be aware that NoNames are usualy shiped (e.g. mine) with plain 21066 > CPUs which don't have these features. When I get my Multia nettbooting and running root-over-nfs, I'll give this a whirl! Speaking of which, has anyone had a setup like this? I want to do it this way - netboot the OS, run a read-only filesystem over NFS and log to a remote syslog host. I'm trying to get Linux happening, but this isn't going too well, and since one of my other Alpha's runs FreeBSD, I'll give that a whirl ... or mabey OpenBSD so many choices, so little time :) Cheers, Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 2 3:32:22 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from gnah.bolet.org (gnah.bolet.org [80.65.226.87]) by hub.freebsd.org (Postfix) with ESMTP id 5AAD837B41A for ; Tue, 2 Apr 2002 03:32:17 -0800 (PST) Received: (from pornin@localhost) by gnah.bolet.org (8.11.6/8.11.6) id g32BW9Y06640; Tue, 2 Apr 2002 13:32:09 +0200 (CEST) (envelope-from pornin) Date: Tue, 2 Apr 2002 13:32:08 +0200 From: Thomas Pornin To: Rob B Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Source of "processor correctable error"? Message-ID: <20020402133207.A6601@gnah.bolet.org> References: <3CA8EADE.C11C8DF7@mindspring.com> <20020402002303.GH41357@cicely8.cicely.de> <20020402112528.A6188@gnah.bolet.org> <20020402110420.GI41357@cicely8.cicely.de> <00d801c1da37$50e313c0$0b64a8c0@becca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <00d801c1da37$50e313c0$0b64a8c0@becca>; from rbyrnes@ozemail.com.au on Tue, Apr 02, 2002 at 09:12:44PM +1000 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Apr 02, 2002 at 09:12:44PM +1000, Rob B wrote: > When I get my Multia nettbooting and running root-over-nfs, I'll give this a > whirl! > > Speaking of which, has anyone had a setup like this? I have never done root-over-nfs, but I netbooted several times two Multia boxes. It was when 4.0 was actually -CURRENT in early stages. The floppy drive was dead. At that time, I could *not* netboot neither FreeBSD, NetBSD nor OpenBSD. The usual FAQs said that the SRM was too old. However, I could netboot Linux on the same boxes. This way, I could have a minimal OS and dump the contents of the boot disk on the internal hard drive (a raw byte by byte write, no partition table nor disklabel stuff). Then I could boot on the disk as if I had booted a floppy. The NetBSD and FreeBSD install programs were smart enough not to believe the floppy disklabel that was on the hard disk, and detected the right disk geometry. OpenBSD fumbled, however, and I had to enter that geometry by hand. It is quite possible that the netbooting code has been reviewed since. Or maybe my SRM was indeed too old, and a new version would have set things aright. > I'll give that a whirl ... or maybe OpenBSD Back to when I did my testing, OpenBSD was not a real option, due to lack of shared libraries. It seems that the newest release has shared libraries, though. You might try NetBSD as well. It has the longest history of Alpha support, among the "free unices". --Thomas Pornin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 2 6:15:55 2002 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 ABAE337B419 for ; Tue, 2 Apr 2002 06:15:46 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA03861; Tue, 2 Apr 2002 09:15:19 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g32EEnI93684; Tue, 2 Apr 2002 09:14:49 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15529.48345.376711.770341@grasshopper.cs.duke.edu> Date: Tue, 2 Apr 2002 09:14:49 -0500 (EST) To: rittle@labs.mot.com Cc: freebsd-alpha@freebsd.org Subject: Re: alpha/36327: trap within cvt() while attempting to printf() an FP number In-Reply-To: <200204020813.g328DLq66977@latour.rsch.comm.mot.com> References: <200203260906.g2Q962l84742@freefall.freebsd.org> <15520.33765.216885.639741@grasshopper.cs.duke.edu> <200204020813.g328DLq66977@latour.rsch.comm.mot.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Loren James Rittle writes: > > In any event, it is not the code for d/10 that traps. It is code > inside cvt() which is called from vfprintf(). Two issues: Should a > library routine ever internally trap; no matter what the mask setting? > Shouldn't there be some way to disable the trap? There is currently no way to disable the trap for routines which are not compiled with -mieee. The library is not compiled with -mieee, so even if you don't get the trap in your code, you may get the trap in a library. (I compile my libm with -mieee so that Konqueror doesn't crash with FPE's on poorly written javascript code, its worth the slowdown. Patch appended.) Ross Harvey over at NetBSD seems to have implemented something which optionally allows software completion to happen on instructions without the software completion flag set. I'm not sure if we could do this. Doug, what do you think? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 2 6:17:47 2002 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 DC73637B41D for ; Tue, 2 Apr 2002 06:17:32 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA03911; Tue, 2 Apr 2002 09:17:32 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g32EH2c93690; Tue, 2 Apr 2002 09:17:02 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15529.48477.957312.781154@grasshopper.cs.duke.edu> Date: Tue, 2 Apr 2002 09:17:01 -0500 (EST) To: Roberto de Iriarte Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Alphaserver 2100A success with 4.5-Release and GCC whoes. In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Roberto de Iriarte writes: > > Just wanted to let you know that 4.5-Release installs and runs > perfectly on the much discredited AS2100A (aka Lynx) Cool. I'm glad to hear it! <..> > On a completely unrelated subject that might be of interest to Andrew > i've been doing some experiments with DRM for an ATI Rage 128 on linux, > that worked exellently on an AS800 with a 500Mhz 21164a, but only if the > modules where compiled with -O -mcpu=ev56, -O2 -mcpu=ev56 locking the > machine completely. So, it seems the problems are not completely > alleviated by -mcpu=ev56. That's too bad. Well, its a good thing our compiler spits out: cc1: warning: *** *** The -O2 flag TRIGGERS KNOWN OPTIMIZER BUGS ON THIS PLATFORM *** Have you managed to build DRM on FreeBSD/alpha? What is DRM, anyway? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 2 7:15:27 2002 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 ABC3337B405 for ; Tue, 2 Apr 2002 07:15:22 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA05825; Tue, 2 Apr 2002 10:15:22 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g32FEq093770; Tue, 2 Apr 2002 10:14:52 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15529.51948.89157.959573@grasshopper.cs.duke.edu> Date: Tue, 2 Apr 2002 10:14:52 -0500 (EST) To: rittle@labs.mot.com Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: alpha/36327: trap within cvt() while attempting to printf() an FP number In-Reply-To: <15529.48345.376711.770341@grasshopper.cs.duke.edu> References: <200203260906.g2Q962l84742@freefall.freebsd.org> <15520.33765.216885.639741@grasshopper.cs.duke.edu> <200204020813.g328DLq66977@latour.rsch.comm.mot.com> <15529.48345.376711.770341@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Andrew Gallatin writes: > > Loren James Rittle writes: > > > > In any event, it is not the code for d/10 that traps. It is code > > inside cvt() which is called from vfprintf(). Two issues: Should a > > library routine ever internally trap; no matter what the mask setting? > > Shouldn't there be some way to disable the trap? > > There is currently no way to disable the trap for routines which are > not compiled with -mieee. The library is not compiled with -mieee, so > even if you don't get the trap in your code, you may get the trap in a > library. (I compile my libm with -mieee so that Konqueror doesn't crash with > FPE's on poorly written javascript code, its worth the slowdown. Patch appended.) Do'h! Here's that patch.. Drew Index: Makefile =================================================================== RCS file: /home/ncvs/src/lib/msun/Makefile,v retrieving revision 1.23.2.2 diff -u -r1.23.2.2 Makefile --- Makefile 17 Dec 2001 10:09:20 -0000 1.23.2.2 +++ Makefile 29 Mar 2002 15:06:16 -0000 @@ -45,11 +45,7 @@ .PATH: ${.CURDIR)/alpha ARCH= alpha ARCH_SRCS = s_copysign.S s_copysignf.S -# XXX Comment from NetBSD/Alpha: -# XXX LINT SIGFPEs in e_exp.c's strtod(). FP underflow/denorm software -# handling is broken (doesn't exist!) on the Alpha port. -# Stock gcc 2.7.2.1 doesn't understand these options. -#CFLAGS += -mtrap-precision=i -mfp-trap-mode=su +CFLAGS += -mieee .elif ${MACHINE_ARCH} == "i386" ARCH= i387 ARCH_PREFIX= ${ARCH}_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 2 7:31:14 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 23C3537B41B for ; Tue, 2 Apr 2002 07:31:01 -0800 (PST) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 16sQFL-0003Kp-01; Tue, 2 Apr 2002 17:30:55 +0200 Received: from kemoauc.mips.inka.de (localhost [127.0.0.1]) by kemoauc.mips.inka.de (8.12.2/8.12.2) with ESMTP id g32F7kst001080 for ; Tue, 2 Apr 2002 17:07:46 +0200 (CEST) (envelope-from mailnull@localhost.mips.inka.de) Received: (from mailnull@localhost) by kemoauc.mips.inka.de (8.12.2/8.12.2/Submit) id g32F7kes001079 for freebsd-alpha@freebsd.org; Tue, 2 Apr 2002 17:07:46 +0200 (CEST) (envelope-from mailnull) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: Source of "processor correctable error"? Date: Tue, 2 Apr 2002 15:07:45 +0000 (UTC) Message-ID: References: <20020401152244.GE41357@cicely8.cicely.de> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Bernd Walter wrote: > > Warning: received processor correctable error. > These are most likely main memory errors. Indeed one of the SIMMs is bad. Annoyingly this halves the amount of memory and the memory bus width in the box. What are my chances of replacing the faulty SIMM? Can I just substitute any other 72-pin FP-DRAM 8Mx36 (32MB ECC) 60ns SIMM, or are all modules required to be exactly alike? SIMMs of this general type are still available at somewhat unreasonable prices I guess, but finding one that shares exactly the same organization and God knows what parameters seems unlikely. (The SIMMs in place are physically double-sided, with a total of 24 Siemens HYB514100BJ-60 chips from 1997. There's some sort of warranty label, but I can't identify the vendor.) -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 2 8:27:28 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from aromo.spock.cl (aromo.spock.cl [200.27.125.98]) by hub.freebsd.org (Postfix) with ESMTP id 67AAC37B400 for ; Tue, 2 Apr 2002 08:27:25 -0800 (PST) Received: from aromo.spock.cl (aromo.spock.cl [200.27.125.98]) by aromo.spock.cl (8.11.1/8.9.3) with ESMTP id g32GRIa86474 for ; Tue, 2 Apr 2002 12:27:18 -0400 (CLT) Date: Tue, 2 Apr 2002 12:27:18 -0400 (CLT) From: Roberto de Iriarte To: freebsd-alpha@FreeBSD.org Subject: About DRI Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org From the project website at http://dri.sourceforge.net/ The Direct Rendering Infrastructure, also known as the DRI, is a framework for allowing direct access to graphics hardware in a safe and efficient manner. It includes changes to the X server, to several client libraries, and to the kernel. The first major use for the DRI is to create fast OpenGL implementations. It was developed originally for Linux, but there is a FreeBSD effort located at http://gladstone.uoregon.edu/~eanholt/dri/ The project seems to be targeted for X86 only My goal is to get it running on the Alpha platform, but first, i needed to verify that i have a workable hardware config, therefore the Linux install. On linux, even on my low-end Ati Rage 128 Pro card (16MB) the improvement versus software 3d (Mesa) is tremendous, i.e bzflag is very playable at 1024x768x16bpp Regards Roberto To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 2 8:41: 2 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id E801337B41B for ; Tue, 2 Apr 2002 08:40:49 -0800 (PST) Received: (from uucp@localhost) by srv1.cosmo-project.de (8.11.6/8.11.6) with UUCP id g32GePW62614; Tue, 2 Apr 2002 18:40:26 +0200 (CEST) (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.1.10]) by cicely5.cicely.de (8.12.1/8.12.1) with ESMTP id g32GWL6e083036; Tue, 2 Apr 2002 18:32:21 +0200 (CEST)?g (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (localhost [127.0.0.1]) by cicely8.cicely.de (8.12.2/8.12.2) with ESMTP id g32GWLnU045364; Tue, 2 Apr 2002 18:32:21 +0200 (CEST) (envelope-from ticso@cicely8.cicely.de) Received: (from ticso@localhost) by cicely8.cicely.de (8.12.2/8.12.2/Submit) id g32GWL7s045363; Tue, 2 Apr 2002 18:32:21 +0200 (CEST) Date: Tue, 2 Apr 2002 18:32:20 +0200 From: Bernd Walter To: Christian Weisgerber Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Source of "processor correctable error"? Message-ID: <20020402163220.GO41357@cicely8.cicely.de> References: <20020401152244.GE41357@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.26i X-Operating-System: FreeBSD cicely8.cicely.de 5.0-CURRENT i386 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Apr 02, 2002 at 03:07:45PM +0000, Christian Weisgerber wrote: > Bernd Walter wrote: > > > > Warning: received processor correctable error. > > These are most likely main memory errors. > > Indeed one of the SIMMs is bad. Annoyingly this halves the amount > of memory and the memory bus width in the box. > > What are my chances of replacing the faulty SIMM? Can I just > substitute any other 72-pin FP-DRAM 8Mx36 (32MB ECC) 60ns SIMM, or > are all modules required to be exactly alike? SIMMs of this general > type are still available at somewhat unreasonable prices I guess, > but finding one that shares exactly the same organization and God > knows what parameters seems unlikely. > > (The SIMMs in place are physically double-sided, with a total of > 24 Siemens HYB514100BJ-60 chips from 1997. There's some sort of > warranty label, but I can't identify the vendor.) Generaly speaking they have to be the same because the are all addressed in a single bank and so claims the documentation. But practical speaking you could try a random vendor 24 chip simm with a very good success chance. I wouldn't try to mix with a 18 chip simm. Theoreticaly even edo should work, but you don't get a speed gain and they are rare. There are some possible differences with refresh organisation, but this doesn't seem to matter on a PC164. I'm running myself 3 different vendors mixed. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 2 8:53: 6 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from users.pesaro.com (pesaro.com [195.120.225.6]) by hub.freebsd.org (Postfix) with ESMTP id DF4BF37B446 for ; Tue, 2 Apr 2002 08:52:05 -0800 (PST) Received: from mail.ru (pax2-184.cis.ru [212.109.194.184]) by users.pesaro.com (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with SMTP id g32GwQP11168 for ; Tue, 2 Apr 2002 18:58:27 +0200 Message-Id: <200204021658.g32GwQP11168@users.pesaro.com> From: "Paul" To: Subject: Software Development from Russia ($20-$25 per hour) Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Date: Tue, 2 Apr 2002 23:51:56 +0700 Reply-To: "Paul" X-Priority: 1 (Highest) Content-Transfer-Encoding: 8bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Dear IT Manager, Have you ever thought of redesigning your website or creating an on-line database, in short, anything that has to do with software development, this offer is right for you. Our highly skilled off-shore programmers are capable and ready to develop any of your e-commerce software dreams and needs. We develop for ALL WINDOWS AND UNIX PLATFORMS Auctions, Hosting Solutions, Shopping Carts, databases, networks, plus Perl, PHP, C++, ASP, Cold Fusion, Java, Wap, XML, MS Access, SQL, etc. From business analysis and consulting to web design, from coding to testing we provide a full cycle of IT services. Typical rates are 20-25 USD per hour. For more complete information about the company and services provided please visit http://www.smtprogramming.com I will be glad to answer any of your questions (bestdeal411@mail.ru). Feel free to contact us any time and all the estimates will be done for you FREE of charge. Thanks! Paul PS. It's one time message. You are not on a list. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 2 9:23:21 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id BC47637B400 for ; Tue, 2 Apr 2002 09:23:15 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g32HNDf43572; Tue, 2 Apr 2002 19:23:13 +0200 (CEST) (envelope-from wkb) Date: Tue, 2 Apr 2002 19:23:13 +0200 From: Wilko Bulte To: Christian Weisgerber Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Source of "processor correctable error"? Message-ID: <20020402192313.A43540@freebie.xs4all.nl> References: <20020401152244.GE41357@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from naddy@mips.inka.de on Tue, Apr 02, 2002 at 03:07:45PM +0000 X-OS: FreeBSD 4.5-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Apr 02, 2002 at 03:07:45PM +0000, Christian Weisgerber wrote: > Bernd Walter wrote: > > > > Warning: received processor correctable error. > > These are most likely main memory errors. > > Indeed one of the SIMMs is bad. Annoyingly this halves the amount > of memory and the memory bus width in the box. > > What are my chances of replacing the faulty SIMM? Can I just > substitute any other 72-pin FP-DRAM 8Mx36 (32MB ECC) 60ns SIMM, or > are all modules required to be exactly alike? SIMMs of this general > type are still available at somewhat unreasonable prices I guess, > but finding one that shares exactly the same organization and God > knows what parameters seems unlikely. In my experience: it tends to work, given decent SIMMs. -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands We are FreeBSD. Resistance is futile. Prepare to be committed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 2 9:24:40 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 41C8537B417 for ; Tue, 2 Apr 2002 09:24:34 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g32HOPv43593; Tue, 2 Apr 2002 19:24:25 +0200 (CEST) (envelope-from wkb) Date: Tue, 2 Apr 2002 19:24:25 +0200 From: Wilko Bulte To: Bernd Walter Cc: Christian Weisgerber , freebsd-alpha@FreeBSD.ORG Subject: Re: Source of "processor correctable error"? Message-ID: <20020402192425.B43540@freebie.xs4all.nl> References: <20020401152244.GE41357@cicely8.cicely.de> <20020402163220.GO41357@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020402163220.GO41357@cicely8.cicely.de>; from ticso@cicely8.cicely.de on Tue, Apr 02, 2002 at 06:32:20PM +0200 X-OS: FreeBSD 4.5-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Apr 02, 2002 at 06:32:20PM +0200, Bernd Walter wrote: > On Tue, Apr 02, 2002 at 03:07:45PM +0000, Christian Weisgerber wrote: > > Bernd Walter wrote: > > > > > > Warning: received processor correctable error. > > > These are most likely main memory errors. > > > > Indeed one of the SIMMs is bad. Annoyingly this halves the amount > > of memory and the memory bus width in the box. > > > > What are my chances of replacing the faulty SIMM? Can I just > > substitute any other 72-pin FP-DRAM 8Mx36 (32MB ECC) 60ns SIMM, or > > are all modules required to be exactly alike? SIMMs of this general > > type are still available at somewhat unreasonable prices I guess, > > but finding one that shares exactly the same organization and God > > knows what parameters seems unlikely. > > > > (The SIMMs in place are physically double-sided, with a total of > > 24 Siemens HYB514100BJ-60 chips from 1997. There's some sort of > > warranty label, but I can't identify the vendor.) > > Generaly speaking they have to be the same because the are all > addressed in a single bank and so claims the documentation. > But practical speaking you could try a random vendor 24 chip simm > with a very good success chance. > I wouldn't try to mix with a 18 chip simm. > Theoreticaly even edo should work, but you don't get a speed gain > and they are rare. Are you absolutely sure? I don't think we ever used EDO *SIMMs* on Alpha machines. There are some boxes using EDO *DIMMs* (like the AS500 sitting next to me) -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands We are FreeBSD. Resistance is futile. Prepare to be committed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 2 14:36:51 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 69AED37B41B for ; Tue, 2 Apr 2002 14:36:48 -0800 (PST) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.2/8.12.2) with ESMTP id g32MabYm006038; Tue, 2 Apr 2002 14:36:37 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.2/8.12.2/Submit) id g32MZDqa006031; Tue, 2 Apr 2002 14:35:13 -0800 (PST) Date: Tue, 2 Apr 2002 14:35:13 -0800 From: "David O'Brien" To: Thomas Pornin Cc: Rob B , freebsd-alpha@FreeBSD.ORG Subject: Re: Source of "processor correctable error"? Message-ID: <20020402143513.A1006@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <3CA8EADE.C11C8DF7@mindspring.com> <20020402002303.GH41357@cicely8.cicely.de> <20020402112528.A6188@gnah.bolet.org> <20020402110420.GI41357@cicely8.cicely.de> <00d801c1da37$50e313c0$0b64a8c0@becca> <20020402133207.A6601@gnah.bolet.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020402133207.A6601@gnah.bolet.org>; from pornin@bolet.org on Tue, Apr 02, 2002 at 01:32:08PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Apr 02, 2002 at 01:32:08PM +0200, Thomas Pornin wrote: > > You might try NetBSD as well. It has the longest history of Alpha > support, among the "free unices". But I would not say the best -- FreeBSD has. We were the first to have shared lib OSF/1 support (and NetBSD allowed their to atrophy beyond until they merged some bits from us), first to boot on 2100 (A and non-A), first to support UP1000 and UP2000, only BSD with SMP ability, etc.. -- -- David (obrien@FreeBSD.org) Disclaimer: Not speaking for FreeBSD, just expressing my own opinion. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 2 14:40:49 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mail17.speakeasy.net (mail17.speakeasy.net [216.254.0.217]) by hub.freebsd.org (Postfix) with ESMTP id F1EC337B41D for ; Tue, 2 Apr 2002 14:40:14 -0800 (PST) Received: (qmail 6552 invoked from network); 2 Apr 2002 22:40:13 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail17.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 2 Apr 2002 22:40:13 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.11.6/8.11.6) with ESMTP id g32Mf1v20908; Tue, 2 Apr 2002 17:41:01 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020402143513.A1006@dragon.nuxi.com> Date: Tue, 02 Apr 2002 17:40:15 -0500 (EST) From: John Baldwin To: "David O'Brien" Subject: Re: Source of "processor correctable error"? Cc: freebsd-alpha@FreeBSD.ORG, Rob B , Thomas Pornin Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 02-Apr-2002 David O'Brien wrote: > On Tue, Apr 02, 2002 at 01:32:08PM +0200, Thomas Pornin wrote: >> >> You might try NetBSD as well. It has the longest history of Alpha >> support, among the "free unices". > > But I would not say the best -- FreeBSD has. We were the first to have > shared lib OSF/1 support (and NetBSD allowed their to atrophy beyond > until they merged some bits from us), first to boot on 2100 (A and > non-A), first to support UP1000 and UP2000, only BSD with SMP ability, > etc.. NetBSD does do SMP on alpha btw. Though we beat them to multiuser by a couple of weeks I think. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - 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 Tue Apr 2 14:42: 3 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from meta.lo-res.org (meta.lo-res.org [195.58.189.92]) by hub.freebsd.org (Postfix) with ESMTP id 316B237B416 for ; Tue, 2 Apr 2002 14:41:59 -0800 (PST) Received: from there (chillig.lo-res.org [62.116.8.4]) by meta.lo-res.org (8.11.6/8.11.6) with SMTP id g32Mfgf18964; Wed, 3 Apr 2002 00:41:42 +0200 (CEST) (envelope-from aaron@lo-res.org) Message-Id: <200204022241.g32Mfgf18964@meta.lo-res.org> Content-Type: text/plain; charset="iso-8859-15" From: aaron To: Bernd Walter , Thomas Pornin Subject: Re: Source of "processor correctable error"? Date: Wed, 3 Apr 2002 00:41:40 +0200 X-Mailer: KMail [version 1.3.2] Cc: freebsd-alpha@FreeBSD.ORG References: <20020402112528.A6188@gnah.bolet.org> <20020402110420.GI41357@cicely8.cicely.de> In-Reply-To: <20020402110420.GI41357@cicely8.cicely.de> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Adding to the "processor correctable error" thread: I received an old Alpha PC164 just as the originator of the thread. Same error message over here. Whats more: the message appears on: * netbsd * openbsd (probably freebsd if i manage to install it - kernel traps... :) I can try with different RAM but it struck me that we have the same error with probably different RAMs greetings, aaron. -- If time heals all wounds, how come the belly button stays the same? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 2 15:31:54 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id 4ABA237B4E3 for ; Tue, 2 Apr 2002 15:30:39 -0800 (PST) Received: (from uucp@localhost) by srv1.cosmo-project.de (8.11.6/8.11.6) with UUCP id g32NUUP69351; Wed, 3 Apr 2002 01:30:31 +0200 (CEST) (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.1.10]) by cicely5.cicely.de (8.12.1/8.12.1) with ESMTP id g32NMm6e086566; Wed, 3 Apr 2002 01:22:48 +0200 (CEST)?g (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (localhost [127.0.0.1]) by cicely8.cicely.de (8.12.2/8.12.2) with ESMTP id g32NMknU046224; Wed, 3 Apr 2002 01:22:46 +0200 (CEST) (envelope-from ticso@cicely8.cicely.de) Received: (from ticso@localhost) by cicely8.cicely.de (8.12.2/8.12.2/Submit) id g32NMjEL046223; Wed, 3 Apr 2002 01:22:45 +0200 (CEST) Date: Wed, 3 Apr 2002 01:22:45 +0200 From: Bernd Walter To: Wilko Bulte Cc: Christian Weisgerber , freebsd-alpha@FreeBSD.ORG Subject: Re: Source of "processor correctable error"? Message-ID: <20020402232244.GP41357@cicely8.cicely.de> References: <20020401152244.GE41357@cicely8.cicely.de> <20020402163220.GO41357@cicely8.cicely.de> <20020402192425.B43540@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020402192425.B43540@freebie.xs4all.nl> User-Agent: Mutt/1.3.26i X-Operating-System: FreeBSD cicely8.cicely.de 5.0-CURRENT i386 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Apr 02, 2002 at 07:24:25PM +0200, Wilko Bulte wrote: > On Tue, Apr 02, 2002 at 06:32:20PM +0200, Bernd Walter wrote: > > Generaly speaking they have to be the same because the are all > > addressed in a single bank and so claims the documentation. > > But practical speaking you could try a random vendor 24 chip simm > > with a very good success chance. > > I wouldn't try to mix with a 18 chip simm. > > Theoreticaly even edo should work, but you don't get a speed gain > > and they are rare. > > Are you absolutely sure? I don't think we ever used EDO *SIMMs* > on Alpha machines. EDO and fastpage are nearly the same. EDO only has a longer data output phase while traditional fast page go into tri-state. The speed gain is that you can already take the steps for the next access, while still taking the current data. If you have a board not doing bank interleaving they are often interchangeable as the small difference doesn't matter. > There are some boxes using EDO *DIMMs* (like the AS500 > sitting next to me) Nice shoot - it's the same chipset (21172) as the PC164... But no sign of a possible speed gain in the chipset docs. They should work with identic speed as fastpage. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 2 15:37: 4 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id EB71437B416 for ; Tue, 2 Apr 2002 15:37:00 -0800 (PST) Received: from pool0045.cvx22-bradley.dialup.earthlink.net ([209.179.198.45] helo=mindspring.com) by falcon.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16sXpi-0002XX-00; Tue, 02 Apr 2002 15:36:59 -0800 Message-ID: <3CAA4083.80AB0B72@mindspring.com> Date: Tue, 02 Apr 2002 15:36:35 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Christian Weisgerber Cc: freebsd-alpha@freebsd.org Subject: Re: Source of "processor correctable error"? References: <20020401152244.GE41357@cicely8.cicely.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Christian Weisgerber wrote: > Bernd Walter wrote: > > > Warning: received processor correctable error. > > These are most likely main memory errors. > > Indeed one of the SIMMs is bad. Annoyingly this halves the amount > of memory and the memory bus width in the box. Verify that it's the SIMMs, by swapping them. It may be that your wide path is broken, instead. > What are my chances of replacing the faulty SIMM? Can I just > substitute any other 72-pin FP-DRAM 8Mx36 (32MB ECC) 60ns SIMM, or > are all modules required to be exactly alike? SIMMs of this general > type are still available at somewhat unreasonable prices I guess, > but finding one that shares exactly the same organization and God > knows what parameters seems unlikely. Usually, you want them to be the same, because of slight differences in timing that come from method of manufacture and internal logic design. You can generally get away with matching banks with the same address select. My main source of these things is PS/2 memory suppliers, but I don't know your bus speed, so I don't know if this will work for you. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 2 23:17:45 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from skywalker.systec.no (skywalker.systec.no [80.64.196.212]) by hub.freebsd.org (Postfix) with ESMTP id CB5CA37B41C for ; Tue, 2 Apr 2002 23:17:39 -0800 (PST) Received: from skywalker.systec.no (skywalker.systec.no [192.168.100.3]) by relay.systec.no (8.11.6/8.11.6) with ESMTP id g32HtqZ31406 for ; Tue, 2 Apr 2002 19:55:53 +0200 (CEST) (envelope-from oystein.andreassen@systec.no) Received: by skywalker.systec.no with Internet Mail Service (5.5.2653.19) id ; Tue, 2 Apr 2002 19:49:52 +0200 Message-ID: From: =?iso-8859-1?Q?=D8ystein_Andreassen?= To: freebsd-alpha@FreeBSD.ORG Subject: Problem with MyLex KZPAC PCI RAID controller Date: Tue, 2 Apr 2002 19:49:49 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, I have tried to install FreeBSD 4.5 (Release(?)) on a Digital Server = 5000 Model 5303 6533A. It has a MyLex KZPAC PCI RAID Controller. I manage to boot the CD and everything seems fine until the file copying starts. When the copying is around 23% of / it comes to a complete halt and i = get ALOT of errors like "mlx0: I/O error - attempt to write beyond end of drive" I've read the mailinglists and found that this was a problem in 4.3 = (i386) (mailinglist "current", may 2001). So I tried to put the MyLex controller in an i386 machine. I still had = the disks in the alpha. This worked fine! I guess my question is: Why isn't the alpha driver updated while the = i386 driver is? (I really hope that someone just forgot and it's VERY simple = to fix!:) =D8ystein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Apr 3 6:37:20 2002 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 4D47D37B400; Wed, 3 Apr 2002 06:37:17 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA10734; Wed, 3 Apr 2002 09:37:16 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g33EakE96080; Wed, 3 Apr 2002 09:36:46 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <15531.4990.536630.145584@grasshopper.cs.duke.edu> Date: Wed, 3 Apr 2002 09:36:46 -0500 (EST) To: =?iso-8859-1?Q?=D8ystein_Andreassen?= Cc: freebsd-alpha@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: Problem with MyLex KZPAC PCI RAID controller In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org =D8ystein Andreassen writes: >=20 > Hello, >=20 > I have tried to install FreeBSD 4.5 (Release(?)) on a Digital Server= 5000 > Model 5303 6533A. > It has a MyLex KZPAC PCI RAID Controller. I manage to boot the CD an= d > everything seems fine until the file copying starts. > When the copying is around 23% of / it comes to a complete halt and = i get > ALOT of errors like > "mlx0: I/O error - attempt to write beyond end of drive" > I've read the mailinglists and found that this was a problem in 4.3 = (i386) > (mailinglist "current", may 2001). > So I tried to put the MyLex controller in an i386 machine. I still h= ad the > disks in the alpha. This worked fine! >=20 > I guess my question is: Why isn't the alpha driver updated while the= i386 > driver is? (I really hope that someone just forgot and it's VERY sim= ple to > fix!:) Its the same driver on all platforms. I'm a little out of my depth here, as I've never even seen a mylex card. One WAG I have is that perhaps the alpha is storing the size of the array someplace in the hosts firmware & when you moved the card to a PC, that information was cleared? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Apr 3 6:39:45 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 280F337B41A; Wed, 3 Apr 2002 06:39:38 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g33EdTd47458; Wed, 3 Apr 2002 16:39:29 +0200 (CEST) (envelope-from wkb) Date: Wed, 3 Apr 2002 16:39:29 +0200 From: Wilko Bulte To: Andrew Gallatin Cc: =?iso-8859-15?Q?=D8ystein_Andreassen?= , freebsd-alpha@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: Problem with MyLex KZPAC PCI RAID controller Message-ID: <20020403163929.A47435@freebie.xs4all.nl> References: <15531.4990.536630.145584@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <15531.4990.536630.145584@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Apr 03, 2002 at 09:36:46AM -0500 X-OS: FreeBSD 4.5-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Apr 03, 2002 at 09:36:46AM -0500, Andrew Gallatin wrote: We used to have different firmware on the Mylex's for Intel and Alpha based servers. Don't ask me why. Wilko > Øystein Andreassen writes: > > > > Hello, > > > > I have tried to install FreeBSD 4.5 (Release(?)) on a Digital Server 5000 > > Model 5303 6533A. > > It has a MyLex KZPAC PCI RAID Controller. I manage to boot the CD and > > everything seems fine until the file copying starts. > > When the copying is around 23% of / it comes to a complete halt and i get > > ALOT of errors like > > "mlx0: I/O error - attempt to write beyond end of drive" > > I've read the mailinglists and found that this was a problem in 4.3 (i386) > > (mailinglist "current", may 2001). > > So I tried to put the MyLex controller in an i386 machine. I still had the > > disks in the alpha. This worked fine! > > > > I guess my question is: Why isn't the alpha driver updated while the i386 > > driver is? (I really hope that someone just forgot and it's VERY simple to > > fix!:) > > Its the same driver on all platforms. > > I'm a little out of my depth here, as I've never even seen a mylex > card. One WAG I have is that perhaps the alpha is storing the size of > the array someplace in the hosts firmware & when you moved the card to > a PC, that information was cleared? > > Drew > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message ---end of quoted text--- -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Apr 3 8:12:22 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from aromo.spock.cl (aromo.spock.cl [200.27.125.98]) by hub.freebsd.org (Postfix) with ESMTP id 8D41837B400 for ; Wed, 3 Apr 2002 08:12:14 -0800 (PST) Received: from aromo.spock.cl (aromo.spock.cl [200.27.125.98]) by aromo.spock.cl (8.11.1/8.9.3) with ESMTP id g33GBta04778; Wed, 3 Apr 2002 12:11:55 -0400 (CLT) Date: Wed, 3 Apr 2002 12:11:55 -0400 (CLT) From: Roberto de Iriarte To: =?iso-8859-1?Q?=D8ystein_Andreassen?= Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Problem with MyLex KZPAC PCI RAID controller In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, 2 Apr 2002, [iso-8859-1] =D8ystein Andreassen wrote: >=20 > Hello, >=20 > I have tried to install FreeBSD 4.5 (Release(?)) on a Digital Server 5000 > Model 5303 6533A. > It has a MyLex KZPAC PCI RAID Controller. I manage to boot the CD and > everything seems fine until the file copying starts. > When the copying is around 23% of / it comes to a complete halt and i get > ALOT of errors like > "mlx0: I/O error - attempt to write beyond end of drive" > I've read the mailinglists and found that this was a problem in 4.3 (i386= ) > (mailinglist "current", may 2001). > So I tried to put the MyLex controller in an i386 machine. I still had th= e > disks in the alpha. This worked fine! >=20 > I guess my question is: Why isn't the alpha driver updated while the i386 > driver is? (I really hope that someone just forgot and it's VERY simple t= o > fix!:) >=20 >=20 >=20 > =D8ystein >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message >=20 I have an alphaserver 2100A with a very similar controller. Getting it to work was a headache, mostly for firmware problems. The firmware of the DEC oem controllers was not updated as frequently as the one on PC's, as a matter of fact, i could never get the upgrade programm (ARC based) to work. I would=20 a) Check that the firmware is the latest supported revision for the controller. The upgrade needs to be done on a PC. 2.73-0-00 is the minimun for FreeBSD. 3.X is much better, i.e it allows to use the mlxtools, but you need a controller with two EEPROMS to be able to install it!=20 b) Check that the Dallas NVRAM is OK, if the controller has been sitting idle for a long time, i would replace it just for good measure c) Erase all the array config and rebuild from scratch using the latest utilities ON THE ALPHA!. What is the actual config on your machine (Firmware revision, Disk make and size, Raid config, strip size) Get me some more info and i'll try to provide a detailed procedure for you. Regards Roberto de I roberto@spock.cl Santiago, CL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Apr 3 8:13:30 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id D95F637B41C for ; Wed, 3 Apr 2002 08:13:24 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g33GCu4F047337 for ; Wed, 3 Apr 2002 18:12:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: alpha@freebsd.org Subject: please test kernel patch on alpha-CURRENT please! From: Poul-Henning Kamp Date: Wed, 03 Apr 2002 18:12:56 +0200 Message-ID: <47336.1017850376@critter.freebsd.dk> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I need somebody to test this kernel patch for on an alpha: http://phk.freebsd.dk/patch/alpha.patch Please boot a kernel with a userland _not_ compiled with this patch and tell me if the following things work or break: fsck ? mounting filesystems ? disklabel da0 (for whatever suitable value of da0) Thanks! -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Apr 3 9:37:51 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 37F7837B41C for ; Wed, 3 Apr 2002 09:37:45 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g33HbYP48093; Wed, 3 Apr 2002 19:37:34 +0200 (CEST) (envelope-from wkb) Date: Wed, 3 Apr 2002 19:37:34 +0200 From: Wilko Bulte To: Bernd Walter Cc: Christian Weisgerber , freebsd-alpha@FreeBSD.ORG Subject: Re: Source of "processor correctable error"? Message-ID: <20020403193734.A48068@freebie.xs4all.nl> References: <20020401152244.GE41357@cicely8.cicely.de> <20020402163220.GO41357@cicely8.cicely.de> <20020402192425.B43540@freebie.xs4all.nl> <20020402232244.GP41357@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020402232244.GP41357@cicely8.cicely.de>; from ticso@cicely8.cicely.de on Wed, Apr 03, 2002 at 01:22:45AM +0200 X-OS: FreeBSD 4.5-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Apr 03, 2002 at 01:22:45AM +0200, Bernd Walter wrote: > On Tue, Apr 02, 2002 at 07:24:25PM +0200, Wilko Bulte wrote: > > On Tue, Apr 02, 2002 at 06:32:20PM +0200, Bernd Walter wrote: > > > Generaly speaking they have to be the same because the are all > > > addressed in a single bank and so claims the documentation. > > > But practical speaking you could try a random vendor 24 chip simm > > > with a very good success chance. > > > I wouldn't try to mix with a 18 chip simm. > > > Theoreticaly even edo should work, but you don't get a speed gain > > > and they are rare. > > > > Are you absolutely sure? I don't think we ever used EDO *SIMMs* > > on Alpha machines. > > EDO and fastpage are nearly the same. Nearly.. One of my direct colleagues was one of the folks who was involved with qualifying RAM/simm vendors for Alphas. I've heared enough stories of junk RAM to be very weary of 'nearly the same' ;) > EDO only has a longer data output phase while traditional fast page > go into tri-state. > The speed gain is that you can already take the steps for the next > access, while still taking the current data. > If you have a board not doing bank interleaving they are often > interchangeable as the small difference doesn't matter. There is of course the matter that you need to find 36 bit EDO SIMMs to be able to test this in the first place. EDO PC stuff tends to be 32 bit only in my experience at least. > > There are some boxes using EDO *DIMMs* (like the AS500 > > sitting next to me) > > Nice shoot - it's the same chipset (21172) as the PC164... > But no sign of a possible speed gain in the chipset docs. > They should work with identic speed as fastpage. You can try of course. -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Apr 3 10: 1: 8 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from piglet.theeirons.org (dsl-64-195-193-89.telocity.com [64.195.193.89]) by hub.freebsd.org (Postfix) with ESMTP id 51C3037B417 for ; Wed, 3 Apr 2002 10:01:02 -0800 (PST) Received: from localhost (nadav@localhost) by piglet.theeirons.org (8.11.6/8.11.6) with ESMTP id g33Hxjx03522; Wed, 3 Apr 2002 09:59:46 -0800 (PST) (envelope-from nadav@TheEirons.org) Date: Wed, 3 Apr 2002 09:59:45 -0800 (PST) From: Nadav Eiron To: Roberto de Iriarte Cc: =?iso-8859-1?Q?=D8ystein_Andreassen?= , freebsd-alpha@FreeBSD.ORG Subject: Re: Problem with MyLex KZPAC PCI RAID controller In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 3 Apr 2002, Roberto de Iriarte wrote: > > I have an alphaserver 2100A with a very similar controller. Getting > it to work was a headache, mostly for firmware problems. > > The firmware of the DEC oem controllers was not updated as frequently > as the one on PC's, as a matter of fact, i could never get the upgrade > programm (ARC based) to work. > > I would > > a) Check that the firmware is the latest supported revision for the > controller. The upgrade needs to be done on a PC. > > 2.73-0-00 is the minimun for FreeBSD. FWIW, I updated my Mylex (in a DS10L) to 2.73-00 on the Alpha. It required booting into AlphaBIOS and using DEQ's (not Mylex's) floppy image. Otherwise, it worked as advertised. YMMV. Nadav To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 4 3:25:55 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from trillian.santala.org (ip212-226-173-33.adsl.kpnqwest.fi [212.226.173.33]) by hub.freebsd.org (Postfix) with SMTP id DFF8537B421 for ; Thu, 4 Apr 2002 03:25:49 -0800 (PST) Received: (qmail 73163 invoked by uid 11053); 4 Apr 2002 11:25:47 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 4 Apr 2002 11:25:47 -0000 Date: Thu, 4 Apr 2002 14:25:47 +0300 (EEST) From: Jarkko Santala X-X-Sender: jake@trillian.santala.org To: freebsd-alpha@freebsd.org Subject: Still about ISA NICs on FreeBSD 4.5/alpha Message-ID: <20020404140739.H61960-100000@trillian.santala.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi all, Sorry for writing about this again, but does anyone else have this same problem? I know some EISA stuff might not work, but how about ISA NICs? Doesn't seem to me like this would be horribly hard to fix if one knows what she is doing. I'm running 4.5-RELEASE-p1 on a AlphaServer 1000. If I'm doing something stupid please let me know so I can stop making a fool of myself. ;) And if there's anything I can do to provide more information, I will be happy to do it. First with 3 ISA NICs in kernel like this: ---cut--- --- GENERIC Wed Dec 19 20:34:44 2001 +++ GENERIC-ISA Thu Apr 4 12:19:58 2002 @@ -131,4 +131,9 @@ device ppi # Parallel port interface device #device vpo # Requires scbus and da + +# ISA Etherner NICs (let's see now...) +device ep +device ex +device fe0 at isa? port 0x300 # PCI Ethernet NICs. ---cut--- 'config GENERIC-ISA' goes fine, 'make depend' results in: ---cut--- bd_isa.c ../../isa/atkbdc_isa.c ../../isa/fd.c ../../isa/ppc.c ../../isa/psm.c ../../isa/sio.c ../../isa/syscons_isa.c ../../isa/vga_isa.c ../../kern/subr_diskmbr.c ../../libkern/bcmp.c ../../libkern/ffs.c ioconf.c vnode_if.c config.c ../../alpha/alpha/genassym.c ../../dev/fe/if_fe.c:71: opt_fe.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/sys/compile/GENERIC-ISA. trillian:/usr/src/sys/compile/GENERIC-ISA# ---cut--- Then, with the fe0 removed: ---cut--- --- GENERIC Wed Dec 19 20:34:44 2001 +++ GENERIC-ISA2 Thu Apr 4 12:35:28 2002 @@ -131,4 +131,8 @@ device ppi # Parallel port interface device #device vpo # Requires scbus and da + +# ISA Etherner NICs (let's see now...) +device ep +device ex # PCI Ethernet NICs. ---cut--- 'config GENERIC-ISA2' and 'make depend' go fine, but 'make' results in: ---cut--- cc -c -O -pipe -mcpu=ev4 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -I../../contrib/ipfilter -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 vers.c linking kernel if_ep_isa.o: In function `ep_isa_identify': if_ep_isa.o(.text+0x1d0): undefined reference to `elink_idseq' if_ep_isa.o(.text+0x1d4): undefined reference to `elink_idseq' if_ep_isa.o(.text+0x1e0): undefined reference to `elink_reset' if_ep_isa.o(.text+0x1e4): undefined reference to `elink_reset' if_ep_isa.o(.text+0x244): undefined reference to `elink_idseq' if_ep_isa.o(.text+0x248): undefined reference to `elink_idseq' *** Error code 1 Stop in /usr/src/sys/compile/GENERIC-ISA2. ---cut--- -jake -- Jarkko Santala http://www.iki.fi/jake/ System Administrator Cell. +358 40 720 4512 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 4 6:25:10 2002 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 67C6C37B419 for ; Thu, 4 Apr 2002 06:25:03 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA18131; Thu, 4 Apr 2002 09:25:02 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g34EOVB98428; Thu, 4 Apr 2002 09:24: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 Message-ID: <15532.25119.807428.35143@grasshopper.cs.duke.edu> Date: Thu, 4 Apr 2002 09:24:31 -0500 (EST) To: Jarkko Santala Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Still about ISA NICs on FreeBSD 4.5/alpha In-Reply-To: <20020404140739.H61960-100000@trillian.santala.org> References: <20020404140739.H61960-100000@trillian.santala.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Jarkko Santala writes: > Hi all, > > Sorry for writing about this again, but does anyone else have this same > problem? I know some EISA stuff might not work, but how about ISA NICs? > Doesn't seem to me like this would be horribly hard to fix if one knows > what she is doing. Nobody else has tried to run most ISA nics on anything but x86. That's why they are not in the alpha GENERIC kernel. You're tredding on new ground here. Your initial problems are configuration related. Expect to have more problems once you get the drivers building. > I'm running 4.5-RELEASE-p1 on a AlphaServer 1000. If I'm doing something > stupid please let me know so I can stop making a fool of myself. ;) And > if there's anything I can do to provide more information, I will be happy > to do it. > > First with 3 ISA NICs in kernel like this: > > ---cut--- > --- GENERIC Wed Dec 19 20:34:44 2001 > +++ GENERIC-ISA Thu Apr 4 12:19:58 2002 > @@ -131,4 +131,9 @@ > device ppi # Parallel port interface device > #device vpo # Requires scbus and da > + > +# ISA Etherner NICs (let's see now...) > +device ep > +device ex > +device fe0 at isa? port 0x300 > > # PCI Ethernet NICs. > ---cut--- > > 'config GENERIC-ISA' goes fine, 'make depend' results in: > > ---cut--- > bd_isa.c ../../isa/atkbdc_isa.c ../../isa/fd.c ../../isa/ppc.c > ../../isa/psm.c ../../isa/sio.c ../../isa/syscons_isa.c > ../../isa/vga_isa.c ../../kern/subr_diskmbr.c ../../libkern/bcmp.c > ../../libkern/ffs.c ioconf.c vnode_if.c config.c > ../../alpha/alpha/genassym.c > ../../dev/fe/if_fe.c:71: opt_fe.h: No such file or directory > mkdep: compile failed > *** Error code 1 Move: FE_8BIT_SUPPORT opt_fe.h from conf/options.i386 to conf/options & try again. You'll probably stumble on something else. > > Stop in /usr/src/sys/compile/GENERIC-ISA. > trillian:/usr/src/sys/compile/GENERIC-ISA# > ---cut--- > > Then, with the fe0 removed: > > ---cut--- > --- GENERIC Wed Dec 19 20:34:44 2001 > +++ GENERIC-ISA2 Thu Apr 4 12:35:28 2002 > @@ -131,4 +131,8 @@ > device ppi # Parallel port interface device > #device vpo # Requires scbus and da > + > +# ISA Etherner NICs (let's see now...) > +device ep > +device ex > > # PCI Ethernet NICs. > ---cut--- > > 'config GENERIC-ISA2' and 'make depend' go fine, but 'make' results in: > > ---cut--- > cc -c -O -pipe -mcpu=ev4 -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. > -I../../../include -I../../contrib/ipfilter -D_KERNEL -include > opt_global.h -elf -mno-fp-regs -Wa,-mev56 vers.c > linking kernel > if_ep_isa.o: In function `ep_isa_identify': > if_ep_isa.o(.text+0x1d0): undefined reference to `elink_idseq' > if_ep_isa.o(.text+0x1d4): undefined reference to `elink_idseq' > if_ep_isa.o(.text+0x1e0): undefined reference to `elink_reset' > if_ep_isa.o(.text+0x1e4): undefined reference to `elink_reset' > if_ep_isa.o(.text+0x244): undefined reference to `elink_idseq' > if_ep_isa.o(.text+0x248): undefined reference to `elink_idseq' > *** Error code 1 > Move i386/isa/elink.c optional ep from conf/files.i386 to conf/files & try again. I notice the ep driver still does inb/outb so it hasn't been converted to bus space yet. This reduces the likleyhood of it actually working if you manage to compile it. BTW, do you actually have all these nics? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 4 12: 7:50 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from espresso.q9media.com (espresso.q9media.com [216.254.138.122]) by hub.freebsd.org (Postfix) with ESMTP id 94FEB37B41C; Thu, 4 Apr 2002 12:07:47 -0800 (PST) Received: (from mike@localhost) by espresso.q9media.com (8.11.6/8.11.6) id g34K1PV36252; Thu, 4 Apr 2002 15:01:25 -0500 (EST) (envelope-from mike) Date: Thu, 4 Apr 2002 15:01:25 -0500 From: Mike Barcroft To: Poul-Henning Kamp Cc: alpha@freebsd.org Subject: Re: please test kernel patch on alpha-CURRENT please! Message-ID: <20020404150125.D93859@espresso.q9media.com> References: <47336.1017850376@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47336.1017850376@critter.freebsd.dk>; from phk@freebsd.org on Wed, Apr 03, 2002 at 06:12:56PM +0200 Organization: The FreeBSD Project Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Poul-Henning Kamp writes: > I need somebody to test this kernel patch for on an alpha: > > http://phk.freebsd.dk/patch/alpha.patch > > Please boot a kernel with a userland _not_ compiled with this > patch and tell me if the following things work or break: I tested this on a GENERIC kernel. > fsck ? Works correctly. > mounting filesystems ? Works correctly; all three local harddisks mounted okay. > disklabel da0 (for whatever suitable value of da0) Works correctly; diff(1) shows no difference in disklabels between a kernel with your patch applied and a kernel without. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 4 14:53:11 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from meta.lo-res.org (meta.lo-res.org [195.58.189.92]) by hub.freebsd.org (Postfix) with ESMTP id D196A37B419 for ; Thu, 4 Apr 2002 14:53:02 -0800 (PST) Received: from there (chillig.lo-res.org [62.116.8.4]) by meta.lo-res.org (8.11.6/8.11.6) with SMTP id g34Mr0f36976; Fri, 5 Apr 2002 00:53:00 +0200 (CEST) (envelope-from aaron@lo-res.org) Message-Id: <200204042253.g34Mr0f36976@meta.lo-res.org> Content-Type: text/plain; charset="iso-8859-15" From: aaron To: naddy@mips.inka.de (Christian Weisgerber), freebsd-alpha@FreeBSD.ORG Subject: Re: Source of "processor correctable error"? Date: Fri, 5 Apr 2002 00:52:59 +0200 X-Mailer: KMail [version 1.3.2] References: <20020401152244.GE41357@cicely8.cicely.de> In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tuesday 02 April 2002 17:07, Christian Weisgerber wrote: ok, maybe this is known already. but since I had the same annoying error message i figured this might be of interest to a few ppl here: http://hepalpha1.phy.uic.edu/l2alpha/docs/pc164trm.pdf > Bernd Walter wrote: > > > Warning: received processor correctable error. > > > > These are most likely main memory errors. > > Indeed one of the SIMMs is bad. Annoyingly this halves the amount > of memory and the memory bus width in the box. > > What are my chances of replacing the faulty SIMM? Can I just > substitute any other 72-pin FP-DRAM 8Mx36 (32MB ECC) 60ns SIMM, or > are all modules required to be exactly alike? SIMMs of this general > type are still available at somewhat unreasonable prices I guess, > but finding one that shares exactly the same organization and God > knows what parameters seems unlikely. > > (The SIMMs in place are physically double-sided, with a total of > 24 Siemens HYB514100BJ-60 chips from 1997. There's some sort of > warranty label, but I can't identify the vendor.) -- If time heals all wounds, how come the belly button stays the same? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 4 19: 1:21 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from hub.freebsd.org (ws084187.housing-ec.siu.edu [131.230.84.187]) by hub.freebsd.org (Postfix) with SMTP id 10E5737B41C for ; Thu, 4 Apr 2002 19:01:20 -0800 (PST) From: "pht92gee@hotmail.com" Date: Thu, 04 Apr 2002 21:01:03 To: alpha@freebsd.org Subject: Tool Kit MIME-Version: 1.0 Content-Type: text/plain;charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <20020405030120.10E5737B41C@hub.freebsd.org> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hey there, I found this web site that gives some good sources for doing more with the school’s web site. Let me know what you think. http://www.pluggedin.org/tool_kit/ Bradley Smith Educator To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 4 21:51:10 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from trillian.santala.org (ip212-226-173-33.adsl.kpnqwest.fi [212.226.173.33]) by hub.freebsd.org (Postfix) with SMTP id BA76E37B41A for ; Thu, 4 Apr 2002 21:51:06 -0800 (PST) Received: (qmail 86396 invoked by uid 11053); 5 Apr 2002 05:51:05 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 5 Apr 2002 05:51:05 -0000 Date: Fri, 5 Apr 2002 08:51:04 +0300 (EEST) From: Jarkko Santala X-X-Sender: jake@trillian.santala.org To: Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Still about ISA NICs on FreeBSD 4.5/alpha In-Reply-To: <15532.25119.807428.35143@grasshopper.cs.duke.edu> Message-ID: <20020405084009.J61960-100000@trillian.santala.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 4 Apr 2002, Andrew Gallatin wrote: > Nobody else has tried to run most ISA nics on anything but x86. > That's why they are not in the alpha GENERIC kernel. You're tredding > on new ground here. Your initial problems are configuration related. > Expect to have more problems once you get the drivers building. Ahaa, that explains a lot. ;) Using your instructions I was able to compile ep, ex and fe0 into the kernel. Now I'll just have to find a suitable time to shutdown the server and test the cards. > BTW, do you actually have all these nics? Actually I don't have ex (included that one by mistake), but I should have at least fe, ed and ep cards + I have access to the QA lab here at work and they have all kinds of NICs. Maybe I'll gather as many different ones as possible and spend a weekend trying them all. If you think that it would be worth it, that is. I might also have a bug to report concerning bridge + ipfw on alpha, but I'll have to repeat it a few times before I'll cry wolf. The firewall I have now is an alpha too and it panicked a few times when none of the interfaces had ip addresses assigned. More specs on that when I get around to it. -jake -- Jarkko Santala http://www.iki.fi/jake/ System Administrator Cell. +358 40 720 4512 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 4 23:24:10 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from skywalker.systec.no (skywalker.systec.no [80.64.196.212]) by hub.freebsd.org (Postfix) with ESMTP id 89C5E37B422; Thu, 4 Apr 2002 23:22:14 -0800 (PST) Received: from skywalker.systec.no (skywalker.systec.no [192.168.100.3]) by relay.systec.no (8.11.6/8.11.6) with ESMTP id g33FQpZ34159; Wed, 3 Apr 2002 17:26:51 +0200 (CEST) (envelope-from oystein.andreassen@systec.no) Received: by skywalker.systec.no with Internet Mail Service (5.5.2653.19) id ; Wed, 3 Apr 2002 17:20:44 +0200 Message-ID: From: =?iso-8859-15?Q?=D8ystein_Andreassen?= To: "'Wilko Bulte'" , Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: RE: Problem with MyLex KZPAC PCI RAID controller Date: Wed, 3 Apr 2002 17:20:34 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org (If I'm posting this wrong, kick me or something... I'm kinda new to = this.. :) If it helps, the controller firmware is 2.70 (Latest I found on www.compaq.com). The config prog for both DOS and Alpha reports that = this is the firmware version. I found an article on FreeBSD.org (http://www.freebsd.org/relnotes/4-STABLE/installation/alpha/trouble.htm= l#Q4 .3.21.), but I can't seem to find the place where I set the geometry = mode, so I can't test this... :( =D8ystein -----Original Message----- From: Wilko Bulte [mailto:wkb@freebie.xs4all.nl] Sent: Wednesday, April 03, 2002 16:39 To: Andrew Gallatin Cc: =D8ystein Andreassen; freebsd-alpha@FreeBSD.ORG; msmith@FreeBSD.ORG Subject: Re: Problem with MyLex KZPAC PCI RAID controller On Wed, Apr 03, 2002 at 09:36:46AM -0500, Andrew Gallatin wrote: We used to have different firmware on the Mylex's for Intel and Alpha based servers. Don't ask me why. Wilko > =D8ystein Andreassen writes: > >=20 > > Hello, > >=20 > > I have tried to install FreeBSD 4.5 (Release(?)) on a Digital = Server 5000 > > Model 5303 6533A. > > It has a MyLex KZPAC PCI RAID Controller. I manage to boot the CD = and > > everything seems fine until the file copying starts. > > When the copying is around 23% of / it comes to a complete halt = and i get > > ALOT of errors like > > "mlx0: I/O error - attempt to write beyond end of drive" > > I've read the mailinglists and found that this was a problem in = 4.3 (i386) > > (mailinglist "current", may 2001). > > So I tried to put the MyLex controller in an i386 machine. I still = had the > > disks in the alpha. This worked fine! > >=20 > > I guess my question is: Why isn't the alpha driver updated while = the i386 > > driver is? (I really hope that someone just forgot and it's VERY = simple to > > fix!:) >=20 > Its the same driver on all platforms. >=20 > I'm a little out of my depth here, as I've never even seen a mylex > card. One WAG I have is that perhaps the alpha is storing the size = of > the array someplace in the hosts firmware & when you moved the card = to > a PC, that information was cleared? >=20 > Drew >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message ---end of quoted text--- --=20 | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Apr 5 7:29:15 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id 31FDF37B99B for ; Fri, 5 Apr 2002 07:26:37 -0800 (PST) Received: from bmah.dyndns.org ([12.233.149.189]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020405152615.QGGE18078.rwcrmhc51.attbi.com@bmah.dyndns.org>; Fri, 5 Apr 2002 15:26:15 +0000 Received: from intruder.bmah.org (localhost [IPv6:::1]) by bmah.dyndns.org (8.12.2/8.12.2) with ESMTP id g35FQFt2002845; Fri, 5 Apr 2002 07:26:15 -0800 (PST) (envelope-from bmah@intruder.bmah.org) Received: (from bmah@localhost) by intruder.bmah.org (8.12.2/8.12.2/Submit) id g35FQFO8002844; Fri, 5 Apr 2002 07:26:15 -0800 (PST) Message-Id: <200204051526.g35FQFO8002844@intruder.bmah.org> X-Mailer: exmh version 2.5+ 20020403 with nmh-1.0.4 To: Jarkko Santala Cc: Andrew Gallatin , freebsd-alpha@FreeBSD.org Subject: Re: Still about ISA NICs on FreeBSD 4.5/alpha In-reply-to: <20020405084009.J61960-100000@trillian.santala.org> References: <20020405084009.J61960-100000@trillian.santala.org> Comments: In-reply-to Jarkko Santala message dated "Fri, 05 Apr 2002 08:51:04 +0300." From: bmah@FreeBSD.org (Bruce A. Mah) Reply-To: bmah@FreeBSD.org X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Apr 2002 07:26:15 -0800 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org If memory serves me right, Jarkko Santala wrote: > On Thu, 4 Apr 2002, Andrew Gallatin wrote: > > > Nobody else has tried to run most ISA nics on anything but x86. > > That's why they are not in the alpha GENERIC kernel. You're tredding > > on new ground here. Your initial problems are configuration related. > > Expect to have more problems once you get the drivers building. > > Ahaa, that explains a lot. ;) Using your instructions I was able to > compile ep, ex and fe0 into the kernel. Now I'll just have to find a > suitable time to shutdown the server and test the cards. If and when you get these things working, can you drop me a note to make sure the {hardware,release} notes for the Alpha get updated appropriately? Thanks! Bruce. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Apr 5 9:25:54 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id E7F3737B405 for ; Fri, 5 Apr 2002 09:25:46 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g35HPjN57678 for freebsd-alpha@freebsd.org; Fri, 5 Apr 2002 19:25:45 +0200 (CEST) (envelope-from wkb) Date: Fri, 5 Apr 2002 19:25:45 +0200 From: Wilko Bulte To: freebsd-alpha@freebsd.org Subject: DEFPA / fddi borked on Alpha Message-ID: <20020405192545.A57660@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-OS: FreeBSD 4.5-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I just stuck a DEC DEFPA in my AS500 and another one in a K6 x86 box. Both are RELENG_4On the x86 this appears to work, on the Alpha I'm getting: isp0: port 0x10000-0x100ff mem 0x8006800 0-0x80068fff irq 12 at device 9.0 on pci0 isp0: interrupting at CIA irq 12 isab0: at device 10.0 on pci0 isa0: on isab0 pci0: at 11.0 irq 0 fpa0: port 0x10100-0x1017f mem 0x80040000-0x 8004ffff,0x80069000-0x8006907f irq 4 at device 12.0 on pci0 fatal kernel trap: trap entry = 0x2 (memory management fault) a0 = 0x80069014 a1 = 0x1 a2 = 0x0 pc = 0xfffffc000037bf98 ra = 0xfffffc000037bcd8 curproc = 0xfffffc0000635530 pid = 0, comm = swapper ddbprinttrap from 0xfffffc000037bf98 ddbprinttrap(0x80069014, 0x1, 0x0, 0x2) panic: trap panic Stopped at Debugger+0x2c: ldq ra,0(sp) <0xfffffc00006b7960> db> trace Debugger() at Debugger+0x2c panic() at panic+0x100 trap() at trap+0x620 XentMM() at XentMM+0x2c --- memory management fault (from ipl 6) --- pdq_initialize() at pdq_initialize+0x538 pdq_pci_attach() at pdq_pci_attach+0x150 pci_compat_attach() at pci_compat_attach+0x88 DEVICE_ATTACH() at DEVICE_ATTACH+0x5c device_probe_and_attach() at device_probe_and_attach+0x90 bus_generic_attach() at bus_generic_attach+0x28 DEVICE_ATTACH() at DEVICE_ATTACH+0x5c device_probe_and_attach() at device_probe_and_attach+0x90 bus_generic_attach() at bus_generic_attach+0x28 DEVICE_ATTACH() at DEVICE_ATTACH+0x5c device_probe_and_attach() at device_probe_and_attach+0x90 bus_generic_attach() at bus_generic_attach+0x28 cia_attach() at cia_attach+0x180 DEVICE_ATTACH() at DEVICE_ATTACH+0x5c device_probe_and_attach() at device_probe_and_attach+0x90 root_bus_configure() at root_bus_configure+0x38 configure() at configure+0x40 mi_startup() at mi_startup+0xf4 locorestart() at locorestart+0x68 --- root of call graph --- db> Ideas? -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Apr 5 9:41:10 2002 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 9705B37B478; Fri, 5 Apr 2002 09:40:43 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id MAA03192; Fri, 5 Apr 2002 12:40:42 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g35HeCt01248; Fri, 5 Apr 2002 12:40:12 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15533.57724.532779.255990@grasshopper.cs.duke.edu> Date: Fri, 5 Apr 2002 12:40:12 -0500 (EST) To: Wilko Bulte Cc: freebsd-alpha@FreeBSD.ORG, mdodd@FreeBSD.ORG Subject: Re: DEFPA / fddi borked on Alpha In-Reply-To: <20020405192545.A57660@freebie.xs4all.nl> References: <20020405192545.A57660@freebie.xs4all.nl> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Wilko Bulte writes: > I just stuck a DEC DEFPA in my AS500 and another one in a K6 x86 > box. Both are RELENG_4On the x86 this appears > to work, on the Alpha I'm getting: > > isp0: port 0x10000-0x100ff mem > 0x8006800 > 0-0x80068fff irq 12 at device 9.0 on pci0 > isp0: interrupting at CIA irq 12 > isab0: at device 10.0 on pci0 > isa0: on isab0 > pci0: at 11.0 irq 0 > fpa0: port 0x10100-0x1017f mem > 0x80040000-0x > 8004ffff,0x80069000-0x8006907f irq 4 at device 12.0 on pci0 > > fatal kernel trap: > > trap entry = 0x2 (memory management fault) > a0 = 0x80069014 Somebody is mapping the board without PCI_RF_DENSE or PCI_RF_BWX set & getting back the raw r_start address. I don't know why we don't just assume BWX or DENSE or something.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Apr 5 9:56:56 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from web14506.mail.yahoo.com (web14506.mail.yahoo.com [216.136.224.69]) by hub.freebsd.org (Postfix) with SMTP id 7980337B419 for ; Fri, 5 Apr 2002 09:56:54 -0800 (PST) Message-ID: <20020405175654.74560.qmail@web14506.mail.yahoo.com> Received: from [198.95.226.224] by web14506.mail.yahoo.com via HTTP; Fri, 05 Apr 2002 09:56:54 PST Date: Fri, 5 Apr 2002 09:56:54 -0800 (PST) From: Jeffrey Katcher Subject: Two Questions To: freebsd-alpha@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org 1. I just added a new disk drive to my XP1000. When I used sysinstall to partition/newfs lots and lots of "unaligned access" messages were printed. The action worked fine, but is this a concern? 2. What relatively modern video cards are people using with their Alphas to run XFree? I have a useless PowerStorm 300 (well it works as a VGA OK) that I'm going to replace. I was thinking about an ATI Rage 128 as being cheap with relatively good X performance and support. Many thanks in advance, Jeff Katcher __________________________________________________ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Apr 5 10:16:27 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by hub.freebsd.org (Postfix) with ESMTP id 4044737B41D; Fri, 5 Apr 2002 10:16:14 -0800 (PST) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.11.6/8.11.6) with ESMTP id g35IGAX23961; Fri, 5 Apr 2002 13:16:10 -0500 (EST) (envelope-from winter@jurai.net) Date: Fri, 5 Apr 2002 13:16:10 -0500 (EST) From: "Matthew N. Dodd" To: Andrew Gallatin Cc: Wilko Bulte , , Subject: Re: DEFPA / fddi borked on Alpha In-Reply-To: <15533.57724.532779.255990@grasshopper.cs.duke.edu> Message-ID: <20020405131512.M42854-100000@sasami.jurai.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 5 Apr 2002, Andrew Gallatin wrote: > Wilko Bulte writes: > > I just stuck a DEC DEFPA in my AS500 and another one in a K6 x86 > > box. Both are RELENG_4On the x86 this appears > > to work, on the Alpha I'm getting: > > > > isp0: port 0x10000-0x100ff mem > > 0x8006800 > > 0-0x80068fff irq 12 at device 9.0 on pci0 > > isp0: interrupting at CIA irq 12 > > isab0: at device 10.0 on pci0 > > isa0: on isab0 > > pci0: at 11.0 irq 0 > > fpa0: port 0x10100-0x1017f mem > > 0x80040000-0x > > 8004ffff,0x80069000-0x8006907f irq 4 at device 12.0 on pci0 > > > > fatal kernel trap: > > > > trap entry = 0x2 (memory management fault) > > a0 = 0x80069014 > > Somebody is mapping the board without PCI_RF_DENSE or PCI_RF_BWX set > & getting back the raw r_start address. I don't know why we don't > just assume BWX or DENSE or something.. I wonder if the stuff in -CURRENT would compile cleanly on -STABLE. I suspect it might. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Apr 5 10:36:44 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.dis.org (dhcp45-24.dis.org [216.240.45.24]) by hub.freebsd.org (Postfix) with ESMTP id 61CB237B417; Fri, 5 Apr 2002 10:36:34 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.6) with ESMTP id g35IYsS03825; Fri, 5 Apr 2002 10:34:55 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200204051834.g35IYsS03825@mass.dis.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Andrew Gallatin Cc: =?iso-8859-1?Q?=D8ystein_Andreassen?= , freebsd-alpha@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: Problem with MyLex KZPAC PCI RAID controller In-reply-to: Your message of "Wed, 03 Apr 2002 09:36:46 EST." <15531.4990.536630.145584@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Apr 2002 10:34:54 -0800 From: Michael Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The problem is a driver bug; the error from the controller is misleading, and I believe in reality it reflects a corrupt command being issued. Unfortunately, I have neither card nor controller to verify this with, and have been waiting for some enterprising individual to look at the failing command (printing it is relatively easy) and tell me what's wrong. There are no differences between the i386 and Alpha drivers; the same problem manifests on 2.xx and 3.xx firmware cards on i386 systems. > > =D8ystein Andreassen writes: > >=20 > > Hello, > >=20 > > I have tried to install FreeBSD 4.5 (Release(?)) on a Digital Server= > 5000 > > Model 5303 6533A. > > It has a MyLex KZPAC PCI RAID Controller. I manage to boot the CD an= > d > > everything seems fine until the file copying starts. > > When the copying is around 23% of / it comes to a complete halt and = > i get > > ALOT of errors like > > "mlx0: I/O error - attempt to write beyond end of drive" > > I've read the mailinglists and found that this was a problem in 4.3 = > (i386) > > (mailinglist "current", may 2001). > > So I tried to put the MyLex controller in an i386 machine. I still h= > ad the > > disks in the alpha. This worked fine! > >=20 > > I guess my question is: Why isn't the alpha driver updated while the= > i386 > > driver is? (I really hope that someone just forgot and it's VERY sim= > ple to > > fix!:) > > Its the same driver on all platforms. > > I'm a little out of my depth here, as I've never even seen a mylex > card. One WAG I have is that perhaps the alpha is storing the size of > the array someplace in the hosts firmware & when you moved the card to > a PC, that information was cleared? > > Drew -- To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. - Theodore Roosevelt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Apr 5 10:37:28 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.dis.org (dhcp45-24.dis.org [216.240.45.24]) by hub.freebsd.org (Postfix) with ESMTP id 0838037B41E; Fri, 5 Apr 2002 10:37:16 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.6) with ESMTP id g35IZkS03938; Fri, 5 Apr 2002 10:35:47 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200204051835.g35IZkS03938@mass.dis.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Wilko Bulte Cc: Andrew Gallatin , =?iso-8859-15?Q?=D8ystein_Andreassen?= , freebsd-alpha@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: Problem with MyLex KZPAC PCI RAID controller In-reply-to: Your message of "Wed, 03 Apr 2002 16:39:29 +0200." <20020403163929.A47435@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Fri, 05 Apr 2002 10:35:46 -0800 From: Michael Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > On Wed, Apr 03, 2002 at 09:36:46AM -0500, Andrew Gallatin wrote: > = > We used to have different firmware on the Mylex's for Intel and Alpha > based servers. Don't ask me why. There are a number of "preferential" behaviours and quirks for broken = disks that Mylex built into these controllers, however the major = difference is simply that the AXP controllers have no BIOS. -- = To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to = the American public. - Theodore Roosevelt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Apr 5 10:47:28 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id C4A0437B416 for ; Fri, 5 Apr 2002 10:47:15 -0800 (PST) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.2/8.12.2) with ESMTP id g35IUxYm047359; Fri, 5 Apr 2002 10:32:19 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.2/8.12.2/Submit) id g35ITijC047347; Fri, 5 Apr 2002 10:29:44 -0800 (PST) Date: Fri, 5 Apr 2002 10:29:44 -0800 From: "David O'Brien" To: Jeffrey Katcher Cc: freebsd-alpha@freebsd.org Subject: Re: Two Questions Message-ID: <20020405102944.A47315@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20020405175654.74560.qmail@web14506.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020405175654.74560.qmail@web14506.mail.yahoo.com>; from jmkatcher@yahoo.com on Fri, Apr 05, 2002 at 09:56:54AM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, Apr 05, 2002 at 09:56:54AM -0800, Jeffrey Katcher wrote: > 1. I just added a new disk drive to my XP1000. When I > used sysinstall to partition/newfs lots and lots of > "unaligned access" messages were printed. The action > worked fine, but is this a concern? Not a concern. Sysinstall is not well written for 64-bit platforms. This does not affect how you were able to `label' a new disk. > 2. What relatively modern video cards are people using > with their Alphas to run XFree? Matrox all the way baby! :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Apr 5 12:33:28 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from aromo.spock.cl (aromo.spock.cl [200.27.125.98]) by hub.freebsd.org (Postfix) with ESMTP id 97D8237B416 for ; Fri, 5 Apr 2002 12:33:18 -0800 (PST) Received: from aromo.spock.cl (aromo.spock.cl [200.27.125.98]) by aromo.spock.cl (8.11.1/8.9.3) with ESMTP id g35KXAT64662; Fri, 5 Apr 2002 16:33:10 -0400 (CLT) Date: Fri, 5 Apr 2002 16:33:10 -0400 (CLT) From: Roberto de Iriarte To: Jeffrey Katcher Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Two Questions In-Reply-To: <20020405175654.74560.qmail@web14506.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 5 Apr 2002, Jeffrey Katcher wrote: > 1. I just added a new disk drive to my XP1000. When I > used sysinstall to partition/newfs lots and lots of > "unaligned access" messages were printed. The action > worked fine, but is this a concern? > Not at all. Just ignore them. BTW, AFAIK it's sysinstall's user interface that is complaining, not the actual disklabel/newfs tools. > 2. What relatively modern video cards are people using > with their Alphas to run XFree? I have a useless > PowerStorm 300 (well it works as a VGA OK) that I'm > going to replace. I was thinking about an ATI Rage > 128 as being cheap with relatively good X performance > and support. > I have an Ati RAGE 128 pro PCI (16MB), and while it's happy with Xfree86 4.2, OpenGL support is lacking as of now. (I'm trying to get it to work, however). At least in theory, an old 3DFX card like the Voodoo 3/4/5 series should be a better bet to get some hardware 3D acceleration. Besides, i don't think there is a faster PCI graphics adaptor than the 3DFX voodoo 5 5500. You should be able to get one from EBAY for about US$ 100. > Many thanks in advance, > > Jeff Katcher > My .02 cents Roberto de Iriarte Spock S.A. BTW, are you happy with the XP1000' performance? I am thinking about getting one or perhaps a DS20 (expen$ive) to replace my trusty DS3305, but with alphas dying, i should perhaps move over to PowerPC or Sparc ?! What do you think ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Apr 5 13:21:48 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 120AC37B420; Fri, 5 Apr 2002 13:21:37 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g35LLai58489; Fri, 5 Apr 2002 23:21:36 +0200 (CEST) (envelope-from wkb) Date: Fri, 5 Apr 2002 23:21:36 +0200 From: Wilko Bulte To: Michael Smith Cc: Andrew Gallatin , =?iso-8859-15?Q?=D8ystein_Andreassen?= , freebsd-alpha@FreeBSD.ORG Subject: Re: Problem with MyLex KZPAC PCI RAID controller Message-ID: <20020405232136.D58357@freebie.xs4all.nl> References: <20020403163929.A47435@freebie.xs4all.nl> <200204051835.g35IZkS03938@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200204051835.g35IZkS03938@mass.dis.org>; from msmith@FreeBSD.ORG on Fri, Apr 05, 2002 at 10:35:46AM -0800 X-OS: FreeBSD 4.5-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, Apr 05, 2002 at 10:35:46AM -0800, Michael Smith wrote: > > On Wed, Apr 03, 2002 at 09:36:46AM -0500, Andrew Gallatin wrote: > > > > We used to have different firmware on the Mylex's for Intel and Alpha > > based servers. Don't ask me why. > > There are a number of "preferential" behaviours and quirks for broken > disks that Mylex built into these controllers, however the major > difference is simply that the AXP controllers have no BIOS. OK. There used to be a time (dim, dark past) where the Mylex-for-Intel servers (out of the DEC PC business unit) had newer firmware than the ones for Alpha (out of the Storage Business unit). To complicate things the Storage business unit *also* had a Mylex for Intel-based servers that had different f/w again. Argh.. -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Apr 5 16:55:20 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from skywalker.systec.no (skywalker.systec.no [80.64.196.212]) by hub.freebsd.org (Postfix) with ESMTP id 3441537B404 for ; Fri, 5 Apr 2002 16:55:15 -0800 (PST) Received: from skywalker.systec.no (skywalker.systec.no [192.168.100.3]) by relay.systec.no (8.11.6/8.11.6) with ESMTP id g35EZjZ39547; Fri, 5 Apr 2002 16:35:47 +0200 (CEST) (envelope-from oystein.andreassen@systec.no) Received: by skywalker.systec.no with Internet Mail Service (5.5.2653.19) id ; Fri, 5 Apr 2002 16:29:25 +0200 Message-ID: From: =?iso-8859-1?Q?=D8ystein_Andreassen?= To: "'Roberto de Iriarte'" Cc: "FreeBSD Alpha (E-mail)" Subject: RE: Problem with MyLex KZPAC PCI RAID controller Date: Fri, 5 Apr 2002 16:29:24 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello! I'll try to tell you a little about the config, but if I leave = something out you have to ask (I'm new sorta to alpha:). The console version is v6.0-4 dated 10-MAY-2001 The controller's FW version is now 2.73 (updated this after I recived = you mail. Still the same problem though). From a 'show config' command i can read this about the controller: Name/type: MyLex DAC960 Slot:4 Type:14069 Rev:0002 I can also tell you the following: It is a KZPAC (DEC/Compaq's name for = the controller I think) / DAC960PU (MyLex' name for it) with 8 MB RAM. It = has 7x18,2 disks attached, 4x on ch0 and 3x on ch2. The RAID is configured = with the 2 first disks on ch0 in RAID1, the two next are hotspare and the = three disks on ch2 is a RAID5 with 32768MB configured. Controller options: Automatic Rebuild Management: Disabled Storageworks Fault Management: Disabled Rebuild Rate: 50 Controller Read Ahead: Disabled Stripe Size: 64K All 3 buses: -- Scsi Transfer Rate: 20MHz Command tagging: Enabled Scsi data bus width: 16Bit -- Disk spinup: Automatic Spin devices: 1 (Spin device) Delay: 6 In DOS the BIOS is version 1.41 dated 15 May 96 I have tried to update the firmware to 3.x but the controller only has = a 128K EEPROM. (I even tried to put another 128K from another controller = in the spare slot... Didn't work! :) Hmm...I think thats all... =D8ystein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Apr 6 13:48:39 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 1C42737B416; Sat, 6 Apr 2002 13:48:35 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g36LmVY68283; Sat, 6 Apr 2002 23:48:31 +0200 (CEST) (envelope-from wkb) Date: Sat, 6 Apr 2002 23:48:31 +0200 From: Wilko Bulte To: Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG, mdodd@FreeBSD.ORG Subject: Re: DEFPA / fddi borked on Alpha Message-ID: <20020406234831.A68269@freebie.xs4all.nl> References: <20020405192545.A57660@freebie.xs4all.nl> <15533.57724.532779.255990@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15533.57724.532779.255990@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Fri, Apr 05, 2002 at 12:40:12PM -0500 X-OS: FreeBSD 4.5-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, Apr 05, 2002 at 12:40:12PM -0500, Andrew Gallatin wrote: I'll get to testing this in a weeks time as I'm on a business trip the coming week. W/ > > Wilko Bulte writes: > > I just stuck a DEC DEFPA in my AS500 and another one in a K6 x86 > > box. Both are RELENG_4On the x86 this appears > > to work, on the Alpha I'm getting: > > > > isp0: port 0x10000-0x100ff mem > > 0x8006800 > > 0-0x80068fff irq 12 at device 9.0 on pci0 > > isp0: interrupting at CIA irq 12 > > isab0: at device 10.0 on pci0 > > isa0: on isab0 > > pci0: at 11.0 irq 0 > > fpa0: port 0x10100-0x1017f mem > > 0x80040000-0x > > 8004ffff,0x80069000-0x8006907f irq 4 at device 12.0 on pci0 > > > > fatal kernel trap: > > > > trap entry = 0x2 (memory management fault) > > a0 = 0x80069014 > > Somebody is mapping the board without PCI_RF_DENSE or PCI_RF_BWX set > & getting back the raw r_start address. I don't know why we don't > just assume BWX or DENSE or something.. > > Drew ---end of quoted text--- -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message