From owner-freebsd-alpha Sun Sep 17 3:20:34 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 450B337B422; Sun, 17 Sep 2000 03:20:27 -0700 (PDT) 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 e8HAK5Q11678 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Sun, 17 Sep 2000 12:20:16 +0200 (MET DST) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0::104:200:92ff:fe9b:20e7]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e8HAK8I92606; Sun, 17 Sep 2000 12:20:10 +0200 (CEST) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.0/8.9.2) id e8HAK8267920; Sun, 17 Sep 2000 12:20:08 +0200 (CEST) (envelope-from ticso) Date: Sun, 17 Sep 2000 12:20:08 +0200 From: Bernd Walter To: Doug Rabson Cc: John Baldwin , alpha@FreeBSD.org, smp@FreeBSD.org Subject: Re: Prelimiary interrupt thread patches for alpha Message-ID: <20000917122007.A67895@cicely5.cicely.de> References: <20000915075812.B60348@cicely5.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from dfr@nlsystems.com on Sat, Sep 16, 2000 at 01:25:36PM +0100 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Sep 16, 2000 at 01:25:36PM +0100, Doug Rabson wrote: > The patch should work on all except AS4100 and AS8200. I would like to get > some testing on tsunami, apecs and lca based machines for a sanity check > but it ought to work (crossed fingers). -current won't work on AXPpci systems even without any patch: 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 5.0-CURRENT #1: Sun Sep 17 12:02:20 CEST 2000 ticso@cicely9.cicely.de:/var/d7/src-2000-09-17/src/sys/compile/CICELY10 DEC AXPpci Alpha PC AXPpci33, 167MHz 8192 byte page size, 1 processor. CPU: LCA Family major=4 minor=2 OSF PAL rev: 0x100090002012d real memory = 132145152 (129048K bytes) avail memory = 122486784 (119616K bytes) Preloaded elf kernel "kernel" at 0xfffffc0000650000. lca0: <21066 Core Logic chipset> fatal kernel trap: trap entry = 0x2 (memory management fault) a0 = 0xfffffbf1e0000018 a1 = 0x1 a2 = 0x0 pc = 0xfffffc000050e3b0 ra = 0xfffffc000050e2bc curproc = 0xfffffc00005de3f0 pid = 0, comm = swapper Stopped at badaddr_read+0xd0: ldl t0,0(a0) <0xfffffbf1e0000018> db> trace badaddr_read() at badaddr_read+0xd0 badaddr() at badaddr+0x1c lca_pcib_read_config() at lca_pcib_read_config+0x34c pci_read_device() at pci_read_device+0xb0 pci_add_children() at pci_add_children+0xe4 pci_probe() at pci_probe+0x17c device_probe_child() at device_probe_child+0x13c device_probe_and_attach() at device_probe_and_attach+0x54 bus_generic_attach() at bus_generic_attach+0x28 device_probe_and_attach() at device_probe_and_attach+0xcc bus_generic_attach() at bus_generic_attach+0x28 lca_attach() at lca_attach+0xa0 device_probe_and_attach() at device_probe_and_attach+0xcc root_bus_configure() at root_bus_configure+0x38 configure() at configure+0x40 mi_startup() at mi_startup+0xf4 locorestart() at locorestart+0x6c -- 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 Sep 17 6:31:37 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by hub.freebsd.org (Postfix) with ESMTP id 9869F37B423; Sun, 17 Sep 2000 06:31:33 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-34.mail.demon.net with esmtp (Exim 2.12 #1) id 13aeXY-000DDd-0Y; Sun, 17 Sep 2000 14:31:31 +0100 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 OAA33687; Sun, 17 Sep 2000 14:33:51 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 17 Sep 2000 14:31:49 +0100 (BST) From: Doug Rabson To: Matthew Jacob Cc: Bernd Walter , John Baldwin , alpha@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: Prelimiary interrupt thread patches for alpha 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 Sat, 16 Sep 2000, Matthew Jacob wrote: > > I can look at Rawhide and TurboLaser next week when my temperature comes down > (flu). Doug- you have a rawhide. I have the turbolaseers. Why don't y'all > check the patch in so we have something same to work with? I'm looking at rawhide right now, so hopefully the patch should contain support for that when its committed. We can leave turbolaser for you then. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 20 8348 3944 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Sep 17 7:18:59 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 8DE9937B422; Sun, 17 Sep 2000 07:18:55 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13afHR-0005kK-00; Sun, 17 Sep 2000 14:18:53 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e8HEK6I49677; Sun, 17 Sep 2000 16:20:06 +0200 (CEST) (envelope-from wkb) Date: Sun, 17 Sep 2000 16:20:06 +0200 From: Wilko Bulte To: Doug Rabson Cc: Matthew Jacob , Bernd Walter , John Baldwin , alpha@freebsd.org, smp@freebsd.org Subject: Re: Prelimiary interrupt thread patches for alpha Message-ID: <20000917162006.B49643@freebie.demon.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from dfr@nlsystems.com on Sun, Sep 17, 2000 at 02:31:49PM +0100 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Sep 17, 2000 at 02:31:49PM +0100, Doug Rabson wrote: > On Sat, 16 Sep 2000, Matthew Jacob wrote: > > > > > I can look at Rawhide and TurboLaser next week when my temperature comes down > > (flu). Doug- you have a rawhide. I have the turbolaseers. Why don't y'all > > check the patch in so we have something same to work with? > > I'm looking at rawhide right now, so hopefully the patch should contain > support for that when its committed. We can leave turbolaser for you then. Does this imply 'loader' is working again or am I reading something that is not implied? -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Sep 17 8:12: 2 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by hub.freebsd.org (Postfix) with ESMTP id CA89337B422; Sun, 17 Sep 2000 08:11:58 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-34.mail.demon.net with esmtp (Exim 2.12 #1) id 13ag6l-000K24-0Y; Sun, 17 Sep 2000 16:11:56 +0100 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 QAA34226; Sun, 17 Sep 2000 16:13:56 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 17 Sep 2000 16:11:52 +0100 (BST) From: Doug Rabson To: Wilko Bulte Cc: Matthew Jacob , Bernd Walter , John Baldwin , alpha@freebsd.org, smp@freebsd.org Subject: Re: Prelimiary interrupt thread patches for alpha In-Reply-To: <20000917162006.B49643@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 Sun, 17 Sep 2000, Wilko Bulte wrote: > On Sun, Sep 17, 2000 at 02:31:49PM +0100, Doug Rabson wrote: > > On Sat, 16 Sep 2000, Matthew Jacob wrote: > > > > > > > > I can look at Rawhide and TurboLaser next week when my temperature comes down > > > (flu). Doug- you have a rawhide. I have the turbolaseers. Why don't y'all > > > check the patch in so we have something same to work with? > > > > I'm looking at rawhide right now, so hopefully the patch should contain > > support for that when its committed. We can leave turbolaser for you then. > > Does this imply 'loader' is working again or am I reading something that is > not implied? I'm not looking at loader at all right now. I'm netbooting all my test machines and netboot isn't affected by the loader size problems. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 20 8348 3944 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Sep 17 8:43: 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 C578337B42C; Sun, 17 Sep 2000 08:42:58 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13agan-000HZZ-00; Sun, 17 Sep 2000 15:42:58 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e8HFiB950228; Sun, 17 Sep 2000 17:44:11 +0200 (CEST) (envelope-from wkb) Date: Sun, 17 Sep 2000 17:44:11 +0200 From: Wilko Bulte To: Doug Rabson Cc: Matthew Jacob , Bernd Walter , John Baldwin , alpha@freebsd.org, smp@freebsd.org Subject: Re: Prelimiary interrupt thread patches for alpha Message-ID: <20000917174411.A50193@freebie.demon.nl> References: <20000917162006.B49643@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 dfr@nlsystems.com on Sun, Sep 17, 2000 at 04:11:52PM +0100 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Sep 17, 2000 at 04:11:52PM +0100, Doug Rabson wrote: > On Sun, 17 Sep 2000, Wilko Bulte wrote: > > > On Sun, Sep 17, 2000 at 02:31:49PM +0100, Doug Rabson wrote: > > > On Sat, 16 Sep 2000, Matthew Jacob wrote: > > > I'm looking at rawhide right now, so hopefully the patch should contain > > > support for that when its committed. We can leave turbolaser for you then. > > > > Does this imply 'loader' is working again or am I reading something that is > > not implied? > > I'm not looking at loader at all right now. I'm netbooting all my test > machines and netboot isn't affected by the loader size problems. OK, clear. Thanks -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Sep 17 14:25: 3 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 B413437B422; Sun, 17 Sep 2000 14:25:01 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA04985; Sun, 17 Sep 2000 14:25:00 -0700 Date: Sun, 17 Sep 2000 14:25:00 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: cvs@freebsd.org Cc: alpha@freebsd.org Subject: tag movement requested 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 May I request that the tag for PRE_SMPNG in src/sys/alpha/pci/cia.c be moved from rev 1.27 to 1.28? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Sep 17 15:58:39 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 824F937B422; Sun, 17 Sep 2000 15:58:37 -0700 (PDT) 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 PAA27730; Sun, 17 Sep 2000 15:58:34 -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 In-Reply-To: Date: Sun, 17 Sep 2000 15:58:34 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Matthew Jacob Subject: RE: tag movement requested Cc: alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob wrote: > > May I request that the tag for PRE_SMPNG in > > src/sys/alpha/pci/cia.c > > be moved from rev 1.27 to 1.28? Done. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Sep 17 16:58:13 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 9D62737B423 for ; Sun, 17 Sep 2000 16:58:09 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA05382; Sun, 17 Sep 2000 16:58:03 -0700 Date: Sun, 17 Sep 2000 16:58:03 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Polstra Cc: alpha@freebsd.org Subject: RE: tag movement requested 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 Molto Grazie! On Sun, 17 Sep 2000, John Polstra wrote: > Matthew Jacob wrote: > > > > May I request that the tag for PRE_SMPNG in > > > > src/sys/alpha/pci/cia.c > > > > be moved from rev 1.27 to 1.28? > > Done. > > John > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Sep 17 17:35:48 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 DFC8E37B422 for ; Sun, 17 Sep 2000 17:35:45 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id RAA05461 for ; Sun, 17 Sep 2000 17:35:45 -0700 Date: Sun, 17 Sep 2000 17:35:45 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: alpha@FreeBSD.ORG Subject: looks like RELENG_4/stable buildworld is broken 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 sr/src/sys/boot/alpha/netboot/../../.. -I. -DPRIMARY_LOAD_ADDRESS=0x20000000 -DSECONDARY_LOAD_ADDRESS=0x2000c000 -Wall -I/usr/src/sys/boot/alpha/netboot/../../../../lib/libstand -I/usr/src/sys/boot/alpha/netboot/.. -I/usr/obj/usr/src/alpha/usr/include -c /usr/src/sys/boot/alpha/netboot/../../common/dev_net.c /usr/src/sys/boot/alpha/netboot/../../common/dev_net.c:200: conflicting types for `bootp' /usr/src/sys/boot/alpha/netboot/../../../../lib/libstand/net.h:117: previous declaration of `bootp' /usr/src/sys/boot/alpha/netboot/../../common/dev_net.c: In function `net_getparams': /usr/src/sys/boot/alpha/netboot/../../common/dev_net.c:222: too many arguments to function `bootp' *** Error code 1 Stop in /usr/src/sys/boot/alpha/netboot. *** Error code 1 Stop in /usr/src/sys/boot/alpha. *** Error code 1 Stop in /usr/src/sys/boot. *** Error code 1 Stop in /usr/src/sys. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Sep 17 18:17: 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 27D5737B424 for ; Sun, 17 Sep 2000 18:17:04 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id SAA05650; Sun, 17 Sep 2000 18:16:56 -0700 Date: Sun, 17 Sep 2000 18:16:55 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Peter Wemm Cc: "Daniel C. Sobral" , alpha@FreeBSD.ORG Subject: Re: Loader badly broken on the alpha In-Reply-To: <200009160726.e8G7QPG10931@netplex.com.au> 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 > Matthew Jacob wrote: > > > > I think I had determined (I thought) that it was just loader itself, but I > > could be wrong. > > The problem is that the loader is now too large, it cannot fit inside the > ~208K window that boot1 has got available to it. > > peter@ashburton[12:14am]/home/obj/home/src/sys/boot/alpha/loader-130# nm loader.sym | sort | tail -1 > 000000002003e190 A end > > The VM space ends at 2004000. I can't find where, but I was pretty sure that > the last 8K page was already spoken for and we've clobbered it. > > Was the pnp stuff added to the Alpha loader images? That is what probably > tipped it over the edge. I've been looking at this a little bit. The last last 8k may not be entirely spoken for, because previous loader.sym's had: 000000002003d260 A _end 000000002003d260 A end But if it's 8k (and I don't know anything much about this really- I have never delved to much into this portion of alphas) this may explain why the boot stuff never did work right entirely for all models (e.g., off of floppy for a rawhide). In any case, this one is a hard one. I was comparing object sizes between June 23'd loader.sym and the current one on alpha, and there's no one single thing that got all that much bigger! We need to pull out 3408 bytes- but it's not that simple- bcopy seems to take 2544 bytes, which is ridiculously large for a boot block- so I replaced it with a dopey one line C function but that didn't change _end for me, so I have to look at the linker magic some I guess. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Sep 17 18:38:13 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 0820737B424 for ; Sun, 17 Sep 2000 18:38:12 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id SAA05713; Sun, 17 Sep 2000 18:38:04 -0700 Date: Sun, 17 Sep 2000 18:38:04 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Peter Wemm Cc: "Daniel C. Sobral" , alpha@FreeBSD.ORG Subject: If we could just figure this one out.... 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 If you sort objects in the loader by size, this one is always the top sizes.. 0000000000008ba0 T twoConstParen 00000000000021c0 T ficlCompileCore 0000000000002000 B stack 00000000000019c0 t gcc2_compiled. 0000000000001328 D z_errmsg A little sleuthing, though, finds that the object z_errmsg is only 0x50 bytes in size. Hmm -We'd definitely reclaim all the space we needed if we could figure out why there seems to be this padding. Any ideas? This comes out of libstand.a. I'll try linker optimizations to see if this can be shrunk! -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Sep 17 18:46:40 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 DA59D37B422 for ; Sun, 17 Sep 2000 18:46:37 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id SAA05742; Sun, 17 Sep 2000 18:46:28 -0700 Date: Sun, 17 Sep 2000 18:46:28 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Peter Wemm Cc: "Daniel C. Sobral" , alpha@FreeBSD.ORG Subject: oops... 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 Sorry- I was not using the right args to nm..I'll be quiet now until I actually have a fix (if any). On Sun, 17 Sep 2000, Matthew Jacob wrote: > > If you sort objects in the loader by size, this one is always the top sizes.. > > 0000000000008ba0 T twoConstParen > 00000000000021c0 T ficlCompileCore > 0000000000002000 B stack > 00000000000019c0 t gcc2_compiled. > 0000000000001328 D z_errmsg > > A little sleuthing, though, finds that the object z_errmsg is only 0x50 bytes > in size. Hmm -We'd definitely reclaim all the space we needed if we could > figure out why there seems to be this padding. > > Any ideas? This comes out of libstand.a. I'll try linker optimizations to see > if this can be shrunk! > > -matt > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Sep 17 21: 5:41 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from server.baldwin.cx (server.geekhouse.net [64.81.6.52]) by hub.freebsd.org (Postfix) with ESMTP id DC4FE37B422; Sun, 17 Sep 2000 21:05:37 -0700 (PDT) Received: from john.baldwin.cx (root@john.baldwin.cx [192.168.1.18]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id VAA63765; Sun, 17 Sep 2000 21:07:13 -0700 (PDT) (envelope-from john@baldwin.cx) Received: (from john@localhost) by john.baldwin.cx (8.9.3/8.9.3) id VAA03411; Sun, 17 Sep 2000 21:06:49 -0700 (PDT) (envelope-from john) Message-Id: <200009180406.VAA03411@john.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 17 Sep 2000 21:06:49 -0700 (PDT) From: John Baldwin To: alpha@FreeBSD.ORG Subject: Re: Prelimiary interrupt thread patches for alpha Cc: smp@FreeBSD.ORG Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 17-Sep-00 Doug Rabson wrote: > On Sat, 16 Sep 2000, Matthew Jacob wrote: > >> >> I can look at Rawhide and TurboLaser next week when my temperature comes down >> (flu). Doug- you have a rawhide. I have the turbolaseers. Why don't y'all >> check the patch in so we have something same to work with? > > I'm looking at rawhide right now, so hopefully the patch should contain > support for that when its committed. We can leave turbolaser for you then. I've taken some things out of the ithreads patch and updated it again. Basically, I split the KTR changes and kern_shutdown.c changes out as they are unrelated to ithreads. Once this is committed I'll look at doing softinterrupts next. I think I can just rip out the x86 sofinterrupt thread code that we have and make it MI with just a few tweaks.  -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Sep 17 22:35: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 C13BC37B422 for ; Sun, 17 Sep 2000 22:35:33 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id WAA06272; Sun, 17 Sep 2000 22:35:23 -0700 Date: Sun, 17 Sep 2000 22:35:23 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Peter Wemm Cc: "Daniel C. Sobral" , alpha@FreeBSD.ORG Subject: Re: If we could just figure this one out.... 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 It's more complicated than we thought. I did all sorts of dances with changing sizes and shrinking the secondary. Then I installed boot1 as well. Badness. Same problem: (boot dkb100.1.0.4.1 -flags A) block 0 of dkb100.1.0.4.1 is a valid boot block reading 16 blocks from dkb100.1.0.4.1 bootstrap code read in Building FRU table base = 200000, image_start = 0, image_bytes = 2000 initializing HWRPB at 2000 initializing page table at 1f2000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code halted CPU 0 halt code = 2 kernel stack not valid halt PC = 5555555555555554 P00>>FreeBSD>>e -n 30 r0 gpr: 0 ( R0) 0000000000000000 gpr: 1 ( R1) 000000000000F5C8 gpr: 2 ( R2) 5555555555555554 gpr: 3 ( R3) 5555555555555555 gpr: 4 ( R4) 5555555555555554 gpr: 5 ( R5) 0000000000000001 gpr: 6 ( R6) 00000006C6000045 gpr: 7 ( R7) 000000001FF237C3 gpr: 8 ( R8) 0000000000006E80 gpr: 9 ( R9) 0000000000000000 gpr: A ( R10) 0000000000013454 gpr: B ( R11) 000000F9E0002000 gpr: C ( R12) 0000000000000000 gpr: D ( R13) 0000000000000001 gpr: E ( R14) 0000000000113454 gpr: F ( R15) 0000000080000000 gpr: 10 ( R16) 0000000000000000 gpr: 11 ( R17) 0000000000000000 gpr: 12 ( R18) 0000000000000001 gpr: 13 ( R19) 0000000000000400 gpr: 14 ( R20) 0000000000000001 gpr: 15 ( R21) 000000F9E0000780 gpr: 16 ( R22) 0000000000560005 gpr: 17 ( R23) 0000000000004718 gpr: 18 ( R24) 000000F801E00000 gpr: 19 ( R25) 0000000000560005 gpr: 1A ( R26) 0000000020000020 gpr: 1B ( R27) 0000100000000000 gpr: 1C ( R28) 0000000000008000 gpr: 1D ( R29) 0000000020009E18 gpr: 1E ( R30) 0000000020044000 gpr: 1F ( R31) 0000000000000000 Note r26 (ra) (0000000020000020). This puppy is dying darn right away. Like, in bzero called from start. You know- I'm wondering if all of the libc goop pulled in by libstand is at fault here? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Sep 18 1:21:30 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 AB9B437B423; Mon, 18 Sep 2000 01:21:28 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id BAA06585; Mon, 18 Sep 2000 01:21:26 -0700 Date: Mon, 18 Sep 2000 01:21:26 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: alpha@FreeBSD.ORG, Peter Wemm , dcs@FreeBSD.ORG Subject: Re: Loader badly broken on the alpha In-Reply-To: <200009160120.SAA45920@pike.osd.bsdi.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 think I fixed it- 4KB more stack, 256KB more heap, and shoved the secondary load address down 8KB. This fixes this for now. Definitely a candidate for some rework. I tried some fun and games using the boot1 area (which gets freed anyway) as a stack zone, but that didn't work real well- mostly I just wanted to get this fixed for now. On Fri, 15 Sep 2000, John Baldwin wrote: > Well, after a rather long and frustrating afternoon, it seems that > revision of the loader after Fri Sep 8 16:30 2000 UTC is broken for > the alpha arch. I've tried to narrow things down to see if it was just > the 4th changes or the pnp changes, but have been unable to get anything > to boot except for a binary and 4th files from that date. I've even > tried removing all of the 4th stuff and /boot/loader.rc and the newer > loader binaries still break. Every time they break, they trigger a > kernel stack not valid fault. My guess is that ficl is recursing in an > infinite loop somewhere, that it is recursing too deeply and using up > all available memory, or that something is failing to handle error conditions > and is dereferencing a NULL pointer. > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Sep 18 2:10:50 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from anchor-post-31.mail.demon.net (anchor-post-31.mail.demon.net [194.217.242.89]) by hub.freebsd.org (Postfix) with ESMTP id 70EB937B422 for ; Mon, 18 Sep 2000 02:10:48 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-31.mail.demon.net with esmtp (Exim 2.12 #1) id 13awwE-000GZz-0V; Mon, 18 Sep 2000 10:10:11 +0100 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 KAA37382; Mon, 18 Sep 2000 10:12:29 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 18 Sep 2000 10:10:14 +0100 (BST) From: Doug Rabson To: Matthew Jacob Cc: Peter Wemm , "Daniel C. Sobral" , alpha@freebsd.org Subject: Re: Loader badly broken on the alpha 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 Sun, 17 Sep 2000, Matthew Jacob wrote: > > > > Matthew Jacob wrote: > > > > > > I think I had determined (I thought) that it was just loader itself, but I > > > could be wrong. > > > > The problem is that the loader is now too large, it cannot fit inside the > > ~208K window that boot1 has got available to it. > > > > peter@ashburton[12:14am]/home/obj/home/src/sys/boot/alpha/loader-130# nm loader.sym | sort | tail -1 > > 000000002003e190 A end > > > > The VM space ends at 2004000. I can't find where, but I was pretty sure that > > the last 8K page was already spoken for and we've clobbered it. > > > > Was the pnp stuff added to the Alpha loader images? That is what probably > > tipped it over the edge. > > I've been looking at this a little bit. The last last 8k may not be entirely > spoken for, because previous loader.sym's had: > > 000000002003d260 A _end > 000000002003d260 A end > > > But if it's 8k (and I don't know anything much about this really- I have never > delved to much into this portion of alphas) this may explain why the boot > stuff never did work right entirely for all models (e.g., off of floppy for a > rawhide). > > In any case, this one is a hard one. I was comparing object sizes between June > 23'd loader.sym and the current one on alpha, and there's no one single thing > that got all that much bigger! > > We need to pull out 3408 bytes- but it's not that simple- bcopy seems to take > 2544 bytes, which is ridiculously large for a boot block- so I replaced it > with a dopey one line C function but that didn't change _end for me, so I have > to look at the linker magic some I guess. Looking at sizes, supporting gzip'ed files is quite expensive - about 23k of code and data. Ficl is the real heavyweight with 50k in words.o alone. I just tried building everything with -Os but that was a waste of time - only 784 bytes difference. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 20 8348 3944 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Sep 18 8:14:46 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 957AC37B422 for ; Mon, 18 Sep 2000 08:14:44 -0700 (PDT) Received: from newsguy.com (p03-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.132]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id AAA27909; Tue, 19 Sep 2000 00:14:23 +0900 (JST) Message-ID: <39C6311E.19B7337B@newsguy.com> Date: Tue, 19 Sep 2000 00:13:34 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: mjacob@feral.com Cc: Peter Wemm , alpha@FreeBSD.ORG Subject: Re: Loader badly broken on the alpha 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: > > We need to pull out 3408 bytes- but it's not that simple- bcopy seems to take > 2544 bytes, which is ridiculously large for a boot block- so I replaced it > with a dopey one line C function but that didn't change _end for me, so I have > to look at the linker magic some I guess. Well, here is my position on this. No, we need not pull out 3408 bytes. While the loader must not bloat, the whole point of having boot[12] _and_ loader is allowing us to add extra features and intelligence to loader without having to worry about how many bytes a function is taking. boot[12] _must_ be capable of providing a decent environment for loader. That's it's main function, nowadays, no matter what bde wants or says. For the short term, one area of investigation that might provide us a quick respite is compressing softwords.c on FICL. This file contains a huge string of Forth commands that is interpreted when FICL is initialized. Since we do have gz uncompression on libstand, it should probably be easy to change the build process as to make that string a compressed version of what it is right now (softwords.c is generated by softwords.awk -- there's also a softwords.pl, if whoever does it is more comfortable with perl), and then uncompress it before interpreting it during FICL initialization. Alas, I'm not doing it, I'm not even looking into it. I have absolutely _no_ time to do it. Sorry. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.secret.bsdconspiracy.net "I demand that my picture show a handsome face, even if it doesn't look like me." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Sep 18 8:20:35 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 4253C37B423 for ; Mon, 18 Sep 2000 08:20:33 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id IAA00450; Mon, 18 Sep 2000 08:20:25 -0700 Date: Mon, 18 Sep 2000 08:17:23 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Daniel C. Sobral" Cc: Peter Wemm , alpha@FreeBSD.ORG Subject: Re: Loader badly broken on the alpha In-Reply-To: <39C6311E.19B7337B@newsguy.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 Whoa! Take it easy... Fine insofar as it goes, and, err, umm, I wasn't asking you to pull the 3KB out of the FICL code. I was trying to squeeze it elsewhere coz I *like* the FICL code. There are some fun && games for alpha boot space and how FreeBSD uses it which makes this dance somewhat interesting. But see later mail- we've solved the problem for now. A bit more cleverness will extend things even further. I doubt that we'll need to require any scrunch from FICL, which, as you correctly are hinting it, is the queen bee of the boot code which everything else should bust butt to serve. -matt > Matthew Jacob wrote: > > > > We need to pull out 3408 bytes- but it's not that simple- bcopy seems to take > > 2544 bytes, which is ridiculously large for a boot block- so I replaced it > > with a dopey one line C function but that didn't change _end for me, so I have > > to look at the linker magic some I guess. > > Well, here is my position on this. No, we need not pull out 3408 bytes. > While the loader must not bloat, the whole point of having boot[12] > _and_ loader is allowing us to add extra features and intelligence to > loader without having to worry about how many bytes a function is > taking. > > boot[12] _must_ be capable of providing a decent environment for loader. > That's it's main function, nowadays, no matter what bde wants or says. > > For the short term, one area of investigation that might provide us a > quick respite is compressing softwords.c on FICL. This file contains a > huge string of Forth commands that is interpreted when FICL is > initialized. Since we do have gz uncompression on libstand, it should > probably be easy to change the build process as to make that string a > compressed version of what it is right now (softwords.c is generated by > softwords.awk -- there's also a softwords.pl, if whoever does it is more > comfortable with perl), and then uncompress it before interpreting it > during FICL initialization. > > Alas, I'm not doing it, I'm not even looking into it. I have absolutely > _no_ time to do it. Sorry. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Sep 18 8:27:35 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id C7B6E37B422 for ; Mon, 18 Sep 2000 08:27:32 -0700 (PDT) Received: from newsguy.com (p03-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.132]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id AAA02711; Tue, 19 Sep 2000 00:27:21 +0900 (JST) Message-ID: <39C63428.49F39F5D@newsguy.com> Date: Tue, 19 Sep 2000 00:26:32 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: mjacob@feral.com Cc: Peter Wemm , alpha@FreeBSD.ORG Subject: Re: Loader badly broken on the alpha 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: > > Whoa! Take it easy... > > Fine insofar as it goes, and, err, umm, I wasn't asking you to pull the 3KB > out of the FICL code. I was trying to squeeze it elsewhere coz I *like* the > FICL code. > > There are some fun && games for alpha boot space and how FreeBSD uses it which > makes this dance somewhat interesting. > > But see later mail- we've solved the problem for now. A bit more cleverness > will extend things even further. I doubt that we'll need to require any > scrunch from FICL, which, as you correctly are hinting it, is the queen bee of > the boot code which everything else should bust butt to serve. I wasn't suggesting taking anything out. Just that there is this huge string of source code that is linked, which could be compressed before linked, and then uncompressed before use with the gunzip code we already have. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.secret.bsdconspiracy.net "I demand that my picture show a handsome face, even if it doesn't look like me." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Sep 18 11: 1: 9 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id 87F1237B423 for ; Mon, 18 Sep 2000 11:01:04 -0700 (PDT) Received: from FOETZSTATION (p3EE3728E.dip0.t-ipconnect.de [62.227.114.142]) by post.webmailer.de (8.9.3/8.8.7) with SMTP id UAA13873 for ; Mon, 18 Sep 2000 20:01:00 +0200 (MET DST) From: webmaster@ah-network.de Message-ID: <000a01c0219a$29761aa0$8b00a8c0@FOETZSTATION> To: Subject: =?iso-8859-1?Q?doesn=B4t_boot?= Date: Mon, 18 Sep 2000 19:59:12 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C021AA.EA122AF0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.5600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.5600 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C021AA.EA122AF0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable hello daemons, everytime i want to boot with cd the system hangs up at the "jumping to = bootstrap". with the floppies it=B4s the same. and with netbsd, too.=20 i can see the cubic cursor and then nothing happens.=20 i tried: freebsd 4.1, netbsd 1.4.2 and freebsd 3.2(disks only).=20 my system: 21164 533mhz lx164 256ram 15gb maxtor/ide 48xcd/ide LG floppy(!!) matrox 2mb svga all other systems work normally but i can=B4t stand the linuxes, and for = WinNT i don=B4t need an alpha.=20 what can i do?? the system is o.k. and there also was no problem with installing = anything else using the srm-console or the alphabios. best regards ------=_NextPart_000_0007_01C021AA.EA122AF0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
hello daemons,
 
everytime i want to boot with cd the = system hangs=20 up at the "jumping to bootstrap". with the floppies it=B4s the same. and = with=20 netbsd, too.
i can see the cubic cursor and then = nothing =20 happens.
i tried: freebsd 4.1, netbsd 1.4.2 and = freebsd=20 3.2(disks only).
my system:
21164 533mhz
lx164
256ram
15gb maxtor/ide
48xcd/ide LG
floppy(!!)
matrox 2mb svga
 
all other systems work normally but i = can=B4t stand=20 the linuxes, and for WinNT i don=B4t need an alpha.
what can i do??
the system is o.k. and there also was = no problem=20 with installing anything else using the srm-console or the=20 alphabios.
 
best regards
------=_NextPart_000_0007_01C021AA.EA122AF0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Sep 18 11: 7:16 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 89E6E37B424 for ; Mon, 18 Sep 2000 11:07:07 -0700 (PDT) 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 OAA08162; Mon, 18 Sep 2000 14:07:03 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e8II73q02713; Mon, 18 Sep 2000 14:07:03 -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: Mon, 18 Sep 2000 14:07:03 -0400 (EDT) To: webmaster@ah-network.de Cc: Subject: Re: =?iso-8859-1?Q?doesn=B4t_boot?= In-Reply-To: <000a01c0219a$29761aa0$8b00a8c0@FOETZSTATION> References: <000a01c0219a$29761aa0$8b00a8c0@FOETZSTATION> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14790.22706.875016.353651@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org webmaster@ah-network.de writes: > hello daemons, >=20 > everytime i want to boot with cd the system hangs up at the "jumping= to bootstrap". with the floppies it=B4s the same. and with netbsd, too= .=20 <...> > best regards > Ugh. Please don't post html and text to this list. Please post just text.=20 Make sure your srm console "console" enviroment matches reality. It sounds like your console is set to serial & you're using a graphics=20= head. Use "show console" to check for this. So do: >>> set console graphics >>> init <...> >>> show console graphics >>> boot dka500 (or wherever your cd is..) BTW: Linux "works" because it is broken & ignores the setting of this variable. Cheers, Drew -----------------------------------------------------------------------= ------- Andrew Gallatin, Sr Systems Programmer=09http://www.cs.duke.edu/~gallat= in 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 Mon Sep 18 15:42: 9 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 2374C37B423 for ; Mon, 18 Sep 2000 15:42:06 -0700 (PDT) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8IMg2i07702; Mon, 18 Sep 2000 15:42:02 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.0/8.11.0) id e8IMdiv74189; Mon, 18 Sep 2000 15:39:44 -0700 (PDT) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 18 Sep 2000 15:39:44 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: Matthew Jacob Subject: RE: cvs commit: src/sys/boot/alpha/common main.c Cc: alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ moved to -alpha ] On 18-Sep-00 Matthew Jacob wrote: > >> >> On 18-Sep-00 Matthew Jacob wrote: >> > >> > Really? >> > >> > Hmm. Thought we got this one for the moment. >> > >> > Are you sure you remembered to disklabel -B the new boot1? >> >> Yep. :( I have the ra's from the old loader that used to >> work (although I don't have a loader.sym for that) and for >> the new loader. I'll see what I can do with that. > > Does i die in loader or in boot1? Loader: 0x2001cce0 : mov a0,v0 0x2001cce4 : ble a2,0x2001cf34 0x2001cce8 : subq a0,a1,t5 0x2001ccec : cmpult t5,a2,t5 0x2001ccf0 : bne t5,0x2001ce88 0x2001ccf4 : addq a1,a2,a3 0x2001ccf8 : ldq_u t2,0(a1) 0x2001ccfc : xor a1,a0,t0 0x2001cd00 : and t0,0x7,t0 0x2001cd04 : and a0,0x7,t1 0x2001cd08 : bne t0,0x2001cd70 0x2001cd0c : beq t1,0x2001cd24 0x2001cd10 : ldq_u t3,0(a0) 0x2001cd14 : addq a2,t1,a2 0x2001cd18 : mskqh t2,a1,t2 It dies with PC = 0 at that last address I guess it is dereferencing a NULL pointer or something silly like that? Hmm, looking in src/libc/alpha/string/bcopy.S: /* src & dst have same alignment */ beq t1,bcopy_all_aligned ldq_u t3,0(DSTREG) addq SIZEREG,t1,SIZEREG mskqh t2,SRCREG,t2 mskql t3,SRCREG,t3 or t2,t3,t2 So it looks like possibly a NULL source? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Sep 18 16:38:23 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 4819437B424; Mon, 18 Sep 2000 16:38:20 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA02169; Mon, 18 Sep 2000 16:38:19 -0700 Date: Mon, 18 Sep 2000 16:38:19 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: alpha@FreeBSD.org Subject: RE: cvs commit: src/sys/boot/alpha/common main.c 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 This was the same pattern that got me. It's what had convinced me that libstand was to blame. Gee- I dunno now... On Mon, 18 Sep 2000, John Baldwin wrote: > [ moved to -alpha ] > > On 18-Sep-00 Matthew Jacob wrote: > > > >> > >> On 18-Sep-00 Matthew Jacob wrote: > >> > > >> > Really? > >> > > >> > Hmm. Thought we got this one for the moment. > >> > > >> > Are you sure you remembered to disklabel -B the new boot1? > >> > >> Yep. :( I have the ra's from the old loader that used to > >> work (although I don't have a loader.sym for that) and for > >> the new loader. I'll see what I can do with that. > > > > Does i die in loader or in boot1? > > Loader: > > 0x2001cce0 : mov a0,v0 > 0x2001cce4 : ble a2,0x2001cf34 > 0x2001cce8 : subq a0,a1,t5 > 0x2001ccec : cmpult t5,a2,t5 > 0x2001ccf0 : bne t5,0x2001ce88 > 0x2001ccf4 : addq a1,a2,a3 > 0x2001ccf8 : ldq_u t2,0(a1) > 0x2001ccfc : xor a1,a0,t0 > 0x2001cd00 : and t0,0x7,t0 > 0x2001cd04 : and a0,0x7,t1 > 0x2001cd08 : bne t0,0x2001cd70 > 0x2001cd0c : beq t1,0x2001cd24 > 0x2001cd10 : ldq_u t3,0(a0) > 0x2001cd14 : addq a2,t1,a2 > 0x2001cd18 : mskqh t2,a1,t2 > > It dies with PC = 0 at that last address > > I guess it is dereferencing a NULL pointer or something silly like > that? > > Hmm, looking in src/libc/alpha/string/bcopy.S: > > /* src & dst have same alignment */ > beq t1,bcopy_all_aligned > > ldq_u t3,0(DSTREG) > addq SIZEREG,t1,SIZEREG > mskqh t2,SRCREG,t2 > mskql t3,SRCREG,t3 > or t2,t3,t2 > > So it looks like possibly a NULL source? > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Sep 19 6:58:16 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dd-mail-smtp.dk.damgaard.com (dd-mail-smtp.dk.damgaard.com [213.237.137.2]) by hub.freebsd.org (Postfix) with SMTP id B040237B42C for ; Tue, 19 Sep 2000 06:58:13 -0700 (PDT) Received: from 213.237.137.2 by dd-mail-smtp.dk.damgaard.com (InterScan E-Mail VirusWall NT); Tue, 19 Sep 2000 15:58:06 +0200 (Romance Daylight Time) Received: by dd-mail-smtp.dk.damgaard.com with Internet Mail Service (5.5.2650.21) id ; Tue, 19 Sep 2000 15:58:06 +0200 Message-ID: <5ED89301AE60D311AAD500508B0EF55F50E070@dd-mail.intern.dd.dk> From: Bjarne Blichfeldt To: "Freebsd-Alpha (E-mail)" Subject: alpha ev56 contra ev67 Date: Tue, 19 Sep 2000 15:54:26 +0200 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 Gentlemen, Not directly FreeBSD, but close. What are the changes from ev56 to ev67? Specifically, will I see any performance increase from compiling a program on a ev67, compared to compiling on a ev56 and running the same program on a ev67. ex. 1. compile program AA on a ev56, execute on a ev56 = performance XX 2. compile program AA on a ev56, execute on a ev67 = performance XX + some % 3. compile program AA on a ev67, execute on a ev67 = performance ?? compared to 2. Depends on the program, I know, but in general non obligated terms ;-) Compiling the program is done with gcc 2.95.2 in this scenario. Does anybody, by the way, have any idea of how the gcc compiler fares, compared to Compaq's own compiler on the alpha platform ? TIA, Bjarne Blichfeldt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Sep 19 7:57:19 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from utep.el.utwente.nl (utep.el.utwente.nl [130.89.30.10]) by hub.freebsd.org (Postfix) with ESMTP id 23FF337B422 for ; Tue, 19 Sep 2000 07:57:12 -0700 (PDT) Received: from tn.utwente.nl (uttnb55.tn.utwente.nl [130.89.74.55]) by utep.el.utwente.nl (8.9.3/8.9.3) with ESMTP id QAA14634 for ; Tue, 19 Sep 2000 16:58:02 +0200 Message-ID: <39C77F10.A89C1C6A@tn.utwente.nl> Date: Tue, 19 Sep 2000 16:58:24 +0200 From: "Andrei A. Dergatchev" X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: en,ru MIME-Version: 1.0 To: "Freebsd-Alpha (E-mail)" Subject: Re: alpha ev56 contra ev67 References: <5ED89301AE60D311AAD500508B0EF55F50E070@dd-mail.intern.dd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, In case you haven't heard yet, there is a set of good docs available directly from Compaq :-) http://ftp.digital.com/pub/Digital/info/semiconductor/literature/dsc-library.html > Gentlemen, > > Not directly FreeBSD, but close. > > What are the changes from ev56 to ev67? In short - out of order execution, bigger L1 cache (64K I, 64K D instead of 8K/8K+96K L2). > Specifically, will I see any performance increase from compiling a > program on a ev67, compared to compiling on a ev56 and running the > same program on a ev67. As I heard from someone, if your program is written in hand optimized assembly avoiding stalls and squeezing last cycles from the ev56 using all its features, than you are unlikely to see a big performance boost :-) Otherwise out of order execution and other features of the 264 will likely speed your code up by about factor of 2. By the way why do you expect any change in execution time depending on the platform you're compiling ? > Does anybody, by the way, have any idea of how the gcc compiler fares, > compared > to Compaq's own compiler on the alpha platform ? ccc is better on optimizing for the Alpha, especially when there is something significant to optimize in your code :-) > > TIA, > Bjarne Blichfeldt Rgds, Andrei To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Sep 19 8:43:53 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from blighty.com (vix.samspade.org [204.152.186.148]) by hub.freebsd.org (Postfix) with ESMTP id 8544337B423 for ; Tue, 19 Sep 2000 08:43:51 -0700 (PDT) Received: by blighty.com (Postfix, from userid 1000) id 4C724533; Tue, 19 Sep 2000 08:43:59 -0700 (PDT) Date: Tue, 19 Sep 2000 08:43:59 -0700 From: Steve Atkins To: freebsd-alpha@freebsd.org Subject: Re: alpha ev56 contra ev67 Message-ID: <20000919084359.B12931@blighty.com> References: <5ED89301AE60D311AAD500508B0EF55F50E070@dd-mail.intern.dd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <5ED89301AE60D311AAD500508B0EF55F50E070@dd-mail.intern.dd.dk>; from bbl@dk.damgaard.com on Tue, Sep 19, 2000 at 03:54:26PM +0200 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Sep 19, 2000 at 03:54:26PM +0200, Bjarne Blichfeldt wrote: > Gentlemen, > > Not directly FreeBSD, but close. > > What are the changes from ev56 to ev67? Out of order execution is the biggie, but the cache increased in size too - from 8/8+96 to 64/64 > Specifically, will I see any performance increase from compiling a > program on a ev67, compared to compiling on a ev56 and running the > same program on a ev67. I assume you mean optimise for EV6/EV5 rather than compile on EV6/EV5? > ex. > 1. compile program AA on a ev56, execute on a ev56 = performance XX > 2. compile program AA on a ev56, execute on a ev67 = performance XX + some > % > 3. compile program AA on a ev67, execute on a ev67 = performance ?? > compared to 2. > > Depends on the program, I know, but in general non obligated terms ;-) > Compiling the program is done with gcc 2.95.2 in this scenario. Generally, a program that is compiler-optimised for EV5 will run nearly as well on an EV6 as a program compiler-optimised for EV6. Code optimised for an in-order machine will run nicely on an OOO machine. There'll always be some improvement optimising for EV6, and occasionally the improvement is large. Performance differences will depend on lots of things. If it is memory intensive and the inner loop fits into a 64k cache but not an 8k cache you'll see a big speedup. If your application smells like SPECint or SPECfp you may see a c. 2x performance improvement. > Does anybody, by the way, have any idea of how the gcc compiler fares, > compared > to Compaq's own compiler on the alpha platform ? Poorly. Compaqs compiler/linker/optimiser suite is very good. Gcc isn't that bad, though. The effect is less spectacular on an EV6, as the OOO makes clever scheduling less valuable. Cheers, Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Sep 19 23:33:34 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 1FFCF37B422 for ; Tue, 19 Sep 2000 23:33:33 -0700 (PDT) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8K6XSi65323 for ; Tue, 19 Sep 2000 23:33:28 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.0/8.11.0) id e8K6V8H92742 for alpha@FreeBSD.org; Tue, 19 Sep 2000 23:31:08 -0700 (PDT) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 19 Sep 2000 23:31:08 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: alpha@FreeBSD.org Subject: Ithreads kernel weirdness Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I suppose many of you are wondering why there haven't been any recent commits of ithreads for the alpha as promised. The reason is that I can't get a plain kernel to boot. My test kernel with several debugging kernel options added in the config file boots fine. If I remove some of those debugging options, the kernel will boot sometimes, and hang others. If I remove all the debugging options, the kernel always hangs. When it hangs, the kernel is always hanging just after the 'timecounter' device probe printf's. Normally after this I get the acd0 probe message. Booting verbose ends with two messages from ata-master0, so I'm assuming it is during ata's probe of its busses, which use the await()/asleep() code. At this point in time, my guess is that this another weird manifestation of the possible BSS corruption bug that a few people are seeing (like static hints not working because hints_loaded is getting trounced). I would have committed this 2 days ago, but I can't get a normal kernel to boot. It might also be weirdness with spl()'s (although it used to work fine, so no reason that it doesn't work now, to be honest). Regardless, my next step is to make the softinterrupt code mostly MI which will move SWI's to the softinterrupt thread as a side effect. Then we should be able to kill spl's (I hope), which may clear up some problems as well. The current ithreads patchset as always is at: http://www.FreeBSD.org/~jhb/patches/alpha.ithreads.patch. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Sep 19 23:38:50 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 80D3D37B422; Tue, 19 Sep 2000 23:38:47 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id XAA03278; Tue, 19 Sep 2000 23:38:47 -0700 Date: Tue, 19 Sep 2000 23:38:45 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: alpha@FreeBSD.ORG Subject: Re: Ithreads kernel weirdness In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've had a slightly similar experience on my pc164- it dies just after loading f/w into the Qlogic ISP, which usually means that this is some interrupt related breakage. Time and heat (heatwave in SF means I have to really shut down all my systems) has kept me from pursuing this further- I sure have it on the top of my list. On Tue, 19 Sep 2000, John Baldwin wrote: > I suppose many of you are wondering why there haven't been any > recent commits of ithreads for the alpha as promised. The reason > is that I can't get a plain kernel to boot. My test kernel with > several debugging kernel options added in the config file boots > fine. If I remove some of those debugging options, the kernel > will boot sometimes, and hang others. If I remove all the > debugging options, the kernel always hangs. When it hangs, the > kernel is always hanging just after the 'timecounter' device > probe printf's. Normally after this I get the acd0 probe > message. Booting verbose ends with two messages from > ata-master0, so I'm assuming it is during ata's probe of its > busses, which use the await()/asleep() code. At this point in > time, my guess is that this another weird manifestation of the > possible BSS corruption bug that a few people are seeing > (like static hints not working because hints_loaded is getting > trounced). I would have committed this 2 days ago, but I can't > get a normal kernel to boot. It might also be weirdness with > spl()'s (although it used to work fine, so no reason that it > doesn't work now, to be honest). Regardless, my next step is > to make the softinterrupt code mostly MI which will move SWI's > to the softinterrupt thread as a side effect. Then we should > be able to kill spl's (I hope), which may clear up some problems > as well. The current ithreads patchset as always is at: > http://www.FreeBSD.org/~jhb/patches/alpha.ithreads.patch. > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Sep 20 3:14:37 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dd-mail-smtp.dk.damgaard.com (dd-mail-smtp.dk.damgaard.com [213.237.137.2]) by hub.freebsd.org (Postfix) with SMTP id 4845237B424 for ; Wed, 20 Sep 2000 03:14:34 -0700 (PDT) Received: from 213.237.137.2 by dd-mail-smtp.dk.damgaard.com (InterScan E-Mail VirusWall NT); Wed, 20 Sep 2000 12:14:31 +0200 (Romance Daylight Time) Received: by dd-mail-smtp.dk.damgaard.com with Internet Mail Service (5.5.2650.21) id ; Wed, 20 Sep 2000 12:14:31 +0200 Message-ID: <5ED89301AE60D311AAD500508B0EF55F50E072@dd-mail.intern.dd.dk> From: Bjarne Blichfeldt To: "Freebsd-Alpha (E-mail)" Subject: Re: alpha ev56 contra ev67 Date: Wed, 20 Sep 2000 12:10:53 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) 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 Thanks for your answers. Yes I did read the alpha manual before mailing, but I=20 obviously didn't got any wiser,=A0I am not into heavy cpu-ing ;-) Our current development platform is a ev56 and we produce code for that by default, but we also produce code for ev4 for=20 customers with older machines. The software is accounting software, and is mostly i/o, not processor heavy in any way. Now, one customer has upgraded his machine to a ev67 and is not impressed by the performance increase they have seen. They therefore request (thru Compaq) that we upgrade our machine, or borrow one from Compaq so we can compile our software on a ev67. Now there are about a zillion things to look into here, which has = nothing to do with the chips and I dont seriously believe that this customer's lack of expectation has much to do whith the chips, but... The ev5 had new instructions compared to ev4. That might had improved=20 performance, but only a recompile on a ev5 would have taken advantage of that. I could not find any instructions new to ev6, but understood there might be other issues, hence the question on the list. So while the case with this customer is probably not a processor problem, it triggered the thought process on wether or not it is time for us to upgrade our hardware. The downside of a newer processor is = that=20 we then have to produce both ev4 and ev56 in addition to the new = default=20 ev67 code. At least, that was the reasoning. Since there are no new instructions, we would be able to produce only ev4 and ev67 code, and then use ev67 code on a ev56 with no ill effect. So thanks again for your inputs. Regards, Bjarne Blichfeldt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Sep 20 21:43:44 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 5435E37B424 for ; Wed, 20 Sep 2000 21:43:40 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id VAA07313 for ; Wed, 20 Sep 2000 21:43:40 -0700 Date: Wed, 20 Sep 2000 21:43:36 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: alpha@FreeBSD.ORG Subject: end of life for DEC branded Alphas (and Tru64) (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ---------- Forwarded message ---------- Date: Wed, 20 Sep 2000 15:51:02 -0400 (EDT) From: William H. Magill Reply-To: axp-list@redhat.com To: axp-list@redhat.com Subject: end of life for DEC branded Alphas (and Tru64) My understanding is that any EV56 or earlier processor will no longer be supported by Tru64 after 5.1 (and depending on how you read the 5.1 release notes, NOT in 5.1) This implies that there will be a LOT of 1000A's hitting the market in the not too distant future. (There are supposedly "thousands" of them in use by various telcos.) The 1000As are a nice box. Lots of PCI slots. ----------< Forwarded Message Follows >---------- Date: Wed, 20 Sep 2000 15:24:11 -0400 From: "Dr. Tom Blinn, 603-884-0646" Subject: Tru64 UNIX V5.1 and TruCluster software To: tru64-unix-managers@ornl.gov Rich asked: > Just curious if anyone has the status on whether > 5.1 has been qualified and is shipping yet? Yes, kits are starting to ship. I've received my shipment, and once the internal distribution is complete, they start shipping customer updates. Someone asked about fibre channel arbitrated loop for the TruCluster product, and that's still in testing, so the statement of support for that isn't ready, but otherwise, the TruCluster product is also out and ready to go. By the way, V5.1 is the last release that will support the older "DEC" branded Alpha systems (the ones that do NOT have PCI buses for I/O -- the DEC 2000, DEC 3000, DEC 4000, DEC 7000/10000). We announced in the V5.0A release notes that support would be removed in a future release, and in the V5.1 notes that V5.1 is the last release to support those older systems. Bear in mind that all of these systems ARE supported in the V4.0G release, and that V4.0G is planned to have a long service life. If you are using one of these older systems and have not yet decided to move to V5.x, you might be better off moving to V4.0G than to V5.0 or V5.0A or V5.1. I have also heard reports that Oracle Corporation may be retiring their support for the older CPU models that did not support byte and double-byte (8 bit and 16 bit) operations (LCA, EV4, EV45, EV5). If you are using Oracle software on older systems using those old CPU designs, you may wish to check with Oracle on their intentions for future support. Tom Dr. Thomas P. Blinn + UNIX Software Group + Compaq Computer Corporation 110 Spit Brook Road, MS ZKO3-2/W17 Nashua, New Hampshire 03062-2698 Technology Partnership Engineering Phone: (603) 884-0646 Internet: tpb@zk3.dec.com Compaq's Easynet: alpha::tpb ACM Member: tpblinn@acm.org PC@Home: tom@felines.mv.net Worry kills more people than work because more people worry than work. Keep your stick on the ice. -- Steve Smith ("Red Green") My favorite palindrome is: Satan, oscillate my metallic sonatas. -- Phil Agre, pagre@alpha.oac.ucla.edu Yesterday it worked / Today it is not working / UNIX is like that -- apologies to Margaret Segall Opinions expressed herein are my own, and do not necessarily represent those of my employer or anyone else, living or dead, real or imagined. -------------< End Forwarded Message >----------- -- www.tru64unix.compaq.com www.tru64.org comp.unix.tru64 T.T.F.N. William H. Magill Senior Systems Administrator Information Services and Computing (ISC) University of Pennsylvania Internet: magill@isc.upenn.edu magill@acm.org http://www.isc-net.upenn.edu/~magill/ _______________________________________________ Axp-list mailing list Axp-list@redhat.com https://listman.redhat.com/mailman/listinfo/axp-list To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Sep 21 11:15:21 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 AC19037B424 for ; Thu, 21 Sep 2000 11:15:17 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13cAsI-000NiO-00; Thu, 21 Sep 2000 18:15:11 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e8LIGWl02114; Thu, 21 Sep 2000 20:16:32 +0200 (CEST) (envelope-from wkb) Date: Thu, 21 Sep 2000 20:16:32 +0200 From: Wilko Bulte To: Matthew Jacob Cc: alpha@freebsd.org Subject: Re: end of life for DEC branded Alphas (and Tru64) (fwd) Message-ID: <20000921201632.L1760@freebie.demon.nl> 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 Wed, Sep 20, 2000 at 09:43:36PM -0700 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Sep 20, 2000 at 09:43:36PM -0700, Matthew Jacob wrote: Sigh.. > ---------- Forwarded message ---------- > Date: Wed, 20 Sep 2000 15:51:02 -0400 (EDT) > From: William H. Magill > Reply-To: axp-list@redhat.com > To: axp-list@redhat.com > Subject: end of life for DEC branded Alphas (and Tru64) > > My understanding is that any EV56 or earlier processor will no longer be > supported by Tru64 after 5.1 (and depending on how you read the 5.1 release > notes, NOT in 5.1) Which is a *wrong* understanding. Just read Tom's words carefully. Oracle may be moving, there is nothing that says T64 does the same. What Tom writes is that the Turbochannel I/O bus machines are end of support. And DEC2000 (Jensen & Culzean) which are EISA-only. TC based boxes are just marginally useful on FreeBSD to start with: the SCSI CAM subsystem does not support TC based SCSI adapters. Jensen is not supported at all. > This implies that there will be a LOT of 1000A's hitting the market > in the not too distant future. (There are supposedly "thousands" > of them in use by various telcos.) The 1000As are a nice box. Lots of PCI > slots. Guess what: 1000A are PCI/EISA machines right? Where does it say PCI boxes are being retired?? > ----------< Forwarded Message Follows >---------- > Date: Wed, 20 Sep 2000 15:24:11 -0400 > From: "Dr. Tom Blinn, 603-884-0646" > Subject: Tru64 UNIX V5.1 and TruCluster software > To: tru64-unix-managers@ornl.gov > > Rich asked: > > > Just curious if anyone has the status on whether > > 5.1 has been qualified and is shipping yet? > > Yes, kits are starting to ship. I've received my shipment, and once > the internal distribution is complete, they start shipping customer > updates. Someone asked about fibre channel arbitrated loop for the > TruCluster product, and that's still in testing, so the statement of > support for that isn't ready, but otherwise, the TruCluster product > is also out and ready to go. > > By the way, V5.1 is the last release that will support the older > "DEC" branded Alpha systems (the ones that do NOT have PCI buses > for I/O -- the DEC 2000, DEC 3000, DEC 4000, DEC 7000/10000). We > announced in the V5.0A release notes that support would be removed > in a future release, and in the V5.1 notes that V5.1 is the last > release to support those older systems. Bear in mind that all of > these systems ARE supported in the V4.0G release, and that V4.0G > is planned to have a long service life. If you are using one of > these older systems and have not yet decided to move to V5.x, you > might be better off moving to V4.0G than to V5.0 or V5.0A or V5.1. > > I have also heard reports that Oracle Corporation may be retiring > their support for the older CPU models that did not support byte > and double-byte (8 bit and 16 bit) operations (LCA, EV4, EV45, EV5). > If you are using Oracle software on older systems using those old > CPU designs, you may wish to check with Oracle on their intentions > for future support. > > Tom > > Dr. Thomas P. Blinn + UNIX Software Group + Compaq Computer Corporation > 110 Spit Brook Road, MS ZKO3-2/W17 Nashua, New Hampshire 03062-2698 -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Sep 21 14: 3:29 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from fep01-svc.swip.net (fep01.swip.net [130.244.199.129]) by hub.freebsd.org (Postfix) with ESMTP id E4DBF37B43E for ; Thu, 21 Sep 2000 14:03:21 -0700 (PDT) Received: from rejva.nu ([212.151.89.36]) by fep01-svc.swip.net (InterMail vM.5.01.01.01 201-252-104) with ESMTP id <20000921210320.BNZZ16761.fep01-svc.swip.net@rejva.nu> for ; Thu, 21 Sep 2000 23:03:20 +0200 Message-ID: <39CA75C4.AA0B92DF@rejva.nu> Date: Thu, 21 Sep 2000 22:55:33 +0200 From: flam Organization: flam X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.13 i586) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-alpha@freebsd.org Subject: Hello. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello! I just bought a AlphaServer 800. Digital Server 3305. When i'm booting.. it says: Cannot load /boot/loader I've tested to make different boot-discs. But it always says the same thing. I've tried to re-install, but it says the same thing again. So..I wonder if the file /boot/loader is missing from the system. But i can't do anything, because I can't touch anything. I also wonder if you have anything help me boot my freebsd. Mail me back as fast as possible. flam@rejva.nu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Sep 21 16:23:15 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 C0B7737B42C; Thu, 21 Sep 2000 16:23:06 -0700 (PDT) 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 e8LNN2423565 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Fri, 22 Sep 2000 01:23:04 +0200 (MET DST) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0::104:200:92ff:fe9b:20e7]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e8LNNGT09365; Fri, 22 Sep 2000 01:23:16 +0200 (CEST) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.0/8.9.2) id e8LNNCM58742; Fri, 22 Sep 2000 01:23:12 +0200 (CEST) (envelope-from ticso) Date: Fri, 22 Sep 2000 01:23:11 +0200 From: Bernd Walter To: John Baldwin Cc: alpha@FreeBSD.ORG Subject: Re: Ithreads kernel weirdness Message-ID: <20000922012311.A58579@cicely5.cicely.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from jhb@FreeBSD.ORG on Tue, Sep 19, 2000 at 11:31:08PM -0700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Sep 19, 2000 at 11:31:08PM -0700, John Baldwin wrote: > I suppose many of you are wondering why there haven't been any > recent commits of ithreads for the alpha as promised. The reason > is that I can't get a plain kernel to boot. My test kernel with > several debugging kernel options added in the config file boots > fine. If I remove some of those debugging options, the kernel > will boot sometimes, and hang others. If I remove all the > debugging options, the kernel always hangs. When it hangs, the > kernel is always hanging just after the 'timecounter' device > probe printf's. Normally after this I get the acd0 probe > message. Booting verbose ends with two messages from > ata-master0, so I'm assuming it is during ata's probe of its > busses, which use the await()/asleep() code. At this point in > time, my guess is that this another weird manifestation of the > possible BSS corruption bug that a few people are seeing > (like static hints not working because hints_loaded is getting > trounced). I would have committed this 2 days ago, but I can't > get a normal kernel to boot. It might also be weirdness with > spl()'s (although it used to work fine, so no reason that it > doesn't work now, to be honest). Regardless, my next step is > to make the softinterrupt code mostly MI which will move SWI's > to the softinterrupt thread as a side effect. Then we should > be able to kill spl's (I hope), which may clear up some problems > as well. The current ithreads patchset as always is at: > http://www.FreeBSD.org/~jhb/patches/alpha.ithreads.patch. Pressing the halt key on the hanging system showed me that it is always in hardclock() -- 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 Thu Sep 21 16:46:55 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 2FA3837B422; Thu, 21 Sep 2000 16:46:52 -0700 (PDT) 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 e8LNkm424631 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Fri, 22 Sep 2000 01:46:50 +0200 (MET DST) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0::104:200:92ff:fe9b:20e7]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e8LNl2T09391; Fri, 22 Sep 2000 01:47:02 +0200 (CEST) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.0/8.9.2) id e8LNkwG58784; Fri, 22 Sep 2000 01:46:58 +0200 (CEST) (envelope-from ticso) Date: Fri, 22 Sep 2000 01:46:58 +0200 From: Bernd Walter To: John Baldwin Cc: alpha@FreeBSD.ORG Subject: Re: Ithreads kernel weirdness Message-ID: <20000922014657.B58579@cicely5.cicely.de> References: <20000922012311.A58579@cicely5.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000922012311.A58579@cicely5.cicely.de>; from ticso on Fri, Sep 22, 2000 at 01:23:11AM +0200 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Sep 22, 2000 at 01:23:11AM +0200, Bernd Walter wrote: > Pressing the halt key on the hanging system showed me that > it is always in hardclock() To be exact PC is fffffc0000376dac which means that call_pal isn't returning. I repeated it several times and it's always the same address independent where the kernel hang. For reference from kern/kern_clock.c: if (CLKF_BASEPRI(frame)) { fffffc0000376d98: f0 00 2b a4 ldq t0,240(s2) fffffc0000376d9c: 01 f0 20 44 and t0,0x7,t0 fffffc0000376da0: 07 00 20 f4 bne t0,fffffc0000376dc0 static __inline u_int64_t alpha_pal_swpipl(u_int64_t newipl) { register u_int64_t a0 __asm__("$16") = newipl; fffffc0000376da4: 01 00 1f 22 lda a0,1(zero) register u_int64_t v0 __asm__("$0"); __asm__ __volatile__ ( fffffc0000376da8: 35 00 00 00 call_pal 0x35 /* * Save the overhead of a software interrupt; * it will happen as soon as we return, so do it now. */ (void)splsoftclock(); softclock(); fffffc0000376dac: 30 cc 7d a7 ldq t12,-13264(gp) fffffc0000376db0: c3 56 5b 6b jsr ra,(t12),fffffc000037c8c0 fffffc0000376db4: 22 00 ba 27 ldah gp,34(ra) fffffc0000376db8: cc 3f bd 23 lda gp,16332(gp) } else fffffc0000376dbc: 11 00 e0 c3 br fffffc0000376e04 setsoftclock(); fffffc0000376dc0: 80 8d 7d a7 ldq t12,-29312(gp) fffffc0000376dc4: 1e 6b 5b 6b jsr ra,(t12),fffffc0000371a40 fffffc0000376dc8: 22 00 ba 27 ldah gp,34(ra) fffffc0000376dcc: b8 3f bd 23 lda gp,16312(gp) } else if (softticks + 1 == ticks) -- 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 Fri Sep 22 2: 5:27 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 E3F7F37B422 for ; Fri, 22 Sep 2000 02:05:25 -0700 (PDT) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8M95Ei44359 for ; Fri, 22 Sep 2000 02:05:14 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.0/8.11.0) id e8M93eu16551 for alpha@FreeBSD.ORG; Fri, 22 Sep 2000 02:03:40 -0700 (PDT) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 22 Sep 2000 02:03:39 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: alpha@FreeBSD.ORG Subject: RE: Ithreads kernel weirdness Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 20-Sep-00 John Baldwin wrote: > I suppose many of you are wondering why there haven't been any > recent commits of ithreads for the alpha as promised. The reason > is that I can't get a plain kernel to boot. My test kernel with ... Ok, status update: I know have an almost fully MI softinterrupt thread which works fine on UP and SMP i386. It also seems to work fine with a normal kernel with interrupt threads on the alpha. I have one last bug to track down (we are grabbing shed_lock with interrupts disabled at some point late in the sysinit right before init forks, probably the first time we grab the sched_lock). Currently my running kernel is hacking around it by always assuming the saved ipl in a spin mutex is ALPHA_PSL_IPL_0. :-P Once I track this last bug down I'll update the alpha.ithreads.patch so you all can test it and help fine other bugs. We also are still in need of some low-level PCI interrupt enable/disable code for two of the PCI chipsets. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Sep 22 13:28:39 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 4EB4537B422 for ; Fri, 22 Sep 2000 13:28:34 -0700 (PDT) Received: from cold.cs.duke.edu (cold.cs.duke.edu [152.3.140.78]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id QAA20712; Fri, 22 Sep 2000 16:28:32 -0400 (EDT) From: Darrell Anderson Received: (anderson@localhost) by cold.cs.duke.edu (8.8.5/8.6.9) id QAA16630; Fri, 22 Sep 2000 16:28:31 -0400 (EDT) Message-Id: <200009222028.QAA16630@cold.cs.duke.edu> Subject: FreeBSD alpha cycle counter wackiness To: freebsd-alpha@freebsd.org Date: Fri, 22 Sep 2000 16:28:31 -0400 (EDT) Cc: gallatin@cs.duke.edu (Andrew Gallatin) X-Mailer: ELM [version 2.5 PL2] 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 Can someone explain this cycle counter behavior to me? The attached program reads the cycle counter from userspace, spitting out cycle counter values and deltas. On x86, I see consistent deltas (~8000 cycles). On alpha, I usually see a reasonable delta (~6000 cycles), with occassional jumps (~2^64). The jumps appear at consistent intervals. Sometimes there are long sequences where every delta is a jump. Before you tell me it's just wrapping, the delta is ~2^56. Deltas before and after the jumps seem quite reasonable. Here is some sample output from a 500MHz XP1000. I get similar results for 4.0-RELEASE and 5.0-CURRENT. 0xc5657103cc1d06a3 delta 0x1602 0xc5657103cc1d1ae5 delta 0x1442 0xc5657103cc1d2f41 delta 0x145c 0xc5652696cc1d9bc3 delta 0xffffb59300006c82 0xc5652696cc1db76e delta 0x1bab 0xc5652696cc1dcf85 delta 0x1817 0xc5652696cc1de53c delta 0x15b7 ... 0xc5652696cc1fda5e delta 0x13bc 0xc5652696cc1fedba delta 0x135c 0xc5652696cc200266 delta 0x14ac 0xc564dfc7cc206c65 delta 0xffffb931000069ff 0xc564dfc7cc208930 delta 0x1ccb 0xc564dfc7cc20a033 delta 0x1703 0xc564dfc7cc20b646 delta 0x1613 ... 0xc564dfc7cc22b111 delta 0x1374 0xc564dfc7cc22c690 delta 0x157f 0xc564dfc7cc22d9ed delta 0x135d 0xc564900ecc234d57 delta 0xffffb0470000736a 0xc564900ecc236b22 delta 0x1dcb 0xc564900ecc2382fb delta 0x17d9 0xc564900ecc239aae delta 0x17b3 here's the code: --begin-- #include #include static __inline u_int64_t read_cc(void) { u_int64_t rv = 0; #ifdef __i386__ __asm__ __volatile__ (".byte 0x0f, 0x31" : "=A" (rv)); #endif #ifdef __alpha__ __asm__ __volatile__ ("rpcc %0" : "=r" (rv)); #endif return rv; } int main(int argc, char *argv[]) { unsigned long then = read_cc(), now; while (1) { now = read_cc(); printf("0x%lx delta 0x%lx\n", now, now - then); then = now; } return 0; } --end-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Sep 22 14: 5: 0 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 34E2237B424 for ; Fri, 22 Sep 2000 14:04:58 -0700 (PDT) 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 RAA21415; Fri, 22 Sep 2000 17:04:56 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e8ML4uC13390; Fri, 22 Sep 2000 17:04:56 -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, 22 Sep 2000 17:04:56 -0400 (EDT) To: Darrell Anderson Cc: freebsd-alpha@freebsd.org Subject: Re: FreeBSD alpha cycle counter wackiness In-Reply-To: <200009222028.QAA16630@cold.cs.duke.edu> References: <200009222028.QAA16630@cold.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14795.51314.262384.708418@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Darrell Anderson writes: > Can someone explain this cycle counter behavior to me? The attached > program reads the cycle counter from userspace, spitting out cycle counter > values and deltas. > > On x86, I see consistent deltas (~8000 cycles). On alpha, I usually see a > reasonable delta (~6000 cycles), with occassional jumps (~2^64). The jumps > appear at consistent intervals. Sometimes there are long sequences where > every delta is a jump. Before you tell me it's just wrapping, the delta is > ~2^56. Deltas before and after the jumps seem quite reasonable. > > Here is some sample output from a 500MHz XP1000. I get similar results for > 4.0-RELEASE and 5.0-CURRENT. > > 0xc5657103cc1d06a3 delta 0x1602 > 0xc5657103cc1d1ae5 delta 0x1442 > 0xc5657103cc1d2f41 delta 0x145c > 0xc5652696cc1d9bc3 delta 0xffffb59300006c82 According to the green book, section (I:3.1.5), the PCC (Processor Cycle Counter) register consists of 2 32-bit fields. The lower 32-bits is a wrapping, unsigned 32-bit counter. The high-order bits are OS dependent. I don't think FreeBSD does anything to set up the high-order 32-bits, so it is likely that they're just garbage. So just use the lower 32-bits & watch for wraps. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Sep 23 0:36:11 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 A55D837B423; Sat, 23 Sep 2000 00:36:06 -0700 (PDT) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8N7Zqi82290; Sat, 23 Sep 2000 00:35:52 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.0/8.11.0) id e8N7YMi09670; Sat, 23 Sep 2000 00:34:22 -0700 (PDT) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 23 Sep 2000 00:34:22 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: smp@FreeBSD.org, cp@bsdi.com, alpha@FreeBSD.org Subject: Status update Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok, the alpha seems to be rather stable now without the need for obscene hacks to the mutex code to dink with mtx_saveipl. To summarize, here are the changes thus far: - software interrupts (SWI's) are now MI except for a few constants. Currently we still only have 8 SWI's on the x86 due to old compatability nonsense. We should be able to bump this to 32 like it is on the alpha very easily if it proves beneficial. Also software interrutps are completely divorced from the x86 hardware interrupt code. The softinterrupt thread is also now a simple kthread instead of an ithread. - interrupt threads on the alpha for device I/O interrupts. Note that two bus chipsets (dwlpx and mcpcia) still need a couple of low-level functions to handle enable/disable of interrupt sources. - spl()'s are stubbed out on the alpha. Actually, they are now stubbed out in MI code (kern_intr.c specifically). As a side effect of the IPL code becoming mostly MI now, there is a that includes and should be used instead. The individal machine/ipl.h are now quite short and simple. - The interrupt state of the sched_lock is now saved in a process's PCB during cpu_switch(). This way, code before and after a call to either mi_switch() or cpu_switch() is guaranteed to be run at the same interrupt state. Without this I was having problems on the alpha where the idle loop was running at ALPHA_PSL_IPL_SOFT (1) and as a result init's child process was never ran, among other things. This last change is something I'd like some feedback on. I've checked the BSD/OS x86 code, and it onyl saves the recursion count of the sched_lock in the pcb. However, after the problems with the alpha and some discussion with Peter Wemm on IRC, I decided that we should be doing this. However, I'm not completely certain, and any thoughts that anyone has would be appreciated. There are also a few more weirdism's on the alpha. In a few places in sys/kern, we call spl0() instead of splx(). I've added some debugging code to do a printf() if we aren't actually at IPL_0 (what spl0 used to do) after the mtx_exit(). It does trigger in several cases during /etc/rc at least, but the machine seems to be running stable regardless (I'll be running a buildworld -j 8 tonight to stress test it). My question is: is it ok for the code to run with some interrupts disabled or do we need to replace the calls to spl0() with enable_intr()? I'll be updating my patchset at http://www.FreeBSD.org/~jhb/patches/alpha.ithreads.patch shortly. If you have time, please test this stuff out so we can get it committed. Thanks. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Sep 23 10:28: 2 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from berserker.bsdi.com (berserker.twistedbit.com [199.79.183.1]) by hub.freebsd.org (Postfix) with ESMTP id 9E50B37B422; Sat, 23 Sep 2000 10:27:55 -0700 (PDT) Received: from berserker.bsdi.com (cp@[127.0.0.1]) by berserker.bsdi.com (8.9.3/8.9.3) with ESMTP id LAA17839; Sat, 23 Sep 2000 11:27:51 -0600 (MDT) Message-Id: <200009231727.LAA17839@berserker.bsdi.com> To: John Baldwin Cc: smp@freebsd.org, alpha@freebsd.org Subject: Re: Status update In-reply-to: Your message of "Sat, 23 Sep 2000 00:34:22 PDT." From: Chuck Paterson Date: Sat, 23 Sep 2000 11:27:51 -0600 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John, } }- software interrupts (SWI's) are now MI except for a few constants. } Currently we still only have 8 SWI's on the x86 due to old compatability } nonsense. We should be able to bump this to 32 like it is on the alpha very } easily if it proves beneficial. Also software interrutps are completely } divorced from the x86 hardware interrupt code. The softinterrupt thread is } also now a simple kthread instead of an ithread. I guess I'm a little unclear about this. We certainly don't want any hardware goop with software interrupts, at least in the case where there is no hardware support of software interrupts, but it seems like we do want them to be more than just another kthread, we want to be able to schedule them on the fly like hardware interrupts and do light weight context switches to them. Am I missing something? }- The interrupt state of the sched_lock is now saved in a process's PCB during } cpu_switch(). This way, code before and after a call to either mi_switch() } or cpu_switch() is guaranteed to be run at the same interrupt state. Without } this I was having problems on the alpha where the idle loop was running at } ALPHA_PSL_IPL_SOFT (1) and as a result init's child process was never ran, } among other things. BSD/OS on Sparc actually has interrupt levels that are associated with some mutexs. However the code that uses these levels are always using spin locks so there isn't an issue. Whenever cpu_switch is called all interrupts are blocked, but the spl level, which it think is ~= interrupt state is not raised at all. On sparc these are use for the low level code in for devices like the com driver. I guess the first question is why there is any kernel code calling switch with the interrupt priority up. This sounds like it may be a result of software interrupts being changed into kthreads? If alpha has hardware support for software interrupts then we might be able to treat them fully like hardware interrupts. The case in BSD/OS where a software interrupt is scheduled and the no switch flag is passed in will just work, the reason for the no switch is because the thread currently holds spins locks, which in the case of hardware supported interrupts should be blocked anyway. Chuck Chuck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Sep 23 10:53:44 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from server.baldwin.cx (server.geekhouse.net [64.81.6.52]) by hub.freebsd.org (Postfix) with ESMTP id 8D16D37B422; Sat, 23 Sep 2000 10:53:35 -0700 (PDT) Received: from john.baldwin.cx (root@john.baldwin.cx [192.168.1.18]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id KAA91697; Sat, 23 Sep 2000 10:55:51 -0700 (PDT) (envelope-from john@baldwin.cx) Received: (from john@localhost) by john.baldwin.cx (8.9.3/8.9.3) id KAA51845; Sat, 23 Sep 2000 10:55:12 -0700 (PDT) (envelope-from john) Message-Id: <200009231755.KAA51845@john.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200009231727.LAA17839@berserker.bsdi.com> Date: Sat, 23 Sep 2000 10:55:12 -0700 (PDT) From: John Baldwin To: Chuck Paterson Subject: Re: Status update Cc: alpha@freebsd.org, smp@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 23-Sep-00 Chuck Paterson wrote: > > John, > } > }- software interrupts (SWI's) are now MI except for a few constants. > } Currently we still only have 8 SWI's on the x86 due to old compatability > } nonsense. We should be able to bump this to 32 like it is on the alpha very > } easily if it proves beneficial. Also software interrutps are completely > } divorced from the x86 hardware interrupt code. The softinterrupt thread is > } also now a simple kthread instead of an ithread. > > > I guess I'm a little unclear about this. We certainly don't want > any hardware goop with software interrupts, at least in the case > where there is no hardware support of software interrupts, > but it seems like we do want them to be more than just another > kthread, we want to be able to schedule them on the fly like hardware > interrupts and do light weight context switches to them. Hmm, ok. Currently the only thing we were using from the ithd structure was the it_need flag (like the runstatus flag in BSD/OS' ithreads) to know when to keep looping. I changed it to just use spending for this. It is still scheduled and ran using a method similar to the hardware ithreads, it just doesn't have a ithd struct. However, it is quite easy to add the ithd struct back in when we go to light-weight context switches. > }- The interrupt state of the sched_lock is now saved in a process's PCB during > } cpu_switch(). This way, code before and after a call to either mi_switch() > } or cpu_switch() is guaranteed to be run at the same interrupt state. Without > } this I was having problems on the alpha where the idle loop was running at > } ALPHA_PSL_IPL_SOFT (1) and as a result init's child process was never ran, > } among other things. > > > BSD/OS on Sparc actually has interrupt levels that are associated > with some mutexs. However the code that uses these levels are always > using spin locks so there isn't an issue. Whenever cpu_switch > is called all interrupts are blocked, but the spl level, which it > think is ~= interrupt state is not raised at all. On sparc these > are use for the low level code in for devices like the com driver. > > I guess the first question is why there is any kernel code calling > switch with the interrupt priority up. This sounds like it may be > a result of software interrupts being changed into kthreads? It just happens on the alpha, it doesn't happen on the x86. I'm not sure where it is happening though. If we are sure of that guarantee (interrupts should always be enabled before grabbing sched_lock and calling either cpu_switch or mi_switch) then that should make my KASSERT()'s to find this easier, and I can get rid of this code. > If alpha has hardware support for software interrupts then we might > be able to treat them fully like hardware interrupts. The case in > BSD/OS where a software interrupt is scheduled and the no switch > flag is passed in will just work, the reason for the no switch > is because the thread currently holds spins locks, which in the > case of hardware supported interrupts should be blocked anyway. Currently all SWI's are now triggered by setting the appropriate bit in spending and calling sched_softintr() to make the softinterrupt thread runnable. sched_softintr() is very similar in functionality to sched_ithd in the x86 hardware interrupt code. > Chuck -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Sep 23 16: 0:18 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 C762737B424; Sat, 23 Sep 2000 16:00:04 -0700 (PDT) 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 e8NN00g06265 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Sun, 24 Sep 2000 01:00:02 +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 e8NN0G518938; Sun, 24 Sep 2000 01:00:16 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.11.0/8.9.2) id e8NN0GK68893; Sun, 24 Sep 2000 01:00:16 +0200 (CEST) (envelope-from ticso) Date: Sun, 24 Sep 2000 01:00:15 +0200 From: Bernd Walter To: John Baldwin Cc: smp@FreeBSD.ORG, cp@bsdi.com, alpha@FreeBSD.ORG Subject: Re: Status update Message-ID: <20000924010015.A68775@cicely8.cicely.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from jhb@FreeBSD.ORG on Sat, Sep 23, 2000 at 12:34:22AM -0700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Sep 23, 2000 at 12:34:22AM -0700, John Baldwin wrote: > I'll be updating my patchset at > http://www.FreeBSD.org/~jhb/patches/alpha.ithreads.patch shortly. If you have > time, please test this stuff out so we can get it committed. Thanks. It still doesn't work for me: 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 5.0-CURRENT #0: Sun Sep 24 00:14:11 CEST 2000 ticso@cicely9.cicely.de:/var/d7/src-2000-09-23/src/sys/compile/CICELY9 EB164 Digital AlphaPC 164 500 MHz, 500MHz 8192 byte page size, 1 processor. CPU: EV56 (21164A) major=7 minor=2 extensions=0x1 OSF PAL rev: 0x1000800020117 real memory = 265904128 (259672K bytes) avail memory = 253419520 (247480K bytes) Preloaded elf kernel "kernel.ko" at 0xfffffc0000628000. ../../kern/kern_fork.c:537:fork1() spl0 needs fixing cia0: <2117x Core Logic chipset> cia0: ALCOR/ALCOR2, pass 3 cia0: extended capabilities: 21 pcib0: <2117x PCI host bus adapter> on cia0 pci0: on pcib0 sym0: <895> port 0x10200-0x102ff mem 0x82030000-0x82030fff,0x82031200-0x820312ff irq 2 at device 5.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: interrupting at CIA irq 2 sym1: <810a> port 0x10100-0x101ff mem 0x82031100-0x820311ff irq 0 at device 6.0 on pci0 sym1: No NVRAM, ID 7, Fast-10, SE, parity checking sym1: interrupting at CIA irq 0 sym2: <810a> port 0x10000-0x100ff mem 0x82031000-0x820310ff irq 1 at device 7.0 on pci0 sym2: No NVRAM, ID 7, Fast-10, SE, parity checking sym2: interrupting at CIA irq 1 isab0: at device 8.0 on pci0 isa0: on isab0 xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0x10300-0x1037f mem 0x82031300-0x8203137f irq 3 at device 9.0 on pci0 xl0: interrupting at CIA irq 3 xl0: Ethernet address: 00:10:5a:30:1c:1a miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto atapci0: port 0x10380-0x1038f irq 5 at device 11.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: interrupting at ISA irq 14 fdc0: cannot reserve I/O port range mcclock0: at port 0x70-0x71 on isa0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A, console sio0: interrupting at ISA irq 4 sio1: reserved for low-level i/o Timecounter "i8254" frequency 1193182 Hz Timecounter "alpha" frequency 500006125 Hz ad0: 1219MB [2477/16/63] at ata0-master WDMA2 Waiting 15 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. And nothing more happens... boot -v shows this: [...] ata0-master: success setting WDMA2 on CMD646 chip ad0: ATA-0 disk at ata0-master ad0: 1219MB (2496816 sectors), 2477 cyls, 16 heads, 63 S/T, 512 B/S ad0: 1 secs/int, 1 depth queue, WDMA2 ad0: piomode=4 dmamode=2 udmamode=-1 cblid=0 Creating DISK ad0 Waiting 15 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. sym0: enabling clock multiplier sym0: Downloading SCSI SCRIPTS. (noperiph:sym1:0:-1:-1): SCSI BUS reset delivered. (noperiph:sym2:0:-1:-1): SCSI BUS reset delivered. (probe15:sym1:0:0:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe15:sym1:0:0:0): ILLEGAL REQUEST asc:24,0 (probe15:sym1:0:0:0): Invalid field in CDB sks:c0,2 (probe16:sym1:0:1:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe16:sym1:0:1:0): ILLEGAL REQUEST asc:24,0 (probe16:sym1:0:1:0): Invalid field in CDB sks:c0,2 (probe17:sym1:0:2:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe17:sym1:0:2:0): ILLEGAL REQUEST asc:24,0 (probe17:sym1:0:2:0): Invalid field in CDB sks:c0,2 (probe18:sym1:0:3:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe18:sym1:0:3:0): ILLEGAL REQUEST asc:24,0 (probe18:sym1:0:3:0): Invalid field in CDB sks:c0,2 (probe19:sym1:0:4:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe19:sym1:0:4:0): ILLEGAL REQUEST asc:24,0 (probe19:sym1:0:4:0): Invalid field in CDB sks:c0,2 The SCSI messages are normal for the disks. Sometimes it comes to print the first SCSI "Creating Disk" lines. -- 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 Sat Sep 23 16: 0: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 0109337B42C; Sat, 23 Sep 2000 16:00:14 -0700 (PDT) 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 e8NN00g06265 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Sun, 24 Sep 2000 01:00:02 +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 e8NN0G518938; Sun, 24 Sep 2000 01:00:16 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.11.0/8.9.2) id e8NN0GK68893; Sun, 24 Sep 2000 01:00:16 +0200 (CEST) (envelope-from ticso) Date: Sun, 24 Sep 2000 01:00:15 +0200 From: Bernd Walter To: John Baldwin Cc: smp@FreeBSD.ORG, cp@bsdi.com, alpha@FreeBSD.ORG Subject: Re: Status update Message-ID: <20000924010015.A68775@cicely8.cicely.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from jhb@FreeBSD.ORG on Sat, Sep 23, 2000 at 12:34:22AM -0700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Sep 23, 2000 at 12:34:22AM -0700, John Baldwin wrote: > I'll be updating my patchset at > http://www.FreeBSD.org/~jhb/patches/alpha.ithreads.patch shortly. If you have > time, please test this stuff out so we can get it committed. Thanks. It still doesn't work for me: 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 5.0-CURRENT #0: Sun Sep 24 00:14:11 CEST 2000 ticso@cicely9.cicely.de:/var/d7/src-2000-09-23/src/sys/compile/CICELY9 EB164 Digital AlphaPC 164 500 MHz, 500MHz 8192 byte page size, 1 processor. CPU: EV56 (21164A) major=7 minor=2 extensions=0x1 OSF PAL rev: 0x1000800020117 real memory = 265904128 (259672K bytes) avail memory = 253419520 (247480K bytes) Preloaded elf kernel "kernel.ko" at 0xfffffc0000628000. ../../kern/kern_fork.c:537:fork1() spl0 needs fixing cia0: <2117x Core Logic chipset> cia0: ALCOR/ALCOR2, pass 3 cia0: extended capabilities: 21 pcib0: <2117x PCI host bus adapter> on cia0 pci0: on pcib0 sym0: <895> port 0x10200-0x102ff mem 0x82030000-0x82030fff,0x82031200-0x820312ff irq 2 at device 5.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: interrupting at CIA irq 2 sym1: <810a> port 0x10100-0x101ff mem 0x82031100-0x820311ff irq 0 at device 6.0 on pci0 sym1: No NVRAM, ID 7, Fast-10, SE, parity checking sym1: interrupting at CIA irq 0 sym2: <810a> port 0x10000-0x100ff mem 0x82031000-0x820310ff irq 1 at device 7.0 on pci0 sym2: No NVRAM, ID 7, Fast-10, SE, parity checking sym2: interrupting at CIA irq 1 isab0: at device 8.0 on pci0 isa0: on isab0 xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0x10300-0x1037f mem 0x82031300-0x8203137f irq 3 at device 9.0 on pci0 xl0: interrupting at CIA irq 3 xl0: Ethernet address: 00:10:5a:30:1c:1a miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto atapci0: port 0x10380-0x1038f irq 5 at device 11.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: interrupting at ISA irq 14 fdc0: cannot reserve I/O port range mcclock0: at port 0x70-0x71 on isa0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A, console sio0: interrupting at ISA irq 4 sio1: reserved for low-level i/o Timecounter "i8254" frequency 1193182 Hz Timecounter "alpha" frequency 500006125 Hz ad0: 1219MB [2477/16/63] at ata0-master WDMA2 Waiting 15 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. And nothing more happens... boot -v shows this: [...] ata0-master: success setting WDMA2 on CMD646 chip ad0: ATA-0 disk at ata0-master ad0: 1219MB (2496816 sectors), 2477 cyls, 16 heads, 63 S/T, 512 B/S ad0: 1 secs/int, 1 depth queue, WDMA2 ad0: piomode=4 dmamode=2 udmamode=-1 cblid=0 Creating DISK ad0 Waiting 15 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. sym0: enabling clock multiplier sym0: Downloading SCSI SCRIPTS. (noperiph:sym1:0:-1:-1): SCSI BUS reset delivered. (noperiph:sym2:0:-1:-1): SCSI BUS reset delivered. (probe15:sym1:0:0:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe15:sym1:0:0:0): ILLEGAL REQUEST asc:24,0 (probe15:sym1:0:0:0): Invalid field in CDB sks:c0,2 (probe16:sym1:0:1:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe16:sym1:0:1:0): ILLEGAL REQUEST asc:24,0 (probe16:sym1:0:1:0): Invalid field in CDB sks:c0,2 (probe17:sym1:0:2:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe17:sym1:0:2:0): ILLEGAL REQUEST asc:24,0 (probe17:sym1:0:2:0): Invalid field in CDB sks:c0,2 (probe18:sym1:0:3:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe18:sym1:0:3:0): ILLEGAL REQUEST asc:24,0 (probe18:sym1:0:3:0): Invalid field in CDB sks:c0,2 (probe19:sym1:0:4:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe19:sym1:0:4:0): ILLEGAL REQUEST asc:24,0 (probe19:sym1:0:4:0): Invalid field in CDB sks:c0,2 The SCSI messages are normal for the disks. Sometimes it comes to print the first SCSI "Creating Disk" lines. -- 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