From owner-freebsd-alpha Sun Sep 24 4:31:27 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id BBD1737B424; Sun, 24 Sep 2000 04:31:23 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 13dA09-000GJU-0K; Sun, 24 Sep 2000 11:31:22 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id MAA66367; Sun, 24 Sep 2000 12:35:24 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 24 Sep 2000 12:31:34 +0100 (BST) From: Doug Rabson 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 On Fri, 22 Sep 2000, John Baldwin wrote: > > 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. Does this fix the hang you were seeing before? I'm hoping its the same problem which was hanging the the rawhide when I was trying to get the ithreads changes to dxlpx to work. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Sep 24 10:10:29 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.gplsucks.org (mail.gplsucks.org [63.227.213.93]) by hub.freebsd.org (Postfix) with ESMTP id ABDCB37B42C for ; Sun, 24 Sep 2000 10:10:27 -0700 (PDT) Received: from localhost (bwoods2@localhost) by mail.gplsucks.org (8.11.0/8.11.0) with ESMTP id e8OHAWB54498 for ; Sun, 24 Sep 2000 10:10:32 -0700 (PDT) Date: Sun, 24 Sep 2000 10:10:31 -0700 (PDT) From: William Woods To: freebsd-alpha@freebsd.org Subject: mysql on alpha? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does the Mysql port compile on a Alpha? Thanks, Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Sep 24 10:17:59 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from femail3.sdc1.sfba.home.com (femail3.sdc1.sfba.home.com [24.0.95.83]) by hub.freebsd.org (Postfix) with ESMTP id 9C9E637B422 for ; Sun, 24 Sep 2000 10:17:58 -0700 (PDT) Received: from home.net ([24.0.178.21]) by femail3.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000924171712.IEDH27591.femail3.sdc1.sfba.home.com@home.net>; Sun, 24 Sep 2000 10:17:12 -0700 Message-ID: <39CE3881.477D6371@home.net> Date: Sun, 24 Sep 2000 10:23:13 -0700 From: Craig Burgess X-Mailer: Mozilla 4.72 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: William Woods Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: mysql on 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 Yes. William Woods wrote: > > Does the Mysql port compile on a Alpha? > > Thanks, > > Bill > -- ... mind like a steel trap: things wander in and get mangled ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Sep 24 10:53:17 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mailout04.sul.t-online.com (mailout04.sul.t-online.com [194.25.134.18]) by hub.freebsd.org (Postfix) with ESMTP id EC76C37B424 for ; Sun, 24 Sep 2000 10:53:10 -0700 (PDT) Received: from fmrl02.sul.t-online.de by mailout04.sul.t-online.com with smtp id 13dFxa-0000Y1-00; Sun, 24 Sep 2000 19:53:06 +0200 Received: from neutron.cichlids.com (520050424122-0001@[62.158.38.14]) by fmrl02.sul.t-online.com with esmtp id 13dFxP-11ytXMC; Sun, 24 Sep 2000 19:52:55 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id B3A9FAB91 for ; Sun, 24 Sep 2000 19:53:23 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 9797514AFD; Sun, 24 Sep 2000 19:52:55 +0200 (CEST) Date: Sun, 24 Sep 2000 19:52:55 +0200 To: alpha@freebsd.org Subject: loader problem Message-ID: <20000924195255.A30987@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. From: alex@big.endian.de (Alexander Langer) X-Sender: 520050424122-0001@t-dialin.net Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello!" I tried to update my -current today. That's what I have now: >>>boot (boot dka0.0.0.5.0 -file kernel) block 0 of dka0.0.0.5.0 is a valid boot block reading 15 blocks from dka0.0.0.5.0 bootstrap code read in base = 112000, image_start = 0, image_bytes = 1e00 initializing HWRPB at 2000 initializing page table at 104000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code Loading /boot/loader / halted CPU 0 halt code = 2 kernel stack not valid halt PC = 2389ead1a6a93af0 >>> Cool. Any suggestion what to do now?-) Thanks IA Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Sep 24 11:26:43 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 D13B737B42C for ; Sun, 24 Sep 2000 11:26:38 -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 e8OIQAR28814 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Sun, 24 Sep 2000 20:26:19 +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 e8OIQP521370; Sun, 24 Sep 2000 20:26:27 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.11.0/8.9.2) id e8OIQPn70309; Sun, 24 Sep 2000 20:26:25 +0200 (CEST) (envelope-from ticso) Date: Sun, 24 Sep 2000 20:26:24 +0200 From: Bernd Walter To: Alexander Langer Cc: alpha@FreeBSD.ORG Subject: Re: loader problem Message-ID: <20000924202624.A70289@cicely8.cicely.de> References: <20000924195255.A30987@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000924195255.A30987@cichlids.cichlids.com>; from alex@big.endian.de on Sun, Sep 24, 2000 at 07:52:55PM +0200 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Sep 24, 2000 at 07:52:55PM +0200, Alexander Langer wrote: > Hello!" > > I tried to update my -current today. > > That's what I have now: > > >>>boot > (boot dka0.0.0.5.0 -file kernel) > block 0 of dka0.0.0.5.0 is a valid boot block > reading 15 blocks from dka0.0.0.5.0 > bootstrap code read in > base = 112000, image_start = 0, image_bytes = 1e00 > initializing HWRPB at 2000 > initializing page table at 104000 > initializing machine state > setting affinity to the primary CPU > jumping to bootstrap code > Loading /boot/loader > / > halted CPU 0 > > halt code = 2 > kernel stack not valid halt > PC = 2389ead1a6a93af0 > >>> > > Cool. Any suggestion what to do now?-) Did you disklabel -B ? For me it worked and stoped because of a missing /boot/kernel/kernel.ko. no magic as the kernel got installed without ending in .ko ;( boot from cdrom - I got it working with burning the 100M disk from another alpha onto a cdrom. If you have a fixit cdrom it's much easier. Maybe you can also win if you have an older loader on the disk with pressing 'space' quite after the "jumping to bootstrap code" message and entering the pathname. -- 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 24 14: 5:17 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 AEC4337B42C for ; Sun, 24 Sep 2000 14:05:13 -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 OAA95724; Sun, 24 Sep 2000 14:07:37 -0700 (PDT) (envelope-from john@baldwin.cx) Received: (from john@localhost) by john.baldwin.cx (8.9.3/8.9.3) id OAA53607; Sun, 24 Sep 2000 14:06:56 -0700 (PDT) (envelope-from john) Message-Id: <200009242106.OAA53607@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, 24 Sep 2000 14:06:56 -0700 (PDT) From: John Baldwin To: Doug Rabson Subject: RE: Ithreads kernel weirdness Cc: alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 24-Sep-00 Doug Rabson wrote: > On Fri, 22 Sep 2000, John Baldwin wrote: > >> >> 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. > > Does this fix the hang you were seeing before? I'm hoping its the same > problem which was hanging the the rawhide when I was trying to get the > ithreads changes to dxlpx to work. Yes. Actually, it looks like the kproc's (syncer, for example) are starting off with a saved PSR that has an IPL != 0 in them. I'm going to be looking at this some more today. -- 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 24 17: 8:51 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 3A98F37B424 for ; Sun, 24 Sep 2000 17:08:49 -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 e8P08Pi17924; Sun, 24 Sep 2000 17:08:25 -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 e8P06sj29257; Sun, 24 Sep 2000 17:06:54 -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: <200009242106.OAA53607@john.baldwin.cx> Date: Sun, 24 Sep 2000 17:06:54 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: alpha@FreeBSD.ORG Subject: RE: Ithreads kernel weirdness Cc: Doug Rabson Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 24-Sep-00 John Baldwin wrote: >> Does this fix the hang you were seeing before? I'm hoping its the same >> problem which was hanging the the rawhide when I was trying to get the >> ithreads changes to dxlpx to work. > > Yes. Actually, it looks like the kproc's (syncer, for example) are > starting off with a saved PSR that has an IPL != 0 in them. I'm going > to be looking at this some more today. Ok, the problem was that when a new process started, it called exception_restart() with a recursed sched_lock. The MTX_EXIT() macro assumed that the sched_lock it was getting was not recursed (which it didnt need to be for the return path that a new process uses), however, it didn't update the mtx_recurse counter. Thus, the next time the sched_lock was obtained and released, the release thought it was unrecursing, and didn't fully release the sched_lock, thus leaving interrupts disabled still. The "fix" is to have the MTX_EXIT() macro explicitly set the recursion count to 0 when it releases the mutex. An updated patch should be up at http://www.FreeBSD.org/~jhb/patches/alpha.ithreads.patch in a few minutes. It has lots of debugging printf()'s after spl0's to make sure that interrupts are actually enabled after spl0's (as they always were back when spl's did something). You shouldn't see any of these kernel printf's referencing spl0. If you do, it's a bug. :P -- 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 24 22:25:28 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from master.telia.net (master.telia.net [194.237.170.70]) by hub.freebsd.org (Postfix) with ESMTP id CEF9B37B424 for ; Sun, 24 Sep 2000 22:25:24 -0700 (PDT) Received: from localhost (elite@localhost) by master.telia.net (8.9.3/8.9.1) with ESMTP id HAA20908; Mon, 25 Sep 2000 07:24:52 +0200 (CEST) (envelope-from khaled@w-arts.com) X-Authentication-Warning: master.telia.net: elite owned process doing -bs Date: Mon, 25 Sep 2000 07:24:51 +0200 (CEST) From: Khaled Daham X-Sender: elite@master.telia.net To: William Woods Cc: freebsd-alpha@freebsd.org Subject: Re: mysql on 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, 24 Sep 2000, William Woods wrote: > Does the Mysql port compile on a Alpha? > > Thanks, > > Bill > Yes and more importantly PostgreSQL too :) /Khaled Daham, w.arts Mail: khaled@w-arts.com Cell: +46-70-6785492, +966-54491462 FreeBSD: 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 25 1:49:49 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 F322237B422; Mon, 25 Sep 2000 01:49:44 -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 13dTxD-000PvI-0V; Mon, 25 Sep 2000 09:49:40 +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 JAA69908; Mon, 25 Sep 2000 09:53:55 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 25 Sep 2000 09:49:51 +0100 (BST) From: Doug Rabson To: John Baldwin Cc: alpha@freebsd.org Subject: RE: Ithreads kernel weirdness In-Reply-To: <200009242106.OAA53607@john.baldwin.cx> 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, 24 Sep 2000, John Baldwin wrote: > > On 24-Sep-00 Doug Rabson wrote: > > On Fri, 22 Sep 2000, John Baldwin wrote: > > > >> > >> 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. > > > > Does this fix the hang you were seeing before? I'm hoping its the same > > problem which was hanging the the rawhide when I was trying to get the > > ithreads changes to dxlpx to work. > > Yes. Actually, it looks like the kproc's (syncer, for example) are > starting off with a saved PSR that has an IPL != 0 in them. I'm going > to be looking at this some more today. Hmm. Possibly cpu_fork needs to fiddle with the savepsr's of the child? -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Sep 25 1:56:11 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by hub.freebsd.org (Postfix) with ESMTP id 9F77B37B42C; Mon, 25 Sep 2000 01:56:08 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1) id 13dU3S-000Njx-0X; Mon, 25 Sep 2000 09:56:07 +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 KAA69965; Mon, 25 Sep 2000 10:00:00 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 25 Sep 2000 09:55:56 +0100 (BST) From: Doug Rabson 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 On Sun, 24 Sep 2000, John Baldwin wrote: > > On 24-Sep-00 John Baldwin wrote: > >> Does this fix the hang you were seeing before? I'm hoping its the same > >> problem which was hanging the the rawhide when I was trying to get the > >> ithreads changes to dxlpx to work. > > > > Yes. Actually, it looks like the kproc's (syncer, for example) are > > starting off with a saved PSR that has an IPL != 0 in them. I'm going > > to be looking at this some more today. > > Ok, the problem was that when a new process started, it called > exception_restart() with a recursed sched_lock. The MTX_EXIT() > macro assumed that the sched_lock it was getting was not recursed > (which it didnt need to be for the return path that a new process > uses), however, it didn't update the mtx_recurse counter. Thus, > the next time the sched_lock was obtained and released, the release > thought it was unrecursing, and didn't fully release the sched_lock, > thus leaving interrupts disabled still. The "fix" is to have the > MTX_EXIT() macro explicitly set the recursion count to 0 when it > releases the mutex. An updated patch should be up at > http://www.FreeBSD.org/~jhb/patches/alpha.ithreads.patch in a few > minutes. It has lots of debugging printf()'s after spl0's to > make sure that interrupts are actually enabled after spl0's (as > they always were back when spl's did something). You shouldn't > see any of these kernel printf's referencing spl0. If you do, it's > a bug. :P Woo. Good sleuthing. I'll have to update my IA64 version of MTX_EXIT to do the right thing :-). Alternatively, cpu_fork should clear pcb_schednest. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Sep 25 8:22:55 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 E49A037B42C; Mon, 25 Sep 2000 08:22:43 -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 NAA13395; Sun, 24 Sep 2000 13:59:45 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e8OHxjM21733; Sun, 24 Sep 2000 13:59:45 -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: Sun, 24 Sep 2000 13:59:44 -0400 (EDT) To: John Baldwin Cc: alpha@freebsd.org Subject: Re: Status update In-Reply-To: <200009231755.KAA51845@john.baldwin.cx> References: <200009231727.LAA17839@berserker.bsdi.com> <200009231755.KAA51845@john.baldwin.cx> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14798.14987.25117.33017@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John, I just tried your latest patchset on an API UP1000. (MD5 (alpha.ithreads.patch) = 11d809b59741189c7261be15166e2519) It locks solid after printing the copyright: FreeBSD/alpha SRM disk boot, Revision 0.3 (root@thunder.cs.duke.edu, Tue Aug 29 11:44:06 EDT 2000) Memory: 131072 k <...> ok unload kernel ok load kernel.ithreads /kernel.ithreads data=0x3c8c98+0x327a8 syms=[0x8+0x4eeb8+0x8+0x393ce] ok boot Entering kernel.ithreads at 0xfffffc0000330780... 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. This is with both serial & graphics console. The UP1000 uses the irongate chipset & routes all interrupts through isa. I tried adding an isa_{dis,en}able_intr() functions and replacing the enable/disable args to alpha_setup_intr() in isa_setup_intr(), but it didn't seem to have any affect. The box doesn't have a halt switch, so I cannot determine exacly where it is locking up. Do you have any ideas? Thanks, Drew PS: Config file is basically generic, plus static hints, plus your suggested debugging flags: --- GENERIC Wed Sep 20 13:30:20 2000 +++ ITHREADS Sun Sep 24 13:49:45 2000 @@ -24,11 +24,11 @@ machine alpha cpu EV4 cpu EV5 -ident GENERIC +ident ITHREADS maxusers 32 #To statically compile in device wiring instead of /boot/device.hints -#hints "GENERIC.hints" +hints "ITHREADS.hints" #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols @@ -63,7 +63,7 @@ options CD9660_ROOT #CD-ROM usable as root device options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] -options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI +options SCSI_DELAY=1500 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory @@ -182,3 +182,8 @@ device aue # ADMtek USB ethernet device cue # CATC USB ethernet device kue # Kawasaki LSI USB ethernet +options SMP_DEBUG +options DIAGNOSTIC +options INVARIANTS +options INVARIANT_SUPPORT + To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Sep 25 9: 7:33 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 907F837B42C for ; Mon, 25 Sep 2000 09:07:22 -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 e8PG7Hi38604; Mon, 25 Sep 2000 09:07:17 -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 e8PG5Ok36068; Mon, 25 Sep 2000 09:05:24 -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: <20000925135319.3173837B424@hub.freebsd.org> Date: Mon, 25 Sep 2000 09:05:24 -0700 (PDT) From: John Baldwin To: gallatin@cs.buffalo.edu Subject: RE: ithreads on UP1000 Cc: alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 25-Sep-00 Andrew Gallatin wrote: > > (apol;ogies if you get 2 copies of this, mail @ Freebsd is pretty flaky > for me right now) > > John, > > I just tried your latest patchset on an API UP1000. > (MD5 (alpha.ithreads.patch) = 11d809b59741189c7261be15166e2519) Try it without static hints. Some people have been having problems with static hints. Also, if dynamic hints works ok for you, please do an nm of your kernel and see where the hints_loaded variable shows up in the list. Esp. in relation to sched_lock and Giant in the BSS. It seems that we may have a bug in the mutex code that trashes the memory just before a mutex. :-/ It's been reported on the x86, and the mutex code is almost identical in the two platforms. > It locks solid after printing the copyright: > FreeBSD/alpha SRM disk boot, Revision 0.3 > (root@thunder.cs.duke.edu, Tue Aug 29 11:44:06 EDT 2000) > Memory: 131072 k > <...> > ok unload kernel > ok load kernel.ithreads > /kernel.ithreads data=0x3c8c98+0x327a8 syms=[0x8+0x4eeb8+0x8+0x393ce] > ok boot > Entering kernel.ithreads at 0xfffffc0000330780... > 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. > > > > This is with both serial & graphics console. > > The UP1000 uses the irongate chipset & routes all interrupts through > isa. I tried adding an isa_{dis,en}able_intr() functions and > replacing the enable/disable args to alpha_setup_intr() in > isa_setup_intr(), but it didn't seem to have any affect. The box > doesn't have a halt switch, so I cannot determine exacly where it is > locking up. > > Do you have any ideas? > > Thanks, > > Drew > > PS: > > Config file is basically generic, plus static hints, plus your > suggested debugging flags: > > --- GENERIC Wed Sep 20 13:30:20 2000 > +++ ITHREADS Sun Sep 24 13:49:45 2000 > @@ -24,11 +24,11 @@ > machine alpha > cpu EV4 > cpu EV5 > -ident GENERIC > +ident ITHREADS > maxusers 32 > > #To statically compile in device wiring instead of /boot/device.hints > -#hints "GENERIC.hints" > +hints "ITHREADS.hints" > > #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols > > @@ -63,7 +63,7 @@ > options CD9660_ROOT #CD-ROM usable as root device > options PROCFS #Process filesystem > options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] > -options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI > +options SCSI_DELAY=1500 #Delay (in ms) before probing SCSI > options UCONSOLE #Allow users to grab the console > options KTRACE #ktrace(1) syscall trace support > options SYSVSHM #SYSV-style shared memory > @@ -182,3 +182,8 @@ > device aue # ADMtek USB ethernet > device cue # CATC USB ethernet > device kue # Kawasaki LSI USB ethernet > +options SMP_DEBUG > +options DIAGNOSTIC > +options INVARIANTS > +options INVARIANT_SUPPORT > + > > > Drew -- 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 Tue Sep 26 1:32:55 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by hub.freebsd.org (Postfix) with ESMTP id 7BE6C37B424; Tue, 26 Sep 2000 01:32:48 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1) id 13dqAQ-0003bt-0X; Tue, 26 Sep 2000 09:32:47 +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 JAA74959; Tue, 26 Sep 2000 09:36:51 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 26 Sep 2000 09:32:32 +0100 (BST) From: Doug Rabson To: John Baldwin Cc: smp@freebsd.org, cp@bsdi.com, alpha@freebsd.org Subject: Re: Status update 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, 23 Sep 2000, John Baldwin wrote: > 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: > > - 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. I think this is probably unnecessary. After implementing swi threads, the only place in the kernel where ipl will be non-zero when sched_lock is taken should be in the interrupt code and I don't think a context switch is possible there until the AST after returning. > > 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'm testing this now and I'm seeing a flood of diagnostic messages like: ../../kern/kern_fork.c:537:fork1() spl0 needs fixing I think these are all due to the fact that sched_lock is held at that point. The preceding mtx_exit() just decrements the recursion count. I haven't worked out exactly why sched_lock is held here because it shouldn't be. Possibly its because we don't clear pcb_schednest in cpu_fork(). -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Sep 26 1:49:29 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by hub.freebsd.org (Postfix) with ESMTP id A34AC37B42C; Tue, 26 Sep 2000 01:49:24 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 13dqQS-000B5T-0B; Tue, 26 Sep 2000 08:49:23 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA75095; Tue, 26 Sep 2000 09:53:49 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 26 Sep 2000 09:49:30 +0100 (BST) From: Doug Rabson To: John Baldwin Cc: smp@freebsd.org, cp@bsdi.com, alpha@freebsd.org Subject: Re: Status update 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 Tue, 26 Sep 2000, Doug Rabson wrote: > On Sat, 23 Sep 2000, John Baldwin wrote: > > > > 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'm testing this now and I'm seeing a flood of diagnostic messages like: > > ../../kern/kern_fork.c:537:fork1() spl0 needs fixing > > I think these are all due to the fact that sched_lock is held at that > point. The preceding mtx_exit() just decrements the recursion count. > I haven't worked out exactly why sched_lock is held here because it > shouldn't be. Possibly its because we don't clear pcb_schednest in > cpu_fork(). As I suspected, clearing pcb_schednest makes this lot go away. Try this version of vm_machdep.c: Index: vm_machdep.c =================================================================== RCS file: /home/ncvs/src/sys/alpha/alpha/vm_machdep.c,v retrieving revision 1.33 diff -u -r1.33 vm_machdep.c --- vm_machdep.c 2000/09/07 01:32:39 1.33 +++ vm_machdep.c 2000/09/26 08:38:55 @@ -210,6 +210,13 @@ up->u_pcb.pcb_context[2] = (u_long) p2; /* s2: a0 */ up->u_pcb.pcb_context[7] = (u_int64_t)switch_trampoline; /* ra: assembly magic */ + + /* + * Clear the saved recursion count for sched_lock + * since the child needs only one count which is + * released in switch_trampoline. + */ + up->u_pcb.pcb_schednest = 0; } } -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Sep 26 9:41:24 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id BA5C037B424 for ; Tue, 26 Sep 2000 09:41:11 -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 MAA22321; Tue, 26 Sep 2000 12:41:09 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e8QGf8V29116; Tue, 26 Sep 2000 12:41:08 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 26 Sep 2000 12:41:08 -0400 (EDT) To: jhb@osd.bsdi.com Cc: alpha@FreeBSD.ORG Subject: RE: ithreads on UP1000 In-Reply-To: References: <20000925135319.3173837B424@hub.freebsd.org> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14800.47994.288410.1680@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John Baldwin writes: > > On 25-Sep-00 Andrew Gallatin wrote: > > > > (apol;ogies if you get 2 copies of this, mail @ Freebsd is pretty flaky > > for me right now) > > > > John, > > > > I just tried your latest patchset on an API UP1000. > > (MD5 (alpha.ithreads.patch) = 11d809b59741189c7261be15166e2519) > > Try it without static hints. Some people have been having problems with > static hints. Also, if dynamic hints works ok for you, please do an > nm of your kernel and see where the hints_loaded variable shows up in the > list. Esp. in relation to sched_lock and Giant in the BSS. It seems that > we may have a bug in the mutex code that trashes the memory just before > a mutex. :-/ It's been reported on the x86, and the mutex code is almost > identical in the two platforms. It seems we have a similar, but slightly different problem. If I use your ithreads patch and a stock GENERIC config file, I boot past the copyright and the machine hangs mounting root (the scsi bus probes come back showing da0, though). This is progress ;) Howver, If I use any GENERIC kernel config plus +options DIAGNOSTIC +options INVARIANTS +options INVARIANT_SUPPORT The box locks after the copyright is printed. Eg, it locks with or without your ithreads patch. I can duplicate this on an AS500 5/266 which actually has a halt button. However, it doesn't seem to help as the box is locked so solidly that it ignores the halt button. Am I the only one seeing this? I'm using a fairly old loader (Tue Aug 29 11:44:06 EDT 2000) on the UP1000 and a truly ancient netboot loader on the AS500 (Sat Oct 16 11:02:54 EDT 1999). For the netboot, I've been seting the clock and sio0 hints manually.. Since we show every sign of falling off the edge of the universe after returning from the first sysinit (announce), I thought we might be running out of space on the bootstrap stack and I tried doubling the size of the bootstrap stack in alpha_init(), but it didn't seem to help. Are others seeing this, or am I going crazy? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Sep 26 15:26:54 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from finch-post-12.mail.demon.net (finch-post-12.mail.demon.net [194.217.242.41]) by hub.freebsd.org (Postfix) with ESMTP id 1C22C37B423 for ; Tue, 26 Sep 2000 15:26:35 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-12.mail.demon.net with esmtp (Exim 2.12 #1) id 13e3BH-00088Z-0C; Tue, 26 Sep 2000 22:26:32 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id XAA77025; Tue, 26 Sep 2000 23:30:56 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 26 Sep 2000 23:26:28 +0100 (BST) From: Doug Rabson To: Andrew Gallatin Cc: jhb@osd.bsdi.com, alpha@freebsd.org Subject: RE: ithreads on UP1000 In-Reply-To: <14800.47994.288410.1680@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 26 Sep 2000, Andrew Gallatin wrote: > > John Baldwin writes: > > > > On 25-Sep-00 Andrew Gallatin wrote: > > > > > > (apol;ogies if you get 2 copies of this, mail @ Freebsd is pretty flaky > > > for me right now) > > > > > > John, > > > > > > I just tried your latest patchset on an API UP1000. > > > (MD5 (alpha.ithreads.patch) = 11d809b59741189c7261be15166e2519) > > > > Try it without static hints. Some people have been having problems with > > static hints. Also, if dynamic hints works ok for you, please do an > > nm of your kernel and see where the hints_loaded variable shows up in the > > list. Esp. in relation to sched_lock and Giant in the BSS. It seems that > > we may have a bug in the mutex code that trashes the memory just before > > a mutex. :-/ It's been reported on the x86, and the mutex code is almost > > identical in the two platforms. > > It seems we have a similar, but slightly different problem. > > If I use your ithreads patch and a stock GENERIC config file, I boot > past the copyright and the machine hangs mounting root (the scsi bus > probes come back showing da0, though). This is progress ;) > > Howver, If I use any GENERIC kernel config plus > > +options DIAGNOSTIC > +options INVARIANTS > +options INVARIANT_SUPPORT > > The box locks after the copyright is printed. Eg, it locks with or > without your ithreads patch. > > I can duplicate this on an AS500 5/266 which actually has a halt > button. However, it doesn't seem to help as the box is locked so > solidly that it ignores the halt button. > > Am I the only one seeing this? I'm using a fairly old loader (Tue Aug > 29 11:44:06 EDT 2000) on the UP1000 and a truly ancient netboot loader > on the AS500 (Sat Oct 16 11:02:54 EDT 1999). For the netboot, I've > been seting the clock and sio0 hints manually.. > > Since we show every sign of falling off the edge of the universe after > returning from the first sysinit (announce), I thought we might be > running out of space on the bootstrap stack and I tried doubling the > size of the bootstrap stack in alpha_init(), but it didn't seem to > help. We are running securely on proc0's stack before the first sysinit happens (i.e. alpha_init() has returned and we have switched to proc0's context). > > Are others seeing this, or am I going crazy? I haven't seen this but I haven't tried exactly this configuration yet. I'll try to reproduce it. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Sep 26 23:23:24 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.gplsucks.org (mail.gplsucks.org [63.227.213.93]) by hub.freebsd.org (Postfix) with ESMTP id 29D3237B422 for ; Tue, 26 Sep 2000 23:23:23 -0700 (PDT) Received: from localhost (bwoods2@localhost) by mail.gplsucks.org (8.11.0/8.11.0) with ESMTP id e8R6Nrr06126 for ; Tue, 26 Sep 2000 23:23:53 -0700 (PDT) Date: Tue, 26 Sep 2000 23:23:52 -0700 (PDT) From: William Woods To: freebsd-alpha@freebsd.org Subject: 4.1.1 ISO for Alpha ?? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org IS there going to be a 4.1.1 ISO for the Alpha platform ? Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Sep 27 12:27:56 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id AFC8B37B423 for ; Wed, 27 Sep 2000 12:27:54 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id MAA49303; Wed, 27 Sep 2000 12:27:29 -0700 (PDT) (envelope-from obrien) Date: Wed, 27 Sep 2000 12:27:29 -0700 From: "David O'Brien" To: William Woods Cc: freebsd-alpha@freebsd.org Subject: Re: 4.1.1 ISO for Alpha ?? Message-ID: <20000927122729.A49280@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from bwoods2@uswest.net on Tue, Sep 26, 2000 at 11:23:52PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Sep 26, 2000 at 11:23:52PM -0700, William Woods wrote: > IS there going to be a 4.1.1 ISO for the Alpha platform ? Yes. It will take a couple of days -- we don't have as many scratch Alphas laying around as we do x86 boxes -- thus there is a delay getting one freed up to do the release on. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Sep 28 11:18:36 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.159.1.85]) by hub.freebsd.org (Postfix) with ESMTP id 7A6CD37B422 for ; Thu, 28 Sep 2000 11:18:33 -0700 (PDT) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id TAA03201 for freebsd-alpha@freebsd.org; Thu, 28 Sep 2000 19:18:29 +0100 (BST) (envelope-from geoffb) Date: Thu, 28 Sep 2000 19:18:29 +0100 From: Geoff Buckingham To: freebsd-alpha@freebsd.org Subject: Hardware/Software Multia/UDB questions Message-ID: <20000928191829.A3154@chuggalug.clues.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I purchased a Multia 18-24 months ago, managed to get it up and running FreeBSD for about a month when it died. I have finally got around to ordering the replacment logic IC and now have a few questions. (Anyone looking for the part in the UK search for the suggested replacement parts from the NetBSD Multia FAQ at http://rsweb.com) On the Hardware front: I have just stumbled accross a refernce to replacing six resistor networks in addition to the Logic IC, is this a common problem? I have just knocked what looks like I diode off the base of the board it is labeled 10-35 EN does anybody know of a replacement part as it has nothing left to solder :-( On the FreeBSD front, does the onboard TGA still get mistaken for VGA by the console and hanging kernels with the VGA support compiled in? I have seen (on the linux alpha lists) folks running a VGA console and X on a card in the PCI slot, anyone got this working under FreeBSD? -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Sep 28 11:25: 3 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id 929F337B424 for ; Thu, 28 Sep 2000 11:24:51 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8SIQEA01703; Thu, 28 Sep 2000 11:26:14 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009281826.e8SIQEA01703@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Geoff Buckingham Cc: freebsd-alpha@freebsd.org Subject: Re: Hardware/Software Multia/UDB questions In-reply-to: Your message of "Thu, 28 Sep 2000 19:18:29 BST." <20000928191829.A3154@chuggalug.clues.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 Sep 2000 11:26:14 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I purchased a Multia 18-24 months ago, managed to get it up and running > FreeBSD for about a month when it died. Heh. 8) That's a pretty good run. > I have finally got around to ordering the replacment logic IC and now > have a few questions. I have a question - did you get a new (faster) fan? > On the Hardware front: > > I have just stumbled accross a refernce to replacing six resistor networks > in addition to the Logic IC, is this a common problem? I haven't met this one. Typically they're not going to be damaged, but there are possibly other good reasons for this. > I have just knocked what looks like I diode off the base of the board > it is labeled 10-35 EN does anybody know of a replacement part as it has > nothing left to solder :-( This is a 10u 35v tantalum capacitor. The banded side was +ve (if you can't remember which way around it went, and there are no markings on the board, you can probably safely assume that the -ve end of it went to ground. (Check with a beep meter.) > On the FreeBSD front, does the onboard TGA still get mistaken for VGA > by the console and hanging kernels with the VGA support compiled in? It never did. The problem was always people thinking that they had supported video when the kernel was just using the default SRM output vector. > I have seen (on the linux alpha lists) folks running a VGA console and > X on a card in the PCI slot, anyone got this working under FreeBSD? Not AFAIK. Not many of us put up with the Multias, I'd guess. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Sep 28 12: 3:12 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.159.1.85]) by hub.freebsd.org (Postfix) with ESMTP id 17F5A37B42C; Thu, 28 Sep 2000 12:03:04 -0700 (PDT) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id UAA03330; Thu, 28 Sep 2000 20:03:03 +0100 (BST) (envelope-from geoffb) Date: Thu, 28 Sep 2000 20:03:02 +0100 From: Geoff Buckingham To: Mike Smith Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Hardware/Software Multia/UDB questions Message-ID: <20000928200302.A3288@chuggalug.clues.com> References: <20000928191829.A3154@chuggalug.clues.com> <200009281826.e8SIQEA01703@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <200009281826.e8SIQEA01703@mass.osd.bsdi.com>; from Mike Smith on Thu, Sep 28, 2000 at 11:26:14AM -0700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Sep 28, 2000 at 11:26:14AM -0700, Mike Smith wrote: > > > > I purchased a Multia 18-24 months ago, managed to get it up and running > > FreeBSD for about a month when it died. > > Heh. 8) That's a pretty good run. > > > I have finally got around to ordering the replacment logic IC and now > > have a few questions. > > I have a question - did you get a new (faster) fan? > I Have been looking into this how much air does the original move, I have seen replacements that do 3.8 to 20 l/s Thanks -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Sep 28 13:57:24 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id 674AA37B43C for ; Thu, 28 Sep 2000 13:57:13 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8SKwZA02107; Thu, 28 Sep 2000 13:58:35 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009282058.e8SKwZA02107@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Geoff Buckingham Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Hardware/Software Multia/UDB questions In-reply-to: Your message of "Thu, 28 Sep 2000 20:03:02 BST." <20000928200302.A3288@chuggalug.clues.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 Sep 2000 13:58:35 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Thu, Sep 28, 2000 at 11:26:14AM -0700, Mike Smith wrote: > > > > > > I purchased a Multia 18-24 months ago, managed to get it up and running > > > FreeBSD for about a month when it died. > > > > Heh. 8) That's a pretty good run. > > > > > I have finally got around to ordering the replacment logic IC and now > > > have a few questions. > > > > I have a question - did you get a new (faster) fan? > > > I Have been looking into this how much air does the original move, I > have seen replacements that do 3.8 to 20 l/s The original is pretty anaemic; just get the fastest fan that you can, and remove the thermal sensor. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Sep 29 3:21:36 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from rios.sitaranetworks.com (rios.sitaranetworks.com [199.103.141.78]) by hub.freebsd.org (Postfix) with ESMTP id 6547837B423 for ; Fri, 29 Sep 2000 03:20:11 -0700 (PDT) Received: by rios.sitaranetworks.com with Internet Mail Service (5.5.2650.21) id ; Fri, 29 Sep 2000 06:23:33 -0400 Message-ID: <31269226357BD211979E00A0C9866DABE411FD@rios.sitaranetworks.com> From: Charles Richmond To: freebsd-alpha@FreeBSD.ORG Subject: RE: Hardware/Software Multia/UDB questions Date: Fri, 29 Sep 2000 06:23:25 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > -----Original Message----- > From: Mike Smith [mailto:msmith@FreeBSD.ORG] > Sent: Thursday, September 28, 2000 4:59 PM > To: Geoff Buckingham > Cc: freebsd-alpha@FreeBSD.ORG > Subject: Re: Hardware/Software Multia/UDB questions > > > > On Thu, Sep 28, 2000 at 11:26:14AM -0700, Mike Smith wrote: > > > > > > > > I purchased a Multia 18-24 months ago, managed to get > it up and running > > > > FreeBSD for about a month when it died. > > > > > > Heh. 8) That's a pretty good run. > > > > > > > I have finally got around to ordering the replacment > logic IC and now > > > > have a few questions. > > > > > > I have a question - did you get a new (faster) fan? > > > > > I Have been looking into this how much air does the original move, I > > have seen replacements that do 3.8 to 20 l/s > > The original is pretty anaemic; just get the fastest fan that > you can, > and remove the thermal sensor. > The internal drives generate a lot of heat for what is very little drive space (in today's world). Taking out the drive will do enough for the cooling. Mind you, I could be convinced otherwise if I new of a source for cheap 2.5" SCSI drives of reasonable size. I loaded up all 3 flavours of BSD on various alphas and the Multia is currently running OpenBSD 2.6. I could probably switch that around if there was an over-riding reason. Charlie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Sep 29 7:30:12 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from Samizdat.uucom.com (samizdat.uucom.com [198.202.217.54]) by hub.freebsd.org (Postfix) with ESMTP id B144537B422 for ; Fri, 29 Sep 2000 07:30:10 -0700 (PDT) Received: (from cshenton@localhost) by Samizdat.uucom.com (8.9.3/8.9.3) id KAA04685; Fri, 29 Sep 2000 10:29:49 -0400 (EDT) To: Charles Richmond Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Hardware/Software Multia/UDB questions References: <31269226357BD211979E00A0C9866DABE411FD@rios.sitaranetworks.com> From: Chris Shenton Date: 29 Sep 2000 10:29:49 -0400 In-Reply-To: Charles Richmond's message of "Fri, 29 Sep 2000 06:23:25 -0400" Message-ID: Lines: 17 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 29 Sep 2000 06:23:25 -0400, Charles Richmond said: Charles> The internal drives generate a lot of heat for what is very Charles> little drive space (in today's world). Taking out the drive Charles> will do enough for the cooling. Mind you, I could be Charles> convinced otherwise if I new of a source for cheap 2.5" SCSI Charles> drives of reasonable size. I loaded up all 3 flavours of BSD Charles> on various alphas and the Multia is currently running OpenBSD Charles> 2.6. I could probably switch that around if there was an Charles> over-riding reason. How hard would it be to turn a diskless multia into a diskless X-term? I've been avoiding doing anything with mine due to fear of heat-death. If running diskless can be done -- preferably as an Xterm, not a full OS -- I'd be all over it. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Sep 29 7:39: 4 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 84BCD37B422 for ; Fri, 29 Sep 2000 07:38:25 -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 13f1Ip-00046l-00; Fri, 29 Sep 2000 14:38:19 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e8TEe4s01232; Fri, 29 Sep 2000 16:40:04 +0200 (CEST) (envelope-from wkb) Date: Fri, 29 Sep 2000 16:40:04 +0200 From: Wilko Bulte To: Chris Shenton Cc: Charles Richmond , freebsd-alpha@freebsd.org Subject: Re: Hardware/Software Multia/UDB questions Message-ID: <20000929164004.B1155@freebie.demon.nl> References: <31269226357BD211979E00A0C9866DABE411FD@rios.sitaranetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from cshenton@uucom.com on Fri, Sep 29, 2000 at 10:29:49AM -0400 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 Fri, Sep 29, 2000 at 10:29:49AM -0400, Chris Shenton wrote: > On Fri, 29 Sep 2000 06:23:25 -0400, Charles Richmond said: > > Charles> The internal drives generate a lot of heat for what is very > Charles> little drive space (in today's world). Taking out the drive > Charles> will do enough for the cooling. Mind you, I could be > Charles> convinced otherwise if I new of a source for cheap 2.5" SCSI > Charles> drives of reasonable size. I loaded up all 3 flavours of BSD > Charles> on various alphas and the Multia is currently running OpenBSD > Charles> 2.6. I could probably switch that around if there was an > Charles> over-riding reason. > > How hard would it be to turn a diskless multia into a diskless X-term? > I've been avoiding doing anything with mine due to fear of heat-death. > If running diskless can be done -- preferably as an Xterm, not a full > OS -- I'd be all over it. Multia has builtin TGA, I'm not too sure if there is a working X server for that one. -- 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 Fri Sep 29 8: 7: 5 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.159.1.85]) by hub.freebsd.org (Postfix) with ESMTP id 1184637B422 for ; Fri, 29 Sep 2000 08:07:03 -0700 (PDT) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id QAA09300; Fri, 29 Sep 2000 16:06:56 +0100 (BST) (envelope-from geoffb) Date: Fri, 29 Sep 2000 16:06:56 +0100 From: Geoff Buckingham To: Wilko Bulte Cc: Chris Shenton , Charles Richmond , freebsd-alpha@FreeBSD.ORG Subject: Re: Hardware/Software Multia/UDB questions Message-ID: <20000929160656.B8918@chuggalug.clues.com> References: <31269226357BD211979E00A0C9866DABE411FD@rios.sitaranetworks.com> <20000929164004.B1155@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000929164004.B1155@freebie.demon.nl>; from Wilko Bulte on Fri, Sep 29, 2000 at 04:40:04PM +0200 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Sep 29, 2000 at 04:40:04PM +0200, Wilko Bulte wrote: > > > > How hard would it be to turn a diskless multia into a diskless X-term? > > I've been avoiding doing anything with mine due to fear of heat-death. > > If running diskless can be done -- preferably as an Xterm, not a full > > OS -- I'd be all over it. > > Multia has builtin TGA, I'm not too sure if there is a working X server > for that one. > I was a part of a group of 20 folks who purchased multias 18-24 months ago most of them experianced heat death, including those that ran diskless:-) I would suggest following Mikes advice and uprgrading the fan, combine that with the vertical stand and possibly a DIY heatsink. It may work. I think of the folks here people had the most luck running Linux, heat death wise. (probably just dumb luck) Xfree does have a TGA driver, seen it reported working under linux. Linux folks also report working machines using S3 PCI VGA cards in the PCI slot. PS I wish in no way to advocate the use of Linux. -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Sep 30 3:52:14 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mailout06.sul.t-online.com (mailout06.sul.t-online.com [194.25.134.19]) by hub.freebsd.org (Postfix) with ESMTP id A852B37B502 for ; Sat, 30 Sep 2000 03:52:10 -0700 (PDT) Received: from fmrl02.sul.t-online.de by mailout06.sul.t-online.com with smtp id 13fKFT-0004WB-01; Sat, 30 Sep 2000 12:52:07 +0200 Received: from neutron.cichlids.com (520050424122-0001@[62.157.56.207]) by fmrl02.sul.t-online.com with esmtp id 13fKFJ-0y9rNYC; Sat, 30 Sep 2000 12:51:57 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id E37ACAB91; Sat, 30 Sep 2000 12:52:49 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 4CDB714A5C; Sat, 30 Sep 2000 12:51:55 +0200 (CEST) Date: Sat, 30 Sep 2000 12:51:55 +0200 From: Alexander Langer To: Bernd Walter Cc: alpha@freebsd.org Subject: Re: loader problem Message-ID: <20000930125155.A5697@cichlids.cichlids.com> References: <20000924195255.A30987@cichlids.cichlids.com> <20000924202624.A70289@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20000924202624.A70289@cicely8.cicely.de>; from ticso@cicely8.cicely.de on Sun, Sep 24, 2000 at 08:26:24PM +0200 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. X-Sender: 520050424122-0001@t-dialin.net Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The old loader worked, in fact. The problem seems fixed now, since a loader from beast.freebsd.org works. Thanks Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Sep 30 10: 4: 9 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from francine.edoropolis.org (catv6055.extern.kun.nl [131.174.116.55]) by hub.freebsd.org (Postfix) with ESMTP id 4273037B503 for ; Sat, 30 Sep 2000 10:04:07 -0700 (PDT) Received: from francine.edoropolis.org (localhost [127.0.0.1]) by francine.edoropolis.org (8.11.0/8.9.2) with ESMTP id e8UH43u11199 for ; Sat, 30 Sep 2000 19:04:05 +0200 (CEST) (envelope-from purrcat@edoropolis.org) Message-Id: <200009301704.e8UH43u11199@francine.edoropolis.org> To: freebsd-alpha@freebsd.org Subject: 3c509 isa cards on an AXPPCI33..? X-Mailer: nmh X-Maileditor: vi X-Visit: http://www.edoropolis.org/ X-Use: Leona-HTTPd, http://www.qdonksoft.com/ Date: Sat, 30 Sep 2000 19:04:00 +0200 From: Khamba Staring Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Does anyone know FreeBSD 4.1 alpha release has 3c509 isa card support? I remember the 3.1 release didn't have support yet.. Regards, -- Khamba Staring ps: I'm currently not on the freebsd-alpha mailing list. Please mail any answer to me as well.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Sep 30 10: 8:37 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from ptldpop2.ptld.uswest.net (ptldpop2.ptld.uswest.net [198.36.160.2]) by hub.freebsd.org (Postfix) with SMTP id DE70637B503 for ; Sat, 30 Sep 2000 10:08:35 -0700 (PDT) Received: (qmail 18814 invoked by alias); 30 Sep 2000 17:08:34 -0000 Delivered-To: fixup-freebsd-alpha@freebsd.org@fixme Received: (qmail 18799 invoked by uid 0); 30 Sep 2000 17:08:33 -0000 Received: from win2k.gplsucks.org (HELO win2k) (63.227.213.89) by ptldpop2.ptld.uswest.net with SMTP; 30 Sep 2000 17:08:33 -0000 From: "William Woods" To: Subject: 4.1.1 boot disks.... Date: Sat, 30 Sep 2000 10:04:20 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Whats up with the 4.1.1 boot disks for the Alpha ? I get past loading the mfsroot.flp then nothing, this happens when I make the floppies from the CD (I burned the ISO) or when I DL the floppies from ftp.freebsd.org. Any ideas? Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Sep 30 11:55:12 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 8E36F37B66C for ; Sat, 30 Sep 2000 11:55:10 -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 13fRms-0000My-00; Sat, 30 Sep 2000 18:55:06 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e8UIurY08784; Sat, 30 Sep 2000 20:56:53 +0200 (CEST) (envelope-from wkb) Date: Sat, 30 Sep 2000 20:56:53 +0200 From: Wilko Bulte To: William Woods Cc: freebsd-alpha@freebsd.org Subject: Re: 4.1.1 boot disks.... Message-ID: <20000930205653.B8746@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 bwoods2@uswest.net on Sat, Sep 30, 2000 at 10:04:20AM -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 Sat, Sep 30, 2000 at 10:04:20AM -0700, William Woods wrote: > Whats up with the 4.1.1 boot disks for the Alpha ? I get past loading the > mfsroot.flp then nothing, this happens when I make the floppies from the CD > (I burned the ISO) or when I DL the floppies from ftp.freebsd.org. What machine type are you using? -- 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 Sat Sep 30 14: 8:37 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 2BA5437B66C for ; Sat, 30 Sep 2000 14:08:36 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA91274; Sat, 30 Sep 2000 14:08:33 -0700 (PDT) (envelope-from obrien) Date: Sat, 30 Sep 2000 14:08:33 -0700 From: "David O'Brien" To: William Woods Cc: freebsd-alpha@freebsd.org Subject: Re: 4.1.1 boot disks.... Message-ID: <20000930140833.A48536@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from bwoods2@uswest.net on Sat, Sep 30, 2000 at 10:04:20AM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Sep 30, 2000 at 10:04:20AM -0700, William Woods wrote: > Whats up with the 4.1.1 boot disks for the Alpha ? Can you provide more details? I tested the 4.1.1 release on a Miata (Personal Workstation). -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Sep 30 14:35:24 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 1CB3537B502 for ; Sat, 30 Sep 2000 14:35:21 -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 e8ULZGa26699 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK) for ; Sat, 30 Sep 2000 23:35:19 +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 e8ULZg545747 for ; Sat, 30 Sep 2000 23:35:42 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.11.0/8.9.2) id e8ULZbF84100 for freebsd-alpha@freebsd.org; Sat, 30 Sep 2000 23:35:37 +0200 (CEST) (envelope-from ticso) Date: Sat, 30 Sep 2000 23:35:37 +0200 From: Bernd Walter To: freebsd-alpha@freebsd.org Subject: I still have problems booting into su-mode with ithread patches Message-ID: <20000930233536.A83846@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Since the first version I tested current with the ithread patches on my PC164 I can see it hanging during boot and if I press the halt button I catch it always with the pointer after the call pal operation of alpha_pal_swpipl(). First it was an spl call now that they are removed I catch it within mtx_exit of the sched_lock resource. I even set it explicitly to ALPHA_PSL_IPL_0 when releasing a mutex. I asume that I catch it always at these point because it's spending most time there and not because the call pal itself is hanging. During the boot process the hanging is always during scsi-bus probing. With an earlier version of the patches it sometime made it to adding the devices to the kernel tables. Is anyone who got it running using a system with multiple scsi channels and/or multiple devices and/or seriel console? As I'm catching it in releasing sched_lock after calling mi_switch the scheduler still seems to work. The only debugging functionality I know of is the objdump -S output from the kernel and the halt-button. Does anyone know more I can try - I can't enter ddb with a break. Is there any way to look into the witness output using SRM? -- 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 30 16:56:46 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 64EFF37B502 for ; Sat, 30 Sep 2000 16:56:39 -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 TAA22563; Sat, 30 Sep 2000 19:56:26 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e8UNuQW06263; Sat, 30 Sep 2000 19:56:26 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 30 Sep 2000 19:56:25 -0400 (EDT) To: freebsd-alpha@freebsd.org Cc: dfr@nlsystems.com Subject: size problems with INVARIANTS/DIAGNOSTIC -current kernels X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14806.26688.509296.391897@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org With an INVARIANTS/DIAGNOSTIC kernel, my -current machines are locking up (or halting) at boot with a stack that looks like the following: malloc resource_create resource_set_string hints_load mi_startup (discovered with printfs) At the point it hangs, there should be a trap the first time malloc touches kmemusage (kup->ku_indx = indx;, line 203 of kern_malloc.c). I assume this is happening the first time the kernel touches mapped (not kseg) memory. Rather than taking a trap & doing the normal vm magic, the machine just sits there. It sometimes will eventually halt. When it does, I see >>>e pc PC psr: 0 ( PC) FFFFFC00006960F8 >>>e ra gpr: 1A ( R26) FFFFFC00005E1F4C The RA maps to XentMM: (gdb) l *0xFFFFFC00005E1F4C 0xfffffc00005e1f4c is in XentMM (../../alpha/alpha/exception.s:94). 89 PALVECT(XentMM) /* setup frame, save registers */ 90 91 /* a0, a1, & a2 already set up */ 92 ldiq a3, ALPHA_KENTRY_MM 93 mov sp, a4 ; .loc 1 __LINE__ 94 CALL(trap) 95 96 jmp zero, exception_return 97 END(XentMM) The PC is off in the data segment (doesn't map to anything in the kernel text). trap is 0xfffffc00005f4460 Hmmm.... After more debugging, I'm fairly sure this is a size issue. A much smaller kernel (all unneeded devs, IPv6, etc, stripped out but with INVARIANTS/DIAGNOSTIC options), boots just fine. I need some help here.. Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message