From owner-freebsd-alpha Sun Nov 10 3:10:51 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF75237B401 for ; Sun, 10 Nov 2002 03:10:48 -0800 (PST) Received: from herring.nlsystems.com (mailgate.nlsystems.com [62.49.251.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAA3143E42 for ; Sun, 10 Nov 2002 03:10:46 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring [10.0.0.2]) by herring.nlsystems.com (8.12.6/8.12.6) with ESMTP id gAABAYVu040399; Sun, 10 Nov 2002 11:10:34 GMT (envelope-from dfr@nlsystems.com) Content-Type: text/plain; charset="iso-8859-1" From: Doug Rabson To: "Alan L. Cox" , Jeff Roberson Subject: Re: alpha: top of tree kernel blooie Date: Sun, 10 Nov 2002 11:10:34 +0000 User-Agent: KMail/1.4.3 Cc: Matthew Jacob , Andrew Gallatin , alpha@FreeBSD.ORG, alc@FreeBSD.ORG, John Baldwin References: <20021109150359.B97372-100000@mail.chesapeake.net> <3DCD7244.DEEA7387@imimic.com> In-Reply-To: <3DCD7244.DEEA7387@imimic.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200211101110.34153.dfr@nlsystems.com> X-Spam-Status: No, hits=-7.7 required=5.0 tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01, USER_AGENT,USER_AGENT_KMAIL version=2.41 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Saturday 09 November 2002 8:38 pm, Alan L. Cox wrote: > Jeff Roberson wrote: > > On Fri, 8 Nov 2002, Matthew Jacob wrote: > > > > Can you 'ps aux -o wchan' ? > > > > > > I tried a buildworld -j4 again- this time it was too far hung to > > > let anyone log in... > > > > I ran into the vm_map_delete() duplicate free again. This has been > > the same code path too many times for it to be a non logic bug. > > > > Jeff > > I'm still wondering if this isn't a false positive: > > 1. My reading of the UMA debug code is that two or more processors > can simultaneously read and modify us_freelist[]. The only lock held > during an access is the CPU private lock. > > 2. Don't we compile by default for the older Alphas that lack byte > manipulation instructions? Thus, a byte store is implemented by a > read-modify-write sequence of instructions. Thus, two simultaneous > uma_dbg_alloc()s on adjacent locations in us_freelist could cause > corruption. It was exactly this kind of breakage that prompted me to write the=20 atomic_* functions in the first place. Note that it is often possible=20 to get corruption even on a UP machine if an interrupt happens mid=20 sequence. --=20 Doug Rabson=09=09=09=09Mail: dfr@nlsystems.com =09=09=09=09=09Phone: +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 Nov 10 8:15:22 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6036E37B406; Sun, 10 Nov 2002 08:15:21 -0800 (PST) Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8217543E75; Sun, 10 Nov 2002 08:15:20 -0800 (PST) (envelope-from mjacob@feral.com) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id gAAGEuZ59342; Sun, 10 Nov 2002 08:14:56 -0800 (PST) (envelope-from mjacob@feral.com) Date: Sun, 10 Nov 2002 08:14:55 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Doug Rabson Cc: "Alan L. Cox" , Jeff Roberson , Andrew Gallatin , alpha@FreeBSD.ORG, alc@FreeBSD.ORG, John Baldwin Subject: Re: alpha: top of tree kernel blooie In-Reply-To: <200211101110.34153.dfr@nlsystems.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > 2. Don't we compile by default for the older Alphas that lack byte > > manipulation instructions? Thus, a byte store is implemented by a > > read-modify-write sequence of instructions. Thus, two simultaneous > > uma_dbg_alloc()s on adjacent locations in us_freelist could cause > > corruption. > > It was exactly this kind of breakage that prompted me to write the > atomic_* functions in the first place. Note that it is often possible > to get corruption even on a UP machine if an interrupt happens mid > sequence. I survived a -j4 buildworld on the 4-way SMP with atomic_set_8 in the uma_dbg_alloc/uma_dbg_free. I think we'll call this one 'good' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 10 8:23:42 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B14337B401; Sun, 10 Nov 2002 08:23:41 -0800 (PST) Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0ED043E3B; Sun, 10 Nov 2002 08:23:40 -0800 (PST) (envelope-from mjacob@feral.com) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id gAAGNdZ59409; Sun, 10 Nov 2002 08:23:39 -0800 (PST) (envelope-from mjacob@feral.com) Date: Sun, 10 Nov 2002 08:23:39 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: "Alan L. Cox" Cc: alpha@FreeBSD.ORG, John Baldwin Subject: on the same note.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org .... In vm_object.c you or somebody had a question about atomicity in bumping the object generation count. What is wrong with just making that atomic_add_int for now? I see no locks otherwise covering it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 10 8:26:53 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBCF537B401 for ; Sun, 10 Nov 2002 08:26:51 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 612FC43E42 for ; Sun, 10 Nov 2002 08:26:47 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA23274 for ; Sun, 10 Nov 2002 11:26:41 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gAAGQB646444; Sun, 10 Nov 2002 11:26:11 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15822.34979.564442.702858@grasshopper.cs.duke.edu> Date: Sun, 10 Nov 2002 11:26:11 -0500 (EST) To: freebsd-alpha@freebsd.org Subject: 164lx power issues X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org My company is using a 164lx as a web server. Its located 3,000 miles away in the home office, and it was physically assembled by people other than myself.. Recently we had a long power outage and we discovered that the machine does not automatically power on when A/C power is restored. Rather, a human must press the power button to switch the machine on. Is there a common misconfiguration which would result in this behaviour? If so, how do we ensure the machine powers itself back on without manual intervention when A/C power is restored? Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 10 8:28:32 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6979337B401 for ; Sun, 10 Nov 2002 08:28:31 -0800 (PST) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6432743E3B for ; Sun, 10 Nov 2002 08:28:30 -0800 (PST) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.6/8.12.6) with ESMTP id gAAGSRHX088113; Sun, 10 Nov 2002 17:28:27 +0100 (CET) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.6/8.12.6/Submit) id gAAGSRhC088110; Sun, 10 Nov 2002 17:28:27 +0100 (CET) Date: Sun, 10 Nov 2002 17:28:27 +0100 From: Wilko Bulte To: Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: 164lx power issues Message-ID: <20021110172827.B83187@freebie.xs4all.nl> References: <15822.34979.564442.702858@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15822.34979.564442.702858@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Sun, Nov 10, 2002 at 11:26:11AM -0500 X-OS: FreeBSD 4.7-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, Nov 10, 2002 at 11:26:11AM -0500, Andrew Gallatin wrote: > > My company is using a 164lx as a web server. Its located 3,000 miles > away in the home office, and it was physically assembled by people > other than myself.. > > Recently we had a long power outage and we discovered that the machine > does not automatically power on when A/C power is restored. Rather, a > human must press the power button to switch the machine on. > > Is there a common misconfiguration which would result in this > behaviour? If so, how do we ensure the machine powers itself back > on without manual intervention when A/C power is restored? Doesn't the LX use an ATX power supply that needs some minor tweaking for it to work? -- | / o / /_ _ FreeBSD core team secretary |/|/ / / /( (_) Bulte wilko@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 Nov 10 8:35:53 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F76D37B401; Sun, 10 Nov 2002 08:35:52 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9ADF643E42; Sun, 10 Nov 2002 08:35:51 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA23548; Sun, 10 Nov 2002 11:35:51 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gAAGZLc46459; Sun, 10 Nov 2002 11:35:21 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15822.35528.984561.534904@grasshopper.cs.duke.edu> Date: Sun, 10 Nov 2002 11:35:20 -0500 (EST) To: Poul-Henning Kamp Cc: alpha@FreeBSD.ORG Subject: Re: ev4/5/6 issue ? In-Reply-To: <51801.1036863194@critter.freebsd.dk> References: <51801.1036863194@critter.freebsd.dk> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Poul-Henning Kamp writes: > > An alphastation255 has found its way to my lab but I'm having a spot of > trouble getting it into workable state. > > I installed an iso which jhb@ had produced and the system boots. > > But make(1) coredumps with illegal instruction. > > I've tried to compile a make(1) on beast (setting CPUTYPE="") but it > also core-dumps. I pressume that's because the libs are ev6. > An illegal instruction trap occurs when the processor attempts to execute an instruction which it does not recognize. We attempt to fixup the most common instructions in the kernel (mainly so you can run the acrobat reader binary on older alphas..) However, beast is a 21264a and it supports all valid alpha instructions. So rather than a bug in the opdec code, I suspect that the compiler or linker is emitting bad code, or something else weird is happening. What instruction is causing the trap? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 10 10:43:31 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF6F037B401 for ; Sun, 10 Nov 2002 10:43:29 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id E149243E3B for ; Sun, 10 Nov 2002 10:43:28 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id gAAIh7Or026566; Sun, 10 Nov 2002 19:43:08 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Andrew Gallatin Cc: alpha@FreeBSD.ORG Subject: Re: ev4/5/6 issue ? In-Reply-To: Your message of "Sun, 10 Nov 2002 11:35:20 EST." <15822.35528.984561.534904@grasshopper.cs.duke.edu> Date: Sun, 10 Nov 2002 19:43:07 +0100 Message-ID: <26565.1036953787@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message <15822.35528.984561.534904@grasshopper.cs.duke.edu>, Andrew Gallatin writes: > >Poul-Henning Kamp writes: > > > > An alphastation255 has found its way to my lab but I'm having a spot of > > trouble getting it into workable state. > > > > I installed an iso which jhb@ had produced and the system boots. > > > > But make(1) coredumps with illegal instruction. > > > > I've tried to compile a make(1) on beast (setting CPUTYPE="") but it > > also core-dumps. I pressume that's because the libs are ev6. > > > >An illegal instruction trap occurs when the processor attempts to >execute an instruction which it does not recognize. We attempt to >fixup the most common instructions in the kernel (mainly so you can >run the acrobat reader binary on older alphas..) > >However, beast is a 21264a and it supports all valid alpha >instructions. So rather than a bug in the opdec code, I suspect that >the compiler or linker is emitting bad code, or something else weird >is happening. I get the trap on my alphastation 255, not on beast. >What instruction is causing the trap? I have no idea, gdb doesn't offer any help as far as I can see :-( -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 10 10:53: 8 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 435BC37B401; Sun, 10 Nov 2002 10:53:07 -0800 (PST) Received: from parmenion.hosting.swbell.net (parmenion.hosting.swbell.net [216.100.98.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id D936143E42; Sun, 10 Nov 2002 10:53:06 -0800 (PST) (envelope-from alc@imimic.com) Received: from imimic.com (adsl-216-63-78-19.dsl.hstntx.swbell.net [216.63.78.19]) by parmenion.hosting.swbell.net id NAA00473; Sun, 10 Nov 2002 13:53:01 -0500 (EST) [ConcentricHost SMTP Relay 1.14] Message-ID: <3DCEAB0C.F2898200@imimic.com> Date: Sun, 10 Nov 2002 12:53:00 -0600 From: "Alan L. Cox" Organization: iMimic Networking, Inc. X-Mailer: Mozilla 4.8 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: mjacob@feral.com Cc: alpha@FreeBSD.ORG, John Baldwin Subject: Re: on the same note.. References: Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Matthew Jacob wrote: > > .... > > In vm_object.c you or somebody had a question about atomicity in bumping > the object generation count. What is wrong with just making that > atomic_add_int for now? I see no locks otherwise covering it. It and the other vm_object fields are generally covered by Giant. I believe that vm_object allocation and initialization are the only activities that aren't. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 10 11:12:17 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B58F37B401 for ; Sun, 10 Nov 2002 11:12:16 -0800 (PST) Received: from trillian.santala.org (ip212-226-173-33.adsl.kpnqwest.fi [212.226.173.33]) by mx1.FreeBSD.org (Postfix) with SMTP id 1D45E43E3B for ; Sun, 10 Nov 2002 11:12:10 -0800 (PST) (envelope-from jake@iki.fi) Received: (qmail 41163 invoked by uid 11053); 10 Nov 2002 19:12:07 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 10 Nov 2002 19:12:07 -0000 Date: Sun, 10 Nov 2002 21:12:07 +0200 (EET) From: Jarkko Santala X-X-Sender: jake@trillian.santala.org To: Wilko Bulte Cc: Andrew Gallatin , Subject: Re: 164lx power issues In-Reply-To: <20021110172827.B83187@freebie.xs4all.nl> Message-ID: <20021110210210.W346-100000@trillian.santala.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, 10 Nov 2002, Wilko Bulte wrote: > On Sun, Nov 10, 2002 at 11:26:11AM -0500, Andrew Gallatin wrote: > > Recently we had a long power outage and we discovered that the machine > > does not automatically power on when A/C power is restored. Rather, a > > human must press the power button to switch the machine on. > > > > Is there a common misconfiguration which would result in this > > behaviour? If so, how do we ensure the machine powers itself back > > on without manual intervention when A/C power is restored? > > Doesn't the LX use an ATX power supply that needs some minor > tweaking for it to work? Yes, you have to connect the green wire to one of the black ones in the ATX power connector to automagically "turn on" an ATX PSU when power cord is inserted or a proper power switch on the PSU is turned on. So to me it sounds like that the power switch on the case has been connected so that when pressed it connects the green to one of the blacks, causing the PSU to power up. If this is the case, the solution is to open the box and do some soldering. Either solder the power switch on the front panel to be always on or do the soldering on the ATX power connector, as it has been done in my PC164. Oh, and YMMV. And it might also be a good idea to check somewhere it really is the green wire... ;) -jake -- Jarkko Santala http://www.iki.fi/~jake/ System Administrator 2001:670:83:f08::/64 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 10 11:26: 3 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 608FE37B401; Sun, 10 Nov 2002 11:26:02 -0800 (PST) Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADED743E4A; Sun, 10 Nov 2002 11:26:01 -0800 (PST) (envelope-from mjacob@feral.com) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id gAAJPxZ60730; Sun, 10 Nov 2002 11:25:59 -0800 (PST) (envelope-from mjacob@feral.com) Date: Sun, 10 Nov 2002 11:25:59 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: "Alan L. Cox" Cc: alpha@FreeBSD.ORG, John Baldwin Subject: Re: on the same note.. In-Reply-To: <3DCEAB0C.F2898200@imimic.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Err, well, this *is* in vm object allocation... On Sun, 10 Nov 2002, Alan L. Cox wrote: > Matthew Jacob wrote: > > > > .... > > > > In vm_object.c you or somebody had a question about atomicity in bumping > > the object generation count. What is wrong with just making that > > atomic_add_int for now? I see no locks otherwise covering it. > > It and the other vm_object fields are generally covered by Giant. I > believe that vm_object allocation and initialization are the only > activities that aren't. > > Alan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 10 11:46:49 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0A6737B401; Sun, 10 Nov 2002 11:46:48 -0800 (PST) Received: from philotas.hosting.swbell.net (philotas.hosting.swbell.net [216.100.99.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 756C143E6E; Sun, 10 Nov 2002 11:46:48 -0800 (PST) (envelope-from alc@imimic.com) Received: from imimic.com (adsl-216-63-78-19.dsl.hstntx.swbell.net [216.63.78.19]) by philotas.hosting.swbell.net id OAA12790; Sun, 10 Nov 2002 14:46:36 -0500 (EST) [ConcentricHost SMTP Relay 1.14] Message-ID: <3DCEB79A.69EB752D@imimic.com> Date: Sun, 10 Nov 2002 13:46:34 -0600 From: "Alan L. Cox" Organization: iMimic Networking, Inc. X-Mailer: Mozilla 4.8 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: mjacob@feral.com Cc: alpha@FreeBSD.ORG, John Baldwin Subject: Re: on the same note.. References: Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Matthew Jacob wrote: > > Err, well, this *is* in vm object allocation... Ah, I see what you're talking about now. Until the vm object has been returned by the allocation routine it is not shared data. The generation count is used to detect changes in the list of resident pages by sleeping processes, not to detect that the same storage is being recycled for a new object. Alan > On Sun, 10 Nov 2002, Alan L. Cox wrote: > > > Matthew Jacob wrote: > > > > > > .... > > > > > > In vm_object.c you or somebody had a question about atomicity in bumping > > > the object generation count. What is wrong with just making that > > > atomic_add_int for now? I see no locks otherwise covering it. > > > > It and the other vm_object fields are generally covered by Giant. I > > believe that vm_object allocation and initialization are the only > > activities that aren't. > > > > Alan > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 10 12:24:59 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A586537B406 for ; Sun, 10 Nov 2002 12:24:58 -0800 (PST) Received: from tibor.org (117-5-237-24-cable.anchorageak.net [24.237.5.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 991E243E6E for ; Sun, 10 Nov 2002 12:24:56 -0800 (PST) (envelope-from tibor@tibor.org) Received: from xena.mikey.net (xena.mikey.net [192.168.1.2]) by tibor.org (Postfix) with ESMTP id 5C6F1A9CC for ; Sun, 10 Nov 2002 11:24:50 -0900 (AKST) Date: Sun, 10 Nov 2002 11:24:50 -0900 (AKST) From: Mike Tibor X-X-Sender: tibor@xena.mikey.net To: freebsd-alpha@FreeBSD.ORG Subject: Re: 164lx power issues In-Reply-To: <20021110210210.W346-100000@trillian.santala.org> Message-ID: <20021110111402.C12814-100000@xena.mikey.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, 10 Nov 2002, Jarkko Santala wrote: > On Sun, 10 Nov 2002, Wilko Bulte wrote: > > > Doesn't the LX use an ATX power supply that needs some minor > > tweaking for it to work? Nope, nothing more than a high-quality ATX power supply, 300 watt minimum (realistically speaking). > Yes, you have to connect the green wire to one of the black ones in the > ATX power connector to automagically "turn on" an ATX PSU when power cord > is inserted or a proper power switch on the PSU is turned on. This is grounding out the soft power circuit. I think it depends on the power supply whether this will work. The two or three power supplies I played with on my 164LX required me to ground the soft power circuit while power was connected. If I had it grounded before power was connected, I had to break the circuit, and then ground it again in order for the machine to power up. Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 10 16:26:41 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D54B937B401; Sun, 10 Nov 2002 16:26:36 -0800 (PST) Received: from mta05.mail.mel.aone.net.au (mta05.mail.au.uu.net [203.2.192.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AE6C43E77; Sun, 10 Nov 2002 16:26:35 -0800 (PST) (envelope-from rbyrnes@ozemail.com.au) Received: from ausyddtp0050.ozemail.com.au ([203.166.67.234]) by mta05.mail.mel.aone.net.au with ESMTP id <20021111002628.OKYH19025.mta05.mail.mel.aone.net.au@ausyddtp0050.ozemail.com.au>; Mon, 11 Nov 2002 11:26:28 +1100 Message-Id: <5.1.0.14.2.20021111112347.05180670@pop.ozemail.com.au> X-Sender: rbyrnes@pop.ozemail.com.au X-Mailer: I wish it was Linux Date: Mon, 11 Nov 2002 11:25:15 +1100 To: John Baldwin From: Rob B Subject: Re: 5.0 alpha install tests Cc: freebsd-alpha@freebsd.org, Andrew Gallatin In-Reply-To: References: <00f201c287d5$9f4b6f20$3164a8c0@pootah> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At 09:39 9/11/2002 -0500, John Baldwin sent this up the stick: >On 09-Nov-2002 Rob B wrote: > > ----- Original Message ----- > > From: "Andrew Gallatin" > > To: "Rob B" > > Cc: > > Sent: Thursday, November 07, 2002 1:44 PM > > Subject: Re: 5.0 alpha install tests > > > > > >> Rob B writes: > > > >>>> sho conf > > Digital AlphaPC 64 274MHz > > SRM Console V4.8-1 VMS PALcode V5.56-1, OSF PALcode V1.45-4 > > DECchip (tm) 21064A-2 > > DECchip (tm) 21071-DA Pass 1 > > DECchip (tm) 21071-CA Pass 2 > > > > MEMORY > > 64Meg of system memory > > > > > > PCI Bus > > Bus 00 Slot 05: NCR 53C875 Scsi Controller > > pka0.7.0.5.0 Scsi Bus ID 7 > > dka0.0.0.5.0 COMPAQ > > BD00421936 > > Bus 00 Slot 08: Intel 82378IB PCI to ISA Bridge > > > > ISA > > Slot Device Name Type Enabled BaseAddr > > IRQ DMA > > 0 > > 0 MOUSE Embedded Yes 60 > > 12 > > 1 KBD Embedded Yes 60 > > 1 > > 2 COM1 Embedded Yes 3f8 > > 4 > > 3 COM2 Embedded Yes 2f8 > > 3 > > 4 LPT1 Embedded Yes > > 3bc 7 > > 5 FLOPPY Embedded Yes 3f0 > > 6 2 > > > > aylee# dmesg > > Copyright (c) 1992-2002 The FreeBSD Project. > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > > The Regents of the University of California. All rights reserved. > > FreeBSD 5.0-DP1 #0: Sun Apr 7 07:34:25 GMT 2002 > > murray@axpbuilder.freebsdmall.com:/usr/src/sys/alpha/compile/GENERIC > > Preloaded elf kernel "/boot/kernel/kernel" at 0xfffffc0000814000. > > EB64+ > > Digital AlphaPC 64 274 MHz, 274MHz > > 8192 byte page size, 1 processor. > > CPU: EV45 (21064A) major=6 minor=2 > > OSF PAL rev: 0x100040002012d > > real memory = 65019904 (63496K bytes) > > avail memory = 55279616 (53984K bytes) > > apecs0: > > pci0: on pcib0 > > sym0: <875> port 0x10000-0x100ff mem > > 0x8205c000-0x8205cfff,0x8205d000-0x8205d0ff irq 2 at device 5.0 on pci0 > > sym0: Tekram NVRAM, ID 7, Fast-20, SE, parity checking > > sym0: interrupting at APECS irq 2 > > pci0: at device 7.0 (no driver attached) > > isab0: at device 8.0 on pci0 > > isa0: on isab0 > > dc0: port 0x10100-0x1017f mem > > 0x8205d100-0x8205d17f irq 3 at device 9.0 on pci0 > > dc0: interrupting at APECS irq 3 > > dc0: Ethernet address: 08:00:2b:c3:dd:56 > > miibus0: on dc0 > > dcphy0: on miibus0 > > dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > atkbdc0: at port 0x64,0x60 on isa0 > > atkbd0: irq 1 on atkbdc0 > > atkbd0: interrupting at ISA irq 1 > > fdc0: at port > > 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 > > fdc0: interrupting at ISA irq 6 > > mcclock0: at port 0x70-0x71 on isa0 > > ppc0: at port 0x3bc-0x3c3 irq 7 on isa0 > > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > > plip0: cannot reserve interrupt, failed. > > lpt0: on ppbus0 > > lpt0: Polled port > > ppi0: on ppbus0 > > ppc0: interrupting at ISA irq 7 > > sc0: on isa0 > > sc0: VGA <16 virtual consoles, flags=0x200> > > sio0 at port 0x3f8-0x3ff irq 4 on isa0 > > sio0: type 16550A > > sio0: interrupting at ISA irq 4 > > sio1: reserved for low-level i/o > > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > > Timecounter "i8254" frequency 1193182 Hz > > Timecounter "alpha" frequency 275002485 Hz > > Waiting 15 seconds for SCSI devices to settle > > da0 at sym0 bus 0 target 0 lun 0 > > da0: Fixed Direct Access SCSI-2 device > > da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing > > Enabled > > da0: 4091MB (8380080 512 byte sectors: 255H 63S/T 521C) > > Mounting root from ufs:/dev/da0a > > > > > > aylee# pciconf -lv > > sym0@pci0:5:0: class=0x010000 card=0x00000000 chip=0x000f1000 rev=0x01 > > hdr=0x00 > > vendor = 'Symbios Logic (NCR) (LSI Logic)' > > device = '53C875, 53C876 Ultra-Wide SCSI (53C876 is dual-channel)' > > class = mass storage > > subclass = SCSI > > none0@pci0:7:0: class=0x030000 card=0x00000000 chip=0x0519102b rev=0x01 > > hdr=0x00 > > vendor = 'Matrox Graphics Inc' > > device = 'MGA-2064W Millenium GUI Accelerator' > > class = display > > subclass = VGA > > isab0@pci0:8:0: class=0x000000 card=0x00000000 chip=0x04848086 rev=0x84 > > hdr=0x00 > > vendor = 'Intel Corporation' > > device = '82378ZB/IB,82379AB PCI to ISA Bridge, System I/O' > > class = old > > subclass = non-VGA display device > > dc0@pci0:9:0: class=0x020000 card=0x500b1011 chip=0x00191011 rev=0x30 > > hdr=0x00 > > vendor = 'Digital Equipment Corporation' > > device = 'DC21142/3 PCI/CardBus 10/100 Mbit Ethernet Ctlr' > > class = network > > subclass = ethernet > > > > > >> Also, did this work with previous version of FreeBSD, or is this the > >> first time this machine was installed with FreeBSD? > > > > It's never worked, but I've also not needed it prior to now > >Do you have an ISA ATA controller? If so, try breaking into the >loader (hit a key during the 10 second countdown) and type in the >following: > >set hint.ata.0.at="isa" >set hint.ata.0.port="0x1f0" >set hint.ata.0.irq="14" >set hint.ata.1.at="isa" >set hint.ata.1.port="0x170" >set hint.ata.1.irq="15" >boot > >If it does work, then add the following lines to your /boot/device.hints >file: > >hint.ata.0.at="isa" >hint.ata.0.port="0x1F0" >hint.ata.0.irq="14" >hint.ata.1.at="isa" >hint.ata.1.port="0x170" >hint.ata.1.irq="15" > >Also, if that does work, then we should think about adding those lines >to GENERIC.hints for Alpha. Thanks, I'll try the hints tonight. The ATA controller is built into the motherboard on the Cabriolet -- In this world, truth can wait; she's used to it. This is random quote 706 of a collection of 1255 Distance from the centre of the brewing universe: [15200.8 km (8207.8 mi), 262.8 deg](Apparent) Rennerian Public Key fingerprint = 6219 33BD A37B 368D 29F5 19FB 945D C4D7 1F66 D9C5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 10 16:30:46 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24D7037B401 for ; Sun, 10 Nov 2002 16:30:45 -0800 (PST) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6C5E43E4A for ; Sun, 10 Nov 2002 16:30:43 -0800 (PST) (envelope-from ticso@cicely8.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) by srv1.cosmo-project.de (8.12.5/8.12.5) with ESMTP id gAB0URsP083743 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Mon, 11 Nov 2002 01:30:29 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.1.10]) by cicely5.cicely.de (8.12.6/8.12.6) with ESMTP id gAB0UQCu050073 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 11 Nov 2002 01:30:27 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (localhost [127.0.0.1]) by cicely8.cicely.de (8.12.6/8.12.6) with ESMTP id gAB0UOl8061858; Mon, 11 Nov 2002 01:30:25 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: (from ticso@localhost) by cicely8.cicely.de (8.12.6/8.12.6/Submit) id gAB0UMMs061857; Mon, 11 Nov 2002 01:30:23 +0100 (CET) Date: Mon, 11 Nov 2002 01:30:21 +0100 From: Bernd Walter To: Jarkko Santala Cc: Wilko Bulte , Andrew Gallatin , freebsd-alpha@FreeBSD.ORG Subject: Re: 164lx power issues Message-ID: <20021111003020.GP57193@cicely8.cicely.de> Reply-To: ticso@cicely.de References: <20021110172827.B83187@freebie.xs4all.nl> <20021110210210.W346-100000@trillian.santala.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021110210210.W346-100000@trillian.santala.org> X-Operating-System: FreeBSD cicely8.cicely.de 5.0-CURRENT i386 User-Agent: Mutt/1.5.1i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, Nov 10, 2002 at 09:12:07PM +0200, Jarkko Santala wrote: > On Sun, 10 Nov 2002, Wilko Bulte wrote: > > > On Sun, Nov 10, 2002 at 11:26:11AM -0500, Andrew Gallatin wrote: > > > Recently we had a long power outage and we discovered that the machine > > > does not automatically power on when A/C power is restored. Rather, a > > > human must press the power button to switch the machine on. > > > > > > Is there a common misconfiguration which would result in this > > > behaviour? If so, how do we ensure the machine powers itself back > > > on without manual intervention when A/C power is restored? > > > > Doesn't the LX use an ATX power supply that needs some minor > > tweaking for it to work? > > Yes, you have to connect the green wire to one of the black ones in the > ATX power connector to automagically "turn on" an ATX PSU when power cord > is inserted or a proper power switch on the PSU is turned on. > > So to me it sounds like that the power switch on the case has been > connected so that when pressed it connects the green to one of the blacks, > causing the PSU to power up. The power supply only works as long as these lines are shortened. Normaly ATX boards have a power logic driven by a power button (button - no switch!) to toggle grounding the powersupply enable line. Some boards remember the state when powerloss or the have a auto-on function which can be enabled by jumper or bios config. The implementation of the powerlogic often not only controls the power supply, but also some onboard logic so that shorten the power supply doesn't work - enabling the power supply doesn't mean the CPU will run. However accourding to the PC164LX Technical Reference Manual, which is available as pdf, the initialisation logic don't do this. It only uses the power good signal from the supply. I believe shortening the enable line should work with this board. > If this is the case, the solution is to open the box and do some > soldering. Either solder the power switch on the front panel to be always > on or do the soldering on the ATX power connector, as it has been done in > my PC164. The PC164 is different in that there is no power logic on board. You always have to ground the power supply enable line to get it on. PS: no need to solder - a crocodile cable will also do. -- 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 Nov 10 18: 5:23 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3305D37B401; Sun, 10 Nov 2002 18:05:22 -0800 (PST) Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9568143E6E; Sun, 10 Nov 2002 18:05:21 -0800 (PST) (envelope-from mjacob@feral.com) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id gAB24xZ63148; Sun, 10 Nov 2002 18:05:04 -0800 (PST) (envelope-from mjacob@feral.com) Date: Sun, 10 Nov 2002 18:04:59 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: "Alan L. Cox" Cc: alpha@FreeBSD.ORG, John Baldwin Subject: Re: on the same note.. In-Reply-To: <3DCEB79A.69EB752D@imimic.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Matthew Jacob wrote: > > > > Err, well, this *is* in vm object allocation... > > Ah, I see what you're talking about now. Until the vm object has been > returned by the allocation routine it is not shared data. The > generation count is used to detect changes in the list of resident pages > by sleeping processes, not to detect that the same storage is being > recycled for a new object. > Well, if this is the case, the allocator shouldn't be just incrementing it, should it? Shouldn't it always start at zero? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 10 19: 3: 2 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42C9837B401; Sun, 10 Nov 2002 19:03:01 -0800 (PST) Received: from lysimachus.hosting.swbell.net (lysimachus.hosting.swbell.net [216.100.98.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id E858443E6E; Sun, 10 Nov 2002 19:03:00 -0800 (PST) (envelope-from alc@imimic.com) Received: from imimic.com (adsl-216-63-78-19.dsl.hstntx.swbell.net [216.63.78.19]) by lysimachus.hosting.swbell.net id WAA09433; Sun, 10 Nov 2002 22:02:48 -0500 (EST) [ConcentricHost SMTP Relay 1.14] Message-ID: <3DCF1DD7.B472A23A@imimic.com> Date: Sun, 10 Nov 2002 21:02:47 -0600 From: "Alan L. Cox" Organization: iMimic Networking, Inc. X-Mailer: Mozilla 4.8 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: mjacob@feral.com Cc: alpha@FreeBSD.ORG, John Baldwin Subject: Re: on the same note.. References: Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Matthew Jacob wrote: > > > Matthew Jacob wrote: > > > > > > Err, well, this *is* in vm object allocation... > > > > Ah, I see what you're talking about now. Until the vm object has been > > returned by the allocation routine it is not shared data. The > > generation count is used to detect changes in the list of resident pages > > by sleeping processes, not to detect that the same storage is being > > recycled for a new object. > > > > Well, if this is the case, the allocator shouldn't be just incrementing > it, should it? Shouldn't it always start at zero? Basically, yes. This increment has existed for almost five years. At this point, it only exists by inertia. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 10 19:30:46 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E2A937B401; Sun, 10 Nov 2002 19:30:45 -0800 (PST) Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09BD843E91; Sun, 10 Nov 2002 19:30:45 -0800 (PST) (envelope-from mjacob@feral.com) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id gAB3UgZ63765; Sun, 10 Nov 2002 19:30:42 -0800 (PST) (envelope-from mjacob@feral.com) Date: Sun, 10 Nov 2002 19:30:42 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: "Alan L. Cox" Cc: alpha@FreeBSD.ORG, John Baldwin Subject: Re: on the same note.. In-Reply-To: <3DCF1DD7.B472A23A@imimic.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, 10 Nov 2002, Alan L. Cox wrote: > Matthew Jacob wrote: > > > > > Matthew Jacob wrote: > > > > > > > > Err, well, this *is* in vm object allocation... > > > > > > Ah, I see what you're talking about now. Until the vm object has been > > > returned by the allocation routine it is not shared data. The > > > generation count is used to detect changes in the list of resident pages > > > by sleeping processes, not to detect that the same storage is being > > > recycled for a new object. > > > > > > > Well, if this is the case, the allocator shouldn't be just incrementing > > it, should it? Shouldn't it always start at zero? > > Basically, yes. This increment has existed for almost five years. At > this point, it only exists by inertia. DTRT then - at least remove the 'atomic XXX?' comment. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 3:54:24 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BCD1237B401; Mon, 11 Nov 2002 03:54:23 -0800 (PST) Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id E565243E42; Mon, 11 Nov 2002 03:54:22 -0800 (PST) (envelope-from mjacob@feral.com) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id gABBsMZ67167; Mon, 11 Nov 2002 03:54:22 -0800 (PST) (envelope-from mjacob@feral.com) Date: Mon, 11 Nov 2002 03:54:22 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: alpha@freebsd.org Cc: Ruslan Ermilov Subject: alpha floppy sets will be tested by rus ermilov Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I've noticed that ruslan seems to be leaping ahead- clearly he's got a better handle on this than I do. All further issues about floppy sizing *and testing* for alpha should be taken up with him. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 5:45:28 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0963E37B406 for ; Mon, 11 Nov 2002 05:45:25 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BE1F43E77 for ; Mon, 11 Nov 2002 05:45:24 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id IAA01466; Mon, 11 Nov 2002 08:45:20 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gABDioM47843; Mon, 11 Nov 2002 08:44:50 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15823.46162.102126.470628@grasshopper.cs.duke.edu> Date: Mon, 11 Nov 2002 08:44:50 -0500 (EST) To: Poul-Henning Kamp Cc: alpha@FreeBSD.ORG Subject: Re: ev4/5/6 issue ? In-Reply-To: <26565.1036953787@critter.freebsd.dk> References: <15822.35528.984561.534904@grasshopper.cs.duke.edu> <26565.1036953787@critter.freebsd.dk> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Poul-Henning Kamp writes: > > I get the trap on my alphastation 255, not on beast. OK, that wasn't clear to me before. I thought you were saying it also trapped on beast. > >What instruction is causing the trap? > > I have no idea, gdb doesn't offer any help as far as I can see :-( Just disassemble the code around the faulting instruction. Either using gdb's built-in disassembler or objdump. You do have the faulting instruction from gdb, right? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 5:50:30 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E460937B401 for ; Mon, 11 Nov 2002 05:50:28 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5016443E3B for ; Mon, 11 Nov 2002 05:50:27 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id gABDoDOr054464; Mon, 11 Nov 2002 14:50:13 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Andrew Gallatin Cc: alpha@FreeBSD.ORG Subject: Re: ev4/5/6 issue ? In-Reply-To: Your message of "Mon, 11 Nov 2002 08:44:50 EST." <15823.46162.102126.470628@grasshopper.cs.duke.edu> Date: Mon, 11 Nov 2002 14:50:13 +0100 Message-ID: <54463.1037022613@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message <15823.46162.102126.470628@grasshopper.cs.duke.edu>, Andrew Gallatin writes: > >Poul-Henning Kamp writes: > > > > I get the trap on my alphastation 255, not on beast. > >OK, that wasn't clear to me before. I thought you were saying it also >trapped on beast. > > >What instruction is causing the trap? > > > > I have no idea, gdb doesn't offer any help as far as I can see :-( > >Just disassemble the code around the faulting instruction. Either >using gdb's built-in disassembler or objdump. You do have the >faulting instruction from gdb, right? Yeah, well, gdb sort of chokes... l153# gdb /usr/bin/make [yak yak yak...] (gdb) run Starting program: /usr/bin/make warning: shared library handler failed to enable breakpoint Program received signal SIGILL, Illegal instruction. warning: Hit heuristic-fence-post without finding warning: enclosing function for address 0x12001f4e8 This warning occurs if you are debugging a function without any symbols (for example, in a stripped executable). In that case, you may wish to increase the size of the search with the `set heuristic-fence-post' command. Otherwise, you told GDB there was a function where there isn't one, or (more likely) you have encountered a bug in GDB. 0x12001f4e8 in ?? () (gdb) where #0 0x12001f4e8 in ?? () warning: Hit heuristic-fence-post without finding warning: enclosing function for address 0x120000218 (gdb) If this is an ev45/ev6 issue I guess my very na๏ve end-user questions are: 1. Why doesn't file(1) tell me if a binary is ev45 or ev6 ? 2. Couldn't the elf activator not find out and say "Sorry, cannot execute ev6 on this machine" ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 5:57:29 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A947237B401 for ; Mon, 11 Nov 2002 05:57:28 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14BEE43E6E for ; Mon, 11 Nov 2002 05:57:28 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id IAA01992; Mon, 11 Nov 2002 08:57:27 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gABDuvc47861; Mon, 11 Nov 2002 08:56:57 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15823.46889.535089.487743@grasshopper.cs.duke.edu> Date: Mon, 11 Nov 2002 08:56:57 -0500 (EST) To: Poul-Henning Kamp Cc: alpha@FreeBSD.ORG Subject: Re: ev4/5/6 issue ? In-Reply-To: <54463.1037022613@critter.freebsd.dk> References: <15823.46162.102126.470628@grasshopper.cs.duke.edu> <54463.1037022613@critter.freebsd.dk> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Poul-Henning Kamp writes: > (gdb) where > #0 0x12001f4e8 in ?? () Try 'disassemble' here, please. > > 1. Why doesn't file(1) tell me if a binary is ev45 or ev6 ? > > 2. Couldn't the elf activator not find out and say "Sorry, > cannot execute ev6 on this machine" ? Because there is no way of knowing, and in general, you don't need to know. As I said previously, the kernel is supposed to fixup newer instruction executed on older machines. However, this is expensive, and the toolchain should not be emitting code with those instructions in the first place, unless it is told to. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 6:44:49 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F180437B401 for ; Mon, 11 Nov 2002 06:44:47 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2095543E77 for ; Mon, 11 Nov 2002 06:44:46 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id gABEiVOr055060; Mon, 11 Nov 2002 15:44:31 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Andrew Gallatin Cc: alpha@FreeBSD.ORG Subject: Re: ev4/5/6 issue ? In-Reply-To: Your message of "Mon, 11 Nov 2002 08:56:57 EST." <15823.46889.535089.487743@grasshopper.cs.duke.edu> Date: Mon, 11 Nov 2002 15:44:31 +0100 Message-ID: <55059.1037025871@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message <15823.46889.535089.487743@grasshopper.cs.duke.edu>, Andrew Gallatin writes: > >Poul-Henning Kamp writes: > > (gdb) where > > #0 0x12001f4e8 in ?? () > >Try 'disassemble' here, please. (gdb) disassemble 0x12001f4e8 No function contains specified address. (gdb) disassemble No function contains program counter for selected frame. > > 1. Why doesn't file(1) tell me if a binary is ev45 or ev6 ? > > > > 2. Couldn't the elf activator not find out and say "Sorry, > > cannot execute ev6 on this machine" ? > >Because there is no way of knowing, and in general, you don't need to >know. Well, the compiler could put it somewhere in the elf and it seems like I do :-) >As I said previously, the kernel is supposed to fixup newer >instruction executed on older machines. However, this is expensive, >and the toolchain should not be emitting code with those instructions >in the first place, unless it is told to. Right, so much for theory :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 6:46:47 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 380CE37B401 for ; Mon, 11 Nov 2002 06:46:46 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F2A443E42 for ; Mon, 11 Nov 2002 06:46:45 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA04126; Mon, 11 Nov 2002 09:46:45 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gABEkFF47910; Mon, 11 Nov 2002 09:46:15 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15823.49846.975380.623043@grasshopper.cs.duke.edu> Date: Mon, 11 Nov 2002 09:46:14 -0500 (EST) To: Poul-Henning Kamp Cc: alpha@FreeBSD.ORG Subject: Re: ev4/5/6 issue ? In-Reply-To: <55059.1037025871@critter.freebsd.dk> References: <15823.46889.535089.487743@grasshopper.cs.duke.edu> <55059.1037025871@critter.freebsd.dk> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Poul-Henning Kamp writes: > In message <15823.46889.535089.487743@grasshopper.cs.duke.edu>, Andrew Gallatin > writes: > > > >Poul-Henning Kamp writes: > > > (gdb) where > > > #0 0x12001f4e8 in ?? () > > > >Try 'disassemble' here, please. > > (gdb) disassemble 0x12001f4e8 > No function contains specified address. > Use binutils then. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 6:49:11 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F313C37B401 for ; Mon, 11 Nov 2002 06:49:09 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5628F43E42 for ; Mon, 11 Nov 2002 06:49:09 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA04258; Mon, 11 Nov 2002 09:49:08 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gABEmcg47915; Mon, 11 Nov 2002 09:48:38 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15823.49990.899445.424699@grasshopper.cs.duke.edu> Date: Mon, 11 Nov 2002 09:48:38 -0500 (EST) To: Poul-Henning Kamp Cc: alpha@FreeBSD.ORG Subject: Re: ev4/5/6 issue ? In-Reply-To: <15823.49846.975380.623043@grasshopper.cs.duke.edu> References: <15823.46889.535089.487743@grasshopper.cs.duke.edu> <55059.1037025871@critter.freebsd.dk> <15823.49846.975380.623043@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Andrew Gallatin writes: > > Poul-Henning Kamp writes: > > In message <15823.46889.535089.487743@grasshopper.cs.duke.edu>, Andrew Gallatin > > writes: > > > > > >Poul-Henning Kamp writes: > > > > (gdb) where > > > > #0 0x12001f4e8 in ?? () > > > > > >Try 'disassemble' here, please. > > > > (gdb) disassemble 0x12001f4e8 > > No function contains specified address. > > > > Use binutils then. > (eg objdump -d) Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 6:53:44 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA02F37B401 for ; Mon, 11 Nov 2002 06:53:42 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 176D543E42 for ; Mon, 11 Nov 2002 06:53:41 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id gABErVOr055221; Mon, 11 Nov 2002 15:53:31 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Andrew Gallatin Cc: alpha@FreeBSD.ORG Subject: Re: ev4/5/6 issue ? In-Reply-To: Your message of "Mon, 11 Nov 2002 09:48:38 EST." <15823.49990.899445.424699@grasshopper.cs.duke.edu> Date: Mon, 11 Nov 2002 15:53:31 +0100 Message-ID: <55220.1037026411@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message <15823.49990.899445.424699@grasshopper.cs.duke.edu>, Andrew Gallatin writes: > >Andrew Gallatin writes: > > > > Poul-Henning Kamp writes: > > > In message <15823.46889.535089.487743@grasshopper.cs.duke.edu>, Andrew Gallatin > > > writes: > > > > > > > >Poul-Henning Kamp writes: > > > > > (gdb) where > > > > > #0 0x12001f4e8 in ?? () > > > > > > > >Try 'disassemble' here, please. > > > > > > (gdb) disassemble 0x12001f4e8 > > > No function contains specified address. > > > > >(eg objdump -d) 12001f4cc: 20 00 9e b5 stq s3,32(sp) 12001f4d0: 28 00 be b5 stq s4,40(sp) 12001f4d4: 30 00 de b5 stq s5,48(sp) 12001f4d8: 38 00 fe b5 stq fp,56(sp) 12001f4dc: 40 00 5e 9c stt $f2,64(sp) 12001f4e0: 48 00 7e 9c stt $f3,72(sp) 12001f4e4: 82 04 1f 52 itoft a0,$f2 12001f4e8: d0 88 3d a4 ldq t0,-30512(gp) 12001f4ec: 00 00 21 a0 ldl t0,0(t0) 12001f4f0: 05 00 20 e4 beq t0,0x12001f508 12001f4f4: b0 a2 1d a6 ldq a0,-23888(gp) 12001f4f8: 68 80 7d a7 ldq t12,-32664(gp) 12001f4fc: 38 62 5b 6b jsr ra,(t12),0x120017de0 12001f500: 04 00 ba 27 ldah gp,4(ra) 12001f504: d0 f5 bd 23 lda gp,-2608(gp) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 7:17:38 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04D4937B401 for ; Mon, 11 Nov 2002 07:17:37 -0800 (PST) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE35743E3B for ; Mon, 11 Nov 2002 07:17:35 -0800 (PST) (envelope-from ticso@cicely8.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) by srv1.cosmo-project.de (8.12.5/8.12.5) with ESMTP id gABFHNsP098772 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Mon, 11 Nov 2002 16:17:25 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.1.10]) by cicely5.cicely.de (8.12.6/8.12.6) with ESMTP id gABFHMCu053900 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 11 Nov 2002 16:17:22 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (localhost [127.0.0.1]) by cicely8.cicely.de (8.12.6/8.12.6) with ESMTP id gABFHLl8064945; Mon, 11 Nov 2002 16:17:21 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: (from ticso@localhost) by cicely8.cicely.de (8.12.6/8.12.6/Submit) id gABFHL5T064944; Mon, 11 Nov 2002 16:17:21 +0100 (CET) Date: Mon, 11 Nov 2002 16:17:21 +0100 From: Bernd Walter To: Poul-Henning Kamp Cc: Andrew Gallatin , alpha@FreeBSD.ORG Subject: Re: ev4/5/6 issue ? Message-ID: <20021111151721.GB57193@cicely8.cicely.de> Reply-To: ticso@cicely.de References: <15823.49990.899445.424699@grasshopper.cs.duke.edu> <55220.1037026411@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55220.1037026411@critter.freebsd.dk> X-Operating-System: FreeBSD cicely8.cicely.de 5.0-CURRENT i386 User-Agent: Mutt/1.5.1i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Nov 11, 2002 at 03:53:31PM +0100, Poul-Henning Kamp wrote: > In message <15823.49990.899445.424699@grasshopper.cs.duke.edu>, Andrew Gallatin > writes: > > > >Andrew Gallatin writes: > > > > > > Poul-Henning Kamp writes: > > > > In message <15823.46889.535089.487743@grasshopper.cs.duke.edu>, Andrew Gallatin > > > > writes: > > > > > > > > > >Poul-Henning Kamp writes: > > > > > > (gdb) where > > > > > > #0 0x12001f4e8 in ?? () > > > > > > > > > >Try 'disassemble' here, please. > > > > > > > > (gdb) disassemble 0x12001f4e8 > > > > No function contains specified address. > > > > > > > >(eg objdump -d) > > 12001f4cc: 20 00 9e b5 stq s3,32(sp) > 12001f4d0: 28 00 be b5 stq s4,40(sp) > 12001f4d4: 30 00 de b5 stq s5,48(sp) > 12001f4d8: 38 00 fe b5 stq fp,56(sp) > 12001f4dc: 40 00 5e 9c stt $f2,64(sp) > 12001f4e0: 48 00 7e 9c stt $f3,72(sp) > 12001f4e4: 82 04 1f 52 itoft a0,$f2 > 12001f4e8: d0 88 3d a4 ldq t0,-30512(gp) > 12001f4ec: 00 00 21 a0 ldl t0,0(t0) > 12001f4f0: 05 00 20 e4 beq t0,0x12001f508 > 12001f4f4: b0 a2 1d a6 ldq a0,-23888(gp) > 12001f4f8: 68 80 7d a7 ldq t12,-32664(gp) > 12001f4fc: 38 62 5b 6b jsr ra,(t12),0x120017de0 > 12001f500: 04 00 ba 27 ldah gp,4(ra) > 12001f504: d0 f5 bd 23 lda gp,-2608(gp) These opcodes should all work on every alpha cpu without emulation. I would asume that either the address is wrong, your hardware is broken or a bug has corrupted the code. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 7:18:45 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B4A037B401 for ; Mon, 11 Nov 2002 07:18:44 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id A606343E75 for ; Mon, 11 Nov 2002 07:18:43 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA06090; Mon, 11 Nov 2002 10:18:43 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gABFIDA47946; Mon, 11 Nov 2002 10:18:13 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15823.51765.171947.796322@grasshopper.cs.duke.edu> Date: Mon, 11 Nov 2002 10:18:13 -0500 (EST) To: Poul-Henning Kamp Cc: alpha@FreeBSD.ORG Subject: Re: ev4/5/6 issue ? In-Reply-To: <55220.1037026411@critter.freebsd.dk> References: <15823.49990.899445.424699@grasshopper.cs.duke.edu> <55220.1037026411@critter.freebsd.dk> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Poul-Henning Kamp writes: > 12001f4e4: 82 04 1f 52 itoft a0,$f2 OK, this is a FIX instruction, which is not implemented on ev4, nor even ev5 or ev56. We also don't bother to emulate it in the kernel, since no commercial binaries depend on it. Your initial assertion that this might be happening because the libraries are built for ev6 on beast could be true. Can you verify that that 12001f4e4 is indeed inside a library function using nm? (12001f4e4 is looks like a library address, but it would be better to be certain). If so, perhaps you could link make shared on beast and get yourself bootstrapped that way. That doesn't solve the initial problem of why your make was busted, though. If its in the libs, then your libs are likely busted too. Perhaps you'll also need to build a libc on beast, explicitly setting your cpuflags to ev4. Or perhaps the compiler is emitting FIX instructions when it should not. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 7:21:23 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7CFB037B401 for ; Mon, 11 Nov 2002 07:21:22 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id D900643E6E for ; Mon, 11 Nov 2002 07:21:21 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA06295; Mon, 11 Nov 2002 10:21:21 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gABFKpF47954; Mon, 11 Nov 2002 10:20:51 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15823.51923.39593.321255@grasshopper.cs.duke.edu> Date: Mon, 11 Nov 2002 10:20:51 -0500 (EST) To: ticso@cicely.de Cc: alpha@FreeBSD.ORG Subject: Re: ev4/5/6 issue ? In-Reply-To: <20021111151721.GB57193@cicely8.cicely.de> References: <15823.49990.899445.424699@grasshopper.cs.duke.edu> <55220.1037026411@critter.freebsd.dk> <20021111151721.GB57193@cicely8.cicely.de> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Bernd Walter writes: > > 12001f4e4: 82 04 1f 52 itoft a0,$f2 <...> > These opcodes should all work on every alpha cpu without emulation. > I would asume that either the address is wrong, your hardware is > broken or a bug has corrupted the code. Isn't itoft a FIX instruction? The brown book doesn't mention it as such (which is surprising, as its careful to point out ldbu, etc as BWX), but various online sources describing FIX instructions list it as one.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 7:42: 6 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E06F37B401 for ; Mon, 11 Nov 2002 07:42:05 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26E0A43E3B for ; Mon, 11 Nov 2002 07:42:04 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id gABFftOr055810; Mon, 11 Nov 2002 16:41:55 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Andrew Gallatin Cc: alpha@FreeBSD.ORG Subject: Re: ev4/5/6 issue ? In-Reply-To: Your message of "Mon, 11 Nov 2002 10:18:13 EST." <15823.51765.171947.796322@grasshopper.cs.duke.edu> Date: Mon, 11 Nov 2002 16:41:55 +0100 Message-ID: <55809.1037029315@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message <15823.51765.171947.796322@grasshopper.cs.duke.edu>, Andrew Gallatin writes: >Your initial assertion that this might be happening because the >libraries are built for ev6 on beast could be true. Can you verify >that that 12001f4e4 is indeed inside a library function using nm? Well, GDB said that much already. >That doesn't solve the initial problem of why your make was busted, >though. If its in the libs, then your libs are likely busted too. >Perhaps you'll also need to build a libc on beast, explicitly >setting your cpuflags to ev4. Or perhaps the compiler is emitting >FIX instructions when it should not. I think ev4 should be the default on beast. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 7:48:22 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 15C4D37B404 for ; Mon, 11 Nov 2002 07:48:21 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C83343E3B for ; Mon, 11 Nov 2002 07:48:20 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA08342; Mon, 11 Nov 2002 10:48:19 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gABFlnJ47979; Mon, 11 Nov 2002 10:47:49 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15823.53541.490794.635227@grasshopper.cs.duke.edu> Date: Mon, 11 Nov 2002 10:47:49 -0500 (EST) To: Poul-Henning Kamp Cc: alpha@FreeBSD.ORG Subject: Re: ev4/5/6 issue ? In-Reply-To: <55809.1037029315@critter.freebsd.dk> References: <15823.51765.171947.796322@grasshopper.cs.duke.edu> <55809.1037029315@critter.freebsd.dk> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Poul-Henning Kamp writes: > In message <15823.51765.171947.796322@grasshopper.cs.duke.edu>, Andrew Gallatin > writes: > > >Your initial assertion that this might be happening because the > >libraries are built for ev6 on beast could be true. Can you verify > >that that 12001f4e4 is indeed inside a library function using nm? > > Well, GDB said that much already. It did? Which function? That's what I want to know.. > >That doesn't solve the initial problem of why your make was busted, > >though. If its in the libs, then your libs are likely busted too. > >Perhaps you'll also need to build a libc on beast, explicitly > >setting your cpuflags to ev4. Or perhaps the compiler is emitting > >FIX instructions when it should not. > > I think ev4 should be the default on beast. No, the build process or tools should be fixed. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 7:58: 3 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 320D737B401 for ; Mon, 11 Nov 2002 07:58:02 -0800 (PST) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36E9543E42 for ; Mon, 11 Nov 2002 07:58:01 -0800 (PST) (envelope-from ticso@cicely8.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) by srv1.cosmo-project.de (8.12.5/8.12.5) with ESMTP id gABFvssP099451 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Mon, 11 Nov 2002 16:57:56 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.1.10]) by cicely5.cicely.de (8.12.6/8.12.6) with ESMTP id gABFvqCu054126 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 11 Nov 2002 16:57:53 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (localhost [127.0.0.1]) by cicely8.cicely.de (8.12.6/8.12.6) with ESMTP id gABFvql8065030; Mon, 11 Nov 2002 16:57:52 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: (from ticso@localhost) by cicely8.cicely.de (8.12.6/8.12.6/Submit) id gABFvpvA065029; Mon, 11 Nov 2002 16:57:51 +0100 (CET) Date: Mon, 11 Nov 2002 16:57:51 +0100 From: Bernd Walter To: Andrew Gallatin Cc: ticso@cicely.de, alpha@FreeBSD.ORG Subject: Re: ev4/5/6 issue ? Message-ID: <20021111155750.GC57193@cicely8.cicely.de> Reply-To: ticso@cicely.de References: <15823.49990.899445.424699@grasshopper.cs.duke.edu> <55220.1037026411@critter.freebsd.dk> <20021111151721.GB57193@cicely8.cicely.de> <15823.51923.39593.321255@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15823.51923.39593.321255@grasshopper.cs.duke.edu> X-Operating-System: FreeBSD cicely8.cicely.de 5.0-CURRENT i386 User-Agent: Mutt/1.5.1i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Nov 11, 2002 at 10:20:51AM -0500, Andrew Gallatin wrote: > > Bernd Walter writes: > > > 12001f4e4: 82 04 1f 52 itoft a0,$f2 > > <...> > > These opcodes should all work on every alpha cpu without emulation. > > I would asume that either the address is wrong, your hardware is > > broken or a bug has corrupted the code. > > Isn't itoft a FIX instruction? The brown book doesn't mention it as > such (which is surprising, as its careful to point out ldbu, etc as > BWX), but various online sources describing FIX instructions list it > as one.. You could be right - I had only looked into the command description where it is not mentioned as a special command, but yes it is listed as FIX in the AMASK description. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 8:12:39 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 79A7137B401 for ; Mon, 11 Nov 2002 08:12:38 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 281D743E4A for ; Mon, 11 Nov 2002 08:12:37 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id gABGCLOr056206; Mon, 11 Nov 2002 17:12:21 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Andrew Gallatin Cc: alpha@FreeBSD.ORG Subject: Re: ev4/5/6 issue ? In-Reply-To: Your message of "Mon, 11 Nov 2002 10:47:49 EST." <15823.53541.490794.635227@grasshopper.cs.duke.edu> Date: Mon, 11 Nov 2002 17:12:21 +0100 Message-ID: <56205.1037031141@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message <15823.53541.490794.635227@grasshopper.cs.duke.edu>, Andrew Gallatin writes: > >Poul-Henning Kamp writes: > > In message <15823.51765.171947.796322@grasshopper.cs.duke.edu>, Andrew Gallatin > > writes: > > > > >Your initial assertion that this might be happening because the > > >libraries are built for ev6 on beast could be true. Can you verify > > >that that 12001f4e4 is indeed inside a library function using nm? > > > > Well, GDB said that much already. > >It did? Which function? That's what I want to know.. It said it was in a library so it had no symbols. > > I think ev4 should be the default on beast. > >No, the build process or tools should be fixed. Whatever... Hopefully somebody produces a snapshot I can use to install some day, until then I seem to be hosed. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 8:18:23 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0991C37B42C for ; Mon, 11 Nov 2002 08:18:23 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E58543E6E for ; Mon, 11 Nov 2002 08:18:21 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA10518; Mon, 11 Nov 2002 11:18:11 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gABGHfM48015; Mon, 11 Nov 2002 11:17:41 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15823.55333.363606.765616@grasshopper.cs.duke.edu> Date: Mon, 11 Nov 2002 11:17:41 -0500 (EST) To: Poul-Henning Kamp Cc: alpha@FreeBSD.ORG Subject: Re: ev4/5/6 issue ? In-Reply-To: <56205.1037031141@critter.freebsd.dk> References: <15823.53541.490794.635227@grasshopper.cs.duke.edu> <56205.1037031141@critter.freebsd.dk> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Poul-Henning Kamp writes: > > Whatever... > > Hopefully somebody produces a snapshot I can use to install some day, > until then I seem to be hosed. Yep, whatever. Thanks for all your help in tracking this problem down.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 9:23:21 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0760437B485 for ; Mon, 11 Nov 2002 09:23:16 -0800 (PST) Received: from mail.speakeasy.net (mail17.speakeasy.net [216.254.0.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D95743E75 for ; Mon, 11 Nov 2002 09:23:16 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 10201 invoked from network); 11 Nov 2002 17:23:19 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail17.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 11 Nov 2002 17:23:19 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.6/8.12.6) with ESMTP id gABHND2D001600; Mon, 11 Nov 2002 12:23:14 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <55809.1037029315@critter.freebsd.dk> Date: Mon, 11 Nov 2002 12:23:15 -0500 (EST) From: John Baldwin To: Poul-Henning Kamp Subject: Re: ev4/5/6 issue ? Cc: alpha@FreeBSD.ORG, Andrew Gallatin Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 11-Nov-2002 Poul-Henning Kamp wrote: > In message <15823.51765.171947.796322@grasshopper.cs.duke.edu>, Andrew Gallatin > writes: > >>Your initial assertion that this might be happening because the >>libraries are built for ev6 on beast could be true. Can you verify >>that that 12001f4e4 is indeed inside a library function using nm? > > Well, GDB said that much already. > >>That doesn't solve the initial problem of why your make was busted, >>though. If its in the libs, then your libs are likely busted too. >>Perhaps you'll also need to build a libc on beast, explicitly >>setting your cpuflags to ev4. Or perhaps the compiler is emitting >>FIX instructions when it should not. > > I think ev4 should be the default on beast. This release wasn't built on beast. It was built on a DS20 (which is an EV6). However, it should be built with '-mcpu=ev4 -mtune=ev6' so it should not be using any !ev4 instructions. Perhaps -mtune is broken? Hmm, actually, the whole release was compiled with '-mcpu=ev5 -mtune=ev5'. I do know that on alpha gcc "adjusts" itself to whatever CPU it is built on, so maybe because the gcc in the release make world was built on an EV6 it thinks it can emit EV6 instructions? Weird. -- 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 Nov 11 9:39:20 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E33B37B401; Mon, 11 Nov 2002 09:39:17 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E70243E4A; Mon, 11 Nov 2002 09:39:16 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id gABHd1Or057359; Mon, 11 Nov 2002 18:39:01 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Baldwin Cc: alpha@FreeBSD.org, Andrew Gallatin Subject: Re: ev4/5/6 issue ? In-Reply-To: Your message of "Mon, 11 Nov 2002 12:23:15 EST." Date: Mon, 11 Nov 2002 18:39:01 +0100 Message-ID: <57358.1037036341@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message , John Baldwin writes: > >On 11-Nov-2002 Poul-Henning Kamp wrote: >> In message <15823.51765.171947.796322@grasshopper.cs.duke.edu>, Andrew Gallatin >> writes: >> >>>Your initial assertion that this might be happening because the >>>libraries are built for ev6 on beast could be true. Can you verify >>>that that 12001f4e4 is indeed inside a library function using nm? >> >> Well, GDB said that much already. >> >>>That doesn't solve the initial problem of why your make was busted, >>>though. If its in the libs, then your libs are likely busted too. >>>Perhaps you'll also need to build a libc on beast, explicitly >>>setting your cpuflags to ev4. Or perhaps the compiler is emitting >>>FIX instructions when it should not. >> >> I think ev4 should be the default on beast. > >This release wasn't built on beast. It was built on a DS20 (which >is an EV6). However, it should be built with '-mcpu=ev4 -mtune=ev6' >so it should not be using any !ev4 instructions. Perhaps -mtune >is broken? Could be, but I tried to build some binaries on beast to recover and was bitten by beast generating ev6 as default. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 10: 2:34 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD33C37B407; Mon, 11 Nov 2002 10:02:32 -0800 (PST) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5ED6843E4A; Mon, 11 Nov 2002 10:02:30 -0800 (PST) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.6/8.12.6) with ESMTP id gABI2Po9051038; Mon, 11 Nov 2002 19:02:25 +0100 (CET) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.6/8.12.6/Submit) id gABI2OMn051037; Mon, 11 Nov 2002 19:02:24 +0100 (CET) Date: Mon, 11 Nov 2002 19:02:24 +0100 From: Wilko Bulte To: John Baldwin Cc: Poul-Henning Kamp , alpha@FreeBSD.ORG, Andrew Gallatin Subject: Re: ev4/5/6 issue ? Message-ID: <20021111190224.B50999@freebie.xs4all.nl> References: <55809.1037029315@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.ORG on Mon, Nov 11, 2002 at 12:23:15PM -0500 X-OS: FreeBSD 4.7-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Nov 11, 2002 at 12:23:15PM -0500, John Baldwin wrote: > > On 11-Nov-2002 Poul-Henning Kamp wrote: > > In message <15823.51765.171947.796322@grasshopper.cs.duke.edu>, Andrew Gallatin > > writes: > > > >>Your initial assertion that this might be happening because the > >>libraries are built for ev6 on beast could be true. Can you verify > >>that that 12001f4e4 is indeed inside a library function using nm? > > > > Well, GDB said that much already. > > > >>That doesn't solve the initial problem of why your make was busted, > >>though. If its in the libs, then your libs are likely busted too. > >>Perhaps you'll also need to build a libc on beast, explicitly > >>setting your cpuflags to ev4. Or perhaps the compiler is emitting > >>FIX instructions when it should not. > > > > I think ev4 should be the default on beast. > > This release wasn't built on beast. It was built on a DS20 (which > is an EV6). However, it should be built with '-mcpu=ev4 -mtune=ev6' > so it should not be using any !ev4 instructions. Perhaps -mtune > is broken? > > Hmm, actually, the whole release was compiled with Is this 4.7R we are talking about? > '-mcpu=ev5 -mtune=ev5'. I do know that on alpha gcc "adjusts" itself > to whatever CPU it is built on, so maybe because the gcc in the release > make world was built on an EV6 it thinks it can emit EV6 instructions? I tested 4.7-RCs on EV4 machines (AS200, AS500, PC64) without incident. Poul: what machine did you have? /me has a secret cache of Alpha CPUs here.. :-P -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 10: 2:48 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71DF637B406 for ; Mon, 11 Nov 2002 10:02:47 -0800 (PST) Received: from mail.speakeasy.net (mail16.speakeasy.net [216.254.0.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id 066CC43E75 for ; Mon, 11 Nov 2002 10:02:47 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 32066 invoked from network); 11 Nov 2002 18:02:51 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail16.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 11 Nov 2002 18:02:51 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.6/8.12.6) with ESMTP id gABI2i2D001785; Mon, 11 Nov 2002 13:02:44 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <57358.1037036341@critter.freebsd.dk> Date: Mon, 11 Nov 2002 13:02:45 -0500 (EST) From: John Baldwin To: Poul-Henning Kamp Subject: Re: ev4/5/6 issue ? Cc: Andrew Gallatin , alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 11-Nov-2002 Poul-Henning Kamp wrote: > In message , John Baldwin writes: >> >>On 11-Nov-2002 Poul-Henning Kamp wrote: >>> In message <15823.51765.171947.796322@grasshopper.cs.duke.edu>, Andrew Gallatin >>> writes: >>> >>>>Your initial assertion that this might be happening because the >>>>libraries are built for ev6 on beast could be true. Can you verify >>>>that that 12001f4e4 is indeed inside a library function using nm? >>> >>> Well, GDB said that much already. >>> >>>>That doesn't solve the initial problem of why your make was busted, >>>>though. If its in the libs, then your libs are likely busted too. >>>>Perhaps you'll also need to build a libc on beast, explicitly >>>>setting your cpuflags to ev4. Or perhaps the compiler is emitting >>>>FIX instructions when it should not. >>> >>> I think ev4 should be the default on beast. >> >>This release wasn't built on beast. It was built on a DS20 (which >>is an EV6). However, it should be built with '-mcpu=ev4 -mtune=ev6' >>so it should not be using any !ev4 instructions. Perhaps -mtune >>is broken? > > Could be, but I tried to build some binaries on beast to recover > and was bitten by beast generating ev6 as default. make CPUTYPE="" all -- 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 Nov 11 10: 5:13 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6174537B401; Mon, 11 Nov 2002 10:05:12 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23EAF43E3B; Mon, 11 Nov 2002 10:05:11 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id gABI52Or057667; Mon, 11 Nov 2002 19:05:02 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Baldwin Cc: Andrew Gallatin , alpha@FreeBSD.org Subject: Re: ev4/5/6 issue ? In-Reply-To: Your message of "Mon, 11 Nov 2002 13:02:45 EST." Date: Mon, 11 Nov 2002 19:05:02 +0100 Message-ID: <57666.1037037902@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message , John Baldwin writes: > >On 11-Nov-2002 Poul-Henning Kamp wrote: >> In message , John Baldwin writes: >>> >>>On 11-Nov-2002 Poul-Henning Kamp wrote: >>>> In message <15823.51765.171947.796322@grasshopper.cs.duke.edu>, Andrew Gallatin >>>> writes: >>>> >>>>>Your initial assertion that this might be happening because the >>>>>libraries are built for ev6 on beast could be true. Can you verify >>>>>that that 12001f4e4 is indeed inside a library function using nm? >>>> >>>> Well, GDB said that much already. >>>> >>>>>That doesn't solve the initial problem of why your make was busted, >>>>>though. If its in the libs, then your libs are likely busted too. >>>>>Perhaps you'll also need to build a libc on beast, explicitly >>>>>setting your cpuflags to ev4. Or perhaps the compiler is emitting >>>>>FIX instructions when it should not. >>>> >>>> I think ev4 should be the default on beast. >>> >>>This release wasn't built on beast. It was built on a DS20 (which >>>is an EV6). However, it should be built with '-mcpu=ev4 -mtune=ev6' >>>so it should not be using any !ev4 instructions. Perhaps -mtune >>>is broken? >> >> Could be, but I tried to build some binaries on beast to recover >> and was bitten by beast generating ev6 as default. > >make CPUTYPE="" all I'm not convinced that works for a kernel actually. sys/conf/kern.mk contains: .if ${MACHINE_ARCH} == "alpha" CFLAGS+= -mno-fp-regs -ffixed-8 -Wa,-mev6 .endif -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 10: 7: 1 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B58F37B401; Mon, 11 Nov 2002 10:07:00 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C48043E3B; Mon, 11 Nov 2002 10:06:59 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA19871; Mon, 11 Nov 2002 13:06:58 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gABI6Q848106; Mon, 11 Nov 2002 13:06:26 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15823.61858.784838.471039@grasshopper.cs.duke.edu> Date: Mon, 11 Nov 2002 13:06:26 -0500 (EST) To: John Baldwin Cc: alpha@FreeBSD.org, obrien@FreeBSD.org, kan@FreeBSD.org Subject: Re: ev4/5/6 issue ? In-Reply-To: References: <55809.1037029315@critter.freebsd.dk> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org John Baldwin writes: > so it should not be using any !ev4 instructions. Perhaps -mtune > is broken? > > Hmm, actually, the whole release was compiled with > '-mcpu=ev5 -mtune=ev5'. I do know that on alpha gcc "adjusts" itself > to whatever CPU it is built on, so maybe because the gcc in the release > make world was built on an EV6 it thinks it can emit EV6 instructions? > > Weird. I was worried about this self-adjustment myself, but I thought that it was a function of gnu configure, and would be taken care of by the way we emulate or otherwise fake-out configre for the in-tree gcc. gcc gurus? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 10:11:18 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3516A37B401; Mon, 11 Nov 2002 10:11:17 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63F3143E4A; Mon, 11 Nov 2002 10:11:16 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA20311; Mon, 11 Nov 2002 13:11:15 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gABIAjX48118; Mon, 11 Nov 2002 13:10:45 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15823.62117.919469.410057@grasshopper.cs.duke.edu> Date: Mon, 11 Nov 2002 13:10:45 -0500 (EST) To: Poul-Henning Kamp Cc: John Baldwin , alpha@FreeBSD.ORG Subject: Re: ev4/5/6 issue ? In-Reply-To: <57666.1037037902@critter.freebsd.dk> References: <57666.1037037902@critter.freebsd.dk> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Poul-Henning Kamp writes: > >make CPUTYPE="" all > > I'm not convinced that works for a kernel actually. sys/conf/kern.mk > contains: > > .if ${MACHINE_ARCH} == "alpha" > CFLAGS+= -mno-fp-regs -ffixed-8 -Wa,-mev6 > .endif > This should just affect what gas will accept, not what gcc generates. It read '-mev56' for the entire history of FreeBSD/alpha until it was upgraded 2 months ago. It has caused zero problems in the last 3 years. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 10:20:15 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E08E37B401; Mon, 11 Nov 2002 10:20:14 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id A471143E3B; Mon, 11 Nov 2002 10:20:12 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id gABIK2Or057863; Mon, 11 Nov 2002 19:20:03 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Wilko Bulte Cc: John Baldwin , alpha@FreeBSD.ORG, Andrew Gallatin Subject: Re: ev4/5/6 issue ? In-Reply-To: Your message of "Mon, 11 Nov 2002 19:02:24 +0100." <20021111190224.B50999@freebie.xs4all.nl> Date: Mon, 11 Nov 2002 19:20:02 +0100 Message-ID: <57862.1037038802@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message <20021111190224.B50999@freebie.xs4all.nl>, Wilko Bulte writes: >Poul: what machine did you have? /me has a secret cache of Alpha CPUs >here.. :-P AlphaStation255/233 -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 10:20:17 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E683B37B404 for ; Mon, 11 Nov 2002 10:20:14 -0800 (PST) Received: from mail.speakeasy.net (mail14.speakeasy.net [216.254.0.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 742DA43E3B for ; Mon, 11 Nov 2002 10:20:14 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 27090 invoked from network); 11 Nov 2002 18:20:19 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail14.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 11 Nov 2002 18:20:19 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.6/8.12.6) with ESMTP id gABIKC2D001867; Mon, 11 Nov 2002 13:20:12 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20021111190224.B50999@freebie.xs4all.nl> Date: Mon, 11 Nov 2002 13:20:13 -0500 (EST) From: John Baldwin To: Wilko Bulte Subject: Re: ev4/5/6 issue ? Cc: Andrew Gallatin , alpha@FreeBSD.ORG, Poul-Henning Kamp Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 11-Nov-2002 Wilko Bulte wrote: > On Mon, Nov 11, 2002 at 12:23:15PM -0500, John Baldwin wrote: >> >> On 11-Nov-2002 Poul-Henning Kamp wrote: >> > In message <15823.51765.171947.796322@grasshopper.cs.duke.edu>, Andrew Gallatin >> > writes: >> > >> >>Your initial assertion that this might be happening because the >> >>libraries are built for ev6 on beast could be true. Can you verify >> >>that that 12001f4e4 is indeed inside a library function using nm? >> > >> > Well, GDB said that much already. >> > >> >>That doesn't solve the initial problem of why your make was busted, >> >>though. If its in the libs, then your libs are likely busted too. >> >>Perhaps you'll also need to build a libc on beast, explicitly >> >>setting your cpuflags to ev4. Or perhaps the compiler is emitting >> >>FIX instructions when it should not. >> > >> > I think ev4 should be the default on beast. >> >> This release wasn't built on beast. It was built on a DS20 (which >> is an EV6). However, it should be built with '-mcpu=ev4 -mtune=ev6' >> so it should not be using any !ev4 instructions. Perhaps -mtune >> is broken? >> >> Hmm, actually, the whole release was compiled with > > Is this 4.7R we are talking about? > >> '-mcpu=ev5 -mtune=ev5'. I do know that on alpha gcc "adjusts" itself >> to whatever CPU it is built on, so maybe because the gcc in the release >> make world was built on an EV6 it thinks it can emit EV6 instructions? > > I tested 4.7-RCs on EV4 machines (AS200, AS500, PC64) without incident. > > Poul: what machine did you have? /me has a secret cache of Alpha CPUs > here.. :-P No, this is a 5.0 snapshot. Compiled on the same exact machine as 4.7, but under -current rathern than under -stable. -- 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 Nov 11 13:35: 0 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED13937B401 for ; Mon, 11 Nov 2002 13:34:59 -0800 (PST) Received: from server07.icaen.uiowa.edu (server07.icaen.uiowa.edu [128.255.17.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 113A343E42 for ; Mon, 11 Nov 2002 13:34:59 -0800 (PST) (envelope-from michael-mackey@uiowa.edu) Received: from server11.icaen.uiowa.edu (server11.icaen.uiowa.edu [128.255.17.51]) by server07.icaen.uiowa.edu (8.9.3/8.9.3) with ESMTP id PAA00663 for sent by ; Mon, 11 Nov 2002 15:35:05 -0600 (CST) Received: from focaccia. (12-217-236-86.client.mchsi.com [12.217.236.86]) by server11.icaen.uiowa.edu (8.9.3/smtp-service-1.6) with ESMTP id PAA01950 for ; sent by ; Mon, 11 Nov 2002 15:34:46 -0600 (CST) Subject: Extreme time drift in SMP mode From: "Michael A. Mackey" To: freebsd-alpha@FreeBSD.ORG Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 11 Nov 2002 15:34:40 -0600 Message-Id: <1037050487.14529.17.camel@focaccia.> Mime-Version: 1.0 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have recently installed 5.0-CURRENT onto my AlphaServer 2100A. When running an SMP kernel, the time drift is very large. I am running ntpd, but it doesn't correct the error in system time. The only solution: use CRON to run ntpdate (this prevents ntpd from running) efvery few minutes. This solution is much less than desirable, as I won;t this box to run kerberos. Is there some solution to this problem? Michael Mackey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 13:57:11 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B08D37B401 for ; Mon, 11 Nov 2002 13:57:10 -0800 (PST) Received: from mail.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25A0C43E4A for ; Mon, 11 Nov 2002 13:57:10 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 24129 invoked from network); 11 Nov 2002 21:57:17 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 11 Nov 2002 21:57:17 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.6/8.12.6) with ESMTP id gABLv72D002371; Mon, 11 Nov 2002 16:57:08 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <1037050487.14529.17.camel@focaccia.> Date: Mon, 11 Nov 2002 16:57:09 -0500 (EST) From: John Baldwin To: "Michael A. Mackey" Subject: RE: Extreme time drift in SMP mode Cc: freebsd-alpha@FreeBSD.ORG Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 11-Nov-2002 Michael A. Mackey wrote: > I have recently installed 5.0-CURRENT onto my AlphaServer 2100A. When > running an SMP kernel, the time drift is very large. > > I am running ntpd, but it doesn't correct the error in system time. > > The only solution: use CRON to run ntpdate (this prevents ntpd from > running) efvery few minutes. This solution is much less than desirable, > as I won;t this box to run kerberos. > > Is there some solution to this problem? Not at the moment. Does the time run too fast or too slow? -- 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 Nov 11 14: 0: 5 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B2A2537B401 for ; Mon, 11 Nov 2002 14:00:04 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DE2543E75 for ; Mon, 11 Nov 2002 14:00:00 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id QAA03128; Mon, 11 Nov 2002 16:59:56 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gABLxQ548342; Mon, 11 Nov 2002 16:59:26 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15824.10302.110339.545856@grasshopper.cs.duke.edu> Date: Mon, 11 Nov 2002 16:59:26 -0500 (EST) To: "Michael A. Mackey" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Extreme time drift in SMP mode In-Reply-To: <1037050487.14529.17.camel@focaccia.> References: <1037050487.14529.17.camel@focaccia.> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Michael A. Mackey writes: > I have recently installed 5.0-CURRENT onto my AlphaServer 2100A. When > running an SMP kernel, the time drift is very large. > > I am running ntpd, but it doesn't correct the error in system time. > > The only solution: use CRON to run ntpdate (this prevents ntpd from > running) efvery few minutes. This solution is much less than desirable, > as I won;t this box to run kerberos. > > Is there some solution to this problem? Nothing other than disabling SMP.. FWIW, it only happens on 2100s. Those machines are evil. Its been a while since I've played w/it. What does this say: /usr/bin/time sleep 10 Also, how many CPUs do you have? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 14:26:42 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A88F137B401 for ; Mon, 11 Nov 2002 14:26:40 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7427E43E3B for ; Mon, 11 Nov 2002 14:26:39 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA04543; Mon, 11 Nov 2002 17:26:39 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gABMQ8L48370; Mon, 11 Nov 2002 17:26:08 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15824.11904.925794.589053@grasshopper.cs.duke.edu> Date: Mon, 11 Nov 2002 17:26:08 -0500 (EST) To: "Michael A. Mackey" Cc: freebsd-alpha@freebsd.org Subject: Re: Extreme time drift in SMP mode In-Reply-To: <1037053307.14529.24.camel@focaccia.> References: <1037050487.14529.17.camel@focaccia.> <15824.10302.110339.545856@grasshopper.cs.duke.edu> <1037053307.14529.24.camel@focaccia.> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Michael A. Mackey writes: > test timing results: > > bash$ /usr/bin/time sleep 10 > 10.01 real 0.00 user 0.00 sys > > bash$ time sleep 10 > real 0m10.017s > user 0m0.003s > sys 0m0.011s > > I have two 291 MHz cpus. > > Left on its own, the system loses time dramatically (about 10 minutes on > the half hour). And timing against a working clock (like your watch, or another computer?) Eg, how long did the sleep really take? 5 seconds? 20 seconds? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 14:37:31 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3877B37B401 for ; Mon, 11 Nov 2002 14:37:30 -0800 (PST) Received: from cs671050-228.houston.rr.com (cs671050-228.houston.rr.com [67.10.50.228]) by mx1.FreeBSD.org (Postfix) with SMTP id D394143E6E for ; Mon, 11 Nov 2002 14:37:27 -0800 (PST) (envelope-from dkalepi@prodigy.com) Received: from bigfoot.com (prodigy.com [111.161.13.133]) by hotmail.com (8.11.6/8.11.6) with ESMTP id 5252 for ; Mon, 11 Nov 2002 22:37:33 +0000 From: "srishworth" To: "" Subject: Bullet proof bulk email friendly hosting & cheap mass email campaigns. X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 Date: Mon, 11 Nov 2002 22:37:33 +0000 Message-ID: <25561077doskdCiuhhevg1ruj@mailexcite.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org We are the marketing specialists www.host4bulk.com that provide cheap bullet proof bulk email friendly hosting for your website ($400 for one month of bullet proof hosting) and cheap bulk email campaigns ($200 for 1 million emails sent) As you may already know, many web hosting companies have Terms of Service (TOS) or Acceptable Use Policies (AUP) against the delivery of emails advertising or promoting your web site. If your web site host receives complaints or discovers that your web site has been advertised in email broadcasts, they may disconnect your account and shut down your web site. Our mission is to solve your problem and provide you with bulk email friendly hosting. You don't have to worry about your website being closed again. Adult and gambling sites welcomed. No set up fee. You may advertise your website by using your own resources or using 3rd party's service. However we can do all the advertising for your business. You just sit, relax and see how your income grows constantly. We guarantee the lowest prices on the web for our web hosting and bulk email campaigns. We only ask $200 us dollars for 1 million emails sent with your ad. We don't use duplicate emails. Our email base is up to date and it is updated weekly. Our current email data base contains over 50.000.000 emails sorted by various parameters to meet your specific needs. No competitors may offer this price. The lowest price you can find on the net is well over $500 for 1 million Don't make the mistake of bulk emailing directly to your website without bulletproof web hosting. Your web host will close your account and shut your site down in no time! No matter how long you have been with them, how much you are paying them, or how beautiful your site is. There are companies charging thousands for bulletproof web hosting and they can't keep you up and running like we can. If you host with us, your site will NOT BE SHUT DOWN due to complaints! Bulk email campaign together with bullet proof hosting will bring your business to success. Just imagine how many people will learn about your business or product at a really low price. Bulk email is considered to be the most effective way to advertise on the net. It is hundreds times effective than banner, solo ad and other campaigns. Once people use our service they always come back for more. We can always provide websites that use bulk email campaigns with our new reliable way to accept credit cards on the net without the need to open merchant account. You can start accepting credit card payments in second. It is totally free. Visit our website at http://www.host4bulk.com for more information and to order your bulk email hosting or/and email campaign. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 11 15:28:33 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F05537B401 for ; Mon, 11 Nov 2002 15:28:32 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id A366843E4A for ; Mon, 11 Nov 2002 15:28:31 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id SAA07004; Mon, 11 Nov 2002 18:28:31 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gABNS1n48426; Mon, 11 Nov 2002 18:28:01 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15824.15617.29097.140638@grasshopper.cs.duke.edu> Date: Mon, 11 Nov 2002 18:28:01 -0500 (EST) To: "Michael A. Mackey" Cc: freebsd-alpha@freebsd.org Subject: Re: Extreme time drift in SMP mode In-Reply-To: <1037056691.26905.7.camel@focaccia.> References: <1037050487.14529.17.camel@focaccia.> <15824.10302.110339.545856@grasshopper.cs.duke.edu> <1037053307.14529.24.camel@focaccia.> <15824.11904.925794.589053@grasshopper.cs.duke.edu> <1037056691.26905.7.camel@focaccia.> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Michael A. Mackey writes: > It takes precisely twice as long (20 seconds) to run `sleep 10`. > > Why can't ntpd keep things in line? > Because its not desgined to fix a clock which is that broken -- it only increments a second or so at a time. Far too slow for your purposes. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Nov 12 3:17:42 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CC2337B494; Tue, 12 Nov 2002 03:17:26 -0800 (PST) Received: from mail4.caramail.com (mail4.caramail.com [213.193.13.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4EF043E75; Tue, 12 Nov 2002 03:17:25 -0800 (PST) (envelope-from kseseko@caramail.com) Received: from caramail.com (www14.caramail.com [213.193.13.24]) by mail4.caramail.com (Postfix) with SMTP id 2B88B154F1; Tue, 12 Nov 2002 11:41:38 +0100 (MET) From: kseseko seko To: kseseko@caramail.com Message-ID: <1037097359002000@caramail.com> X-Mailer: Caramail - www.caramail.com X-Originating-IP: [216.139.169.154] Mime-Version: 1.0 Subject: Greetings Date: Tue, 12 Nov 2002 11:35:59 GMT+1 Content-Type: multipart/mixed; boundary="=_NextPart_Caramail_0020001037097359_ID" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --=_NextPart_Caramail_0020001037097359_ID Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable From: Kuzo M. Seseko Alternative Email Address: suun4us@yahoo.com My name is Kuzo Mobutu Seseko, the daughter of the late President of Republic of Zaire, now living in exile in South Africa. The circumstances that led to my living in South Africa at the moment cannot be new to you , I know you must know the history of my family. However , during the days of my father=92s reign we were into solid minerals exploration and mining which was the soul base of our family business, mostly diamond and gold. But unfortunately, before my father passed on, he was on exile in Europe which made it impossible for us to organize our businesses especially mining before the political hostility which saw him out of office began. Last year a security company in our country wrote me informing me of a deposit made by my father in my name which is still with them. I intended leaving the deposit with them sequel to my return home so that I can fall on that to start up a business ,but unfortunately, the rebel hostilities at home which have refused to stop up till this moment has made me to think otherwise. Hence I am considering asking the security company to transfer the sum to an oversea country with a stable economy and favorable political condition, so that I can find an indigenous business man / investor in that country to work with in partnership and invest this money. I know your country is an advanced democracy with a more stable economy than that of African countries. Hence I would want us to seek how to invest this sum agreeing on a working percentage.However due to my living status here in South Africa I would want you to keep this offer confidential. Get back to me suggesting what we are to do, while I will furnish you with my contact telephone numbers and fax in South Africa and that of my lawyers. I wish you strength. K. Seseko. _________________________________________________________ Gagne une PS2 ! Envoie un SMS avec le code PS au 61166 (0,35€ Hors co=FBt du SMS) --=_NextPart_Caramail_0020001037097359_ID-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Nov 12 6:50: 4 2002 Delivered-To: freebsd-alpha@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA32937B401 for ; Tue, 12 Nov 2002 06:50:02 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02B9143E75 for ; Tue, 12 Nov 2002 06:50:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id gACEo1x3011596 for ; Tue, 12 Nov 2002 06:50:01 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.6/8.12.6/Submit) id gACEo1KJ011595; Tue, 12 Nov 2002 06:50:01 -0800 (PST) Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E477C37B401 for ; Tue, 12 Nov 2002 06:42:21 -0800 (PST) Received: from uplift.sunquest.com (uplift.hosp.misyshealthcare.com [149.138.10.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EF7243E77 for ; Tue, 12 Nov 2002 06:42:21 -0800 (PST) (envelope-from terry@uplift.sunquest.com) Received: from uplift.sunquest.com (localhost [127.0.0.1]) by uplift.sunquest.com (8.12.6/8.12.6) with ESMTP id gAC7gdlt060879; Tue, 12 Nov 2002 07:42:39 GMT (envelope-from terry@uplift.sunquest.com) Received: (from terry@localhost) by uplift.sunquest.com (8.12.6/8.12.6/Submit) id gAC7gdAP060878; Tue, 12 Nov 2002 07:42:39 GMT Message-Id: <200211120742.gAC7gdAP060878@uplift.sunquest.com> Date: Tue, 12 Nov 2002 07:42:39 GMT From: "Terry R. Friedrichsen" Reply-To: "Terry R. Friedrichsen" To: FreeBSD-gnats-submit@FreeBSD.org Cc: terry@uplift.sunquest.com X-Send-Pr-Version: 3.113 Subject: alpha/45240: pstat -f column headings misaligned on Alpha Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 45240 >Category: alpha >Synopsis: pstat -f column headings misaligned on Alpha >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-alpha >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Nov 12 06:50:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Terry R. Friedrichsen >Release: FreeBSD 4.7-RELEASE alpha >Organization: TRF Astro Imaging >Environment: System: FreeBSD uplift.sunquest.com 4.7-RELEASE FreeBSD 4.7-RELEASE #0: Wed Oct 9 23:00:51 GMT 2002 root@sema.baldwin.cx:/usr/obj/usr/src/sys/GENERIC alpha >Description: The column headings for pstat -f are misaligned; they should be moved out to the right. This is due to the fact that the "LOC" and "DATA" fields are 16 characters long, instead of 8, for the 64-bit Alpha architecture. >How-To-Repeat: Observe the first 3 lines of output from "pstat -f". >Fix: For the Alpha platform, add additional spacing around the "LOC" and "DATA" column headings. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Nov 12 7:48:22 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E90F037B401 for ; Tue, 12 Nov 2002 07:48:21 -0800 (PST) Received: from mail.speakeasy.net (mail16.speakeasy.net [216.254.0.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79F4143E3B for ; Tue, 12 Nov 2002 07:48:21 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 2077 invoked from network); 12 Nov 2002 15:48:23 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail16.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 12 Nov 2002 15:48:23 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.6/8.12.6) with ESMTP id gACFmE2D004666; Tue, 12 Nov 2002 10:48:15 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <15824.15617.29097.140638@grasshopper.cs.duke.edu> Date: Tue, 12 Nov 2002 10:48:16 -0500 (EST) From: John Baldwin To: Andrew Gallatin Subject: Re: Extreme time drift in SMP mode Cc: freebsd-alpha@freebsd.org, "Michael A. Mackey" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 11-Nov-2002 Andrew Gallatin wrote: > > Michael A. Mackey writes: > > It takes precisely twice as long (20 seconds) to run `sleep 10`. > > > > Why can't ntpd keep things in line? > > > > Because its not desgined to fix a clock which is that broken -- it > only increments a second or so at a time. Far too slow for your > purposes. So the clock is running at half-speed now? Hmm, the 2100[A] are Tincup, not Turbolaser, right? So it should be using the i8254 for its timecounter. Maybe the 8254 timecounter isn't setup right on the 2100a? -- 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 Nov 12 8: 3: 9 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55CCF37B401; Tue, 12 Nov 2002 08:03:08 -0800 (PST) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8560843E3B; Tue, 12 Nov 2002 08:03:06 -0800 (PST) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.6/8.12.6) with ESMTP id gACG30bY001754; Tue, 12 Nov 2002 17:03:01 +0100 (CET) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.6/8.12.6/Submit) id gACG30Id001753; Tue, 12 Nov 2002 17:03:00 +0100 (CET) Date: Tue, 12 Nov 2002 17:03:00 +0100 From: Wilko Bulte To: John Baldwin Cc: Andrew Gallatin , freebsd-alpha@FreeBSD.ORG, "Michael A. Mackey" Subject: Re: Extreme time drift in SMP mode Message-ID: <20021112170300.A1738@freebie.xs4all.nl> References: <15824.15617.29097.140638@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.ORG on Tue, Nov 12, 2002 at 10:48:16AM -0500 X-OS: FreeBSD 4.7-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Nov 12, 2002 at 10:48:16AM -0500, John Baldwin wrote: > > On 11-Nov-2002 Andrew Gallatin wrote: > > > > Michael A. Mackey writes: > > > It takes precisely twice as long (20 seconds) to run `sleep 10`. > > > > > > Why can't ntpd keep things in line? > > > > > > > Because its not desgined to fix a clock which is that broken -- it > > only increments a second or so at a time. Far too slow for your > > purposes. > > So the clock is running at half-speed now? Hmm, the 2100[A] are > Tincup, not Turbolaser, right? So it should be using the i8254 for Sable. Tincup is the AS1200. Tlaser is AS8[24]00 > its timecounter. Maybe the 8254 timecounter isn't setup right on > the 2100a? > -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Nov 12 8: 7: 1 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45E2E37B401 for ; Tue, 12 Nov 2002 08:07:00 -0800 (PST) Received: from aromo.spock.cl (aromo.spock.cl [200.27.125.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0166443E77 for ; Tue, 12 Nov 2002 08:06:59 -0800 (PST) (envelope-from roberto@spock.cl) Received: from spock.cl (multia.spock.cl [200.27.125.107]) by aromo.spock.cl (8.11.1/8.9.3) with ESMTP id gACG7vj13146 for ; Tue, 12 Nov 2002 13:07:57 -0300 (CLST) Message-ID: <3DD12716.2080506@spock.cl> Date: Tue, 12 Nov 2002 13:06:46 -0300 From: Roberto de Iriarte User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-alpha@FreeBSD.ORG Subject: Re: Extreme time drift in SMP mode References: <15824.15617.29097.140638@grasshopper.cs.duke.edu> <20021112170300.A1738@freebie.xs4all.nl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Wilko Bulte wrote: >On Tue, Nov 12, 2002 at 10:48:16AM -0500, John Baldwin wrote: > > >>On 11-Nov-2002 Andrew Gallatin wrote: >> >> >>>Michael A. Mackey writes: >>> > It takes precisely twice as long (20 seconds) to run `sleep 10`. >>> > > Why can't ntpd keep things in line? >>> > Because its not desgined to fix a clock which is that broken -- it >>>only increments a second or so at a time. Far too slow for your >>>purposes. >>> >>> >>So the clock is running at half-speed now? Hmm, the 2100[A] are >>Tincup, not Turbolaser, right? So it should be using the i8254 for >> >> > >Sable. Tincup is the AS1200. Tlaser is AS8[24]00 > > 2100 is Sable, the rarer 2100A is called Lynx > > >>its timecounter. Maybe the 8254 timecounter isn't setup right on >>the 2100a? >> >> >> > > > Regards, Roberto To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Nov 12 8:21:58 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2521637B401; Tue, 12 Nov 2002 08:21:57 -0800 (PST) Received: from pisello.ecn.uiowa.edu (pisello.ecn.uiowa.edu [128.255.23.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2DBE43E75; Tue, 12 Nov 2002 08:21:55 -0800 (PST) (envelope-from mackey@engineering.uiowa.edu) Received: from engineering.uiowa.edu (localhost.localdomain [127.0.0.1]) by pisello.ecn.uiowa.edu (8.11.6/8.11.6) with ESMTP id gACGLsE01411; Tue, 12 Nov 2002 10:21:54 -0600 Message-ID: <3DD12AA2.8D84B3E2@engineering.uiowa.edu> Date: Tue, 12 Nov 2002 10:21:54 -0600 From: "Dr. Michael Mackey" Organization: University of Iowa X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.19 i686) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin , freebsd-alpha@FreeBSD.org Subject: Re: Extreme time drift in SMP mode References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org You're right, the clock on the Lynx (2100a) is an 8254: (from the output of dmesg) FreeBSD 5.0-CURRENT #0: Mon Nov 11 15:31:50 CST 2002 mackey@home.:/usr/src/sys/alpha/compile/HOME Preloaded elf kernel "/boot/kernel/kernel" at 0xfffffc00006c2000. DEC AlphaServer 2100A AlphaServer 2100A 5/300, 291MHz 8192 byte page size, 2 processors. CPU: EV5 (21164) major=5 minor=5 OSF PAL rev: 0x4000100020116 real memory = 199155712 (189 MB) avail memory = 187490304 (178 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs --- snip --- Timecounters tick every 0.976 msec Timecounter "i8254" frequency 1193182 Hz --- snip --- John Baldwin wrote: > > On 11-Nov-2002 Andrew Gallatin wrote: > > > > Michael A. Mackey writes: > > > It takes precisely twice as long (20 seconds) to run `sleep 10`. > > > > > > Why can't ntpd keep things in line? > > > > > > > Because its not desgined to fix a clock which is that broken -- it > > only increments a second or so at a time. Far too slow for your > > purposes. > > So the clock is running at half-speed now? Hmm, the 2100[A] are > Tincup, not Turbolaser, right? So it should be using the i8254 for > its timecounter. Maybe the 8254 timecounter isn't setup right on > the 2100a? > > -- > > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ -- Prof. Michael A. Mackey (michael-mackey@uiowa.edu) Biomedical Engineering / Radiology University of Iowa, Iowa City, Iowa Voice: 319-335-6058 Fax: 319-335-5631 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Nov 12 8:32: 4 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE10237B401; Tue, 12 Nov 2002 08:32:01 -0800 (PST) Received: from aromo.spock.cl (aromo.spock.cl [200.27.125.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68E1D43E75; Tue, 12 Nov 2002 08:32:00 -0800 (PST) (envelope-from roberto@spock.cl) Received: from spock.cl (multia.spock.cl [200.27.125.107]) by aromo.spock.cl (8.11.1/8.9.3) with ESMTP id gACGWjj13425; Tue, 12 Nov 2002 13:32:45 -0300 (CLST) Message-ID: <3DD12CE7.10103@spock.cl> Date: Tue, 12 Nov 2002 13:31:35 -0300 From: Roberto de Iriarte User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Dr. Michael Mackey" Cc: John Baldwin , freebsd-alpha@FreeBSD.ORG Subject: Re: Extreme time drift in SMP mode References: <3DD12AA2.8D84B3E2@engineering.uiowa.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Dr. Michael Mackey wrote: >You're right, the clock on the Lynx (2100a) is an 8254: > >(from the output of dmesg) >FreeBSD 5.0-CURRENT #0: Mon Nov 11 15:31:50 CST 2002 > mackey@home.:/usr/src/sys/alpha/compile/HOME >Preloaded elf kernel "/boot/kernel/kernel" at 0xfffffc00006c2000. >DEC AlphaServer 2100A >AlphaServer 2100A 5/300, 291MHz >8192 byte page size, 2 processors. >CPU: EV5 (21164) major=5 minor=5 >OSF PAL rev: 0x4000100020116 >real memory = 199155712 (189 MB) >avail memory = 187490304 (178 MB) >FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >--- snip --- >Timecounters tick every 0.976 msec >Timecounter "i8254" frequency 1193182 Hz >--- snip --- > > >John Baldwin wrote: > > >>On 11-Nov-2002 Andrew Gallatin wrote: >> >> >>>Michael A. Mackey writes: >>> > It takes precisely twice as long (20 seconds) to run `sleep 10`. >>> > >>> > Why can't ntpd keep things in line? >>> > >>> >>>Because its not desgined to fix a clock which is that broken -- it >>>only increments a second or so at a time. Far too slow for your >>>purposes. >>> >>> >>So the clock is running at half-speed now? Hmm, the 2100[A] are >>Tincup, not Turbolaser, right? So it should be using the i8254 for >>its timecounter. Maybe the 8254 timecounter isn't setup right on >>the 2100a? >> >>-- >> >>John Baldwin <>< http://www.FreeBSD.org/~jhb/ >>"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ >> >> > > > Hmmm. my dmesg reads differently BTW, my system has only one CPU, and the clock has never drifted. ------------------------------------------------------------------------------------------------------------------------ FreeBSD 4.6.2-RELEASE #0: Thu Aug 22 20:40:14 GMT 2002 root@sema.baldwin.cx:/usr/src/sys/compile/GENERIC DEC AlphaServer 2100A AlphaServer 2100A 5/375, 374MHz 8192 byte page size, 1 processor. CPU: EV56 (21164A) major=7 minor=1 extensions=0x1 OSF PAL rev: 0x4000100020116 real memory = 1071570944 (1046456K bytes) avail memory = 1036902400 (1012600K bytes) Preloaded elf kernel "kernel" at 0xfffffc00007c6000. md0: Malloc disk t20: using interrupt type 1 on pci bus 0 pci0: on pcib0 isab0: at device 2.0 on pci0 isa0: on isab0 pcib1: at device 3.0 on pci0 pci2: on pcib1 sym0: <810a> port 0x5000-0x50ff mem 0x81040000-0x810400ff irq 28 at device 1.0 on pci2 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking dc0: port 0x5400-0x547f mem 0x81040100-0x8104017f irq 48 at device 6.0 on pci2 dc0: Ethernet address: 00:00:f8:1f:f6:2a miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto mlx0: port 0x10000-0x1007f irq 32 at device 6.0 on pci0 mlx0: DAC960P/PD, 1 channel, firmware 2.73-0-00, 16MB RAM mlxd0: on mlx0 mlxd0: 12042MB (24662016 sectors) RAID 5 (online) pci0: (vendor=0xff00, dev=0xff00) at 12.0 irq 1 pci0: (vendor=0x0000, dev=0x0000) at 12.4 pci0: (vendor=0xff00, dev=0xff00) at 13.0 irq 1 pci0: (vendor=0x0000, dev=0x0000) at 13.4 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 mcclock0: at port 0x70-0x71 on isa0 sio0: configured irq 4 not in bitmap of probed irqs 0x1 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A, console sio1: reserved for low-level i/o ppc0: at port 0x3bc-0x3c3 irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Polled port ppi0: on ppbus0 Timecounter "alpha" frequency 374661324 Hz Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/mlxd0a cd0 at sym0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.166MB/s transfers (4.166MHz, offset 8) cd0: cd present [384512 x 512 byte records] ------------------------------------------------------------------------------------------------------------------------------- As a matter of fact, there is no mention of an i8254 whatsoever. Should i source another CPU and try out 5.0 Current ? Regards, Roberto To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Nov 12 8:48:17 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8CF637B401; Tue, 12 Nov 2002 08:48:16 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id E716C43E3B; Tue, 12 Nov 2002 08:48:06 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA16044; Tue, 12 Nov 2002 11:47:50 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gACGlGG49667; Tue, 12 Nov 2002 11:47:16 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15825.12436.199011.915697@grasshopper.cs.duke.edu> Date: Tue, 12 Nov 2002 11:47:16 -0500 (EST) To: Roberto de Iriarte Cc: "Dr. Michael Mackey" , John Baldwin , freebsd-alpha@FreeBSD.ORG Subject: Re: Extreme time drift in SMP mode In-Reply-To: <3DD12CE7.10103@spock.cl> References: <3DD12AA2.8D84B3E2@engineering.uiowa.edu> <3DD12CE7.10103@spock.cl> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Roberto de Iriarte writes: > Hmmm. my dmesg reads differently > BTW, my system has only one CPU, and the clock has never drifted. > That's the thing. The 2100 is unlike all other alphas, and handles clocks differently in MP mode. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Nov 12 9:14:31 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C077D37B401; Tue, 12 Nov 2002 09:14:29 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id E169A43E4A; Tue, 12 Nov 2002 09:14:28 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id MAA17730; Tue, 12 Nov 2002 12:14:28 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gACHDwB49691; Tue, 12 Nov 2002 12:13:58 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15825.14038.294916.650698@grasshopper.cs.duke.edu> Date: Tue, 12 Nov 2002 12:13:58 -0500 (EST) To: "Dr. Michael Mackey" Cc: John Baldwin , freebsd-alpha@FreeBSD.ORG Subject: Re: Extreme time drift in SMP mode In-Reply-To: <15825.12436.199011.915697@grasshopper.cs.duke.edu> References: <3DD12AA2.8D84B3E2@engineering.uiowa.edu> <3DD12CE7.10103@spock.cl> <15825.12436.199011.915697@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Andrew Gallatin writes: > > Roberto de Iriarte writes: > > > Hmmm. my dmesg reads differently > > BTW, my system has only one CPU, and the clock has never drifted. > > > > That's the thing. The 2100 is unlike all other alphas, and handles > clocks differently in MP mode. To elaborate on the above, I think most MP alphas tie the clock interrupt to the boot cpu, and it ticks at hz. I think the 2100 round-robins the clock interrupt to all running cpus, therefore the boot cpu only ticks at hz/mp_ncpus. Currently, we pay attention only to the boot CPU. From alpha_clock_interrupt() in sys/alpha/alpha/interrupt.c <...> critical_enter(); #ifdef SMP /* * Only one processor drives the actual timer. */ if (PCPU_GET(cpuid) == boot_cpu_id) { #endif (*platform.clockintr)(framep); /* divide hz (1024) by 8 to get stathz (128) */ if ((++schedclk2 & 0x7) == 0) statclock((struct clockframe *)framep); #ifdef SMP } else { mtx_lock_spin(&sched_lock); hardclock_process(curthread, TRAPF_USERMODE(framep)); if ((schedclk2 & 0x7) == 0) statclock_process(curkse, TRAPF_PC(framep), TRAPF_USERMODE(framep)); mtx_unlock_spin(&sched_lock); } #endif critical_exit(); <...> Given that I know zippo about how timekeeping works, I don't know what a good fix might be. If I had a machine in front of me, I'd be tempted to try dividing the a frequency by 2 in sys/alpha/alpha/clock.c, but I'm not sure which one, or if it can be adjusted as additional processors are found and started. (which would be slightly less wrong..). Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Nov 12 11:57:42 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6474837B401 for ; Tue, 12 Nov 2002 11:57:40 -0800 (PST) Received: from mail.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C36043E88 for ; Tue, 12 Nov 2002 11:57:38 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 8969 invoked from network); 12 Nov 2002 19:57:44 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 12 Nov 2002 19:57:44 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.6/8.12.6) with ESMTP id gACJva2D005393; Tue, 12 Nov 2002 14:57:36 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3DD12AA2.8D84B3E2@engineering.uiowa.edu> Date: Tue, 12 Nov 2002 14:57:37 -0500 (EST) From: John Baldwin To: "Dr. Michael Mackey" Subject: Re: Extreme time drift in SMP mode Cc: freebsd-alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 12-Nov-2002 Dr. Michael Mackey wrote: > You're right, the clock on the Lynx (2100a) is an 8254: > > (from the output of dmesg) > FreeBSD 5.0-CURRENT #0: Mon Nov 11 15:31:50 CST 2002 > mackey@home.:/usr/src/sys/alpha/compile/HOME > Preloaded elf kernel "/boot/kernel/kernel" at 0xfffffc00006c2000. > DEC AlphaServer 2100A > AlphaServer 2100A 5/300, 291MHz > 8192 byte page size, 2 processors. > CPU: EV5 (21164) major=5 minor=5 > OSF PAL rev: 0x4000100020116 > real memory = 199155712 (189 MB) > avail memory = 187490304 (178 MB) > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > --- snip --- > Timecounters tick every 0.976 msec > Timecounter "i8254" frequency 1193182 Hz > --- snip --- Hmm, what does it look like with a UP kernel? It would be using the "alpha" timecounter right? Also, how often do timecounters tick with the UP kernel? It's usually every 10 msec on all the systems I have that are running current. > John Baldwin wrote: >> >> On 11-Nov-2002 Andrew Gallatin wrote: >> > >> > Michael A. Mackey writes: >> > > It takes precisely twice as long (20 seconds) to run `sleep 10`. >> > > >> > > Why can't ntpd keep things in line? >> > > >> > >> > Because its not desgined to fix a clock which is that broken -- it >> > only increments a second or so at a time. Far too slow for your >> > purposes. >> >> So the clock is running at half-speed now? Hmm, the 2100[A] are >> Tincup, not Turbolaser, right? So it should be using the i8254 for >> its timecounter. Maybe the 8254 timecounter isn't setup right on >> the 2100a? >> >> -- >> >> John Baldwin <>< http://www.FreeBSD.org/~jhb/ >> "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > > -- > Prof. Michael A. Mackey (michael-mackey@uiowa.edu) > Biomedical Engineering / Radiology > University of Iowa, Iowa City, Iowa > Voice: 319-335-6058 Fax: 319-335-5631 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message -- 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 Nov 12 13:15:29 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D35B37B401; Tue, 12 Nov 2002 13:15:27 -0800 (PST) Received: from server07.icaen.uiowa.edu (server07.icaen.uiowa.edu [128.255.17.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46D9943E6E; Tue, 12 Nov 2002 13:15:26 -0800 (PST) (envelope-from michael-mackey@uiowa.edu) Received: from server11.icaen.uiowa.edu (server11.icaen.uiowa.edu [128.255.17.51]) by server07.icaen.uiowa.edu (8.9.3/8.9.3) with ESMTP id PAA03220 sent by ; Tue, 12 Nov 2002 15:15:35 -0600 (CST) Received: from focaccia. (12-217-236-86.client.mchsi.com [12.217.236.86]) by server11.icaen.uiowa.edu (8.9.3/smtp-service-1.6) with ESMTP id PAA26334; sent by ; Tue, 12 Nov 2002 15:15:17 -0600 (CST) Subject: Re: Extreme time drift in SMP mode From: "Michael A. Mackey" To: jhb@freebsd.org Cc: freebsd-alpha@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 12 Nov 2002 15:15:14 -0600 Message-Id: <1037135718.27957.17.camel@focaccia.> Mime-Version: 1.0 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Well, I guess I got really lucky.... I seem to have fixed the time drift problem, based on a hunch. Drew, after what you said about the boot processor alone driving the timing, I decided to allow both processors to drive the timer. So, I changed the code in the function 'alpha_clock_interrupt ()' in /usr/src/sys/alpha/alpha/interrupt.c (actually I only added an #undef SMP statement on line 467 and redefined it before the 'critical_exit()' call). And now, the SMP system keeps proper track of the time. In a couple of days, I have two more processors arriving. Then I can really test if this fix works. Thanks for your help - and I hope others can verify my results. On Tue, 2002-11-12 at 11:13, Andrew Gallatin wrote: > > Andrew Gallatin writes: > > > > Roberto de Iriarte writes: > > > > > Hmmm. my dmesg reads differently > > > BTW, my system has only one CPU, and the clock has never drifted. > > > > > > > That's the thing. The 2100 is unlike all other alphas, and handles > > clocks differently in MP mode. > > To elaborate on the above, I think most MP alphas tie the clock > interrupt to the boot cpu, and it ticks at hz. > > I think the 2100 round-robins the clock interrupt to all running cpus, > therefore the boot cpu only ticks at hz/mp_ncpus. > > Currently, we pay attention only to the boot CPU. From > alpha_clock_interrupt() in sys/alpha/alpha/interrupt.c > <...> > critical_enter(); > #ifdef SMP > /* > * Only one processor drives the actual timer. > */ > if (PCPU_GET(cpuid) == boot_cpu_id) { > #endif > (*platform.clockintr)(framep); > /* divide hz (1024) by 8 to get stathz (128) */ > if ((++schedclk2 & 0x7) == 0) > statclock((struct clockframe *)framep); > #ifdef SMP > } else { > mtx_lock_spin(&sched_lock); > hardclock_process(curthread, TRAPF_USERMODE(framep)); > if ((schedclk2 & 0x7) == 0) > statclock_process(curkse, TRAPF_PC(framep), > TRAPF_USERMODE(framep)); > mtx_unlock_spin(&sched_lock); > } > #endif > critical_exit(); > <...> > > > Given that I know zippo about how timekeeping works, I don't know > what a good fix might be. If I had a machine in front of me, > I'd be tempted to try dividing the a frequency by 2 in sys/alpha/alpha/clock.c, > but I'm not sure which one, or if it can be adjusted as additional processors > are found and started. (which would be slightly less wrong..). > > Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Nov 12 13:45: 2 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1758137B401 for ; Tue, 12 Nov 2002 13:45:00 -0800 (PST) Received: from mail.speakeasy.net (mail16.speakeasy.net [216.254.0.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F7EB43E91 for ; Tue, 12 Nov 2002 13:44:59 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 29979 invoked from network); 12 Nov 2002 21:45:07 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail16.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 12 Nov 2002 21:45:07 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.6/8.12.6) with ESMTP id gACLiv2D005734; Tue, 12 Nov 2002 16:44:57 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <1037135718.27957.17.camel@focaccia.> Date: Tue, 12 Nov 2002 16:44:59 -0500 (EST) From: John Baldwin To: "Michael A. Mackey" Subject: Re: Extreme time drift in SMP mode Cc: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 12-Nov-2002 Michael A. Mackey wrote: > Well, I guess I got really lucky.... > > I seem to have fixed the time drift problem, based on a hunch. > > Drew, after what you said about the boot processor alone driving the > timing, I decided to allow both processors to drive the timer. So, I > changed the code in the function 'alpha_clock_interrupt ()' in > /usr/src/sys/alpha/alpha/interrupt.c (actually I only added an #undef > SMP statement on line 467 and redefined it before the 'critical_exit()' > call). > > And now, the SMP system keeps proper track of the time. > > In a couple of days, I have two more processors arriving. Then I can > really test if this fix works. > > Thanks for your help - and I hope others can verify my results. Well, that's not really an ideal fix for the problem. :( Adjusting the timer frequency in the SMP case instead would be preferred. > On Tue, 2002-11-12 at 11:13, Andrew Gallatin wrote: >> >> Andrew Gallatin writes: >> > >> > Roberto de Iriarte writes: >> > >> > > Hmmm. my dmesg reads differently >> > > BTW, my system has only one CPU, and the clock has never > drifted. >> > > >> > >> > That's the thing. The 2100 is unlike all other alphas, and handles >> > clocks differently in MP mode. >> >> To elaborate on the above, I think most MP alphas tie the clock >> interrupt to the boot cpu, and it ticks at hz. >> >> I think the 2100 round-robins the clock interrupt to all running cpus, >> therefore the boot cpu only ticks at hz/mp_ncpus. >> >> Currently, we pay attention only to the boot CPU. From >> alpha_clock_interrupt() in sys/alpha/alpha/interrupt.c >> <...> >> critical_enter(); >> #ifdef SMP >> /* >> * Only one processor drives the actual timer. >> */ >> if (PCPU_GET(cpuid) == boot_cpu_id) { >> #endif >> (*platform.clockintr)(framep); >> /* divide hz (1024) by 8 to get stathz (128) > */ >> if ((++schedclk2 & 0x7) == 0) >> statclock((struct clockframe > *)framep); >> #ifdef SMP >> } else { >> mtx_lock_spin(&sched_lock); >> hardclock_process(curthread, > TRAPF_USERMODE(framep)); >> if ((schedclk2 & 0x7) == 0) >> statclock_process(curkse, > TRAPF_PC(framep), >> TRAPF_USERMODE(framep)); >> mtx_unlock_spin(&sched_lock); >> } >> #endif >> critical_exit(); >> <...> >> >> >> Given that I know zippo about how timekeeping works, I don't know >> what a good fix might be. If I had a machine in front of me, >> I'd be tempted to try dividing the a frequency by 2 in > sys/alpha/alpha/clock.c, >> but I'm not sure which one, or if it can be adjusted as additional > processors >> are found and started. (which would be slightly less wrong..). >> >> Drew > > > -- 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 Nov 12 14:43:35 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F6BA37B401; Tue, 12 Nov 2002 14:43:34 -0800 (PST) Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F8CC43E75; Tue, 12 Nov 2002 14:43:34 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0050.cvx22-bradley.dialup.earthlink.net ([209.179.198.50] helo=mindspring.com) by harrier.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18BjYu-0002SS-00; Tue, 12 Nov 2002 14:31:12 -0800 Message-ID: <3DD180E3.80D3C4F6@mindspring.com> Date: Tue, 12 Nov 2002 14:29:55 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: "Michael A. Mackey" , freebsd-alpha@freebsd.org Subject: Re: Extreme time drift in SMP mode References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org John Baldwin wrote: > On 12-Nov-2002 Michael A. Mackey wrote: > > Well, I guess I got really lucky.... > > > > I seem to have fixed the time drift problem, based on a hunch. > > > > Drew, after what you said about the boot processor alone driving the > > timing, I decided to allow both processors to drive the timer. So, I > > changed the code in the function 'alpha_clock_interrupt ()' in > > /usr/src/sys/alpha/alpha/interrupt.c (actually I only added an #undef > > SMP statement on line 467 and redefined it before the 'critical_exit()' > > call). > > > > And now, the SMP system keeps proper track of the time. > > > > In a couple of days, I have two more processors arriving. Then I can > > really test if this fix works. > > > > Thanks for your help - and I hope others can verify my results. > > Well, that's not really an ideal fix for the problem. :( Adjusting > the timer frequency in the SMP case instead would be preferred. What if that's just a statistical fix, having to do with interrupt delivery, rather than a real fix? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Nov 12 15: 8:53 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A87B37B401 for ; Tue, 12 Nov 2002 15:08:52 -0800 (PST) Received: from server07.icaen.uiowa.edu (server07.icaen.uiowa.edu [128.255.17.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0FD443E4A for ; Tue, 12 Nov 2002 15:08:49 -0800 (PST) (envelope-from michael-mackey@uiowa.edu) Received: from server11.icaen.uiowa.edu (server11.icaen.uiowa.edu [128.255.17.51]) by server07.icaen.uiowa.edu (8.9.3/8.9.3) with ESMTP id RAA06765 sent by ; Tue, 12 Nov 2002 17:08:59 -0600 (CST) Received: from focaccia. (12-217-236-86.client.mchsi.com [12.217.236.86]) by server11.icaen.uiowa.edu (8.9.3/smtp-service-1.6) with ESMTP id RAA05983; sent by ; Tue, 12 Nov 2002 17:08:40 -0600 (CST) Subject: Re: Extreme time drift in SMP mode From: "Michael A. Mackey" To: Terry Lambert Cc: freebsd-alpha@freebsd.org In-Reply-To: <3DD180E3.80D3C4F6@mindspring.com> References: <3DD180E3.80D3C4F6@mindspring.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 12 Nov 2002 17:08:38 -0600 Message-Id: <1037142521.27992.41.camel@focaccia.> Mime-Version: 1.0 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I guess I don't understand the problem. It seemed to me that the problem was that not all the interrupts were being delivered because the Lynx architecture expects each processor to generate interrupts. Before the fix, the system lost time by an amount which was equivalent to throwing away half of the interrupts. After my modification, each processor is allowed to generate clock interrupts, and the system receives the complete set of interrupts, yielding the result that the system keeps time correctly. I'm sure that this is a naive picture of what's going on (and I'm not a kernel developer), but it works. I realize that it is probably specific to the Lynx architecture, and I of course would be happy for a 'correct' way to allow this old box to happily crank along solving PDE's. Anyway, I sure am glad to have such high quality software to run on this box. Keep up the great work FreeBSD-Alpha! On Tue, 2002-11-12 at 16:29, Terry Lambert wrote: > John Baldwin wrote: > > On 12-Nov-2002 Michael A. Mackey wrote: > > > Well, I guess I got really lucky.... > > > > > > I seem to have fixed the time drift problem, based on a hunch. > > > > > > Drew, after what you said about the boot processor alone driving the > > > timing, I decided to allow both processors to drive the timer. So, I > > > changed the code in the function 'alpha_clock_interrupt ()' in > > > /usr/src/sys/alpha/alpha/interrupt.c (actually I only added an #undef > > > SMP statement on line 467 and redefined it before the 'critical_exit()' > > > call). > > > > > > And now, the SMP system keeps proper track of the time. > > > > > > In a couple of days, I have two more processors arriving. Then I can > > > really test if this fix works. > > > > > > Thanks for your help - and I hope others can verify my results. > > > > Well, that's not really an ideal fix for the problem. :( Adjusting > > the timer frequency in the SMP case instead would be preferred. > > What if that's just a statistical fix, having to do with interrupt > delivery, rather than a real fix? > > -- Terry > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Nov 12 15:50:57 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FF6537B401 for ; Tue, 12 Nov 2002 15:50:56 -0800 (PST) Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id F021543E3B for ; Tue, 12 Nov 2002 15:50:55 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0050.cvx22-bradley.dialup.earthlink.net ([209.179.198.50] helo=mindspring.com) by gull.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18Bko1-00076z-00; Tue, 12 Nov 2002 15:50:53 -0800 Message-ID: <3DD19384.5355662E@mindspring.com> Date: Tue, 12 Nov 2002 15:49:24 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Michael A. Mackey" Cc: freebsd-alpha@freebsd.org Subject: Re: Extreme time drift in SMP mode References: <3DD180E3.80D3C4F6@mindspring.com> <1037142521.27992.41.camel@focaccia.> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org "Michael A. Mackey" wrote: > I guess I don't understand the problem. Adjusting the timer frequency, as John suggested, would give the appearance of a fix, but would not really fix the problem: if you do that, you are assuming that an exactly equal number of interrupts per interval come from each processor. This is true statistically, but not overall. > It seemed to me that the problem was that not all the interrupts were > being delivered because the Lynx architecture expects each processor to > generate interrupts. Before the fix, the system lost time by an amount > which was equivalent to throwing away half of the interrupts. After my > modification, each processor is allowed to generate clock interrupts, > and the system receives the complete set of interrupts, yielding the > result that the system keeps time correctly. Yes. IMO, your modification is the correct one; John's suggested change would be statistical in nature, at best. The disadvantage of your approach is that it implies that the clock interrupt handling code needs to be reentrant, which it might not be, since there is an implicit expectation of only a single hardware clock interrupt source. > I'm sure that this is a naive picture of what's going on (and I'm not a > kernel developer), but it works. I realize that it is probably specific > to the Lynx architecture, and I of course would be happy for a 'correct' > way to allow this old box to happily crank along solving PDE's. As I implied in my previous posting, I think your fix is the correct one, and John's would be a statistical fix, at best, which I would not trust. An interesting question would be whether or not you can have different clock rates for different CPU's on the box, and what happens in that case (whether the answer is right or not). As the clock is calibrated on a single CPU at startup, it's a problem of interrrupt routing being symmetric vs. generation being symmetric; if it's the former, then you're OK, and if it's the latter, then John's fix is better, even if it is only statistical. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Nov 12 17:41:35 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 130E837B4CA for ; Tue, 12 Nov 2002 17:41:32 -0800 (PST) Received: from server07.icaen.uiowa.edu (server07.icaen.uiowa.edu [128.255.17.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BE9C43E42 for ; Tue, 12 Nov 2002 17:41:31 -0800 (PST) (envelope-from michael-mackey@uiowa.edu) Received: from server11.icaen.uiowa.edu (server11.icaen.uiowa.edu [128.255.17.51]) by server07.icaen.uiowa.edu (8.9.3/8.9.3) with ESMTP id TAA09908 for sent by ; Tue, 12 Nov 2002 19:41:42 -0600 (CST) Received: from focaccia. (12-217-236-86.client.mchsi.com [12.217.236.86]) by server11.icaen.uiowa.edu (8.9.3/smtp-service-1.6) with ESMTP id TAA14640 for ; sent by ; Tue, 12 Nov 2002 19:41:21 -0600 (CST) Subject: RE: Extreme time drift in SMP mode From: "Michael A. Mackey" To: freebsd-alpha@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 12 Nov 2002 19:41:18 -0600 Message-Id: <1037151683.28038.117.camel@focaccia.> Mime-Version: 1.0 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Well, I still don't think I understand. I just built a non-SMP version of the modified kernel (with only the single change previously described) and rebooted. Now, the system loses time (about 5 min every 10 minutes) and sleep 10 takes 20 seconds on an unloaded system. So, the dreaded slow-down is back, this time for a UP system. I will be receiving 2 more processors in a day or two, and then we can see if the two-processor case reported earlier can be generalized to the four-processor one. Nevertheless, I really don't see why the UP system loses time. On Tue, 2002-11-12 at 17:49, Terry Lambert wrote: > "Michael A. Mackey" wrote: > > I guess I don't understand the problem. > > Adjusting the timer frequency, as John suggested, would give the > appearance of a fix, but would not really fix the problem: if > you do that, you are assuming that an exactly equal number of > interrupts per interval come from each processor. This is true > statistically, but not overall. > > > > It seemed to me that the problem was that not all the interrupts were > > being delivered because the Lynx architecture expects each processor to > > generate interrupts. Before the fix, the system lost time by an amount > > which was equivalent to throwing away half of the interrupts. After my > > modification, each processor is allowed to generate clock interrupts, > > and the system receives the complete set of interrupts, yielding the > > result that the system keeps time correctly. > > Yes. IMO, your modification is the correct one; John's suggested > change would be statistical in nature, at best. The disadvantage > of your approach is that it implies that the clock interrupt > handling code needs to be reentrant, which it might not be, since > there is an implicit expectation of only a single hardware clock > interrupt source. > > > > I'm sure that this is a naive picture of what's going on (and I'm not a > > kernel developer), but it works. I realize that it is probably specific > > to the Lynx architecture, and I of course would be happy for a 'correct' > > way to allow this old box to happily crank along solving PDE's. > > As I implied in my previous posting, I think your fix is the > correct one, and John's would be a statistical fix, at best, > which I would not trust. > > An interesting question would be whether or not you can have > different clock rates for different CPU's on the box, and what > happens in that case (whether the answer is right or not). > > As the clock is calibrated on a single CPU at startup, it's a > problem of interrrupt routing being symmetric vs. generation > being symmetric; if it's the former, then you're OK, and if it's > the latter, then John's fix is better, even if it is only > statistical. > > -- Terry > > 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 Nov 13 1:37:50 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 401A737B401 for ; Wed, 13 Nov 2002 01:37:50 -0800 (PST) Received: from mail.tepkom.ru (mail.tepkom.ru [195.9.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8C1F43E42 for ; Wed, 13 Nov 2002 01:37:47 -0800 (PST) (envelope-from wart@mojo.tepkom.ru) Received: from mojo.tepkom.ru (mojo.tepkom.ru [195.9.10.30]) by mail.tepkom.ru (8.11.6/8.11.6) with ESMTP id gAD8qZt61365 for ; Wed, 13 Nov 2002 11:52:35 +0300 (MSK) (envelope-from wart@mojo.tepkom.ru) Received: from wart by mojo.tepkom.ru with local (Exim 3.36 #1 (Debian)) id 18BtF7-00061H-00 for ; Wed, 13 Nov 2002 11:51:25 +0300 Date: Wed, 13 Nov 2002 11:51:24 +0300 From: Wartan Hachaturow To: freebsd-alpha@freebsd.org Subject: Any TODO out there? Message-ID: <20021113085124.GA23125@mojo.tepkom.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello. I did recently acquired an alpha machine (164LX), and now looking forward in helping FreeBSD's Alpha port. Is there any TODO list available for this port? Any things that need to be done? -- Regards, Wartan. "Computers are not intelligent. They only think they are." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 13 2:21: 7 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A675537B401 for ; Wed, 13 Nov 2002 02:21:06 -0800 (PST) Received: from scaup.mail.pas.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4886043E42 for ; Wed, 13 Nov 2002 02:21:06 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0207.cvx21-bradley.dialup.earthlink.net ([209.179.192.207] helo=mindspring.com) by scaup.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18Bucd-0005iL-00; Wed, 13 Nov 2002 02:19:48 -0800 Message-ID: <3DD22648.35D7B3DE@mindspring.com> Date: Wed, 13 Nov 2002 02:15:36 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Wartan Hachaturow Cc: freebsd-alpha@freebsd.org Subject: Re: Any TODO out there? References: <20021113085124.GA23125@mojo.tepkom.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Wartan Hachaturow wrote: > I did recently acquired an alpha machine (164LX), and now > looking forward in helping FreeBSD's Alpha port. > Is there any TODO list available for this port? Any things that > need to be done? There are some really hard ones; I'm sure someone else will give a different list with the easy ones on it. Here are two of the really hard ones: (1) How much RAM do you have? FreeBSD Alpha doesn't work on >2G because some drivers need to use the bus space functions to make sure all DMAs occur in the window accessible to the various busses. For an small overview: cd /usr/src/sys/alpha find . -type f | xargs fgrep 2G There are other things that could be done, as well, but this one needs someone with a system with enough RAM and who cares, to work on it. (2) If you are a real massochist, you could work on making FreeBSD work with firmware other than SRM (that's a *lot* of work, though). People occasionally complain that FreeBSD won't boot on NT-only Alpha machines. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 13 3:13:24 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3B8837B401 for ; Wed, 13 Nov 2002 03:13:22 -0800 (PST) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id 251CC43E77 for ; Wed, 13 Nov 2002 03:13:21 -0800 (PST) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.6/8.12.6) with ESMTP id gADBDIbY007081; Wed, 13 Nov 2002 12:13:19 +0100 (CET) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.6/8.12.6/Submit) id gADBDIKG007080; Wed, 13 Nov 2002 12:13:18 +0100 (CET) Date: Wed, 13 Nov 2002 12:13:18 +0100 From: Wilko Bulte To: Terry Lambert Cc: Wartan Hachaturow , freebsd-alpha@FreeBSD.ORG Subject: Re: Any TODO out there? Message-ID: <20021113121318.A7034@freebie.xs4all.nl> References: <20021113085124.GA23125@mojo.tepkom.ru> <3DD22648.35D7B3DE@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3DD22648.35D7B3DE@mindspring.com>; from tlambert2@mindspring.com on Wed, Nov 13, 2002 at 02:15:36AM -0800 X-OS: FreeBSD 4.7-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Nov 13, 2002 at 02:15:36AM -0800, Terry Lambert wrote: > Wartan Hachaturow wrote: > > I did recently acquired an alpha machine (164LX), and now > > looking forward in helping FreeBSD's Alpha port. > > Is there any TODO list available for this port? Any things that > > need to be done? > > There are some really hard ones; I'm sure someone else will give > a different list with the easy ones on it. Here are two of the > really hard ones: > > (1) > > How much RAM do you have? > > FreeBSD Alpha doesn't work on >2G because some drivers need to > use the bus space functions to make sure all DMAs occur in the > window accessible to the various busses. For an small overview: > > cd /usr/src/sys/alpha > find . -type f | xargs fgrep 2G > > There are other things that could be done, as well, but this one > needs someone with a system with enough RAM and who cares, to work > on it. > > (2) > > If you are a real massochist, you could work on making FreeBSD Make that Real Masochist(TM) as it is a nasty job. > work with firmware other than SRM (that's a *lot* of work, > though). People occasionally complain that FreeBSD won't boot > on NT-only Alpha machines. Given that this mostly is for XL and XLT machines which are EV4 and EV5 (slow EV5) based I would not consider it worthwhile unless you have too much time :) -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 13 4:29:29 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04C9F37B401 for ; Wed, 13 Nov 2002 04:29:28 -0800 (PST) Received: from mail.tepkom.ru (mail.tepkom.ru [195.9.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42D5843E4A for ; Wed, 13 Nov 2002 04:29:13 -0800 (PST) (envelope-from wart@mojo.tepkom.ru) Received: from mojo.tepkom.ru (mojo.tepkom.ru [195.9.10.30]) by mail.tepkom.ru (8.11.6/8.11.6) with ESMTP id gADCT5t65776 for ; Wed, 13 Nov 2002 15:29:05 +0300 (MSK) (envelope-from wart@mojo.tepkom.ru) Received: from wart by mojo.tepkom.ru with local (Exim 3.36 #1 (Debian)) id 18Bwcd-0001ZB-00 for ; Wed, 13 Nov 2002 15:27:55 +0300 Date: Wed, 13 Nov 2002 15:27:55 +0300 From: Wartan Hachaturow To: freebsd-alpha@freebsd.org Subject: Re: Any TODO out there? Message-ID: <20021113122755.GA5995@mojo.tepkom.ru> References: <20021113085124.GA23125@mojo.tepkom.ru> <3DD22648.35D7B3DE@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3DD22648.35D7B3DE@mindspring.com> User-Agent: Mutt/1.4i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Nov 13, 2002 at 02:15:36AM -0800, Terry Lambert wrote: > (1) > How much RAM do you have? No, 512Mb, so "2G barrier" is not for me :) > If you are a real massochist, you could work on making FreeBSD > work with firmware other than SRM (that's a *lot* of work, > though). People occasionally complain that FreeBSD won't boot > on NT-only Alpha machines. Hmm, I guess this one is not applicable for me either. I use SRM :) BTW, I tried searching PR database on "Alpha" section, and found only one PR with patch attached. Are there any other bug databases? (I'm unfortunately not that familar with FreeBSD development process -- I'm a Debian developer, just decided to help the "Other OS I Like and Use" :) -- Regards, Wartan. "Computers are not intelligent. They only think they are." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 13 7:30:32 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 270CD37B401 for ; Wed, 13 Nov 2002 07:30:32 -0800 (PST) Received: from reiher.informatik.uni-wuerzburg.de (wi4d22.informatik.uni-wuerzburg.de [132.187.101.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 366DD43E4A for ; Wed, 13 Nov 2002 07:30:30 -0800 (PST) (envelope-from mkb@mukappabeta.de) Received: from mukappabeta.de (localhost [127.0.0.1]) by reiher.informatik.uni-wuerzburg.de (Postfix) with ESMTP id 3CACCA92B; Wed, 13 Nov 2002 16:30:17 +0100 (CET) Message-ID: <3DD27009.90003@mukappabeta.de> Date: Wed, 13 Nov 2002 16:30:17 +0100 From: Matthias Buelow User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20021024 X-Accept-Language: de, en MIME-Version: 1.0 To: Terry Lambert Cc: Wartan Hachaturow , freebsd-alpha@freebsd.org Subject: Re: Any TODO out there? References: <20021113085124.GA23125@mojo.tepkom.ru> <3DD22648.35D7B3DE@mindspring.com> X-Enigmail-Version: 0.65.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Terry Lambert wrote: > FreeBSD Alpha doesn't work on >2G because some drivers need to > use the bus space functions to make sure all DMAs occur in the > window accessible to the various busses. For an small overview: Are you sure the limit isn't 1Gig? I have a PWS with 1.5GB and on reporting crashes on boot with 4.7 to the list, I was told it was because fbsd doesn't have DMA bouncing or whatever to < 1GB (yet). -- Matthias Buelow To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 13 7:30:38 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F5BA37B401 for ; Wed, 13 Nov 2002 07:30:37 -0800 (PST) Received: from mail.inka.de (quechua.inka.de [193.197.184.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E378D43E6E for ; Wed, 13 Nov 2002 07:30:36 -0800 (PST) (envelope-from mailnull@mips.inka.de) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with gbsmtp id 18BzTP-0006RH-03; Wed, 13 Nov 2002 16:30:35 +0100 Received: from kemoauc.mips.inka.de (localhost [127.0.0.1]) by kemoauc.mips.inka.de (8.12.6/8.12.6) with ESMTP id gADFAI02046631 for ; Wed, 13 Nov 2002 16:10:18 +0100 (CET) (envelope-from mailnull@localhost.mips.inka.de) Received: (from mailnull@localhost) by kemoauc.mips.inka.de (8.12.6/8.12.6/Submit) id gADFAIsH046630 for freebsd-alpha@freebsd.org; Wed, 13 Nov 2002 16:10:18 +0100 (CET) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: Any TODO out there? Date: Wed, 13 Nov 2002 15:10:17 +0000 (UTC) Message-ID: References: <20021113085124.GA23125@mojo.tepkom.ru> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Wartan Hachaturow wrote: > I did recently acquired an alpha machine (164LX), and now > looking forward in helping FreeBSD's Alpha port. > Is there any TODO list available for this port? Any things that > need to be done? Are you looking for system or ports tree work? The latter is easy to find. Go to /usr/ports, start building and running random stuff. You'll run into breakage pretty quickly. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 13 7:54:53 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D0F837B401 for ; Wed, 13 Nov 2002 07:54:52 -0800 (PST) Received: from gatekeeper.oremut01.us.wh.verio.net (gatekeeper.oremut01.us.wh.verio.net [198.65.168.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3B5443E42 for ; Wed, 13 Nov 2002 07:54:51 -0800 (PST) (envelope-from fclift@verio.net) Received: from mx.dmz.orem.verio.net (mx.dmz.orem.verio.net [10.1.1.10]) by gatekeeper.oremut01.us.wh.verio.net (Postfix) with ESMTP id 38EAF3BF1E7 for ; Wed, 13 Nov 2002 08:54:51 -0700 (MST) Received: from vespa.dmz.orem.verio.net (vespa.dmz.orem.verio.net [10.1.1.59]) by mx.dmz.orem.verio.net (8.11.6/8.11.6) with ESMTP id gADFsn398523; Wed, 13 Nov 2002 08:54:49 -0700 (MST) Date: Wed, 13 Nov 2002 08:56:16 -0700 (MST) From: Fred Clift X-X-Sender: To: Wartan Hachaturow Cc: Subject: Re: Any TODO out there? In-Reply-To: <20021113085124.GA23125@mojo.tepkom.ru> Message-ID: <20021113085517.G74969-100000@vespa.dmz.orem.verio.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 13 Nov 2002, Wartan Hachaturow wrote: > Hello. > > I did recently acquired an alpha machine (164LX), and now > looking forward in helping FreeBSD's Alpha port. > Is there any TODO list available for this port? Any things that > need to be done? You can try building random things you might want to use in the ports tree - there are plenty of ports that dont work seamlessly, or at all. Fred -- Fred Clift - fclift@verio.net -- Remember: If brute force doesn't work, you're just not using enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 13 8: 1:44 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C07237B401 for ; Wed, 13 Nov 2002 08:01:43 -0800 (PST) Received: from l04.oase.research.kpn.com (l04.oase.research.kpn.com [139.63.192.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5752143E3B for ; Wed, 13 Nov 2002 08:01:41 -0800 (PST) (envelope-from K.J.Koster@kpn.com) Received: by l04.oase.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Wed, 13 Nov 2002 17:01:39 +0100 Message-ID: <59063B5B4D98D311BC0D0001FA7E45220A3568A3@l04.oase.research.kpn.com> From: K.J.Koster@kpn.com To: wart@tepkom.ru Cc: freebsd-alpha@FreeBSD.ORG Subject: RE: Any TODO out there? Date: Wed, 13 Nov 2002 17:01:38 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Dear Wartan, > > I did recently acquired an alpha machine (164LX), and now > looking forward in helping FreeBSD's Alpha port. > Is there any TODO list available for this port? Any things that > need to be done? > I think there's a problem with timed not being 64-bit clean on Alpha. Kees Jan ===================================================== You can't have everything. Where would you put it? [Steven Wright] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 13 8: 6:31 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7FEC637B401 for ; Wed, 13 Nov 2002 08:06:30 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70FB043E75 for ; Wed, 13 Nov 2002 08:06:29 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA15913; Wed, 13 Nov 2002 11:05:55 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gADG5Pn51320; Wed, 13 Nov 2002 11:05:25 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15826.30789.443260.294559@grasshopper.cs.duke.edu> Date: Wed, 13 Nov 2002 11:05:25 -0500 (EST) To: Matthias Buelow Cc: Terry Lambert , Wartan Hachaturow , freebsd-alpha@FreeBSD.ORG Subject: Re: Any TODO out there? In-Reply-To: <3DD27009.90003@mukappabeta.de> References: <20021113085124.GA23125@mojo.tepkom.ru> <3DD22648.35D7B3DE@mindspring.com> <3DD27009.90003@mukappabeta.de> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Matthias Buelow writes: > Terry Lambert wrote: > > > FreeBSD Alpha doesn't work on >2G because some drivers need to > > use the bus space functions to make sure all DMAs occur in the > > window accessible to the various busses. For an small overview: > > Are you sure the limit isn't 1Gig? I have a PWS with 1.5GB and on > reporting crashes on boot with 4.7 to the list, I was told it was > because fbsd doesn't have DMA bouncing or whatever to < 1GB (yet). Its 1GB on most machines, 2GB on some newer ones. And its not bouncing, its re-mapping. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 13 9: 2:56 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C753C37B414 for ; Wed, 13 Nov 2002 09:02:53 -0800 (PST) Received: from mail.speakeasy.net (mail17.speakeasy.net [216.254.0.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2FA943E75 for ; Wed, 13 Nov 2002 09:02:51 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 14232 invoked from network); 13 Nov 2002 17:02:55 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail17.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 13 Nov 2002 17:02:55 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.6/8.12.6) with ESMTP id gADH2m2D008466; Wed, 13 Nov 2002 12:02:49 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <1037142521.27992.41.camel@focaccia.> Date: Wed, 13 Nov 2002 12:02:50 -0500 (EST) From: John Baldwin To: "Michael A. Mackey" Subject: Re: Extreme time drift in SMP mode Cc: freebsd-alpha@freebsd.org, Terry Lambert Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 12-Nov-2002 Michael A. Mackey wrote: > I guess I don't understand the problem. > > It seemed to me that the problem was that not all the interrupts were > being delivered because the Lynx architecture expects each processor to > generate interrupts. Before the fix, the system lost time by an amount > which was equivalent to throwing away half of the interrupts. After my > modification, each processor is allowed to generate clock interrupts, > and the system receives the complete set of interrupts, yielding the > result that the system keeps time correctly. > > I'm sure that this is a naive picture of what's going on (and I'm not a > kernel developer), but it works. I realize that it is probably specific > to the Lynx architecture, and I of course would be happy for a 'correct' > way to allow this old box to happily crank along solving PDE's. > > > Anyway, I sure am glad to have such high quality software to run on this > box. > Keep up the great work FreeBSD-Alpha! I'll try to explain. For better or for worse, FreeBSD currently uses the following model of clock interrupts to drive hardclock() (update timecounters, handle profiling, drive softclock) and statclock() (update statistics): For each "virtual" system-wide clock interrupt, all CPU's execute statclock_process() and hardclock_process() (should be renamed to *_thread() at this point) to perform process-specific updates (profiling, stats, etc.) that need to happen on all CPU's. All but one of these CPU's execute these functions directly from their clock interrupt. One CPU executes statclock() and hardclock() directly which call the _process() variants as part of their task, but also perform system-wide updates such as update the timecounters and drive softclock(). On i386, clock interrupts are only sent to one processor in a sort of round-robin fashion. What we do there is that each time a clock interrupt occurs, the receiving CPU acts as the "master" CPU and executes hardclock() and statclock(). It then IPI's all the other CPU's in the system to simulate a system-wide clock interrupt, and all the other CPU's in the system then execute the _process() functions. When we did SMP on Alpha we wanted to avoid sending all those IPI's if possible. For one thing, IPI's in general are expensive. On the Alpha they are a bit worse though as you can only IPI one CPU at a time whereas on i386 you can send broadcast IPI's to all other CPU's at once. On at least the 4100 and DS20 type machines, we found that the clock interrupt was broadcast to all CPU's, but in a round-robin fashion. That is, if we were getting X clock interrupts / sec in UP on CPU 0, we still got X clock ints / sec on CPU 0, but we also got X clock ints / sec on CPU 1, 2, etc. but offset so that they didn't all get interrupted at once. Thus, we made the boot processor the "master" CPU for all clock interrupts and had it call hardclock() and statclock() while all the other CPU's would call the _process() variants. Basically, the system was doing the global IPI for us except that since the interrupts were staggered, there was less contesting on common locks. Now enter the 2100 into the picture. I'm not really sure what it is doing with its clock interrupts. I'm not sure if it is acting like a i386 and round-robin'ing the clock interrupts to all processors or if it is acting like other Alpha's but slowing down the clock. Probably it is acting like a i386 and we might need to just change the 2100 clock interrupt handler to use the i386 model and go and IPI the other CPU's when a clock interrupt comes in. If anyone can stick more than 2 CPU's in a 2100 system and see if the clock runs 3x or 4x as slow that might help. The reason I would prefer to just dink with the timer_freq is that it is simple and doesn't change the model that system-wide things like timekeeping only happen once per "virtual" clock interrupt. -- 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 Wed Nov 13 9: 2:57 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0B7337B401 for ; Wed, 13 Nov 2002 09:02:55 -0800 (PST) Received: from mail.speakeasy.net (mail16.speakeasy.net [216.254.0.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6532A43E42 for ; Wed, 13 Nov 2002 09:02:55 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 23649 invoked from network); 13 Nov 2002 17:02:57 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail16.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 13 Nov 2002 17:02:57 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.6/8.12.6) with ESMTP id gADH2p2D008473; Wed, 13 Nov 2002 12:02:52 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <59063B5B4D98D311BC0D0001FA7E45220A3568A3@l04.oase.research.kpn.com> Date: Wed, 13 Nov 2002 12:02:53 -0500 (EST) From: John Baldwin To: K.J.Koster@kpn.com Subject: RE: Any TODO out there? Cc: freebsd-alpha@FreeBSD.ORG, wart@tepkom.ru Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 13-Nov-2002 K.J.Koster@kpn.com wrote: > Dear Wartan, > >> >> I did recently acquired an alpha machine (164LX), and now >> looking forward in helping FreeBSD's Alpha port. >> Is there any TODO list available for this port? Any things that >> need to be done? >> > I think there's a problem with timed not being 64-bit clean on Alpha. timed works fine. It did have some problems on sparc64 though (due to endian issues) but I fixed those a while ago. -- 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 Wed Nov 13 10:38:39 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7921E37B401 for ; Wed, 13 Nov 2002 10:38:38 -0800 (PST) Received: from mail.tepkom.ru (mail.tepkom.ru [195.9.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80AB243E4A for ; Wed, 13 Nov 2002 10:38:15 -0800 (PST) (envelope-from wart@mojo.tepkom.ru) Received: from mojo.tepkom.ru (mojo.tepkom.ru [195.9.10.30]) by mail.tepkom.ru (8.11.6/8.11.6) with ESMTP id gADIbpt73071 for ; Wed, 13 Nov 2002 21:37:51 +0300 (MSK) (envelope-from wart@mojo.tepkom.ru) Received: from wart by mojo.tepkom.ru with local (Exim 3.36 #1 (Debian)) id 18C2NU-000840-00 for ; Wed, 13 Nov 2002 21:36:40 +0300 Date: Wed, 13 Nov 2002 21:36:40 +0300 From: Wartan Hachaturow To: freebsd-alpha@freebsd.org Subject: Re: Any TODO out there? Message-ID: <20021113183640.GA12798@mojo.tepkom.ru> References: <20021113085124.GA23125@mojo.tepkom.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Nov 13, 2002 at 03:10:17PM +0000, Christian Weisgerber wrote: > Are you looking for system or ports tree work? The latter is easy Well, I've been looking mostly for system work -- ports can be so boring :) But thanks for the idea, anyway. It is a boring, but needed job. -- Regards, Wartan. "Computers are not intelligent. They only think they are." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 13 10:42:28 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D17E37B401 for ; Wed, 13 Nov 2002 10:42:28 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A52643E42 for ; Wed, 13 Nov 2002 10:42:27 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA26527; Wed, 13 Nov 2002 13:42:21 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gADIfp351434; Wed, 13 Nov 2002 13:41:51 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15826.40175.235699.586835@grasshopper.cs.duke.edu> Date: Wed, 13 Nov 2002 13:41:51 -0500 (EST) To: Wartan Hachaturow Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Any TODO out there? In-Reply-To: <20021113183640.GA12798@mojo.tepkom.ru> References: <20021113085124.GA23125@mojo.tepkom.ru> <20021113183640.GA12798@mojo.tepkom.ru> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Wartan Hachaturow writes: > On Wed, Nov 13, 2002 at 03:10:17PM +0000, Christian Weisgerber wrote: > > > Are you looking for system or ports tree work? The latter is easy > > Well, I've been looking mostly for system work -- ports can be > so boring :) But thanks for the idea, anyway. It is a boring, but > needed job. If you want system work, and are interested in the DMA mapping issues, you can poke your host bridge chip to reduce the size of the direct-mapped window to make testing busdma changes/fixes meaningful. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 13 10:55:22 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF76A37B401 for ; Wed, 13 Nov 2002 10:55:19 -0800 (PST) Received: from server07.icaen.uiowa.edu (server07.icaen.uiowa.edu [128.255.17.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1638C43E42 for ; Wed, 13 Nov 2002 10:55:19 -0800 (PST) (envelope-from michael-mackey@uiowa.edu) Received: from server11.icaen.uiowa.edu (server11.icaen.uiowa.edu [128.255.17.51]) by server07.icaen.uiowa.edu (8.9.3/8.9.3) with ESMTP id MAA02374 for sent by ; Wed, 13 Nov 2002 12:55:29 -0600 (CST) Received: from TURING (turing.ecn.uiowa.edu [128.255.23.75]) by server11.icaen.uiowa.edu (8.9.3/smtp-service-1.6) with ESMTP id MAA17990 for ; sent by ; Wed, 13 Nov 2002 12:55:11 -0600 (CST) From: "Michael A. Mackey" To: Subject: RE: Extreme time drift in SMP mode Date: Wed, 13 Nov 2002 12:54:56 -0600 Message-ID: <002301c28b46$294c40f0$4b17ff80@TURING> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Thanks for your time in explaining this. I should be receiving some more cpu's for this thing in a day or two - I'll let you know how that changes the timing issues. -----Original Message----- From: owner-freebsd-alpha@FreeBSD.org [mailto:owner-freebsd-alpha@FreeBSD.org] On Behalf Of John Baldwin Sent: Wednesday, November 13, 2002 11:03 AM To: Michael A. Mackey Cc: freebsd-alpha@FreeBSD.org; Terry Lambert Subject: Re: Extreme time drift in SMP mode On 12-Nov-2002 Michael A. Mackey wrote: > I guess I don't understand the problem. > > It seemed to me that the problem was that not all the interrupts were > being delivered because the Lynx architecture expects each processor to > generate interrupts. Before the fix, the system lost time by an amount > which was equivalent to throwing away half of the interrupts. After my > modification, each processor is allowed to generate clock interrupts, > and the system receives the complete set of interrupts, yielding the > result that the system keeps time correctly. > > I'm sure that this is a naive picture of what's going on (and I'm not a > kernel developer), but it works. I realize that it is probably specific > to the Lynx architecture, and I of course would be happy for a 'correct' > way to allow this old box to happily crank along solving PDE's. > > > Anyway, I sure am glad to have such high quality software to run on this > box. > Keep up the great work FreeBSD-Alpha! I'll try to explain. For better or for worse, FreeBSD currently uses the following model of clock interrupts to drive hardclock() (update timecounters, handle profiling, drive softclock) and statclock() (update statistics): For each "virtual" system-wide clock interrupt, all CPU's execute statclock_process() and hardclock_process() (should be renamed to *_thread() at this point) to perform process-specific updates (profiling, stats, etc.) that need to happen on all CPU's. All but one of these CPU's execute these functions directly from their clock interrupt. One CPU executes statclock() and hardclock() directly which call the _process() variants as part of their task, but also perform system-wide updates such as update the timecounters and drive softclock(). On i386, clock interrupts are only sent to one processor in a sort of round-robin fashion. What we do there is that each time a clock interrupt occurs, the receiving CPU acts as the "master" CPU and executes hardclock() and statclock(). It then IPI's all the other CPU's in the system to simulate a system-wide clock interrupt, and all the other CPU's in the system then execute the _process() functions. When we did SMP on Alpha we wanted to avoid sending all those IPI's if possible. For one thing, IPI's in general are expensive. On the Alpha they are a bit worse though as you can only IPI one CPU at a time whereas on i386 you can send broadcast IPI's to all other CPU's at once. On at least the 4100 and DS20 type machines, we found that the clock interrupt was broadcast to all CPU's, but in a round-robin fashion. That is, if we were getting X clock interrupts / sec in UP on CPU 0, we still got X clock ints / sec on CPU 0, but we also got X clock ints / sec on CPU 1, 2, etc. but offset so that they didn't all get interrupted at once. Thus, we made the boot processor the "master" CPU for all clock interrupts and had it call hardclock() and statclock() while all the other CPU's would call the _process() variants. Basically, the system was doing the global IPI for us except that since the interrupts were staggered, there was less contesting on common locks. Now enter the 2100 into the picture. I'm not really sure what it is doing with its clock interrupts. I'm not sure if it is acting like a i386 and round-robin'ing the clock interrupts to all processors or if it is acting like other Alpha's but slowing down the clock. Probably it is acting like a i386 and we might need to just change the 2100 clock interrupt handler to use the i386 model and go and IPI the other CPU's when a clock interrupt comes in. If anyone can stick more than 2 CPU's in a 2100 system and see if the clock runs 3x or 4x as slow that might help. The reason I would prefer to just dink with the timer_freq is that it is simple and doesn't change the model that system-wide things like timekeeping only happen once per "virtual" clock interrupt. -- 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 Wed Nov 13 11: 8:23 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C5BA37B401 for ; Wed, 13 Nov 2002 11:08:11 -0800 (PST) Received: from mail.hiwaay.net (fly.hiwaay.net [216.180.54.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBD8643E4A for ; Wed, 13 Nov 2002 11:08:09 -0800 (PST) (envelope-from kdunn@hiwaay.net) Received: from mail.hiwaay.net (localhost [127.0.0.1]) by mail.hiwaay.net (8.12.5/8.12.5) with ESMTP id gADJ89nO483124 for ; Wed, 13 Nov 2002 13:08:09 -0600 (CST) Received: from localhost (kdunn@localhost) by mail.hiwaay.net (8.12.5/8.12.5/flySubmit) with ESMTP id gADJ88A3100210 for ; Wed, 13 Nov 2002 13:08:08 -0600 (CST) X-Authentication-Warning: fly.hiwaay.net: kdunn owned process doing -bs Date: Wed, 13 Nov 2002 13:08:08 -0600 (CST) From: "Karl L. Dunn" Reply-To: Karl Dunn To: freebsd-alpha@freebsd.org Subject: Multia: syscons does not find PCI vga card Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have a Multia/UDB (alpha) to which I added a Diamond VGA card in the internal PCI slot. This has a S3 Trio64V+ chip. The intent is to be able to run X over FreeBSD 4.6.2. Linux RH6.0 (boot from the ARC of course) works OK with the S3 card (XF86_S3), and it worked OK with the internal TGA card (XF86_TGA). But it's Linux, and I'd much rather have FreeBSD. The SRM talks only to the TGA. I don't care about that -- I can set it to autoboot and move the monitor to the S3 VGA and forget about it unless I want to see it again someday. The problem is that syscons can't find the S3 VGA (see the verbose dmesg output below). Maybe this is related to what the SRM leaves behind, but I doubt it. The kernel here is the GENERIC that came on the 4.6.2 CD I got from the BSD mall. Can anybody give me some help here? If this can't be solved, can the TGA be used for X on 4.6.2, and if so how? (It looks as if some of the stuff needed is in the source tree.) I like the S3 card more than the TGA, but I have used the TGA with Linux and NTalpha (ugh!) for about two years, and it's certainly usable. --- Karl L. Dunn k.l.dunn@ieee.org ======================================================================= Multia/UDB SRM screen after power-up ======================================================================= Multia SRM Console BL5 V3.8-3, built on Aug 10 1995 at 03:22:55 Testing Memory from 8 to 64 meg... Executing power-up script... version BL5 V3.8-3 Aug 10 1995 03:22:55 dka100.1.0.6.0 DKA100 CONNER CFP4207S 4.28GB 1524 dka200.2.0.6.0 DKA200 SEAGATE ST318418N 0003 dka400.4.0.6.0 DKA400 YAMAHA CRW8424S 1.0d dva0.0.0.0.1 DVA0 ewa0.0.0.8.0 EWA0 08-00-2B-E5-F0-7C pka0.7.0.6.0 PKA0 SCSI Bus ID 7 64 Meg of system memory CPU speed is 166 MHZ Cache size is 256 Kbytes >>>boot dka200 ======================================================================= dmesg after boot -v (ESC at loader countdown, then boot -v) ======================================================================= Unrecognized boot flag '0'. Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.6.2-RELEASE #0: Thu Aug 22 20:40:14 GMT 2002 root@sema.baldwin.cx:/usr/src/sys/compile/GENERIC DEC AXPpci (PCI ISA), 167MHz 8192 byte page size, 1 processor. CPU: LCA Family major=4 minor=2 OSF PAL rev: 0x1000000020123 real memory = 64684032 (63168K bytes) Physical memory chunk(s): 0x007e2000 - 0x03f0dfff, 57851904 bytes (7062 pages) avail memory = 55894016 (54584K bytes) Preloaded elf kernel "kernel" at 0xfffffc00007c6000. md0: Malloc disk Creating DISK md0 found-> vendor=0x0003, dev=0x0000, revid=0x03 class=00-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 found-> vendor=0x1000, dev=0x0001, revid=0x02 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base 00010000, size 8 map[14]: type 1, range 32, base 81000000, size 8 found-> vendor=0x8086, dev=0x0484, revid=0x84 class=00-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x1011, dev=0x0002, revid=0x23 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=15 map[10]: type 1, range 32, base 00010100, size 7 map[14]: type 1, range 32, base 81000100, size 7 found-> vendor=0x0000, dev=0x0000, revid=0x00 class=00-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 found-> vendor=0x1011, dev=0x0004, revid=0x02 class=03-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base 88000000, size 25 found-> vendor=0x5333, dev=0x8811, revid=0x54 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=15 map[10]: type 1, range 32, base 84000000, size 26 found-> vendor=0x00c0, dev=0x0000, revid=0x00 class=00-02-00, hdrtype=0x0f, mfdev=0 subordinatebus=0 secondarybus=0 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 dec_axppci_33_intr_map: bad interrupt pin 30 found-> vendor=0x1e02, dev=0x0000, revid=0x02 class=00-00-1e, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=~, irq=2 map[10]: type 1, range 20, base 00001e00, size 9 map[14]: type 1, range 20, base 00001e00, size 9 map[18]: type 1, range 20, base 00001e00, size 9 map[1c]: type 1, range 20, base 00001e00, size 9 map[20]: type 1, range 20, base 00001e00, size 9 map[24]: type 1, range 20, base 00001e00, size 9 pci0: on pcib0 pci0: (vendor=0x0003, dev=0x0000) at 0.0 pci0: (vendor=0x1e02, dev=0x0000) at 1.0 irq 2 pci0: (vendor=0x1e02, dev=0x0000) at 2.0 irq 2 pci0: (vendor=0x1e02, dev=0x0000) at 3.0 irq 2 pci0: (vendor=0x1e02, dev=0x0000) at 4.0 irq 2 pci0: (vendor=0x1e02, dev=0x0000) at 5.0 irq 2 sym0: <810> port 0x10000-0x100ff mem 0x81000000-0x810000ff irq 11 at device 6.0 on pci0 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking sym0: open drain IRQ line driver sym0: using NCR-generic firmware. sym0: initial SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 00/00/00/00/00/00 sym0: final SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 03/c8/00/00/08/00 sym0: Delay (GEN=11): 234 msec, 37984 KHz sym0: Delay (GEN=11): 291 msec, 30544 KHz sym0: Delay (GEN=11): 292 msec, 30439 KHz sym0: interrupting at ISA irq 11 isab0: at device 7.0 on pci0 Bus Modes: Bus Park, Resource Lock, IDE controller: Secondary (170h-177h,376h,377h) Floppy controller: 370h,371h Floppy controller: 372h-377h Keyboard controller: 60h,62h,64h,66h RTC: 70h-77h Configuration RAM: 0C00h,0800h-08FFh Port 92: enabled isa0: on isab0 de0: port 0x10100-0x1017f mem 0x81000100-0x8100017f irq 15 at device 8.0 on pci0 de0: interrupting at ISA irq 15 de0: DEC 21040 [10Mb/s] pass 2.3 de0: address 08:00:2b:e5:f0:7c bpf: de0 attached pci0: (vendor=0x0000, dev=0x0000) at 9.0 pci0: (vendor=0x1e02, dev=0x0000) at 10.0 irq 2 pci0: (vendor=0x1011, dev=0x0004) at 11.0 irq 10 pci0: (vendor=0x5333, dev=0x8811) at 12.0 irq 15 pci0: (vendor=0x00c0, dev=0x0000) at 14.0 pci0: (vendor=0x1e02, dev=0x0000) at 15.0 irq 2 pci0: (vendor=0x1e02, dev=0x0000) at 16.0 irq 2 pci0: (vendor=0x1e02, dev=0x0000) at 17.0 irq 2 pci0: (vendor=0x1e02, dev=0x0000) at 18.0 irq 2 pci0: (vendor=0x1e02, dev=0x0000) at 19.0 irq 2 pci0: (vendor=0x1e02, dev=0x0000) at 20.0 irq 2 pci0: (vendor=0x1e02, dev=0x0000) at 21.0 irq 2 pci0: (vendor=0x1e02, dev=0x0000) at 22.0 irq 2 pci0: (vendor=0x1e02, dev=0x0000) at 23.0 irq 2 pci0: (vendor=0x1e02, dev=0x0000) at 24.0 irq 2 pci0: (vendor=0x1e02, dev=0x0000) at 25.0 irq 2 pci0: (vendor=0x1e02, dev=0x0000) at 26.0 irq 2 pci0: (vendor=0x1e02, dev=0x0000) at 27.0 irq 2 pci0: (vendor=0x1e02, dev=0x0000) at 28.0 irq 2 pci0: (vendor=0x1e02, dev=0x0000) at 29.0 irq 2 pci0: (vendor=0x1e02, dev=0x0000) at 30.0 irq 2 pci0: (vendor=0x1e02, dev=0x0000) at 31.0 irq 2 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: interrupting at ISA irq 6 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0023 atkbd: keyboard ID 0x83ab (2) kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x1d0000 atkbd0: interrupting at ISA irq 1 psm0: current command byte:0063 psm0: irq 12 on atkbdc0 psm0: interrupting at ISA irq 12 psm0: model Generic PS/2 mouse, device ID 0-00, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 vga0: failed to probe on isa0 sc0: no video adapter found. sc0: failed to probe on isa0 mcclock0: at port 0x70-0x71 on isa0 Calibrating clock(s) ... PCC clock: 166646718 Hz (firmware 167166666 Hz) sio0: irq maps: 0x8044 0x8054 0x8044 0x8044 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio0: interrupting at ISA irq 4 sio1: reserved for low-level i/o sio1 failed to probe at port 0x2f8-0x2ff irq 3 flags 0x50 on isa0 ppc0: using extended I/O port range ppc0: SPP ppc0: at port 0x3bc-0x3c3 irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Polled port ppi0: on ppbus0 ppc0: interrupting at ISA irq 7 isa_probe_children: probing PnP devices Timecounter "alpha" frequency 166646718 Hz bpf: lo0 attached bpf: ppp0 attached bpf: sl0 attached bpf: faith0 attached Waiting 15 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. de0: enabling 10baseT port (probe4:sym0:0:4:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe4:sym0:0:4:0): ILLEGAL REQUEST asc:24,0 (probe4:sym0:0:4:0): Invalid field in CDB Creating DISK da0 Creating DISK da1 Creating DISK cd0 pass0 at sym0 bus 0 target 1 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number DX90WE4 pass0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled pass1 at sym0 bus 0 target 2 lun 0 pass1: Fixed Direct Access SCSI-3 device pass1: Serial Number 3JJ02ZFE0000724594XN pass1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled pass2 at sym0 bus 0 target 4 lun 0 pass2: Removable CD-ROM SCSI-2 device pass2: 10.000MB/s transfers (10.000MHz, offset 8) da0 at sym0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number DX90WE4 da0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da0: 4096MB (8388608 512 byte sectors: 255H 63S/T 522C) da1 at sym0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-3 device da1: Serial Number 3JJ02ZFE0000724594XN da1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da1: 19001MB (38914049 512 byte sectors: 255H 63S/T 2422C) Mounting root from ufs:/dev/da1a (cd0:sym0:0:4:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:sym0:0:4:0): NOT READY asc:3a,1 (cd0:sym0:0:4:0): Medium not present - tray closed cd0 at sym0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed da1: invalid primary partition table: no magic start_init: trying /sbin/init ======================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 13 11:10:38 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 54B1837B401; Wed, 13 Nov 2002 11:10:36 -0800 (PST) Received: from net2.gendyn.com (gate2.gendyn.com [204.60.171.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C0C343E4A; Wed, 13 Nov 2002 11:10:34 -0800 (PST) (envelope-from eischen@vigrid.com) Received: from [153.11.11.3] (helo=ebnext01) by net2.gendyn.com with esmtp (Exim 2.12 #1) id 18C2u8-0001Mg-00; Wed, 13 Nov 2002 14:10:24 -0500 Received: from clcrtr.gdeb.com ([153.11.109.11]) by ebnext01 with SMTP id gADJANLQ030462; Wed, 13 Nov 2002 14:10:23 -0500 Received: from vigrid.com (gpz.clc.gdeb.com [192.168.3.12]) by clcrtr.gdeb.com (8.11.4/8.11.4) with ESMTP id gACLhLl39632; Tue, 12 Nov 2002 16:43:23 -0500 (EST) (envelope-from eischen@vigrid.com) Message-ID: <3DD2A3AD.D6ECFD0@vigrid.com> Date: Wed, 13 Nov 2002 14:10:37 -0500 From: Daniel Eischen X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.9 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: alpha@FreeBSD.org Cc: sparc@FreeBSD.org Subject: [PATCH] *context() as syscalls Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I've got a patch that makes {get,set,swap}context() system calls, removing them from libc. I've built and tested an i386 kernel, but can only build an alpha kernel (a buildworld is in progress now). Can someone test an alpha kernel with this patch? For sparc, ia64, and powerpc, I just returned ENOSYS for now. It shouldn't break any builds and can be implemented later. Thanks, -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 13 11:13:18 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2260E37B401; Wed, 13 Nov 2002 11:13:16 -0800 (PST) Received: from net2.gendyn.com (gate2.gendyn.com [204.60.171.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5123F43E4A; Wed, 13 Nov 2002 11:13:14 -0800 (PST) (envelope-from eischen@vigrid.com) Received: from [153.11.11.3] (helo=ebnext01) by net2.gendyn.com with esmtp (Exim 2.12 #1) id 18C2wj-0001hz-00; Wed, 13 Nov 2002 14:13:05 -0500 Received: from clcrtr.gdeb.com ([153.11.109.11]) by ebnext01 with SMTP id gADJD4LQ029432; Wed, 13 Nov 2002 14:13:04 -0500 Received: from vigrid.com (gpz.clc.gdeb.com [192.168.3.12]) by clcrtr.gdeb.com (8.11.4/8.11.4) with ESMTP id gACLk4l39640; Tue, 12 Nov 2002 16:46:04 -0500 (EST) (envelope-from eischen@vigrid.com) Message-ID: <3DD2A44F.95F9DD30@vigrid.com> Date: Wed, 13 Nov 2002 14:13:19 -0500 From: Daniel Eischen X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.9 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: alpha@FreeBSD.org Cc: sparc@FreeBSD.org Subject: [PATCH] *context() as syscalls Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Oops, forgot to include URL. http://people.freebsd.org/~deischen/uc-sys.diffs > I've got a patch that makes {get,set,swap}context() system calls, > removing them from libc. I've built and tested an i386 kernel, > but can only build an alpha kernel (a buildworld is in progress > now). > > Can someone test an alpha kernel with this patch? > > For sparc, ia64, and powerpc, I just returned ENOSYS for now. > It shouldn't break any builds and can be implemented later. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 13 12:26:48 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 345D337B404; Wed, 13 Nov 2002 12:26:47 -0800 (PST) Received: from alcanet.com.au (mail3.alcanet.com.au [208.178.117.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C2E843E4A; Wed, 13 Nov 2002 12:26:45 -0800 (PST) (envelope-from peter.jeremy@alcatel.com.au) Received: from sydsmtp01.alcatel.com.au (IDENT:root@localhost.localdomain [127.0.0.1]) by alcanet.com.au (8.12.4/8.12.4/Alcanet1.3) with ESMTP id gADKQcwL022135; Thu, 14 Nov 2002 07:26:38 +1100 Received: from gsmx07.alcatel.com.au ([139.188.20.247]) by sydsmtp01.alcatel.com.au (Lotus Domino Release 5.0.11) with ESMTP id 2002111407263763:26356 ; Thu, 14 Nov 2002 07:26:37 +1100 Received: from gsmx07.alcatel.com.au (localhost [127.0.0.1]) by gsmx07.alcatel.com.au (8.12.5/8.12.5) with ESMTP id gADKQbRL023760; Thu, 14 Nov 2002 07:26:37 +1100 (EST) (envelope-from peter.jeremy@alcatel.com.au) Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.12.5/8.12.5/Submit) id gADKQacx023759; Thu, 14 Nov 2002 07:26:36 +1100 (EST) (envelope-from peter.jeremy@alcatel.com.au) Date: Thu, 14 Nov 2002 07:26:36 +1100 From: Peter Jeremy To: John Baldwin Cc: alpha@FreeBSD.ORG Subject: Re: cvs commit: src/sys/conf files files.i386 files.pc98 Message-ID: <20021113202636.GA23652@gsmx07.alcatel.com.au> Mail-Followup-To: John Baldwin , alpha@FreeBSD.ORG References: <200211082233.gA8MXFSc085711@repoman.freebsd.org> Mime-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.4i X-MIMETrack: Itemize by SMTP Server on SYDSMTP01/AlcatelAustralia(Release 5.0.11 |July 24, 2002) at 14/11/2002 07:26:37 AM, Serialize by Router on SYDSMTP01/AlcatelAustralia(Release 5.0.11 |July 24, 2002) at 14/11/2002 07:26:38 AM, Serialize complete at 14/11/2002 07:26:38 AM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 2002-Nov-08 17:55:20 -0500, John Baldwin wrote: >Even with all this we still have a problem. :) The problem is that >the kernel is too big (well, .text is too big) for it to link with >our current atomic operation implementation. The problem is that in >order to optimize for the common case, our atomic operations branch >to a branch in the .text3 section in the failure case. We branch the >way we do to take advantage of branch prediction on the alpha. However, >the LINT kernel is so big that .text is large enough that the linker >cannot handle some of the relocations to places in .text3 resulting in >truncating the relocations. Any ideas on fixing this? Has any checked to see if arranging the atomic operation logic to avoid a forward branch in the success case actually provides a performance benefit? Unless the kernel is covered by either super-page or large-page ITB mappings, the cost of a likely ITB miss will outweigh the branch prediction benefits. There's also a probable Icache (and maybe other caches) miss. Also, not all the AXP implementations actually use the branch direction for prediction. The 2106xA variants all use a 2-bit history in the Icache (with a new line just inheriting whatever's left over from the previous entry). I'm not sure about more recent chips (I don't have the specs to hand). The only other option I can see is a new section tag that means "load this section after any similarly-named sections within the current module". This would push the forward branches to the end of the current module rather than the end of the kernel. The downside is that it means more custom hacks to gas and ld. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 13 13:41:38 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0857037B404 for ; Wed, 13 Nov 2002 13:41:37 -0800 (PST) Received: from mail.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CF6D43E8A for ; Wed, 13 Nov 2002 13:41:31 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 3486 invoked from network); 13 Nov 2002 21:41:38 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 13 Nov 2002 21:41:38 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.6/8.12.6) with ESMTP id gADLfS2D009383; Wed, 13 Nov 2002 16:41:29 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20021113202636.GA23652@gsmx07.alcatel.com.au> Date: Wed, 13 Nov 2002 16:41:31 -0500 (EST) From: John Baldwin To: Peter Jeremy Subject: Re: cvs commit: src/sys/conf files files.i386 files.pc98 Cc: alpha@FreeBSD.ORG Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 13-Nov-2002 Peter Jeremy wrote: > On 2002-Nov-08 17:55:20 -0500, John Baldwin wrote: >>Even with all this we still have a problem. :) The problem is that >>the kernel is too big (well, .text is too big) for it to link with >>our current atomic operation implementation. The problem is that in >>order to optimize for the common case, our atomic operations branch >>to a branch in the .text3 section in the failure case. We branch the >>way we do to take advantage of branch prediction on the alpha. However, >>the LINT kernel is so big that .text is large enough that the linker >>cannot handle some of the relocations to places in .text3 resulting in >>truncating the relocations. Any ideas on fixing this? > > Has any checked to see if arranging the atomic operation logic to > avoid a forward branch in the success case actually provides a > performance benefit? I don't know. I think we may have gotten them that way from NetBSD. It is how the Brown Book recommends that one do things. However, the Brown Book didn't recommend jumping to the end of the kernel and back either. :-( > Unless the kernel is covered by either super-page or large-page ITB > mappings, the cost of a likely ITB miss will outweigh the branch > prediction benefits. There's also a probable Icache (and maybe other > caches) miss. Also, not all the AXP implementations actually use the > branch direction for prediction. The 2106xA variants all use a 2-bit > history in the Icache (with a new line just inheriting whatever's left > over from the previous entry). I'm not sure about more recent chips > (I don't have the specs to hand). > > The only other option I can see is a new section tag that means "load > this section after any similarly-named sections within the current > module". This would push the forward branches to the end of the > current module rather than the end of the kernel. The downside is > that it means more custom hacks to gas and ld. Well, custom hacks to binutils would be a Bad Thing (tm). Perhaps there is already a way to do this in gas and ld that we just don't know about? -- 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 Wed Nov 13 14:11:52 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4AEE337B401 for ; Wed, 13 Nov 2002 14:11:51 -0800 (PST) Received: from alcanet.com.au (mail2.alcanet.com.au [203.62.196.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 128FC43E75 for ; Wed, 13 Nov 2002 14:11:50 -0800 (PST) (envelope-from peter.jeremy@alcatel.com.au) Received: from sydsmtp01.alcatel.com.au (IDENT:root@localhost.localdomain [127.0.0.1]) by alcanet.com.au (8.12.4/8.12.4/Alcanet1.3) with ESMTP id gADMBl5O022927; Thu, 14 Nov 2002 09:11:47 +1100 Received: from gsmx07.alcatel.com.au ([139.188.20.247]) by sydsmtp01.alcatel.com.au (Lotus Domino Release 5.0.11) with ESMTP id 2002111409114575:27080 ; Thu, 14 Nov 2002 09:11:45 +1100 Received: from gsmx07.alcatel.com.au (localhost [127.0.0.1]) by gsmx07.alcatel.com.au (8.12.5/8.12.5) with ESMTP id gADMBjRL024035; Thu, 14 Nov 2002 09:11:45 +1100 (EST) (envelope-from peter.jeremy@alcatel.com.au) Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.12.5/8.12.5/Submit) id gADMBjh8024034; Thu, 14 Nov 2002 09:11:45 +1100 (EST) (envelope-from peter.jeremy@alcatel.com.au) Date: Thu, 14 Nov 2002 09:11:45 +1100 From: Peter Jeremy To: Karl Dunn Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Multia: syscons does not find PCI vga card Message-ID: <20021113221144.GU6446@gsmx07.alcatel.com.au> Mail-Followup-To: Karl Dunn , freebsd-alpha@FreeBSD.ORG References: Mime-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.4i X-MIMETrack: Itemize by SMTP Server on SYDSMTP01/AlcatelAustralia(Release 5.0.11 |July 24, 2002) at 14/11/2002 09:11:45 AM, Serialize by Router on SYDSMTP01/AlcatelAustralia(Release 5.0.11 |July 24, 2002) at 14/11/2002 09:11:47 AM, Serialize complete at 14/11/2002 09:11:47 AM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 2002-Nov-13 13:08:08 -0600, "Karl L. Dunn" wrote: >I have a Multia/UDB (alpha) to which I added a Diamond VGA card in the >internal PCI slot. This has a S3 Trio64V+ chip. The intent is to be able >to run X over FreeBSD 4.6.2. I haven't actually tried it yet, but all the documentation states that the TGA is supported by XFree86 - both 3.3.6 and 4.2.0 (and maybe older 4.x versions). There is FreeBSD support for the TGA in -current and the driver code also supports -stable. I thought it had been MFC'd but it looks like it hasn't. If you rummage back through the archives of this list, you should find instructions for getting a TGA running in -stable. (The original port was to -stable and I was only involved in porting it to -current). >The problem is that syscons can't find the S3 VGA (see the verbose dmesg >output below). Maybe this is related to what the SRM leaves behind, but I >doubt it. The kernel here is the GENERIC that came on the 4.6.2 CD I got >from the BSD mall. The S3 card is being found as a PCI device. The problem is that syscons looks for an ISA VGA card. There's a variety of glue logic that makes the PCI card masquerate as an ISA device for booting purposes - and I believe that this needs SRM assistance as well. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 13 14:20:31 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 794AE37B401 for ; Wed, 13 Nov 2002 14:20:30 -0800 (PST) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 546D043E42 for ; Wed, 13 Nov 2002 14:20:29 -0800 (PST) (envelope-from ticso@cicely8.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) by srv1.cosmo-project.de (8.12.5/8.12.5) with ESMTP id gADMKOsP053466 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Wed, 13 Nov 2002 23:20:26 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.1.10]) by cicely5.cicely.de (8.12.6/8.12.6) with ESMTP id gADMKNCu070350 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 13 Nov 2002 23:20:24 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (localhost [127.0.0.1]) by cicely8.cicely.de (8.12.6/8.12.6) with ESMTP id gADMKNl8073663; Wed, 13 Nov 2002 23:20:23 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: (from ticso@localhost) by cicely8.cicely.de (8.12.6/8.12.6/Submit) id gADMKMkC073662; Wed, 13 Nov 2002 23:20:22 +0100 (CET) Date: Wed, 13 Nov 2002 23:20:22 +0100 From: Bernd Walter To: Karl Dunn Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Multia: syscons does not find PCI vga card Message-ID: <20021113222021.GS71666@cicely8.cicely.de> Reply-To: ticso@cicely.de References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely8.cicely.de 5.0-CURRENT i386 User-Agent: Mutt/1.5.1i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Nov 13, 2002 at 01:08:08PM -0600, Karl L. Dunn wrote: > I have a Multia/UDB (alpha) to which I added a Diamond VGA card in the > internal PCI slot. This has a S3 Trio64V+ chip. The intent is to be able > to run X over FreeBSD 4.6.2. > > Linux RH6.0 (boot from the ARC of course) works OK with the S3 card > (XF86_S3), and it worked OK with the internal TGA card (XF86_TGA). But > it's Linux, and I'd much rather have FreeBSD. > > The SRM talks only to the TGA. I don't care about that -- I can set it to > autoboot and move the monitor to the S3 VGA and forget about it unless I > want to see it again someday. You need to initialize a card for text mode. This is normaly done by the BIOS. Especially as FreeBSD needs it on the standart VGA addresses, which is part of the PCI initialisation of the BIOS. Nevertheless if SRM had initialized the normal PCI part of that card you can use it with XF86. > The problem is that syscons can't find the S3 VGA (see the verbose dmesg > output below). Maybe this is related to what the SRM leaves behind, but I > doubt it. The kernel here is the GENERIC that came on the 4.6.2 CD I got > from the BSD mall. > > Can anybody give me some help here? > > If this can't be solved, can the TGA be used for X on 4.6.2, and if so > how? (It looks as if some of the stuff needed is in the source tree.) I > like the S3 card more than the TGA, but I have used the TGA with Linux and > NTalpha (ugh!) for about two years, and it's certainly usable. I don't know, but if it has worked with XF86 on Linux chances are good that it also works with FreeBSD. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 13 16:58:11 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1134837B404 for ; Wed, 13 Nov 2002 16:58:10 -0800 (PST) Received: from conure.mail.pas.earthlink.net (conure.mail.pas.earthlink.net [207.217.120.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEA1D43E42 for ; Wed, 13 Nov 2002 16:58:09 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0374.cvx22-bradley.dialup.earthlink.net ([209.179.199.119] helo=mindspring.com) by conure.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18C8K9-0004Kr-00; Wed, 13 Nov 2002 16:57:38 -0800 Message-ID: <3DD2F4A5.450C0C4F@mindspring.com> Date: Wed, 13 Nov 2002 16:56:05 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Matthias Buelow Cc: Wartan Hachaturow , freebsd-alpha@freebsd.org Subject: Re: Any TODO out there? References: <20021113085124.GA23125@mojo.tepkom.ru> <3DD22648.35D7B3DE@mindspring.com> <3DD27009.90003@mukappabeta.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Matthias Buelow wrote: > Terry Lambert wrote: > > FreeBSD Alpha doesn't work on >2G because some drivers need to > > use the bus space functions to make sure all DMAs occur in the > > window accessible to the various busses. For an small overview: > > Are you sure the limit isn't 1Gig? I have a PWS with 1.5GB and on > reporting crashes on boot with 4.7 to the list, I was told it was > because fbsd doesn't have DMA bouncing or whatever to < 1GB (yet). Depends on the alpha. If you do the "grep", you'll see that there are three cases where Windows are setup; most cases deal with 2G, but one of them is 1G. The general problem is a driver problem, though. FreeBSD has DMA bouncing, the drivers just aren't coded to use it, so you run into a problem. FreeBSD on x86 using PAE or PSE36, should that come in, will end up having problems with the same drivers, FWIW, so the work's going to be appreciated, if someone has an Alpha with enough memory to trigger the problem reliably... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 13 17: 4: 7 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 18FFC37B401 for ; Wed, 13 Nov 2002 17:04:07 -0800 (PST) Received: from conure.mail.pas.earthlink.net (conure.mail.pas.earthlink.net [207.217.120.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAC8C43E42 for ; Wed, 13 Nov 2002 17:04:06 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0374.cvx22-bradley.dialup.earthlink.net ([209.179.199.119] helo=mindspring.com) by conure.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18C8Q2-0006Cp-00; Wed, 13 Nov 2002 17:03:42 -0800 Message-ID: <3DD2F610.5548B3BE@mindspring.com> Date: Wed, 13 Nov 2002 17:02:08 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Wartan Hachaturow Cc: freebsd-alpha@freebsd.org Subject: Re: Any TODO out there? References: <20021113085124.GA23125@mojo.tepkom.ru> <20021113183640.GA12798@mojo.tepkom.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Wartan Hachaturow wrote: > On Wed, Nov 13, 2002 at 03:10:17PM +0000, Christian Weisgerber wrote: > > Are you looking for system or ports tree work? The latter is easy > > Well, I've been looking mostly for system work -- ports can be > so boring :) But thanks for the idea, anyway. It is a boring, but > needed job. I always forget ports, because I simply don't have the bandwidth or disk space to pull down all that code to compile them like that. If you have both, ports are a good thing to work on. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 13 17: 4:46 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6818437B401 for ; Wed, 13 Nov 2002 17:04:45 -0800 (PST) Received: from conure.mail.pas.earthlink.net (conure.mail.pas.earthlink.net [207.217.120.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F0F843E42 for ; Wed, 13 Nov 2002 17:04:45 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0374.cvx22-bradley.dialup.earthlink.net ([209.179.199.119] helo=mindspring.com) by conure.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18C8Qp-0007VH-00; Wed, 13 Nov 2002 17:04:32 -0800 Message-ID: <3DD2F640.666A08F@mindspring.com> Date: Wed, 13 Nov 2002 17:02:56 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Gallatin Cc: Wartan Hachaturow , freebsd-alpha@FreeBSD.ORG Subject: Re: Any TODO out there? References: <20021113085124.GA23125@mojo.tepkom.ru> <20021113183640.GA12798@mojo.tepkom.ru> <15826.40175.235699.586835@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Andrew Gallatin wrote: > Wartan Hachaturow writes: > > On Wed, Nov 13, 2002 at 03:10:17PM +0000, Christian Weisgerber wrote: > > > > > Are you looking for system or ports tree work? The latter is easy > > > > Well, I've been looking mostly for system work -- ports can be > > so boring :) But thanks for the idea, anyway. It is a boring, but > > needed job. > > If you want system work, and are interested in the DMA mapping issues, > you can poke your host bridge chip to reduce the size of the > direct-mapped window to make testing busdma changes/fixes meaningful. Sneaky; I never even thought of that... 8-(. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 13 17:33:41 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5724B37B401 for ; Wed, 13 Nov 2002 17:33:39 -0800 (PST) Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6FC943E6E for ; Wed, 13 Nov 2002 17:33:38 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0374.cvx22-bradley.dialup.earthlink.net ([209.179.199.119] helo=mindspring.com) by falcon.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18C8sw-0004Ar-00; Wed, 13 Nov 2002 17:33:34 -0800 Message-ID: <3DD2FD05.882412E3@mindspring.com> Date: Wed, 13 Nov 2002 17:31:49 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Karl Dunn Cc: freebsd-alpha@freebsd.org Subject: Re: Multia: syscons does not find PCI vga card References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org "Karl L. Dunn" wrote: > I have a Multia/UDB (alpha) to which I added a Diamond VGA card in the > internal PCI slot. This has a S3 Trio64V+ chip. The intent is to be able > to run X over FreeBSD 4.6.2. [ ... ] > The problem is that syscons can't find the S3 VGA (see the verbose dmesg > output below). Maybe this is related to what the SRM leaves behind, but I > doubt it. The kernel here is the GENERIC that came on the 4.6.2 CD I got > from the BSD mall. [ ... ] > pci0: (vendor=0x5333, dev=0x8811) at 12.0 irq 15 [ ... ] > sc0: no video adapter found. > sc0: failed to probe on isa0 OK. Probably it's because the syscons code forces vid_register() in the case that it's possible to use it as a console, and that calls probe_adapters(), which ends up returning noting, because the PCI bus hasn't been probed yet, and there's no BIOS knowledge of an adapter. Basically, this means that "vga_init_done" is true, and so it doesn't get reprobed later. The fix is to make the syscons driver inelegible as a console device, which should avoid the early probe, at which point the later probe should find it successfully, since it doesn't have a failed probe that won't be repeated. Alternately, you can hack probe_agapters() in /sys/dev/fb/vga.c: #if !defined(VGS_NO_BIOS) /* do this test only once */ if (vga_init_done) return biosadapters; #endif and this will probably work for your case, but is not something that can be committed because it would screw up part of the time. If you want a permanent fix, you'll want to only set vgs_init_done to TRUE in the case that it's found. This *might* work satisfactorily (it doesn't puke out my x86 box): /* do this test only once */ if (vga_init_done && biosadapters > 0) return biosadapters; ...it causes the probe to repeat, even if it was attempted previously, so long as it failed previously. IT's ugly, but if you have no console, you probably don't care. Really, the console code wants to be able to be attached at any point in the boot process, so that your console messages end up going to "the no place", until the console is attached to syscons. That's a lot of work, and it would be very hard to get past an x86-centric commit review, so I don't recommend it. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 13 20:54: 7 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37CFC37B401; Wed, 13 Nov 2002 20:53:59 -0800 (PST) Received: from mta08.mail.mel.aone.net.au (mta08.mail.au.uu.net [203.2.192.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7C9643E7B; Wed, 13 Nov 2002 20:53:57 -0800 (PST) (envelope-from rbyrnes@ozemail.com.au) Received: from ausyddtp0050 ([203.166.67.234]) by mta08.mail.mel.aone.net.au with ESMTP id <20021114045343.FLOW7429.mta08.mail.mel.aone.net.au@ausyddtp0050>; Thu, 14 Nov 2002 15:53:43 +1100 MIME-Version: 1.0 To: John Baldwin Cc: freebsd-alpha@freebsd.org, Andrew Gallatin Subject: Re: 5.0 alpha install tests References: Message-ID: Content-Type: text/plain; charset=iso-8859-15; format=flowed From: Rob Date: Thu, 14 Nov 2002 15:53:35 +1100 User-Agent: Opera M2 7.0 build 2345 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, 09 Nov 2002 09:39:04 -0500 (EST), John Baldwin wrote: > > On 09-Nov-2002 Rob B wrote: >> ----- Original Message ----- >> From: "Andrew Gallatin" >> To: "Rob B" >> Cc: >> Sent: Thursday, November 07, 2002 1:44 PM >> Subject: Re: 5.0 alpha install tests >> >> >>> Rob B writes: >>> > >>> > OK ... maybe my terminology was out (a lot). The APECS is in dmesg, >> the >>> > IDE interfaces don't show up at all. >>> >>> Again, it would help, A LOT, to see dmesg, pciconf -lv, and 'show >>> conf' output. (the latter being done from the SRM console). >> >>>>> sho conf >> Digital AlphaPC 64 274MHz >> SRM Console V4.8-1 VMS PALcode V5.56-1, OSF PALcode V1.45-4 >> DECchip (tm) 21064A-2 >> DECchip (tm) 21071-DA Pass 1 >> DECchip (tm) 21071-CA Pass 2 >> >> MEMORY >> 64Meg of system memory >> >> >> PCI Bus >> Bus 00 Slot 05: NCR 53C875 Scsi Controller >> pka0.7.0.5.0 Scsi Bus ID 7 >> dka0.0.0.5.0 COMPAQ >> BD00421936 >> Bus 00 Slot 08: Intel 82378IB PCI to ISA Bridge >> >> ISA >> Slot Device Name Type Enabled >> BaseAddr >> IRQ DMA >> 0 >> 0 MOUSE Embedded Yes 60 >> 12 >> 1 KBD Embedded Yes 60 >> 1 >> 2 COM1 Embedded Yes 3f8 >> 4 >> 3 COM2 Embedded Yes 2f8 >> 3 >> 4 LPT1 Embedded Yes >> 3bc 7 >> 5 FLOPPY Embedded Yes 3f0 >> 6 2 >> >> aylee# dmesg >> Copyright (c) 1992-2002 The FreeBSD Project. >> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 >> The Regents of the University of California. All rights reserved. >> FreeBSD 5.0-DP1 #0: Sun Apr 7 07:34:25 GMT 2002 >> murray@axpbuilder.freebsdmall.com:/usr/src/sys/alpha/compile/GENERIC >> Preloaded elf kernel "/boot/kernel/kernel" at 0xfffffc0000814000. >> EB64+ >> Digital AlphaPC 64 274 MHz, 274MHz >> 8192 byte page size, 1 processor. >> CPU: EV45 (21064A) major=6 minor=2 >> OSF PAL rev: 0x100040002012d >> real memory = 65019904 (63496K bytes) >> avail memory = 55279616 (53984K bytes) >> apecs0: >> pci0: on pcib0 >> sym0: <875> port 0x10000-0x100ff mem >> 0x8205c000-0x8205cfff,0x8205d000-0x8205d0ff irq 2 at device 5.0 on pci0 >> sym0: Tekram NVRAM, ID 7, Fast-20, SE, parity checking >> sym0: interrupting at APECS irq 2 >> pci0: at device 7.0 (no driver attached) >> isab0: at device 8.0 on pci0 >> isa0: on isab0 >> dc0: port 0x10100-0x1017f mem >> 0x8205d100-0x8205d17f irq 3 at device 9.0 on pci0 >> dc0: interrupting at APECS irq 3 >> dc0: Ethernet address: 08:00:2b:c3:dd:56 >> miibus0: on dc0 >> dcphy0: on miibus0 >> dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> atkbdc0: at port 0x64,0x60 on isa0 >> atkbd0: irq 1 on atkbdc0 >> atkbd0: interrupting at ISA irq 1 >> fdc0: at port >> 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 >> fdc0: interrupting at ISA irq 6 >> mcclock0: at port 0x70-0x71 on isa0 >> ppc0: at port 0x3bc-0x3c3 irq 7 on isa0 >> ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode >> plip0: cannot reserve interrupt, failed. >> lpt0: on ppbus0 >> lpt0: Polled port >> ppi0: on ppbus0 >> ppc0: interrupting at ISA irq 7 >> sc0: on isa0 >> sc0: VGA <16 virtual consoles, flags=0x200> >> sio0 at port 0x3f8-0x3ff irq 4 on isa0 >> sio0: type 16550A >> sio0: interrupting at ISA irq 4 >> sio1: reserved for low-level i/o >> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on >> isa0 >> Timecounter "i8254" frequency 1193182 Hz >> Timecounter "alpha" frequency 275002485 Hz >> Waiting 15 seconds for SCSI devices to settle >> da0 at sym0 bus 0 target 0 lun 0 >> da0: Fixed Direct Access SCSI-2 device >> da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing >> Enabled >> da0: 4091MB (8380080 512 byte sectors: 255H 63S/T 521C) >> Mounting root from ufs:/dev/da0a >> >> >> aylee# pciconf -lv >> sym0@pci0:5:0: class=0x010000 card=0x00000000 chip=0x000f1000 rev=0x01 >> hdr=0x00 >> vendor = 'Symbios Logic (NCR) (LSI Logic)' >> device = '53C875, 53C876 Ultra-Wide SCSI (53C876 is dual-channel)' >> class = mass storage >> subclass = SCSI >> none0@pci0:7:0: class=0x030000 card=0x00000000 chip=0x0519102b rev=0x01 >> hdr=0x00 >> vendor = 'Matrox Graphics Inc' >> device = 'MGA-2064W Millenium GUI Accelerator' >> class = display >> subclass = VGA >> isab0@pci0:8:0: class=0x000000 card=0x00000000 chip=0x04848086 rev=0x84 >> hdr=0x00 >> vendor = 'Intel Corporation' >> device = '82378ZB/IB,82379AB PCI to ISA Bridge, System I/O' >> class = old >> subclass = non-VGA display device >> dc0@pci0:9:0: class=0x020000 card=0x500b1011 chip=0x00191011 rev=0x30 >> hdr=0x00 >> vendor = 'Digital Equipment Corporation' >> device = 'DC21142/3 PCI/CardBus 10/100 Mbit Ethernet Ctlr' >> class = network >> subclass = ethernet >> >> >>> Also, did this work with previous version of FreeBSD, or is this the >>> first time this machine was installed with FreeBSD? >> >> It's never worked, but I've also not needed it prior to now > > Do you have an ISA ATA controller? If so, try breaking into the > loader (hit a key during the 10 second countdown) and type in the > following: > > set hint.ata.0.at="isa" > set hint.ata.0.port="0x1f0" > set hint.ata.0.irq="14" > set hint.ata.1.at="isa" > set hint.ata.1.port="0x170" > set hint.ata.1.irq="15" > boot > > If it does work, then add the following lines to your /boot/device.hints > file: > > hint.ata.0.at="isa" > hint.ata.0.port="0x1F0" > hint.ata.0.irq="14" > hint.ata.1.at="isa" > hint.ata.1.port="0x170" > hint.ata.1.irq="15" > > Also, if that does work, then we should think about adding those lines > to GENERIC.hints for Alpha. > Thanks John, seems that it works ... now just gotta fix my b0rked fstab. Something went awry in the build - most likely PEBKAC -- Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 14 7:14:55 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05B9637B40C for ; Thu, 14 Nov 2002 07:14:50 -0800 (PST) Received: from mail.speakeasy.net (mail13.speakeasy.net [216.254.0.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D0FC43E4A for ; Thu, 14 Nov 2002 07:14:49 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 9258 invoked from network); 14 Nov 2002 15:14:51 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail13.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 14 Nov 2002 15:14:51 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.6/8.12.6) with ESMTP id gAEFEl2D011807; Thu, 14 Nov 2002 10:14:47 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 14 Nov 2002 10:14:49 -0500 (EST) From: John Baldwin To: Rob Subject: Re: 5.0 alpha install tests Cc: Andrew Gallatin , freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 14-Nov-2002 Rob wrote: > On Sat, 09 Nov 2002 09:39:04 -0500 (EST), John Baldwin wrote: > >> >> On 09-Nov-2002 Rob B wrote: >>> ----- Original Message ----- >>> From: "Andrew Gallatin" >>> To: "Rob B" >>> Cc: >>> Sent: Thursday, November 07, 2002 1:44 PM >>> Subject: Re: 5.0 alpha install tests >>> >>> >>>> Rob B writes: >>>> > >>>> > OK ... maybe my terminology was out (a lot). The APECS is in dmesg, >>> the >>>> > IDE interfaces don't show up at all. >>>> >>>> Again, it would help, A LOT, to see dmesg, pciconf -lv, and 'show >>>> conf' output. (the latter being done from the SRM console). >>> >>>>>> sho conf >>> Digital AlphaPC 64 274MHz >>> SRM Console V4.8-1 VMS PALcode V5.56-1, OSF PALcode V1.45-4 >>> DECchip (tm) 21064A-2 >>> DECchip (tm) 21071-DA Pass 1 >>> DECchip (tm) 21071-CA Pass 2 >>> >>> MEMORY >>> 64Meg of system memory >>> >>> >>> PCI Bus >>> Bus 00 Slot 05: NCR 53C875 Scsi Controller >>> pka0.7.0.5.0 Scsi Bus ID 7 >>> dka0.0.0.5.0 COMPAQ >>> BD00421936 >>> Bus 00 Slot 08: Intel 82378IB PCI to ISA Bridge >>> >>> ISA >>> Slot Device Name Type Enabled >>> BaseAddr >>> IRQ DMA >>> 0 >>> 0 MOUSE Embedded Yes 60 >>> 12 >>> 1 KBD Embedded Yes 60 >>> 1 >>> 2 COM1 Embedded Yes 3f8 >>> 4 >>> 3 COM2 Embedded Yes 2f8 >>> 3 >>> 4 LPT1 Embedded Yes >>> 3bc 7 >>> 5 FLOPPY Embedded Yes 3f0 >>> 6 2 >>> >>> aylee# dmesg >>> Copyright (c) 1992-2002 The FreeBSD Project. >>> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 >>> The Regents of the University of California. All rights reserved. >>> FreeBSD 5.0-DP1 #0: Sun Apr 7 07:34:25 GMT 2002 >>> murray@axpbuilder.freebsdmall.com:/usr/src/sys/alpha/compile/GENERIC >>> Preloaded elf kernel "/boot/kernel/kernel" at 0xfffffc0000814000. >>> EB64+ >>> Digital AlphaPC 64 274 MHz, 274MHz >>> 8192 byte page size, 1 processor. >>> CPU: EV45 (21064A) major=6 minor=2 >>> OSF PAL rev: 0x100040002012d >>> real memory = 65019904 (63496K bytes) >>> avail memory = 55279616 (53984K bytes) >>> apecs0: >>> pci0: on pcib0 >>> sym0: <875> port 0x10000-0x100ff mem >>> 0x8205c000-0x8205cfff,0x8205d000-0x8205d0ff irq 2 at device 5.0 on pci0 >>> sym0: Tekram NVRAM, ID 7, Fast-20, SE, parity checking >>> sym0: interrupting at APECS irq 2 >>> pci0: at device 7.0 (no driver attached) >>> isab0: at device 8.0 on pci0 >>> isa0: on isab0 >>> dc0: port 0x10100-0x1017f mem >>> 0x8205d100-0x8205d17f irq 3 at device 9.0 on pci0 >>> dc0: interrupting at APECS irq 3 >>> dc0: Ethernet address: 08:00:2b:c3:dd:56 >>> miibus0: on dc0 >>> dcphy0: on miibus0 >>> dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >>> atkbdc0: at port 0x64,0x60 on isa0 >>> atkbd0: irq 1 on atkbdc0 >>> atkbd0: interrupting at ISA irq 1 >>> fdc0: at port >>> 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 >>> fdc0: interrupting at ISA irq 6 >>> mcclock0: at port 0x70-0x71 on isa0 >>> ppc0: at port 0x3bc-0x3c3 irq 7 on isa0 >>> ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode >>> plip0: cannot reserve interrupt, failed. >>> lpt0: on ppbus0 >>> lpt0: Polled port >>> ppi0: on ppbus0 >>> ppc0: interrupting at ISA irq 7 >>> sc0: on isa0 >>> sc0: VGA <16 virtual consoles, flags=0x200> >>> sio0 at port 0x3f8-0x3ff irq 4 on isa0 >>> sio0: type 16550A >>> sio0: interrupting at ISA irq 4 >>> sio1: reserved for low-level i/o >>> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on >>> isa0 >>> Timecounter "i8254" frequency 1193182 Hz >>> Timecounter "alpha" frequency 275002485 Hz >>> Waiting 15 seconds for SCSI devices to settle >>> da0 at sym0 bus 0 target 0 lun 0 >>> da0: Fixed Direct Access SCSI-2 device >>> da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing >>> Enabled >>> da0: 4091MB (8380080 512 byte sectors: 255H 63S/T 521C) >>> Mounting root from ufs:/dev/da0a >>> >>> >>> aylee# pciconf -lv >>> sym0@pci0:5:0: class=0x010000 card=0x00000000 chip=0x000f1000 rev=0x01 >>> hdr=0x00 >>> vendor = 'Symbios Logic (NCR) (LSI Logic)' >>> device = '53C875, 53C876 Ultra-Wide SCSI (53C876 is dual-channel)' >>> class = mass storage >>> subclass = SCSI >>> none0@pci0:7:0: class=0x030000 card=0x00000000 chip=0x0519102b rev=0x01 >>> hdr=0x00 >>> vendor = 'Matrox Graphics Inc' >>> device = 'MGA-2064W Millenium GUI Accelerator' >>> class = display >>> subclass = VGA >>> isab0@pci0:8:0: class=0x000000 card=0x00000000 chip=0x04848086 rev=0x84 >>> hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = '82378ZB/IB,82379AB PCI to ISA Bridge, System I/O' >>> class = old >>> subclass = non-VGA display device >>> dc0@pci0:9:0: class=0x020000 card=0x500b1011 chip=0x00191011 rev=0x30 >>> hdr=0x00 >>> vendor = 'Digital Equipment Corporation' >>> device = 'DC21142/3 PCI/CardBus 10/100 Mbit Ethernet Ctlr' >>> class = network >>> subclass = ethernet >>> >>> >>>> Also, did this work with previous version of FreeBSD, or is this the >>>> first time this machine was installed with FreeBSD? >>> >>> It's never worked, but I've also not needed it prior to now >> >> Do you have an ISA ATA controller? If so, try breaking into the >> loader (hit a key during the 10 second countdown) and type in the >> following: >> >> set hint.ata.0.at="isa" >> set hint.ata.0.port="0x1f0" >> set hint.ata.0.irq="14" >> set hint.ata.1.at="isa" >> set hint.ata.1.port="0x170" >> set hint.ata.1.irq="15" >> boot >> >> If it does work, then add the following lines to your /boot/device.hints >> file: >> >> hint.ata.0.at="isa" >> hint.ata.0.port="0x1F0" >> hint.ata.0.irq="14" >> hint.ata.1.at="isa" >> hint.ata.1.port="0x170" >> hint.ata.1.irq="15" >> >> Also, if that does work, then we should think about adding those lines >> to GENERIC.hints for Alpha. >> > > Thanks John, seems that it works ... now just gotta fix my b0rked fstab. > Something went awry in the build - most likely PEBKAC Ok, great. I'll add those hints to GENERIC.hints then so that this can work out of the box. -- 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 Thu Nov 14 10:22:48 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 95B8F37B401 for ; Thu, 14 Nov 2002 10:22:45 -0800 (PST) Received: from blacklamb.mykitchentable.net (207-173-241-209.bras01.elk.ca.frontiernet.net [207.173.241.209]) by mx1.FreeBSD.org (Postfix) with ESMTP id E77BD43E4A for ; Thu, 14 Nov 2002 10:22:44 -0800 (PST) (envelope-from drew@mykitchentable.net) Received: from tagalong (unknown [165.107.42.110]) by blacklamb.mykitchentable.net (Postfix) with SMTP id 395D3EE571 for ; Thu, 14 Nov 2002 10:22:44 -0800 (PST) Message-ID: <009301c28c0a$d356fc10$6e2a6ba5@tagalong> From: "Drew Tomlinson" To: Subject: Fw: OpenSSL Problems Building Webmin Port Date: Thu, 14 Nov 2002 10:22:44 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I sent the following post to -questions a few days ago but have not gotten a response. I'm hoping someone here might have an idea on how to resolve this problem. Thanks, Drew ----- Original Message ----- From: "Drew Tomlinson" To: "FreeBSD Questions" Sent: Tuesday, November 12, 2002 3:20 PM Subject: OpenSSL Problems Building Webmin Port > I just installed 4.7-RELEASE on a ev56 Alpha platform via bootdisks and > FTP. The install went without a hitch. Next I downloaded the > 4.7-RELEASE-p1 sources, and built a custom kernel. Again no problems. > > I have done a fresh cvsup of my ports tree as of today, 11/12/02. > However when attempting to install webmin via portupgrade, I get the > following error: > > ===> Verifying reinstall for > /usr/local/lib/perl5/site_perl/5.005/alpha-freebsd/Net/SSLeay.pm in > /usr/ports/security/p5-Net-SSLeay > ===> Extracting for p5-Net-SSLeay-1.17 > >> Checksum OK for Net_SSLeay.pm-1.17.tar.gz. > ===> Patching for p5-Net-SSLeay-1.17 > ===> Configuring for p5-Net-SSLeay-1.17 > Checking for OpenSSL-0.9.6d or newer... > You have OpenSSL-0.9.6g installed in /usr > *** Could not figure out which C compiler was used to compile > /usr/bin/openssl. It is essentiall that OpenSSL, perl, and Net::SSLeay > are compiled with the same compiler and flags. Mixing and matching > compilers is not supported. at ./Makefile.PL line 132. > Checking if your kit is complete... > Looks good > Checking if your kit is complete... > Looks good > Writing Makefile for Net::SSLeay::Handle > Writing Makefile for Net::SSLeay > ===> Building for p5-Net-SSLeay-1.17 > Makefile out-of-date with respect to > /usr/libdata/perl/5.00503/mach/Config.pm > /usr/libdata/perl/5.00503/mach/CORE/config.h > Cleaning current config before rebuilding Makefile... > make -f Makefile.old clean > /dev/null 2>&1 || /bin/sh -c true > /usr/bin/perl5.00503 "-I/usr/libdata/perl/5.00503/mach" > "-I/usr/libdata/perl/5.00503" Makefile.PL "CC=cc" > "CCFLAGS=-O -pipe -mcpu=ev56" "PREFIX=/usr/local" > "INSTALLPRIVLIB=/usr/local/lib" "INSTALLARCHLIB=/usr/local/lib" > Checking for OpenSSL-0.9.6d or newer... > I could not find your OpenSSL in `CC=cc' > Please provide OpenSSL-0.9.6d installation directory (get from > http://www.openssl.org/ if you don't have it; please note that > SSLeay is no longer supported, see README) (C-c to abort): > > *** END OF OUTPUT *** > > and there it sits, waiting for me to tell it where OpenSSL lives. I > have check my system and found /usr/bin/openssl. It appears I have it > installed: > > zombie# /usr/bin/openssl version > OpenSSL 0.9.6g 9 Aug 2002 > > However, passing either '/usr/bin' or '/usr/bin/openssl' doesn't satisfy > the request. I've searched the web but found only one small thread that > didn't have a resolution. So far, other ports build fine. Any ideas? > > Thanks, > > Drew > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" 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 Thu Nov 14 18:39:10 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED35937B401 for ; Thu, 14 Nov 2002 18:39:09 -0800 (PST) Received: from yahoo.samart.co.th (tidkeaw.samart.co.th [203.149.0.14]) by mx1.FreeBSD.org (Postfix) with SMTP id 1A0BE43E6E for ; Thu, 14 Nov 2002 18:39:09 -0800 (PST) (envelope-from iddi@hotmail.com) Received: (qmail 20578 invoked from network); 15 Nov 2002 02:47:09 -0000 Received: from unknown (HELO ardency.samart.co.th) ([10.0.0.11]) (envelope-sender ) by 10.0.0.22 (qmail-ldap-1.03) with SMTP for ; 15 Nov 2002 02:47:09 -0000 Received: (qmail 18822 invoked from network); 15 Nov 2002 02:48:17 -0000 Received: from unknown (HELO yahoo.samart.co.th) ([203.149.32.130]) (envelope-sender ) by yahoo.samart.co.th (qmail-ldap-1.03) with SMTP for ; 15 Nov 2002 02:48:17 -0000 Message-Id: <1037327940.477@samart.co.th> Date: Fri, 15 Nov 2002 09:39:00 0700 To: freebsd-alpha@FreeBSD.org From: "getrich" Subject: มีของดีมาบอก.... MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII"; format=flowed Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Part-Time Job!! สำหรับนักเรียน นักศึกษา และผู้ทำงานประจำ คุณต้องการงานแบบนี้บ้างไหม…?? -งาน parttime ทำงานที่บ้านได้ ถ้าคุณใช้ Internet เป็น -ทำงานเพียงวันละ 2-3 ชม. -รายได้ 5,000 – 15,000 บาท ถ้าคุณเป็นคนหนึ่งที่ทำงานประจำหรือยังไม่มีงานทำ นักศึกษาที่กำลังศึกษาอยู่ ผู้ว่างงาน หรือผู้ที่ยังพอมีเวลาว่างจากงานประจำ มีคุณสมบัติเบื้องต้นดังนี้ 1. มีทัศนคติที่ดี 2. พร้อมที่จะเรียนรู้ เนื่องจากเป็นระบบใหม่จึงต้องให้มีการอบรมให้ตามความเหมาะสม 3. ต้องการที่จะทำงานอย่างจริงจัง อยากที่จะเปลี่ยนฐานะทางการเงินของตนเอง และอยากมีรายได้จากการทำงานตรงนี้จริงๆ ทุกอย่างเป็นไปได้ ใน สนใจรับข้อมูลเพิ่มเติมฟรี ได้ที่ http://ejobthailand.net/getrich อย่า !…………….. เป็นแค่เพียงคนที่นั่งรอโอกาส To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 14 20:48:51 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A6C937B401 for ; Thu, 14 Nov 2002 20:48:50 -0800 (PST) Received: from mta04.mail.mel.aone.net.au (mta04.mail.au.uu.net [203.2.192.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18C4E43E75 for ; Thu, 14 Nov 2002 20:48:49 -0800 (PST) (envelope-from rbyrnes@ozemail.com.au) Received: from ausyddtp0050.ozemail.com.au ([203.166.67.234]) by mta04.mail.mel.aone.net.au with ESMTP id <20021115044837.TETH22483.mta04.mail.mel.aone.net.au@ausyddtp0050.ozemail.com.au>; Fri, 15 Nov 2002 15:48:37 +1100 Message-Id: <5.1.1.6.0.20021115154657.00a8aa30@pop.ozemail.com.au> X-Sender: rbyrnes@pop.ozemail.com.au X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Fri, 15 Nov 2002 15:48:25 +1100 To: Wartan Hachaturow From: Rob B Subject: Re: Any TODO out there? Cc: freebsd-alpha@freebsd.org In-Reply-To: <20021113122755.GA5995@mojo.tepkom.ru> References: <3DD22648.35D7B3DE@mindspring.com> <20021113085124.GA23125@mojo.tepkom.ru> <3DD22648.35D7B3DE@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At 15:27 13/11/2002 +0300, Wartan Hachaturow sent this up the stick: >On Wed, Nov 13, 2002 at 02:15:36AM -0800, Terry Lambert wrote: > >BTW, I tried searching PR database on "Alpha" section, and found only >one PR with patch attached. Are there any other bug databases? >(I'm unfortunately not that familar with FreeBSD development process -- >I'm a Debian developer, just decided to help the "Other OS I Like and >Use" :) Cool!! It would be interesting to see what it is about both OSen (on Alpha) that you like/dislike. I use both Debian and FreeBSD on Alpha as well. cheers, Rob -- Duct tape is like the Force. It has a light side and a dark side, and it binds the universe together. This is random quote 466 of a collection of 1255 Distance from the centre of the brewing universe: [15200.8 km (8207.8 mi), 262.8 deg](Apparent) Rennerian Public Key fingerprint = 6219 33BD A37B 368D 29F5 19FB 945D C4D7 1F66 D9C5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Nov 15 8:51:19 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94C8737B401 for ; Fri, 15 Nov 2002 08:51:16 -0800 (PST) Received: from mail.hiwaay.net (fly.hiwaay.net [216.180.54.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id C596A43E4A for ; Fri, 15 Nov 2002 08:51:15 -0800 (PST) (envelope-from kdunn@hiwaay.net) Received: from mail.hiwaay.net (localhost [127.0.0.1]) by mail.hiwaay.net (8.12.5/8.12.5) with ESMTP id gAFGp9nO331177; Fri, 15 Nov 2002 10:51:10 -0600 (CST) Received: from localhost (kdunn@localhost) by mail.hiwaay.net (8.12.5/8.12.5/flySubmit) with ESMTP id gAFGp9BD375618; Fri, 15 Nov 2002 10:51:09 -0600 (CST) X-Authentication-Warning: fly.hiwaay.net: kdunn owned process doing -bs Date: Fri, 15 Nov 2002 10:51:09 -0600 (CST) From: "Karl L. Dunn" Reply-To: Karl Dunn To: Terry Lambert Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Multia: syscons does not find PCI vga card In-Reply-To: <3DD2FD05.882412E3@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I put the following fix in, rebuilt the GENERIC kernel (on this Multia that takes about four hours), and booted it. dmesg (verbose boot) comes out the same as before, that is, the vga card probe fails. A diff between the previous dmesg and the present one shows only the build date stuff. I realize there aren't many folks trying to get a Multia to run FreeBSD with X, but there must be some. I want to continue to hack this by proxy (I'm new to kernel stuff myself), and could use any more hints you can think of. BTW - how do I get X to run without syscons, once we get the vga to work? Or do we actually have to have syscons, and a successful setup of the S3 vga is a step in that direction? It seems to me that X has to have a working console. ======================================================================== --- vga.c.org Sat Aug 11 02:58:44 2001 +++ vga.c Thu Nov 14 14:50:23 2002 @@ -25,12 +25,13 @@ * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. * * $FreeBSD: src/sys/dev/fb/vga.c,v 1.9.2.1 2001/08/11 02:58:44 yokota Exp $ */ + /* Fix PCI vga probe failure per Terry Lambert msg 2002/Nov/13 -- KLD */ #include "opt_vga.h" #include "opt_fb.h" #include "opt_syscons.h" /* should be removed in the future, XXX */ #include @@ -924,13 +925,15 @@ #if !defined(VGA_NO_BIOS) && !defined(VGA_NO_MODE_CHANGE) u_char *mp; #endif int i; /* do this test only once */ - if (vga_init_done) + /* Fix PCI vga probe failure per Terry Lambert msg 2002/Nov/13 -- KLD */ + /* if (vga_init_done) */ + if (vga_init_done && (biosadapters > 0)) return biosadapters; vga_init_done = TRUE; /* * Locate display adapters. * The AT architecture supports upto two adapters. `syscons' allows ======================================================================== -- Karl Dunn k.l.dunn@ieee.org On Wed, 13 Nov 2002, Terry Lambert wrote: > "Karl L. Dunn" wrote: > > I have a Multia/UDB (alpha) to which I added a Diamond VGA card in the > > internal PCI slot. This has a S3 Trio64V+ chip. The intent is to be able > > to run X over FreeBSD 4.6.2. > [ ... ] > > The problem is that syscons can't find the S3 VGA (see the verbose dmesg > > output below). Maybe this is related to what the SRM leaves behind, but I > > doubt it. The kernel here is the GENERIC that came on the 4.6.2 CD I got > > from the BSD mall. > [ ... ] > > pci0: (vendor=0x5333, dev=0x8811) at 12.0 irq 15 > [ ... ] > > sc0: no video adapter found. > > sc0: failed to probe on isa0 > > OK. Probably it's because the syscons code forces vid_register() > in the case that it's possible to use it as a console, and that > calls probe_adapters(), which ends up returning noting, because > the PCI bus hasn't been probed yet, and there's no BIOS knowledge > of an adapter. Basically, this means that "vga_init_done" is true, > and so it doesn't get reprobed later. > > The fix is to make the syscons driver inelegible as a console > device, which should avoid the early probe, at which point the > later probe should find it successfully, since it doesn't have > a failed probe that won't be repeated. > > Alternately, you can hack probe_agapters() in /sys/dev/fb/vga.c: > > #if !defined(VGS_NO_BIOS) > /* do this test only once */ > if (vga_init_done) > return biosadapters; > #endif > > and this will probably work for your case, but is not something > that can be committed because it would screw up part of the time. > > If you want a permanent fix, you'll want to only set vgs_init_done > to TRUE in the case that it's found. This *might* work satisfactorily > (it doesn't puke out my x86 box): > > /* do this test only once */ > if (vga_init_done && biosadapters > 0) > return biosadapters; > > ...it causes the probe to repeat, even if it was attempted previously, > so long as it failed previously. IT's ugly, but if you have no console, > you probably don't care. > > Really, the console code wants to be able to be attached at any > point in the boot process, so that your console messages end up > going to "the no place", until the console is attached to syscons. > > That's a lot of work, and it would be very hard to get past an > x86-centric commit review, so I don't recommend it. > > -- Terry > > 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 Sat Nov 16 2:28:31 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E98AF37B401 for ; Sat, 16 Nov 2002 02:28:30 -0800 (PST) Received: from postino.fi.infn.it (postino.fi.infn.it [192.84.145.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8009943E4A for ; Sat, 16 Nov 2002 02:28:29 -0800 (PST) (envelope-from Riccardo.Veraldi@fi.infn.it) Received: from dijkstra.fi.infn.it (dijkstra.fi.infn.it [192.84.145.13]) by postino.fi.infn.it (8.12.6/8.12.6) with ESMTP id gAGAS7m3037388 for ; Sat, 16 Nov 2002 11:28:08 +0100 (CET) Received: by dijkstra.fi.infn.it (Postfix, from userid 1000) id CC4A836D81; Sat, 16 Nov 2002 11:28:06 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by dijkstra.fi.infn.it (Postfix) with ESMTP id A15C730C01 for ; Sat, 16 Nov 2002 11:28:06 +0100 (CET) Date: Sat, 16 Nov 2002 11:28:06 +0100 (CET) From: Riccardo.Veraldi@fi.infn.it X-X-Sender: fddi@dijkstra.fi.infn.it To: freebsd-alpha@FreeBSD.ORG Subject: processorcorrectable error Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-RAVMilter-Version: 8.4.1(snapshot 20020920) (postino.fi.infn.it) X-Spam-Status: No, hits=-99.5 required=6.5 tests=NO_REAL_NAME,USER_IN_WHITELIST version=2.31 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Warning: received processor correctable error I have FreeBSD-4.7 STABLE on a DPW 500a. I receive this kind of herror about once every 4 or 5 months... is it normal? what is it? memory parity error, bcache errors??? thanks Rick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Nov 16 9:33:31 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45E8E37B401; Sat, 16 Nov 2002 09:33:30 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F8BE43E77; Sat, 16 Nov 2002 09:33:29 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.6/8.12.5) with SMTP id gAGHXRBF054602; Sat, 16 Nov 2002 12:33:27 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sat, 16 Nov 2002 12:33:27 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Daniel Eischen Cc: alpha@FreeBSD.org, sparc@FreeBSD.org Subject: Re: [PATCH] *context() as syscalls In-Reply-To: <3DD2A3AD.D6ECFD0@vigrid.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 13 Nov 2002, Daniel Eischen wrote: > For sparc, ia64, and powerpc, I just returned ENOSYS for now. It > shouldn't break any builds and can be implemented later. Do you have a schedule for implementing these interfaces on sparc64? Having libc_r and libpthread working on sparc64 would be a Very Good Thing for 5.0. Do you need access to sparc64 hardware to do proper testing of the libc_r on that platform? That can probably be arranged pretty easily (either remote access, or if you drop e-mail to donations@, real access). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Nov 16 12:22:36 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E313F37B401 for ; Sat, 16 Nov 2002 12:22:34 -0800 (PST) Received: from mail.hiwaay.net (fly.hiwaay.net [216.180.54.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EAD343E4A for ; Sat, 16 Nov 2002 12:22:34 -0800 (PST) (envelope-from kdunn@hiwaay.net) Received: from mail.hiwaay.net (localhost [127.0.0.1]) by mail.hiwaay.net (8.12.5/8.12.5) with ESMTP id gAGKMRnO225145; Sat, 16 Nov 2002 14:22:27 -0600 (CST) Received: from localhost (kdunn@localhost) by mail.hiwaay.net (8.12.5/8.12.5/flySubmit) with ESMTP id gAGKMQ08209865; Sat, 16 Nov 2002 14:22:27 -0600 (CST) X-Authentication-Warning: fly.hiwaay.net: kdunn owned process doing -bs Date: Sat, 16 Nov 2002 14:22:26 -0600 (CST) From: "Karl L. Dunn" Reply-To: Karl Dunn To: Wilko Bulte Cc: Terry Lambert , Subject: Re: Multia: syscons does not find PCI vga card In-Reply-To: <20021113232834.A9924@freebie.xs4all.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I got the newer SRM load you pointed out, loaded it, and it finds the PCI video card! As soon as the SRM displays on the TGA video, the PCI video shows a blue screen with a cursor. The PCI video sttays that way until FreeBSD boots (the kernel is entered by the SRM boot command), at which point the TGA video stays as is, and the kernel displays messages and eventually a login prompt, with a working virtual terminal syscons. The kernel with the fix Terry Lambert suggested hangs with no messages displayed, and both monitors go blank. The new SRM boots the GENERIC 4.6.2 kernel as above. Thanks for all your help. In summary, 4.6.2 alpha will run a syscons on at least a S3 Trio64 PCI card, if you get the new SRM you suggested. -- Karl Dunn k.l.dunn@ieee.org On Wed, 13 Nov 2002, Wilko Bulte wrote: > On Wed, Nov 13, 2002 at 01:08:08PM -0600, Karl L. Dunn wrote: > > I have a Multia/UDB (alpha) to which I added a Diamond VGA card in the > > internal PCI slot. This has a S3 Trio64V+ chip. The intent is to be able > > to run X over FreeBSD 4.6.2. > > > > Linux RH6.0 (boot from the ARC of course) works OK with the S3 card > > (XF86_S3), and it worked OK with the internal TGA card (XF86_TGA). But > > it's Linux, and I'd much rather have FreeBSD. > > > > The SRM talks only to the TGA. I don't care about that -- I can set it to > > autoboot and move the monitor to the S3 VGA and forget about it unless I > > want to see it again someday. > > > > The problem is that syscons can't find the S3 VGA (see the verbose dmesg > > output below). Maybe this is related to what the SRM leaves behind, but I > > doubt it. The kernel here is the GENERIC that came on the 4.6.2 CD I got > > from the BSD mall. > > > > Can anybody give me some help here? > > You might want to try the very latest SRM for the Multia. I found it > on a DEC-internal server, it was never officiall released but it worked > great on my own Multias (I don't own those anymore). > > You can find it at: > > ftp://ftp.tcja.nl/pub/wilko/alpha/ > > It seems the VGA card is not initialised correctly or somesuch. I don't > recall if I ever had a S3 card in my Multias. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message