From owner-freebsd-alpha Sun Jul 16 0:58:35 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 6236F37BA24 for ; Sun, 16 Jul 2000 00:58:27 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13DjJi-000MPA-00 for freebsd-alpha@freebsd.org; Sun, 16 Jul 2000 07:58:26 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id JAA02666 for freebsd-alpha@freebsd.org; Sun, 16 Jul 2000 09:58:27 +0200 (CEST) (envelope-from wkb) Date: Sun, 16 Jul 2000 09:58:27 +0200 From: Wilko Bulte To: FreeBSD-alpha mailing list Subject: make release fail on 4.1-RC / alpha Message-ID: <20000716095827.B2600@freebie.demon.nl> Reply-To: wilko@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Something seems to have grown over the 1.44Mb size limit: Setting up /boot directory for kern floppy /R/stage/image.kern/kernel: Jul 16 04:26:34 miata /kernel: /mnt: optimizati on changed from SPACE to TIME Jul 16 04:26:34 miata /kernel: pid 95222 (cpio), uid 0 on /mnt: file system full Jul 16 04:26:34 miata /kernel: pid 95222 (cpio), uid 0 on /mnt: file system full 63.6% -- replaced with /R/stage/image.kern/kernel.gz sh -e /usr/src/release/scripts/doFS.sh /R/stage/floppies/kern.flp /R/stage /mnt 1440 /R/stage/image.kern 80000 fd1440 Warning: Block size restricts cylinders per group to 6. Warning: 1216 sector(s) in last cylinder unallocated /dev/rvnn0c: 2880 sectors in 1 cylinders of 1 tracks, 4096 sectors 1.4MB in 1 cyl groups (6 c/g, 12.00MB/g, 32 i/g) super-block backups (for fsck -b #) at: 32 /mnt: write failed, file system is full cpio: write error: No space left on device *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. real 289m33.220s user 194m17.175s sys 41m59.143s You have new mail in /var/mail/root bash-2.03# df bash-2.03# bash-2.03# bash-2.03# bash-2.03# bash-2.03# exit Script done on Sun Jul 16 09:52:42 2000 ^C This is 4.1-RC as of Saturday afternoon CET. W/ -- Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try" wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Jul 16 2:34: 7 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id B155A37B5C5 for ; Sun, 16 Jul 2000 02:34:04 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13DkoD-000NGm-00 for freebsd-alpha@freebsd.org; Sun, 16 Jul 2000 09:34:02 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id LAA03325 for freebsd-alpha@freebsd.org; Sun, 16 Jul 2000 11:33:53 +0200 (CEST) (envelope-from wkb) Date: Sun, 16 Jul 2000 11:33:53 +0200 From: Wilko Bulte To: FreeBSD-alpha mailing list Subject: Re: make release fail on 4.1-RC / alpha Message-ID: <20000716113353.A3311@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <20000716095827.B2600@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000716095827.B2600@freebie.demon.nl>; from wkb@freebie.demon.nl on Sun, Jul 16, 2000 at 09:58:27AM +0200 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Jul 16, 2000 at 09:58:27AM +0200, Wilko Bulte wrote: Duh... seems David got here first (I also want an EV6/667Mc... ;-) > Something seems to have grown over the 1.44Mb size limit: > > Setting up /boot directory for kern floppy > /R/stage/image.kern/kernel: Jul 16 04:26:34 miata /kernel: /mnt: > optimizati > on changed from SPACE to TIME > Jul 16 04:26:34 miata /kernel: pid 95222 (cpio), uid 0 on /mnt: file system -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Jul 16 5:22:16 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 10FA937BBC8; Sun, 16 Jul 2000 05:22:13 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e6GCM6Q03174 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Sun, 16 Jul 2000 14:22:09 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e6GCLSq32605; Sun, 16 Jul 2000 14:21:28 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id OAA14681; Sun, 16 Jul 2000 14:21:25 +0200 (CEST) (envelope-from ticso) Date: Sun, 16 Jul 2000 14:21:24 +0200 From: Bernd Walter To: Mike Smith Cc: dg@root.com, freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE Message-ID: <20000716142124.A14427@cicely8.cicely.de> References: <200007141707.KAA16976@implode.root.com> <200007142125.OAA05782@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200007142125.OAA05782@mass.osd.bsdi.com>; from msmith@FreeBSD.ORG on Fri, Jul 14, 2000 at 02:25:05PM -0700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jul 14, 2000 at 02:25:05PM -0700, Mike Smith wrote: > > >fxp is not supported on the Alpha, and known to be unreliable there. > > >Contact the maintainer or use a different card. FWIW, this actually > > >sounds like an issue that's been seen on x86 as well. > > > > It does? I've never heard of a bug report like this for x86 and in fact I'm > > not aware of any bugs in the driver for x86. > > It's been described many times, actually. It sounds a lot like a bad > interaction between either the card or the driver and the hub/switch at > the other end, however it's shown up on a reasonably regular basis. At least I can say that the card/switch is not the problem here. The card and the switch are fixed configured to 100M/full-duplex. There are several x86 FreeBSD hosts with fxp cards running at the same switch without any problems. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Jul 16 5:25:22 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 0648237BBC8; Sun, 16 Jul 2000 05:25:18 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e6GCP5Q03273 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Sun, 16 Jul 2000 14:25:07 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e6GCOTq32611; Sun, 16 Jul 2000 14:24:29 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id OAA14691; Sun, 16 Jul 2000 14:24:24 +0200 (CEST) (envelope-from ticso) Date: Sun, 16 Jul 2000 14:24:24 +0200 From: Bernd Walter To: Andrew Gallatin Cc: dg@root.com, mjacob@feral.com, Mike Smith , freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE Message-ID: <20000716142424.B14427@cicely8.cicely.de> References: <14703.24005.384580.704375@grasshopper.cs.duke.edu> <200007141908.MAA17583@implode.root.com> <14703.31808.282545.767536@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <14703.31808.282545.767536@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Fri, Jul 14, 2000 at 05:23:21PM -0400 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jul 14, 2000 at 05:23:21PM -0400, Andrew Gallatin wrote: > As for the bug. I can duplicate it I run both the sender & receiver > fairly hard, like 2 100Mb/tcp connections running in opposite > directions. When I do this, it looks like the xmit side locks up but > the recv. side is at least partially OK. And I'm still getting stats > updates. Looks like you are on the right way. I can download a big file to the host without any problems but cvsup gets the interface stoped quite soon. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Jul 16 8:34:55 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5D9E037B846; Sun, 16 Jul 2000 08:34:53 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id IAA22135; Sun, 16 Jul 2000 08:34:51 -0700 Date: Sun, 16 Jul 2000 08:34:54 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: wilko@FreeBSD.ORG Cc: FreeBSD-alpha mailing list Subject: Re: make release fail on 4.1-RC / alpha In-Reply-To: <20000716095827.B2600@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hmm. It worked for me the other day... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Jul 16 13:18: 1 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 8604637B6FB; Sun, 16 Jul 2000 13:17:53 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13DurD-0003Ag-00; Sun, 16 Jul 2000 20:17:47 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id WAA06155; Sun, 16 Jul 2000 22:11:42 +0200 (CEST) (envelope-from wkb) Date: Sun, 16 Jul 2000 22:11:42 +0200 From: Wilko Bulte To: Matthew Jacob Cc: wilko@freebsd.org, FreeBSD-alpha mailing list Subject: Re: make release fail on 4.1-RC / alpha Message-ID: <20000716221142.B6109@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <20000716095827.B2600@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Sun, Jul 16, 2000 at 08:34:54AM -0700 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Jul 16, 2000 at 08:34:54AM -0700, Matthew Jacob wrote: > > Hmm. It worked for me the other day... Cockpit error on my part.. forgot the: # If this is a -stable snapshot, then set #RELEASETAG=RELENG_4 I'd been trying to get -current to build but switched to 4.1-RC in the meantime. Sorry for the confusion. -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jul 17 0:53: 3 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from eel.radicalmedia.com (eel.radicalmedia.com [204.254.246.9]) by hub.freebsd.org (Postfix) with ESMTP id C98A737B90C for ; Mon, 17 Jul 2000 00:53:00 -0700 (PDT) (envelope-from phiber@eel.radicalmedia.com) Received: (from phiber@localhost) by eel.radicalmedia.com (8.9.3/8.9.3) id DAA08255 for freebsd-alpha@freebsd.org; Mon, 17 Jul 2000 03:52:58 -0400 (EDT) Date: Mon, 17 Jul 2000 03:52:57 -0400 From: Mark Abene To: freebsd-alpha@freebsd.org Subject: fix for libskey Message-ID: <20000717035257.W22774@radicalmedia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Please accept the following diff against libskey, which fixes the fact that it returned nonsensical results (e.g. from /usr/bin/key). It now works properly. Cheers, -Mark --- /usr/src/lib/libskey/skeysubr.c.orig Mon Jul 17 03:44:30 2000 +++ /usr/src/lib/libskey/skeysubr.c Mon Jul 17 03:45:00 2000 @@ -21,7 +21,7 @@ { char *buf; MDX_CTX md; - u_long results[4]; + u_int results[4]; unsigned int buflen; buflen = strlen(seed) + strlen(passwd); @@ -51,7 +51,7 @@ char *x; { MDX_CTX md; - u_long results[4]; + u_int results[4]; MDXInit(&md); MDXUpdate(&md,(unsigned char *)x,8); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jul 17 4:42: 1 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from nadja.cis.ibaraki.ac.jp (nadja.cis.ibaraki.ac.jp [157.80.87.69]) by hub.freebsd.org (Postfix) with ESMTP id 9066437B568 for ; Mon, 17 Jul 2000 04:41:55 -0700 (PDT) (envelope-from th@cis.ibaraki.ac.jp) Received: from cis.ibaraki.ac.jp (localhost [127.0.0.1]) by nadja.cis.ibaraki.ac.jp (8.9.3/8.9.3) with ESMTP id UAA79988 for ; Mon, 17 Jul 2000 20:40:53 +0900 (JST) (envelope-from th@cis.ibaraki.ac.jp) Message-ID: <3972F0C5.5582C90@cis.ibaraki.ac.jp> Date: Mon, 17 Jul 2000 20:40:53 +0900 From: Takeshi Hiyama Organization: Dept. of Comp. & Info. Sci.s, Ibaraki University X-Mailer: Mozilla 4.73C-ja [ja] (X11; I; FreeBSD 4.1-RC i386) X-Accept-Language: ja MIME-Version: 1.0 To: freebsd-alpha Subject: X won't work Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm using FreeBSD 4.0-STABLE on Digital Personal WorkStation 500au. Almost everything is working fine except XFree86. I don't know the name of this video card. Things that was printed on the card is Bt485AKHJ170 CIRRUS LOGIC CL-GD5429-86QC-C Does any one know is this able to run XFree86 on this card, or what video card can run XFree86? -- <><>o<><>O<><>o<><>O<><>o<><> HIYAMA Takeshi e-mail:th@cis.ibaraki.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jul 17 5:23:44 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from ripsport.aist.go.jp (ripsport.aist.go.jp [150.29.251.10]) by hub.freebsd.org (Postfix) with ESMTP id BEDE037B90F for ; Mon, 17 Jul 2000 05:23:41 -0700 (PDT) (envelope-from ynishimura@home.nimc.go.jp) Received: from rpsmtp1.aist.go.jp (rpsmtp1.aist.go.jp [150.29.254.30]) by ripsport.aist.go.jp (8.9.3/3.7W) with ESMTP id VAA22912; Mon, 17 Jul 2000 21:23:40 +0900 (JST) From: ynishimura@home.nimc.go.jp Received: from cmce2.nimc.go.jp (localhost [127.0.0.1]) by rpsmtp1.aist.go.jp (8.9.3/3.7W) with ESMTP id VAA16820; Mon, 17 Jul 2000 21:23:40 +0900 (JST) Received: from cmnotesx.nimc.go.jp ([150.29.144.81]) by cmce2.nimc.go.jp with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id 37XN12Z2; Mon, 17 Jul 2000 21:25:34 +0900 Received: by cmnotesx.nimc.go.jp(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id 4925691F.00448A1D ; Mon, 17 Jul 2000 21:28:38 +0900 X-Lotus-FromDomain: AIST To: Takeshi Hiyama Cc: freebsd-alpha Message-ID: <4925691F.00448894.00@cmnotesx.nimc.go.jp> Date: Mon, 17 Jul 2000 21:25:04 +0900 Subject: Re: X won't work Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 00/07/17 20:40, Takeshi Hiyama wrote: > > Bt485AKHJ170 > > CIRRUS LOGIC > CL-GD5429-86QC-C > > Does any one know is this able to run XFree86 on this card, > or what video card can run XFree86? > > -- > I am using Matrox milenium with DPW 600a with XFree86. And Netscape and xview is working with it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jul 17 9:45:39 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id CD1CC37B582 for ; Mon, 17 Jul 2000 09:45:32 -0700 (PDT) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JRVTVVTBBY0001V1@research.kpn.com> for freebsd-alpha@freebsd.org; Mon, 17 Jul 2000 18:45:30 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id <3G58KZ66>; Mon, 17 Jul 2000 18:45:30 +0100 Content-return: allowed Date: Mon, 17 Jul 2000 18:45:29 +0100 From: "Koster, K.J." Subject: RE: fxp0 hangs on a PC164 using STABLE To: 'FreeBSD Alpha mailing list' Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D76F9@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > For me that means that it must be removed from GENERIC and > documented as not working in HARDWARE.TXT for 4.1R > > Objections? > Well ... No. :-( I have that fxp-card for my playtime Alpha. I'd love to see that card supported. I'm glad others people on this list are showing interest too. No time for active development, but I hereby volunteer to test your fxp code for Alpha in any state that it's in. I have a x86 with the identical card, so I can do regression testing in the same go. :-) Kees Jan ================================================= TV is the worst of both worlds. It's not as good at words as radio is because the pictures are a distraction which demand attention, and it's not as good as cinema because the pictures are not nearly as good. Douglas Adams To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jul 17 19:37:33 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id D510C37B8CF; Mon, 17 Jul 2000 19:37:23 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id WAA19565; Mon, 17 Jul 2000 22:37:19 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id WAA44113; Mon, 17 Jul 2000 22:37:19 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 17 Jul 2000 22:37:19 -0400 (EDT) To: Bernd Walter Cc: dg@root.com, mjacob@feral.com, Mike Smith , freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE In-Reply-To: <20000716142424.B14427@cicely8.cicely.de> References: <14703.24005.384580.704375@grasshopper.cs.duke.edu> <200007141908.MAA17583@implode.root.com> <14703.31808.282545.767536@grasshopper.cs.duke.edu> <20000716142424.B14427@cicely8.cicely.de> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14707.48450.371071.494543@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bernd Walter writes: > On Fri, Jul 14, 2000 at 05:23:21PM -0400, Andrew Gallatin wrote: > > As for the bug. I can duplicate it I run both the sender & receiver > > fairly hard, like 2 100Mb/tcp connections running in opposite > > directions. When I do this, it looks like the xmit side locks up but > > the recv. side is at least partially OK. And I'm still getting stats > > updates. > > Looks like you are on the right way. > I can download a big file to the host without any problems but cvsup gets > the interface stoped quite soon. The problem is that the status & command field share a 32-bit word. The programming API of the eepro apparently requires that you update the status field of a transmit slot that you've given to the card. Since alphas can only operate on 32-bit chunks of memory, both the status & command fields are loaded into memory & operated on in registers when the following line of C is executed: /* * Advance the end of list forward. */ sc->cbl_last->cb_command &= ~FXP_CB_COMMAND_S; The race is caused by the card DMA'ing up the status at just the wrong time -- after it has been loaded into a register & before it has been written back. The old value of the status is written back, clobbering the status the card just DMA'ed up. The fact that the card has sent this frame is missed & the transmit engine appears to hang. I think I have a fix. It feels like overkill, but if the programming interface of the chip does not allow for something better why not just turn off DMA while we update cb_command? Can anybody having problems with fxp's please try the appended patch? Without this patch, I have a test case that can lock the xmitter in < 5 seconds 100% of the time. With the patch, I've been unable to get it to lock up using this test case. Can a PCI expert comment on its safety? Mike? Index: pci/if_fxp.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_fxp.c,v retrieving revision 1.77.2.4 diff -u -r1.77.2.4 if_fxp.c --- pci/if_fxp.c 2000/07/13 07:53:06 1.77.2.4 +++ pci/if_fxp.c 2000/07/18 02:07:04 @@ -527,6 +527,8 @@ callout_handle_init(&sc->stat_ch); + sc->dev = dev; + s = splimp(); /* @@ -535,6 +537,7 @@ val = pci_read_config(dev, PCIR_COMMAND, 2); val |= (PCIM_CMD_MEMEN|PCIM_CMD_BUSMASTEREN); pci_write_config(dev, PCIR_COMMAND, val, 2); + sc->cmd = val; /* * Map control/status registers. @@ -960,6 +963,7 @@ { struct fxp_softc *sc = ifp->if_softc; struct fxp_cb_tx *txp; + int s; /* * See if we need to suspend xmit until the multicast filter @@ -1052,10 +1056,24 @@ } txp->tx_threshold = tx_threshold; +#ifdef __alpha__ + /* + * Prevent the card from DMA'ing up the status while + * we update the command field. This could cause + * us to overwrite the completion status. + */ + s = splhigh(); + pci_write_config(sc->dev, PCIR_COMMAND, + (sc->cmd & ~PCIM_CMD_BUSMASTEREN), 2); +#endif /*alpha*/ /* * Advance the end of list forward. */ sc->cbl_last->cb_command &= ~FXP_CB_COMMAND_S; +#ifdef __alpha__ + pci_write_config(sc->dev, PCIR_COMMAND, sc->cmd, 2); + splx(s); +#endif /*alpha*/ sc->cbl_last = txp; /* Index: pci/if_fxpvar.h =================================================================== RCS file: /home/ncvs/src/sys/pci/if_fxpvar.h,v retrieving revision 1.9.2.1 diff -u -r1.9.2.1 if_fxpvar.h --- pci/if_fxpvar.h 2000/03/29 02:02:39 1.9.2.1 +++ pci/if_fxpvar.h 2000/07/18 02:03:50 @@ -48,6 +48,7 @@ struct resource *mem; /* resource descriptor for registers */ struct resource *irq; /* resource descriptor for interrupt */ void *ih; /* interrupt handler cookie */ + device_t dev; /* newbus device pointer */ #endif /* __NetBSD__ */ bus_space_tag_t sc_st; /* bus space tag */ bus_space_handle_t sc_sh; /* bus space handle */ @@ -68,6 +69,7 @@ int phy_primary_device; /* device type of primary PHY */ int phy_10Mbps_only; /* PHY is 10Mbps-only device */ int eeprom_size; /* size of serial EEPROM */ + u_long cmd; /* contents of pci CMD register */ }; /* Macros to ease CSR access. */ Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 0: 7:23 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id CA55437BC79; Tue, 18 Jul 2000 00:07:19 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id XAA27563; Mon, 17 Jul 2000 23:53:36 -0700 (PDT) Message-Id: <200007180653.XAA27563@implode.root.com> To: Andrew Gallatin Cc: Bernd Walter , mjacob@feral.com, Mike Smith , freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE In-reply-to: Your message of "Mon, 17 Jul 2000 22:37:19 EDT." <14707.48450.371071.494543@grasshopper.cs.duke.edu> From: David Greenman Reply-To: dg@root.com Date: Mon, 17 Jul 2000 23:53:36 -0700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >The problem is that the status & command field share a 32-bit word. >The programming API of the eepro apparently requires that you update >the status field of a transmit slot that you've given to the card. >Since alphas can only operate on 32-bit chunks of memory, both the >status & command fields are loaded into memory & operated on in >registers when the following line of C is executed: > > /* > * Advance the end of list forward. > */ > sc->cbl_last->cb_command &= ~FXP_CB_COMMAND_S; > >The race is caused by the card DMA'ing up the status at just the wrong >time -- after it has been loaded into a register & before it has been >written back. The old value of the status is written back, clobbering >the status the card just DMA'ed up. The fact that the card has sent >this frame is missed & the transmit engine appears to hang. I wonder - does the Alpha CPU have support for locked read-modify-write type operations? I'm thinking that perhaps that might be a better way to fix the problem. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org Manufacturer of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 0:12: 1 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 186EC37BAA2; Tue, 18 Jul 2000 00:11:57 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id AAA29639; Tue, 18 Jul 2000 00:11:48 -0700 Date: Tue, 18 Jul 2000 00:11:51 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: David Greenman Cc: Andrew Gallatin , Bernd Walter , Mike Smith , freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE In-Reply-To: <200007180653.XAA27563@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I wonder - does the Alpha CPU have support for locked read-modify-write > type operations? I'm thinking that perhaps that might be a better way to > fix the problem. Funny you should say that (see below) I'm a little unsure whether they guarantee interlocks against I/O devices. Basically it allows you to set a flag on an address and then later do a conditional store. If the lock is gone, that adress was modified, and the conditional fails- so you can cycle back and try again- kinda cool. From mjacob@feral.com Tue Jul 18 00:08:29 2000 Date: Mon, 17 Jul 2000 20:21:07 -0700 (PDT) From: Matthew Jacob To: Andrew Gallatin , Doug Rabson Subject: Re: fxp0 hangs on a PC164 using STABLE I'm a little uneasy about this. It's likely to make the FXP unhappy, to say the least. If you *do* use this, put memory barriers in before and after the the flag update. Doug, Drew- I'm not sure whether LDL_L/STL_C and LDQ_L/STQ_C are cognizant of I/O device accesses to memory or not- my green book sayeth not. It's possible not. It'd be preferrable, IMO, to write 5 lines of inline assembly code that use the load_locked && store_locked_conditional rather than hit the FXP over the head. Anybody else know? Or should we go ask Chris/Jason/Ross (I'm sure Ross'd know)? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 0:58:42 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from msw.onthenet.com.au (pulsar.OntheNet.com.au [203.10.89.92]) by hub.freebsd.org (Postfix) with ESMTP id 82D3A37B7EA; Tue, 18 Jul 2000 00:58:36 -0700 (PDT) (envelope-from tonyg@onthenet.com.au) Received: from lancia.onthenet.com.au (unverified) by msw.onthenet.com.au (Content Technologies SMTPRS 4.1.5) with ESMTP id ; Tue, 18 Jul 2000 17:58:27 +1000 Received: from OntheNet.com.au (quasar.nt.com.au [203.14.201.5]) by lancia.onthenet.com.au (8.9.3/8.9.3) with ESMTP id RAA44649; Tue, 18 Jul 2000 17:58:22 +1000 (EST) Message-ID: <39740E1D.7F2AF81D@OntheNet.com.au> Date: Tue, 18 Jul 2000 17:58:21 +1000 From: Tony Griffiths Organization: Network Technologies P/L X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: mjacob@feral.com Cc: David Greenman , Andrew Gallatin , Bernd Walter , Mike Smith , freebsd-alpha@freebsd.org Subject: Re: fxp0 hangs on a PC164 using STABLE References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob wrote: > > > > > I wonder - does the Alpha CPU have support for locked read-modify-write > > type operations? I'm thinking that perhaps that might be a better way to > > fix the problem. Yes... Ldx_L (Load x Locked) and Stx_C (Store x Conditional [on the lock being set]) > > Funny you should say that (see below) I'm a little unsure whether they > guarantee interlocks against I/O devices. Basically it allows you to set a > flag on an address and then later do a conditional store. If the lock is gone, > that adress was modified, and the conditional fails- so you can cycle back and > try again- kinda cool. I'm stretching my memory synapses here but I seem to remember that the actual 'lock' h/w was part of the memory subsystem and didn't really care who or what wrote to the cache block that was locked. Ie. The same or another cpu or a device DMA'ing to anywhere in the cache block would clear the 'lock' flag causing a STx_C to fail! > > >From mjacob@feral.com Tue Jul 18 00:08:29 2000 > Date: Mon, 17 Jul 2000 20:21:07 -0700 (PDT) > From: Matthew Jacob > To: Andrew Gallatin , Doug Rabson > Subject: Re: fxp0 hangs on a PC164 using STABLE > > I'm a little uneasy about this. It's likely to make the FXP unhappy, to say > the least. If you *do* use this, put memory barriers in before and after > the the flag update. > > Doug, Drew- I'm not sure whether LDL_L/STL_C and LDQ_L/STQ_C are cognizant of > I/O device accesses to memory or not- my green book sayeth not. It's possible > not. It'd be preferrable, IMO, to write 5 lines of inline assembly code that > use the load_locked && store_locked_conditional rather than hit the FXP over > the head. Anybody else know? Or should we go ask Chris/Jason/Ross (I'm sure > Ross'd know)? > > -matt > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > > ***************************************************************** > This email has been checked by the e-Sweeper Service > ***************************************************************** ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify postmaster@OntheNet.com.au This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 2:16:30 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 4CC9F37BCBA; Tue, 18 Jul 2000 02:16:25 -0700 (PDT) (envelope-from ticso@mail.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e6I9GFU03260 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Tue, 18 Jul 2000 11:16:17 +0200 (MET DST) Received: (from ticso@localhost) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) id e6I9Ffg39323; Tue, 18 Jul 2000 11:15:41 +0200 (CEST) Date: Tue, 18 Jul 2000 11:15:40 +0200 From: Bernd Walter To: Andrew Gallatin Cc: Bernd Walter , dg@root.com, mjacob@feral.com, Mike Smith , freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE Message-ID: <20000718111540.A39306@cicely7.cicely.de> References: <14703.24005.384580.704375@grasshopper.cs.duke.edu> <200007141908.MAA17583@implode.root.com> <14703.31808.282545.767536@grasshopper.cs.duke.edu> <20000716142424.B14427@cicely8.cicely.de> <14707.48450.371071.494543@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <14707.48450.371071.494543@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Mon, Jul 17, 2000 at 10:37:19PM -0400 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Jul 17, 2000 at 10:37:19PM -0400, Andrew Gallatin wrote: > Can anybody having problems with fxp's please try the appended patch? > Without this patch, I have a test case that can lock the xmitter in < > 5 seconds 100% of the time. With the patch, I've been unable to get > it to lock up using this test case. It seems to have solved my problem. -- 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 Jul 18 6:27:17 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 0BFFD37BDF0; Tue, 18 Jul 2000 06:27:10 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA26642; Tue, 18 Jul 2000 09:26:57 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id JAA45033; Tue, 18 Jul 2000 09:26:57 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 18 Jul 2000 09:26:57 -0400 (EDT) To: Tony Griffiths Cc: mjacob@feral.com, David Greenman , Bernd Walter , Mike Smith , freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE In-Reply-To: <39740E1D.7F2AF81D@OntheNet.com.au> References: <39740E1D.7F2AF81D@OntheNet.com.au> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14708.21581.689293.987109@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Tony Griffiths writes: > I'm stretching my memory synapses here but I seem to remember that the > actual 'lock' > h/w was part of the memory subsystem and didn't really care who or what > wrote to the > cache block that was locked. Ie. The same or another cpu or a device > DMA'ing to > anywhere in the cache block would clear the 'lock' flag causing a STx_C > to fail! > I thought of this, but the Green Book only seems to mention locking between CPUs, not as part of the memory subsystem. I then looked at the 21264 CPU manual. (http://ftp.digital.com/pub/Digital/info/semiconductor/literature/21264hrm.pdf) Paraphrasing from page 4-14, it says that when a load-lock instruction exectutes, it loads the data from the D-cache; if there is a miss, its associated cache line is filled in a clean state. When the store-conditional instruction executes, it is allowed to succeed if the associated cache line is still in the D-cache and can be made writable. This works because something else writing to the same cache line would make it invalid in the Dcache. Sure enough, the following patch works on a UP1000 (21164A). However, I'm uncertain about other CPUs. In particular, the 21164's description is more complex & I don't really understand it. Bernd -- Can you try this new patch on your machine (you have a 21164, right?): Index: pci/if_fxp.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_fxp.c,v retrieving revision 1.77.2.4 diff -u -r1.77.2.4 if_fxp.c --- pci/if_fxp.c 2000/07/13 07:53:06 1.77.2.4 +++ pci/if_fxp.c 2000/07/18 13:24:39 @@ -1051,11 +1051,25 @@ ifp->if_timer = 5; } txp->tx_threshold = tx_threshold; - + /* * Advance the end of list forward. */ + +#ifdef __alpha__ + /* + * On platforms which can't access memory in 16-bit + * granularities, we must prevent the card from DMA'ing + * up the status while we update the command field. + * This could cause us to overwrite the completion status. + */ + atomic_clear_short(&sc->cbl_last->cb_command, + FXP_CB_COMMAND_S); +#else + sc->cbl_last->cb_command &= ~FXP_CB_COMMAND_S; +#endif /* __alpha__ */ + sc->cbl_last = txp; /* Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 10:20:27 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 032B337B887 for ; Tue, 18 Jul 2000 10:20:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id KAA86663; Tue, 18 Jul 2000 10:20:05 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from krowa.astercity.net (krowa.astercity.net [212.76.33.33]) by hub.freebsd.org (Postfix) with ESMTP id D524537B94C for ; Tue, 18 Jul 2000 10:15:11 -0700 (PDT) (envelope-from madej@krowa.astercity.net) Received: (from root@localhost) by krowa.astercity.net (8.9.3/8.9.3) id TAA18400; Tue, 18 Jul 2000 19:15:04 +0200 (CEST) (envelope-from madej) Message-Id: <200007181715.TAA18400@krowa.astercity.net> Date: Tue, 18 Jul 2000 19:15:04 +0200 (CEST) From: root@krowa.astercity.net Reply-To: root@krowa.astercity.net To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: alpha/20011: trap entry = 0x2 (memory management fault) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 20011 >Category: alpha >Synopsis: trap entry = 0x2 (memory management fault) >Confidential: yes >Severity: critical >Priority: high >Responsible: freebsd-alpha >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jul 18 10:20:05 PDT 2000 >Closed-Date: >Last-Modified: >Originator: Charlie & >Release: FreeBSD 4.0-RELEASE alpha >Organization: >Environment: Jul 18 17:30:23 krowa /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Jul 18 17:30:23 krowa /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Jul 18 17:30:23 krowa /kernel: The Regents of the University of California. All rights reserved. Jul 18 17:30:23 krowa /kernel: FreeBSD 4.0-RELEASE #0: Mon Jul 17 15:20:35 CEST 2000 Jul 18 17:30:23 krowa /kernel: root@foo.acn.pl:/usr/src/sys/compile/KROWA Jul 18 17:30:23 krowa /kernel: ST6600 Jul 18 17:30:23 krowa /kernel: AlphaServer DS20 500 MHz, 500MHz Jul 18 17:30:23 krowa /kernel: 8192 byte page size, 1 processor. Jul 18 17:30:23 krowa /kernel: CPU: EV6 (21264) major=8 minor=7 extensions=0x303 Jul 18 17:30:23 krowa /kernel: OSF PAL rev: 0x200370002013e Jul 18 17:30:23 krowa /kernel: real memory = 534142976 (521624K bytes) Jul 18 17:30:23 krowa /kernel: avail memory = 514400256 (502344K bytes) Jul 18 17:30:23 krowa /kernel: Preloaded elf kernel "kernel" at 0xfffffc00006d0000. Jul 18 17:30:23 krowa /kernel: md0: Malloc disk Jul 18 17:30:23 krowa /kernel: pcib0: <21271 PCI host bus adapter> on tsunami0 Jul 18 17:30:23 krowa /kernel: pci0: on pcib0 Jul 18 17:30:23 krowa /kernel: isab0: at device 5.0 on pci0 Jul 18 17:30:23 krowa /kernel: isa0: on isab0 Jul 18 17:30:23 krowa /kernel: atapci0: port 0x2080-0x208f,0x3f4-0x3f7,0x1f0-0x1f7 irq 238 at device 5.1 on pci0 Jul 18 17:30:23 krowa /kernel: atapci1: port 0x374-0x377,0x170-0x177 irq 239 at device 5.2 on pci0 Jul 18 17:30:23 krowa /kernel: atapci1: Busmastering DMA not supported Jul 18 17:30:23 krowa /kernel: pci0: at 5.3 irq 234 Jul 18 17:30:23 krowa /kernel: pci0: at 7.0 irq 31 Jul 18 17:30:23 krowa /kernel: pcib2: at device 8.0 on pci0 Jul 18 17:30:23 krowa /kernel: pci2: on pcib2 Jul 18 17:30:23 krowa /kernel: sym0: <875> port 0x1000-0x10ff mem 0x2060000-0x2060fff,0x2062000-0x20620ff irq 27 at device 0.0 on pci2 Jul 18 17:30:23 krowa /kernel: sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking Jul 18 17:30:23 krowa /kernel: sym0: open drain IRQ line driver, using on-chip SRAM Jul 18 17:30:23 krowa /kernel: sym0: interrupting at TSUNAMI irq 27 Jul 18 17:30:23 krowa /kernel: sym1: <875> port 0x1400-0x14ff mem 0x2061000-0x2061fff,0x2062100-0x20621ff irq 26 at device 1.0 on pci2 Jul 18 17:30:23 krowa /kernel: sym1: Symbios NVRAM, ID 7, Fast-20, SE, parity checking Jul 18 17:30:23 krowa /kernel: sym1: open drain IRQ line driver, using on-chip SRAM Jul 18 17:30:23 krowa /kernel: sym1: interrupting at TSUNAMI irq 26 Jul 18 17:30:23 krowa /kernel: de0: port 0x1800-0x187f mem 0x2062200-0x206227f irq 25 at device 2.0 on pci2 Jul 18 17:30:23 krowa /kernel: de0: interrupting at TSUNAMI irq 25 Jul 18 17:30:23 krowa /kernel: de0: 21140A [10-100Mb/s] pass 2.2 Jul 18 17:30:23 krowa /kernel: de0: address 00:06:2b:00:d0:de Jul 18 17:30:23 krowa /kernel: de0: supplying EUI64: 00:06:2b:ff:fe:00:d0:de Jul 18 17:30:23 krowa /kernel: de0: driver is using old-style compatability shims Jul 18 17:30:23 krowa /kernel: dc0: port 0x2000-0x207f mem 0x2181000-0x218107f irq 23 at device 9.0 on pci0 Jul 18 17:30:23 krowa /kernel: dc0: interrupting at TSUNAMI irq 23 Jul 18 17:30:23 krowa /kernel: dc0: Ethernet address: 08:00:2b:c4:a1:f0 Jul 18 17:30:23 krowa /kernel: miibus0: on dc0 Jul 18 17:30:23 krowa /kernel: dcphy0: on miibus0 Jul 18 17:30:23 krowa /kernel: dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Jul 18 17:30:23 krowa /kernel: pcib1: <21271 PCI host bus adapter> on tsunami0 Jul 18 17:30:24 krowa /kernel: pci1: on pcib1 Jul 18 17:30:24 krowa /kernel: dc1: port 0x80010000-0x8001007f mem 0x81048000-0x8104807f irq 47 at device 7.0 on pci1 Jul 18 17:30:24 krowa /kernel: dc1: interrupting at TSUNAMI irq 47 Jul 18 17:30:24 krowa /kernel: dc1: Ethernet address: 08:00:2b:c4:54:cf Jul 18 17:30:24 krowa /kernel: miibus1: on dc1 Jul 18 17:30:24 krowa /kernel: dcphy1: on miibus1 Jul 18 17:30:24 krowa /kernel: dcphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Jul 18 17:30:24 krowa /kernel: pci1: (vendor=0x1069, dev=0x0001) at 8.0 irq 43 Jul 18 17:30:24 krowa /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Jul 18 17:30:24 krowa /kernel: fdc0: interrupting at ISA irq 6 Jul 18 17:30:24 krowa /kernel: fdc0: FIFO enabled, 8 bytes threshold Jul 18 17:30:24 krowa /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Jul 18 17:30:24 krowa /kernel: atkbdc0: at port 0x60-0x6f on isa0 Jul 18 17:30:24 krowa /kernel: atkbd0: irq 1 on atkbdc0 Jul 18 17:30:24 krowa /kernel: atkbd0: interrupting at ISA irq 1 Jul 18 17:30:24 krowa /kernel: psm0: irq 12 on atkbdc0 Jul 18 17:30:24 krowa /kernel: psm0: model Generic PS/2 mouse, device ID 0 Jul 18 17:30:24 krowa /kernel: psm0: interrupting at ISA irq 12 Jul 18 17:30:24 krowa /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Jul 18 17:30:24 krowa /kernel: sc0: on isa0 Jul 18 17:30:24 krowa /kernel: sc0: VGA <16 virtual consoles, flags=0x0> Jul 18 17:30:24 krowa /kernel: mcclock0: at port 0x70-0x71 on isa0 Jul 18 17:30:24 krowa /kernel: sio0 at port 0x3f8-0x3ff irq 4 on isa0 Jul 18 17:30:24 krowa /kernel: sio0: type 16550A, console Jul 18 17:30:24 krowa /kernel: sio0: interrupting at ISA irq 4 Jul 18 17:30:24 krowa /kernel: sio1: reserved for low-level i/o Jul 18 17:30:24 krowa /kernel: Timecounter "alpha" frequency 499874820 Hz Jul 18 17:30:24 krowa /kernel: IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry by default Jul 18 17:30:24 krowa /kernel: DUMMYNET initialized (000106) Jul 18 17:30:24 krowa /kernel: IPsec: Initialized Security Association Processing. Jul 18 17:30:24 krowa /kernel: IPv6 packet filtering initialized, default to accept, logging limited to 100 packets/entry Jul 18 17:30:24 krowa /kernel: IP Filter: initialized. Default = pass all, Logging = enabled Jul 18 17:30:24 krowa /kernel: IP Filter: v3.3.8 Jul 18 17:30:24 krowa /kernel: Waiting 15 seconds for SCSI devices to settle Jul 18 17:30:24 krowa /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. Jul 18 17:30:24 krowa /kernel: (noperiph:sym1:0:-1:-1): SCSI BUS reset delivered. Jul 18 17:30:24 krowa /kernel: de0: enabling Full Duplex 100baseTX port Jul 18 17:30:24 krowa /kernel: Mounting root from ufs:/dev/da0a Jul 18 17:30:24 krowa /kernel: da3 at sym1 bus 0 target 0 lun 0 Jul 18 17:30:24 krowa /kernel: da3: Fixed Direct Access SCSI-2 device Jul 18 17:30:24 krowa /kernel: da3: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Jul 18 17:30:24 krowa /kernel: da3: 8678MB (17773524 512 byte sectors: 255H 63S/T 1106C) Jul 18 17:30:24 krowa /kernel: da6 at sym1 bus 0 target 3 lun 0 Jul 18 17:30:24 krowa /kernel: da6: Fixed Direct Access SCSI-2 device Jul 18 17:30:24 krowa /kernel: da6: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Jul 18 17:30:24 krowa /kernel: da6: 8678MB (17773524 512 byte sectors: 255H 63S/T 1106C) Jul 18 17:30:24 krowa /kernel: da5 at sym1 bus 0 target 2 lun 0 Jul 18 17:30:24 krowa /kernel: da5: Fixed Direct Access SCSI-2 device Jul 18 17:30:24 krowa /kernel: da5: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Jul 18 17:30:24 krowa /kernel: da5: 8678MB (17773524 512 byte sectors: 255H 63S/T 1106C) Jul 18 17:30:24 krowa /kernel: da4 at sym1 bus 0 target 1 lun 0 Jul 18 17:30:24 krowa /kernel: da4: Fixed Direct Access SCSI-2 device Jul 18 17:30:24 krowa /kernel: da4: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Jul 18 17:30:24 krowa /kernel: da4: 8678MB (17773524 512 byte sectors: 255H 63S/T 1106C) Jul 18 17:30:24 krowa /kernel: da2 at sym0 bus 0 target 2 lun 0 Jul 18 17:30:24 krowa /kernel: da2: Fixed Direct Access SCSI-2 device Jul 18 17:30:24 krowa /kernel: da2: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Jul 18 17:30:24 krowa /kernel: da2: 8678MB (17773524 512 byte sectors: 255H 63S/T 1106C) Jul 18 17:30:24 krowa /kernel: da1 at sym0 bus 0 target 1 lun 0 Jul 18 17:30:25 krowa /kernel: da1: Fixed Direct Access SCSI-2 device Jul 18 17:30:25 krowa /kernel: da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Jul 18 17:30:25 krowa /kernel: da1: 8678MB (17773524 512 byte sectors: 255H 63S/T 1106C) Jul 18 17:30:25 krowa /kernel: da0 at sym0 bus 0 target 0 lun 0 Jul 18 17:30:25 krowa /kernel: da0: Fixed Direct Access SCSI-2 device Jul 18 17:30:25 krowa /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Jul 18 17:30:25 krowa /kernel: da0: 8678MB (17773524 512 byte sectors: 255H 63S/T 1106C) Jul 18 17:30:25 krowa /kernel: cd0 at sym0 bus 0 target 5 lun 0 Jul 18 17:30:25 krowa /kernel: cd0: Removable CD-ROM SCSI-2 device Jul 18 17:30:25 krowa /kernel: cd0: 10.000MB/s transfers (10.000MHz, offset 16) Jul 18 17:30:25 krowa /kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present Jul 18 17:30:25 krowa /kernel: WARNING: / was not properly dismounted Jul 18 17:30:25 krowa /kernel: de0: enabling 100baseTX port Jul 18 17:30:25 krowa /kernel: de0: enabling Full Duplex 100baseTX port >Description: Jul 18 17:30:22 krowa /kernel: Jul 18 17:30:22 krowa /kernel: fatal kernel trap: Jul 18 17:30:22 krowa /kernel: Jul 18 17:30:22 krowa /kernel: trap entry = 0x2 (memory management fault) Jul 18 17:30:22 krowa /kernel: a0 = 0x40 Jul 18 17:30:22 krowa /kernel: a1 = 0x1 Jul 18 17:30:22 krowa /kernel: a2 = 0x0 Jul 18 17:30:22 krowa /kernel: pc = 0xfffffc000043c874 Jul 18 17:30:22 krowa /kernel: ra = 0xfffffc000043c82c Jul 18 17:30:22 krowa /kernel: curproc = 0 Jul 18 17:30:22 krowa /kernel: Jul 18 17:30:22 krowa /kernel: panic: trap Jul 18 17:30:22 krowa /kernel: Jul 18 17:30:22 krowa /kernel: syncing disks... Jul 18 17:30:23 krowa /kernel: fatal kernel trap: Jul 18 17:30:23 krowa /kernel: Jul 18 17:30:23 krowa /kernel: trap entry = 0x2 (memory management fault) Jul 18 17:30:23 krowa /kernel: a0 = 0x30 Jul 18 17:30:23 krowa /kernel: a1 = 0x1 Jul 18 17:30:23 krowa /kernel: a2 = 0x0 Jul 18 17:30:23 krowa /kernel: pc = 0xfffffc00004ed428 Jul 18 17:30:23 krowa /kernel: ra = 0xfffffc00004ed3f4 Jul 18 17:30:23 krowa /kernel: curproc = 0 Jul 18 17:30:23 krowa /kernel: Jul 18 17:30:23 krowa /kernel: panic: trap Jul 18 17:30:23 krowa /kernel: Uptime: 5h26m3s >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 10:40: 4 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 2EDD037B6AE for ; Tue, 18 Jul 2000 10:40:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id KAA89363; Tue, 18 Jul 2000 10:40:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Tue, 18 Jul 2000 10:40:02 -0700 (PDT) Message-Id: <200007181740.KAA89363@freefall.freebsd.org> To: freebsd-alpha@freebsd.org Cc: From: Matthew Jacob Subject: Re: alpha/20011: trap entry = 0x2 (memory management fault) Reply-To: Matthew Jacob Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR alpha/20011; it has been noted by GNATS. From: Matthew Jacob To: root@krowa.astercity.net Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: alpha/20011: trap entry = 0x2 (memory management fault) Date: Tue, 18 Jul 2000 10:31:57 -0700 (PDT) You need to give a bit more information if you can. This is a kernel you've built (root@foo.acn.pl:/usr/src/sys/compile/KROWA). Use nm to tell us what corresponds to the pc and ra values in the trap message. Better yet, build with options DDB and when it panics, type t to get a stack trace. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 10:41:35 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id C6A9337B9CE for ; Tue, 18 Jul 2000 10:41:32 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13EbN5-000HpB-00 for freebsd-alpha@freebsd.org; Tue, 18 Jul 2000 17:41:31 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id TAA02084 for freebsd-alpha@freebsd.org; Tue, 18 Jul 2000 19:41:05 +0200 (CEST) (envelope-from wkb) Date: Tue, 18 Jul 2000 19:41:05 +0200 From: Wilko Bulte To: FreeBSD-alpha mailing list Subject: test results (or rather lack thereof) for 4.1RC on Rawhide (AS4100) Message-ID: <20000718194105.A2056@freebie.demon.nl> Reply-To: wilko@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Question: has anybody had any success recently booting 4.1RC or 4.0stable on a AS4100? I have tried two different AS4100 with known-good boot floppies and both lockup with something like: Booting kernel / (note the /, it just freezes). Boot from CD does not seem to work on any Alpha that I tried it on at the moment :-( -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 10:41:46 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id B168637B9D1 for ; Tue, 18 Jul 2000 10:41:34 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13EbN6-000HpB-00; Tue, 18 Jul 2000 17:41:33 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id TAA02022; Tue, 18 Jul 2000 19:35:36 +0200 (CEST) (envelope-from wkb) Date: Tue, 18 Jul 2000 19:35:36 +0200 From: Wilko Bulte To: FreeBSD-alpha mailing list Cc: Andrew Gallatin Subject: testresults for 4.1RC on Sable (AS2100) Message-ID: <20000718193536.A1996@freebie.demon.nl> Reply-To: wilko@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.2i X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org FYI: Sable seems to install OK on my homegrown-41RC (except for a bad block on the CDRW in the bindist. Grrrr.) In case somebody wants me to test anything particular please let me know W/ Script started on Tue Jul 18 15:15:02 2000 wilklt#tip a VMS PALcode V5.56-7=00=00=00=00, OSF PALcode V1.45-12 P00>>>sho conf Digital Equipment Corporation AlphaServer 2100 4/200 SRM Console V5.3-2 VMS PALcode V5.56-7, OSF PALcode V1.45-12 Component Status Module ID CPU 0 P B2020-AA DECchip (tm) 21064-3 Memory 0 P B2021-CA 128 MB I/O B2110-AA dva0.0.0.0.1 RX26/RX23 Slot Option Hose 0, Bus 0, PCI 0 DECchip 21040-AA ewa0.0.0.0.0 08-00-2B-E2-84-04 1 NCR 53C810 pka0.7.0.1.0 SCSI Bus ID 7 dka0.0.0.1.0 RZ29B dka600.6.0.1.0 RRD43 2 Intel 82375 Bridge to Hose 1, EISA Slot Option Hose 1, EISA 2 Compaq Qvision =09 P00>>> P00>>>boot =08 =08=08 =08=08 =08=08 =08=08 =08\ _> P00>>> P00>>> P00>>>sho dev dka0.0.0.1.0 DKA0 RZ29B 0014 dka600.6.0.1.0 DKA600 RRD43 1084 dva0.0.0.0.1 DVA0 RX26/RX23 ewa0.0.0.0.0 EWA0 08-00-2B-E2-84-04 pka0.7.0.1.0 PKA0 SCSI Bus ID 7 P00>>>boot dva0 (boot dva0.0.0.0.1 -flags a) block 0 of dva0.0.0.0.1 is a valid boot block reading 15 blocks from dva0.0.0.0.1 bootstrap code read in base =3D 200000, image_start =3D 0, image_bytes =3D 1e00 initializing HWRPB at 2000 initializing page table at 7ff0000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code VMS PAL rev: 0x4000700010538 OSF PAL rev: 0x4000c0002012d Switch to OSF PAL code succeeded. FreeBSD/alpha SRM disk boot, Revision 0.3 (root@miata.wbnet, Sun Jul 16 17:19:42 GMT 2000) Memory: 131072 k Please insert MFS root floppy and press enter: Entering kernel at 0xfffffc00003297e0... Copyright (c) 1992-2000 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 41rc-16jul #0: Sun Jul 16 19:24:36 GMT 2000 root@miata.wbnet:/usr/src/sys/compile/BOOTMFS DEC AlphaServer 2100 AlphaServer 2100 4/200, 190MHz 8192 byte page size, 1 processor. CPU: EV4 (21064) major=3D2 minor=3D1 OSF PAL rev: 0x4000c0002012d real memory =3D 132046848 (128952K bytes) avail memory =3D 120553472 (117728K bytes) Preloaded elf kernel "kernel" at 0xfffffc00008fe000. Preloaded mfs_root "/mfsroot" at 0xfffffc00008fe0a0. md0: Preloaded image 2949120 bytes at 0xfffffc000062b410 md1: Malloc disk pci0: on pcib0 de0: port 0x10100-0x1017f mem 0x81000100-0x8100017= f irq 34 at device 0.0 on pci0 de0: interrupting at T2 irq 34 de0: DEC 21040 [10Mb/s] pass 2.3 de0: address 08:00:2b:e2:84:04 sym0: <810> port 0x10000-0x100ff mem 0x81000000-0x810000ff irq 33 at device= 1.0 on pci0 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking sym0: interrupting at T2 irq 33 isab0: at device 2.0 on pci0 isa0: on isab0 pci0: (vendor=3D0x0001, dev=3D0x0000) at 12.0 irq 32 pci0: (vendor=3D0x0000, dev=3D0x0000) at 12.4 pci0: (vendor=3D0x0001, dev=3D0x0000) at 13.0 irq 32 pci0: (vendor=3D0x0000, dev=3D0x0000) at 13.4 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: interrupting at T2 irq 6 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 atkbd0: interrupting at T2 irq 1 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=3D0x0> mcclock0: at port 0x70-0x71 on isa0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A, console sio0: interrupting at T2 irq 4 sio1: reserved for low-level i/o Timecounter "alpha" frequency 190019628 Hz Waiting 15 seconds for SCSI devices to settle de0: autosense failed: cable problem? Mounting root from ufs:/dev/md0c cd0 at sym0 bus 0 target 2 lun 0 cd0: Removable CD-ROM SCSI-2 device=20 cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: cd present [295960 x 512 byte records] da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device=20 da0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da0: 4091MB (8380080 512 byte sectors: 255H 63S/T 521C) cd1 at sym0 bus 0 target 6 lun 0 cd1: Removable CD-ROM SCSI-2 device=20 cd1: 4.166MB/s transfers (4.166MHz, offset 8) cd1: Attempt to query device size failed: NOT READY,=20 /stand/sysinstall running as init on serial console These are the predefined terminal types available to sysinstall when running stand-alone. Please choose the closest match for your particular terminal. 1 ...................... Standard ANSI terminal. 2 ...................... VT100 or compatible terminal. 3 ...................... FreeBSD system console (color). 4 ...................... FreeBSD system console (monochrome). Script done on Tue Jul 18 15:56:59 2000 --=20 Wilko Bulte http://www.freebsd.org =20 wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 10:41:53 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 4812737BB69 for ; Tue, 18 Jul 2000 10:41:36 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13EbN8-000HpB-00; Tue, 18 Jul 2000 17:41:34 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id TAA02047; Tue, 18 Jul 2000 19:37:08 +0200 (CEST) (envelope-from wkb) Date: Tue, 18 Jul 2000 19:37:08 +0200 From: Wilko Bulte To: Andrew Gallatin Cc: FreeBSD-alpha mailing list Subject: test results for Lynx (AS2100A) Message-ID: <20000718193708.A2031@freebie.demon.nl> Reply-To: wilko@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Below the results of booting 4.1-RC on a Lynx (AS2100A). Works reasonably well, but locks up/waits forever after printing 'waiting 15 secs for SCSI devices to settle'. Any ideas? Maybe interrupts don't get thru? (wild guess). Test boot floppies can be pulled over for test, I have the Lynx wednesday & thursday available.. Wilko --------- Script started on Tue Jul 18 14:45:39 2000 wilklt#tip a connected P00>>>sho conf Digital Equipment Corporation AlphaServer 2100A 4/200 SRM Console V5.3-10 VMS PALcode V5.56-7, OSF PALcode V1.45-12 Component Status Module ID CPU 0 P B2020-AA DECchip (tm) 21064-3 Memory 0 P B2021-CA 128 MB I/O B2222-AA dva0.0.0.1000.0 RX26/RX23 Slot Option Hose 0, Bus 0, PCI 2 Intel 82375 Bridge to Bus 1, EISA 3 DECchip 21050-AA Bridge to Bus 2, PCI 7 DECchip 21040-AA ewa0.0.0.7.0 00-00-F8-23-16-31 9 QLogic ISP1020 pkb0.7.0.9.0 SCSI Bus ID 7 dkb0.0.0.9.0 RZ29B dkb600.6.0.9.0 RRD46 Slot Option Hose 0, Bus 1, EISA 1 Compaq Qvision 3 Mylex DAC960 dra.0.0.1003.0 dra0.0.0.1003.0 5 Member RAID 5 Slot Option Hose 0, Bus 2, PCI 1 NCR 53C810 pka0.7.0.2001.0 SCSI Bus ID 7 dka600.6.0.2001.0 RRD43 6 Mylex DAC960 drb.0.0.2006.0 drb0.0.0.2006.0 2 Member RAID 1 drb1.0.0.2006.0 2 Member RAID 1 drb2.0.0.2006.0 2 Member RAID 1 P00>>>sho auto_action HALT boot_dev drb0.0.0.2006.0 boot_file boot_osflags 0,0 boot_reset OFF bootdef_dev drb0.0.0.2006.0 booted_dev booted_file booted_osflags bus_probe_algorithm new char_set 0 com1_baud 9600 com1_flow SOFTWARE com1_modem OFF com2_baud 9600 com2_flow SOFTWARE com2_modem OFF console serial controlp ON cpu_enabled ff d_bell off d_cleanup on d_complete off d_eop off d_group field d_harderr halt d_loghard on d_logsoft off d_omit d_oper on d_passes 1 d_quick off d_report full d_runtime 0 d_softerr halt d_startup off d_status off d_trace off d_verbose 0 dump_dev enable_audit ON ewa0_arp_tries 3 ewa0_bootp_file ewa0_bootp_server ewa0_bootp_tries 3 ewa0_def_ginetaddr 0.0.0.0 ewa0_def_inetaddr 0.0.0.0 ewa0_def_inetfile ewa0_def_sinetaddr 0.0.0.0 ewa0_def_subnetmask 0.0.0.0 ewa0_ginetaddr 0.0.0.0 ewa0_inet_init bootp ewa0_inetaddr 0.0.0.0 ewa0_inetfile ewa0_loop_count 2 ewa0_loop_inc d0 ewa0_loop_patt ffffffff ewa0_loop_size 100 ewa0_lp_msg_node 8 ewa0_mode Twisted-Pair ewa0_protocols MOP ewa0_sinetaddr 0.0.0.0 ewa0_tftp_tries 3 exdep_data 0 exdep_location 0 exdep_size 0 exdep_space pmem exdep_type 3 full_powerup_diags ON heap_expand NONE i g j u kbd_hardware_type PCXAL language 36 language_name English (American) license MU ocp_text StorageWorks ocp_text_default Model 4/200 os_type UNIX pal VMS PALcode V5.56-7, OSF PALcode V1.45-12 pci_arb Partial-Rotating pci_parity ON pka0_disconnect 1 pka0_fast 1 pka0_host_id 7 pkb0_host_id 7 pkb0_soft_term on rcm_answer rcm_dialout rcm_init screen_mode OFF scsi_poll ON scsi_reset ON scsnode scssystemid 65534 scssystemidh 0 srm2dev sys_serial_num tga_sync_green 8 tt_allow_login 1 tty_dev 0 version V5.3-10 Oct 16 1998 14:06:58 P00>>> P00>>>sho dev dka600.6.0.2001.0 DKA600 RRD43 1084 dkb0.0.0.9.0 DKB0 RZ29B 0014 dkb600.6.0.9.0 DKB600 RRD46 0557 dra0.0.0.1003.0 DRA0 5 Member RAID 5 drb0.0.0.2006.0 DRB0 2 Member RAID 1 drb1.0.0.2006.0 DRB1 2 Member RAID 1 drb2.0.0.2006.0 DRB2 2 Member RAID 1 dva0.0.0.1000.0 DVA0 RX26/RX23 ewa0.0.0.7.0 EWA0 00-00-F8-23-16-31 pka0.7.0.2001.0 PKA0 SCSI Bus ID 7 pkb0.7.0.9.0 PKB0 SCSI Bus ID 7 5.57 P00>>>boot dva0 (boot dva0.0.0.1000.0 -flags 0,0) block 0 of dva0.0.0.1000.0 is a valid boot block reading 15 blocks from dva0.0.0.1000.0 bootstrap code read in base = 200000, image_start = 0, image_bytes = 1e00 initializing HWRPB at 2000 initializing page table at 7ff0000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code VMS PAL rev: 0x4000700010538 OSF PAL rev: 0x4000c0002012d Switch to OSF PAL code succeeded. FreeBSD/alpha SRM disk boot, Revision 0.3 (root@miata.wbnet, Sun Jul 16 17:19:42 GMT 2000) Memory: 131072 k Please insert MFS root floppy and press enter: Entering kernel at 0xfffffc00003297e0... Unrecognized boot flag '0'. Unrecognized boot flag ','. Unrecognized boot flag '0'. Copyright (c) 1992-2000 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 41rc-16jul #0: Sun Jul 16 19:24:36 GMT 2000 root@miata.wbnet:/usr/src/sys/compile/BOOTMFS DEC AlphaServer 2100A AlphaServer 2100A 4/200, 190MHz 8192 byte page size, 1 processor. CPU: EV4 (21064) major=2 minor=1 OSF PAL rev: 0x4000c0002012d real memory = 132046848 (128952K bytes) avail memory = 120553472 (117728K bytes) Preloaded elf kernel "kernel" at 0xfffffc00008fe000. Preloaded mfs_root "/mfsroot" at 0xfffffc00008fe0a0. md0: Preloaded image 2949120 bytes at 0xfffffc000062b410 md1: Malloc disk 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 0x81004000-0x810040ff irq 60 at device 1.0 on pci2 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking sym0: interrupting at T2 irq 60 pci2: (vendor=0x1069, dev=0x0001) at 6.0 irq 80 de0: port 0x10100-0x1017f mem 0x81111000-0x8111107f irq 68 at device 7.0 on pci0 de0: interrupting at T2 irq 68 de0: DEC 21040 [10Mb/s] pass 2.4 de0: address 00:00:f8:23:16:31 isp0: port 0x10000-0x100ff mem 0x81110000-0x81110fff irq 76 at device 9.0 on pci0 isp0: interrupting at T2 irq 76 pci0: (vendor=0x0000, dev=0x0000) at 12.0 irq 32 pci0: (vendor=0x0000, dev=0x0000) at 12.4 pci0: (vendor=0x0000, dev=0x0000) at 13.0 irq 32 pci0: (vendor=0x0000, dev=0x0000) at 13.4 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: interrupting at T2 irq 6 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 atkbd0: interrupting at T2 irq 1 psm: keyboard controller failed. vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x0> mcclock0: at port 0x70-0x71 on isa0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A, console sio0: interrupting at T2 irq 4 sio1: reserved for low-level i/o Timecounter "alpha" frequency 190009732 Hz Waiting 15 seconds for SCSI devices to settle de0: enabling 10baseT port wilklt# Script done on Tue Jul 18 14:55:36 2000 -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 10:41:57 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id EFB7837B97D for ; Tue, 18 Jul 2000 10:41:37 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13EbN9-000HpI-00 for freebsd-alpha@freebsd.org; Tue, 18 Jul 2000 17:41:35 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id TAA01988; Tue, 18 Jul 2000 19:32:07 +0200 (CEST) (envelope-from wkb) Date: Tue, 18 Jul 2000 19:32:07 +0200 From: Wilko Bulte To: FreeBSD-alpha mailing list Cc: drew@freebie.demon.nl Subject: testresults for AS2100A/Lynx on 4.1RC Message-ID: <20000718193207.A1632@freebie.demon.nl> Reply-To: wilko@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Below the results of booting 4.1-RC on a Lynx (AS2100A). Works reasonably well, but locks up/waits forever after printing 'waiting 15 secs for SCSI devices to settle'. Any ideas? Maybe interrupts don't get thru? (wild guess). Test boot floppies can be pulled over for test, I have the Lynx wednesday & thursday available.. Wilko --------- Script started on Tue Jul 18 14:45:39 2000 wilklt#tip a connected P00>>>sho conf Digital Equipment Corporation AlphaServer 2100A 4/200 SRM Console V5.3-10 VMS PALcode V5.56-7, OSF PALcode V1.45-12 Component Status Module ID CPU 0 P B2020-AA DECchip (tm) 21064-3 Memory 0 P B2021-CA 128 MB I/O B2222-AA dva0.0.0.1000.0 RX26/RX23 Slot Option Hose 0, Bus 0, PCI 2 Intel 82375 Bridge to Bus 1, EISA 3 DECchip 21050-AA Bridge to Bus 2, PCI 7 DECchip 21040-AA ewa0.0.0.7.0 00-00-F8-23-16-31 9 QLogic ISP1020 pkb0.7.0.9.0 SCSI Bus ID 7 dkb0.0.0.9.0 RZ29B dkb600.6.0.9.0 RRD46 Slot Option Hose 0, Bus 1, EISA 1 Compaq Qvision 3 Mylex DAC960 dra.0.0.1003.0 dra0.0.0.1003.0 5 Member RAID 5 Slot Option Hose 0, Bus 2, PCI 1 NCR 53C810 pka0.7.0.2001.0 SCSI Bus ID 7 dka600.6.0.2001.0 RRD43 6 Mylex DAC960 drb.0.0.2006.0 drb0.0.0.2006.0 2 Member RAID 1 drb1.0.0.2006.0 2 Member RAID 1 drb2.0.0.2006.0 2 Member RAID 1 P00>>>sho auto_action HALT boot_dev drb0.0.0.2006.0 boot_file boot_osflags 0,0 boot_reset OFF bootdef_dev drb0.0.0.2006.0 booted_dev booted_file booted_osflags bus_probe_algorithm new char_set 0 com1_baud 9600 com1_flow SOFTWARE com1_modem OFF com2_baud 9600 com2_flow SOFTWARE com2_modem OFF console serial controlp ON cpu_enabled ff d_bell off d_cleanup on d_complete off d_eop off d_group field d_harderr halt d_loghard on d_logsoft off d_omit d_oper on d_passes 1 d_quick off d_report full d_runtime 0 d_softerr halt d_startup off d_status off d_trace off d_verbose 0 dump_dev enable_audit ON ewa0_arp_tries 3 ewa0_bootp_file ewa0_bootp_server ewa0_bootp_tries 3 ewa0_def_ginetaddr 0.0.0.0 ewa0_def_inetaddr 0.0.0.0 ewa0_def_inetfile ewa0_def_sinetaddr 0.0.0.0 ewa0_def_subnetmask 0.0.0.0 ewa0_ginetaddr 0.0.0.0 ewa0_inet_init bootp ewa0_inetaddr 0.0.0.0 ewa0_inetfile ewa0_loop_count 2 ewa0_loop_inc d0 ewa0_loop_patt ffffffff ewa0_loop_size 100 ewa0_lp_msg_node 8 ewa0_mode Twisted-Pair ewa0_protocols MOP ewa0_sinetaddr 0.0.0.0 ewa0_tftp_tries 3 exdep_data 0 exdep_location 0 exdep_size 0 exdep_space pmem exdep_type 3 full_powerup_diags ON heap_expand NONE i g j u kbd_hardware_type PCXAL language 36 language_name English (American) license MU ocp_text StorageWorks ocp_text_default Model 4/200 os_type UNIX pal VMS PALcode V5.56-7, OSF PALcode V1.45-12 pci_arb Partial-Rotating pci_parity ON pka0_disconnect 1 pka0_fast 1 pka0_host_id 7 pkb0_host_id 7 pkb0_soft_term on rcm_answer rcm_dialout rcm_init screen_mode OFF scsi_poll ON scsi_reset ON scsnode scssystemid 65534 scssystemidh 0 srm2dev sys_serial_num tga_sync_green 8 tt_allow_login 1 tty_dev 0 version V5.3-10 Oct 16 1998 14:06:58 P00>>> P00>>>sho dev dka600.6.0.2001.0 DKA600 RRD43 1084 dkb0.0.0.9.0 DKB0 RZ29B 0014 dkb600.6.0.9.0 DKB600 RRD46 0557 dra0.0.0.1003.0 DRA0 5 Member RAID 5 drb0.0.0.2006.0 DRB0 2 Member RAID 1 drb1.0.0.2006.0 DRB1 2 Member RAID 1 drb2.0.0.2006.0 DRB2 2 Member RAID 1 dva0.0.0.1000.0 DVA0 RX26/RX23 ewa0.0.0.7.0 EWA0 00-00-F8-23-16-31 pka0.7.0.2001.0 PKA0 SCSI Bus ID 7 pkb0.7.0.9.0 PKB0 SCSI Bus ID 7 5.57 P00>>>boot dva0 (boot dva0.0.0.1000.0 -flags 0,0) block 0 of dva0.0.0.1000.0 is a valid boot block reading 15 blocks from dva0.0.0.1000.0 bootstrap code read in base = 200000, image_start = 0, image_bytes = 1e00 initializing HWRPB at 2000 initializing page table at 7ff0000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code VMS PAL rev: 0x4000700010538 OSF PAL rev: 0x4000c0002012d Switch to OSF PAL code succeeded. FreeBSD/alpha SRM disk boot, Revision 0.3 (root@miata.wbnet, Sun Jul 16 17:19:42 GMT 2000) Memory: 131072 k Please insert MFS root floppy and press enter: Entering kernel at 0xfffffc00003297e0... Unrecognized boot flag '0'. Unrecognized boot flag ','. Unrecognized boot flag '0'. Copyright (c) 1992-2000 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 41rc-16jul #0: Sun Jul 16 19:24:36 GMT 2000 root@miata.wbnet:/usr/src/sys/compile/BOOTMFS DEC AlphaServer 2100A AlphaServer 2100A 4/200, 190MHz 8192 byte page size, 1 processor. CPU: EV4 (21064) major=2 minor=1 OSF PAL rev: 0x4000c0002012d real memory = 132046848 (128952K bytes) avail memory = 120553472 (117728K bytes) Preloaded elf kernel "kernel" at 0xfffffc00008fe000. Preloaded mfs_root "/mfsroot" at 0xfffffc00008fe0a0. md0: Preloaded image 2949120 bytes at 0xfffffc000062b410 md1: Malloc disk 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 0x81004000-0x810040ff irq 60 at device 1.0 on pci2 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking sym0: interrupting at T2 irq 60 pci2: (vendor=0x1069, dev=0x0001) at 6.0 irq 80 de0: port 0x10100-0x1017f mem 0x81111000-0x8111107f irq 68 at device 7.0 on pci0 de0: interrupting at T2 irq 68 de0: DEC 21040 [10Mb/s] pass 2.4 de0: address 00:00:f8:23:16:31 isp0: port 0x10000-0x100ff mem 0x81110000-0x81110fff irq 76 at device 9.0 on pci0 isp0: interrupting at T2 irq 76 pci0: (vendor=0x0000, dev=0x0000) at 12.0 irq 32 pci0: (vendor=0x0000, dev=0x0000) at 12.4 pci0: (vendor=0x0000, dev=0x0000) at 13.0 irq 32 pci0: (vendor=0x0000, dev=0x0000) at 13.4 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: interrupting at T2 irq 6 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 atkbd0: interrupting at T2 irq 1 psm: keyboard controller failed. vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x0> mcclock0: at port 0x70-0x71 on isa0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A, console sio0: interrupting at T2 irq 4 sio1: reserved for low-level i/o Timecounter "alpha" frequency 190009732 Hz Waiting 15 seconds for SCSI devices to settle de0: enabling 10baseT port wilklt# Script done on Tue Jul 18 14:55:36 2000 -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 10:54:41 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 528B337B67C; Tue, 18 Jul 2000 10:54:39 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA31782; Tue, 18 Jul 2000 10:54:37 -0700 Date: Tue, 18 Jul 2000 10:54:30 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: alpha@FreeBSD.org Subject: Re: cvs commit: src/release/texts/alpha HARDWARE.TXT In-Reply-To: <200007181750.KAA90612@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can you this to HARDWARE.TXT? (you're MAINTAINER, right?) Alpha 4100 Known Problems The current implementation has problems with handling PCI bridges. There is currently a limited fix for this in place which allows for single level, single device, PCI bridges (this allows for the Digital supplied Qlogic SCSI card which sits behind a 21054 PCI bridge chip). Alpha 8200 Known Problems The Alpha 8200 cannot handle PCI cards that are PCI bridges. Don't use them at this time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 11: 6: 8 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 4B10B37B6BA; Tue, 18 Jul 2000 11:06:04 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13Ebkl-000I8h-01; Tue, 18 Jul 2000 18:06:00 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id UAA02354; Tue, 18 Jul 2000 20:03:49 +0200 (CEST) (envelope-from wkb) Date: Tue, 18 Jul 2000 20:03:49 +0200 From: Wilko Bulte To: Matthew Jacob Cc: wilko@FreeBSD.ORG, FreeBSD-alpha mailing list Subject: Re: test results (or rather lack thereof) for 4.1RC on Rawhide (AS4100) Message-ID: <20000718200349.A2320@freebie.demon.nl> Reply-To: wilko@FreeBSD.ORG References: <20000718194105.A2056@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Tue, Jul 18, 2000 at 10:49:46AM -0700 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jul 18, 2000 at 10:49:46AM -0700, Matthew Jacob wrote: > 4.0 won't work- this stuff wasn't checked in then. 4.0-stable just before it became 4.1RC should do it. I know 4.0release does not. > Really? See attached dmesg for what I've been having no problemo on. > > I *have* had a couple of times, one of the NASA/Ames Rawhides (which are in > the, what is it, Mustang configuration- 4 MCPCIAs) freeze on boot, but I > think I tracked that to a flakey disk box connection. I haven't done fuller > testing because the installer is broken when there are 'foreign but similar' > operating systems on disks. You mean the 'don't go nowhere without my init' ? It does not get as far as that. > This is not good, as we're only a couple of days away 4.1 release and I've > run out of time to work on this :-)! Yep.. > What h/w do you have in your machine? Well: KZPSA DECs own FWD SCSI KGPSA Emulex LP7000 KZPBA Qlogic1040 DEC4xx ethernet some VGA thingy (I think) but running serial console. probably Memory Channel The machine lives in our lab at work so I cannot check right now. -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 11:14: 1 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 64F9E37B5F5 for ; Tue, 18 Jul 2000 11:13:58 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13EbsS-0006kX-00 for freebsd-alpha@freebsd.org; Tue, 18 Jul 2000 18:13:57 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id UAA02533 for freebsd-alpha@freebsd.org; Tue, 18 Jul 2000 20:13:56 +0200 (CEST) (envelope-from wkb) Date: Tue, 18 Jul 2000 20:13:56 +0200 From: Wilko Bulte To: FreeBSD-alpha mailing list Subject: parallel ports on alpha in 4.1? Message-ID: <20000718201356.C2427@freebie.demon.nl> Reply-To: wilko@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Your friendly *.TXT maintainer calling: Will there be parallel port support in 4.1 for alpha? I know it went into -current sometime ago but there was work in progress on releng_4 Has that been completed? -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 11:21:30 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from lh2.rdc1.tx.home.com (ha2.rdc1.tx.home.com [24.4.0.67]) by hub.freebsd.org (Postfix) with ESMTP id 4387637B723; Tue, 18 Jul 2000 11:21:28 -0700 (PDT) (envelope-from miklic@ibm.net) Received: from ibm.net ([24.10.140.87]) by lh2.rdc1.tx.home.com (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20000718182127.NIWT13510.lh2.rdc1.tx.home.com@ibm.net>; Tue, 18 Jul 2000 11:21:27 -0700 Message-ID: <3974A0E1.D7723C01@ibm.net> Date: Tue, 18 Jul 2000 12:24:34 -0600 From: "Andrew M. Miklic" X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 4.1-RC alpha) X-Accept-Language: en MIME-Version: 1.0 To: wilko@freebsd.org Cc: FreeBSD-alpha mailing list Subject: Re: parallel ports on alpha in 4.1? References: <20000718201356.C2427@freebie.demon.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've got diffs, and they're just waiting for Doug Rabson to submit them...I don't know if they'll make it in time for 4.1, though... By the way, for anyone interested, i've just finished support for native ppc_detect for the Miata platforms (National Semiconductor 873xx SuperI/O), and so we now have code to provide a parallel port that is capable of being relocated to 0x378 (and fully capable of ECP/EPP, thanks to Mark abene's work)--the chip actually supports being relocated to 0x278 as well, but there's a little more work involved, and since any port other than 0x3bc is what is needed to do ECP/EPP support without wiping the screen, this _should_ suffice for now... Andrew Wilko Bulte wrote: > Your friendly *.TXT maintainer calling: > > Will there be parallel port support in 4.1 for alpha? I know it went into > -current sometime ago but there was work in progress on releng_4 Has > that been completed? > > -- > Wilko Bulte http://www.freebsd.org > wilko@freebsd.org http://www.nlfug.nl > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 11:23:29 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 16E8F37B772; Tue, 18 Jul 2000 11:23:27 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA31916; Tue, 18 Jul 2000 11:23:26 -0700 Date: Tue, 18 Jul 2000 11:23:19 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: wilko@FreeBSD.ORG Cc: FreeBSD-alpha mailing list Subject: Re: test results (or rather lack thereof) for 4.1RC on Rawhide (AS4100) In-Reply-To: <20000718200349.A2320@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > You mean the 'don't go nowhere without my init' ? It does not get as far as > that. Yes, I know... > > > This is not good, as we're only a couple of days away 4.1 release and I've > > run out of time to work on this :-)! > > Yep.. Hmmm... > > > What h/w do you have in your machine? > > Well: > KZPSA DECs own FWD SCSI > KGPSA Emulex LP7000 > KZPBA Qlogic1040 > DEC4xx ethernet > some VGA thingy (I think) but running serial console. > probably Memory Channel > > The machine lives in our lab at work so I cannot check right now. Well, from what you said about where it hangs, I'm wondering if it has even transferred to the loader yet? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 11:26:31 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id E70BA37B756; Tue, 18 Jul 2000 11:26:24 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA03123; Tue, 18 Jul 2000 14:26:21 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id OAA45449; Tue, 18 Jul 2000 14:26:21 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 18 Jul 2000 14:26:21 -0400 (EDT) To: wilko@FreeBSD.ORG Cc: FreeBSD-alpha mailing list Subject: Re: test results (or rather lack thereof) for 4.1RC on Rawhide (AS4100) In-Reply-To: <20000718194105.A2056@freebie.demon.nl> References: <20000718194105.A2056@freebie.demon.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14708.41223.166538.493762@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte writes: > Question: has anybody had any success recently booting 4.1RC or 4.0stable > on a AS4100? I have tried two different AS4100 with known-good boot floppies > and both lockup with something like: > > Booting kernel > / > > (note the /, it just freezes). Boot from CD does not seem to work on any > Alpha that I tried it on at the moment :-( Dumb question: Do your console settings match your configuration (graphics or serial)? If serial, are you using the correct serial line? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 11:29:26 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id E105337BAEA; Tue, 18 Jul 2000 11:29:17 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA03199; Tue, 18 Jul 2000 14:29:17 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id OAA45453; Tue, 18 Jul 2000 14:29:17 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 18 Jul 2000 14:29:17 -0400 (EDT) To: wilko@FreeBSD.ORG Cc: FreeBSD-alpha mailing list Subject: Re: test results for Lynx (AS2100A) In-Reply-To: <20000718193708.A2031@freebie.demon.nl> References: <20000718193708.A2031@freebie.demon.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14708.41311.494517.133622@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte writes: > Below the results of booting 4.1-RC on a Lynx (AS2100A). > Works reasonably well, but locks up/waits forever after printing > 'waiting 15 secs for SCSI devices to settle'. > > Any ideas? Maybe interrupts don't get thru? (wild guess). > > Test boot floppies can be pulled over for test, I have the Lynx wednesday & > thursday available.. Yes, the IRQs are almost certainly wrong. I'll try to look into this tonight or tomorrow (I just had a slew of hardware arrive that we've been waiting for for quite some time, so I'm pretty busy today). I don't suppose you can netboot the thing? It makes for much easier testing.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 11:41: 2 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id BA99437B800; Tue, 18 Jul 2000 11:40:57 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13EcIZ-000IYJ-01; Tue, 18 Jul 2000 18:40:56 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id UAA02744; Tue, 18 Jul 2000 20:29:21 +0200 (CEST) (envelope-from wkb) Date: Tue, 18 Jul 2000 20:29:21 +0200 From: Wilko Bulte To: Matthew Jacob Cc: Wilko Bulte , alpha@freebsd.org Subject: Re: cvs commit: src/release/texts/alpha HARDWARE.TXT Message-ID: <20000718202921.A2681@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <200007181750.KAA90612@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Tue, Jul 18, 2000 at 10:54:30AM -0700 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jul 18, 2000 at 10:54:30AM -0700, Matthew Jacob wrote: > > > Can you this to HARDWARE.TXT? (you're MAINTAINER, right?) ^-- yes Just committed your updates. -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 11:41: 5 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id ADD5D37B80A; Tue, 18 Jul 2000 11:40:58 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13EcIb-000IYJ-00; Tue, 18 Jul 2000 18:40:57 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id UAA02858; Tue, 18 Jul 2000 20:38:14 +0200 (CEST) (envelope-from wkb) Date: Tue, 18 Jul 2000 20:38:14 +0200 From: Wilko Bulte To: Andrew Gallatin Cc: wilko@freebsd.org, FreeBSD-alpha mailing list Subject: Re: test results for Lynx (AS2100A) Message-ID: <20000718203813.B2834@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <20000718193708.A2031@freebie.demon.nl> <14708.41311.494517.133622@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <14708.41311.494517.133622@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Tue, Jul 18, 2000 at 02:29:17PM -0400 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jul 18, 2000 at 02:29:17PM -0400, Andrew Gallatin wrote: > > Wilko Bulte writes: > > Below the results of booting 4.1-RC on a Lynx (AS2100A). > > Works reasonably well, but locks up/waits forever after printing > > 'waiting 15 secs for SCSI devices to settle'. > > > > Any ideas? Maybe interrupts don't get thru? (wild guess). > > > > Test boot floppies can be pulled over for test, I have the Lynx wednesday & > > thursday available.. > > Yes, the IRQs are almost certainly wrong. I'll try to look into this > tonight or tomorrow (I just had a slew of hardware arrive that we've > been waiting for for quite some time, so I'm pretty busy today). I notices NetBSD is also quite involved with AS2100[a] these days > I don't suppose you can netboot the thing? It makes for much easier > testing.. Not easily no. If you can provide me with a bootfloppy pair that'd do it most easily for me. -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 11:41:12 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 3D52037B83A; Tue, 18 Jul 2000 11:41:01 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13EcIb-000IYJ-01; Tue, 18 Jul 2000 18:40:57 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id UAA02868; Tue, 18 Jul 2000 20:38:54 +0200 (CEST) (envelope-from wkb) Date: Tue, 18 Jul 2000 20:38:54 +0200 From: Wilko Bulte To: Andrew Gallatin Cc: wilko@freebsd.org, FreeBSD-alpha mailing list Subject: Re: test results (or rather lack thereof) for 4.1RC on Rawhide (AS4100) Message-ID: <20000718203853.C2834@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <20000718194105.A2056@freebie.demon.nl> <14708.41223.166538.493762@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <14708.41223.166538.493762@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Tue, Jul 18, 2000 at 02:26:21PM -0400 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jul 18, 2000 at 02:26:21PM -0400, Andrew Gallatin wrote: > > Wilko Bulte writes: > > Question: has anybody had any success recently booting 4.1RC or 4.0stable > > on a AS4100? I have tried two different AS4100 with known-good boot floppies > > and both lockup with something like: > > > > Booting kernel > > / > > > > (note the /, it just freezes). Boot from CD does not seem to work on any > > Alpha that I tried it on at the moment :-( > > Dumb question: Do your console settings match your configuration > (graphics or serial)? If serial, are you using the correct serial > line? It is serial yes. But I'll double check tomorrow. -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 11:41:10 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id F079A37B723; Tue, 18 Jul 2000 11:41:00 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13EcIa-000IYJ-00; Tue, 18 Jul 2000 18:40:56 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id UAA02884; Tue, 18 Jul 2000 20:40:32 +0200 (CEST) (envelope-from wkb) Date: Tue, 18 Jul 2000 20:40:32 +0200 From: Wilko Bulte To: Matthew Jacob Cc: wilko@freebsd.org, FreeBSD-alpha mailing list Subject: Re: test results (or rather lack thereof) for 4.1RC on Rawhide (AS4100) Message-ID: <20000718204032.D2834@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <20000718200349.A2320@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Tue, Jul 18, 2000 at 11:23:19AM -0700 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jul 18, 2000 at 11:23:19AM -0700, Matthew Jacob wrote: > > > This is not good, as we're only a couple of days away 4.1 release and I've > > > run out of time to work on this :-)! > > > > Yep.. > > Hmmm... Smells like a thawing code freeze to me (at least for alpha). > > Well: > > KZPSA DECs own FWD SCSI > > KGPSA Emulex LP7000 > > KZPBA Qlogic1040 > > DEC4xx ethernet > > some VGA thingy (I think) but running serial console. > > probably Memory Channel > > > > The machine lives in our lab at work so I cannot check right now. > > Well, from what you said about where it hangs, I'm wondering if it has even > transferred to the loader yet? Don't think so, but I'll capture a boot session on the ol' laptop tomorrow (just need to keep those customers off my back ;-) -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 12: 4: 6 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id E756637BADB; Tue, 18 Jul 2000 12:03:58 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id PAA03978; Tue, 18 Jul 2000 15:03:57 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id PAA45540; Tue, 18 Jul 2000 15:03:57 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 18 Jul 2000 15:03:57 -0400 (EDT) To: wilko@freebsd.org Cc: FreeBSD-alpha mailing list Subject: Re: test results for Lynx (AS2100A) In-Reply-To: <20000718203813.B2834@freebie.demon.nl> References: <20000718193708.A2031@freebie.demon.nl> <14708.41311.494517.133622@grasshopper.cs.duke.edu> <20000718203813.B2834@freebie.demon.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14708.43258.138626.9497@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte writes: > On Tue, Jul 18, 2000 at 02:29:17PM -0400, Andrew Gallatin wrote: > > > > Wilko Bulte writes: > > > Below the results of booting 4.1-RC on a Lynx (AS2100A). > > > Works reasonably well, but locks up/waits forever after printing > > > 'waiting 15 secs for SCSI devices to settle'. > > > > > > Any ideas? Maybe interrupts don't get thru? (wild guess). > > > > > > Test boot floppies can be pulled over for test, I have the Lynx wednesday & > > > thursday available.. > > > > Yes, the IRQs are almost certainly wrong. I'll try to look into this > > tonight or tomorrow (I just had a slew of hardware arrive that we've > > been waiting for for quite some time, so I'm pretty busy today). > > I notices NetBSD is also quite involved with AS2100[a] these days It would be very cool if you could try to boot NetBSD on your 2100A & see what happens. From what I know of how the interrupt routing works on the 2100, the irqs we're seeing are impossible. So they may have changed it on the 2100A. Cheers, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 12: 6:15 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0D81637B8C4; Tue, 18 Jul 2000 12:06:13 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA32223; Tue, 18 Jul 2000 12:06:07 -0700 Date: Tue, 18 Jul 2000 12:06:00 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: wilko@FreeBSD.ORG, FreeBSD-alpha mailing list Subject: Re: test results for Lynx (AS2100A) In-Reply-To: <14708.43258.138626.9497@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > It would be very cool if you could try to boot NetBSD on your 2100A & see > what happens. And if it doesn't work, does this constitute 'two wrongs make a right'? :-) > >From what I know of how the interrupt routing works on the 2100, the > irqs we're seeing are impossible. So they may have changed it on the > 2100A. > > Cheers, > > Drew > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 12:22:41 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id E9F6937B911; Tue, 18 Jul 2000 12:22:33 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id PAA04344; Tue, 18 Jul 2000 15:22:33 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id PAA45565; Tue, 18 Jul 2000 15:22:33 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 18 Jul 2000 15:22:32 -0400 (EDT) To: mjacob@feral.com Cc: wilko@FreeBSD.ORG, FreeBSD-alpha mailing list Subject: Re: test results for Lynx (AS2100A) In-Reply-To: References: <14708.43258.138626.9497@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14708.44543.901084.816115@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > > > > It would be very cool if you could try to boot NetBSD on your 2100A & see > > what happens. > > And if it doesn't work, does this constitute 'two wrongs make a right'? :-) > I was thinking more along the lines what happens if it does work -- then we know that somebody has the documentation. Right now, I don't think any open source OS works on the 2100A. From searching the linux-alpha mailing lists, it looks like they don't know how the irq mapping works either. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 13:36:50 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from front2.grolier.fr (front2.grolier.fr [194.158.96.52]) by hub.freebsd.org (Postfix) with ESMTP id 8DE8937B8EB; Tue, 18 Jul 2000 13:36:44 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from Guyancourt-1-99.club-internet.fr (Guyancourt-1-99.club-internet.fr [195.36.205.99]) by front2.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id WAA19657; Tue, 18 Jul 2000 22:36:15 +0200 (MET DST) Date: Tue, 18 Jul 2000 22:15:45 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Andrew Gallatin Cc: Bernd Walter , dg@root.com, mjacob@feral.com, Mike Smith , freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE In-Reply-To: <14707.48450.371071.494543@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 17 Jul 2000, Andrew Gallatin wrote: =20 > Bernd Walter writes: > > On Fri, Jul 14, 2000 at 05:23:21PM -0400, Andrew Gallatin wrote: > > > As for the bug. I can duplicate it I run both the sender & receiver > > > fairly hard, like 2 100Mb/tcp connections running in opposite > > > directions. When I do this, it looks like the xmit side locks up b= ut=20 > > > the recv. side is at least partially OK. And I'm still getting stat= s > > > updates.=20 > >=20 > > Looks like you are on the right way. > > I can download a big file to the host without any problems but cvsup g= ets > > the interface stoped quite soon. >=20 > The problem is that the status & command field share a 32-bit word. > The programming API of the eepro apparently requires that you update > the status field of a transmit slot that you've given to the card. > Since alphas can only operate on 32-bit chunks of memory, both the > status & command fields are loaded into memory & operated on in > registers when the following line of C is executed: >=20 > =09=09/* > =09=09 * Advance the end of list forward. > =09=09 */ > =09=09sc->cbl_last->cb_command &=3D ~FXP_CB_COMMAND_S; I am not an Alpha expert, but my reading of the Alpha Architecture Handbook rev. 4 let me think that not too old Alpha Systems should allow atomic WORD and BYTE memory access from agents on the system BUS. CPUs with AMASK bit 0 set support proper intructions for doing such kind of access. If the C compiler does not want to generate the corresponding code, then=20 assembly is to be used. The assembly will force compiler barrier, but if=20 C can be used, may-be a volatile cast should be used to force such a=20 barrier. You may also want to add a memory barrier in places where some strong=20 ordering regarding how LOADs and STOREs are carried out to the system=20 BUS is expected. > The race is caused by the card DMA'ing up the status at just the wrong > time -- after it has been loaded into a register & before it has been > written back. The old value of the status is written back, clobbering > the status the card just DMA'ed up. The fact that the card has sent > this frame is missed & the transmit engine appears to hang. >=20 > I think I have a fix. It feels like overkill, but if the programming > interface of the chip does not allow for something better why not just > turn off DMA while we update cb_command? >=20 > Can anybody having problems with fxp's please try the appended patch? > Without this patch, I have a test case that can lock the xmitter in < > 5 seconds 100% of the time. With the patch, I've been unable to get > it to lock up using this test case. >=20 > Can a PCI expert comment on its safety? Mike? As a PCI non-expert, I may comment on its apparent brokenness. ;-) Clearing the PCI BUS MASTER ENABLE bit is generally not a documented way to tell a `running' PCI device to suspend DMA and wait for the bit to be set again prior to continuing operations. This is likely to confuse most PCI devices, in my opinion. I hope I haven't been too wrong. :-) G=E9rard. > Index: pci/if_fxp.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > RCS file: /home/ncvs/src/sys/pci/if_fxp.c,v > retrieving revision 1.77.2.4 > diff -u -r1.77.2.4 if_fxp.c > --- pci/if_fxp.c=092000/07/13 07:53:06=091.77.2.4 > +++ pci/if_fxp.c=092000/07/18 02:07:04 > @@ -527,6 +527,8 @@ > =20 > =09callout_handle_init(&sc->stat_ch); > =20 > +=09sc->dev =3D dev; > + > =09s =3D splimp(); > =20 > =09/* > @@ -535,6 +537,7 @@ > =09val =3D pci_read_config(dev, PCIR_COMMAND, 2); > =09val |=3D (PCIM_CMD_MEMEN|PCIM_CMD_BUSMASTEREN); > =09pci_write_config(dev, PCIR_COMMAND, val, 2); > +=09sc->cmd =3D val; > =20 > =09/* > =09 * Map control/status registers. > @@ -960,6 +963,7 @@ > { > =09struct fxp_softc *sc =3D ifp->if_softc; > =09struct fxp_cb_tx *txp; > +=09int s; > =20 > =09/* > =09 * See if we need to suspend xmit until the multicast filter > @@ -1052,10 +1056,24 @@ > =09=09} > =09=09txp->tx_threshold =3D tx_threshold; > =09 > +#ifdef __alpha__ > +=09=09/* > +=09=09 * Prevent the card from DMA'ing up the status while > +=09=09 * we update the command field. This could cause > +=09=09 * us to overwrite the completion status. > +=09=09 */ > +=09=09s =3D splhigh(); > +=09=09pci_write_config(sc->dev, PCIR_COMMAND,=20 > +=09=09 (sc->cmd & ~PCIM_CMD_BUSMASTEREN), 2); > +#endif /*alpha*/ > =09=09/* > =09=09 * Advance the end of list forward. > =09=09 */ > =09=09sc->cbl_last->cb_command &=3D ~FXP_CB_COMMAND_S; > +#ifdef __alpha__ > +=09=09pci_write_config(sc->dev, PCIR_COMMAND, sc->cmd, 2); > +=09=09splx(s); > +#endif /*alpha*/ > =09=09sc->cbl_last =3D txp; > =20 > =09=09/* > Index: pci/if_fxpvar.h > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > RCS file: /home/ncvs/src/sys/pci/if_fxpvar.h,v > retrieving revision 1.9.2.1 > diff -u -r1.9.2.1 if_fxpvar.h > --- pci/if_fxpvar.h=092000/03/29 02:02:39=091.9.2.1 > +++ pci/if_fxpvar.h=092000/07/18 02:03:50 > @@ -48,6 +48,7 @@ > =09struct resource *mem;=09=09/* resource descriptor for registers */ > =09struct resource *irq;=09=09/* resource descriptor for interrupt */ > =09void *ih;=09=09=09/* interrupt handler cookie */ > +=09device_t dev;=09=09=09/* newbus device pointer */ > #endif /* __NetBSD__ */ > =09bus_space_tag_t sc_st;=09=09/* bus space tag */ > =09bus_space_handle_t sc_sh;=09/* bus space handle */ > @@ -68,6 +69,7 @@ > =09int phy_primary_device;=09=09/* device type of primary PHY */ > =09int phy_10Mbps_only;=09=09/* PHY is 10Mbps-only device */ > =09int eeprom_size;=09=09/* size of serial EEPROM */ > +=09u_long cmd;=09=09=09/* contents of pci CMD register */ > }; > =20 > /* Macros to ease CSR access. */ >=20 >=20 > Cheers, >=20 > Drew > -------------------------------------------------------------------------= ----- > Andrew Gallatin, Sr Systems Programmer=09http://www.cs.duke.edu/~gallatin > Duke University=09=09=09=09Email: gallatin@cs.duke.edu > Department of Computer Science=09=09Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 14:32:12 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B74D837BB87; Tue, 18 Jul 2000 14:32:09 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA00105; Tue, 18 Jul 2000 14:31:49 -0700 Date: Tue, 18 Jul 2000 14:31:41 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Cc: Andrew Gallatin , Bernd Walter , dg@root.com, Mike Smith , freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We won't support BWX as a default. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 14:42:47 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id E590037B5DE for ; Tue, 18 Jul 2000 14:42:41 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id OAA19240; Tue, 18 Jul 2000 14:51:33 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007182151.OAA19240@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andrew Gallatin Cc: FreeBSD-alpha mailing list Subject: Re: test results for Lynx (AS2100A) In-reply-to: Your message of "Tue, 18 Jul 2000 15:03:57 EDT." <14708.43258.138626.9497@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Jul 2000 14:51:33 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > It would be very cool if you could try to boot NetBSD on your 2100A & > see what happens. > > >From what I know of how the interrupt routing works on the 2100, the > irqs we're seeing are impossible. So they may have changed it on the > 2100A. From the time I spent reading the Sable/Lynx code in the Linux tree, the two principal differences were the base address for 'interesting' register space, and the interrupt layout. I'd be fairly certain that things are different on the 2100A. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 14:45:51 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 6A44137B80B; Tue, 18 Jul 2000 14:45:48 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA07205; Tue, 18 Jul 2000 17:45:47 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id RAA45772; Tue, 18 Jul 2000 17:45:47 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 18 Jul 2000 17:45:46 -0400 (EDT) To: Mike Smith Cc: FreeBSD-alpha mailing list Subject: Re: test results for Lynx (AS2100A) In-Reply-To: <200007182151.OAA19240@mass.osd.bsdi.com> References: <14708.43258.138626.9497@grasshopper.cs.duke.edu> <200007182151.OAA19240@mass.osd.bsdi.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14708.53166.457782.141424@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith writes: > > It would be very cool if you could try to boot NetBSD on your 2100A & > > see what happens. > > > > >From what I know of how the interrupt routing works on the 2100, the > > irqs we're seeing are impossible. So they may have changed it on the > > 2100A. > > >From the time I spent reading the Sable/Lynx code in the Linux tree, the > two principal differences were the base address for 'interesting' > register space, and the interrupt layout. I'd be fairly certain that > things are different on the 2100A. > Where did you see a description of the Lynx's interrupt routing??? Which kernel version? Or what patch set? All I see is "PCI Fixup configuration for ALPHA SABLE (2100) - 2100A is different ??" And I've read some comments in the alpha-linux lists saying that lynx isn't supported.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 15:11:13 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 2174737BC02 for ; Tue, 18 Jul 2000 15:11:10 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id PAA19484; Tue, 18 Jul 2000 15:20:03 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007182220.PAA19484@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andrew Gallatin Cc: FreeBSD-alpha mailing list Subject: Re: test results for Lynx (AS2100A) In-reply-to: Your message of "Tue, 18 Jul 2000 17:45:46 EDT." <14708.53166.457782.141424@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Jul 2000 15:20:03 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > >From the time I spent reading the Sable/Lynx code in the Linux tree, the > > two principal differences were the base address for 'interesting' > > register space, and the interrupt layout. I'd be fairly certain that > > things are different on the 2100A. > > Where did you see a description of the Lynx's interrupt routing??? > Which kernel version? Or what patch set? Well, I *thought* I recalled two separate *_map_irq() functions with different swizzle tables, but of course now there's only one. 8( This would have been about a year or so ago, if I'm not entirely delusional. If I am, then sorry. 8( > All I see is "PCI Fixup configuration for ALPHA SABLE (2100) - 2100A is different ??" > And I've read some comments in the alpha-linux lists saying that lynx > isn't supported.. I was never able to get any Linux variant going on the AS2100, so I'm not sure how relevant any of that code really is. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 15:43:35 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from eel.radicalmedia.com (eel.radicalmedia.com [204.254.246.9]) by hub.freebsd.org (Postfix) with ESMTP id 7733B37B5C3; Tue, 18 Jul 2000 15:43:32 -0700 (PDT) (envelope-from phiber@eel.radicalmedia.com) Received: (from phiber@localhost) by eel.radicalmedia.com (8.9.3/8.9.3) id SAA02492; Tue, 18 Jul 2000 18:43:21 -0400 (EDT) Date: Tue, 18 Jul 2000 18:43:19 -0400 From: Mark Abene To: "Andrew M. Miklic" Cc: wilko@FreeBSD.ORG, FreeBSD-alpha mailing list Subject: Re: parallel ports on alpha in 4.1? Message-ID: <20000718184319.D18832@radicalmedia.com> References: <20000718201356.C2427@freebie.demon.nl> <3974A0E1.D7723C01@ibm.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <3974A0E1.D7723C01@ibm.net>; from Andrew M. Miklic on Tue, Jul 18, 2000 at 12:24:34PM -0600 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm curious when you say more work was involved to use port 0x278 on the NatSemi chip. Is it not like the SMSC chip where you can simply tell it any i/o port you want? Considering we will now have i/o port relocation covered for the PC164 and Miata, is anyone willing to compile a list of the various Super I/O chips in use by Alphas so we could add this support to more machines? -Mark On Tue, Jul 18, 2000 at 12:24:34PM -0600, Andrew M. Miklic wrote: > I've got diffs, and they're just waiting for Doug Rabson to submit them...I > don't know if they'll make it in time for 4.1, though... > > By the way, for anyone interested, i've just finished support for native > ppc_detect for the Miata platforms (National Semiconductor 873xx SuperI/O), > and so we now have code to provide a parallel port that is capable of being > relocated to 0x378 (and fully capable of ECP/EPP, thanks to Mark abene's > work)--the chip actually supports being relocated to 0x278 as well, but > there's a little more work involved, and since any port other than 0x3bc is > what is needed to do ECP/EPP support without wiping the screen, this > _should_ suffice for now... > > Andrew > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jul 18 15:49:43 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 023B237BBBF; Tue, 18 Jul 2000 15:49:39 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13EgBE-000LcR-00; Tue, 18 Jul 2000 22:49:37 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id AAA04556; Wed, 19 Jul 2000 00:49:36 +0200 (CEST) (envelope-from wkb) Date: Wed, 19 Jul 2000 00:49:36 +0200 From: Wilko Bulte To: "Andrew M. Miklic" Cc: wilko@FreeBSD.ORG, FreeBSD-alpha mailing list Subject: Re: parallel ports on alpha in 4.1? Message-ID: <20000719004936.A4534@freebie.demon.nl> Reply-To: wilko@FreeBSD.ORG References: <20000718201356.C2427@freebie.demon.nl> <3974A0E1.D7723C01@ibm.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3974A0E1.D7723C01@ibm.net>; from miklic@ibm.net on Tue, Jul 18, 2000 at 12:24:34PM -0600 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jul 18, 2000 at 12:24:34PM -0600, Andrew M. Miklic wrote: > I've got diffs, and they're just waiting for Doug Rabson to submit them...I > don't know if they'll make it in time for 4.1, though... Doug tonight put ppc support into the RELENG_4 branch, so 4.1R should have the ppc support included. I have not checked the exact nature of what he MFCed, just saw the commit message go by. > By the way, for anyone interested, i've just finished support for native > ppc_detect for the Miata platforms (National Semiconductor 873xx SuperI/O), > and so we now have code to provide a parallel port that is capable of being > relocated to 0x378 (and fully capable of ECP/EPP, thanks to Mark abene's > work)--the chip actually supports being relocated to 0x278 as well, but > there's a little more work involved, and since any port other than 0x3bc is > what is needed to do ECP/EPP support without wiping the screen, this > _should_ suffice for now... -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jul 19 3:38:28 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 74EF237BF00; Wed, 19 Jul 2000 03:38:23 -0700 (PDT) (envelope-from ticso@mail.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e6JAcH621253 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Wed, 19 Jul 2000 12:38:19 +0200 (MET DST) Received: (from ticso@localhost) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) id e6JAbh544475; Wed, 19 Jul 2000 12:37:43 +0200 (CEST) Date: Wed, 19 Jul 2000 12:37:43 +0200 From: Bernd Walter To: Andrew Gallatin Cc: Tony Griffiths , mjacob@feral.com, David Greenman , Bernd Walter , Mike Smith , freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE Message-ID: <20000719123743.A44454@cicely7.cicely.de> References: <39740E1D.7F2AF81D@OntheNet.com.au> <14708.21581.689293.987109@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <14708.21581.689293.987109@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Tue, Jul 18, 2000 at 09:26:57AM -0400 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jul 18, 2000 at 09:26:57AM -0400, Andrew Gallatin wrote: > Sure enough, the following patch works on a UP1000 (21164A). You mean 21264 I expect :) > However, I'm uncertain about other CPUs. In particular, the 21164's > description is more complex & I don't really understand it. Bernd -- > Can you try this new patch on your machine (you have a 21164, right?): Yes it's an 21164@500MHz on a PC164 Board. Your current patches seem to run fine. I wasn't able to reproduce the original Problem with an 21066@166MHz on a apxpci33 Board - the problems begun after I exchanged the axppci33 Board with the PC164. -- 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 Wed Jul 19 5:40:55 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from lh2.rdc1.tx.home.com (ha2.rdc1.tx.home.com [24.4.0.67]) by hub.freebsd.org (Postfix) with ESMTP id D230237BF34; Wed, 19 Jul 2000 05:40:52 -0700 (PDT) (envelope-from miklic@attglobal.net) Received: from attglobal.net ([24.10.140.87]) by lh2.rdc1.tx.home.com (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20000719124052.URAT13510.lh2.rdc1.tx.home.com@attglobal.net>; Wed, 19 Jul 2000 05:40:52 -0700 Message-ID: <3975A28F.963347D5@attglobal.net> Date: Wed, 19 Jul 2000 06:43:59 -0600 From: "Andrew M. Miklic" X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 4.1-RC alpha) X-Accept-Language: en MIME-Version: 1.0 To: Mark Abene Cc: "Andrew M. Miklic" , wilko@FreeBSD.ORG, FreeBSD-alpha mailing list Subject: Re: parallel ports on alpha in 4.1? References: <20000718201356.C2427@freebie.demon.nl> <3974A0E1.D7723C01@ibm.net> <20000718184319.D18832@radicalmedia.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'm curious when you say more work was involved to use port 0x278 on the > NatSemi chip. Is it not like the SMSC chip where you can simply tell it > any i/o port you want? In short, no. Basically, there are 5 "modes" that you can put the PC873xx SuperI/O chips into, and these modes correspond to an address/irq combination. 2 of the 5 modes assume by default irq7, or can be told to assume for irq7 by default (corresponding to the address 0x3bc and 0x378), another assumes 0x278 but irq5, and the other 2 assume the defaults of irq7 with addresses of 0x278 and 0x378, but requires another bit to be twiddled, and I have not looked much at the functionality/implications of such a bit (and the current driver, as I found it, did not utilize the bit yet at all)... Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jul 19 5:49:11 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from lh2.rdc1.tx.home.com (ha2.rdc1.tx.home.com [24.4.0.67]) by hub.freebsd.org (Postfix) with ESMTP id B3E9837BC67; Wed, 19 Jul 2000 05:49:09 -0700 (PDT) (envelope-from miklic@attglobal.net) Received: from attglobal.net ([24.10.140.87]) by lh2.rdc1.tx.home.com (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20000719124909.UWAY13510.lh2.rdc1.tx.home.com@attglobal.net>; Wed, 19 Jul 2000 05:49:09 -0700 Message-ID: <3975A480.10E6FFAD@attglobal.net> Date: Wed, 19 Jul 2000 06:52:16 -0600 From: "Andrew M. Miklic" X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 4.1-RC alpha) X-Accept-Language: en MIME-Version: 1.0 To: wilko@FreeBSD.ORG Cc: "Andrew M. Miklic" , FreeBSD-alpha mailing list Subject: Re: parallel ports on alpha in 4.1? References: <20000718201356.C2427@freebie.demon.nl> <3974A0E1.D7723C01@ibm.net> <20000719004936.A4534@freebie.demon.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Doug tonight put ppc support into the RELENG_4 branch, so 4.1R should have the > ppc support included. I have not checked the exact nature of what he > MFCed, just saw the commit message go by. Just checked the latest cvsup'ed ppc stuff for Alpha support...it's in there!!! Thanks, Doug!!! Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jul 19 7: 4:17 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from charon.npc.net (charon.finall.com [199.15.61.3]) by hub.freebsd.org (Postfix) with ESMTP id 1420737B514 for ; Wed, 19 Jul 2000 07:04:13 -0700 (PDT) (envelope-from mjung@npc.net) Received: from exchange1.npc.net ([10.0.157.36]) by charon.npc.net (8.10.2/8.10.2) with ESMTP id e6JE4Be41769 for ; Wed, 19 Jul 2000 10:04:12 -0400 (EDT) Received: by EXCHANGE1 with Internet Mail Service (5.5.1960.3) id ; Wed, 19 Jul 2000 10:04:13 -0400 Message-ID: <921763828F4BD4118D7D00805FEDF35810C5A8@EXCHANGE1> From: "Jung, Michael" To: "'freebsd-alpha@FreeBSD.ORG'" Subject: Alphserver 2100 4/233 Date: Wed, 19 Jul 2000 10:04:12 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is work on going for the 2100 4/233 ? 5.0-20000525-CURRENT states that system type 9 (ST_DEC_2100_A500) is not supported. We have a couple of these box's and would like to run BSD on them. Thanks --mikej Michael Jung To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jul 19 7:13:37 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id C8E8037B517 for ; Wed, 19 Jul 2000 07:13:28 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA19514; Wed, 19 Jul 2000 10:13:23 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id KAA47193; Wed, 19 Jul 2000 10:13:23 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 19 Jul 2000 10:13:23 -0400 (EDT) To: "Jung, Michael" Cc: "'freebsd-alpha@FreeBSD.ORG'" Subject: Re: Alphserver 2100 4/233 In-Reply-To: <921763828F4BD4118D7D00805FEDF35810C5A8@EXCHANGE1> References: <921763828F4BD4118D7D00805FEDF35810C5A8@EXCHANGE1> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14709.46736.198171.3010@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jung, Michael writes: > Is work on going for the 2100 4/233 ? > > 5.0-20000525-CURRENT states > that system type 9 (ST_DEC_2100_A500) is > not supported. > > We have a couple of these box's and would > like to run BSD on them. You're off by 3 days. I added support for the 2100 on May 28. 2100 support will be in 4.1-RELEASE & the 4.1RC snapshots. Note that 2100A (lynx) machines will almost certainly not work properly at this time. 2100 (sable) and 2000 (demi-sable) machines should be fine though. Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jul 19 7:45:59 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 5040837BF7F; Wed, 19 Jul 2000 07:45:55 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA20124; Wed, 19 Jul 2000 10:45:50 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id KAA47244; Wed, 19 Jul 2000 10:45:50 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 19 Jul 2000 10:45:49 -0400 (EDT) To: "Jung, Michael" Cc: freebsd-alpha@freebsd.org, jkh@freebsd.org Subject: alpha snapshots? (was RE: Alphserver 2100 4/233) In-Reply-To: <921763828F4BD4118D7D00805FEDF35810C5A9@EXCHANGE1> References: <921763828F4BD4118D7D00805FEDF35810C5A9@EXCHANGE1> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14709.48828.202497.430928@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I don't know if there are any more recent snaps than the 5/25 which are currently available. There should be a 4.1RC for alpha "any day now".. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jul 19 8:25:58 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 35D1837BF5A; Wed, 19 Jul 2000 08:25:56 -0700 (PDT) (envelope-from jhb@pike.osd.bsdi.com) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id IAA77616; Wed, 19 Jul 2000 08:25:17 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200007191525.IAA77616@pike.osd.bsdi.com> Subject: Re: alpha snapshots? (was RE: Alphserver 2100 4/233) In-Reply-To: <14709.48828.202497.430928@grasshopper.cs.duke.edu> from Andrew Gallatin at "Jul 19, 2000 10:45:49 am" To: Andrew Gallatin Date: Wed, 19 Jul 2000 08:25:17 -0700 (PDT) Cc: freebsd-alpha@FreeBSD.ORG, jkh@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I don't know if there are any more recent snaps than the 5/25 which > are currently available. There should be a 4.1RC for alpha "any day > now".. > > Drew David O`Brien is working on the alpha RC snapshots. He has RC1 done, we are just waiting on Jordan to put it up somewhere that is publically accesible. *poke* *poke* David is also having fun since we are apparently out of space on the Alpha boot floppies, so he is trying to trim then down to size. :( -- John Baldwin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jul 19 8:37:47 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 7170A37BEB5; Wed, 19 Jul 2000 08:37:42 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA21057; Wed, 19 Jul 2000 11:37:41 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id LAA47339; Wed, 19 Jul 2000 11:37:40 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 19 Jul 2000 11:37:40 -0400 (EDT) To: John Baldwin Cc: freebsd-alpha@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: alpha snapshots? (was RE: Alphserver 2100 4/233) In-Reply-To: <200007191525.IAA77616@pike.osd.bsdi.com> References: <14709.48828.202497.430928@grasshopper.cs.duke.edu> <200007191525.IAA77616@pike.osd.bsdi.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14709.51428.333589.473414@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John Baldwin writes: > > I don't know if there are any more recent snaps than the 5/25 which > > are currently available. There should be a 4.1RC for alpha "any day > > now".. > > > > Drew > > David O`Brien is working on the alpha RC snapshots. He has RC1 done, we > are just waiting on Jordan to put it up somewhere that is publically > accesible. *poke* *poke* David is also having fun since we are apparently > out of space on the Alpha boot floppies, so he is trying to trim then down > to size. :( Hmm.. I'd suggest axing the ncr driver (why is it still in GENERIC now that SYM supports the older devices??). And after that, some of nics which are unlikely to be found in alphas (rl, sf, sis, ste, tl, vr, wb, xl, le, fxp). We really need a modules floppy so we can keep the install kernel small & allow people with uncommon hardware to still install over their uncommon devices.. Since we're the only Open Source OS to support some of the Mylex controllers found in AlphaServers, it would be nice to make it easy for people to install onto one.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jul 19 10:19:29 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id A077837B6C2 for ; Wed, 19 Jul 2000 10:19:24 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13ExVC-000DAU-00; Wed, 19 Jul 2000 17:19:22 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id TAA01495; Wed, 19 Jul 2000 19:19:21 +0200 (CEST) (envelope-from wkb) Date: Wed, 19 Jul 2000 19:19:21 +0200 From: Wilko Bulte To: Andrew Gallatin Cc: "Jung, Michael" , "'freebsd-alpha@FreeBSD.ORG'" Subject: Re: Alphserver 2100 4/233 Message-ID: <20000719191921.A1234@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <921763828F4BD4118D7D00805FEDF35810C5A8@EXCHANGE1> <14709.46736.198171.3010@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <14709.46736.198171.3010@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Jul 19, 2000 at 10:13:23AM -0400 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Jul 19, 2000 at 10:13:23AM -0400, Andrew Gallatin wrote: > > Jung, Michael writes: > > Is work on going for the 2100 4/233 ? > > > > 5.0-20000525-CURRENT states > > that system type 9 (ST_DEC_2100_A500) is > > not supported. > > > > We have a couple of these box's and would > > like to run BSD on them. > > You're off by 3 days. I added support for the 2100 on May 28. > 2100 support will be in 4.1-RELEASE & the 4.1RC snapshots. > > Note that 2100A (lynx) machines will almost certainly not work > properly at this time. 2100 (sable) and 2000 (demi-sable) machines > should be fine though. I've today installed successfully on AS2100. AS2100A fails to install. -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jul 19 10:38:14 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 2555337C02F; Wed, 19 Jul 2000 10:38:10 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13ExnE-000DLf-00; Wed, 19 Jul 2000 17:38:01 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id TAA01574; Wed, 19 Jul 2000 19:30:53 +0200 (CEST) (envelope-from wkb) Date: Wed, 19 Jul 2000 19:30:53 +0200 From: Wilko Bulte To: Andrew Gallatin Cc: John Baldwin , freebsd-alpha@freebsd.org, jkh@freebsd.org Subject: Re: alpha snapshots? (was RE: Alphserver 2100 4/233) Message-ID: <20000719193053.D1234@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <14709.48828.202497.430928@grasshopper.cs.duke.edu> <200007191525.IAA77616@pike.osd.bsdi.com> <14709.51428.333589.473414@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <14709.51428.333589.473414@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Jul 19, 2000 at 11:37:40AM -0400 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Jul 19, 2000 at 11:37:40AM -0400, Andrew Gallatin wrote: > > John Baldwin writes: > > > I don't know if there are any more recent snaps than the 5/25 which > > > are currently available. There should be a 4.1RC for alpha "any day > > > now".. > > > > > > Drew > > > > David O`Brien is working on the alpha RC snapshots. He has RC1 done, we > > are just waiting on Jordan to put it up somewhere that is publically > > accesible. *poke* *poke* David is also having fun since we are apparently > > out of space on the Alpha boot floppies, so he is trying to trim then down > > to size. :( > > Hmm.. I'd suggest axing the ncr driver (why is it still in GENERIC now > that SYM supports the older devices??). > > And after that, some of nics which are unlikely to be found in alphas > (rl, sf, sis, ste, tl, vr, wb, xl, le, fxp). Speaking of which: when looking at the alpha release notes (RELNOTES.TXT) I see an awful lot of adapters/hardware listed as 'supported' of which I'm pretty sure have never seen the inside of any alpha box. Any reason not to axe those? And I'm not speaking of the fact that the RELNOTES IMO are not the place to list supported hardware.. > Since we're the only Open Source OS to support some of the Mylex > controllers found in AlphaServers, it would be nice to make it easy for > people to install onto one.. Seconded.. -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jul 19 12:18:58 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 7AE0537C013 for ; Wed, 19 Jul 2000 12:18:43 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13EzMe-000EZV-00 for freebsd-alpha@freebsd.org; Wed, 19 Jul 2000 19:18:40 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id VAA02248 for freebsd-alpha@freebsd.org; Wed, 19 Jul 2000 21:18:39 +0200 (CEST) (envelope-from wkb) Date: Wed, 19 Jul 2000 21:18:39 +0200 From: Wilko Bulte To: FreeBSD-alpha mailing list Subject: Re: test results for Lynx (AS2100A) Message-ID: <20000719211839.A2061@freebie.demon.nl> Reply-To: wilko@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.2i X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [forgot to cc: -alpha] On Tue, Jul 18, 2000 at 10:50:19AM -0700, Matthew Jacob wrote: > boot verbose, please... Here you are. I have booted a SCSI disk with 4.1RC as of Jul 18 on it that I pre-installed on a AS2100. Wilko Script started on Wed Jul 19 13:16:28 2000 P00>>>sho dev dka600.6.0.2001.0 DKA600 RRD43 1084 dkb0.0.0.9.0 DKB0 RZ29B 0014 dkb600.6.0.9.0 DKB600 RRD46 0557 dra0.0.0.1003.0 DRA0 5 Member RAID 5 =20 drb0.0.0.2006.0 DRB0 2 Member RAID 1 =20 drb1.0.0.2006.0 DRB1 2 Member RAID 1 =20 drb2.0.0.2006.0 DRB2 2 Member RAID 1 =20 dva0.0.0.1000.0 DVA0 RX26/RX23 ewa0.0.0.7.0 EWA0 00-00-F8-23-16-31 pka0.7.0.2001.0 PKA0 SCSI Bus ID 7 pkb0.7.0.9.0 PKB0 SCSI Bus ID 7 5.57 P00>>>boot dkb0 (boot dkb0.0.0.9.0 -flags A) block 0 of dkb0.0.0.9.0 is a valid boot block reading 15 blocks from dkb0.0.0.9.0 bootstrap code read in base =3D 200000, image_start =3D 0, image_bytes =3D 1e00 initializing HWRPB at 2000 initializing page table at 7ff0000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code VMS PAL rev: 0x4000700010538 OSF PAL rev: 0x4000c0002012d Switch to OSF PAL code succeeded. FreeBSD/alpha SRM disk boot, Revision 0.3 (root@miata.wbnet, Tue Jul 18 21:05:09 GMT 2000) Memory: 131072 k Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel] in 9 seconds... Booting [kernel] in 8 seconds... Booting [= kernel]... =20 Entering kernel at 0xfffffc000032b280... Copyright (c) 1992-2000 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 18jul00-41rc #0: Tue Jul 18 22:19:33 GMT 2000 root@miata.wbnet:/usr/src/sys/compile/GENERIC DEC AlphaServer 2100A AlphaServer 2100A 4/200, 190MHz 8192 byte page size, 1 processor. CPU: EV4 (21064) major=3D2 minor=3D1 OSF PAL rev: 0x4000c0002012d real memory =3D 132046848 (128952K bytes) Physical memory chunk(s): 0x00710000 - 0x07fe5fff, 126705664 bytes (15467 pages) avail memory =3D 122511360 (119640K bytes) Preloaded elf kernel "kernel" at 0xfffffc00006f4000. md0: Malloc disk Creating DISK md0 found-> vendor=3D0x8086, dev=3D0x0482, revid=3D0x15 class=3D00-00-00, hdrtype=3D0x00, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 found-> vendor=3D0x1011, dev=3D0x0001, revid=3D0x02 class=3D06-04-00, hdrtype=3D0x01, mfdev=3D0 subordinatebus=3D2 secondarybus=3D2 found-> vendor=3D0x1011, dev=3D0x0002, revid=3D0x24 class=3D02-00-00, hdrtype=3D0x00, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 intpin=3Da, irq=3D68 map[10]: type 1, range 32, base 00010100, size 7 map[14]: type 1, range 32, base 81111000, size 7 found-> vendor=3D0x1077, dev=3D0x1020, revid=3D0x05 class=3D01-00-00, hdrtype=3D0x00, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 intpin=3Da, irq=3D76 map[10]: type 1, range 32, base 00010000, size 8 map[14]: type 1, range 32, base 81110000, size 12 found-> vendor=3D0x0000, dev=3D0x0000, revid=3D0x00 class=3Dff-ff-ff, hdrtype=3D0x7f, mfdev=3D1 subordinatebus=3D0 secondarybus=3D0 intpin=3D[, irq=3D33 found-> vendor=3D0x0000, dev=3D0x0000, revid=3D0x00 class=3D00-00-00, hdrtype=3D0x0f, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 found-> vendor=3D0x0000, dev=3D0x0000, revid=3D0x00 class=3Dff-ff-ff, hdrtype=3D0x7f, mfdev=3D1 subordinatebus=3D0 secondarybus=3D0 intpin=3D[, irq=3D32 found-> vendor=3D0x0000, dev=3D0x0000, revid=3D0x00 class=3D00-00-00, hdrtype=3D0x0f, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 pci0: on pcib0 isab0: at device 2.0 on pci0 isa0: on isab0 pcib1: at device 3.0 on pci0 found-> vendor=3D0x1000, dev=3D0x0001, revid=3D0x11 class=3D01-00-00, hdrtype=3D0x00, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 intpin=3Da, irq=3D60 map[10]: type 1, range 32, base 00005000, size 8 map[14]: type 1, range 32, base 81004000, size 8 found-> vendor=3D0x1069, dev=3D0x0001, revid=3D0x00 class=3D01-04-00, hdrtype=3D0x00, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 intpin=3Da, irq=3D80 map[10]: type 1, range 32, base 00005400, size 7 pci2: on pcib1 sym0: <810a> port 0x5000-0x50ff mem 0x81004000-0x810040ff irq 60 at device = 1.0 on pci2 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking sym0: open drain IRQ line driver sym0: using LOAD/STORE-based firmware. sym0: initial SCNTL3/DMODE/DCNTL/CTEST3/4/5 =3D (hex) 00/00/00/00/00/00 sym0: final SCNTL3/DMODE/DCNTL/CTEST3/4/5 =3D (hex) 03/c2/a0/00/08/00 sym0: Delay (GEN=3D11): 258 msec, 34450 KHz sym0: Delay (GEN=3D11): 283 msec, 31407 KHz sym0: Delay (GEN=3D11): 283 msec, 31407 KHz sym0: interrupting at T2 irq 60 pci2: (vendor=3D0x1069, dev=3D0x0001) at 6.0 irq 80 de0: port 0x10100-0x1017f mem 0x81111000-0x8111107= f irq 68 at device 7.0 on pci0 de0: interrupting at T2 irq 68 de0: DEC 21040 [10Mb/s] pass 2.4 de0: address 00:00:f8:23:16:31 bpf: de0 attached Qlogic ISP Driver, FreeBSD Version 4.4, Core Version 1.16 isp0: port 0x10000-0x100ff mem 0x81= 110000-0x81110fff irq 76 at device 9.0 on pci0 isp0: using Memory space register mapping isp0: set PCI line size to 16 isp0: interrupting at T2 irq 76 isp0: Ultra Mode Capable isp0: Board Revision 1040B, resident F/W Revision 5.57.1 isp0: Last F/W revision was 5.57.1 isp0: 256 max I/O commands supported pci0: (vendor=3D0x0000, dev=3D0x0000) at 12.0 irq 33 pci0: (vendor=3D0x0000, dev=3D0x0000) at 12.4 pci0: (vendor=3D0x0000, dev=3D0x0000) at 13.0 irq 32 pci0: (vendor=3D0x0000, dev=3D0x0000) at 13.4 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: interrupting at T2 irq 6 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 atkbd0: irq 1 on atkbdc0 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 kbd0: atkbd0, generic (0), config:0x0, flags:0x1f0000 atkbd0: interrupting at T2 irq 1 psm0: current command byte:0061 kbdc: TEST_AUX_PORT status:0074 kbdc: DIAGNOSE status:0075 psm: keyboard controller failed. kbdc: TEST_KBD_PORT status:0077 psm: keyboard port failed. psm0: the aux port is not functioning (116). vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xb8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81=20 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96=20 b9 a3 ff 00 04 02 14 01 05 03 07 38 3c 3a 3e 39=20 3d 3b 3f 04 00 0f 08 00 00 00 00 00 10 0e 00 ff=20 VGA parameters in BIOS for mode 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=20 EGA/VGA parameters to be used for mode 24 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81=20 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96=20 b9 a3 ff 00 04 02 14 01 05 03 07 38 3c 3a 3e 39=20 3d 3b 3f 04 00 0f 08 00 00 00 00 00 10 0e 00 ff=20 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=3D0x0> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) mcclock0: at port 0x70-0x71 on isa0 Calibrating clock(s) ... PCC clock: 190008696 Hz (firmware 190114068 Hz) sio0: configured irq 4 not in bitmap of probed irqs 0x1 sio0: irq maps: 0 0x1 0x1 0x1 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A, console sio0: interrupting at T2 irq 4 sio1: reserved for low-level i/o isa_probe_children: probing PnP devices Timecounter "alpha" frequency 190008696 Hz bpf: sl0 attached bpf: ppp0 attached bpf: lo0 attached bpf: gif0 attached bpf: gif1 attached bpf: gif2 attached bpf: gif3 attached bpf: faith0 attached Waiting 15 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. isp0: driver initiated bus reset of bus 0 de0: enabling 10baseT port halted CPU 0 halt code =3D 1 operator initiated halt PC =3D fffffc00003a2e98 P00>>>=00=00~ [EOT] wilklt# wilklt#exit Script done on Wed Jul 19 13:23:46 2000 --=20 Wilko Bulte http://www.freebsd.org =20 wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jul 19 16:22:47 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from zippy.osd.bsdi.com (zippy.osd.bsdi.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 86E3037B56B; Wed, 19 Jul 2000 16:22:40 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id QAA04831; Wed, 19 Jul 2000 16:23:36 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: John Baldwin Cc: Andrew Gallatin , freebsd-alpha@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: alpha snapshots? (was RE: Alphserver 2100 4/233) In-reply-to: Your message of "Wed, 19 Jul 2000 08:25:17 PDT." <200007191525.IAA77616@pike.osd.bsdi.com> Date: Wed, 19 Jul 2000 16:23:36 -0700 Message-ID: <4828.964049016@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As far as I know, David has no ISO image which currently works. I'm waiting for HIM to provide me with one which does. *poke* *poke* - Jordan > > I don't know if there are any more recent snaps than the 5/25 which > > are currently available. There should be a 4.1RC for alpha "any day > > now".. > > > > Drew > > David O`Brien is working on the alpha RC snapshots. He has RC1 done, we > are just waiting on Jordan to put it up somewhere that is publically > accesible. *poke* *poke* David is also having fun since we are apparently > out of space on the Alpha boot floppies, so he is trying to trim then down > to size. :( > > -- > > John Baldwin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jul 19 16:32:31 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id E857037B764 for ; Wed, 19 Jul 2000 16:32:27 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id QAA27822; Wed, 19 Jul 2000 16:41:21 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007192341.QAA27822@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE In-reply-to: Your message of "Mon, 17 Jul 2000 22:37:19 EDT." <14707.48450.371071.494543@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Jul 2000 16:41:21 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I think I have a fix. It feels like overkill, but if the programming > interface of the chip does not allow for something better why not just > turn off DMA while we update cb_command? The gotcha with this is of course that you have no idea what "turning off DMA" actually entails. If the chip is in the middle of a DMA operation, what happens then? Do you lose the entire DMA? Does it keep going? How often does the chip test the flag, etc... > Can a PCI expert comment on its safety? Mike? I think the approach you've taken with using atomic updates is definitely the right one. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jul 19 17: 9:20 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 4738F37B67A for ; Wed, 19 Jul 2000 17:09:15 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id RAA30033 for alpha@freebsd.org; Wed, 19 Jul 2000 17:09:12 -0700 (PDT) (envelope-from obrien) Date: Wed, 19 Jul 2000 17:09:11 -0700 From: "David O'Brien" To: alpha@freebsd.org Subject: 5.0 snapshot on ftp.freebsd.org Message-ID: <20000719170911.A30000@dragon.nuxi.com> Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i 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 X-Loop: FreeBSD.org I have placed a 5.0-20000714-CURRENT DEC Alpha snapshot at ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha/5.0-20000714-CURRENT/ Enjoy! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jul 19 17:56: 2 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 2780C37B765; Wed, 19 Jul 2000 17:55:59 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id RAA30602; Wed, 19 Jul 2000 17:55:58 -0700 (PDT) (envelope-from obrien) Date: Wed, 19 Jul 2000 17:55:58 -0700 From: "David O'Brien" To: alpha@freebsd.org, stable@freebsd.org Subject: 4.1-RC snapshot on ftp.freebsd.org Message-ID: <20000719175558.A30579@dragon.nuxi.com> Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have placed a 4.1-20000718-RC DEC Alpha snapshot at ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha/4.1-20000718-RC/ Enjoy! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jul 19 18: 2: 3 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 53E6C37B765 for ; Wed, 19 Jul 2000 18:02:01 -0700 (PDT) (envelope-from buile@edgenet.net) Received: from edgenet.net ([24.18.158.133]) by mail.rdc1.ct.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000720010201.LQDW3598.mail.rdc1.ct.home.com@edgenet.net> for ; Wed, 19 Jul 2000 18:02:01 -0700 Message-ID: <3976504E.E409FC00@edgenet.net> Date: Wed, 19 Jul 2000 21:05:18 -0400 From: duine buile Reply-To: buile@edgenet.net X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-alpha@freebsd.org Subject: alpha 1000A Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Apologies for asking an install question on this list :( Is it worth it for me to keep plugging away at installing FreeBSD on a 1000A? I get what appears to be probe timeouts on the QLogic ISP1020 scsi adaptor just before the graphic install screen. The install cannot detect any hard drives and cant begin. That's where i'm stuck. I am attempting to boot 5.0 Current using an SRM install ( >>> boot dva0 ). Stable 4.0 gave machine check panics. My attempt at info from notes (i am *brand new* to the Alpha... knew nothing about it the day before i attempted the install): Alpha AS1000A 4/266 64MB RAM QLogic ISP1020, DECchip 21040-AA Slot 0 QLogic ISP1020 Hose 0 Bus 2 PCI pka 0.7.0.2000.0 SCSI Bus ID 7 dva 0 is in here somewhere dka 0.0.0.2000.0 RZ28 (no "B" on this one) dka 100.1.0.2000.0 RZ28B dka 200.2.0.2000.0 RZ28B dka 300.3.0.2000.0 RZ28B dka 600.6.0.2000.0 RRD43 dka 500.5.0.2000.0 TLZ06 Any and all help is appreciated. --- other problematic behavior --- constant ST0=40 read/address mark missing errors from all floppies i tried. All the floppies work fine on other FreeBSD, Linux, WinNT systems so i no longer think the floppies are at fault. It boots the kernel and brings me to the graphic install screen so they get me there. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jul 19 18:10: 5 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 714BB37B8FC for ; Wed, 19 Jul 2000 18:10:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id SAA42426; Wed, 19 Jul 2000 18:10:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: by hub.freebsd.org (Postfix, from userid 32767) id AC8EA37B6A3; Wed, 19 Jul 2000 18:04:08 -0700 (PDT) Message-Id: <20000720010408.AC8EA37B6A3@hub.freebsd.org> Date: Wed, 19 Jul 2000 18:04:08 -0700 (PDT) From: dhankins@mercenary.net To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: alpha/20047: FreeBSD does not yet support system type 201 (???). Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 20047 >Category: alpha >Synopsis: FreeBSD does not yet support system type 201 (???). >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-alpha >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jul 19 18:10:01 PDT 2000 >Closed-Date: >Last-Modified: >Originator: David W. Hankins >Release: 3.4, 4.0, 5.0-CURRENT all replicate >Organization: Mercenaries Anonymous >Environment: Alpha Processor, Inc UP1000 motherboard. >Description: Install floppies fail after control goes to kernel: FreeBSD does not yet support system type 201 (???). panic: platform not supported Uptime: 0s Anyone working on it? API's stuff is getting pc-cheap, so we're likely to see a lot of them around. >How-To-Repeat: Use freebsd install floppies on an API-motherboarded system. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jul 19 18:31:38 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 9127B37B684 for ; Wed, 19 Jul 2000 18:31:35 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA00825; Wed, 19 Jul 2000 21:31:33 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id VAA48621; Wed, 19 Jul 2000 21:31:33 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 19 Jul 2000 21:31:33 -0400 (EDT) To: dhankins@mercenary.net Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: alpha/20047: FreeBSD does not yet support system type 201 (???). In-Reply-To: <20000720010408.AC8EA37B6A3@hub.freebsd.org> References: <20000720010408.AC8EA37B6A3@hub.freebsd.org> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14710.22017.650094.119362@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org dhankins@mercenary.net writes: > Anyone working on it? API's stuff is getting pc-cheap, so we're > likely to see a lot of them around. > >How-To-Repeat: > Use freebsd install floppies on an API-motherboarded system. > >Fix: Support for the UP1000 was recently added to both -current and -stable. Try the 4.1 release candidate at: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha/4.1-20000718-RC/ Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jul 19 18:33:19 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id C147237B931 for ; Wed, 19 Jul 2000 18:33:16 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA00854; Wed, 19 Jul 2000 21:33:15 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id VAA48627; Wed, 19 Jul 2000 21:33:15 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 19 Jul 2000 21:33:15 -0400 (EDT) To: buile@edgenet.net Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: alpha 1000A In-Reply-To: <3976504E.E409FC00@edgenet.net> References: <3976504E.E409FC00@edgenet.net> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14710.22200.3214.302606@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org duine buile writes: > Apologies for asking an install question on this list :( > > Is it worth it for me to keep plugging away at installing FreeBSD on a > 1000A? I get what appears to be probe timeouts on the QLogic ISP1020 > scsi adaptor just before the graphic install screen. The install cannot > detect any hard drives and cant begin. That's where i'm stuck. > Again, are you sure the drives are spun up? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jul 19 18:38: 5 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 43A5537B5A9 for ; Wed, 19 Jul 2000 18:38:02 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id SAA06376; Wed, 19 Jul 2000 18:37:56 -0700 Date: Wed, 19 Jul 2000 18:37:59 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: buile@edgenet.net, freebsd-alpha@FreeBSD.ORG Subject: Re: alpha 1000A In-Reply-To: <14710.22200.3214.302606@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It's crucial to know whether this is with the 4.1RC or -current. On Wed, 19 Jul 2000, Andrew Gallatin wrote: > > duine buile writes: > > Apologies for asking an install question on this list :( > > > > Is it worth it for me to keep plugging away at installing FreeBSD on a > > 1000A? I get what appears to be probe timeouts on the QLogic ISP1020 > > scsi adaptor just before the graphic install screen. The install cannot > > detect any hard drives and cant begin. That's where i'm stuck. > > > > Again, are you sure the drives are spun up? > > Drew > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jul 19 18:39:14 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E4EAD37B931 for ; Wed, 19 Jul 2000 18:39:10 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id SAA06385; Wed, 19 Jul 2000 18:39:06 -0700 Date: Wed, 19 Jul 2000 18:39:08 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: duine buile Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: alpha 1000A In-Reply-To: <3976504E.E409FC00@edgenet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Is it worth it for me to keep plugging away at installing FreeBSD on a > 1000A? I get what appears to be probe timeouts on the QLogic ISP1020 Details, damn it! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 0:45: 1 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 9C7F437BAF9; Thu, 20 Jul 2000 00:44:46 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13FB0a-000L2X-01; Thu, 20 Jul 2000 07:44:41 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id JAA06446; Thu, 20 Jul 2000 09:32:34 +0200 (CEST) (envelope-from wkb) Date: Thu, 20 Jul 2000 09:32:34 +0200 From: Wilko Bulte To: "David O'Brien" Cc: alpha@freebsd.org, stable@freebsd.org Subject: Re: 4.1-RC snapshot on ftp.freebsd.org Message-ID: <20000720093233.A6432@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <20000719175558.A30579@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000719175558.A30579@dragon.nuxi.com>; from obrien@freebsd.org on Wed, Jul 19, 2000 at 05:55:58PM -0700 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Jul 19, 2000 at 05:55:58PM -0700, David O'Brien wrote: > I have placed a 4.1-20000718-RC DEC Alpha snapshot at > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha/4.1-20000718-RC/ > > Enjoy! No :-( It has no /boot and no kernel... And I wanted to see if I could get a bootable CD... -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 6: 6:15 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from lh2.rdc1.tx.home.com (ha2.rdc1.tx.home.com [24.4.0.67]) by hub.freebsd.org (Postfix) with ESMTP id 7FD7737B54D; Thu, 20 Jul 2000 06:06:08 -0700 (PDT) (envelope-from miklic@ibm.net) Received: from ibm.net ([24.10.140.87]) by lh2.rdc1.tx.home.com (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20000720130607.PVQG13510.lh2.rdc1.tx.home.com@ibm.net>; Thu, 20 Jul 2000 06:06:07 -0700 Message-ID: <3976F9FA.CFAF8EEE@ibm.net> Date: Thu, 20 Jul 2000 07:09:14 -0600 From: "Andrew M. Miklic" X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 4.1-RC alpha) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-alpha@freebsd.org, wilko@freebsd.org Subject: [Fwd: More ppc diffs] Content-Type: multipart/mixed; boundary="------------923E08B669CA3DF4E2E52C4E" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------923E08B669CA3DF4E2E52C4E Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Wilko, vpo (aka zip-drive support) now works for Alpha with relocatable ppc port ranges (any range but 0x3bc will work), and native SuperI/O chipset support for the Miata (as well as relocatable ppc port ranges for other National Semiconductor PC873xx SuperI/O-based machines) has been added... Andrew --------------923E08B669CA3DF4E2E52C4E Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Received: from finch-post-10.mail.demon.net [194.217.242.38] by in3.prserv.net id 964085289.65770-1 ; Thu, 20 Jul 2000 09:28:09 +0000 Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 13FCch-000LuZ-0A for miklic@ibm.net; Thu, 20 Jul 2000 09:28:08 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA61450 for ; Thu, 20 Jul 2000 10:29:40 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Thu, 20 Jul 2000 10:29:02 +0100 (BST) From: Doug Rabson To: "Andrew M. Miklic" Subject: Re: More ppc diffs In-Reply-To: <397647FA.A7B070BB@ibm.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mozilla-Status2: 00000000 On Wed, 19 Jul 2000, Andrew M. Miklic wrote: > Doug, > > I've got another set of diffs that I'd like to get into 4.1 (if > still possible)--these diffs add the support for the SuperI/O chipset on > the Miata (PC87303), and adds support for relocating the port addresses > of all PC873xx devices (this should also fix the timeout problem with > the vpo on your machine)... > > Can you give these a try (I did both 5.0 diffs, as well as > back-ported 4.0 diffs)? I have just committed this. It works very nicely and detects the Miata chipset. After I added a hint to my kernel configuration about where to relocate the ppc port, the zip+ drive started working too. I'll give it a day to settle in -current and then I'll submit a patch to the release engineer for 4.1 (we are in code freeze now). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 20 8348 3944 --------------923E08B669CA3DF4E2E52C4E-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 10:59:58 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id D029C37B6D5; Thu, 20 Jul 2000 10:59:53 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA15759; Thu, 20 Jul 2000 13:59:53 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id NAA50533; Thu, 20 Jul 2000 13:59:53 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 20 Jul 2000 13:59:53 -0400 (EDT) To: obrien@freebsd.org Subject: dhclient breaks alpha RELENG_4 buildworld Cc: freebsd-alpha@freebsd.org X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14711.15628.540509.396810@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David, An alpha -stable buildworld just died in dhclient: cc -O -pipe -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp/includes -I/usr/src/ sbin/dhclient/../../contrib/isc-dhcp -DCLIENT_PATH='"PATH=/sbin:/usr/sbin:/bin"' -I/usr/obj/usr/src/alpha/usr/include -c /usr/src/sbin/dhclient/../../contrib/ isc-dhcp/common/hash.c /usr/src/sbin/dhclient/../../contrib/isc-dhcp/client/dhclient.c: In function `dh cp_option_ev_name': /usr/src/sbin/dhclient/../../contrib/isc-dhcp/client/dhclient.c:2178: argument ` buflen' doesn't match prototype /usr/src/sbin/dhclient/../../contrib/isc-dhcp/includes/dhcpd.h:909: prototype de claration *** Error code 1 The following fixes it: Index: dhclient.c =================================================================== RCS file: /home/ncvs/src/contrib/isc-dhcp/client/dhclient.c,v retrieving revision 1.9.2.2 diff -u -r1.9.2.2 dhclient.c --- dhclient.c 2000/07/20 10:26:14 1.9.2.2 +++ dhclient.c 2000/07/20 17:57:21 @@ -2173,7 +2173,7 @@ int dhcp_option_ev_name (buf, buflen, option) char *buf; - unsigned buflen; + size_t buflen; struct option *option; { int i; (I think this also applied to -current) I'm reluctant to commit anything in src/contrib because I don't understand the rules for CVS on contributed software, or I'd commit it myself. Cheers, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 11:39:33 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from front1.grolier.fr (front1.grolier.fr [194.158.96.51]) by hub.freebsd.org (Postfix) with ESMTP id 2929B37B6BE; Thu, 20 Jul 2000 11:39:27 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from Guyancourt-1-173.club-internet.fr (nas1-173.guy.club-internet.fr [195.36.205.173]) by front1.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id UAA17300; Thu, 20 Jul 2000 20:39:16 +0200 (MET DST) Date: Thu, 20 Jul 2000 20:18:53 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Mike Smith Cc: Andrew Gallatin , freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE In-Reply-To: <200007192341.QAA27822@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 19 Jul 2000, Mike Smith wrote: > > I think I have a fix. It feels like overkill, but if the programming > > interface of the chip does not allow for something better why not just > > turn off DMA while we update cb_command? >=20 > The gotcha with this is of course that you have no idea what "turning off= =20 > DMA" actually entails. If the chip is in the middle of a DMA operation,= =20 > what happens then? Do you lose the entire DMA? Does it keep going? How= =20 > often does the chip test the flag, etc... >=20 > > Can a PCI expert comment on its safety? Mike? >=20 > I think the approach you've taken with using atomic updates is definitely= =20 > the right one. I donnot think so. ;-) Here are some of the reasons: 1) Use of Load/Locked Store/Conditional CPU instructions to synchronize=20 with another agent on the system BUS requires the other agent to=20 implement some given protocol for the involved access. The other agent= =20 is the host bridge as you know and not another CPU. What's our knowledge about the behaviour of the bridge? 2) We also ignore the width of the access performed by the PCI device. Is it a 16 bit access or a full DWORD access. And how will the memory controller do the memory access if 16bit: A) Use 16 bit atomic modify (if supported by the hardware) ? or B) Read a full DWORD atomically, clear the bit, Modify the full DWORD ? The only win of this patch is that it (seems to?) work, and obviously user= =20 want to use it. Early committing it is another story and you can count me= =20 as opposed to this commit. ;-) What is 100% sure is that the change does force a memory barrier before the offending instruction and after it. I donnot seem to see that just adding these 2 barriers has been investigated. This should be tried, IMHO. As you know modern CPUs do speculative executions and other optimizations that may reorder LOADs and STOREs in a way that can break programmer assumptions about ordering of LOADs and STOREs when carried out to the=20 system BUS. As a result ( applying to my opinion ;-) ), when a PCI device and its software driver communicates through the main memory, it is _very_ likely memory barrier to be needed in some places so that program-expected ordering as seen from the system BUS will happen. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 11:47: 8 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 45E8337B6BE for ; Thu, 20 Jul 2000 11:47:06 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from gale.cs.duke.edu (gale.cs.duke.edu [152.3.145.6]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA16931; Thu, 20 Jul 2000 14:46:58 -0400 (EDT) From: Andrew Gallatin Received: (gallatin@localhost) by gale.cs.duke.edu (8.8.4/8.6.9) id OAA29958; Thu, 20 Jul 2000 14:46:58 -0400 (EDT) Date: Thu, 20 Jul 2000 14:46:58 -0400 (EDT) Message-Id: <200007201846.OAA29958@gale.cs.duke.edu> To: groudier@club-internet.fr Subject: Re: fxp0 hangs on a PC164 using STABLE Cc: freebsd-alpha@FreeBSD.ORG Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Please read the 21264 CPU manual. From this document, it appears the fix is correct. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 11:56:46 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id EA1EE37B7CA; Thu, 20 Jul 2000 11:56:42 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA09278; Thu, 20 Jul 2000 11:56:17 -0700 Date: Thu, 20 Jul 2000 11:56:20 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Cc: Mike Smith , Andrew Gallatin , freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 1) Use of Load/Locked Store/Conditional CPU instructions to synchronize > with another agent on the system BUS requires the other agent to > implement some given protocol for the involved access. The other agent > is the host bridge as you know and not another CPU. > What's our knowledge about the behaviour of the bridge? The Alpha Architecture reference manual is a little ambiguous about this, but it is our belief (based on feedbacdk from this list) that the memory subsystem must be architected such that it doesn't matter whether or not it is a CPU or any other device. > > 2) We also ignore the width of the access performed by the PCI device. > Is it a 16 bit access or a full DWORD access. > And how will the memory controller do the memory access if 16bit: > A) Use 16 bit atomic modify (if supported by the hardware) ? > or > B) Read a full DWORD atomically, clear the bit, Modify the full DWORD ? The underlying instruction covers either 32 or 64 bits. In the FreeBSD alpha implementation, the 64 bit instruction is used (maybe overkill) and shifts and ors and masks are done as appropriate. The object being changed is 16 bits, so the usage is correct. As long as either the 32 or 64 bits of address fully overlaps the access that the PCI device will be making (which is likely to be an RMW cycle), the semantics of the interlock will guarantee that the disparate size of access will be irrelevant. > the offending instruction and after it. I donnot seem to see that just > adding these 2 barriers has been investigated. This should be tried, IMHO. > As you know modern CPUs do speculative executions and other optimizations > that may reorder LOADs and STOREs in a way that can break programmer > assumptions about ordering of LOADs and STOREs when carried out to the > system BUS. A memory barrier here would not help since they are implied by the ldq_l/stq_c pair, but, hell, let's put one just for grins. Drew? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 12: 3: 5 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5652037C0F6 for ; Thu, 20 Jul 2000 12:03:01 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA09332; Thu, 20 Jul 2000 12:02:54 -0700 Date: Thu, 20 Jul 2000 12:02:56 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Cc: freebsd-alpha@FreeBSD.ORG Subject: more on- Re: fxp0 hangs on a PC164 using STABLE In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > A memory barrier here would not help since they are implied by the ldq_l/stq_c > pair, but, hell, let's put one just for grins. Drew? > You are, btw, absolutely right, in general, about the usage of memory barriers. Any shared memory model device in alpha should be using barrier instructions. We're given them for free with I/O and Mem space register accesses, but you have to add them by hand otherwise. The Qlogic driver uses them extensively. There's every reason to assume that they would be useful in i386 too, no? It sounds to me that this would be a good argument for a simple inline or asm for both i386 && alpha ports. Now, the sparc port will be more interesting because a plain 'memory barrier' is not what's there - instead you have to do explicit address based flushing and/or invalidation (depending on the platform). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 12:11:24 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 9B48237B5E3 for ; Thu, 20 Jul 2000 12:11:18 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from gale.cs.duke.edu (gale.cs.duke.edu [152.3.145.6]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id PAA17490; Thu, 20 Jul 2000 15:11:16 -0400 (EDT) From: Andrew Gallatin Received: (gallatin@localhost) by gale.cs.duke.edu (8.8.4/8.6.9) id PAA15726; Thu, 20 Jul 2000 15:11:16 -0400 (EDT) Date: Thu, 20 Jul 2000 15:11:16 -0400 (EDT) Message-Id: <200007201911.PAA15726@gale.cs.duke.edu> To: mjacob@feral.com Subject: Re: fxp0 hangs on a PC164 using STABLE Cc: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On the last, (putting in a memory barrier) -- I object because its implicit in the atomic instructions & would be totally superfulous. An addition to the comment to point this out might be appropriate though.. WRT memory barriers on i86 -- I though that writes to device memory space were uncachable & flushed the write buffers unless an mtrr was set up for the region & it was made cacheable. I defer to the i86 experts.. As for flushing writes to main memory for better device communication, I have no clue.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 12:15: 4 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id DEA4037B5B5 for ; Thu, 20 Jul 2000 12:15:01 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id MAA67421; Thu, 20 Jul 2000 12:14:59 -0700 (PDT) (envelope-from obrien) Date: Thu, 20 Jul 2000 12:14:59 -0700 From: "David O'Brien" To: Andrew Gallatin Cc: freebsd-alpha@freebsd.org Subject: Re: dhclient breaks alpha RELENG_4 buildworld Message-ID: <20000720121459.A67395@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <14711.15628.540509.396810@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <14711.15628.540509.396810@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Thu, Jul 20, 2000 at 01:59:53PM -0400 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 X-Loop: FreeBSD.org On Thu, Jul 20, 2000 at 01:59:53PM -0400, Andrew Gallatin wrote: > An alpha -stable buildworld just died in dhclient: Crap! [I killed my own Alpha 4.1 release build] Well I did test compile the code, just on an Intelcrap box. ;-) Foo. Let me think about how I want to fix this. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 12:19: 1 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D05A937BE90 for ; Thu, 20 Jul 2000 12:18:59 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA09402; Thu, 20 Jul 2000 12:18:57 -0700 Date: Thu, 20 Jul 2000 12:19:00 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: freebsd-alpha@freebsd.org Subject: Re: fxp0 hangs on a PC164 using STABLE In-Reply-To: <200007201911.PAA15726@gale.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 20 Jul 2000, Andrew Gallatin wrote: > On the last, (putting in a memory barrier) -- I object because its implicit > in the atomic instructions & would be totally superfulous. An addition > to the comment to point this out might be appropriate though.. Okay. > WRT memory barriers on i86 -- I though that writes to device memory space > were uncachable & flushed the write buffers unless an mtrr was set > up for the region & it was made cacheable. I defer to the i86 experts.. Which could happen. > As for flushing writes to main memory for better device communication, > I have no clue.. > > Drew > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 12:56:18 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from front5m.grolier.fr (front5m.grolier.fr [195.36.216.55]) by hub.freebsd.org (Postfix) with ESMTP id F01D337C0BD for ; Thu, 20 Jul 2000 12:56:13 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from Guyancourt-2-214.club-internet.fr (Guyancourt-2-214.club-internet.fr [195.36.206.214] (may be forged)) by front5m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id VAA00676; Thu, 20 Jul 2000 21:56:00 +0200 (MET DST) Date: Thu, 20 Jul 2000 21:35:38 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Matthew Jacob Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: more on- Re: fxp0 hangs on a PC164 using STABLE In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 20 Jul 2000, Matthew Jacob wrote: > > A memory barrier here would not help since they are implied by the ldq_= l/stq_c > > pair, but, hell, let's put one just for grins. Drew? Hmmm... I meant, first revert the patch, then add the barriers. Damn... I know I am idiot but I thought nobody else discovered it. ;) > You are, btw, absolutely right, in general, about the usage of memory > barriers. Any shared memory model device in alpha should be using barrier > instructions. We're given them for free with I/O and Mem space register > accesses, but you have to add them by hand otherwise. The Qlogic driver u= ses > them extensively. >=20 > There's every reason to assume that they would be useful in i386 too, no? They may well be so, for example, in the situation of the PCI device and its software driver sharing a completion queue in memory. Then a serialization instruction may be needed after having picked the completion thing from the completion queue and before checking the associated status data. This is due to the PII/PIII also reodering LOADs/STOREs in some way. > It sounds to me that this would be a good argument for a simple inline or= asm > for both i386 && alpha ports. Agreed. > Now, the sparc port will be more interesting because a plain 'memory barr= ier' > is not what's there - instead you have to do explicit address based flush= ing > and/or invalidation (depending on the platform). Seems Linux does cope of that without too much complexity. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 13: 3:28 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id F2A2537B67E for ; Thu, 20 Jul 2000 13:03:25 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA67831; Thu, 20 Jul 2000 13:03:24 -0700 (PDT) (envelope-from obrien) Date: Thu, 20 Jul 2000 13:03:24 -0700 From: "David O'Brien" To: Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: alpha snapshots? (was RE: Alphserver 2100 4/233) Message-ID: <20000720130323.B67647@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <14709.48828.202497.430928@grasshopper.cs.duke.edu> <200007191525.IAA77616@pike.osd.bsdi.com> <14709.51428.333589.473414@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <14709.51428.333589.473414@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Jul 19, 2000 at 11:37:40AM -0400 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 X-Loop: FreeBSD.org On Wed, Jul 19, 2000 at 11:37:40AM -0400, Andrew Gallatin wrote: > Hmm.. I'd suggest axing the ncr driver (why is it still in GENERIC now > that SYM supports the older devices??). I feel groudier would be a better judge of this than I am. If he agrees, I'll axe it out. > And after that, some of nics which are unlikely to be found in alphas > (rl, sf, sis, ste, tl, vr, wb, xl, le, fxp). Overall I could go this way, but not with the list above. Right now `xl' is the best Alpha NIC we have. With `xl' removed, I wouldn't be able to install on my AS 250 as it is on a 100-mbit only switch via an `xl'. `xl' is the only NIC in my PC164SX box. Since you've fixed `fxp', I think many will use that too -- especially in 164LX, PC164SX, NoName's, etc.. (ie, anything that was mostly sold as only a CPU + mobo combination). If someone wants to bug him, wpaul would probably be a better judge of which of the above list isn't well suited for use in an Alpha. And even then you know someone will try on of the lesser cards. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 13: 4: 0 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id DD85037B5C7 for ; Thu, 20 Jul 2000 13:03:57 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA09587; Thu, 20 Jul 2000 13:03:45 -0700 Date: Thu, 20 Jul 2000 13:03:48 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: more on- Re: fxp0 hangs on a PC164 using STABLE In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hmmm... I meant, first revert the patch, then add the barriers. > Damn... I know I am idiot but I thought nobody else discovered it. ;) :-) > > There's every reason to assume that they would be useful in i386 too, no? > > They may well be so, for example, in the situation of the PCI device and > its software driver sharing a completion queue in memory. Then a > serialization instruction may be needed after having picked the completion > thing from the completion queue and before checking the associated status > data. This is due to the PII/PIII also reodering LOADs/STOREs in some way. > > > It sounds to me that this would be a good argument for a simple inline or asm > > for both i386 && alpha ports. > > Agreed. > > > Now, the sparc port will be more interesting because a plain 'memory barrier' > > is not what's there - instead you have to do explicit address based flushing > > and/or invalidation (depending on the platform). > > Seems Linux does cope of that without too much complexity. Ooh, I those kind of arguments are tough to answer....:-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 13: 8: 6 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 16AA337C11B; Thu, 20 Jul 2000 13:08:02 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA09601; Thu, 20 Jul 2000 13:07:59 -0700 Date: Thu, 20 Jul 2000 13:08:01 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: Andrew Gallatin , freebsd-alpha@FreeBSD.ORG Subject: Re: alpha snapshots? (was RE: Alphserver 2100 4/233) In-Reply-To: <20000720130323.B67647@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 20 Jul 2000, David O'Brien wrote: > On Wed, Jul 19, 2000 at 11:37:40AM -0400, Andrew Gallatin wrote: > > Hmm.. I'd suggest axing the ncr driver (why is it still in GENERIC now > > that SYM supports the older devices??). > > I feel groudier would be a better judge of this than I am. > If he agrees, I'll axe it out. Does it support the 810 (not the 810a)? > > And after that, some of nics which are unlikely to be found in alphas > > (rl, sf, sis, ste, tl, vr, wb, xl, le, fxp). > > Overall I could go this way, but not with the list above. Right now `xl' > is the best Alpha NIC we have. With `xl' removed, I wouldn't be able to > install on my AS 250 as it is on a 100-mbit only switch via an `xl'. > `xl' is the only NIC in my PC164SX box. Huh? I've found de and dc to be satisfactory. > Since you've fixed `fxp', I think many will use that too -- especially in > 164LX, PC164SX, NoName's, etc.. (ie, anything that was mostly sold as > only a CPU + mobo combination). > > If someone wants to bug him, wpaul would probably be a better judge of > which of the above list isn't well suited for use in an Alpha. And even > then you know someone will try on of the lesser cards. With fxp && some working tulip chip driver in place, we should focus on other issues, IMO. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 13:15:41 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from front2.grolier.fr (front2.grolier.fr [194.158.96.52]) by hub.freebsd.org (Postfix) with ESMTP id 6B73637C24E for ; Thu, 20 Jul 2000 13:15:23 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from nas1-93.guy.club-internet.fr (nas1-93.guy.club-internet.fr [195.36.205.93]) by front2.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id WAA06222; Thu, 20 Jul 2000 22:14:48 +0200 (MET DST) Date: Thu, 20 Jul 2000 21:54:24 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Andrew Gallatin Cc: mjacob@feral.com, freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE In-Reply-To: <200007201911.PAA15726@gale.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 20 Jul 2000, Andrew Gallatin wrote: > On the last, (putting in a memory barrier) -- I object because its implic= it > in the atomic instructions & would be totally superfulous. An addition= =20 > to the comment to point this out might be appropriate though.. This has been a misunderstanding. > WRT memory barriers on i86 -- I though that writes to device memory space > were uncachable & flushed the write buffers unless an mtrr was set > up for the region & it was made cacheable. I defer to the i86 experts.. > As for flushing writes to main memory for better device communication, > I have no clue.. We are speaking about a PCI device and its driver sharing main memory. There are ordering issues in such situations even for IA32 due to possible reordering of LOADs notably. Only considering ordering of IO/MMIO is not enough when the PCI device=20 and its software driver communicates through the main memory. The NewBus IO/MMIO stuff does not help here. At most, it may be enough=20 for device/driver pairs that only communicate through IO/MMIO. I want to say that any PCI device / software driver pair that share main memory (for command queues, for example) that donnot use additional explicit memory barriers are very likely to be broken on modern RISC processors and may also be broken on PII/PIII if processor ordering (as described by Intel) is not enough for ordering to be as program expects. It is my opinion. You may disagree but it will hard for anybody to convince me that I am wrong. ;-) G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 13:23: 2 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 4878A37C105; Thu, 20 Jul 2000 13:22:55 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13FMqH-0002kp-00; Thu, 20 Jul 2000 20:22:49 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id WAA09877; Thu, 20 Jul 2000 22:22:49 +0200 (CEST) (envelope-from wkb) Date: Thu, 20 Jul 2000 22:22:49 +0200 From: Wilko Bulte To: "David O'Brien" Cc: Andrew Gallatin , freebsd-alpha@freebsd.org Subject: Re: alpha snapshots? (was RE: Alphserver 2100 4/233) Message-ID: <20000720222249.A9806@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <14709.48828.202497.430928@grasshopper.cs.duke.edu> <200007191525.IAA77616@pike.osd.bsdi.com> <14709.51428.333589.473414@grasshopper.cs.duke.edu> <20000720130323.B67647@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000720130323.B67647@dragon.nuxi.com>; from obrien@freebsd.org on Thu, Jul 20, 2000 at 01:03:24PM -0700 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jul 20, 2000 at 01:03:24PM -0700, David O'Brien wrote: > On Wed, Jul 19, 2000 at 11:37:40AM -0400, Andrew Gallatin wrote: > > Hmm.. I'd suggest axing the ncr driver (why is it still in GENERIC now > > that SYM supports the older devices??). > > I feel groudier would be a better judge of this than I am. > If he agrees, I'll axe it out. > > > And after that, some of nics which are unlikely to be found in alphas > > (rl, sf, sis, ste, tl, vr, wb, xl, le, fxp). > > Overall I could go this way, but not with the list above. Right now `xl' > is the best Alpha NIC we have. With `xl' removed, I wouldn't be able to > install on my AS 250 as it is on a 100-mbit only switch via an `xl'. > `xl' is the only NIC in my PC164SX box. > > Since you've fixed `fxp', I think many will use that too -- especially in > 164LX, PC164SX, NoName's, etc.. (ie, anything that was mostly sold as > only a CPU + mobo combination). Wait a sec: did I miss the 'fxp is now OK'? If yes, I better cleanup RELNOTES because it looked like (to me) that fxp on alpha was a bad idea. -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 13:26:13 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 2ECAA37C102 for ; Thu, 20 Jul 2000 13:26:10 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA68367; Thu, 20 Jul 2000 13:26:01 -0700 (PDT) (envelope-from obrien) Date: Thu, 20 Jul 2000 13:26:01 -0700 From: "David O'Brien" To: Matthew Jacob Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: alpha snapshots? (was RE: Alphserver 2100 4/233) Message-ID: <20000720132601.C67647@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000720130323.B67647@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Thu, Jul 20, 2000 at 01:08:01PM -0700 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 X-Loop: FreeBSD.org On Thu, Jul 20, 2000 at 01:08:01PM -0700, Matthew Jacob wrote: > > > And after that, some of nics which are unlikely to be found in alphas > > > (rl, sf, sis, ste, tl, vr, wb, xl, le, fxp). > > > > Overall I could go this way, but not with the list above. Right now `xl' > > is the best Alpha NIC we have. With `xl' removed, I wouldn't be able to > > install on my AS 250 as it is on a 100-mbit only switch via an `xl'. > > `xl' is the only NIC in my PC164SX box. > > Huh? I've found de and dc to be satisfactory. Yes, if you happen to have a `dc' or `de' card laying around. Please don't forget the PC164SX comes with no no-board NIC. So the assembler of the machine is able to install their favorite NIC (or some cheapass Fry's POS). Or did you mean the performance issue? Only `xl' and `fxp' can do zero-copy on coming packets (as wpaul told me yesterday). wpaul seems to prefer the `xl' cards, and I want to use the NIC he supports the best, so I prefer to use `xl' when possible. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 13:32:10 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 57B5E37B5C7; Thu, 20 Jul 2000 13:32:05 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA68485; Thu, 20 Jul 2000 13:32:03 -0700 (PDT) (envelope-from obrien) Date: Thu, 20 Jul 2000 13:32:03 -0700 From: "David O'Brien" To: wilko@freebsd.org Cc: Andrew Gallatin , freebsd-alpha@freebsd.org Subject: Re: alpha snapshots? (was RE: Alphserver 2100 4/233) Message-ID: <20000720133203.B68454@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <14709.48828.202497.430928@grasshopper.cs.duke.edu> <200007191525.IAA77616@pike.osd.bsdi.com> <14709.51428.333589.473414@grasshopper.cs.duke.edu> <20000720130323.B67647@dragon.nuxi.com> <20000720222249.A9806@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000720222249.A9806@freebie.demon.nl>; from wkb@freebie.demon.nl on Thu, Jul 20, 2000 at 10:22:49PM +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 X-Loop: FreeBSD.org On Thu, Jul 20, 2000 at 10:22:49PM +0200, Wilko Bulte wrote: > Wait a sec: did I miss the 'fxp is now OK'? If yes, I better cleanup > RELNOTES because it looked like (to me) that fxp on alpha was a bad idea. s/is/is probably/ for 5-CURRENT. Andrew made a fix. It may or may not fix the problem I was having 9mo. ago. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 13:34:59 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id DDAA837B52E; Thu, 20 Jul 2000 13:34:52 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA09695; Thu, 20 Jul 2000 13:34:51 -0700 Date: Thu, 20 Jul 2000 13:34:54 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: alpha snapshots? (was RE: Alphserver 2100 4/233) In-Reply-To: <20000720132601.C67647@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Yes, if you happen to have a `dc' or `de' card laying around. Please > don't forget the PC164SX comes with no no-board NIC. So the assembler of > the machine is able to install their favorite NIC (or some cheapass Fry's > POS). Tulip cards are super cheap ($19.87 for a Netgear 2114X @ CDW.COM). The only reason to use an ISA card is if you're desperate for the PCI slots. > Or did you mean the performance issue? Only `xl' and `fxp' can do > zero-copy on coming packets (as wpaul told me yesterday). wpaul seems to > prefer the `xl' cards, and I want to use the NIC he supports the best, so > I prefer to use `xl' when possible. Well, we use what we know works and are comfortable with. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 14:33: 3 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from front6.grolier.fr (front6.grolier.fr [194.158.96.56]) by hub.freebsd.org (Postfix) with ESMTP id 0C73737B65D; Thu, 20 Jul 2000 14:32:43 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from nas1-252.cgy.club-internet.fr (nas1-252.cgy.club-internet.fr [195.36.197.252]) by front6.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id XAA02551; Thu, 20 Jul 2000 23:32:22 +0200 (MET DST) Date: Thu, 20 Jul 2000 23:11:59 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: "David O'Brien" Cc: Andrew Gallatin , freebsd-alpha@FreeBSD.ORG Subject: Re: alpha snapshots? (was RE: Alphserver 2100 4/233) In-Reply-To: <20000720130323.B67647@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 20 Jul 2000, David O'Brien wrote: > On Wed, Jul 19, 2000 at 11:37:40AM -0400, Andrew Gallatin wrote: > > Hmm.. I'd suggest axing the ncr driver (why is it still in GENERIC now= =20 > > that SYM supports the older devices??).=20 >=20 > I feel groudier would be a better judge of this than I am. > If he agrees, I'll axe it out. I can explain, but I am not the right judge for that at all. IMO, the following are to be considered for Alpha for latest SYM as in current and RELENG_4: - The SYM requires 32 bit DWORD (LWORD for Dec people) write (modify but not update) accesses to its internal data structures in main memory from the BUS (bridge) and from the CPU to happen atomically. (I think this is the same for NCR). I just hope gcc will not play with 64 bit access=20 when the driver states a volatile access to a 32 bit entity. - The SYM implements all barriers that appear to me needed (only one is =20 only useful:) ) from the CPU (mb) and from the PCI BUS (dummy reads,=20 but sometimes useful reads do the needed flushing of posted writes). - I also have checked that memory barriers used by NewBus are enough for=20 the expectations of the driver about IO/MMIO ordering. If I didn't miss something important, and modulo hardware erratas I donnot know about, I donnot expect the driver to cause more failures on Alpha than on IA32. But you must keep in mind that I donnot have Alpha Hardware and am relying on testers for the checking of my statement about SYM reliability on Alpha (compared to IA 32). Regards, G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 14:52:20 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id 1870037C17C for ; Thu, 20 Jul 2000 14:52:17 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id PAA00657; Thu, 20 Jul 2000 15:01:00 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007202201.PAA00657@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE In-reply-to: Your message of "Thu, 20 Jul 2000 20:18:53 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Thu, 20 Jul 2000 15:00:59 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > Can a PCI expert comment on its safety? Mike? > > = > > I think the approach you've taken with using atomic updates is defini= tely = > > the right one. > = > I donnot think so. ;-) I've considered this and, in this instance, I disagree with you. > Here are some of the reasons: > = > 1) Use of Load/Locked Store/Conditional CPU instructions to synchronize= = > with another agent on the system BUS requires the other agent to = > implement some given protocol for the involved access. The other age= nt = > is the host bridge as you know and not another CPU. > What's our knowledge about the behaviour of the bridge? The behaviour of the PCI bridge is defined by the EV6 bus protocol, and = it is required to behave correctly with regards to these instructions. > 2) We also ignore the width of the access performed by the PCI device. > Is it a 16 bit access or a full DWORD access. This is defined by the relevant Intel datasheet; it is a 16-bit access to= = the status word. > And how will the memory controller do the memory access if 16bit: > A) Use 16 bit atomic modify (if supported by the hardware) ? > or > B) Read a full DWORD atomically, clear the bit, Modify the full DWOR= D ? This is irrelevant, since both the CPU and the PCI bridge are talking to = the memory controller, so from either perspective the 16-bit cycle is = atomic. > As a result ( applying to my opinion ;-) ), when a PCI device and its > software driver communicates through the main memory, it is _very_ like= ly > memory barrier to be needed in some places so that program-expected > ordering as seen from the system BUS will happen. I am inclined to agree with you that there are probably cases in the fxp = driver where the author has made assumptions regarding the x86 normal = behaviour of retiring writes in program order, however that's not the = issue that this change is trying to address. -- = =2E.. every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 14:54:49 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id 318B937C185 for ; Thu, 20 Jul 2000 14:54:48 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id PAA00712; Thu, 20 Jul 2000 15:03:36 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007202203.PAA00712@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andrew Gallatin Cc: freebsd-alpha@freebsd.org Subject: Re: fxp0 hangs on a PC164 using STABLE In-reply-to: Your message of "Thu, 20 Jul 2000 15:11:16 EDT." <200007201911.PAA15726@gale.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 Jul 2000 15:03:36 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > WRT memory barriers on i86 -- I though that writes to device memory space > were uncachable & flushed the write buffers unless an mtrr was set > up for the region & it was made cacheable. I defer to the i86 experts.. > As for flushing writes to main memory for better device communication, > I have no clue.. The issue here is that the memory in question isn't in device space, it's in system physical memory. Typically you don't want this sort of stuff uncached, you just want to impose ordering where it actually matters. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 14:56:17 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id 5787837C190 for ; Thu, 20 Jul 2000 14:56:15 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id PAA00739; Thu, 20 Jul 2000 15:04:58 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007202204.PAA00739@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: more on- Re: fxp0 hangs on a PC164 using STABLE In-reply-to: Your message of "Thu, 20 Jul 2000 21:35:38 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Thu, 20 Jul 2000 15:04:58 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > = > > Now, the sparc port will be more interesting because a plain 'memory = barrier' > > is not what's there - instead you have to do explicit address based f= lushing > > and/or invalidation (depending on the platform). > = > Seems Linux does cope of that without too much complexity. Actually, this is pretty easy with bus_space_barrier()... -- = =2E.. every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 15: 0:31 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id E26D337B65D for ; Thu, 20 Jul 2000 15:00:28 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id PAA00823; Thu, 20 Jul 2000 15:09:13 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007202209.PAA00823@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE In-reply-to: Your message of "Thu, 20 Jul 2000 21:54:24 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Thu, 20 Jul 2000 15:09:13 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > It is my opinion. You may disagree but it will hard for anybody to > convince me that I am wrong. ;-) On x86, it's very hard for you to be right; the CPU specification and bus= bridge behaviour both guarantee retirement of writes in order of issuance= =2E This combined with strong cache coherency makes barriers irrelevant on this platform. As far as other platforms are concerned, however, you're quite correct. There does need to be an extension to the busspace API to define a range = of host memory with a tag/handle pair for barrier activity. -- = =2E.. every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 15:18:38 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 772B137C1C6; Thu, 20 Jul 2000 15:18:24 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id PAA07882; Thu, 20 Jul 2000 15:05:27 -0700 (PDT) Message-Id: <200007202205.PAA07882@implode.root.com> To: Mike Smith Cc: =?ISO-8859-1?Q?G=E9rard_Roudier?= , freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE In-reply-to: Your message of "Thu, 20 Jul 2000 15:00:59 PDT." <200007202201.PAA00657@mass.osd.bsdi.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 20 Jul 2000 15:05:27 -0700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> As a result ( applying to my opinion ;-) ), when a PCI device and its >> software driver communicates through the main memory, it is _very_ likely >> memory barrier to be needed in some places so that program-expected >> ordering as seen from the system BUS will happen. > >I am inclined to agree with you that there are probably cases in the fxp >driver where the author has made assumptions regarding the x86 normal >behaviour of retiring writes in program order, however that's not the >issue that this change is trying to address. That is correct. The author assumed that writes would be retired in order and without any special memory barriers or other synchronization. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org Manufacturer of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 18:24:20 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9A61F37C255 for ; Thu, 20 Jul 2000 18:24:18 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id SAA10708; Thu, 20 Jul 2000 18:24:07 -0700 Date: Thu, 20 Jul 2000 18:24:09 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: alpha@freebsd.org Subject: neither 5.0 nor 4.1 RC will install for me on a 4100 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 5.0 panics (as I mentioned) 4.1 floppies hang. I got 4.1 boot.flp (on a disk) to *not* barf on 'going nowhere w/o my init' by having it be the first disk. However, all attempts to install with 'All' failed with the "installation completed with some errors" - which, of course, has debug messages that are not visible for serial install. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 18:39:21 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id C1F1B37B620; Thu, 20 Jul 2000 18:39:18 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA23549; Thu, 20 Jul 2000 21:39:18 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id VAA51152; Thu, 20 Jul 2000 21:39:18 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 20 Jul 2000 21:39:17 -0400 (EDT) To: obrien@FreeBSD.ORG Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: alpha snapshots? (was RE: Alphserver 2100 4/233) In-Reply-To: <20000720132601.C67647@dragon.nuxi.com> References: <20000720130323.B67647@dragon.nuxi.com> <20000720132601.C67647@dragon.nuxi.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14711.43225.700343.909196@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David O'Brien writes: > > Or did you mean the performance issue? Only `xl' and `fxp' can do > zero-copy on coming packets (as wpaul told me yesterday). wpaul seems to > prefer the `xl' cards, and I want to use the NIC he supports the best, so > I prefer to use `xl' when possible. Remember also that the EtherExpress Pro is being OEMed by Compaq as the DE600. As such, newer firmware on newer boxes will netboot from it. On the UP1000: >>> show conf <...> Bus 00 Slot 11: Intel 8255x Ethernet eia0.0.0.11.0 00-A0-C9-8A-AC-AA <...> >>>show dev dka0.0.0.10.0 DKA0 SEAGATE ST39140W 1498 dqa0.0.0.16.0 DQA0 Maxtor 9 0651U2 FA520S60 dqb0.0.1.16.0 DQB0 CD-ROM C DU4011 UY0A dva0.0.0.0.0 DVA0 eia0.0.0.11.0 EIA0 00-A0-C9-8A-AC-AA ewa0.0.0.9.0 EWA0 00-00-F8-07-B6-45 pka0.7.0.10.0 PKA0 SCSI Bus ID 7 If the ability to netboot is important to you & your firmware supports it, then the Intel is probably a better choice than a 3com. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 18:42:46 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id E931E37B620; Thu, 20 Jul 2000 18:42:43 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA23600; Thu, 20 Jul 2000 21:42:43 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id VAA51162; Thu, 20 Jul 2000 21:42:43 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 20 Jul 2000 21:42:43 -0400 (EDT) To: mjacob@feral.com Cc: "David O'Brien" , freebsd-alpha@FreeBSD.ORG Subject: Re: alpha snapshots? (was RE: Alphserver 2100 4/233) In-Reply-To: References: <20000720130323.B67647@dragon.nuxi.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14711.43502.595645.380964@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > On Thu, 20 Jul 2000, David O'Brien wrote: > > > On Wed, Jul 19, 2000 at 11:37:40AM -0400, Andrew Gallatin wrote: > > > Hmm.. I'd suggest axing the ncr driver (why is it still in GENERIC now > > > that SYM supports the older devices??). > > > > I feel groudier would be a better judge of this than I am. > > If he agrees, I'll axe it out. > > Does it support the 810 (not the 810a)? > Yes. At least the Sable at BSDI has one & it works there: FreeBSD 4.0-STABLE #0: Wed Jul 5 09:09:52 EDT 2000 gallatin@chopin.cs.duke.edu:/a/muffin/export/ari_scratch2/gallatin/stable/sys/compile/GENERIC DEC AlphaServer 2100 AlphaServer 2100 4/200, 190MHz 8192 byte page size, 2 processors. CPU: EV4 (21064) major=2 minor=1 OSF PAL rev: 0x4000c0002012d <....> sym0: <810> port 0x10000-0x100ff mem 0x81000000-0x810000ff irq 33 at device 1.0 on pci0 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking sym0: interrupting at T2 irq 33 <...> da0 at sym0 bus 0 target 0 lun 0 <...> Wilko tested it on his AS200 & it reportedly works fine there too. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 18:50:28 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id D643137B636; Thu, 20 Jul 2000 18:50:25 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA23666; Thu, 20 Jul 2000 21:50:25 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id VAA51181; Thu, 20 Jul 2000 21:50:25 -0400 (EDT) (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 Date: Thu, 20 Jul 2000 21:50:25 -0400 (EDT) To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Cc: "David O'Brien" , freebsd-alpha@FreeBSD.ORG Subject: Re: alpha snapshots? (was RE: Alphserver 2100 4/233) In-Reply-To: References: <20000720130323.B67647@dragon.nuxi.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14711.43702.903477.277989@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org G=E9rard Roudier writes: >=20 > If I didn't miss something important, and modulo hardware erratas I = donnot > know about, I donnot expect the driver to cause more failures on Alp= ha > than on IA32. > But you must keep in mind that I donnot have Alpha Hardware and am r= elying > on testers for the checking of my statement about SYM reliability on= Alpha > (compared to IA 32). >=20 > Regards, > G=E9rard. G=E9rard, I've been running an 875 in a UP1000 and I've been running an 810 in an AlphaServer 2100 4/200. Both machines have worked very well with the sym driver. Each machine has done several buildworlds, etc. I'm very happy with the sym driver. I think I speak for nearly everyone when I say that it is wonderful to=20= have a well supported driver for the sym family of adapters!=20 Cheers, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jul 20 20:55:54 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id BCDF337B5CE for ; Thu, 20 Jul 2000 20:55:39 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id UAA70384; Thu, 20 Jul 2000 20:55:02 -0700 (PDT) (envelope-from obrien) Date: Thu, 20 Jul 2000 20:55:02 -0700 From: "David O'Brien" To: Andrew Gallatin Cc: =?iso-8859-1?Q?G=E9rard_Roudier?= , freebsd-alpha@FreeBSD.ORG Subject: Re: alpha snapshots? (was RE: Alphserver 2100 4/233) Message-ID: <20000720205501.A69612@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000720130323.B67647@dragon.nuxi.com> <14711.43702.903477.277989@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2i In-Reply-To: <14711.43702.903477.277989@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Thu, Jul 20, 2000 at 09:50:25PM -0400 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 X-Loop: FreeBSD.org On Thu, Jul 20, 2000 at 09:50:25PM -0400, Andrew Gallatin wrote: Gérard, > I've been running an 875 in a UP1000 and I've been running an 810 in > an AlphaServer 2100 4/200. And my AS 250 4/266 with an 810. > I think I speak for nearly everyone when I say that it is wonderful to > have a well supported driver for the sym family of adapters! YES!! Doubled. I will remove NCR from the BOOTMFS kernel then. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 1:50:33 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 19C2A37BE39; Fri, 21 Jul 2000 01:50:23 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id BAA73096; Fri, 21 Jul 2000 01:50:20 -0700 (PDT) (envelope-from obrien) Date: Fri, 21 Jul 2000 01:50:19 -0700 From: "David O'Brien" To: alpha@freebsd.org Cc: stable@freebsd.org Subject: 4.1-20000719-RC#2 Message-ID: <20000721015019.A73074@dragon.nuxi.com> Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i 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 X-Loop: FreeBSD.org An 4.1-20000719-RC#2 ISO is now available at ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/4.1-20000719-RC It was built using `mkisofs' on the Alpha *AND* /boot/cdboot from 4.0-RELEASE. At this time, I have not tracked down what broke /boot/cdboot. The FTP install will be in place at ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha/4.1-20000719-RC in several hours -- the upload is going now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 6:26:31 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 5813D37B9C5 for ; Fri, 21 Jul 2000 06:26:25 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13Fcop-0003oL-00; Fri, 21 Jul 2000 13:26:23 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id KAA66830; Fri, 21 Jul 2000 10:49:52 +0200 (CEST) (envelope-from wkb) Date: Fri, 21 Jul 2000 10:49:52 +0200 From: Wilko Bulte To: Matthew Jacob Cc: "David O'Brien" , alpha@freebsd.org Subject: Re: neither 5.0 nor 4.1 RC will install for me on a 4100 Message-ID: <20000721104952.A66813@freebie.demon.nl> Reply-To: wilko@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Thu, Jul 20, 2000 at 06:24:09PM -0700 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jul 20, 2000 at 06:24:09PM -0700, Matthew Jacob wrote: > > 5.0 panics (as I mentioned) > > 4.1 floppies hang. I'm (sort of) relieved. At least I'm not alone :-/ > I got 4.1 boot.flp (on a disk) to *not* barf on 'going nowhere w/o my init' by > having it be the first disk. > > However, all attempts to install with 'All' failed with the "installation > completed with some errors" - which, of course, has debug messages that are > not visible for serial install. -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 6:26:31 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 0F5E637B9F4; Fri, 21 Jul 2000 06:26:26 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13Fcop-0003oL-01; Fri, 21 Jul 2000 13:26:23 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id LAA66990; Fri, 21 Jul 2000 11:13:41 +0200 (CEST) (envelope-from wkb) Date: Fri, 21 Jul 2000 11:13:41 +0200 From: Wilko Bulte To: Andrew Gallatin Cc: mjacob@feral.com, "David O'Brien" , freebsd-alpha@freebsd.org Subject: Re: alpha snapshots? (was RE: Alphserver 2100 4/233) Message-ID: <20000721111340.F66813@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <20000720130323.B67647@dragon.nuxi.com> <14711.43502.595645.380964@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <14711.43502.595645.380964@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Thu, Jul 20, 2000 at 09:42:43PM -0400 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jul 20, 2000 at 09:42:43PM -0400, Andrew Gallatin wrote: > > Matthew Jacob writes: > > On Thu, 20 Jul 2000, David O'Brien wrote: > > > > > On Wed, Jul 19, 2000 at 11:37:40AM -0400, Andrew Gallatin wrote: > > > > Hmm.. I'd suggest axing the ncr driver (why is it still in GENERIC now > > > > that SYM supports the older devices??). > > > > > > I feel groudier would be a better judge of this than I am. > > > If he agrees, I'll axe it out. > > > > Does it support the 810 (not the 810a)? > > > > Yes. At least the Sable at BSDI has one & it works there: > > FreeBSD 4.0-STABLE #0: Wed Jul 5 09:09:52 EDT 2000 > gallatin@chopin.cs.duke.edu:/a/muffin/export/ari_scratch2/gallatin/stable/sys/compile/GENERIC > DEC AlphaServer 2100 > AlphaServer 2100 4/200, 190MHz > 8192 byte page size, 2 processors. > CPU: EV4 (21064) major=2 minor=1 > OSF PAL rev: 0x4000c0002012d > <....> > sym0: <810> port 0x10000-0x100ff mem 0x81000000-0x810000ff irq 33 at device 1.0 on pci0 > sym0: No NVRAM, ID 7, Fast-10, SE, parity checking > sym0: interrupting at T2 irq 33 > <...> > da0 at sym0 bus 0 target 0 lun 0 > <...> > > Wilko tested it on his AS200 & it reportedly works fine there too. AS2100 And indeed it worked just fine, at least the install. It used the internal disk shelf, so the builtin 810 -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 6:39:51 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from cgi.sstar.com (cgi.sstar.com [209.205.176.12]) by hub.freebsd.org (Postfix) with ESMTP id 3DD1937BA85; Fri, 21 Jul 2000 06:39:41 -0700 (PDT) (envelope-from jim@jimking.net) Received: from bluto.jimking.net (bluto.jimking.net [216.54.255.8]) by cgi.sstar.com (8.9.3/8.9.3) with ESMTP id IAA66514; Fri, 21 Jul 2000 08:39:34 -0500 (CDT) (envelope-from jim@jimking.net) Received: from marble (marble.lgc.com [134.132.228.8]) by bluto.jimking.net (8.9.3/8.9.3) with SMTP id IAA00477; Fri, 21 Jul 2000 08:39:31 -0500 (CDT) (envelope-from jim@jimking.net) Message-ID: <001101bff319$1ac14930$08e48486@marble> From: "Jim King" To: Cc: References: <20000720130323.B67647@dragon.nuxi.com> <14711.43502.595645.380964@grasshopper.cs.duke.edu> <20000721111340.F66813@freebie.demon.nl> Subject: Re: alpha snapshots? (was RE: Alphserver 2100 4/233) Date: Fri, 21 Jul 2000 08:39:31 -0500 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 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte wrote: > On Thu, Jul 20, 2000 at 09:42:43PM -0400, Andrew Gallatin wrote: > > > > Matthew Jacob writes: > > > On Thu, 20 Jul 2000, David O'Brien wrote: > > > > > > > On Wed, Jul 19, 2000 at 11:37:40AM -0400, Andrew Gallatin wrote: > > > > > Hmm.. I'd suggest axing the ncr driver (why is it still in GENERIC now > > > > > that SYM supports the older devices??). > > > > > > > > I feel groudier would be a better judge of this than I am. > > > > If he agrees, I'll axe it out. > > > > > > Does it support the 810 (not the 810a)? > > > > > > > Yes. At least the Sable at BSDI has one & it works there: > > > > FreeBSD 4.0-STABLE #0: Wed Jul 5 09:09:52 EDT 2000 > > gallatin@chopin.cs.duke.edu:/a/muffin/export/ari_scratch2/gallatin/stable/sy s/compile/GENERIC > > DEC AlphaServer 2100 > > AlphaServer 2100 4/200, 190MHz > > 8192 byte page size, 2 processors. > > CPU: EV4 (21064) major=2 minor=1 > > OSF PAL rev: 0x4000c0002012d > > <....> > > sym0: <810> port 0x10000-0x100ff mem 0x81000000-0x810000ff irq 33 at device 1.0 on pci0 > > sym0: No NVRAM, ID 7, Fast-10, SE, parity checking > > sym0: interrupting at T2 irq 33 > > <...> > > da0 at sym0 bus 0 target 0 lun 0 > > <...> > > > > Wilko tested it on his AS200 & it reportedly works fine there too. > > AS2100 > > And indeed it worked just fine, at least the install. It used the > internal disk shelf, so the builtin 810 fwiw, on my AS200 I just switched from ncr to sym and enabled PPS_SYNC, and got two solid lockups in 12 hours. The source on this box is 4-stable from about a month ago, so this weekend I'll try again with an up-to-date -stable and see if the problem still exists, and whether it's sym or PPS_SYNC that's causing the problem. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 6:56:42 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from off.to (off.to [63.77.233.98]) by hub.freebsd.org (Postfix) with ESMTP id 971BF37B937 for ; Fri, 21 Jul 2000 06:56:37 -0700 (PDT) (envelope-from mts@off.to) Received: from off.to (localhost [127.0.0.1]) by off.to (8.9.1/8.9.1) with ESMTP id JAA09501; Fri, 21 Jul 2000 09:56:31 -0400 (EDT) Message-Id: <200007211356.JAA09501@off.to> To: freebsd-alpha@freebsd.org Cc: mts@off.to Subject: kernel build problem. Reply-To: mts@off.to Date: Fri, 21 Jul 2000 09:56:31 -0400 From: "Michael T. Stolarchuk" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 4.0-RELEASE #0: Mon Mar 20 21:55:10 GMT 2000 i'm having some trouble building kernels... it seems like i've left some step out. a newly installed system can't do a `make depend' after a config. The config succeeds, but when i try the made depend in the target directory, i get a boatload of errors. Its as if /usr/include/machine isn't correct. i've tried some simple fixes, but it still seems wrong. this must be a known problem, but i haven't been able to locate any details about it... and don't see a straightforward fix to deal with it... What's the right thing to do? Get current? or is there some configuration step i've missed? mts. alpha3# make depend cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 ../../alpha/alpha/genassym.c In file included from ../../sys/systm.h:46, from ../../alpha/alpha/genassym.c:43: machine/cpufunc.h: In function `invlpg': machine/cpufunc.h:270: warning: cast to pointer from integer of different size machine/cpufunc.h: In function `outsb': machine/cpufunc.h:339: warning: asm operand 0 probably doesn't match constraints machine/cpufunc.h: In function `outsw': machine/cpufunc.h:347: warning: asm operand 0 probably doesn't match constraints machine/cpufunc.h: In function `outsl': machine/cpufunc.h:355: warning: asm operand 0 probably doesn't match constraints In file included from ../../alpha/alpha/genassym.c:43: ../../sys/systm.h: At top level: ../../sys/systm.h:136: warning: conflicting types for built-in function `memcpy' In file included from ../../sys/systm.h:172, from ../../alpha/alpha/genassym.c:43: ../../sys/libkern.h:84: warning: conflicting types for built-in function `strlen' In file included from ../../alpha/alpha/genassym.c:46: ../../sys/buf.h: In function `BUF_LOCK': ../../sys/buf.h:269: warning: implicit declaration of function `splbio' ../../sys/buf.h:276: warning: implicit declaration of function `splx' In file included from ../../vm/pmap.h:87, from ../../alpha/alpha/genassym.c:58: machine/pmap.h: In function `pmap_kextract': machine/pmap.h:168: warning: cast from pointer to integer of different size ../../alpha/alpha/genassym.c: At top level: ../../alpha/alpha/genassym.c:69: structure has no member named `md_flags' ../../alpha/alpha/genassym.c:70: structure has no member named `md_pcbpaddr' ../../alpha/alpha/genassym.c:71: structure has no member named `md_hae' ../../alpha/alpha/genassym.c:72: `MDP_HAEUSED' undeclared here (not in a function) ../../alpha/alpha/genassym.c:77: `PTLEV1I' undeclared here (not in a function) ../../alpha/alpha/genassym.c:81: structure has no member named `pcb_hw' ../../alpha/alpha/genassym.c:82: structure has no member named `pcb_context' ../../alpha/alpha/genassym.c:84: structure has no member named `pcb_hw' ../../alpha/alpha/genassym.c:86: dereferencing pointer to incomplete type ../../alpha/alpha/genassym.c:87: dereferencing pointer to incomplete type ../../alpha/alpha/genassym.c:93: `FRAME_V0' undeclared here (not in a function) ../../alpha/alpha/genassym.c:94: `FRAME_T0' undeclared here (not in a function) ../../alpha/alpha/genassym.c:95: `FRAME_T1' undeclared here (not in a function) ../../alpha/alpha/genassym.c:96: `FRAME_T2' undeclared here (not in a function) ../../alpha/alpha/genassym.c:97: `FRAME_T3' undeclared here (not in a function) ../../alpha/alpha/genassym.c:98: `FRAME_T4' undeclared here (not in a function) ../../alpha/alpha/genassym.c:99: `FRAME_T5' undeclared here (not in a function) ../../alpha/alpha/genassym.c:100: `FRAME_T6' undeclared here (not in a function) ../../alpha/alpha/genassym.c:101: `FRAME_T7' undeclared here (not in a function) ../../alpha/alpha/genassym.c:102: `FRAME_S0' undeclared here (not in a function) ../../alpha/alpha/genassym.c:103: `FRAME_S1' undeclared here (not in a function) ../../alpha/alpha/genassym.c:104: `FRAME_S2' undeclared here (not in a function) ../../alpha/alpha/genassym.c:105: `FRAME_S3' undeclared here (not in a function) ../../alpha/alpha/genassym.c:106: `FRAME_S4' undeclared here (not in a function) ../../alpha/alpha/genassym.c:107: `FRAME_S5' undeclared here (not in a function) ../../alpha/alpha/genassym.c:108: `FRAME_S6' undeclared here (not in a function) ../../alpha/alpha/genassym.c:109: `FRAME_A3' undeclared here (not in a function) ../../alpha/alpha/genassym.c:110: `FRAME_A4' undeclared here (not in a function) ../../alpha/alpha/genassym.c:111: `FRAME_A5' undeclared here (not in a function) ../../alpha/alpha/genassym.c:112: `FRAME_T8' undeclared here (not in a function) ../../alpha/alpha/genassym.c:113: `FRAME_T9' undeclared here (not in a function) ../../alpha/alpha/genassym.c:114: `FRAME_T10' undeclared here (not in a function) ../../alpha/alpha/genassym.c:115: `FRAME_T11' undeclared here (not in a function) ../../alpha/alpha/genassym.c:116: `FRAME_RA' undeclared here (not in a function) ../../alpha/alpha/genassym.c:117: `FRAME_T12' undeclared here (not in a function) ../../alpha/alpha/genassym.c:118: `FRAME_AT' undeclared here (not in a function) ../../alpha/alpha/genassym.c:119: `FRAME_SP' undeclared here (not in a function) ../../alpha/alpha/genassym.c:121: `FRAME_SW_SIZE' undeclared here (not in a function) ../../alpha/alpha/genassym.c:123: `FRAME_PS' undeclared here (not in a function) ../../alpha/alpha/genassym.c:124: `FRAME_PC' undeclared here (not in a function) ../../alpha/alpha/genassym.c:125: `FRAME_GP' undeclared here (not in a function) ../../alpha/alpha/genassym.c:126: `FRAME_A0' undeclared here (not in a function) ../../alpha/alpha/genassym.c:127: `FRAME_A1' undeclared here (not in a function) ../../alpha/alpha/genassym.c:128: `FRAME_A2' undeclared here (not in a function) ../../alpha/alpha/genassym.c:130: `FRAME_SIZE' undeclared here (not in a function) ../../alpha/alpha/genassym.c:133: `ALPHA_PSL_USERMODE' undeclared here (not in a function) ../../alpha/alpha/genassym.c:134: `ALPHA_PSL_IPL_MASK' undeclared here (not in a function) ../../alpha/alpha/genassym.c:135: `ALPHA_PSL_IPL_0' undeclared here (not in a function) ../../alpha/alpha/genassym.c:136: `ALPHA_PSL_IPL_SOFT' undeclared here (not in a function) ../../alpha/alpha/genassym.c:137: `ALPHA_PSL_IPL_HIGH' undeclared here (not in a function) ../../alpha/alpha/genassym.c:140: `ALPHA_L1SHIFT' undeclared here (not in a function) ../../alpha/alpha/genassym.c:141: `ALPHA_L2SHIFT' undeclared here (not in a function) ../../alpha/alpha/genassym.c:142: `ALPHA_L3SHIFT' undeclared here (not in a function) ../../alpha/alpha/genassym.c:143: `ALPHA_K1SEG_BASE' undeclared here (not in a function) ../../alpha/alpha/genassym.c:144: `ALPHA_PTE_VALID' undeclared here (not in a function) ../../alpha/alpha/genassym.c:145: `ALPHA_PTE_ASM' undeclared here (not in a function) ../../alpha/alpha/genassym.c:146: `ALPHA_PTE_KR' undeclared here (not in a function) ../../alpha/alpha/genassym.c:147: `ALPHA_PTE_KW' undeclared here (not in a function) ../../alpha/alpha/genassym.c:150: `ALPHA_KENTRY_ARITH' undeclared here (not in a function) ../../alpha/alpha/genassym.c:151: `ALPHA_KENTRY_MM' undeclared here (not in a function) ../../alpha/alpha/genassym.c:153: `ALPHA_KENTRY_IF' undeclared here (not in a function) ../../alpha/alpha/genassym.c:154: `ALPHA_KENTRY_UNA' undeclared here (not in a function) ../../alpha/alpha/genassym.c:156: `VPTBASE' undeclared here (not in a function) *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 7:46:21 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 8147537BCAC for ; Fri, 21 Jul 2000 07:46:16 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA02951; Fri, 21 Jul 2000 10:46:15 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id KAA52393; Fri, 21 Jul 2000 10:46:15 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 21 Jul 2000 10:46:15 -0400 (EDT) To: mts@off.to Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: kernel build problem. In-Reply-To: <200007211356.JAA09501@off.to> References: <200007211356.JAA09501@off.to> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14712.24926.268089.962068@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Michael T. Stolarchuk writes: > > 4.0-RELEASE #0: Mon Mar 20 21:55:10 GMT 2000 > > i'm having some trouble building kernels... it seems like i've left > some step out. a newly installed system can't do a `make depend' after > a config. The config succeeds, but when i try the made depend in the > target directory, i get a boatload of errors. > > Its as if /usr/include/machine isn't correct. i've tried some simple > fixes, but it still seems wrong. this must be a known problem, but > i haven't been able to locate any details about it... and don't > see a straightforward fix to deal with it... > > What's the right thing to do? Get current? or is there some > configuration step i've missed? From the symptoms, I'd guess you've configured an i386 kernel & tried to build it on an alpha. Eg, make sure you run config in sys/alpha/conf, _NOT_ sys/i386/conf. You may want to take a fresh source tree, as your above mentioned attempts at fixes may have broken something else. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 7:51:37 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from cgi.sstar.com (cgi.sstar.com [209.205.176.12]) by hub.freebsd.org (Postfix) with ESMTP id 9072737BBAE for ; Fri, 21 Jul 2000 07:51:33 -0700 (PDT) (envelope-from jim@jimking.net) Received: from jking (jking.lgc.com [134.132.75.164]) by cgi.sstar.com (8.9.3/8.9.3) with SMTP id JAA69033 for ; Fri, 21 Jul 2000 09:51:32 -0500 (CDT) (envelope-from jim@jimking.net) Message-ID: <001f01bff323$28996650$a44b8486@jking> From: "Jim King" To: References: <20000720130323.B67647@dragon.nuxi.com> <14711.43502.595645.380964@grasshopper.cs.duke.edu> <20000721111340.F66813@freebie.demon.nl> <001101bff319$1ac14930$08e48486@marble> Subject: Re: alpha snapshots? (was RE: Alphserver 2100 4/233) Date: Fri, 21 Jul 2000 09:51:01 -0500 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 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jim King wrote: > Wilko Bulte wrote: > > > On Thu, Jul 20, 2000 at 09:42:43PM -0400, Andrew Gallatin wrote: > > > > > > Matthew Jacob writes: > > > > On Thu, 20 Jul 2000, David O'Brien wrote: > > > > > > > > > On Wed, Jul 19, 2000 at 11:37:40AM -0400, Andrew Gallatin wrote: > > > > > > Hmm.. I'd suggest axing the ncr driver (why is it still in > GENERIC now > > > > > > that SYM supports the older devices??). > > > > > > > > > > I feel groudier would be a better judge of this than I am. > > > > > If he agrees, I'll axe it out. > > > > > > > > Does it support the 810 (not the 810a)? > > > > > > > > > > Yes. At least the Sable at BSDI has one & it works there: > > > > > > FreeBSD 4.0-STABLE #0: Wed Jul 5 09:09:52 EDT 2000 > > > > gallatin@chopin.cs.duke.edu:/a/muffin/export/ari_scratch2/gallatin/stable/sy > s/compile/GENERIC > > > DEC AlphaServer 2100 > > > AlphaServer 2100 4/200, 190MHz > > > 8192 byte page size, 2 processors. > > > CPU: EV4 (21064) major=2 minor=1 > > > OSF PAL rev: 0x4000c0002012d > > > <....> > > > sym0: <810> port 0x10000-0x100ff mem 0x81000000-0x810000ff irq 33 at > device 1.0 on pci0 > > > sym0: No NVRAM, ID 7, Fast-10, SE, parity checking > > > sym0: interrupting at T2 irq 33 > > > <...> > > > da0 at sym0 bus 0 target 0 lun 0 > > > <...> > > > > > > Wilko tested it on his AS200 & it reportedly works fine there too. > > > > AS2100 > > > > And indeed it worked just fine, at least the install. It used the > > internal disk shelf, so the builtin 810 > > fwiw, on my AS200 I just switched from ncr to sym and enabled PPS_SYNC, and > got two solid lockups in 12 hours. The source on this box is 4-stable from > about a month ago, so this weekend I'll try again with an up-to-date -stable > and see if the problem still exists, and whether it's sym or PPS_SYNC that's > causing the problem. Hmm, it crashed again with the old kernel (which ran fine for a month prior to yesterday). This is starting to look like a hardware problem - ugh! Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 11:52:42 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from front2m.grolier.fr (front2m.grolier.fr [195.36.216.52]) by hub.freebsd.org (Postfix) with ESMTP id AB1A437C151; Fri, 21 Jul 2000 11:52:24 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from nas1-71.cgy.club-internet.fr (nas1-71.cgy.club-internet.fr [195.36.197.71]) by front2m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id UAA05444; Fri, 21 Jul 2000 20:52:19 +0200 (MET DST) Date: Fri, 21 Jul 2000 20:32:00 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Mike Smith Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE In-Reply-To: <200007202209.PAA00823@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 20 Jul 2000, Mike Smith wrote: > > It is my opinion. You may disagree but it will hard for anybody to > > convince me that I am wrong. ;-) >=20 > On x86, it's very hard for you to be right; the CPU specification and bus > bridge behaviour both guarantee retirement of writes in order of issuance= =2E > This combined with strong cache coherency makes barriers irrelevant on > this platform. Let a PCI device perform: =09STORE A =09STORE B Let the CPU perform and expect: LOAD B LOAD A Let some CPU speculative execution carry out to the system BUS: =09LOAD A =09LOAD B My reading of the the Intel docs didn't convince me that such reordering is not possible. =20 Typically A is some indicator of an IO completion pushed to a completion=20 queue and B is the associated status data. =09 > As far as other platforms are concerned, however, you're quite correct. Are you still so sure. ;-) > There does need to be an extension to the busspace API to define a range= =20 > of host memory with a tag/handle pair for barrier activity. Hmmm... Barrier semantics vary so much between architectures that an unified semantic that also address device driver's concerns (not only CPU<->CPU) is either close to impossible or will just be extremally poor, in my opinion. I will give a single exemple for Alpha: the wmb instruction on Alpha orders memory-like stores and non-memory-like stores _independantly_. That means that the mb instruction must be used as a store barrier when both kinds of stores are addressed at the same time. We can, as a second example, consider: 1) Situations when a real barrier (called serialisation) is needed for IA32 and a mb is needed for Alpha. 2) Situations where only a mb is needed for Alpha but the IA32 does=20 not require serialisation. People who are happy with nightmares can also compare all kind of barriers and implicit ordering rules that are in existence and try to elaborate an unified semantic that is both simple and rich. ;-) And People who are happy with nighmares at the power of two can also read documentations of various existing host-bridges. ;-) Most existing software BUS abstractions mostly address consistency given no concurrency. A common problem with PCI device / software driver pairs is consistency given concurrency, that not only requires CPU barriers to be used but also to be careful about posted write flushing. Basically, also the PCI device and the software driver may have to use some different kind of barriers for consistency given concurrency to happen as expected, by flushing when needed posted write transactions. (using read transactions as we know). The drivers I maintain will always contain any stuff needed for them to be as correct as I want them to be, modulo my knowledge and competence on addressed platforms obviously. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 11:57: 8 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 02B9A37B7E5 for ; Fri, 21 Jul 2000 11:57:05 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA07749; Fri, 21 Jul 2000 14:57:04 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id OAA52850; Fri, 21 Jul 2000 14:57:04 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 21 Jul 2000 14:57:03 -0400 (EDT) To: obrien@NUXI.com Cc: alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-Reply-To: <20000721015019.A73074@dragon.nuxi.com> References: <20000721015019.A73074@dragon.nuxi.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14712.39534.122473.899129@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David O'Brien writes: > An 4.1-20000719-RC#2 ISO is now available at > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/4.1-20000719-RC > > It was built using `mkisofs' on the Alpha *AND* /boot/cdboot from > 4.0-RELEASE. At this time, I have not tracked down what broke > /boot/cdboot. > > The FTP install will be in place at > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha/4.1-20000719-RC in > several hours -- the upload is going now. The ISO appears to boot, at least on an AS500 5/266. Cool! One install nit. This box has a TGA card in it. When I use a graphics console, it says: "/stand/sysinstall running as init on serial console" However, its not running on the serial console. In fact, I/O to sysinstall seems to be going into the bitbucket. All is fine if I set the console to serial prior to the install. Is this behaviour documented? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 12:14:57 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from front5.grolier.fr (front5.grolier.fr [194.158.96.55]) by hub.freebsd.org (Postfix) with ESMTP id 21B4137BE0D; Fri, 21 Jul 2000 12:14:49 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from nas1-142.cgy.club-internet.fr (nas1-142.cgy.club-internet.fr [195.36.197.142]) by front5.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id VAA18431; Fri, 21 Jul 2000 21:14:32 +0200 (MET DST) Date: Fri, 21 Jul 2000 20:54:13 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: David Greenman Cc: Mike Smith , freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE In-Reply-To: <200007202205.PAA07882@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 20 Jul 2000, David Greenman wrote: > >> As a result ( applying to my opinion ;-) ), when a PCI device and its > >> software driver communicates through the main memory, it is _very_ lik= ely > >> memory barrier to be needed in some places so that program-expected > >> ordering as seen from the system BUS will happen. > > > >I am inclined to agree with you that there are probably cases in the fxp= =20 > >driver where the author has made assumptions regarding the x86 normal=20 > >behaviour of retiring writes in program order, however that's not the=20 > >issue that this change is trying to address. >=20 > That is correct. The author assumed that writes would be retired in > order and without any special memory barriers or other synchronization. The memory barrier we must use after having READ the FLAG and prior to=20 READ the associated STATUS DATA is _also_ intended to avoid reodering by=20 the CPU of these 2 kinds of READs. If they are reodered the software=20 driver may read stale STATUS DATA. For software drivers that execute concurrently with the PCI device, the FLAG may be the item that tells about the IO that completed and retired from some completion queue in main memory prior to examining the associated STATUS DATA. By the way, software drivers that behave as the above model may also have to insert a serialisation instruction on PII/PII between the READ of the FLAG and the READ of the STATUS DATA (If PII/PPIII can reorder LOADs). G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 12:17:56 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 3401337BE0A for ; Fri, 21 Jul 2000 12:17:50 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13FiIu-0002FJ-00; Fri, 21 Jul 2000 19:17:49 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id VAA21012; Fri, 21 Jul 2000 21:17:31 +0200 (CEST) (envelope-from wkb) Date: Fri, 21 Jul 2000 21:17:31 +0200 From: Wilko Bulte To: Andrew Gallatin Cc: obrien@NUXI.com, alpha@freebsd.org Subject: Re: 4.1-20000719-RC#2 Message-ID: <20000721211731.A20967@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <20000721015019.A73074@dragon.nuxi.com> <14712.39534.122473.899129@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <14712.39534.122473.899129@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Fri, Jul 21, 2000 at 02:57:03PM -0400 X-OS: FreeBSD 4.1-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jul 21, 2000 at 02:57:03PM -0400, Andrew Gallatin wrote: > David O'Brien writes: > > An 4.1-20000719-RC#2 ISO is now available at > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/4.1-20000719-RC > > > > It was built using `mkisofs' on the Alpha *AND* /boot/cdboot from > > 4.0-RELEASE. At this time, I have not tracked down what broke > > /boot/cdboot. > > > > The FTP install will be in place at > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha/4.1-20000719-RC in > > several hours -- the upload is going now. > > The ISO appears to boot, at least on an AS500 5/266. Cool! Yes it does. It uses the 4.0R cdboot ;-) Tested it here on a MiataGL with success. > One install nit. This box has a TGA card in it. When I use a > graphics console, it says: "/stand/sysinstall running as init on > serial console" However, its not running on the serial console. > In fact, I/O to sysinstall seems to be going into the bitbucket. > > All is fine if I set the console to serial prior to the install. > Is this behaviour documented? TGA cards/consoles are flagged as unsupported, but that is it. Anything specific you want me to put in RELNOTES and/or HW.TXT ? -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 12:24:28 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id E199A37BF1A; Fri, 21 Jul 2000 12:24:25 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id PAA08245; Fri, 21 Jul 2000 15:24:24 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id PAA52905; Fri, 21 Jul 2000 15:24:24 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 21 Jul 2000 15:24:23 -0400 (EDT) To: wilko@FreeBSD.ORG Cc: alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-Reply-To: <20000721211731.A20967@freebie.demon.nl> References: <20000721015019.A73074@dragon.nuxi.com> <14712.39534.122473.899129@grasshopper.cs.duke.edu> <20000721211731.A20967@freebie.demon.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14712.41758.459790.390526@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte writes: > > TGA cards/consoles are flagged as unsupported, but that is it. > > Anything specific you want me to put in RELNOTES and/or HW.TXT ? Something along the lines of "TGA cards will not work for installation; you MUST use a VGA card or a serial line for installation." might save somebody some time.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 12:30:33 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8363437BE2E; Fri, 21 Jul 2000 12:30:24 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA13841; Fri, 21 Jul 2000 12:30:22 -0700 Date: Fri, 21 Jul 2000 12:30:00 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: wilko@FreeBSD.ORG Cc: alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-Reply-To: <14712.41758.459790.390526@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I think you need to put into RELNOTES that Alpha 4100 isn't supported. I've tried to install from the RC (even from boot.flp), and it doesn't work, and I've had no response from David about it, Jordan didn't add the xterm entry to the installer (as he said he would), and Mike hasn't looked at the 'going nowhere without my init', so despite the effort I put in I don't believe we can say it's supported. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 12:55:22 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id DE76237BEA3; Fri, 21 Jul 2000 12:55:05 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13Fisx-0002X6-00; Fri, 21 Jul 2000 19:55:03 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id VAA21259; Fri, 21 Jul 2000 21:52:20 +0200 (CEST) (envelope-from wkb) Date: Fri, 21 Jul 2000 21:52:20 +0200 From: Wilko Bulte To: Matthew Jacob Cc: wilko@freebsd.org, alpha@freebsd.org Subject: Re: 4.1-20000719-RC#2 Message-ID: <20000721215220.A21196@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <14712.41758.459790.390526@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Fri, Jul 21, 2000 at 12:30:00PM -0700 X-OS: FreeBSD 4.1-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jul 21, 2000 at 12:30:00PM -0700, Matthew Jacob wrote: > I think you need to put into RELNOTES that Alpha 4100 isn't supported. I've > tried to install from the RC (even from boot.flp), and it doesn't work, and > I've had no response from David about it, Jordan didn't add the xterm entry to > the installer (as he said he would), and Mike hasn't looked at the 'going > nowhere without my init', so despite the effort I put in I don't believe we > can say it's supported. 4100 works fine once installed. That would need another machine to install on a disk subsequently moved to the Rawhide. RELNOTES today has: "AlphaServer 4100 (Rawhide) does not want to allow installation using floppies. Workaround is to install using another Alpha machine and move the disk to the AS4100. Once installed FreeBSD runs fine." I'd say this should be sufficient? I'll also add a note on the 'init' thing if jkh OKs me touching the *.TXT files. W/ -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 12:58:46 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D12D437BDEE; Fri, 21 Jul 2000 12:58:42 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA13960; Fri, 21 Jul 2000 12:58:42 -0700 Date: Fri, 21 Jul 2000 12:58:20 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: wilko@freebsd.org Cc: alpha@freebsd.org Subject: Re: 4.1-20000719-RC#2 In-Reply-To: <20000721215220.A21196@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 21 Jul 2000, Wilko Bulte wrote: > On Fri, Jul 21, 2000 at 12:30:00PM -0700, Matthew Jacob wrote: > > > I think you need to put into RELNOTES that Alpha 4100 isn't supported. I've > > tried to install from the RC (even from boot.flp), and it doesn't work, and > > I've had no response from David about it, Jordan didn't add the xterm entry to > > the installer (as he said he would), and Mike hasn't looked at the 'going > > nowhere without my init', so despite the effort I put in I don't believe we > > can say it's supported. > > 4100 works fine once installed. That would need another machine to install > on a disk subsequently moved to the Rawhide. > > RELNOTES today has: > > "AlphaServer 4100 (Rawhide) does not want to allow installation using > floppies. Workaround is to install using another Alpha machine and > move the disk to the AS4100. Once installed FreeBSD runs fine." > > I'd say this should be sufficient? > > I'll also add a note on the 'init' thing if jkh OKs me touching the *.TXT files. > The install tools *should* install from boot.flp if you dd it onto a disk and boot in on a AS4100- but that does not work. However, your comment is sufficient for now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 13: 6:52 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from front6.grolier.fr (front6.grolier.fr [194.158.96.56]) by hub.freebsd.org (Postfix) with ESMTP id 4604E37BE38; Fri, 21 Jul 2000 13:06:42 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from nas1-11.cgy.club-internet.fr (nas1-11.cgy.club-internet.fr [195.36.197.11]) by front6.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id WAA27582; Fri, 21 Jul 2000 22:06:33 +0200 (MET DST) Date: Fri, 21 Jul 2000 21:46:13 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Andrew Gallatin Cc: "David O'Brien" , freebsd-alpha@FreeBSD.ORG Subject: Re: alpha snapshots? (was RE: Alphserver 2100 4/233) In-Reply-To: <14711.43702.903477.277989@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 20 Jul 2000, Andrew Gallatin wrote: >=20 > G=E9rard Roudier writes: > >=20 > > If I didn't miss something important, and modulo hardware erratas I do= nnot > > know about, I donnot expect the driver to cause more failures on Alpha > > than on IA32. > > But you must keep in mind that I donnot have Alpha Hardware and am rel= ying > > on testers for the checking of my statement about SYM reliability on A= lpha > > (compared to IA 32). > >=20 > > Regards, > > G=E9rard. >=20 > G=E9rard, >=20 > I've been running an 875 in a UP1000 and I've been running an 810 in > an AlphaServer 2100 4/200. Both machines have worked very well with > the sym driver. Each machine has done several buildworlds, etc. I'm > very happy with the sym driver. >=20 > I think I speak for nearly everyone when I say that it is wonderful to=20 > have a well supported driver for the sym family of adapters!=20 Thanks! G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 13:20:44 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from charon.npc.net (charon.finall.com [199.15.61.3]) by hub.freebsd.org (Postfix) with ESMTP id 336F337B614 for ; Fri, 21 Jul 2000 13:20:37 -0700 (PDT) (envelope-from mjung@npc.net) Received: from exchange1.npc.net ([10.0.157.36]) by charon.npc.net (8.10.2/8.10.2) with ESMTP id e6LKKVe56046 for ; Fri, 21 Jul 2000 16:20:31 -0400 (EDT) Received: by EXCHANGE1 with Internet Mail Service (5.5.2650.21) id ; Fri, 21 Jul 2000 16:20:32 -0400 Message-ID: <921763828F4BD4118D7D00805FEDF35810C5B1@EXCHANGE1> From: "Jung, Michael" To: "'alpha@freebsd.org'" Subject: RC2 on 2100 4/233 Date: Fri, 21 Jul 2000 16:20:32 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org For what its worth the iso-image of rc2 boots and loads on a 2100 4/233 Copyright (c) 1992-2000 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.1-20000718-RC #0: Tue Jul 18 17:15:16 GMT 2000 rootk@a41.nuxi.com:/usr/src/sys/compile/BOOTMFS DEC AlphaServer 2100 AlphaServer 2100 4/233, 233MHz 8192 byte page size, 1 processor. CPU: EV45 (21064A) major=6 minor=2 OSF PAL rev: 0x4000c0002012d real memory = 266264576 (260024K bytes) avail memory = 251060224 (245176K bytes) However if you tell the installer to install - everything - it bombs and doesn't update /etc - It complains that INDEX isn't available To thoses who posted the ISO's thanks - we are removing redhat :) --mikej To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 13:28:22 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from zippy.osd.bsdi.com (zippy.osd.bsdi.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id A4C3637B5ED; Fri, 21 Jul 2000 13:28:20 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id NAA04403; Fri, 21 Jul 2000 13:29:26 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: mjacob@feral.com Cc: wilko@FreeBSD.ORG, alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-reply-to: Your message of "Fri, 21 Jul 2000 12:30:00 PDT." Date: Fri, 21 Jul 2000 13:29:25 -0700 Message-ID: <4400.964211365@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I've had no response from David about it, Jordan didn't add the xterm entry t o > the installer (as he said he would), and Mike hasn't looked at the 'going Well, the omission of an xterm entry was simply an oversight on my part and hardly a major show-stopper for the alpha, so I fail to see why you'd include this with the above list. As to the "going nowhere without my init" problem, it's my understanding that nobody else can even *reproduce* it with the equipment available here or I'm sure you'd see a lot more furor over it. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 13:32:10 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id C3B2A37BE79; Fri, 21 Jul 2000 13:32:06 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA14162; Fri, 21 Jul 2000 13:32:00 -0700 Date: Fri, 21 Jul 2000 13:31:39 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Jordan K. Hubbard" Cc: wilko@FreeBSD.ORG, alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-Reply-To: <4400.964211365@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 21 Jul 2000, Jordan K. Hubbard wrote: > > I've had no response from David about it, Jordan didn't add the xterm entry t > o > > the installer (as he said he would), and Mike hasn't looked at the 'going > > Well, the omission of an xterm entry was simply an oversight on my > part and hardly a major show-stopper for the alpha, so I fail to see > why you'd include this with the above list. Sorry- with vt100 or 'ansi' entries it's damned near impossible to be sure whether or not you're actually seeing an artifact of wierd curses on serial installs or not. I probably shouldn't have included it. > As to the "going nowhere > without my init" problem, it's my understanding that nobody else can > even *reproduce* it with the equipment available here or I'm sure > you'd see a lot more furor over it. Nobody *tried* to reproduce it-that's what occurred. I offered to make equipment available to make this process easier, but nobody got back to me on this. It's happened several places, so I'm assuming that it isn't just a oneshot problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 13:39: 7 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from phy.ucsf.edu (phy.ucsf.edu [128.218.64.200]) by hub.freebsd.org (Postfix) with ESMTP id 2F82737C2BA for ; Fri, 21 Jul 2000 13:39:02 -0700 (PDT) (envelope-from dkleinh@phy.ucsf.edu) Received: from amadeus.ucsf.edu (dkleinh@amadeus.ucsf.edu [128.218.65.107]) by phy.ucsf.edu (8.10.1/8.10.1) with ESMTP id e6LKd1k13224 for ; Fri, 21 Jul 2000 13:39:01 -0700 (PDT) Received: from localhost by amadeus.ucsf.edu (8.8.6) id NAA22336; Fri, 21 Jul 2000 13:39:01 -0700 (PDT) Date: Fri, 21 Jul 2000 13:39:00 -0700 (PDT) From: Dirk Kleinhesselink X-Sender: dkleinh@amadeus.ucsf.edu To: alpha@freebsd.org Subject: Re: 4.1-20000719-RC#2 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 21 Jul 2000, Matthew Jacob wrote: > > On Fri, 21 Jul 2000, Jordan K. Hubbard wrote: > > > > I've had no response from David about it, Jordan didn't add the xterm entry t > > o > > > the installer (as he said he would), and Mike hasn't looked at the 'going > > > > Well, the omission of an xterm entry was simply an oversight on my > > part and hardly a major show-stopper for the alpha, so I fail to see > > why you'd include this with the above list. > > Sorry- with vt100 or 'ansi' entries it's damned near impossible to be sure > whether or not you're actually seeing an artifact of wierd curses on serial > installs or not. I probably shouldn't have included it. > > > As to the "going nowhere > > without my init" problem, it's my understanding that nobody else can > > even *reproduce* it with the equipment available here or I'm sure > > you'd see a lot more furor over it. > > Nobody *tried* to reproduce it-that's what occurred. I offered to make > equipment available to make this process easier, but nobody got back to me on > this. It's happened several places, so I'm assuming that it isn't just a > oneshot problem. Seems like it would be an easy thing to try to reproduce: just put a couple of disks on the system and install Tru64/NetBSD/Linux/OpenVMS on one of them and then try to install FreeBSD on the other disk... > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 13:44: 5 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 789A437BEFB for ; Fri, 21 Jul 2000 13:44:02 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA14225; Fri, 21 Jul 2000 13:43:54 -0700 Date: Fri, 21 Jul 2000 13:43:32 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Dirk Kleinhesselink Cc: alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Seems like it would be an easy thing to try to reproduce: just put a > couple of disks on the system and install Tru64/NetBSD/Linux/OpenVMS on > one of them and then try to install FreeBSD on the other disk... You don't even have to do that. Just take a previous FreeBSD installation and move /sbin/init aside and create a zero length /sbin/init. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 13:48:28 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from zippy.osd.bsdi.com (zippy.osd.bsdi.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id B81F537C112 for ; Fri, 21 Jul 2000 13:48:25 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id NAA04988; Fri, 21 Jul 2000 13:49:21 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: mjacob@feral.com Cc: Dirk Kleinhesselink , alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-reply-to: Your message of "Fri, 21 Jul 2000 13:43:32 PDT." Date: Fri, 21 Jul 2000 13:49:20 -0700 Message-ID: <4985.964212560@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > Seems like it would be an easy thing to try to reproduce: just put a > > couple of disks on the system and install Tru64/NetBSD/Linux/OpenVMS on > > one of them and then try to install FreeBSD on the other disk... > > You don't even have to do that. Just take a previous FreeBSD installation and > move /sbin/init aside and create a zero length /sbin/init. I'm still not sure I understand how that should have any effect. You're doing an install here, right? And the install is going to newfs the root filesystem and repopulate it with distribution bits, right? If you're somehow electing to preserve the existing root partition and/or not extract, at a minimum, bindist then this isn't an installation at all, this is some sort of "you must know what you're doing well enough not to shoot your feet off" quasi-upgrade operation. Please clarify. Thanks. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 13:57:12 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from phy.ucsf.edu (phy.ucsf.edu [128.218.64.200]) by hub.freebsd.org (Postfix) with ESMTP id E0EAB37BF0B for ; Fri, 21 Jul 2000 13:57:09 -0700 (PDT) (envelope-from dkleinh@phy.ucsf.edu) Received: from amadeus.ucsf.edu (dkleinh@amadeus.ucsf.edu [128.218.65.107]) by phy.ucsf.edu (8.10.1/8.10.1) with ESMTP id e6LKv9k22472; Fri, 21 Jul 2000 13:57:09 -0700 (PDT) Received: from localhost by amadeus.ucsf.edu (8.8.6) id NAA20961; Fri, 21 Jul 2000 13:57:08 -0700 (PDT) Date: Fri, 21 Jul 2000 13:57:08 -0700 (PDT) From: Dirk Kleinhesselink X-Sender: dkleinh@amadeus.ucsf.edu To: "Jordan K. Hubbard" Cc: mjacob@feral.com, alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-Reply-To: <4985.964212560@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At least for myself and several others who had this problem: you will never get to the install setup up if your system already has a BSD (Tru64/NetBSD/Linux (using BSD disk label) and from Matt's example, a FreeBSD disk with the /sbin/init clobbered) or OpenVMS system disk. FreeBSD will load the kernel, load the install MFS but then will fail to find the MFS init routine -- I guess it will try to look for it on the BSD/VMS disk and will fail to find it. On Fri, 21 Jul 2000, Jordan K. Hubbard wrote: > > > > > > > Seems like it would be an easy thing to try to reproduce: just put a > > > couple of disks on the system and install Tru64/NetBSD/Linux/OpenVMS on > > > one of them and then try to install FreeBSD on the other disk... > > > > You don't even have to do that. Just take a previous FreeBSD installation and > > move /sbin/init aside and create a zero length /sbin/init. > > I'm still not sure I understand how that should have any effect. > You're doing an install here, right? And the install is going to > newfs the root filesystem and repopulate it with distribution bits, > right? > > If you're somehow electing to preserve the existing root partition > and/or not extract, at a minimum, bindist then this isn't an > installation at all, this is some sort of "you must know what you're > doing well enough not to shoot your feet off" quasi-upgrade operation. > Please clarify. Thanks. > > - Jordan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 14: 1:36 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 3916037C021 for ; Fri, 21 Jul 2000 14:01:34 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA14339; Fri, 21 Jul 2000 14:01:27 -0700 Date: Fri, 21 Jul 2000 14:01:05 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Jordan K. Hubbard" Cc: Dirk Kleinhesselink , alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-Reply-To: <4985.964212560@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The presumption here is that sysinstall is mounting the wrong disk. This has nothing to do with preservation of old data. On isaac.nas.nasa.gov, putting boot.flp on the *second* disk, I ran into the 'going nowhere w/o my init' problem as soon as I selected a terminal type. NetBSD was installed on the first && third disks. On ursula.nas.nasa.gov, I put boot.flp on the *first* disk, and did not run into this problem. This seems to give a clue as to where the problem might be. All of this has been reported in email, fairly clearly. On Fri, 21 Jul 2000, Jordan K. Hubbard wrote: > > > > > > > Seems like it would be an easy thing to try to reproduce: just put a > > > couple of disks on the system and install Tru64/NetBSD/Linux/OpenVMS on > > > one of them and then try to install FreeBSD on the other disk... > > > > You don't even have to do that. Just take a previous FreeBSD installation and > > move /sbin/init aside and create a zero length /sbin/init. > > I'm still not sure I understand how that should have any effect. > You're doing an install here, right? And the install is going to > newfs the root filesystem and repopulate it with distribution bits, > right? > > If you're somehow electing to preserve the existing root partition > and/or not extract, at a minimum, bindist then this isn't an > installation at all, this is some sort of "you must know what you're > doing well enough not to shoot your feet off" quasi-upgrade operation. > Please clarify. Thanks. > > - Jordan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 14: 9: 9 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from zippy.osd.bsdi.com (zippy.osd.bsdi.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id A19C237BCFC for ; Fri, 21 Jul 2000 14:09:05 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id OAA05136; Fri, 21 Jul 2000 14:09:53 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: Dirk Kleinhesselink Cc: "Jordan K. Hubbard" , mjacob@feral.com, alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-reply-to: Your message of "Fri, 21 Jul 2000 13:57:08 PDT." Date: Fri, 21 Jul 2000 14:09:53 -0700 Message-ID: <5133.964213793@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > At least for myself and several others who had this problem: > > you will never get to the install setup up if your system already has a > BSD (Tru64/NetBSD/Linux (using BSD disk label) and from Matt's example, a > FreeBSD disk with the /sbin/init clobbered) or OpenVMS system disk. > FreeBSD will load the kernel, load the install MFS but then will fail to > find the MFS init routine -- I guess it will try to look for it on the > BSD/VMS disk and will fail to find it. Erm, if that's the case, something seriously does not make sense or is broken in a very fundamental way. When the md driver is compiled in with MD_ROOT set, this happens: SYSINIT(md_root, SI_SUB_MOUNT_ROOT, SI_ORDER_FIRST, md_takeroot, NULL); Which should put the MFS root *first* in the root mount list. Any existing partitions should have no effect on this. - Jordan > > On Fri, 21 Jul 2000, Jordan K. Hubbard wrote: > > > > > > > > > > > Seems like it would be an easy thing to try to reproduce: just put a > > > > couple of disks on the system and install Tru64/NetBSD/Linux/OpenVMS on > > > > one of them and then try to install FreeBSD on the other disk... > > > > > > You don't even have to do that. Just take a previous FreeBSD installation and > > > move /sbin/init aside and create a zero length /sbin/init. > > > > I'm still not sure I understand how that should have any effect. > > You're doing an install here, right? And the install is going to > > newfs the root filesystem and repopulate it with distribution bits, > > right? > > > > If you're somehow electing to preserve the existing root partition > > and/or not extract, at a minimum, bindist then this isn't an > > installation at all, this is some sort of "you must know what you're > > doing well enough not to shoot your feet off" quasi-upgrade operation. > > Please clarify. Thanks. > > > > - Jordan > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-alpha" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 14:10:55 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 3D53137C021 for ; Fri, 21 Jul 2000 14:10:53 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA14384; Fri, 21 Jul 2000 14:10:46 -0700 Date: Fri, 21 Jul 2000 14:10:25 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Jordan K. Hubbard" Cc: Dirk Kleinhesselink , alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-Reply-To: <5133.964213793@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Erm, if that's the case, something seriously does not make sense or is > broken in a very fundamental way. > > When the md driver is compiled in with MD_ROOT set, this happens: > > SYSINIT(md_root, SI_SUB_MOUNT_ROOT, SI_ORDER_FIRST, md_takeroot, NULL); > > Which should put the MFS root *first* in the root mount list. Any > existing partitions should have no effect on this. One would think. Is there an optimization in the installer to look for an existing UFS filesystem to mount, as I said, *after* the terminal type question is asked which is getting spoofed? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 14:12: 5 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from zippy.osd.bsdi.com (zippy.osd.bsdi.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id BDC1437C02D for ; Fri, 21 Jul 2000 14:12:02 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id OAA05179; Fri, 21 Jul 2000 14:12:56 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: mjacob@feral.com Cc: "Jordan K. Hubbard" , Dirk Kleinhesselink , alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-reply-to: Your message of "Fri, 21 Jul 2000 14:01:05 PDT." Date: Fri, 21 Jul 2000 14:12:56 -0700 Message-ID: <5176.964213976@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The presumption here is that sysinstall is mounting the wrong disk. This has > nothing to do with preservation of old data. Well, I'm still not sure how sysinstall could "mount the wrong disk" unless you explicitly told it to do so or major/minor devices are broken so badly that /dev/sd0a actually points to SCSI disk #2 rather than #1 on your system (which I kinda doubt). When you actually come up, mounting the right disk as root is more of a loader issue and setting your root device properly; it has nothing to do with sysinstall. > On isaac.nas.nasa.gov, putting boot.flp on the *second* disk, I ran into the > 'going nowhere w/o my init' problem as soon as I selected a terminal type. > NetBSD was installed on the first && third disks. I really don't know what you mean by "putting boot.flp on the second disk" - you mean you dd'd the boot.flp image straight onto the beginning of your SCSI drive? I'm getting even more confused. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 14:13: 7 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from zippy.osd.bsdi.com (zippy.osd.bsdi.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id AB59437C021 for ; Fri, 21 Jul 2000 14:13:03 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id OAA05203; Fri, 21 Jul 2000 14:14:02 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: mjacob@feral.com Cc: "Jordan K. Hubbard" , Dirk Kleinhesselink , alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-reply-to: Your message of "Fri, 21 Jul 2000 14:10:25 PDT." Date: Fri, 21 Jul 2000 14:14:02 -0700 Message-ID: <5200.964214042@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Is there an optimization in the installer to look for an existing UFS > filesystem to mount, as I said, *after* the terminal type question is asked > which is getting spoofed? Nope - the installer simply writes the MBR, the disk label and then goes off to newfs each filesystem in turn. It doesn't attempt to mount anything unless you explicitly tell it to do so or are doing an upgrade operation (which is sort of the same thing). - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 14:15:20 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id C9D1337BF63 for ; Fri, 21 Jul 2000 14:15:15 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA14426; Fri, 21 Jul 2000 14:15:08 -0700 Date: Fri, 21 Jul 2000 14:14:46 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Jordan K. Hubbard" Cc: Dirk Kleinhesselink , alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-Reply-To: <5176.964213976@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > The presumption here is that sysinstall is mounting the wrong disk. This has > > nothing to do with preservation of old data. > > Well, I'm still not sure how sysinstall could "mount the wrong disk" > unless you explicitly told it to do so or major/minor devices are broken > so badly that /dev/sd0a actually points to SCSI disk #2 rather than #1 > on your system (which I kinda doubt). > > When you actually come up, mounting the right disk as root is more of > a loader issue and setting your root device properly; it has nothing > to do with sysinstall. Uh- this is *after* the terminal type question is asked. Is that question asked prior to mounting root? > > > On isaac.nas.nasa.gov, putting boot.flp on the *second* disk, I ran into the > > 'going nowhere w/o my init' problem as soon as I selected a terminal type. > > NetBSD was installed on the first && third disks. > > I really don't know what you mean by "putting boot.flp on the second > disk" - you mean you dd'd the boot.flp image straight onto the > beginning of your SCSI drive? I'm getting even more confused. Of course. That's the way to take a 2MB image and try and install from it? I mean, I don't have any 2MB floppy drives. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 14:17:36 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from zippy.osd.bsdi.com (zippy.osd.bsdi.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id E00FA37C021 for ; Fri, 21 Jul 2000 14:17:33 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id OAA05249; Fri, 21 Jul 2000 14:18:16 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: mjacob@feral.com Cc: "Jordan K. Hubbard" , Dirk Kleinhesselink , alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-reply-to: Your message of "Fri, 21 Jul 2000 14:14:46 PDT." Date: Fri, 21 Jul 2000 14:18:16 -0700 Message-ID: <5246.964214296@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Uh- this is *after* the terminal type question is asked. Is that question > asked prior to mounting root? Well, actually, root's already mounted at the point that you get asked that question - it's the MFS partition. You don't get a new root until you've installed and rebooted. > Of course. That's the way to take a 2MB image and try and install from it? I > mean, I don't have any 2MB floppy drives. OK, just making sure. It's still unusual to see this. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 14:19:26 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1B22437C0DA for ; Fri, 21 Jul 2000 14:19:24 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA14465; Fri, 21 Jul 2000 14:19:13 -0700 Date: Fri, 21 Jul 2000 14:18:52 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Jordan K. Hubbard" Cc: Dirk Kleinhesselink , alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-Reply-To: <5246.964214296@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 21 Jul 2000, Jordan K. Hubbard wrote: > > Uh- this is *after* the terminal type question is asked. Is that question > > asked prior to mounting root? > > Well, actually, root's already mounted at the point that you get asked > that question - it's the MFS partition. You don't get a new root > until you've installed and rebooted. Then confusion certainly is our shared emotion about this.... > > > Of course. That's the way to take a 2MB image and try and install from it? I > > mean, I don't have any 2MB floppy drives. > > OK, just making sure. It's still unusual to see this. :) > > - Jordan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 14:24:29 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id D4EDD37C0E4; Fri, 21 Jul 2000 14:24:24 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13FkHL-0002xY-00; Fri, 21 Jul 2000 21:24:19 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id XAA21802; Fri, 21 Jul 2000 23:13:07 +0200 (CEST) (envelope-from wkb) Date: Fri, 21 Jul 2000 23:13:07 +0200 From: Wilko Bulte To: "Jordan K. Hubbard" Cc: mjacob@feral.com, wilko@FreeBSD.ORG, alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 Message-ID: <20000721231307.C21729@freebie.demon.nl> Reply-To: wilko@FreeBSD.ORG References: <4400.964211365@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <4400.964211365@localhost>; from jkh@zippy.osd.bsdi.com on Fri, Jul 21, 2000 at 01:29:25PM -0700 X-OS: FreeBSD 4.1-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jul 21, 2000 at 01:29:25PM -0700, Jordan K. Hubbard wrote: > > I've had no response from David about it, Jordan didn't add the xterm entry t > o > > the installer (as he said he would), and Mike hasn't looked at the 'going > > Well, the omission of an xterm entry was simply an oversight on my > part and hardly a major show-stopper for the alpha, so I fail to see > why you'd include this with the above list. As to the "going nowhere > without my init" problem, it's my understanding that nobody else can > even *reproduce* it with the equipment available here or I'm sure > you'd see a lot more furor over it. Well, it is now in the RELNOTES in case anybody manages to reproduce it involuntary ;-) I've seen to many noise around this to leave it out. Wilko -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 14:24:30 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 12B6A37C0ED for ; Fri, 21 Jul 2000 14:24:25 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13FkHP-0002xX-00; Fri, 21 Jul 2000 21:24:23 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id XAA21765; Fri, 21 Jul 2000 23:08:11 +0200 (CEST) (envelope-from wkb) Date: Fri, 21 Jul 2000 23:08:11 +0200 From: Wilko Bulte To: "Jung, Michael" Cc: "'alpha@freebsd.org'" Subject: Re: RC2 on 2100 4/233 Message-ID: <20000721230811.A21729@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <921763828F4BD4118D7D00805FEDF35810C5B1@EXCHANGE1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <921763828F4BD4118D7D00805FEDF35810C5B1@EXCHANGE1>; from mjung@npc.net on Fri, Jul 21, 2000 at 04:20:32PM -0400 X-OS: FreeBSD 4.1-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jul 21, 2000 at 04:20:32PM -0400, Jung, Michael wrote: > For what its worth the iso-image of rc2 boots and loads > on a 2100 4/233 > > Copyright (c) 1992-2000 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.1-20000718-RC #0: Tue Jul 18 17:15:16 GMT 2000 > rootk@a41.nuxi.com:/usr/src/sys/compile/BOOTMFS > DEC AlphaServer 2100 > AlphaServer 2100 4/233, 233MHz > 8192 byte page size, 1 processor. > CPU: EV45 (21064A) major=6 minor=2 > OSF PAL rev: 0x4000c0002012d > real memory = 266264576 (260024K bytes) > avail memory = 251060224 (245176K bytes) > > However if you tell the installer to install - everything - it bombs and > doesn't update /etc - It complains that INDEX isn't available The ISO image that David put up for ftp is not a complete one, it does not have the ports, packages etc. Take a close look and you will see it is only 160-something Mb in size. That is the reason for the complaining installer. -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 14:42:34 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 0B37137B6F1 for ; Fri, 21 Jul 2000 14:42:31 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA07539; Fri, 21 Jul 2000 14:42:13 -0700 (PDT) (envelope-from obrien) Date: Fri, 21 Jul 2000 14:42:13 -0700 From: "David O'Brien" To: Matthew Jacob Cc: "Jordan K. Hubbard" , alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 Message-ID: <20000721144213.B7414@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <4400.964211365@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Fri, Jul 21, 2000 at 01:31:39PM -0700 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 X-Loop: FreeBSD.org On Fri, Jul 21, 2000 at 01:31:39PM -0700, Matthew Jacob wrote: > > As to the "going nowhere > > without my init" problem, it's my understanding that nobody else can > > even *reproduce* it with the equipment available here or I'm sure > > you'd see a lot more furor over it. > > Nobody *tried* to reproduce it-that's what occurred. This is infact the case. All the Alpha's here are busy being desktop or freebsd.org test machines (ie, Beast, a41, Qube, and Baz). So we are not really able to tear them appart for testing. Mike and I had hoped to use the 4100 to debug this problem. But it isn't usable yet. > I offered to make equipment available to make this process easier, I am sorry that I missed this. I didn't know you had done this. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 14:53: 8 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 89B0C37C0EF for ; Fri, 21 Jul 2000 14:53:04 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA07590; Fri, 21 Jul 2000 14:53:00 -0700 (PDT) (envelope-from obrien) Date: Fri, 21 Jul 2000 14:53:00 -0700 From: "David O'Brien" To: "Jordan K. Hubbard" Cc: alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 Message-ID: <20000721145300.C7414@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <5246.964214296@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <5246.964214296@localhost>; from jkh@zippy.osd.bsdi.com on Fri, Jul 21, 2000 at 02:18:16PM -0700 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 X-Loop: FreeBSD.org On Fri, Jul 21, 2000 at 02:18:16PM -0700, Jordan K. Hubbard wrote: > > Of course. That's the way to take a 2MB image and try and install from it? I > > mean, I don't have any 2MB floppy drives. > > OK, just making sure. It's still unusual to see this. :) Its by far the easiest way to get NetBSD installed on a non-i386 machine. So it isn't that unusual to people familiar with NetBSD. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 14:55:18 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9E69E37B8F1; Fri, 21 Jul 2000 14:55:15 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA14673; Fri, 21 Jul 2000 14:55:14 -0700 Date: Fri, 21 Jul 2000 14:54:52 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: "Jordan K. Hubbard" , alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-Reply-To: <20000721145300.C7414@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Its by far the easiest way to get NetBSD installed on a non-i386 machine. > So it isn't that unusual to people familiar with NetBSD. The netbsd installer actually works reasonably well for Alphas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 14:55:32 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id C1A2D37B7E8; Fri, 21 Jul 2000 14:55:29 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA07606; Fri, 21 Jul 2000 14:55:28 -0700 (PDT) (envelope-from obrien) Date: Fri, 21 Jul 2000 14:55:28 -0700 From: "David O'Brien" To: wilko@freebsd.org Cc: "Jung, Michael" , "'alpha@freebsd.org'" Subject: Re: RC2 on 2100 4/233 Message-ID: <20000721145528.D7414@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <921763828F4BD4118D7D00805FEDF35810C5B1@EXCHANGE1> <20000721230811.A21729@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000721230811.A21729@freebie.demon.nl>; from wkb@freebie.demon.nl on Fri, Jul 21, 2000 at 11:08:11PM +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 X-Loop: FreeBSD.org On Fri, Jul 21, 2000 at 11:08:11PM +0200, Wilko Bulte wrote: > The ISO image that David put up for ftp is not a complete one, it does > not have the ports, packages etc. Take a close look and you will see it > is only 160-something Mb in size. Actually it does have ports, but not packages or docs. The reason being that there are some issues just booting and doing a minimal install. Thus I wanted to make the ISO small to make it easy for people to download and test on as many machines as possible. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 14:56:53 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 7E8CC37B8F1; Fri, 21 Jul 2000 14:56:48 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13Fkmj-0003GC-00; Fri, 21 Jul 2000 21:56:45 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id XAA22135; Fri, 21 Jul 2000 23:47:59 +0200 (CEST) (envelope-from wkb) Date: Fri, 21 Jul 2000 23:47:59 +0200 From: Wilko Bulte To: "David O'Brien" Cc: Matthew Jacob , "Jordan K. Hubbard" , alpha@freebsd.org Subject: Re: 4.1-20000719-RC#2 Message-ID: <20000721234759.C21976@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <4400.964211365@localhost> <20000721144213.B7414@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000721144213.B7414@dragon.nuxi.com>; from obrien@freebsd.org on Fri, Jul 21, 2000 at 02:42:13PM -0700 X-OS: FreeBSD 4.1-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jul 21, 2000 at 02:42:13PM -0700, David O'Brien wrote: > On Fri, Jul 21, 2000 at 01:31:39PM -0700, Matthew Jacob wrote: > > > As to the "going nowhere > > > without my init" problem, it's my understanding that nobody else can > > > even *reproduce* it with the equipment available here or I'm sure > > > you'd see a lot more furor over it. > > > > Nobody *tried* to reproduce it-that's what occurred. > > This is infact the case. All the Alpha's here are busy being desktop or > freebsd.org test machines (ie, Beast, a41, Qube, and Baz). So we are not > really able to tear them appart for testing. FWIW I'm putting T64 4.0G on one of the disks of my Miata. Will see what happens.. Probably tomorrow I hope to have more news. > Mike and I had hoped to use the 4100 to debug this problem. > But it isn't usable yet. 4100 makes a good release builder once installed via another machine.. -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 14:57:54 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 130C637C13C; Fri, 21 Jul 2000 14:57:46 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA14702; Fri, 21 Jul 2000 14:57:44 -0700 Date: Fri, 21 Jul 2000 14:57:23 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: wilko@freebsd.org Cc: "David O'Brien" , "Jordan K. Hubbard" , alpha@freebsd.org Subject: Re: 4.1-20000719-RC#2 In-Reply-To: <20000721234759.C21976@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Mike and I had hoped to use the 4100 to debug this problem. > > But it isn't usable yet. The 4100 is perfectly usable. The issues are entirely in the installer and/or the boot blocks. > 4100 makes a good release builder once installed via another machine.. TurboLaser, even with a slower CPU, actually makes a better one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 15:10: 0 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from charon.npc.net (charon.finall.com [199.15.61.3]) by hub.freebsd.org (Postfix) with ESMTP id 71FC237C1FA for ; Fri, 21 Jul 2000 15:09:57 -0700 (PDT) (envelope-from mikej@charon.npc.net) Received: from localhost (mikej@localhost) by charon.npc.net (8.10.2/8.10.2) with ESMTP id e6LM9qL66130 for ; Fri, 21 Jul 2000 18:09:52 -0400 (EDT) Date: Fri, 21 Jul 2000 18:09:52 -0400 (EDT) From: Michael Jung To: freebsd-alpha@freebsd.org Subject: Booting from Raid Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok I admit I've probably not looked hard enough but it seems that I read recently that you should be able to boot from DAC960 PCI raid partitions under FreeBSD-Alpha... Shortly before I left work today we started to load the rc2 iso on a 2100 and it did not recognize the raid partition.. Hope i'm not once again in left field... --mikej mikej@mikej.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 15:12:51 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from charon.npc.net (charon.finall.com [199.15.61.3]) by hub.freebsd.org (Postfix) with ESMTP id 660EC37C1FA for ; Fri, 21 Jul 2000 15:12:42 -0700 (PDT) (envelope-from mikej@charon.npc.net) Received: from localhost (mikej@localhost) by charon.npc.net (8.10.2/8.10.2) with ESMTP id e6LMCfZ66307 for ; Fri, 21 Jul 2000 18:12:41 -0400 (EDT) Date: Fri, 21 Jul 2000 18:12:41 -0400 (EDT) From: Michael Jung To: freebsd-alpha@freebsd.org Subject: RE: Booting from Raid Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Oh.. and yes this was a raid card sold by DEC/Compaq - This 2100 originally ran NT --mikej To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 15:14:50 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 53E9A37C22B; Fri, 21 Jul 2000 15:14:28 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13Fl3k-0003wI-00; Fri, 21 Jul 2000 22:14:21 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id AAA22494; Sat, 22 Jul 2000 00:14:03 +0200 (CEST) (envelope-from wkb) Date: Sat, 22 Jul 2000 00:14:03 +0200 From: Wilko Bulte To: "David O'Brien" Cc: Matthew Jacob , "Jordan K. Hubbard" , alpha@freebsd.org Subject: Re: 4.1-20000719-RC#2 Message-ID: <20000722001403.A22453@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <4400.964211365@localhost> <20000721144213.B7414@dragon.nuxi.com> <20000721234759.C21976@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000721234759.C21976@freebie.demon.nl>; from wkb@freebie.demon.nl on Fri, Jul 21, 2000 at 11:47:59PM +0200 X-OS: FreeBSD 4.1-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jul 21, 2000 at 11:47:59PM +0200, Wilko Bulte wrote: > On Fri, Jul 21, 2000 at 02:42:13PM -0700, David O'Brien wrote: > > On Fri, Jul 21, 2000 at 01:31:39PM -0700, Matthew Jacob wrote: > > > > As to the "going nowhere > > > > without my init" problem, it's my understanding that nobody else can > > > > even *reproduce* it with the equipment available here or I'm sure > > > > you'd see a lot more furor over it. > > > > > > Nobody *tried* to reproduce it-that's what occurred. > > > > This is infact the case. All the Alpha's here are busy being desktop or > > freebsd.org test machines (ie, Beast, a41, Qube, and Baz). So we are not > > really able to tear them appart for testing. > > FWIW I'm putting T64 4.0G on one of the disks of my Miata. Will see what > happens.. Probably tomorrow I hope to have more news. OK, it is tomorrow ;-) 00:05, T64 installed quicker than I expected. I now have 3 SCSI disks, attached to a single (onboard) QL1040: ID0 -> scratch, for install tests ID1 -> Tru64 4.0G freshly installed ID2 -> RELENG_4 installed (used for test builds etc) I just booted the 4.1RC-2 CD on it and the install ran without accidents (to the disk at ID0). I'm gonna try floppies next. -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 15:17:38 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id EB4B537C156; Fri, 21 Jul 2000 15:16:35 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA14802; Fri, 21 Jul 2000 15:16:35 -0700 Date: Fri, 21 Jul 2000 15:16:13 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: wilko@freebsd.org Cc: "David O'Brien" , "Jordan K. Hubbard" , alpha@freebsd.org Subject: Re: 4.1-20000719-RC#2 In-Reply-To: <20000722001403.A22453@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I just booted the 4.1RC-2 CD on it and the install ran without accidents > (to the disk at ID0). Great news! > > I'm gonna try floppies next. > > -- > Wilko Bulte http://www.freebsd.org > wilko@freebsd.org http://www.nlfug.nl > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 15:44: 3 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 711E737B61A for ; Fri, 21 Jul 2000 15:43:54 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13FlWK-0003gt-01 for freebsd-alpha@freebsd.org; Fri, 21 Jul 2000 22:43:52 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id AAA22793 for freebsd-alpha@freebsd.org; Sat, 22 Jul 2000 00:40:09 +0200 (CEST) (envelope-from wkb) Date: Sat, 22 Jul 2000 00:40:09 +0200 From: Wilko Bulte To: FreeBSD-alpha mailing list Subject: U: Request for testers of "going nowhere without my init" Message-ID: <20000722004009.A22692@freebie.demon.nl> Reply-To: wilko@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-OS: FreeBSD 4.1-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org For those of you who have experienced the dreaded "going nowhere without my init" problem during the install of FreeBSD/alpha: **please** take the time to pull the 4.1-RC from ftp.freebsd.org and test it on the hardware that gave you the "going nowhere without my init" problem. And report back.. -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 15:44: 4 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 1555E37B60F for ; Fri, 21 Jul 2000 15:43:54 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13FlWK-0003gt-00; Fri, 21 Jul 2000 22:43:52 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id AAA22822; Sat, 22 Jul 2000 00:43:32 +0200 (CEST) (envelope-from wkb) Date: Sat, 22 Jul 2000 00:43:32 +0200 From: Wilko Bulte To: Michael Jung Cc: freebsd-alpha@freebsd.org Subject: Re: Booting from Raid Message-ID: <20000722004332.C22692@freebie.demon.nl> Reply-To: wilko@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mikej@charon.npc.net on Fri, Jul 21, 2000 at 06:09:52PM -0400 X-OS: FreeBSD 4.1-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jul 21, 2000 at 06:09:52PM -0400, Michael Jung wrote: > > Ok I admit I've probably not looked hard enough > but it seems that I read recently that you should > be able to boot from DAC960 PCI raid partitions > under FreeBSD-Alpha... > > Shortly before I left work today we started to > load the rc2 iso on a 2100 and it did not > recognize the raid partition.. Guessing: maybe the mlx driver is not in the installkernel? At least the floppies were already over-stuffed with bits. -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 15:44: 6 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id C846037B6BB; Fri, 21 Jul 2000 15:43:57 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13FlWL-0003gt-00; Fri, 21 Jul 2000 22:43:53 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id AAA22804; Sat, 22 Jul 2000 00:41:56 +0200 (CEST) (envelope-from wkb) Date: Sat, 22 Jul 2000 00:41:56 +0200 From: Wilko Bulte To: Matthew Jacob Cc: wilko@freebsd.org, "David O'Brien" , "Jordan K. Hubbard" , alpha@freebsd.org Subject: Re: 4.1-20000719-RC#2 Message-ID: <20000722004156.B22692@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <20000722001403.A22453@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Fri, Jul 21, 2000 at 03:16:13PM -0700 X-OS: FreeBSD 4.1-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jul 21, 2000 at 03:16:13PM -0700, Matthew Jacob wrote: > > I just booted the 4.1RC-2 CD on it and the install ran without accidents > > (to the disk at ID0). > > Great news! Yes. > > I'm gonna try floppies next. Worked fine too. I hope people will respond to my request for testing on those machines exhibiting "going nowhere without my init". W/ -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 15:44:10 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 6C1B837B641; Fri, 21 Jul 2000 15:43:56 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13FlWM-0003gt-00; Fri, 21 Jul 2000 22:43:54 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id AAA22653; Sat, 22 Jul 2000 00:23:31 +0200 (CEST) (envelope-from wkb) Date: Sat, 22 Jul 2000 00:23:31 +0200 From: Wilko Bulte To: Matthew Jacob Cc: wilko@freebsd.org, "David O'Brien" , "Jordan K. Hubbard" , alpha@freebsd.org Subject: Re: 4.1-20000719-RC#2 Message-ID: <20000722002331.B22611@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <20000721234759.C21976@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Fri, Jul 21, 2000 at 02:57:23PM -0700 X-OS: FreeBSD 4.1-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jul 21, 2000 at 02:57:23PM -0700, Matthew Jacob wrote: > > > Mike and I had hoped to use the 4100 to debug this problem. > > > But it isn't usable yet. > > The 4100 is perfectly usable. The issues are entirely in the installer and/or > the boot blocks. Yes, that is what I wrote and experienced myself. > > 4100 makes a good release builder once installed via another machine.. > > TurboLaser, even with a slower CPU, actually makes a better one. And a noisier one ;-) But I'd go for the ES40. -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 15:44:15 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 6207837B7B0 for ; Fri, 21 Jul 2000 15:43:58 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13FlWL-0003gt-01; Fri, 21 Jul 2000 22:43:54 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id AAA22639; Sat, 22 Jul 2000 00:22:14 +0200 (CEST) (envelope-from wkb) Date: Sat, 22 Jul 2000 00:22:14 +0200 From: Wilko Bulte To: Dirk Kleinhesselink Cc: "Jordan K. Hubbard" , mjacob@feral.com, alpha@freebsd.org Subject: Re: 4.1-20000719-RC#2 Message-ID: <20000722002214.A22611@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <4985.964212560@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from dkleinh@phy.ucsf.edu on Fri, Jul 21, 2000 at 01:57:08PM -0700 X-OS: FreeBSD 4.1-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jul 21, 2000 at 01:57:08PM -0700, Dirk Kleinhesselink wrote: Is there any ordering involved? Meaning that the FreeBSD install is aimed at a disk with a higher SCSI ID than the existing T64/VMS/whatever disk? Does it matter if it is a floppy boot or a CD boot? I cannot reproduce it here when aiming the new FreeBSD install at a disk with ID0, so the 2 other disks with T64 and FreeBSD respectively are obviously higher numbered ones. Long shot.. W/ > At least for myself and several others who had this problem: > > you will never get to the install setup up if your system already has a > BSD (Tru64/NetBSD/Linux (using BSD disk label) and from Matt's example, a > FreeBSD disk with the /sbin/init clobbered) or OpenVMS system disk. > FreeBSD will load the kernel, load the install MFS but then will fail to > find the MFS init routine -- I guess it will try to look for it on the > BSD/VMS disk and will fail to find it. > > On Fri, 21 Jul 2000, Jordan K. Hubbard wrote: > > > > > > > > > > > Seems like it would be an easy thing to try to reproduce: just put a > > > > couple of disks on the system and install Tru64/NetBSD/Linux/OpenVMS on > > > > one of them and then try to install FreeBSD on the other disk... > > > > > > You don't even have to do that. Just take a previous FreeBSD installation and > > > move /sbin/init aside and create a zero length /sbin/init. > > > > I'm still not sure I understand how that should have any effect. > > You're doing an install here, right? And the install is going to > > newfs the root filesystem and repopulate it with distribution bits, > > right? > > > > If you're somehow electing to preserve the existing root partition > > and/or not extract, at a minimum, bindist then this isn't an > > installation at all, this is some sort of "you must know what you're > > doing well enough not to shoot your feet off" quasi-upgrade operation. > > Please clarify. Thanks. > > > > - Jordan -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 15:51:43 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CFC3237BEA1; Fri, 21 Jul 2000 15:51:38 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA14966; Fri, 21 Jul 2000 15:51:36 -0700 Date: Fri, 21 Jul 2000 15:51:14 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: wilko@freebsd.org Cc: "David O'Brien" , "Jordan K. Hubbard" , alpha@freebsd.org Subject: Re: 4.1-20000719-RC#2 In-Reply-To: <20000722004156.B22692@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Worked fine too. I hope people will respond to my request for testing > on those machines exhibiting "going nowhere without my init". I'll try. I'm now 80 km away from the machine that I had the problem on- if I can get it booted remotely via netbsd, I'll try to reproduce it again. I have existing tests running on the 4100 at Feral I can't disturb for a day. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 15:52:12 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id C32E437C168; Fri, 21 Jul 2000 15:52:05 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA14976; Fri, 21 Jul 2000 15:52:03 -0700 Date: Fri, 21 Jul 2000 15:51:42 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: wilko@freebsd.org Cc: "David O'Brien" , "Jordan K. Hubbard" , alpha@freebsd.org Subject: Re: 4.1-20000719-RC#2 In-Reply-To: <20000722002331.B22611@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, I'd go for a an ES40 too.... On Sat, 22 Jul 2000, Wilko Bulte wrote: > On Fri, Jul 21, 2000 at 02:57:23PM -0700, Matthew Jacob wrote: > > > > Mike and I had hoped to use the 4100 to debug this problem. > > > > But it isn't usable yet. > > > > The 4100 is perfectly usable. The issues are entirely in the installer and/or > > the boot blocks. > > Yes, that is what I wrote and experienced myself. > > > > 4100 makes a good release builder once installed via another machine.. > > > > TurboLaser, even with a slower CPU, actually makes a better one. > > And a noisier one ;-) But I'd go for the ES40. > > -- > Wilko Bulte http://www.freebsd.org > wilko@freebsd.org http://www.nlfug.nl > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 16:14:44 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from phy.ucsf.edu (phy.ucsf.edu [128.218.64.200]) by hub.freebsd.org (Postfix) with ESMTP id 32F1737C145; Fri, 21 Jul 2000 16:14:40 -0700 (PDT) (envelope-from dkleinh@phy.ucsf.edu) Received: from amadeus.ucsf.edu (dkleinh@amadeus.ucsf.edu [128.218.65.107]) by phy.ucsf.edu (8.10.1/8.10.1) with ESMTP id e6LNEdk26235; Fri, 21 Jul 2000 16:14:40 -0700 (PDT) Received: from localhost by amadeus.ucsf.edu (8.8.6) id QAA22550; Fri, 21 Jul 2000 16:14:39 -0700 (PDT) Date: Fri, 21 Jul 2000 16:14:39 -0700 (PDT) From: Dirk Kleinhesselink X-Sender: dkleinh@amadeus.ucsf.edu To: wilko@freebsd.org Cc: "Jordan K. Hubbard" , mjacob@feral.com, alpha@freebsd.org Subject: Re: 4.1-20000719-RC#2 In-Reply-To: <20000722002214.A22611@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I got the problem on my PC164 system with, if I remember correctly, Tru64 on my one SCSI disk and Linux on the 2nd IDE disk. I was going to replace the Tru64 with FreeBSD on the SCSI disk. I also installed NetBSD on the SCSI and got the problem. I may have also wiped the SCSI disk using linux making a DOS style partition table and Linux ext2 filesystem but it still failed by having Linux bootable on the ide disk. On Sat, 22 Jul 2000, Wilko Bulte wrote: > On Fri, Jul 21, 2000 at 01:57:08PM -0700, Dirk Kleinhesselink wrote: > > Is there any ordering involved? Meaning that the FreeBSD install is > aimed at a disk with a higher SCSI ID than the existing T64/VMS/whatever > disk? > > Does it matter if it is a floppy boot or a CD boot? > > I cannot reproduce it here when aiming the new FreeBSD install at a > disk with ID0, so the 2 other disks with T64 and FreeBSD respectively are > obviously higher numbered ones. > > Long shot.. > > W/ > > > At least for myself and several others who had this problem: > > > > you will never get to the install setup up if your system already has a > > BSD (Tru64/NetBSD/Linux (using BSD disk label) and from Matt's example, a > > FreeBSD disk with the /sbin/init clobbered) or OpenVMS system disk. > > FreeBSD will load the kernel, load the install MFS but then will fail to > > find the MFS init routine -- I guess it will try to look for it on the > > BSD/VMS disk and will fail to find it. > > > > On Fri, 21 Jul 2000, Jordan K. Hubbard wrote: > > > > > > > > > > > > > > > Seems like it would be an easy thing to try to reproduce: just put a > > > > > couple of disks on the system and install Tru64/NetBSD/Linux/OpenVMS on > > > > > one of them and then try to install FreeBSD on the other disk... > > > > > > > > You don't even have to do that. Just take a previous FreeBSD installation and > > > > move /sbin/init aside and create a zero length /sbin/init. > > > > > > I'm still not sure I understand how that should have any effect. > > > You're doing an install here, right? And the install is going to > > > newfs the root filesystem and repopulate it with distribution bits, > > > right? > > > > > > If you're somehow electing to preserve the existing root partition > > > and/or not extract, at a minimum, bindist then this isn't an > > > installation at all, this is some sort of "you must know what you're > > > doing well enough not to shoot your feet off" quasi-upgrade operation. > > > Please clarify. Thanks. > > > > > > - Jordan > > -- > Wilko Bulte http://www.freebsd.org > wilko@freebsd.org http://www.nlfug.nl > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 16:19:10 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CED8437C143 for ; Fri, 21 Jul 2000 16:19:07 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA15096 for ; Fri, 21 Jul 2000 16:19:07 -0700 Date: Fri, 21 Jul 2000 16:18:45 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: alpha@FreeBSD.ORG Subject: so, what does BOOTMFS install kernel need a parallel port for? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org If we're concerned with size on floppies, what is ppc0: at port 0x3bc-0x3c3 irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: cannot reserve interrupt, failed. ppc0: interrupting at ISA irq 7 this doing in the install kernel? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 16:20:54 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from phy.ucsf.edu (phy.ucsf.edu [128.218.64.200]) by hub.freebsd.org (Postfix) with ESMTP id A1D1337C11B; Fri, 21 Jul 2000 16:20:51 -0700 (PDT) (envelope-from dkleinh@phy.ucsf.edu) Received: from amadeus.ucsf.edu (dkleinh@amadeus.ucsf.edu [128.218.65.107]) by phy.ucsf.edu (8.10.1/8.10.1) with ESMTP id e6LNKpk28298; Fri, 21 Jul 2000 16:20:51 -0700 (PDT) Received: from localhost by amadeus.ucsf.edu (8.8.6) id QAA22065; Fri, 21 Jul 2000 16:20:50 -0700 (PDT) Date: Fri, 21 Jul 2000 16:20:50 -0700 (PDT) From: Dirk Kleinhesselink X-Sender: dkleinh@amadeus.ucsf.edu To: wilko@FreeBSD.ORG Cc: alpha@FreeBSD.ORG Subject: Re: U: Request for testers of "going nowhere without my init" In-Reply-To: <20000722004009.A22692@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'll try the floppies this weekend -- I don't think I can download the cd image before I leave this evening. Dirk On Sat, 22 Jul 2000, Wilko Bulte wrote: > For those of you who have experienced the dreaded "going nowhere without my > init" problem during the install of FreeBSD/alpha: > > **please** take the time to pull the 4.1-RC from ftp.freebsd.org > and test it on the hardware that gave you the "going nowhere without my > init" problem. > > And report back.. > > -- > Wilko Bulte http://www.freebsd.org > wilko@freebsd.org http://www.nlfug.nl > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 16:53:23 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 9D1CA37C182 for ; Fri, 21 Jul 2000 16:53:19 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id RAA01857; Fri, 21 Jul 2000 17:02:43 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007220002.RAA01857@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE In-reply-to: Your message of "Fri, 21 Jul 2000 20:32:00 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Fri, 21 Jul 2000 17:02:43 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > = > = > On Thu, 20 Jul 2000, Mike Smith wrote: > = > > > It is my opinion. You may disagree but it will hard for anybody to > > > convince me that I am wrong. ;-) > > = > > On x86, it's very hard for you to be right; the CPU specification and= bus > > bridge behaviour both guarantee retirement of writes in order of issu= ance. > > This combined with strong cache coherency makes barriers irrelevant o= n > > this platform. > = > Let a PCI device perform: > STORE A > STORE B > = > Let the CPU perform and expect: > LOAD B > LOAD A > = > Let some CPU speculative execution carry out to the system BUS: > LOAD A > LOAD B > = > My reading of the the Intel docs didn't convince me that such reorderin= g > is not possible. > = > Typically A is some indicator of an IO completion pushed to a completio= n = > queue and B is the associated status data. You've got those the wrong way around; A will be the status, and B the = indicator (since we have to assume the peripheral is correctly designed).= I don't believe that the x86 re-orders read operations (but I don't have = the P6 architecture manuals here to be certain). If it does, then to = remain compatible with older x86 processors, it would have to invalidate = the pipeline and re-fetch when the bus snoop code detected the STORE B. > > As far as other platforms are concerned, however, you're quite correc= t. > = > Are you still so sure. ;-) Yes. x86 has so much seralised legacy baggage that it's a special case. = = Everyone else needs help. 8) > > There does need to be an extension to the busspace API to define a ra= nge = > > of host memory with a tag/handle pair for barrier activity. > = > Hmmm... Barrier semantics vary so much between architectures that an > unified semantic that also address device driver's concerns (not only > CPU<->CPU) is either close to impossible or will just be extremally poo= r, > in my opinion. I'm open to edification here, but I think that the ability to define the = sort of barrier operation required for a memory region and to then = invoke said barrier is about the best we can hope for. > The drivers I maintain will always contain any stuff needed for them to= be > as correct as I want them to be, modulo my knowledge and competence on > addressed platforms obviously. I don't think anyone could ask for any more than that. -- = =2E.. every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 16:54:33 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id E5A5337C1EF for ; Fri, 21 Jul 2000 16:54:31 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id RAA01882; Fri, 21 Jul 2000 17:03:58 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007220003.RAA01882@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andrew Gallatin Cc: obrien@NUXI.com, alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-reply-to: Your message of "Fri, 21 Jul 2000 14:57:03 EDT." <14712.39534.122473.899129@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Jul 2000 17:03:58 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > One install nit. This box has a TGA card in it. When I use a > graphics console, it says: "/stand/sysinstall running as init on > serial console" However, its not running on the serial console. > In fact, I/O to sysinstall seems to be going into the bitbucket. > > All is fine if I set the console to serial prior to the install. > Is this behaviour documented? From the Alpha HARDWARE.TXT: Please note that TGA cards are not supported as FreeBSD console display cards. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 17: 3:15 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id D42BF37C29E for ; Fri, 21 Jul 2000 17:03:13 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id RAA01937; Fri, 21 Jul 2000 17:12:42 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007220012.RAA01937@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dirk Kleinhesselink Cc: alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-reply-to: Your message of "Fri, 21 Jul 2000 13:57:08 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Jul 2000 17:12:41 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > At least for myself and several others who had this problem: > > you will never get to the install setup up if your system already has a > BSD (Tru64/NetBSD/Linux (using BSD disk label) and from Matt's example, a > FreeBSD disk with the /sbin/init clobbered) or OpenVMS system disk. Hang on; this doesn't make sense. Does Matt's comment imply that if you boot an Alpha setup instance over a FreeBSD system with an *intact* /sbin/init, things work? I've tested _that_, and it certainly works fine here. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 17: 4:54 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 3E32837C14E for ; Fri, 21 Jul 2000 17:04:53 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id RAA01963; Fri, 21 Jul 2000 17:14:19 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007220014.RAA01963@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: mjacob@feral.com Cc: alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-reply-to: Your message of "Fri, 21 Jul 2000 14:01:05 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Jul 2000 17:14:19 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > The presumption here is that sysinstall is mounting the wrong disk. This has > nothing to do with preservation of old data. sysinstall doesn't mount any disks. > On isaac.nas.nasa.gov, putting boot.flp on the *second* disk, I ran into the > 'going nowhere w/o my init' problem as soon as I selected a terminal type. > NetBSD was installed on the first && third disks. Er, if you have been prompted for a terminal type, sysinstall is *already*running*, and it has probably exited. Can you be MORE SPECIFIC about your errors messages? > All of this has been reported in email, fairly clearly. I haven't seen the specific data that I asked for. I'm not convinced this problem is what you think it is. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 17:11: 2 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 4476037C320 for ; Fri, 21 Jul 2000 17:11:00 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id RAA02009; Fri, 21 Jul 2000 17:20:23 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007220020.RAA02009@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Michael Jung Cc: freebsd-alpha@freebsd.org Subject: Re: Booting from Raid In-reply-to: Your message of "Fri, 21 Jul 2000 18:09:52 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Jul 2000 17:20:23 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Ok I admit I've probably not looked hard enough > but it seems that I read recently that you should > be able to boot from DAC960 PCI raid partitions > under FreeBSD-Alpha... > > Shortly before I left work today we started to > load the rc2 iso on a 2100 and it did not > recognize the raid partition.. Can you provide some more details? The output of "show conf" relevant to this card would be a start, as well as the FreeBSD kernel probe messages. You may also have to load the 'mlx' module (this requires booting from floppies, irritatingly) since I get the sneaking suspicion it's not in the GENERIC kernel for Alpha systems. Space in that kernel is *really* tight. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 17:24:54 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1E22137C507; Fri, 21 Jul 2000 17:22:04 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id RAA15311; Fri, 21 Jul 2000 17:22:00 -0700 Date: Fri, 21 Jul 2000 17:21:38 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: wilko@FreeBSD.ORG Cc: FreeBSD-alpha mailing list Subject: Re: U: Request for testers of "going nowhere without my init" In-Reply-To: <20000722004009.A22692@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > **please** take the time to pull the 4.1-RC from ftp.freebsd.org > and test it on the hardware that gave you the "going nowhere without my > init" problem. > > And report back.. Complete report: I installed on a 4100's 4th scsi disk by: + dd'ing boot.flp onto the third disk (from NetBSD running on the first disk) + installing to the 4th disk via ftp. I created one root partition and a swap partition on that device. + installing thru ftp firewall to the specific URL ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha + By selecting something other than 'all' (I think I selected 'developer' for the source sets). Things went well until halfway throught profiled libs, when I guess the ftp session borked (no way to get information from a serial install) and I had to restart it. Other than not being able to set nis client info (which is a generic problem) I was left with a usable and bootable system. At least based on this, we can say that 4100s *do* actually install. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 20:37:22 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 8DA8137B80C; Fri, 21 Jul 2000 20:37:18 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id XAA14399; Fri, 21 Jul 2000 23:37:16 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id XAA53563; Fri, 21 Jul 2000 23:37:15 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 21 Jul 2000 23:37:15 -0400 (EDT) To: Mike Smith Cc: mjacob@feral.com, alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-Reply-To: <200007220014.RAA01963@mass.osd.bsdi.com> References: <200007220014.RAA01963@mass.osd.bsdi.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14713.5018.240866.520423@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith writes: > > Er, if you have been prompted for a terminal type, sysinstall is > *already*running*, and it has probably exited. Can you be MORE SPECIFIC > about your errors messages? Did you look at the boot log that Matt posted last week? I've uploaded it to Freefall & left it in ~gallatin/going_nowhere in case you misplaced it. To sum up, sysinstall complains bitterly about the existing state of the disk labels, then dies. Here's the tail end: da4s4: slice starts beyond end of the disk: rejecting it da1: raw partition size != slice size da1: start 0, end 8380079, size 8380080 da1c: start 0, end 4294967295, size 0 da1: raw partition size != slice size da1: start 0, end 8380079, size 8380080 da1c: start 0, end 4294967295, size 0 init died (signal 0, exit 1) panic: Going nowhere without my init! syncing disks... done Uptime: 1m1s Automatic reboot in 15 seconds - press a key on the console to abort --> Press a key on the console to reboot <-- Rebooting... I think this may be a transient bug in sysinstall, and may not actually be in the loader/bootstrap at all. For what its worth, the sysinstall ran just fine on my AS500, which was configured as da0: linux/alpha (BSD label, SRM bootable, elf /sbin/init) da1: dd'ed ISO RC2 image da2: (unknown; haven't looked at that disk) Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 22:56:50 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 064AA37BA14 for ; Fri, 21 Jul 2000 22:56:39 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id XAA03737; Fri, 21 Jul 2000 23:06:07 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007220606.XAA03737@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andrew Gallatin Cc: alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-reply-to: Your message of "Fri, 21 Jul 2000 23:37:15 EDT." <14713.5018.240866.520423@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Jul 2000 23:06:07 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Did you look at the boot log that Matt posted last week? I've > uploaded it to Freefall & left it in ~gallatin/going_nowhere in case > you misplaced it. > > To sum up, sysinstall complains bitterly about the existing state of > the disk labels, then dies. Here's the tail end: > > > da4s4: slice starts beyond end of the disk: rejecting it > da1: raw partition size != slice size > da1: start 0, end 8380079, size 8380080 > da1c: start 0, end 4294967295, size 0 > da1: raw partition size != slice size > da1: start 0, end 8380079, size 8380080 > da1c: start 0, end 4294967295, size 0 These are all messages from the kernel, not sysinstall unfortunately. > init died (signal 0, exit 1) > panic: Going nowhere without my init! There are a few places where sysinstall might exit(1), but they almost all print something, and none of them are applicable here. Libdisk uses err(1,...) a lot, but again that should have printed something to stderr. Unless stderr has been redirected at this point. An easy test would be to replace all the err(1,...) in libdisk with something else. > I think this may be a transient bug in sysinstall, and may not > actually be in the loader/bootstrap at all. From the output you reference: Mounting root from ufs:/dev/md0c ... /stand/sysinstall running as init on serial console the loader has nothing to do with this. I suspect libdisk, but it's going to be difficult to track down without finding stderr. If someone has a) a prebuilt release area and b) a machine with a disk config that can reproduce this (again, Matt, I don't have anything like this and a remote setup won't do the trick), we can try to track it down... -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jul 21 23:25: 8 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from front7m.grolier.fr (front7m.grolier.fr [195.36.216.57]) by hub.freebsd.org (Postfix) with ESMTP id F002137BAAE; Fri, 21 Jul 2000 23:24:50 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from nas1-54.cgy.club-internet.fr (nas1-54.cgy.club-internet.fr [195.36.197.54]) by front7m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id IAA22725; Sat, 22 Jul 2000 08:24:41 +0200 (MET DST) Date: Sat, 22 Jul 2000 08:04:24 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Mike Smith Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE In-Reply-To: <200007220002.RAA01857@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 21 Jul 2000, Mike Smith wrote: > > On Thu, 20 Jul 2000, Mike Smith wrote: > >=20 > > > > It is my opinion. You may disagree but it will hard for anybody to > > > > convince me that I am wrong. ;-) > > >=20 > > > On x86, it's very hard for you to be right; the CPU specification and= bus > > > bridge behaviour both guarantee retirement of writes in order of issu= ance. > > > This combined with strong cache coherency makes barriers irrelevant o= n > > > this platform. > >=20 > > Let a PCI device perform: > > =09STORE A > > =09STORE B > >=20 > > Let the CPU perform and expect: > > LOAD B > > LOAD A > >=20 > > Let some CPU speculative execution carry out to the system BUS: > > =09LOAD A > > =09LOAD B > >=20 > > My reading of the the Intel docs didn't convince me that such reorderin= g > > is not possible. > > =20 > > Typically A is some indicator of an IO completion pushed to a completio= n=20 > > queue and B is the associated status data. >=20 > You've got those the wrong way around; A will be the status, and B the=20 > indicator (since we have to assume the peripheral is correctly designed). Yes. It has been a typo from me, obviously. Just FYI, the SYM and the AIC7XXX should not get the LOADs reordered, in my opinion, since B (item extracted from the completion queue) is used as an index (or tag) to retrieve the IO data-structure and then the status data (A). An operand of the second LOAD depending on the first one insures no reordering will occur. Anyway, I have put the MB in the SYM for safety against any other weirdness I may have missed. :-) This is different in the NCR, that uses the host_status field of the nccb as completion flag, but tests against the xerr_status flag of the nccb for extended errors. Since these 2 informations are not written together atomically, the NCR falls into the above model, on paper. Just, the 2 LOADs are probably not close enough in the instruction stream for bad reordering to ever happen. > I don't believe that the x86 re-orders read operations (but I don't have= =20 > the P6 architecture manuals here to be certain). If it does, then to=20 > remain compatible with older x86 processors, it would have to invalidate= =20 > the pipeline and re-fetch when the bus snoop code detected the STORE B. >=20 > > > As far as other platforms are concerned, however, you're quite correc= t. > >=20 > > Are you still so sure. ;-) >=20 > Yes. x86 has so much seralised legacy baggage that it's a special case. = =20 You shouldn't, IMO, for Pi, i >=3D II, and some clones. :) > Everyone else needs help. 8) I probably fall into this category too. :) > > > There does need to be an extension to the busspace API to define a ra= nge=20 > > > of host memory with a tag/handle pair for barrier activity. > >=20 > > Hmmm... Barrier semantics vary so much between architectures that an > > unified semantic that also address device driver's concerns (not only > > CPU<->CPU) is either close to impossible or will just be extremally poo= r, > > in my opinion. >=20 > I'm open to edification here, but I think that the ability to define the= =20 > sort of barrier operation required for a memory region and to then=20 > invoke said barrier is about the best we can hope for. This looks to me the best complex and poor possible semantic. :) > > The drivers I maintain will always contain any stuff needed for them to= be > > as correct as I want them to be, modulo my knowledge and competence on > > addressed platforms obviously. >=20 > I don't think anyone could ask for any more than that. Thanks for the reply. Regards, G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Jul 22 1:20:17 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 0C16937B69C for ; Sat, 22 Jul 2000 01:20:08 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13FuVw-0007Ke-00; Sat, 22 Jul 2000 08:20:04 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id KAA27099; Sat, 22 Jul 2000 10:10:23 +0200 (CEST) (envelope-from wkb) Date: Sat, 22 Jul 2000 10:10:23 +0200 From: Wilko Bulte To: Matthew Jacob Cc: alpha@freebsd.org Subject: Re: so, what does BOOTMFS install kernel need a parallel port for? Message-ID: <20000722101023.A26964@freebie.demon.nl> Reply-To: wilko@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Fri, Jul 21, 2000 at 04:18:45PM -0700 X-OS: FreeBSD 4.1-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jul 21, 2000 at 04:18:45PM -0700, Matthew Jacob wrote: > > If we're concerned with size on floppies, what is > > ppc0: at port 0x3bc-0x3c3 irq 7 on isa0 > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > plip0: cannot reserve interrupt, failed. > ppc0: interrupting at ISA irq 7 > > this doing in the install kernel? I guess the idea is to allow PLIP installs. But I agree we could loose it in favor of something more useful. -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Jul 22 1:20:17 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 31AC437B882; Sat, 22 Jul 2000 01:20:11 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13FuVx-0007Ke-00; Sat, 22 Jul 2000 08:20:05 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id KAA27161; Sat, 22 Jul 2000 10:16:34 +0200 (CEST) (envelope-from wkb) Date: Sat, 22 Jul 2000 10:16:34 +0200 From: Wilko Bulte To: Matthew Jacob Cc: wilko@freebsd.org, FreeBSD-alpha mailing list Subject: Re: U: Request for testers of "going nowhere without my init" Message-ID: <20000722101634.B26964@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <20000722004009.A22692@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Fri, Jul 21, 2000 at 05:21:38PM -0700 X-OS: FreeBSD 4.1-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jul 21, 2000 at 05:21:38PM -0700, Matthew Jacob wrote: > Complete report: > > I installed on a 4100's 4th scsi disk by: > > + dd'ing boot.flp onto the third disk (from NetBSD running on the > first disk) I deduct booting the floppies directly would not work? > + installing to the 4th disk via ftp. I created one root partition and a swap > partition on that device. > > + installing thru ftp firewall to the specific URL > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha > > + By selecting something other than 'all' (I think I selected 'developer' for > the source sets). > > Things went well until halfway throught profiled libs, when I guess the ftp > session borked (no way to get information from a serial install) and I had to > restart it. Other than not being able to set nis client info (which is a > generic problem) I was left with a usable and bootable system. > > At least based on this, we can say that 4100s *do* actually install. I could list this as a workaround in RELNOTES.. what do people think? -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Jul 22 1:33:20 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E0B5737B71B; Sat, 22 Jul 2000 01:33:16 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id BAA16627; Sat, 22 Jul 2000 01:33:15 -0700 Date: Sat, 22 Jul 2000 01:33:18 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: wilko@freebsd.org Cc: FreeBSD-alpha mailing list Subject: Re: U: Request for testers of "going nowhere without my init" In-Reply-To: <20000722101634.B26964@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 22 Jul 2000, Wilko Bulte wrote: > On Fri, Jul 21, 2000 at 05:21:38PM -0700, Matthew Jacob wrote: > > > Complete report: > > > > I installed on a 4100's 4th scsi disk by: > > > > + dd'ing boot.flp onto the third disk (from NetBSD running on the > > first disk) > > I deduct booting the floppies directly would not work? No, not for me, David, or for you I believe. > > > + installing to the 4th disk via ftp. I created one root partition and a swap > > partition on that device. > > > > + installing thru ftp firewall to the specific URL > > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha > > > > + By selecting something other than 'all' (I think I selected 'developer' for > > the source sets). > > > > Things went well until halfway throught profiled libs, when I guess the ftp > > session borked (no way to get information from a serial install) and I had to > > restart it. Other than not being able to set nis client info (which is a > > generic problem) I was left with a usable and bootable system. > > > > At least based on this, we can say that 4100s *do* actually install. > > I could list this as a workaround in RELNOTES.. what do people think? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Jul 22 2:40:56 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id CF41C37B6AB for ; Sat, 22 Jul 2000 02:40:53 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13Fvm8-0000Db-00 for freebsd-alpha@freebsd.org; Sat, 22 Jul 2000 09:40:52 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id KAA27280 for freebsd-alpha@freebsd.org; Sat, 22 Jul 2000 10:26:09 +0200 (CEST) (envelope-from wkb) Date: Sat, 22 Jul 2000 10:26:09 +0200 From: Wilko Bulte To: FreeBSD-alpha mailing list Subject: RFC: contents of alpha/RELNOTES Message-ID: <20000722102609.C26964@freebie.demon.nl> Reply-To: wilko@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-OS: FreeBSD 4.1-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org When looking at the alpha release notes (RELNOTES.TXT) I see an awful lot of adapters/hardware listed as 'supported' which I'm pretty sure have never seen the inside of any alpha box. Things like the ISA SCSI controllers, proprietary CDROM interfaces etc is what I mean. Any reason not to axe those? -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Jul 22 8:21:28 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id A6FE037C259 for ; Sat, 22 Jul 2000 08:21:25 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA20083; Sat, 22 Jul 2000 11:21:21 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id LAA57725; Sat, 22 Jul 2000 11:21:21 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 22 Jul 2000 11:21:21 -0400 (EDT) To: mjacob@feral.com Cc: alpha@FreeBSD.ORG Subject: Re: so, what does BOOTMFS install kernel need a parallel port for? In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14713.48085.400102.618441@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > > If we're concerned with size on floppies, what is > > ppc0: at port 0x3bc-0x3c3 irq 7 on isa0 > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > plip0: cannot reserve interrupt, failed. > ppc0: interrupting at ISA irq 7 > > this doing in the install kernel? Seconded.. Let's replace it with something more useful, like the Mylex driver.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Jul 22 12:20:27 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id EB65337BAA3 for ; Sat, 22 Jul 2000 12:20:22 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id MAA29095 for ; Sat, 22 Jul 2000 12:20:21 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 22 Jul 2000 12:20:21 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: alpha@freebsd.org Subject: Question about alpha bootstrap Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From looking at the Alpha boot1 code, it seems that the bootstrap expects there to be a filesystem which starts at the beginning of the disk, and it finds "/boot/loader" (or whatever filename you type in) there. So, for example, it wouldn't work to put a swap partition first on the disk. Is that right? John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Jul 22 13:11:48 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id EAAD737BB14 for ; Sat, 22 Jul 2000 13:11:45 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id NAA10033; Sat, 22 Jul 2000 13:21:07 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007222021.NAA10033@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Polstra Cc: alpha@freebsd.org Subject: Re: Question about alpha bootstrap In-reply-to: Your message of "Sat, 22 Jul 2000 12:20:21 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 22 Jul 2000 13:21:07 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >From looking at the Alpha boot1 code, it seems that the bootstrap > expects there to be a filesystem which starts at the beginning of the > disk, and it finds "/boot/loader" (or whatever filename you type in) > there. So, for example, it wouldn't work to put a swap partition > first on the disk. > > Is that right? That's correct. If you want maximum swap performance, you want swap on the outside of the disk. This typically means working out whether your disk counts inside-out or outside-in, and organising accordingly. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Jul 22 13:16:56 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id ED6E537BAEB for ; Sat, 22 Jul 2000 13:16:51 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA45346; Sat, 22 Jul 2000 13:16:49 -0700 (PDT) (envelope-from obrien) Date: Sat, 22 Jul 2000 13:16:49 -0700 From: "David O'Brien" To: Matthew Jacob Cc: alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 Message-ID: <20000722131648.E44856@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <14712.41758.459790.390526@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Fri, Jul 21, 2000 at 12:30:00PM -0700 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 X-Loop: FreeBSD.org On Fri, Jul 21, 2000 at 12:30:00PM -0700, Matthew Jacob wrote: > I think you need to put into RELNOTES that Alpha 4100 isn't supported. More testing. Using the CDROM that boots fine on my Miata(MX5) on the 4100, I find that the CDROM isn't accessable from the loader. Even doing an ``ls'' from the loader hangs. Note that this has always worked on my Miata (even with the current /boot/cdboot rather than the 4.0-R one). This behavior seems the same with floppies. So for some reason the loader is unable to access any of our bits from the installation media [in the non-harddisk case]. P00>>>boot dka500 Initializing... SROM V2.0 on cpu0 SROM V2.0 on cpu1 XSROM V5.3 on cpu0 XSROM V5.3 on cpu1 BCache testing complete on cpu0 BCache testing complete on cpu1 mem_pair0 - 512 MB 20..20..21..21..23.. please wait 12 seconds for T24 to complete 24..24.. Memory testing complete on cpu1 Memory testing complete on cpu0 starting console on CPU 0 sizing memory 0 512 MB EDO starting console on CPU 1 probing IOD1 hose 1 bus 0 slot 1 - NCR 53C810 bus 0 slot 2 - DECchip 21140-AA probing IOD0 hose 0 bus 0 slot 1 - PCEB probing EISA Bridge, bus 1 bus 0 slot 2 - S3 Trio64/Trio32 bus 0 slot 4 - PCI-PCI Bridge probing PCI-PCI Bridge, bus 2 bus 2 slot 0 - QLogic ISP1020 ** keyboard error ** configuring I/O adapters... ncr0, hose 1, bus 0, slot 1 tulip0, hose 1, bus 0, slot 2 floppy0, hose 0, bus 1, slot 0 isp0, hose 0, bus 2, slot 0 System temperature is 30 degrees C AlphaServer 4100 Console V5.3-1, 27-OCT-1998 11:16:38 CPU 0 booting (boot dka500.5.0.1.1) block 0 of dka500.5.0.1.1 is a valid boot block reading 356 blocks from dka500.5.0.1.1 bootstrap code read in Building FRU table base = 200000, image_start = 0, image_bytes = 2c800 initializing HWRPB at 2000 initializing page table at 1f2000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code Console: SRM firmware console VMS PAL rev: 0x4001200010113 OSF PAL rev: 0x4001a00020115 Switch to OSF PAL code succeeded. FreeBSD/alpha SRM CD9660 boot, Revision 0.1 (jkh@beast.freebsd.org, Mon Mar 20 21:08:56 GMT 2000) Memory: 524288 k > echo \007\007 > autoboot 10 Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel] in 6 seconds... Type '?' for a list of commands, 'help' for more detailed help. ok ls -l failed to send Read to dka500.5.0.1.1 halt code = 7 pcb 0 !!! Console entry context is not valid - Reset the system !!! Brk 0 at 0006621C 0006621C ! BPT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Jul 22 13:45:59 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2C72D37BAEE; Sat, 22 Jul 2000 13:45:58 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA18639; Sat, 22 Jul 2000 13:45:57 -0700 Date: Sat, 22 Jul 2000 13:45:59 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-Reply-To: <20000722131648.E44856@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org sounds like an SRM issue. You're running a really old SRM (v5.3). Can you upgrade to v5.7 (latest)? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Jul 22 15:29:33 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 9005437B52A; Sat, 22 Jul 2000 15:29:30 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13G7lx-000E7T-00; Sat, 22 Jul 2000 22:29:29 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id AAA01098; Sun, 23 Jul 2000 00:23:45 +0200 (CEST) (envelope-from wkb) Date: Sun, 23 Jul 2000 00:23:45 +0200 From: Wilko Bulte To: Matthew Jacob Cc: "David O'Brien" , alpha@freebsd.org Subject: Re: 4.1-20000719-RC#2 Message-ID: <20000723002345.A1060@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <20000722131648.E44856@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Sat, Jul 22, 2000 at 01:45:59PM -0700 X-OS: FreeBSD 4.1-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Jul 22, 2000 at 01:45:59PM -0700, Matthew Jacob wrote: > sounds like an SRM issue. You're running a really old SRM (v5.3). Can you > upgrade to v5.7 (latest)? At least you want to try something later than: Digital Equipment Corporation AlphaServer 4X00 Console V5.5-5 OpenVMS PALcode V1.21-2, Digital UNIX PALcode V1.23-2 (if it exists). V5.5.-5 is what I used and did not work last week. -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Jul 22 16:21: 8 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from wa4phy.dyndns.org (cc449817-a.mrtnz1.ga.home.com [24.12.79.51]) by hub.freebsd.org (Postfix) with ESMTP id 10F1637B7F5 for ; Sat, 22 Jul 2000 16:20:58 -0700 (PDT) (envelope-from sam@wa4phy.dyndns.org) Received: from wa4phy.dyndns.org (sam@localhost [127.0.0.1]) by wa4phy.dyndns.org (8.9.3/8.9.3) with ESMTP id TAA13662 for ; Sat, 22 Jul 2000 19:20:55 -0400 (EDT) (envelope-from sam@wa4phy.dyndns.org) Message-ID: <397A2C57.F2734D26@wa4phy.dyndns.org> Date: Sat, 22 Jul 2000 19:20:55 -0400 From: "S.W. Drinkard" Organization: You Gotta Be Kiddin! X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en, ja MIME-Version: 1.0 To: freebsd-alpha@freebsd.org Subject: ftp bits Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Um, tried to grab the ftp install bits earlier this pm, and got nothing.. Which server should I be using? Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Jul 22 19:19:33 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from wa4phy.dyndns.org (cc449817-a.mrtnz1.ga.home.com [24.12.79.51]) by hub.freebsd.org (Postfix) with ESMTP id 0119237B83F; Sat, 22 Jul 2000 19:19:30 -0700 (PDT) (envelope-from sam@wa4phy.dyndns.org) Received: from wa4phy.dyndns.org (sam@localhost [127.0.0.1]) by wa4phy.dyndns.org (8.9.3/8.9.3) with ESMTP id WAA13984; Sat, 22 Jul 2000 22:19:23 -0400 (EDT) (envelope-from sam@wa4phy.dyndns.org) Message-ID: <397A562B.7E43B7F2@wa4phy.dyndns.org> Date: Sat, 22 Jul 2000 22:19:23 -0400 From: "S.W. Drinkard" Organization: You Gotta Be Kiddin! X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en, ja MIME-Version: 1.0 To: mikej@charon.npc.net, msmith@freebsd.org Cc: freebsd-alpha@freebsd.org Subject: Re: Booting from Raid Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I shouldn't even mention anything, but I have a problem after booting from floppies that only the first drive is available to install on. Looking at the debug output (don't have serial capabilities, (yet) ) it appears that a search is being done for a valid partition on all other disks. This machine also has the DAC 960 raid controller. Machine currently has NT on it. Will try to get some type of console output for verification. Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Jul 22 22:21:12 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id D674E37B781; Sat, 22 Jul 2000 22:21:09 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id WAA00625; Sat, 22 Jul 2000 22:21:08 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id WAA99377; Sat, 22 Jul 2000 22:21:08 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sat, 22 Jul 2000 22:21:08 -0700 (PDT) Message-Id: <200007230521.WAA99377@vashon.polstra.com> To: msmith@freebsd.org Subject: Re: Question about alpha bootstrap In-Reply-To: <200007222021.NAA10033@mass.osd.bsdi.com> References: <200007222021.NAA10033@mass.osd.bsdi.com> Organization: Polstra & Co., Seattle, WA Cc: alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <200007222021.NAA10033@mass.osd.bsdi.com>, Mike Smith wrote: [boot1 looks for /boot/loader on filesystem at beginning of disk, right?] > That's correct. > > If you want maximum swap performance, you want swap on the outside of the > disk. This typically means working out whether your disk counts > inside-out or outside-in, and organising accordingly. Thanks. My situation actually isn't related to swap. I have a somewhat stale dual-boot setup where I can get -stable by booting da0a or -current by booting da0f. But this means I'm using -stable's /boot/loader in both cases. It hasn't been a problem in the past, but I suppose it could be one some day. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message