From owner-freebsd-alpha Sun Apr 29 4:21:50 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from switch2.switchpwr.com (switch1.switchpwr.com [12.14.48.19]) by hub.freebsd.org (Postfix) with ESMTP id 6DBE037B424 for ; Sun, 29 Apr 2001 04:21:40 -0700 (PDT) (envelope-from mel@switchpwr.com) Received: from switchpwr.com (switch4.switchpwr.com [12.14.48.22]) by switch2.switchpwr.com (8.11.0/8.11.0) with ESMTP id f3TBCND09553 for ; Sun, 29 Apr 2001 07:12:24 -0400 (EDT) Message-ID: <3AEBF742.4728CE21@switchpwr.com> Date: Sun, 29 Apr 2001 11:13:06 +0000 From: mel kravitz Organization: switching power inc X-Mailer: Mozilla 4.77 [en] (X11; U; NetBSD 1.5U alpha) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-alpha@freebsd.org Subject: kernel: warning message Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have been receiving the following /var/log/message, twice a week for the last two weeks, anytjing to worry about? This is on a UP1000, running 4.2 release. > 'warning: received processor correctable error.' machine has been up and running for 53+ days. -Mel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Apr 29 8:46:37 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from iona.dcs.gla.ac.uk (iona.dcs.gla.ac.uk [130.209.240.35]) by hub.freebsd.org (Postfix) with ESMTP id 6ABEE37B422 for ; Sun, 29 Apr 2001 08:46:34 -0700 (PDT) (envelope-from neugebar@dcs.gla.ac.uk) Received: from therese.dcs.gla.ac.uk ([130.209.241.134] helo=therese.dcs.gla.ac.uk.dcs.gla.ac.uk) by iona.dcs.gla.ac.uk with esmtp (Exim 3.13 #1) id 14ttP2-00004z-00 for freebsd-alpha@FreeBSD.ORG; Sun, 29 Apr 2001 16:46:28 +0100 Received: by therese.dcs.gla.ac.uk.dcs.gla.ac.uk (8.11.2/Dumb) id f3TFkQm10321; Sun, 29 Apr 2001 16:46:26 +0100 (BST) To: freebsd-alpha@FreeBSD.ORG Subject: determine cycle counter frequency in user space From: Rolf Neugebauer Date: 29 Apr 2001 16:46:24 +0100 Message-ID: Lines: 17 User-Agent: Gnus/5.0805 (Gnus v5.8.5) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I try to determine the cycle counter frequency from a user space program to do some accurate time counting. Ideally, I would like to access the rpb_cc_freq field Hardware Restart Parameter Block (rpb) as possible under OSF/1 using getsysinfo(2) or the calibrated cycles_per_sec variable from sys/alpha/alpha/machdep.c. While it would be easy to introduce a new sysctl or similar, I was wondering if there is already a 'standard' way under FreeBSD to access this information (ideally, also under ix86). I searched around a bit, but couldn't find any obvious way. Thanks Rolf To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Apr 29 16: 5: 0 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from tango.entreri.com (tango.entreri.com [205.219.158.250]) by hub.freebsd.org (Postfix) with ESMTP id 35D4837B422 for ; Sun, 29 Apr 2001 16:04:53 -0700 (PDT) (envelope-from dp@penix.org) Received: from penix.org (Toronto-ppp220856.sympatico.ca [64.228.103.181]) by tango.entreri.com (8.10.2/8.9.1) with ESMTP id f3T00PU16030; Sat, 28 Apr 2001 19:00:26 -0500 Message-ID: <3AEB5A2F.27657B1D@penix.org> Date: Sat, 28 Apr 2001 20:02:55 -0400 From: Paul Halliday X-Mailer: Mozilla 4.75 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm Cc: alpha@FreeBSD.ORG Subject: Re: FYI AlphaProcessor Inc's UP2000 w/ SMP works! References: <20010428202556.D6887380C@overcee.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Wemm wrote: > AlphaPC 264DP 833 MHz, 833MHz > 8192 byte page size, 2 processors. > real memory = 2144706560 (2094440K bytes) > avail memory = 2083627008 (2034792K bytes) Think you could have them loan it to me indefinately? :) > This box is a loaner from AlphaProcessor Inc. > > Cheers, > -Peter > -- > Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Apr 29 19:35:11 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from ns1.khmere.com (sdsl-216-36-70-194.dsl.sjc.megapath.net [216.36.70.194]) by hub.freebsd.org (Postfix) with ESMTP id B84A437B422 for ; Sun, 29 Apr 2001 19:35:09 -0700 (PDT) (envelope-from list@khmere.com) Received: from khmere.com (ns2.khmere.com [216.36.70.196]) by ns1.khmere.com (8.11.0/8.8.7) with ESMTP id f3U2Yx029704 for ; Sun, 29 Apr 2001 19:35:00 -0700 (PDT) Message-ID: <3AECCF5F.230B072E@khmere.com> Date: Sun, 29 Apr 2001 19:35:11 -0700 From: Nathan X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-alpha@freebsd.org Subject: Alphasever 800 SBC ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does FreeBSD support the Alphaserver 800 SBC ? If so can is there a special backplane that I need ? or can I use any backplane ? thanks ! -nb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Apr 30 1: 8: 8 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 0BE4F37B423 for ; Mon, 30 Apr 2001 01:08:06 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.22 #1) id 14u8iy-0000Eu-00; Mon, 30 Apr 2001 08:08:04 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.3/8.11.2) id f3TL47l33143; Sun, 29 Apr 2001 23:04:07 +0200 (CEST) (envelope-from wkb) Date: Sun, 29 Apr 2001 23:04:07 +0200 From: Wilko Bulte To: Nick Evans Cc: "'Andrew Gallatin'" , freebsd-alpha@freebsd.org Subject: Re: UP1500 motherboard support? Message-ID: <20010429230407.B33095@freebie.demon.nl> References: <712384017032D411AD7B0001023D799BDB9B6F@sn1exchmbx.nextvenue.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <712384017032D411AD7B0001023D799BDB9B6F@sn1exchmbx.nextvenue.com>; from nevans@ibeam.com on Wed, Apr 18, 2001 at 03:07:58PM -0400 X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Apr 18, 2001 at 03:07:58PM -0400, Nick Evans wrote: > > Do you know if anybody is selling these? > > On that note, does anyone know where I can easily buy OEM Alpha components? > I want to build a system from scratch getting the components as I get the > money. I've followed tons of links but can't seem to find a place that will > just sell me say the motherboard or a CPU. This appears to be a pain. I have multiple EV6 CPUs sitting here, but no mainboard to plug 'm into :-((( If you discover a place selling empty 21264 MBs I'd be interested (given a sensible pricing of course) W/ -- | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org |/|/ / / /( (_) Bulte Powered by FreeBSD/alpha 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 Apr 30 14:47:16 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 6142237B61A for ; Mon, 30 Apr 2001 14:47:11 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id OAA15921; Mon, 30 Apr 2001 14:47:09 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp03.primenet.com, id smtpdAAAtBaOdF; Mon Apr 30 14:47:01 2001 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id OAA12404; Mon, 30 Apr 2001 14:47:53 -0700 (MST) From: Terry Lambert Message-Id: <200104302147.OAA12404@usr01.primenet.com> Subject: Re: determine cycle counter frequency in user space To: neugebar@dcs.gla.ac.uk (Rolf Neugebauer) Date: Mon, 30 Apr 2001 21:47:48 +0000 (GMT) Cc: freebsd-alpha@FreeBSD.ORG In-Reply-To: from "Rolf Neugebauer" at Apr 29, 2001 04:46:24 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I try to determine the cycle counter frequency from a user space > program to do some accurate time counting. Ideally, I would like to > access the rpb_cc_freq field Hardware Restart Parameter Block (rpb) as > possible under OSF/1 using getsysinfo(2) or the calibrated > cycles_per_sec variable from sys/alpha/alpha/machdep.c. > > While it would be easy to introduce a new sysctl or similar, I was > wondering if there is already a 'standard' way under FreeBSD to access > this information (ideally, also under ix86). > > I searched around a bit, but couldn't find any obvious way. The closest you will find is hw.cpu_mhz, via sysctl. I am personally not very happy at all with what has happened to the clock code; what used to be a direct reference to "curtime" is now a convoluted mess requiring a dead chicken and some pagan incantations to achieve the same thing, at the same time making gettimeofday() inordinately expensive. It also bothers me that the standard system clock doesn't use the cycle counter, and instead is rn of the i8254 interrupt, which bothers me no end. If you could get a baseline and a frequency in user space, it would be very easy to implement gettimeofday() in user space, if things were not so strange. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Apr 30 14:53:22 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 724F237B43C for ; Mon, 30 Apr 2001 14:53:15 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f3ULvvv02259; Mon, 30 Apr 2001 14:57:57 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200104302157.f3ULvvv02259@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Terry Lambert Cc: neugebar@dcs.gla.ac.uk (Rolf Neugebauer), freebsd-alpha@FreeBSD.ORG Subject: Re: determine cycle counter frequency in user space In-reply-to: Your message of "Mon, 30 Apr 2001 21:47:48 -0000." <200104302147.OAA12404@usr01.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 30 Apr 2001 14:57:57 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I am personally not very happy at all with what has happened to > the clock code; what used to be a direct reference to "curtime" > is now a convoluted mess requiring a dead chicken and some pagan > incantations to achieve the same thing, at the same time making > gettimeofday() inordinately expensive. Use time_second for coarse timing requirements. > It also bothers me that the standard system clock doesn't use the > cycle counter, and instead is rn of the i8254 interrupt, which > bothers me no end. The cycle counter can't be relied on. Get this through your thick head. The clock frequency on many Alpha systems is unstable, and on most PCs, it can change out from under you with no warning. > If you could get a baseline and a frequency in user space, it would > be very easy to implement gettimeofday() in user space, if things > were not so strange. Hardware sucks; what can I say? You can't do this usefully in userspace; stop trying and go buy some real timing hardware if you actually care. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue May 1 2: 7:57 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from barry.mail.mindspring.net (barry.mail.mindspring.net [207.69.200.25]) by hub.freebsd.org (Postfix) with ESMTP id 1F08737B422; Tue, 1 May 2001 02:07:55 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (pool0731.cvx21-bradley.dialup.earthlink.net [209.179.194.221]) by barry.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id FAA02289; Tue, 1 May 2001 05:07:49 -0400 (EDT) Message-ID: <3AEE7CF7.69D87D5F@mindspring.com> Date: Tue, 01 May 2001 02:08:07 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: Terry Lambert , Rolf Neugebauer , freebsd-alpha@FreeBSD.ORG Subject: Re: determine cycle counter frequency in user space References: <200104302157.f3ULvvv02259@mass.dis.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith wrote: > Use time_second for coarse timing requirements. [ ... ] > The cycle counter can't be relied on. Get this through your > thick head. The clock frequency on many Alpha systems is > unstable, and on most PCs, it can change out from under you > with no warning. [ ... ] > Hardware sucks; what can I say? You can't do this usefully > in userspace; stop trying and go buy some real timing hardware > if you actually care. Sorry; I didn't get this message in time. Unfortunately, my code is now working with ~90uS accuracy, +/- 90uS. I'll try to be more dilligent in keeping up with my email from now on... ;-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue May 1 2:56:42 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from iona.dcs.gla.ac.uk (iona.dcs.gla.ac.uk [130.209.240.35]) by hub.freebsd.org (Postfix) with ESMTP id 1559C37B423 for ; Tue, 1 May 2001 02:56:31 -0700 (PDT) (envelope-from neugebar@dcs.gla.ac.uk) Received: from therese.dcs.gla.ac.uk ([130.209.241.134] helo=therese.dcs.gla.ac.uk.dcs.gla.ac.uk) by iona.dcs.gla.ac.uk with esmtp (Exim 3.13 #1) id 14uWtS-0005wA-00 for freebsd-alpha@FreeBSD.ORG; Tue, 01 May 2001 10:56:30 +0100 Received: by therese.dcs.gla.ac.uk.dcs.gla.ac.uk (8.11.2/Dumb) id f419uRQ86712; Tue, 1 May 2001 10:56:28 +0100 (BST) To: freebsd-alpha@FreeBSD.ORG Subject: Re: determine cycle counter frequency in user space References: <200104302147.OAA12404@usr01.primenet.com> From: Rolf Neugebauer Date: 01 May 2001 10:56:27 +0100 In-Reply-To: Terry Lambert's message of "Mon, 30 Apr 2001 21:47:48 +0000 (GMT)" Message-ID: Lines: 35 User-Agent: Gnus/5.0805 (Gnus v5.8.5) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Terry Lambert writes: > > I try to determine the cycle counter frequency from a user space > > program to do some accurate time counting. Ideally, I would like to > > access the rpb_cc_freq field Hardware Restart Parameter Block (rpb) as > > possible under OSF/1 using getsysinfo(2) or the calibrated > > cycles_per_sec variable from sys/alpha/alpha/machdep.c. > > > > While it would be easy to introduce a new sysctl or similar, I was > > wondering if there is already a 'standard' way under FreeBSD to access > > this information (ideally, also under ix86). > > > > I searched around a bit, but couldn't find any obvious way. > > The closest you will find is hw.cpu_mhz, via sysctl. Not on my 4.2-STABLE, late February vintage. I could parse hw.model, but that reports 533MHz, while dmesg reports 531MHz. In a followup, Mike mentioned fluctuations of clock frequency. Any idea, by how much this fluctuation can be? percentage of MHz, kHz? In general, I am not too fussed about these fluctuations, as I can take some fine grained samples using cycle counters together with more coarse grained once obtained from gettimeofday(). However, to get an estimate for cycles per second, I was looking for a programmatic way to access above mentioned variables instead of providing them as command line arguments. I'll just add an appropriate sysctl to get cycles_per_sec. If people are interested, I'll submit a patch. Thanks Rolf To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue May 1 8:18:30 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 8EC2A37B422 for ; Tue, 1 May 2001 08:18:25 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA12278; Tue, 1 May 2001 11:18:24 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f41FHsf58190; Tue, 1 May 2001 11:17:54 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15086.54178.150721.633298@grasshopper.cs.duke.edu> Date: Tue, 1 May 2001 11:17:54 -0400 (EDT) To: Rolf Neugebauer Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: determine cycle counter frequency in user space In-Reply-To: References: <200104302147.OAA12404@usr01.primenet.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Rolf Neugebauer writes: > > However, to get an estimate for cycles per second, I was looking for a > programmatic way to access above mentioned variables instead of > providing them as command line arguments. I'll just add an appropriate > sysctl to get cycles_per_sec. If people are interested, I'll submit a > patch. Depending on how accurate you needed them to be, you might be able to just calculate them. __inline int GetClockCycleFreq(void) { unsigned long t0, t1; int delta_t = -1; do { /* loop to avoid nasty negative cycle counts.. */ t0 = alpha_rpcc(); sleep(1); t1 = alpha_rpcc(); delta_t = t1 - t0; } while (delta_t < 0); return(delta_t); } Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue May 1 8:31:59 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id D9EA537B424 for ; Tue, 1 May 2001 08:31:55 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA12513; Tue, 1 May 2001 11:31:54 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f41FVO958219; Tue, 1 May 2001 11:31:24 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15086.54988.462602.169129@grasshopper.cs.duke.edu> Date: Tue, 1 May 2001 11:31:24 -0400 (EDT) To: Nathan Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Alphasever 800 SBC ? In-Reply-To: <3AECCF5F.230B072E@khmere.com> References: <3AECCF5F.230B072E@khmere.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nathan writes: > Does FreeBSD support the Alphaserver 800 SBC ? > > If so can is there a special backplane that I need ? or can I use any > backplane ? > > thanks ! > > -nb > No, I don't think we support any of the SBC machines. You might want to check NetBSD or Linux, but I think that Tru64 may be your only option. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue May 1 10:57:31 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id 123C937B424 for ; Tue, 1 May 2001 10:57:26 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id KAA11894; Tue, 1 May 2001 10:57:23 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp05.primenet.com, id smtpdAAAk7ainx; Tue May 1 10:57:17 2001 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id KAA17133; Tue, 1 May 2001 10:58:13 -0700 (MST) From: Terry Lambert Message-Id: <200105011758.KAA17133@usr01.primenet.com> Subject: Re: determine cycle counter frequency in user space To: neugebar@dcs.gla.ac.uk (Rolf Neugebauer) Date: Tue, 1 May 2001 17:57:42 +0000 (GMT) Cc: freebsd-alpha@FreeBSD.ORG In-Reply-To: from "Rolf Neugebauer" at May 01, 2001 10:56:27 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > The closest you will find is hw.cpu_mhz, via sysctl. > > Not on my 4.2-STABLE, late February vintage. I could parse > hw.model, but that reports 533MHz, while dmesg reports 531MHz. > > In a followup, Mike mentioned fluctuations of clock frequency. Any > idea, by how much this fluctuation can be? percentage of MHz, kHz? > > In general, I am not too fussed about these fluctuations, as I can > take some fine grained samples using cycle counters together with more > coarse grained once obtained from gettimeofday(). > > However, to get an estimate for cycles per second, I was looking for a > programmatic way to access above mentioned variables instead of > providing them as command line arguments. I'll just add an appropriate > sysctl to get cycles_per_sec. If people are interested, I'll submit a > patch. It's unlikely that you will be able to do what you want the way you want to do it. In particular, it's possible for your program to be context switched in the middle of your calculation, or for the system to take interrupts, etc., wihch will result in serious skew of your numbers. When I did this task, I cheated tremendously. Minimally, you will require periodic resynchornization with the kernel drift information stored in timer structure. You should see /sys/i386/isa/clock.c and the timer code in the file /sys/kern/kern_time.c. Tracking through this code is actually pretty miserable, since it uses the aforementioned structure as a template, so there's no global place you can go to retrieve the syncronization data in the kernel, since it's hidden on the other side of a pointer. I wish this code were better documented as to its intended function. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue May 1 11:36:45 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 991F137B424 for ; Tue, 1 May 2001 11:36:32 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f41IaNG08252; Tue, 1 May 2001 11:36:23 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200105011758.KAA17133@usr01.primenet.com> Date: Tue, 01 May 2001 11:35:39 -0700 (PDT) From: John Baldwin To: Terry Lambert Subject: Re: determine cycle counter frequency in user space Cc: freebsd-alpha@FreeBSD.org, (Rolf Neugebauer) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 01-May-01 Terry Lambert wrote: > Minimally, you will require periodic resynchornization with > the kernel drift information stored in timer structure. You > should see /sys/i386/isa/clock.c and the timer code in the > file /sys/kern/kern_time.c. You have _got_ to be kidding me Terry. This is freebsd-_alpha_@FreeBSD.org. /sys/i386/anything isn't very relevant here. :) /sys/alpha would be a better place to investigate. Using microtime or microuptime in the kernel in a critical section (or at splhigh for 4.x I would guess) in conjuction with each rpcc would be perfectly sufficient: struct timeval *start_tv, end_tv; register_t start_cc, end_cc; critical_t s; s = critical_enter(); microuptime(&start_tv); start_cc = alpha_rpcc(); critical_exit(s); tsleep(&foo, PUSER, "ccsec", 10); s = critical_enter(); microuptime(&end_tv); end_cc = alpha_rpcc(); critical_exit(s); /* do calculations here */ There is still the problem on an SMP system that you may spin on a lock in microuptime() while talking to the i8254. Also, I probably fubb'd the priority to tsleep(), and some different timeouts might be more optimal. To be truly pedantic, one could make the clock lock allow recursion and do something along these lines: mtx_lock_spin(&sclock_lock); microuptime(&start_tv); start_cc = alpha_rpcc(); for (count = 0; count < 1000000000; count ++) ; /* nothing */ microuptime(&end_tv); end_cc = alpha_rpcc(); mtx_unlock_spin(&clock_lock); /* do calculations here */ (In -current of course, in -stable splhigh() instead of the mutex ops would probably work as well.) This isn't cheap though. :) -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue May 1 12: 4:58 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id 9FDE237B43C; Tue, 1 May 2001 12:04:54 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id MAA25234; Tue, 1 May 2001 12:04:42 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp05.primenet.com, id smtpdAAA88aarX; Tue May 1 12:04:40 2001 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id MAA05338; Tue, 1 May 2001 12:08:48 -0700 (MST) From: Terry Lambert Message-Id: <200105011908.MAA05338@usr06.primenet.com> Subject: Re: determine cycle counter frequency in user space To: jhb@FreeBSD.ORG (John Baldwin) Date: Tue, 1 May 2001 19:08:48 +0000 (GMT) Cc: tlambert@primenet.com (Terry Lambert), freebsd-alpha@FreeBSD.ORG, neugebar@dcs.gla.ac.uk ((Rolf Neugebauer)) In-Reply-To: from "John Baldwin" at May 01, 2001 11:35:39 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Minimally, you will require periodic resynchornization with > > the kernel drift information stored in timer structure. You > > should see /sys/i386/isa/clock.c and the timer code in the > > file /sys/kern/kern_time.c. > > You have _got_ to be kidding me Terry. This is freebsd-_alpha_@FreeBSD.org. > /sys/i386/anything isn't very relevant here. :) /sys/alpha would be a better > place to investigate. Using microtime or microuptime in the kernel in a > critical section (or at splhigh for 4.x I would guess) in conjuction with each > rpcc would be perfectly sufficient: Sorry; mixesdup my platforms. I have to salute you: I found the timecounter code singularly opaque. > There is still the problem on an SMP system that you may spin on > a lock in microuptime() while talking to the i8254. Also, I > probably fubb'd the priority to tsleep(), and some different > timeouts might be more optimal. To be truly pedantic, one could > make the clock lock allow recursion and do something along > these lines: ... probably overkill; IMO, you only really care about whichever processor you are running on. Too bad you can't synchornize the cycle counters on any hardware I'm aware of to date. 8-(. > (In -current of course, in -stable splhigh() instead of the mutex ops would > probably work as well.) > > This isn't cheap though. :) I think he probably wants what I wanted: a "gettimeofday()" that is "close enough for 1ms or better logging" and doesn't require call overhead. It's unfortunate that there's no "curtime" that could be abused to provide this... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue May 1 13: 4:38 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 323D937B422 for ; Tue, 1 May 2001 13:04:35 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f41K3eG10386; Tue, 1 May 2001 13:03:40 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200105011908.MAA05338@usr06.primenet.com> Date: Tue, 01 May 2001 13:02:57 -0700 (PDT) From: John Baldwin To: Terry Lambert Subject: Re: determine cycle counter frequency in user space Cc: ((Rolf Neugebauer)) , freebsd-alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 01-May-01 Terry Lambert wrote: >> There is still the problem on an SMP system that you may spin on >> a lock in microuptime() while talking to the i8254. Also, I >> probably fubb'd the priority to tsleep(), and some different >> timeouts might be more optimal. To be truly pedantic, one could >> make the clock lock allow recursion and do something along >> these lines: > > ... probably overkill; IMO, you only really care about whichever > processor you are running on. Too bad you can't synchornize the > cycle counters on any hardware I'm aware of to date. 8-(. It's not which processor I'm on that I care about. I want to minimize the error that would arise if the time between the micruptime() and alpha_rpcc() at the start is different from that between microuptime() and alpha_rpcc() at the end. Spinning on a lock or getting an interrupt in that time would increase the error. >> (In -current of course, in -stable splhigh() instead of the mutex ops would >> probably work as well.) >> >> This isn't cheap though. :) > > I think he probably wants what I wanted: a "gettimeofday()" that > is "close enough for 1ms or better logging" and doesn't require > call overhead. > > It's unfortunate that there's no "curtime" that could be abused > to provide this... getmicrotime(). It just reads the current time without dinking with the hardware. However, the original poster wanted the alpha-specific cycles_per_sec variable exported as a sysctl, not a new gettimeofday() call. If gettimeofday() really gets your panties in a bunch, you could change it to use getmicrotime() instead of microtime() at the risk of it becoming less accurate. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed May 2 4:10:54 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from postino.fi.infn.it (postino.fi.infn.it [192.84.145.9]) by hub.freebsd.org (Postfix) with ESMTP id 3A0F437B422 for ; Wed, 2 May 2001 04:10:52 -0700 (PDT) (envelope-from Riccardo.Veraldi@fi.infn.it) Received: from nikita.fi.infn.it (nikita.fi.infn.it [192.84.146.189]) by postino.fi.infn.it (8.11.1/8.11.1) with ESMTP id f42BAfm07982 for ; Wed, 2 May 2001 13:10:41 +0200 (CEST) From: Riccardo.Veraldi@fi.infn.it Received: by nikita.fi.infn.it (Postfix, from userid 1001) id 5194718CE9; Wed, 2 May 2001 13:10:40 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by nikita.fi.infn.it (Postfix) with ESMTP id 2092415919 for ; Wed, 2 May 2001 13:10:40 +0200 (CEST) Date: Wed, 2 May 2001 13:10:39 +0200 (CEST) X-X-Sender: To: Subject: vector: 0x670 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 670 Processor Uncorrectable unrecoverable cache or TLB errors, or read of a non-existent I/O space Do you think it can be an error due to overheating or do I have to throw my AlphaStation away ?? thanks Rick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed May 2 11:15:24 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id C841337B422 for ; Wed, 2 May 2001 11:15:18 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.9.3/8.9.3) id LAA28605; Wed, 2 May 2001 11:07:52 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpdAAAo8aO23; Wed May 2 11:07:45 2001 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id LAA29183; Wed, 2 May 2001 11:27:54 -0700 (MST) From: Terry Lambert Message-Id: <200105021827.LAA29183@usr02.primenet.com> Subject: Re: vector: 0x670 To: Riccardo.Veraldi@fi.infn.it Date: Wed, 2 May 2001 18:27:38 +0000 (GMT) Cc: freebsd-alpha@FreeBSD.ORG In-Reply-To: from "Riccardo.Veraldi@fi.infn.it" at May 02, 2001 01:10:39 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 670 Processor Uncorrectable unrecoverable cache or TLB errors, or > read of a non-existent I/O space > > > Do you think it can be an error due to overheating or do I have to throw > my AlphaStation away ?? No quick answers, but some things to try, and some advice and opinions... A cache error means that the processor is bad, if it's L1 cache; this could be the result of overheating. If it's L2 cache, the cause could still be overheating, but I've seen a lot of people trying to use cache chips that were too slow. - My guess is that it's _not_ a cache error. - If it's overheating, that's usually the result of overclocking, either intentionally, or unintentionally. Make sure you are not doing that. You might also be using memory which is too slow, or has fake parity instead of real parity (don't do that). Slow memory tends to become more of an issue when you stick in a lot of it, since the DMA refresh doesn't get around to each bank in time; this is particularly problematic if you are doing heavy I/O, so that the memory bus is latched for DMA, and refresh is thus delayed really long due to bus hold times; this is usually possible to adjust in the drivers or controller configurations and is often called "bus on" time. - I've occasionally loaded a machine with too much memory for it to reasonably handle refresh, given the memory bus speed and the bus-on time for some PCI controllers (I had an Adaptec that was a bus hog; when I loaded the disk subsystem with the extra amount of RAM, the refresh failed, and the system lost its mind). A TLB error means that the contents of a Translation Lookaside Buffer are incorrect. This could be a kernel bug. - If you are running -current, this one would be my bet; in particular, if you are trying to use SMP, it's nearly a certainty. Alternately, you are using a bad driver for a board you stuck in yourself which works on the x86, but hasn't been tested on the Alpha, and it's accessing non-existant I/O space, or the card itself is bad, and not responding to being addressed. - If I had to bet, I'd say you stuck a sound card in the thing, and it's choking (sound card drivers are notoriously fragile, so that's why that's my guess. The easiest things to do, in order of increasing difficulty: o Make sure you are running cold, and see if the problem occurs while cold; if it doesn't, cool it back down (e.g. leave it off in a cool room for a good long while), and then after booting, immediately put it under a stress load to determine if it's load over time that you are seeing the failure from, or if it's increased heat over time (it may be load that triggers it, but it looks like time because aggregate load over time is high, but instantaneous load is not). o Make sure you are not overclocking the CPU. o Yank all unnecessary cards, and see if you can repeat the problem. o Yank all unnecessary drivers from your config, rebuild a kernel, and try to repeat the problem. o Yank out as much memory as you can, and still be able to boot; if the problem still recurrs, swap the memory still in there for the memory you hanked out, and try again. o Yank out the L2 cache; it will be slow, but it should still be able to work. o Try a different brand of disk controller. o Use the same disk controller, after sticking it in an x86 and resetting its CMOS settings to the factory defaults using the BIOS setup utility. o Replace the CPU, on the theory that it's shot, or the L1 cache is fried on the thing. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed May 2 11:32:48 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 8283D37B424 for ; Wed, 2 May 2001 11:32:44 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.22 #1) id 14v1QZ-0003EL-00; Wed, 02 May 2001 18:32:43 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.3/8.11.2) id f42Ib6E01488; Wed, 2 May 2001 20:37:06 +0200 (CEST) (envelope-from wkb) Date: Wed, 2 May 2001 20:37:06 +0200 From: Wilko Bulte To: Terry Lambert Cc: Riccardo.Veraldi@fi.infn.it, freebsd-alpha@freebsd.org Subject: Re: vector: 0x670 Message-ID: <20010502203706.E1339@freebie.demon.nl> References: <200105021827.LAA29183@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200105021827.LAA29183@usr02.primenet.com>; from tlambert@primenet.com on Wed, May 02, 2001 at 06:27:38PM +0000 X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, May 02, 2001 at 06:27:38PM +0000, Terry Lambert wrote: > > 670 Processor Uncorrectable unrecoverable cache or TLB errors, or > > read of a non-existent I/O space > > > > > > Do you think it can be an error due to overheating or do I have to throw > > my AlphaStation away ?? > > No quick answers, but some things to try, and some advice and > opinions... > > > A cache error means that the processor is bad, if it's L1 cache; > this could be the result of overheating. If it's L2 cache, the > cause could still be overheating, but I've seen a lot of people > trying to use cache chips that were too slow. I don't recall which AS version this was, but most of the have SMD soldered on caches. Some have cache modules, some cache SIMMs. In case of cache modules of any shape or form please check if they are seated well. > - If it's overheating, that's usually the result of overclocking, > either intentionally, or unintentionally. Make sure you are not > doing that. Easily tested by trying if your fingers get fried when touching the heatsink. > You might also be using memory which is too slow, or has fake > parity instead of real parity (don't do that). Slow memory > tends to become more of an issue when you stick in a lot of it, > since the DMA refresh doesn't get around to each bank in time; > this is particularly problematic if you are doing heavy I/O, > so that the memory bus is latched for DMA, and refresh is thus > delayed really long due to bus hold times; this is usually > possible to adjust in the drivers or controller configurations > and is often called "bus on" time. *Very* unlikely. Alpha machines are built to really drive lots of memory. Not this whimpy PC stuff that drives only 4 SIMMs/DIMMs from a single ASIC. > - I've occasionally loaded a machine with too much memory for > it to reasonably handle refresh, given the memory bus speed > and the bus-on time for some PCI controllers (I had an Adaptec > that was a bus hog; when I loaded the disk subsystem with the > extra amount of RAM, the refresh failed, and the system lost > its mind). Again, unlikely. > A TLB error means that the contents of a Translation Lookaside > Buffer are incorrect. This could be a kernel bug. Or the CPU is dead/dying. Seen that before.. -- | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org |/|/ / / /( (_) Bulte Powered by FreeBSD/alpha 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 May 2 12:41:13 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from flounder.jimking.net (flounder.jimking.net [209.205.176.18]) by hub.freebsd.org (Postfix) with ESMTP id BD3F837B422 for ; Wed, 2 May 2001 12:41:11 -0700 (PDT) (envelope-from jim@jimking.net) Received: from jking (jking.lgc.com [134.132.76.82]) (authenticated) by flounder.jimking.net (8.11.3/8.11.2) with ESMTP id f42Jf9D06281 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO) for ; Wed, 2 May 2001 14:41:10 -0500 (CDT) (envelope-from jim@jimking.net) Message-ID: <006e01c0d33f$d6731300$524c8486@jking> From: "Jim King" To: Subject: PCMCIA Date: Wed, 2 May 2001 14:41:09 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2462.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Before I go chasing down too many dead ends, has anybody been successful using PCMCIA? My AS200 came with an ISA-PCMCIA adapter card. My first attempt at using it was unsuccessful - it looked the PCMCIA card's identifier was not able to be read. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed May 2 12:46: 2 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 7F6EA37B423 for ; Wed, 2 May 2001 12:45:58 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id PAA13757; Wed, 2 May 2001 15:45:56 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f42JjQj61579; Wed, 2 May 2001 15:45:26 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15088.25558.606765.29013@grasshopper.cs.duke.edu> Date: Wed, 2 May 2001 15:45:26 -0400 (EDT) To: "Jim King" Cc: Subject: Re: PCMCIA In-Reply-To: <006e01c0d33f$d6731300$524c8486@jking> References: <006e01c0d33f$d6731300$524c8486@jking> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jim King writes: > Before I go chasing down too many dead ends, has anybody been successful > using PCMCIA? My AS200 came with an ISA-PCMCIA adapter card. My first > attempt at using it was unsuccessful - it looked the PCMCIA card's > identifier was not able to be read. > > Jim I don't think anybody has tried PCMCIA on alpha or is working on it. I know NetBSD supports it.. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed May 2 13:28:30 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id DE57037B424 for ; Wed, 2 May 2001 13:28:18 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.22 #1) id 14v3EP-0008FN-00; Wed, 02 May 2001 20:28:17 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.3/8.11.2) id f42KWex02204; Wed, 2 May 2001 22:32:40 +0200 (CEST) (envelope-from wkb) Date: Wed, 2 May 2001 22:32:40 +0200 From: Wilko Bulte To: Andrew Gallatin Cc: Jim King , freebsd-alpha@freebsd.org Subject: Re: PCMCIA Message-ID: <20010502223240.A2190@freebie.demon.nl> References: <006e01c0d33f$d6731300$524c8486@jking> <15088.25558.606765.29013@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <15088.25558.606765.29013@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, May 02, 2001 at 03:45:26PM -0400 X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, May 02, 2001 at 03:45:26PM -0400, Andrew Gallatin wrote: > > Jim King writes: > > Before I go chasing down too many dead ends, has anybody been successful > > using PCMCIA? My AS200 came with an ISA-PCMCIA adapter card. My first > > attempt at using it was unsuccessful - it looked the PCMCIA card's > > identifier was not able to be read. > > > > Jim > > I don't think anybody has tried PCMCIA on alpha or is working on it. > > I know NetBSD supports it.. On Multia they support the builtin slots. I'm not sure about ISA-PCMCIA bridge cards. -- | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org |/|/ / / /( (_) Bulte Powered by FreeBSD/alpha 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 May 2 13:30:26 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 0BE7E37B446 for ; Wed, 2 May 2001 13:30:18 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id QAA15013; Wed, 2 May 2001 16:30:15 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f42KTj361697; Wed, 2 May 2001 16:29:45 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15088.28217.682317.833192@grasshopper.cs.duke.edu> Date: Wed, 2 May 2001 16:29:45 -0400 (EDT) To: Wilko Bulte Cc: Jim King , freebsd-alpha@FreeBSD.ORG Subject: Re: PCMCIA In-Reply-To: <20010502223240.A2190@freebie.demon.nl> References: <006e01c0d33f$d6731300$524c8486@jking> <15088.25558.606765.29013@grasshopper.cs.duke.edu> <20010502223240.A2190@freebie.demon.nl> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte writes: > On Wed, May 02, 2001 at 03:45:26PM -0400, Andrew Gallatin wrote: > > > > Jim King writes: > > > Before I go chasing down too many dead ends, has anybody been successful > > > using PCMCIA? My AS200 came with an ISA-PCMCIA adapter card. My first > > > attempt at using it was unsuccessful - it looked the PCMCIA card's > > > identifier was not able to be read. > > > > > > Jim > > > > I don't think anybody has tried PCMCIA on alpha or is working on it. > > > > I know NetBSD supports it.. > > On Multia they support the builtin slots. I'm not sure about ISA-PCMCIA > bridge cards. Actually, I could swear that they support those too. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed May 2 13:52: 3 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from tango.entreri.com (tango.entreri.com [205.219.158.250]) by hub.freebsd.org (Postfix) with ESMTP id 88CF337B422 for ; Wed, 2 May 2001 13:52:00 -0700 (PDT) (envelope-from dp@penix.org) Received: from penix.org (Toronto-ppp220710.sympatico.ca [64.228.103.35]) by tango.entreri.com (8.10.2/8.9.1) with ESMTP id f42Kp0x01583; Wed, 2 May 2001 15:51:01 -0500 Message-ID: <3AF0762F.1C4E1E@penix.org> Date: Wed, 02 May 2001 17:03:43 -0400 From: Paul Halliday X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Gallatin Cc: Wilko Bulte , Jim King , freebsd-alpha@FreeBSD.ORG Subject: Re: PCMCIA References: <006e01c0d33f$d6731300$524c8486@jking> <15088.25558.606765.29013@grasshopper.cs.duke.edu> <20010502223240.A2190@freebie.demon.nl> <15088.28217.682317.833192@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Gallatin wrote: > > Wilko Bulte writes: > > On Wed, May 02, 2001 at 03:45:26PM -0400, Andrew Gallatin wrote: > > > > > > Jim King writes: > > > > Before I go chasing down too many dead ends, has anybody been successful > > > > using PCMCIA? My AS200 came with an ISA-PCMCIA adapter card. My first > > > > attempt at using it was unsuccessful - it looked the PCMCIA card's > > > > identifier was not able to be read. > > > > > > > > Jim > > > > > > I don't think anybody has tried PCMCIA on alpha or is working on it. > > > > > > I know NetBSD supports it.. > > > > On Multia they support the builtin slots. I'm not sure about ISA-PCMCIA > > bridge cards. > > Actually, I could swear that they support those too. > Give me a half hour and I will fire the one that I have back into my as200 and verify. > Drew > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message -- Paul Halliday Carpenter, Electrician. http://dp.penix.org Rare earth magnets are pretty cool. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed May 2 14:25: 0 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 280F337B496 for ; Wed, 2 May 2001 14:24:56 -0700 (PDT) (envelope-from keichii@peorth.iteration.net) Received: by peorth.iteration.net (Postfix, from userid 1001) id E05C0595FF; Wed, 2 May 2001 16:24:54 -0500 (CDT) Date: Wed, 2 May 2001 16:24:54 -0500 From: "Michael C . Wu" To: Paul Halliday Cc: Andrew Gallatin , Wilko Bulte , Jim King , freebsd-alpha@FreeBSD.ORG Subject: Re: PCMCIA Message-ID: <20010502162454.A66203@peorth.iteration.net> Reply-To: "Michael C . Wu" Mail-Followup-To: "Michael C . Wu" , Paul Halliday , Andrew Gallatin , Wilko Bulte , Jim King , freebsd-alpha@FreeBSD.ORG References: <006e01c0d33f$d6731300$524c8486@jking> <15088.25558.606765.29013@grasshopper.cs.duke.edu> <20010502223240.A2190@freebie.demon.nl> <15088.28217.682317.833192@grasshopper.cs.duke.edu> <3AF0762F.1C4E1E@penix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AF0762F.1C4E1E@penix.org>; from dp@penix.org on Wed, May 02, 2001 at 05:03:43PM -0400 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, May 02, 2001 at 05:03:43PM -0400, Paul Halliday scribbled: | Andrew Gallatin wrote: | > Wilko Bulte writes: | > > On Wed, May 02, 2001 at 03:45:26PM -0400, Andrew Gallatin wrote: | > > > Jim King writes: | > > > > Before I go chasing down too many dead ends, has anybody been successful | > > > > using PCMCIA? My AS200 came with an ISA-PCMCIA adapter card. My first | > > > > attempt at using it was unsuccessful - it looked the PCMCIA card's | > > > > identifier was not able to be read. | > > > I don't think anybody has tried PCMCIA on alpha or is working on it. | > > > I know NetBSD supports it.. | > > | > > On Multia they support the builtin slots. I'm not sure about ISA-PCMCIA | > > bridge cards. | > | > Actually, I could swear that they support those too. | > | Give me a half hour and I will fire the one that I have back into my | as200 and verify. I have talked to Warner Losh about it and actually tested the PCMCIA code on my PWS500au. It does not work. Warner said that the Alpha ISA stuff is a little too much work. In short, PCMCIA does not work on FreeBSD/Alpha. -- +-----------------------------------------------------------+ | keichii@iteration.net | keichii@freebsd.org | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +-----------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu May 3 9:25:38 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 1740A37B422 for ; Thu, 3 May 2001 09:25:35 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f43GP2b65081; Thu, 3 May 2001 10:25:03 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200105031625.f43GP2b65081@harmony.village.org> To: "Jim King" Subject: Re: PCMCIA Cc: freebsd-alpha@FreeBSD.ORG In-reply-to: Your message of "Wed, 02 May 2001 14:41:09 CDT." <006e01c0d33f$d6731300$524c8486@jking> References: <006e01c0d33f$d6731300$524c8486@jking> Date: Thu, 03 May 2001 10:25:02 -0600 From: Warner Losh Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <006e01c0d33f$d6731300$524c8486@jking> "Jim King" writes: : Before I go chasing down too many dead ends, has anybody been successful : using PCMCIA? My AS200 came with an ISA-PCMCIA adapter card. My first : attempt at using it was unsuccessful - it looked the PCMCIA card's : identifier was not able to be read. I have had no reports of pcmcia working on the alpha and there are likely issues with it working that would preclude this. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu May 3 11:16:33 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from flounder.jimking.net (flounder.jimking.net [209.205.176.18]) by hub.freebsd.org (Postfix) with ESMTP id 6F93837B424 for ; Thu, 3 May 2001 11:16:29 -0700 (PDT) (envelope-from jim@jimking.net) Received: from jkinglap ([134.132.79.231]) (authenticated) by flounder.jimking.net (8.11.3/8.11.2) with ESMTP id f43IGAD14423 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO); Thu, 3 May 2001 13:16:11 -0500 (CDT) (envelope-from jim@jimking.net) Message-ID: <002e01c0d3fd$21fefec0$e74f8486@jkinglap> From: "Jim King" To: "Warner Losh" Cc: References: <006e01c0d33f$d6731300$524c8486@jking> <200105031625.f43GP2b65081@harmony.village.org> Subject: Re: PCMCIA Date: Thu, 3 May 2001 13:16:09 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2462.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Warner Losh" wrote: > In message <006e01c0d33f$d6731300$524c8486@jking> "Jim King" writes: > : Before I go chasing down too many dead ends, has anybody been successful > : using PCMCIA? My AS200 came with an ISA-PCMCIA adapter card. My first > : attempt at using it was unsuccessful - it looked the PCMCIA card's > : identifier was not able to be read. > > I have had no reports of pcmcia working on the alpha and there are > likely issues with it working that would preclude this. Oh well, the AS200 is getting a bit long in the tooth anyway. It's probably time for me to replace it with a cheap x86 box. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu May 3 11:43:37 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id A902C37B423 for ; Thu, 3 May 2001 11:43:32 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f43IhLb66733; Thu, 3 May 2001 12:43:21 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200105031843.f43IhLb66733@harmony.village.org> To: "Jim King" Subject: Re: PCMCIA Cc: freebsd-alpha@FreeBSD.ORG In-reply-to: Your message of "Thu, 03 May 2001 13:16:09 CDT." <002e01c0d3fd$21fefec0$e74f8486@jkinglap> References: <002e01c0d3fd$21fefec0$e74f8486@jkinglap> <006e01c0d33f$d6731300$524c8486@jking> <200105031625.f43GP2b65081@harmony.village.org> Date: Thu, 03 May 2001 12:43:21 -0600 From: Warner Losh Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <002e01c0d3fd$21fefec0$e74f8486@jkinglap> "Jim King" writes: : "Warner Losh" wrote: : : > In message <006e01c0d33f$d6731300$524c8486@jking> "Jim King" writes: : > : Before I go chasing down too many dead ends, has anybody been successful : > : using PCMCIA? My AS200 came with an ISA-PCMCIA adapter card. My first : > : attempt at using it was unsuccessful - it looked the PCMCIA card's : > : identifier was not able to be read. : > : > I have had no reports of pcmcia working on the alpha and there are : > likely issues with it working that would preclude this. : : Oh well, the AS200 is getting a bit long in the tooth anyway. It's probably : time for me to replace it with a cheap x86 box. NEWCARD has a chance of supporting it, however. I no longer have alpha hardware to test things on. And even when I did it was so far down on my queue that I never did test things :-( Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu May 3 21: 5:25 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from suntana.fh-konstanz.de (suntana.fh-konstanz.de [141.37.9.230]) by hub.freebsd.org (Postfix) with ESMTP id 8440B37B422 for ; Thu, 3 May 2001 21:05:22 -0700 (PDT) (envelope-from vahe@fh-konstanz.de) Received: from vvl10 (vvl10.fh-konstanz.de [141.37.112.110]) by suntana.fh-konstanz.de (8.9.3+Sun/8.9.3) with SMTP id GAA00773 for ; Fri, 4 May 2001 06:05:20 +0200 (MET DST) Message-ID: <000f01c0d447$eaef9430$7c45fea9@vvl10> From: "Vahe Khachikyan" To: References: <002e01c0d3fd$21fefec0$e74f8486@jkinglap> <006e01c0d33f$d6731300$524c8486@jking> <200105031625.f43GP2b65081@harmony.village.org> <200105031843.f43IhLb66733@harmony.village.org> Subject: Drive Image with dd Date: Fri, 4 May 2001 05:11:30 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Terribly sorry for Off Topic. But I sent the same request to "questions" and got no answer, and I need the answer ASAP :-)) I'll try to be as short as possible. The question is: Will the image of the disk made with "dd if=/dev/da0 of=/backups/scsi.img" reproduce the correct disk structure . I.e will the next command "dd if=/backups/scsi.img of=/dev/da0" recover the disk like it was before, assuming the hard drive is OK (no bad blocks etc). It's out of interest however. The disk contains partitions with OS/2 boot manager, NT 3.11 etc. Theoreticaly it should work. Have anybody experience with such a desposition? Thanks in advance -- Vahe --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri May 4 1:30:20 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from postino.fi.infn.it (postino.fi.infn.it [192.84.145.9]) by hub.freebsd.org (Postfix) with ESMTP id 1D52337B43F for ; Fri, 4 May 2001 01:30:13 -0700 (PDT) (envelope-from Riccardo.Veraldi@fi.infn.it) Received: from nikita.fi.infn.it (nikita.fi.infn.it [192.84.146.189]) by postino.fi.infn.it (8.11.1/8.11.1) with ESMTP id f448Tom37498; Fri, 4 May 2001 10:29:50 +0200 (CEST) From: Riccardo.Veraldi@fi.infn.it Received: by nikita.fi.infn.it (Postfix, from userid 1001) id 2639118CE2; Fri, 4 May 2001 10:29:49 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by nikita.fi.infn.it (Postfix) with ESMTP id DD22415919; Fri, 4 May 2001 10:29:49 +0200 (CEST) Date: Fri, 4 May 2001 10:29:49 +0200 (CEST) X-X-Sender: To: Wilko Bulte Cc: Terry Lambert , , Subject: Re: vector: 0x670 In-Reply-To: <20010502203706.E1339@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all thanks a lot for yoyur valuable help. I Think it might be a problem due to over heating. I removed the dissipator and when I did it hte machine crashed after a few minutes with the machien check 0x670 error... I will change dissipator size and will add special glue for disipation between the CPU and dissipator and I will add a fan and let you know what is going to happen. Now hte CPU is so hot that Icannot even try to put my finger over it!! Rick On Wed, 2 May 2001, Wilko Bulte wrote: > Date: Wed, 2 May 2001 20:37:06 +0200 > From: Wilko Bulte > To: Terry Lambert > Cc: Riccardo.Veraldi@fi.infn.it, freebsd-alpha@freebsd.org > Subject: Re: vector: 0x670 > > On Wed, May 02, 2001 at 06:27:38PM +0000, Terry Lambert wrote: > > > 670 Processor Uncorrectable unrecoverable cache or TLB errors, or > > > read of a non-existent I/O space > > > > > > > > > Do you think it can be an error due to overheating or do I have to throw > > > my AlphaStation away ?? > > > > No quick answers, but some things to try, and some advice and > > opinions... > > > > > > A cache error means that the processor is bad, if it's L1 cache; > > this could be the result of overheating. If it's L2 cache, the > > cause could still be overheating, but I've seen a lot of people > > trying to use cache chips that were too slow. > > I don't recall which AS version this was, but most of the have > SMD soldered on caches. Some have cache modules, some cache SIMMs. > In case of cache modules of any shape or form please check if they > are seated well. > > > - If it's overheating, that's usually the result of overclocking, > > either intentionally, or unintentionally. Make sure you are not > > doing that. > > Easily tested by trying if your fingers get fried when touching the > heatsink. > > > You might also be using memory which is too slow, or has fake > > parity instead of real parity (don't do that). Slow memory > > tends to become more of an issue when you stick in a lot of it, > > since the DMA refresh doesn't get around to each bank in time; > > this is particularly problematic if you are doing heavy I/O, > > so that the memory bus is latched for DMA, and refresh is thus > > delayed really long due to bus hold times; this is usually > > possible to adjust in the drivers or controller configurations > > and is often called "bus on" time. > > *Very* unlikely. Alpha machines are built to really drive lots > of memory. Not this whimpy PC stuff that drives only 4 SIMMs/DIMMs > from a single ASIC. > > > - I've occasionally loaded a machine with too much memory for > > it to reasonably handle refresh, given the memory bus speed > > and the bus-on time for some PCI controllers (I had an Adaptec > > that was a bus hog; when I loaded the disk subsystem with the > > extra amount of RAM, the refresh failed, and the system lost > > its mind). > > Again, unlikely. > > > A TLB error means that the contents of a Translation Lookaside > > Buffer are incorrect. This could be a kernel bug. > > Or the CPU is dead/dying. Seen that before.. > > -- > | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org > |/|/ / / /( (_) Bulte Powered by FreeBSD/alpha http://www.freebsd.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri May 4 1:40:21 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id D986537B422 for ; Fri, 4 May 2001 01:40:16 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [195.11.243.26] (helo=Debug) by post.mail.nl.demon.net with smtp (Exim 3.22 #1) id 14vb8I-0006Zc-00; Fri, 04 May 2001 08:40:14 +0000 To: Riccardo.Veraldi@fi.infn.it, Wilko Bulte , Terry Lambert , , From: Wilko Bulte Subject: Re: vector: 0x670 Date: Fri, 4 May 2001 08:40:14 GMT X-Mailer: www.webmail.nl.demon.net X-Sender: postmaster@wkb@freebie.demon.nl X-Originating-IP: 161.114.88.71 Message-Id: Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi all thanks a lot for yoyur valuable help. > I Think it might be a problem due to over heating. > I removed the dissipator and when I did it hte machine crashed after a few > minutes with the machien check 0x670 error... I will change dissipator Why? I expect this machine to have the standard DEC heatsink? Or has somebody messed with it? > size and will add special glue for disipation between the CPU and Alpha CPUs by default have a Grafoil heat conducting foil between the CPU and the heatsink. It is a small dark gray patch of foil. Is that one missing? Bad idea.. Also, be careful not to over-torque the heatsink mounting nuts! > dissipator and I will add a fan and let you know what is going to happen. > Now hte CPU is so hot that Icannot even try to put my finger over it!! Be careful! You could permanently kill it this way!! Any chance you can make a picture available (borrowing a digital camera or so) of what you have in this machine? Wilko > > Rick > > > On Wed, 2 May > 2001, Wilko Bulte wrote: > > > Date: Wed, 2 May 2001 20:37:06 +0200 > > From: Wilko Bulte > > To: Terry Lambert > > Cc: Riccardo.Veraldi@fi.infn.it, freebsd-alpha@freebsd.org > > Subject: Re: vector: 0x670 > > > > On Wed, May 02, 2001 at 06:27:38PM +0000, Terry Lambert wrote: > > > > 670 Processor Uncorrectable unrecoverable cache or TLB errors, or > > > > read of a non-existent I/O space > > > > > > > > > > > > Do you think it can be an error due to overheating or do I have to throw > > > > my AlphaStation away ?? > > > > > > No quick answers, but some things to try, and some advice and > > > opinions... > > > > > > > > > A cache error means that the processor is bad, if it's L1 cache; > > > this could be the result of overheating. If it's L2 cache, the > > > cause could still be overheating, but I've seen a lot of people > > > trying to use cache chips that were too slow. > > > > I don't recall which AS version this was, but most of the have > > SMD soldered on caches. Some have cache modules, some cache SIMMs. > > In case of cache modules of any shape or form please check if they > > are seated well. > > > > > - If it's overheating, that's usually the result of overclocking, > > > either intentionally, or unintentionally. Make sure you are not > > > doing that. > > > > Easily tested by trying if your fingers get fried when touching the > > heatsink. > > > > > You might also be using memory which is too slow, or has fake > > > parity instead of real parity (don't do that). Slow memory > > > tends to become more of an issue when you stick in a lot of it, > > > since the DMA refresh doesn't get around to each bank in time; > > > this is particularly problematic if you are doing heavy I/O, > > > so that the memory bus is latched for DMA, and refresh is thus > > > delayed really long due to bus hold times; this is usually > > > possible to adjust in the drivers or controller configurations > > > and is often called "bus on" time. > > > > *Very* unlikely. Alpha machines are built to really drive lots > > of memory. Not this whimpy PC stuff that drives only 4 SIMMs/DIMMs > > from a single ASIC. > > > > > - I've occasionally loaded a machine with too much memory for > > > it to reasonably handle refresh, given the memory bus speed > > > and the bus-on time for some PCI controllers (I had an Adaptec > > > that was a bus hog; when I loaded the disk subsystem with the > > > extra amount of RAM, the refresh failed, and the system lost > > > its mind). > > > > Again, unlikely. > > > > > A TLB error means that the contents of a Translation Lookaside > > > Buffer are incorrect. This could be a kernel bug. > > > > Or the CPU is dead/dying. Seen that before.. > > > > -- > > | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org > > |/|/ / / /( (_) Bulte Powered by FreeBSD/alpha http://www.freebsd.org > > > -- | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org |/|/ / / /( (_) Bulte http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri May 4 4:51:36 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from postino.fi.infn.it (postino.fi.infn.it [192.84.145.9]) by hub.freebsd.org (Postfix) with ESMTP id A150737B423 for ; Fri, 4 May 2001 04:51:29 -0700 (PDT) (envelope-from Riccardo.Veraldi@fi.infn.it) Received: from nikita.fi.infn.it (nikita.fi.infn.it [192.84.146.189]) by postino.fi.infn.it (8.11.1/8.11.1) with ESMTP id f44BoXm45925; Fri, 4 May 2001 13:50:34 +0200 (CEST) From: Riccardo.Veraldi@fi.infn.it Received: by nikita.fi.infn.it (Postfix, from userid 1001) id CB08018CEA; Fri, 4 May 2001 13:50:32 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by nikita.fi.infn.it (Postfix) with ESMTP id 610E715905; Fri, 4 May 2001 13:50:31 +0200 (CEST) Date: Fri, 4 May 2001 13:50:30 +0200 (CEST) X-X-Sender: To: Wilko Bulte Cc: Subject: Re: vector: 0x670 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org yes it has the standard heatsink but looking at it, it so really too hot... there is also the patch foil but it looks a little bit messed the surface looks like not the same in all its part the colour changed, maybe the foil does not work anymore very fine... so that I have been thinking to add some of that special "glue" which is used on the Pee See between the Pee Sea CPU and the dissipator. My alpha dissipator looks realy vey very hot... and testing the system without the CPU dissipator it crashes with the same error in 2 minutes... there are 2 possibilites now, the cache is fucked or it is the CPU overheating problem. Someone told me it is really not likely a CPU internal problem like a TLB problem. Someone told me if the CPU is fucked because of overheating permanent damage it will not even start. IF it is the overheating problem I think I will solve it with a bigger dissipator the one from a Pentium 4 carefully adapted to the alpha CPU and adding a new fan also over the dissipator. I have no way right now to know if it is a CPU problem or cache problem or do I have one way to discover it ?? If it is the cache I have no chances, I have to throw away my motherboard I guess. The cache modules are hard wired on the motherboard I wanted to try something else anyway to see if the problem is a problem due overheating. if I put some very vold water in a proper glass box and put the box over the CPU it will help a lot to cool the system, and I Can try to stress the system in that way... I dunno... Iam desperate at this point! thanks Rick On Fri, 4 May 2001, Wilko Bulte wrote: > Date: Fri, 4 May 2001 08:40:14 GMT > From: Wilko Bulte > To: Riccardo.Veraldi@fi.infn.it, Wilko Bulte , > Terry Lambert , Riccardo.Veraldi@fi.infn.it, > freebsd-alpha@freebsd.org > Subject: Re: vector: 0x670 > > > Hi all thanks a lot for yoyur valuable help. > > I Think it might be a problem due to over heating. > > I removed the dissipator and when I did it hte machine crashed after a few > > minutes with the machien check 0x670 error... I will change dissipator > > Why? I expect this machine to have the standard DEC heatsink? Or has somebody > messed with it? > > > size and will add special glue for disipation between the CPU and > > Alpha CPUs by default have a Grafoil heat conducting foil between the > CPU and the heatsink. It is a small dark gray patch of foil. Is that one > missing? Bad idea.. Also, be careful not to over-torque the heatsink mounting > nuts! > > > dissipator and I will add a fan and let you know what is going to happen. > > Now hte CPU is so hot that Icannot even try to put my finger over it!! > > Be careful! You could permanently kill it this way!! > > Any chance you can make a picture available (borrowing a digital camera or > so) of what you have in this machine? > > Wilko > > > > > Rick > > > > > > On Wed, 2 May > > 2001, Wilko Bulte wrote: > > > > > Date: Wed, 2 May 2001 20:37:06 +0200 > > > From: Wilko Bulte > > > To: Terry Lambert > > > Cc: Riccardo.Veraldi@fi.infn.it, freebsd-alpha@freebsd.org > > > Subject: Re: vector: 0x670 > > > > > > On Wed, May 02, 2001 at 06:27:38PM +0000, Terry Lambert wrote: > > > > > 670 Processor Uncorrectable unrecoverable cache or TLB errors, or > > > > > read of a non-existent I/O space > > > > > > > > > > > > > > > Do you think it can be an error due to overheating or do I have to throw > > > > > my AlphaStation away ?? > > > > > > > > No quick answers, but some things to try, and some advice and > > > > opinions... > > > > > > > > > > > > A cache error means that the processor is bad, if it's L1 cache; > > > > this could be the result of overheating. If it's L2 cache, the > > > > cause could still be overheating, but I've seen a lot of people > > > > trying to use cache chips that were too slow. > > > > > > I don't recall which AS version this was, but most of the have > > > SMD soldered on caches. Some have cache modules, some cache SIMMs. > > > In case of cache modules of any shape or form please check if they > > > are seated well. > > > > > > > - If it's overheating, that's usually the result of overclocking, > > > > either intentionally, or unintentionally. Make sure you are not > > > > doing that. > > > > > > Easily tested by trying if your fingers get fried when touching the > > > heatsink. > > > > > > > You might also be using memory which is too slow, or has fake > > > > parity instead of real parity (don't do that). Slow memory > > > > tends to become more of an issue when you stick in a lot of it, > > > > since the DMA refresh doesn't get around to each bank in time; > > > > this is particularly problematic if you are doing heavy I/O, > > > > so that the memory bus is latched for DMA, and refresh is thus > > > > delayed really long due to bus hold times; this is usually > > > > possible to adjust in the drivers or controller configurations > > > > and is often called "bus on" time. > > > > > > *Very* unlikely. Alpha machines are built to really drive lots > > > of memory. Not this whimpy PC stuff that drives only 4 SIMMs/DIMMs > > > from a single ASIC. > > > > > > > - I've occasionally loaded a machine with too much memory for > > > > it to reasonably handle refresh, given the memory bus speed > > > > and the bus-on time for some PCI controllers (I had an Adaptec > > > > that was a bus hog; when I loaded the disk subsystem with the > > > > extra amount of RAM, the refresh failed, and the system lost > > > > its mind). > > > > > > Again, unlikely. > > > > > > > A TLB error means that the contents of a Translation Lookaside > > > > Buffer are incorrect. This could be a kernel bug. > > > > > > Or the CPU is dead/dying. Seen that before.. > > > > > > -- > > > | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org > > > |/|/ / / /( (_) Bulte Powered by FreeBSD/alpha http://www.freebsd.org > > > > > > > > -- > | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org > |/|/ / / /( (_) Bulte http://www.freebsd.org > http://www.nlfug.nl > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri May 4 19:34: 9 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from femail6.sdc1.sfba.home.com (femail6.sdc1.sfba.home.com [24.0.95.86]) by hub.freebsd.org (Postfix) with ESMTP id B24D837B423 for ; Fri, 4 May 2001 19:34:07 -0700 (PDT) (envelope-from miklic@home.com) Received: from c109118a3 ([24.10.140.87]) by femail6.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP id <20010505023407.SQJQ29527.femail6.sdc1.sfba.home.com@c109118a3> for ; Fri, 4 May 2001 19:34:07 -0700 Message-ID: <000801c0d50c$5288ba30$6401a8c0@c109118a3> From: "Andrew M. Miklic" To: Subject: PCI_RF_DENSE Date: Fri, 4 May 2001 19:37:26 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anyone know if the PCI_RF_DENSE flag works with allocating system memory resources in -CURRENT? It used to work on 4.0, but when I tried to port my TGA driver to 5.0 on my AlphaStation200, I keep getting NULL returned in the resource's r_virtual field when allocated from the driver's attach() routine...apparently no machine-specific method is being properly initialized for alphapci_cvt_dense(), as the default null_cvt() is always being called (which just returns NULL)--does anyone have any ideas? Is anyone successfully using a pci driver that uses "dense" memory? Thanks, Andrew Miklic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message