From owner-freebsd-alpha Sun Aug 15 10:17:41 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B8BAD153CE for ; Sun, 15 Aug 1999 10:17:33 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA19255; Sun, 15 Aug 1999 10:17:54 -0700 Date: Sun, 15 Aug 1999 10:17:52 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Alan Cox Cc: alpha@freebsd.org Subject: Re: more breakage... (fwd) In-Reply-To: <19990815013618.B11439@cs.rice.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org These didn't patch cleanly, but I did what I thought was the close equivalent and the problem/panic returned- sorry. I guess some more cleanup in vm_page is warranted. I believe you're right in going from 0 to PQ_COUNT in a number of cases- but there are apparently other oversubtle cases that will have to be addressed. The main thing though is that we can proceed along. I really wish beast had a serial console we could get at- it is really important for both i386 && alpha architectures to be tested. On Sun, 15 Aug 1999, Alan Cox wrote: > Can you tell me if the following works? It doesn't address > the root cause of the problem, but it will confirm my explanation. > > Thanks, > Alan > > Index: vm/vm_page.c > =================================================================== > RCS file: /home/ncvs/src/sys/vm/vm_page.c,v > retrieving revision 1.138 > diff -c -r1.138 vm_page.c > *** vm_page.c 1999/08/11 05:12:00 1.138 > --- vm_page.c 1999/08/15 06:16:44 > *************** > *** 123,129 **** > vm_page_queues[PQ_CACHE+i].pl = &vm_page_queue_cache[i]; > vm_page_queues[PQ_CACHE+i].cnt = &cnt.v_cache_count; > } > ! for(i=PQ_FREE;i if (vm_page_queues[i].pl) { > TAILQ_INIT(vm_page_queues[i].pl); > } else { > --- 123,129 ---- > vm_page_queues[PQ_CACHE+i].pl = &vm_page_queue_cache[i]; > vm_page_queues[PQ_CACHE+i].cnt = &cnt.v_cache_count; > } > ! for (i = 0; i < PQ_COUNT; i++) { > if (vm_page_queues[i].pl) { > TAILQ_INIT(vm_page_queues[i].pl); > } else { > Index: vm/vm_page.h > =================================================================== > RCS file: /home/ncvs/src/sys/vm/vm_page.h,v > retrieving revision 1.66 > diff -c -r1.66 vm_page.h > *** vm_page.h 1999/08/14 06:25:54 1.66 > --- vm_page.h 1999/08/15 06:02:05 > *************** > *** 194,202 **** > #define PQ_L2_MASK (PQ_L2_SIZE - 1) > > #define PQ_NONE PQ_COUNT > ! #define PQ_FREE 0 > ! #define PQ_INACTIVE PQ_L2_SIZE > ! #define PQ_ACTIVE (1 + PQ_L2_SIZE) > #define PQ_CACHE (2 + PQ_L2_SIZE) > #define PQ_COUNT (2 + 2*PQ_L2_SIZE) > > --- 194,202 ---- > #define PQ_L2_MASK (PQ_L2_SIZE - 1) > > #define PQ_NONE PQ_COUNT > ! #define PQ_ACTIVE 0 > ! #define PQ_INACTIVE 1 > ! #define PQ_FREE 2 > #define PQ_CACHE (2 + PQ_L2_SIZE) > #define PQ_COUNT (2 + 2*PQ_L2_SIZE) > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Aug 15 19:21:14 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 079DF14BE1 for ; Sun, 15 Aug 1999 19:21:05 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id WAA61565 for ; Sun, 15 Aug 1999 22:19:22 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Sun, 15 Aug 1999 22:19:22 -0400 (EDT) From: Chuck Robey To: FreeBSD-Alpha Subject: FAQ and power for PC164SX 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 Anyone know the location of any kind of readme, even if it's got loads of spelling errors and bad BO, regarding Alpha installations? Anyhow, I have a PC164SX board. I'd heard that the PC164* boards needed to have a kludged ATX power supply, because the interface offered from the board to the power supply had no ability to turn the power supply on and off. Well, now that I have one, and I've read the PC164SX trm, it says on page 2-13 that connector J1 is for Soft Power, and pin 1, INPUT, is identified by the string "System Power On/Off". That seems suspiciously like just that I was told was missing from the power supply. Could someone please explain about the power situation? I have a 300 watt standard ATX PS, and I'm loathe to spend extra on a specially kludged PS unless there's good reason. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Aug 15 19:27:15 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from dingo.cdrom.com (castles521.castles.com [208.214.165.85]) by hub.freebsd.org (Postfix) with ESMTP id 63C1A1547A for ; Sun, 15 Aug 1999 19:27:08 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id TAA15936; Sun, 15 Aug 1999 19:20:17 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908160220.TAA15936@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chuck Robey Cc: FreeBSD-Alpha Subject: Re: FAQ and power for PC164SX In-reply-to: Your message of "Sun, 15 Aug 1999 22:19:22 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 15 Aug 1999 19:20:17 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The 164SX board should work with any normal ATX power supply; certainly all the ones I've built have. > Anyone know the location of any kind of readme, even if it's got loads > of spelling errors and bad BO, regarding Alpha installations? > > > Anyhow, I have a PC164SX board. I'd heard that the PC164* boards needed > to have a kludged ATX power supply, because the interface offered from > the board to the power supply had no ability to turn the power supply on > and off. Well, now that I have one, and I've read the PC164SX trm, it > says on page 2-13 that connector J1 is for Soft Power, and pin 1, INPUT, > is identified by the string "System Power On/Off". That seems > suspiciously like just that I was told was missing from the power > supply. Could someone please explain about the power situation? I have > a 300 watt standard ATX PS, and I'm loathe to spend extra on a specially > kludged PS unless there's good reason. > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@picnic.mat.net | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. > (301) 220-2114 | > ----------------------------+----------------------------------------------- > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Aug 16 13:34:12 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from swp5.gs.com (swp5.gs.com [192.246.9.39]) by hub.freebsd.org (Postfix) with ESMTP id 62EDA154C1 for ; Mon, 16 Aug 1999 13:34:06 -0700 (PDT) (envelope-from Wally.Koscielny@gs.com) Received: from swp5.gs.com (root@localhost) by swp5.gs.com with ESMTP id QAA29577 for ; Mon, 16 Aug 1999 16:33:28 -0400 (EDT) Received: from nbcppsh02.wan.gs.com ([199.29.246.34]) by swp5.gs.com with ESMTP id QAA29561 for ; Mon, 16 Aug 1999 16:33:27 -0400 (EDT) Received: from nbcppsh01.wan.gs.com (nbcppsh01.wan.gs.com [138.8.220.34]) by nbcppsh02.wan.gs.com (8.9.1a/8.9.0/dmzpo1) with ESMTP id QAA13105 for ; Mon, 16 Aug 1999 16:33:27 -0400 (EDT) Received: from gsny28e.et.gs.com (gsny28e.et.gs.com [148.86.93.30]) by nbcppsh01.wan.gs.com (8.9.1a/8.9.0/postoffice1) with ESMTP id QAA25029 for ; Mon, 16 Aug 1999 16:33:25 -0400 (EDT) Received: by gsny28e.et.gs.com with Internet Mail Service (5.5.2448.0) id ; Mon, 16 Aug 1999 16:33:27 -0400 Message-ID: From: "Koscielny, Wally" To: "'alpha@freebsd.org'" Subject: Help with ed0 or ep0 Date: Mon, 16 Aug 1999 16:33:25 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Guys, I'm trying to install on a Alpha PC164LX / 533 Mhz. but it does not see my ed0 or ep0. It does not even scan for them at bootup of the floppy. It sees everything else though. What should I do ? Thank You, Wally K. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Aug 16 13:50:10 1999 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 5D00C14D76 for ; Mon, 16 Aug 1999 13:50:04 -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.1/8.9.1) with ESMTP id QAA29748; Mon, 16 Aug 1999 16:48:34 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id QAA74166; Mon, 16 Aug 1999 16:48:34 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 16 Aug 1999 16:48:33 -0400 (EDT) To: "Koscielny, Wally" Cc: "'alpha@freebsd.org'" Subject: Re: Help with ed0 or ep0 In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14264.30835.670532.452858@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Koscielny, Wally writes: > Hi Guys, > > > > I'm trying to install on a Alpha PC164LX / 533 Mhz. but it does not see my > ed0 or ep0. It does not even scan for them at bootup of the floppy. It sees > everything else though. What should I do ? > > > > Thank You, > Wally K. > You should use a supported NIC. One of: device al0 device ax0 device de0 device fxp0 device le0 device mx0 device pn0 device rl0 device sf0 device tl0 device vr0 device wb0 device xl0 Note that the 'le0' is the lance ethernet on TurboChannel boxes, not an isa card.. Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Aug 17 6:23:17 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from swp5.gs.com (swp5.gs.com [192.246.9.39]) by hub.freebsd.org (Postfix) with ESMTP id E1E4615694 for ; Tue, 17 Aug 1999 06:23:13 -0700 (PDT) (envelope-from Wally.Koscielny@gs.com) Received: from swp5.gs.com (root@localhost) by swp5.gs.com with ESMTP id JAA26619; Tue, 17 Aug 1999 09:23:43 -0400 (EDT) Received: from nbcppsh02.wan.gs.com ([199.29.246.34]) by swp5.gs.com with ESMTP id JAA26556; Tue, 17 Aug 1999 09:23:40 -0400 (EDT) Received: from nbcppsh01.wan.gs.com (nbcppsh01.wan.gs.com [138.8.220.34]) by nbcppsh02.wan.gs.com (8.9.1a/8.9.0/dmzpo1) with ESMTP id JAA20217; Tue, 17 Aug 1999 09:23:38 -0400 (EDT) Received: from gsny28e.et.gs.com (gsny28e.et.gs.com [148.86.93.30]) by nbcppsh01.wan.gs.com (8.9.1a/8.9.0/postoffice1) with ESMTP id JAA00982; Tue, 17 Aug 1999 09:23:38 -0400 (EDT) Received: by gsny28e.et.gs.com with Internet Mail Service (5.5.2448.0) id ; Tue, 17 Aug 1999 09:23:39 -0400 Message-ID: From: "Koscielny, Wally" To: "'Andrew Gallatin'" Cc: "'alpha@freebsd.org'" Subject: RE: Help with ed0 or ep0 Date: Tue, 17 Aug 1999 09:23:38 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org When I looked up at the hardware.txt contained in the alpha directory on the snapshot server it listed ed0 ep0 and the other nics that are apparently not supported. We should have a hardware.txt specific to the alpha distribution. Or have some website with a listing of the hardware that is supported. This way, people wouldn't have to ask questions like mine on here. Is there a place that I can find a comprehensive listing of the hardware devices that are supported by FreeBSD-alpha ? Thank You, Wally K. > -----Original Message----- > From: Andrew Gallatin [SMTP:gallatin@cs.duke.edu] > Sent: Monday, August 16, 1999 4:49 PM > To: Koscielny, Wally > Cc: 'alpha@freebsd.org' > Subject: Re: Help with ed0 or ep0 > > > Koscielny, Wally writes: > > Hi Guys, > > > > > > > > I'm trying to install on a Alpha PC164LX / 533 Mhz. but it does not see > my > > ed0 or ep0. It does not even scan for them at bootup of the floppy. It > sees > > everything else though. What should I do ? > > > > > > > > Thank You, > > Wally K. > > > > You should use a supported NIC. One of: > > device al0 > device ax0 > device de0 > device fxp0 > device le0 > device mx0 > device pn0 > device rl0 > device sf0 > device tl0 > device vr0 > device wb0 > device xl0 > > > Note that the 'le0' is the lance ethernet on TurboChannel boxes, not > an isa card.. > > Cheers, > > Drew > -------------------------------------------------------------------------- > ---- > Andrew Gallatin, Sr Systems Programmer > http://www.cs.duke.edu/~gallatin > Duke University Email: gallatin@cs.duke.edu > Department of Computer Science Phone: (919) 660-6590 > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Aug 17 6:31:48 1999 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 9E7E015670 for ; Tue, 17 Aug 1999 06:31:45 -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.1/8.9.1) with ESMTP id JAA13390; Tue, 17 Aug 1999 09:31:24 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id JAA75325; Tue, 17 Aug 1999 09: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 Date: Tue, 17 Aug 1999 09:31:23 -0400 (EDT) To: "Koscielny, Wally" Cc: "'alpha@freebsd.org'" Subject: RE: Help with ed0 or ep0 In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14265.25341.874547.16055@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Yes, there should be. And people are working on it. For now, the best way I know of is to look at the latest revision of the GENERIC config file: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/alpha/conf/GENERIC The installation kernels are built from a configuration which is based on this file. More devices than those listed in GENERIC actually work (adaptec PCI scsi, Tigon gigabit ethernet, etc). We also need a LINT. Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 Koscielny, Wally writes: > > > > When I looked up at the hardware.txt contained in the alpha directory on the > snapshot server it listed ed0 ep0 and the other nics that are apparently not > supported. We should have a hardware.txt specific to the alpha distribution. > Or have some website with a listing of the hardware that is supported. This > way, people wouldn't have to ask questions like mine on here. Is there a > place that I can find a comprehensive listing of the hardware devices that > are supported by FreeBSD-alpha ? > > > > Thank You, > Wally K. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Aug 17 6:44:28 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from swp5.gs.com (swp5.gs.com [192.246.9.39]) by hub.freebsd.org (Postfix) with ESMTP id BF91C14E24 for ; Tue, 17 Aug 1999 06:44:25 -0700 (PDT) (envelope-from Wally.Koscielny@gs.com) Received: from swp5.gs.com (root@localhost) by swp5.gs.com with ESMTP id JAA12706; Tue, 17 Aug 1999 09:42:35 -0400 (EDT) Received: from nbcppsh02.wan.gs.com ([199.29.246.34]) by swp5.gs.com with ESMTP id JAA12679; Tue, 17 Aug 1999 09:42:34 -0400 (EDT) Received: from nbcppsh01.wan.gs.com (nbcppsh01.wan.gs.com [138.8.220.34]) by nbcppsh02.wan.gs.com (8.9.1a/8.9.0/dmzpo1) with ESMTP id JAA28463; Tue, 17 Aug 1999 09:42:32 -0400 (EDT) Received: from gsny28e.et.gs.com (gsny28e.et.gs.com [148.86.93.30]) by nbcppsh01.wan.gs.com (8.9.1a/8.9.0/postoffice1) with ESMTP id JAA11779; Tue, 17 Aug 1999 09:42:32 -0400 (EDT) Received: by gsny28e.et.gs.com with Internet Mail Service (5.5.2448.0) id ; Tue, 17 Aug 1999 09:42:33 -0400 Message-ID: From: "Koscielny, Wally" To: "'Andrew Gallatin'" Cc: "'alpha@freebsd.org'" Subject: RE: Help with ed0 or ep0 Date: Tue, 17 Aug 1999 09:42:32 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks. Do you know off the top of your head if any of the supported nics uses BNC ? Thanks again, Wally K. > -----Original Message----- > From: Andrew Gallatin [SMTP:gallatin@cs.duke.edu] > Sent: Tuesday, August 17, 1999 9:31 AM > To: Koscielny, Wally > Cc: 'alpha@freebsd.org' > Subject: RE: Help with ed0 or ep0 > > > > Yes, there should be. And people are working on it. > > For now, the best way I know of is to look at the latest revision of > the GENERIC config file: > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/alpha/conf/GENERIC The > installation kernels are built from a configuration which is based on > this file. > > More devices than those listed in GENERIC actually work (adaptec PCI > scsi, Tigon gigabit ethernet, etc). We also need a LINT. > > Cheers, > > Drew > > -------------------------------------------------------------------------- > ---- > Andrew Gallatin, Sr Systems Programmer > http://www.cs.duke.edu/~gallatin > Duke University Email: gallatin@cs.duke.edu > Department of Computer Science Phone: (919) 660-6590 > > > > Koscielny, Wally writes: > > > > > > > > When I looked up at the hardware.txt contained in the alpha directory > on the > > snapshot server it listed ed0 ep0 and the other nics that are > apparently not > > supported. We should have a hardware.txt specific to the alpha > distribution. > > Or have some website with a listing of the hardware that is supported. > This > > way, people wouldn't have to ask questions like mine on here. Is there > a > > place that I can find a comprehensive listing of the hardware devices > that > > are supported by FreeBSD-alpha ? > > > > > > > > Thank You, > > Wally K. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Aug 17 6:54:57 1999 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 E135415018 for ; Tue, 17 Aug 1999 06:54:48 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id JAA13915; Tue, 17 Aug 1999 09:53:50 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id JAA75372; Tue, 17 Aug 1999 09:53:49 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 17 Aug 1999 09:53:48 -0400 (EDT) To: "Koscielny, Wally" Cc: "'alpha@freebsd.org'" Subject: RE: Help with ed0 or ep0 In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14265.26534.146058.852370@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Koscielny, Wally writes: > Thanks. Do you know off the top of your head if any of the supported nics > uses BNC ? > > Thanks again, > Wally K. Yes, there are cheap 10Mb tulip (21040) cards which have a BNC connectors. The Kingston cards used to use 21040 chips, I haven't bought one in ages & have no idea what they use now.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Aug 17 11:15: 2 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 6C17215757 for ; Tue, 17 Aug 1999 11:14:54 -0700 (PDT) (envelope-from alc@cs.rice.edu) Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id NAA27827 for ; Tue, 17 Aug 1999 13:12:52 -0500 (CDT) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.3/8.7.3) id NAA37601 for alpha@freebsd.org; Tue, 17 Aug 1999 13:12:52 -0500 (CDT) Date: Tue, 17 Aug 1999 13:12:52 -0500 From: Alan Cox To: alpha@freebsd.org Subject: MFC? Message-ID: <19990817131252.C35550@nonpc.cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org See vm/vm_page.c rev 1.131. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Aug 17 14:55:29 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 1725E15A01 for ; Tue, 17 Aug 1999 14:54:07 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id RAA61009 for ; Tue, 17 Aug 1999 17:54:38 -0400 (EDT) Message-Id: <199908172154.RAA61009@cs.rpi.edu> To: freebsd-alpha@freebsd.org Subject: netboot on a multia system Date: Tue, 17 Aug 1999 17:54:38 -0400 From: "David E. Cross" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I picked up one of those "free" multia systems. I am having some difficulty in getting it to netboot. The problem that I have is that it tftp's the boot file, prints some stuff on the screen, and then almost immediately reboots. the Ethernet adapter in the machine is referred to as "ewa0" any ideas? -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Aug 17 15:19:39 1999 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 9732714E85 for ; Tue, 17 Aug 1999 15:19:27 -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.1/8.9.1) with ESMTP id SAA23962; Tue, 17 Aug 1999 18:19:57 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id SAA76587; Tue, 17 Aug 1999 18:19:57 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 17 Aug 1999 18:19:56 -0400 (EDT) To: "David E. Cross" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: netboot on a multia system In-Reply-To: <199908172154.RAA61009@cs.rpi.edu> References: <199908172154.RAA61009@cs.rpi.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14265.56842.680302.912352@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David E. Cross writes: > I picked up one of those "free" multia systems. I am having > some difficulty in getting it to netboot. The problem that I have is > that it tftp's the boot file, prints some stuff on the screen, and then > almost immediately reboots. the Ethernet adapter in the machine is > referred to as "ewa0" any ideas? > I don't have a multia, so I'll just give you a stab in the dark... there might be problems with your firmware. I seem to remember that NetBSD has problems netbooting on this platform with newer firmware revs. Try using a serial console on it so you can read the message. Since the TGA is not yet supported as a console device, you'll probably want a serial console anyway. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Aug 17 15:23:53 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 100261578A for ; Tue, 17 Aug 1999 15:23:45 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id SAA61489; Tue, 17 Aug 1999 18:23:01 -0400 (EDT) Message-Id: <199908172223.SAA61489@cs.rpi.edu> To: Andrew Gallatin Cc: "David E. Cross" , freebsd-alpha@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: netboot on a multia system In-Reply-To: Message from Andrew Gallatin of "Tue, 17 Aug 1999 18:19:56 EDT." <14265.56842.680302.912352@grasshopper.cs.duke.edu> Date: Tue, 17 Aug 1999 18:23:01 -0400 From: "David E. Cross" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have just now, after many reboot attempts, been able to read the message as it scrolls by. boot: boot device name does not contain ethernet address. Reading the source, I can see what to do. I may need to use 'setnetbootinfo'. How do I do this when I have no alpha system from which to do it ;) -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Aug 17 15:38: 5 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from demon.net (sos.support.demon.net [194.217.150.1]) by hub.freebsd.org (Postfix) with SMTP id DA66414EF2 for ; Tue, 17 Aug 1999 15:38:00 -0700 (PDT) (envelope-from afc@demon.net) Received: from pc173.southend.demon.net ([194.217.151.173]) by sos.support.demon.net id aa26696; 17 Aug 99 23:36 BST Message-ID: Date: Tue, 17 Aug 1999 23:37:12 +0100 To: "David E. Cross" Cc: freebsd-alpha@freebsd.org From: Alex Collins Subject: Re: netboot on a multia system References: <199908172154.RAA61009@cs.rpi.edu> In-Reply-To: <199908172154.RAA61009@cs.rpi.edu> MIME-Version: 1.0 X-Mailer: Turnpike Integrated Version 4.02 U Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199908172154.RAA61009@cs.rpi.edu>, David E. Cross writes >I picked up one of those "free" multia systems. I am having >some difficulty in getting it to netboot. The problem that I have is >that it tftp's the boot file, prints some stuff on the screen, and then >almost immediately reboots. the Ethernet adapter in the machine is >referred to as "ewa0" any ideas? > Hi there. The Mulita won't Network Boot. - The console is " Broke " and to my knowledge there is no fix available. You will need to find a floppy drive from an old Laptop machine, or it is possible to boot from ARC into the CD-ROM. I have never tried this from SRM. From ARC - Select " run a program " You could also install NT onto a minimal partition, and create a ~ 5 MB FAT partition and then DD the floppy images to there. I strongly recommend upgrading the SRM console. the updates can be found at ftp://ftp.digital.com/pub/DEC/Alpha/firmware/interim/udb/ Good Luck - they are nice machines to work on. My web page ramblings http://www.par64.com/multia/ may also be of use. Good luck - the Multias are surprisingly good at some things, but very slow at others. -- Alex Collins "Do I have to Register Firm Ware!" Dean Rolfe 24-07-99 Demon Internet afc@demon.net helpdesk@demon.net www.demon.net Frontline Support 0845 2722 444 Fax 0181 371 1168 Sales 0845 2722 666 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Aug 17 15:50:21 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id C501314F80 for ; Tue, 17 Aug 1999 15:50:16 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id PAA27314; Tue, 17 Aug 1999 15:49:43 -0700 Date: Tue, 17 Aug 1999 15:49:42 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: alpha@freebsd.org Subject: Multia Disk Image(?) 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 Hearing David's plaints, and others, I'll find a place to put up a 300MB multia/freebsd disk image (from mostly -current) whioh people ought to be able to use to bootstrap themselves- it'll expect to be da0 but if you boot without the 'a' option and end up single user, you'll be able to edit fstab. The network stuff is for feral, so you'll have to change to suit... I'm dd'ing it now... it'll take quite a while and then I'll try and gzip it. If people think this is still a good idea, I'll find some place, maybe on ftp.freebsd.org(?) - to stash it gzip'd... this might solve some of the bootstrap (literally) issues people might be having. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Aug 17 17:27:37 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id F286E14EAA for ; Tue, 17 Aug 1999 17:27:24 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id RAA15041; Tue, 17 Aug 1999 17:26:53 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id RAA15162; Tue, 17 Aug 1999 17:26:52 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Tue, 17 Aug 1999 17:26:52 -0700 (PDT) Message-Id: <199908180026.RAA15162@vashon.polstra.com> To: alc@cs.rice.edu Subject: Re: MFC? In-Reply-To: <19990817131252.C35550@nonpc.cs.rice.edu> Organization: Polstra & Co., Seattle, WA Cc: alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <19990817131252.C35550@nonpc.cs.rice.edu>, Alan Cox wrote: > See vm/vm_page.c rev 1.131. I can't think of any reason not to merge this change. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Aug 17 20:45:17 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9F1FC15627 for ; Tue, 17 Aug 1999 20:45:15 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id UAA28132 for ; Tue, 17 Aug 1999 20:45:50 -0700 Date: Tue, 17 Aug 1999 20:45:49 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: alpha@FreeBSD.ORG Subject: Re: Multia Disk Image(?) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I'm dd'ing it now... it'll take quite a while and then I'll try and gzip > it. If people think this is still a good idea, I'll find some place, > maybe on ftp.freebsd.org(?) - to stash it gzip'd... this might solve some > of the bootstrap (literally) issues people might be having. Temporarily this can be found in http://www.freebsd.org/~mjacob I'm still waiting to hear whether this is too much usage of 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 Aug 18 5:56:40 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 0F6CA158CD for ; Wed, 18 Aug 1999 05:56:33 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 40B7F1C1F for ; Wed, 18 Aug 1999 20:57:07 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: alpha@freebsd.org Subject: rman_get_virtual() on alpha Date: Wed, 18 Aug 1999 20:57:07 +0800 From: Peter Wemm Message-Id: <19990818125707.40B7F1C1F@overcee.netplex.com.au> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org So, what's the situation these days with rman_get_virtual()? if_fxp explodes on the alpha because it allocates SYS_RES_MEMORY and wants the virtual address of it, but the alpha still is returning physical addresses it seems. It seems to me we might need some alternative to rman_get_virtual since it doesn't have enough context and is just a hack. Perhaps allocating memory and activating a mapping etc needs to be seperate bus methods? That way we can allocate memory, and later activate it (pmap_mapdev on x86, BWX, or DENSE on Alpha as requested) and free it's kvm mappings? *** keyboard not plugged in... ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.f3.f2.f1.f0. ef.ee.ed.probing hose 0, PCI probing PCI-to-ISA bridge, bus 1 bus 0, slot 5 -- pka -- NCR 53C875 bus 0, slot 7 -- eia -- Intel 82558 Ethernet ^^^^^^^^^^^^^^^^^^^^^^^^ Hey! SRM supports the fxp series! bus 0, slot 8, function 1 -- dqa -- Cypress 82C693 IDE bus 0, slot 8, function 2 -- dqb -- Cypress 82C693 IDE ec.f4.eb.ea.e9.e8.e7. Digital AlphaPC 164SX 533 MHz Console V5.4-1, Mar 18 1999 15:23:35 CPU 0 booting waiting for pka0.7.0.5.0 to poll... (boot dka0.0.0.5.0 -flags a) [..] FreeBSD 4.0-CURRENT #92: Wed Aug 18 20:23:04 WST 1999 peter@ashburton.netplex.com.au:/home/src/sys/compile/ASHBURTON EB164 Digital AlphaPC 164SX 533 MHz, 531MHz 8192 byte page size, 1 processor. CPU: PCA56 (21164PC) major=9 minor=2 extensions=0x1 OSF PAL rev: 0x1000600020116 real memory = 132251648 (129152K bytes) avail memory = 124116992 (121208K bytes) Preloaded elf kernel "kernel" at 0xfffffc0000586000. cia0: Pyxis, pass 1 cia0: extended capabilities: 1 pcib0: <2117x PCI host bus adapter> on cia0 pci0: on pcib0 [..] fxp0: irq 10 at device 7.0 on pci0 fxp0: interrupting at CIA irq 10 fatal kernel trap: trap entry = 0x2 (memory management fault) a0 = 0x82221008 a1 = 0x1 a2 = 0x1 pc = 0xfffffc000042ce94 ra = 0xfffffc000042caf0 curproc = 0xfffffc000052e6c8 pid = 0, comm = swapper ddbprinttrap from 0xfffffc000042ce94 ddbprinttrap(0x82221008, 0x1, 0x1, 0x2) panic: trap panic Stopped at Debugger+0x2c: ldq ra,0(sp) <0xfffffc000058b9a0> db> trace Debugger() at Debugger+0x2c panic() at panic+0xf4 trap() at trap+0x5cc XentMM() at XentMM+0x20 fxp_attach() at fxp_attach+0x1f0 _GLOBAL_OFFSET_TABLE_() at _GLOBAL_OFFSET_TABLE_+0x8000 Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Aug 18 6: 3: 2 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id E9AAF14E09 for ; Wed, 18 Aug 1999 06:02:57 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 54C6A1C1F for ; Wed, 18 Aug 1999 21:03:31 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: alpha@freebsd.org Subject: cpu_switch() help needed.. Date: Wed, 18 Aug 1999 21:03:31 +0800 From: Peter Wemm Message-Id: <19990818130331.54C6A1C1F@overcee.netplex.com.au> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I need some help to hook some routines into alpha/swtch.s, but I don't know alpha assembler well enough. I can guess and try and figure it out myself, but I'd rather enlist the help of an expert. :-) I can supply corresponding patches for the x86 (basically delete large chunks of code and replace it with calls to a C routine), but I don't know the calling conventions and implications of side effects for the Alpha. On the x86, the side effects of the registers clobbered by the C code were harmless. I believe Doug is still in transit to/from SIGGRAPH or something. Can any of the other lurkers help? (Andrew? :-). Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Aug 18 6:37:54 1999 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 E722A1591F for ; Wed, 18 Aug 1999 06:37:44 -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.1/8.9.1) with ESMTP id JAA05281; Wed, 18 Aug 1999 09:37:33 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id JAA77706; Wed, 18 Aug 1999 09:37:32 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 18 Aug 1999 09:37:30 -0400 (EDT) To: Peter Wemm Cc: alpha@FreeBSD.ORG Subject: Re: cpu_switch() help needed.. In-Reply-To: <19990818130331.54C6A1C1F@overcee.netplex.com.au> References: <19990818130331.54C6A1C1F@overcee.netplex.com.au> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14266.46516.691196.39030@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Wemm writes: > I need some help to hook some routines into alpha/swtch.s, but I don't know > alpha assembler well enough. I can guess and try and figure it out myself, > but I'd rather enlist the help of an expert. :-) I can supply > corresponding patches for the x86 (basically delete large chunks of code > and replace it with calls to a C routine), but I don't know the calling > conventions and implications of side effects for the Alpha. On the x86, the > side effects of the registers clobbered by the C code were harmless. > > I believe Doug is still in transit to/from SIGGRAPH or something. Can any > of the other lurkers help? (Andrew? :-). > > Cheers, > -Peter What exactly are you trying to do? I might be able to help, but I must admit that I haven't used alpha assembler much myself & am probably at about your skill level with alpha assembler. Two documents you might find useful are: Assembly Language Programmer's Guide: http://www.unix.digital.com/faqs/publications/base_doc/DOCUMENTATION/V40F_PDF/APS31DTE.PDF Calling Standard for Alpha Systems: http://www.unix.digital.com/faqs/publications/base_doc/DOCUMENTATION/V40F_PDF/APY8ACTE.PDF 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 Aug 18 6:57:15 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 7055C1541C for ; Wed, 18 Aug 1999 06:57:06 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id PAA52012; Wed, 18 Aug 1999 15:04:51 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 18 Aug 1999 15:04:50 +0100 (BST) From: Doug Rabson To: Peter Wemm Cc: alpha@freebsd.org Subject: Re: rman_get_virtual() on alpha In-Reply-To: <19990818125707.40B7F1C1F@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 18 Aug 1999, Peter Wemm wrote: > So, what's the situation these days with rman_get_virtual()? if_fxp explodes > on the alpha because it allocates SYS_RES_MEMORY and wants the virtual > address of it, but the alpha still is returning physical addresses it seems. > > It seems to me we might need some alternative to rman_get_virtual since it > doesn't have enough context and is just a hack. Perhaps allocating memory > and activating a mapping etc needs to be seperate bus methods? That way we > can allocate memory, and later activate it (pmap_mapdev on x86, BWX, or > DENSE on Alpha as requested) and free it's kvm mappings? The fxp driver should probable use SYS_RES_DENSE to get the right virtual pointer. It would certainly be a lot cleaner to separate the resource allocation from the virtual mapping. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Aug 18 7: 0: 2 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 8E0B714CFB for ; Wed, 18 Aug 1999 06:59:58 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id PAA52020; Wed, 18 Aug 1999 15:09:33 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 18 Aug 1999 15:09:33 +0100 (BST) From: Doug Rabson To: Peter Wemm Cc: alpha@freebsd.org Subject: Re: cpu_switch() help needed.. In-Reply-To: <19990818130331.54C6A1C1F@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 18 Aug 1999, Peter Wemm wrote: > I need some help to hook some routines into alpha/swtch.s, but I don't know > alpha assembler well enough. I can guess and try and figure it out myself, > but I'd rather enlist the help of an expert. :-) I can supply > corresponding patches for the x86 (basically delete large chunks of code > and replace it with calls to a C routine), but I don't know the calling > conventions and implications of side effects for the Alpha. On the x86, the > side effects of the registers clobbered by the C code were harmless. > > I believe Doug is still in transit to/from SIGGRAPH or something. Can any > of the other lurkers help? (Andrew? :-). Which bit are you trying to hook out? The calling convention is pretty simple - just use the CALL(fn) macro which does everything for you. The C code will tend to clobber everything except s0-s6 and the return value is in v0. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Aug 18 7:20: 3 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 68CAA157E1 for ; Wed, 18 Aug 1999 07:19:55 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 9A5181CA1; Wed, 18 Aug 1999 22:20:13 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Andrew Gallatin Cc: alpha@FreeBSD.ORG Subject: Re: cpu_switch() help needed.. In-reply-to: Your message of "Wed, 18 Aug 1999 09:37:30 -0400." <14266.46516.691196.39030@grasshopper.cs.duke.edu> Date: Wed, 18 Aug 1999 22:20:13 +0800 From: Peter Wemm Message-Id: <19990818142013.9A5181CA1@overcee.netplex.com.au> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Gallatin wrote: > > Peter Wemm writes: > > I need some help to hook some routines into alpha/swtch.s, but I don't kno w > > alpha assembler well enough. I can guess and try and figure it out myself , > > but I'd rather enlist the help of an expert. :-) I can supply > > corresponding patches for the x86 (basically delete large chunks of code > > and replace it with calls to a C routine), but I don't know the calling > > conventions and implications of side effects for the Alpha. On the x86, th e > > side effects of the registers clobbered by the C code were harmless. > > > > I believe Doug is still in transit to/from SIGGRAPH or something. Can any > > of the other lurkers help? (Andrew? :-). > > > > Cheers, > > -Peter > > What exactly are you trying to do? I might be able to help, but I > must admit that I haven't used alpha assembler much myself & am > probably at about your skill level with alpha assembler. I've implemented this on the x86 - moving the next-process selection out of assembler and into a simple C routine, leaving cpu_switch() to just do context saving and restoring. It basically boils down to changing about 150 or so lines of assembler to this: sw1: cli sw1a: ! call _chooseproc /* trash ecx, edx, ret eax*/ ! testl %eax,%eax CROSSJUMP(je, _idle, jne) /* if no proc, idle */ movl %eax,%ecx Then we can do things like per-cpu run queues, affinity, various policy hacks etc without the nightmare of having to implement the bottom end in assembler for each arch. This, incidently, would mean we got idle and realtime scheduling for free on the alpha without having to implement that in assembler. Presently if you start an idle or rtprio process on the alpha, the system comes to a screeching halt as they never run and you end up with deadlocks. I just need to know how to call a C function and how to make sure it's not going to clobber what we're using. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Aug 18 7:44:30 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 9A8E014C25 for ; Wed, 18 Aug 1999 07:44:24 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id DC8091C99; Wed, 18 Aug 1999 22:44:02 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Rabson Cc: alpha@freebsd.org Subject: Re: rman_get_virtual() on alpha In-reply-to: Your message of "Wed, 18 Aug 1999 15:04:50 +0100." Date: Wed, 18 Aug 1999 22:44:02 +0800 From: Peter Wemm Message-Id: <19990818144402.DC8091C99@overcee.netplex.com.au> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug Rabson wrote: > On Wed, 18 Aug 1999, Peter Wemm wrote: > > > So, what's the situation these days with rman_get_virtual()? if_fxp explod es > > on the alpha because it allocates SYS_RES_MEMORY and wants the virtual > > address of it, but the alpha still is returning physical addresses it seems . > > > > It seems to me we might need some alternative to rman_get_virtual since it > > doesn't have enough context and is just a hack. Perhaps allocating memory > > and activating a mapping etc needs to be seperate bus methods? That way we > > can allocate memory, and later activate it (pmap_mapdev on x86, BWX, or > > DENSE on Alpha as requested) and free it's kvm mappings? > > The fxp driver should probable use SYS_RES_DENSE to get the right virtual > pointer. It would certainly be a lot cleaner to separate the resource > allocation from the virtual mapping. The question is though, allocating memory resources on the alpha - does it depend on the mapping type (dense vs. bwx)? Or is that decision better left to mapping time? And can we fit this in with bus_space etc? (NetBSD has a bus_space_map() function to map bus space into kvm, maybe we need a parallel to that such that we don't have to expose DENSE/BWX etc mappings to drivers). Or maybe map it in both dense and bwx space and let bus_space use whichever method is convenient? Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Aug 18 8:51:32 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 4398C14C3D for ; Wed, 18 Aug 1999 08:51:24 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id RAA52509; Wed, 18 Aug 1999 17:00:56 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 18 Aug 1999 17:00:56 +0100 (BST) From: Doug Rabson To: Peter Wemm Cc: alpha@freebsd.org Subject: Re: rman_get_virtual() on alpha In-Reply-To: <19990818144402.DC8091C99@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 18 Aug 1999, Peter Wemm wrote: > Doug Rabson wrote: > > On Wed, 18 Aug 1999, Peter Wemm wrote: > > > > > So, what's the situation these days with rman_get_virtual()? if_fxp explod > es > > > on the alpha because it allocates SYS_RES_MEMORY and wants the virtual > > > address of it, but the alpha still is returning physical addresses it seems > . > > > > > > It seems to me we might need some alternative to rman_get_virtual since it > > > doesn't have enough context and is just a hack. Perhaps allocating memory > > > and activating a mapping etc needs to be seperate bus methods? That way we > > > can allocate memory, and later activate it (pmap_mapdev on x86, BWX, or > > > DENSE on Alpha as requested) and free it's kvm mappings? > > > > The fxp driver should probable use SYS_RES_DENSE to get the right virtual > > pointer. It would certainly be a lot cleaner to separate the resource > > allocation from the virtual mapping. > > The question is though, allocating memory resources on the alpha - does it > depend on the mapping type (dense vs. bwx)? Or is that decision better > left to mapping time? And can we fit this in with bus_space etc? (NetBSD > has a bus_space_map() function to map bus space into kvm, maybe we need a > parallel to that such that we don't have to expose DENSE/BWX etc mappings > to drivers). Or maybe map it in both dense and bwx space and let bus_space > use whichever method is convenient? There is no actual overhead for 'mapping' the resources since we just point at the right part of the direct physical->virtual mapped segment. The main issue as I see it is that the existing mechanism is ugly. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Aug 18 9:11:26 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 2060414C27 for ; Wed, 18 Aug 1999 09:11:16 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 97E171C1F; Thu, 19 Aug 1999 00:09:49 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Rabson Cc: alpha@freebsd.org Subject: Re: rman_get_virtual() on alpha In-reply-to: Your message of "Wed, 18 Aug 1999 17:00:56 +0100." Date: Thu, 19 Aug 1999 00:09:49 +0800 From: Peter Wemm Message-Id: <19990818160949.97E171C1F@overcee.netplex.com.au> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug Rabson wrote: > On Wed, 18 Aug 1999, Peter Wemm wrote: > > > Doug Rabson wrote: > > > On Wed, 18 Aug 1999, Peter Wemm wrote: > > > > > > > So, what's the situation these days with rman_get_virtual()? if_fxp ex plod > > es > > > > on the alpha because it allocates SYS_RES_MEMORY and wants the virtual > > > > address of it, but the alpha still is returning physical addresses it s eems > > . > > > > > > > > It seems to me we might need some alternative to rman_get_virtual since it > > > > doesn't have enough context and is just a hack. Perhaps allocating mem ory > > > > and activating a mapping etc needs to be seperate bus methods? That wa y we > > > > can allocate memory, and later activate it (pmap_mapdev on x86, BWX, or > > > > DENSE on Alpha as requested) and free it's kvm mappings? > > > > > > The fxp driver should probable use SYS_RES_DENSE to get the right virtual > > > pointer. It would certainly be a lot cleaner to separate the resource > > > allocation from the virtual mapping. > > > > The question is though, allocating memory resources on the alpha - does it > > depend on the mapping type (dense vs. bwx)? Or is that decision better > > left to mapping time? And can we fit this in with bus_space etc? (NetBSD > > has a bus_space_map() function to map bus space into kvm, maybe we need a > > parallel to that such that we don't have to expose DENSE/BWX etc mappings > > to drivers). Or maybe map it in both dense and bwx space and let bus_space > > use whichever method is convenient? > > There is no actual overhead for 'mapping' the resources since we just > point at the right part of the direct physical->virtual mapped segment. > The main issue as I see it is that the existing mechanism is ugly. As I see it, the existing method is broken as it requires putting alpha arch stuff into generic drivers. Also, how do we know if a given box *has* got SYS_RES_DENSE support? (ie: bwx instructions) Also.. SYS_RES_MEMORY corresponds to use of physical memory.. Is there a 1:1 relationship between physical memory and BWX and physical->virtual mapping space? (ie: is there any management of that space required?) There is on the x86 since we have to call pmap_mapdev() which allocates KVM which is never freed under the present design. rman_[gs]et_virtual() is (IMHO) evil for this very reason since it requires the parent bus to pre-setup KVM space (on the x86) which may or may not be used, and we never free it. I think it should be: res = BUS_ALLOC_RESOURCE( blah SYS_RES_MEMORY blah) vaddr = BUS_MAP_MEMORY(dev, res, [alignment, any|dense|bwx|whatever, etc]) and corresponding unmap calls or something - just like with BUS_SETUP_INTR() etc. On the alpha it'd be a NOP since the hardware does this kinda stuff for us, but on the x86 we need it for managing kvm wirings. I pretty much think the whole point of doing a mapping at all (in dense mode) is so we can go direct and bypass the bus_space_* macros, with the obvious peril of doing that of course. bus_space_* macros etc have a specific setup in NetBSD which we don't really have a parallel of, and probably should as this would solve this problem for working with the bus_space style interfaces as well. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Aug 18 9:12:44 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 3DE0014EC8 for ; Wed, 18 Aug 1999 09:12:38 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 3C3871C99; Thu, 19 Aug 1999 00:11:33 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Andrew Gallatin Cc: alpha@FreeBSD.ORG Subject: Re: cpu_switch() help needed.. In-reply-to: Your message of "Wed, 18 Aug 1999 09:37:30 -0400." <14266.46516.691196.39030@grasshopper.cs.duke.edu> Date: Thu, 19 Aug 1999 00:11:33 +0800 From: Peter Wemm Message-Id: <19990818161133.3C3871C99@overcee.netplex.com.au> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Gallatin wrote: > > Peter Wemm writes: > > I need some help to hook some routines into alpha/swtch.s, but I don't kno w > > alpha assembler well enough. I can guess and try and figure it out myself , > > but I'd rather enlist the help of an expert. :-) [..] > What exactly are you trying to do? I might be able to help, but I > must admit that I haven't used alpha assembler much myself & am > probably at about your skill level with alpha assembler. Incidently, I got it working, thanks! At last, rtprio and idprio works on the Alpha now. :-) (at least, as well as it normally works, modulo the lock holding problems etc which the stuff I'm working on now will enable us to eventually fix). Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Aug 18 9:28:46 1999 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 E7F0614ED8 for ; Wed, 18 Aug 1999 09:28:39 -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.1/8.9.1) with ESMTP id MAA09008; Wed, 18 Aug 1999 12:28:45 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id MAA77978; Wed, 18 Aug 1999 12:28:45 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 18 Aug 1999 12:28:44 -0400 (EDT) To: Peter Wemm Cc: Doug Rabson , alpha@FreeBSD.ORG Subject: Re: rman_get_virtual() on alpha In-Reply-To: <19990818160949.97E171C1F@overcee.netplex.com.au> References: <19990818160949.97E171C1F@overcee.netplex.com.au> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14266.56422.223568.791717@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Wemm writes: > Doug Rabson wrote: > > On Wed, 18 Aug 1999, Peter Wemm wrote: > > > > > Doug Rabson wrote: > > > > On Wed, 18 Aug 1999, Peter Wemm wrote: > > > > > > > > > So, what's the situation these days with rman_get_virtual()? if_fxp ex > plod > > > es > > > > > on the alpha because it allocates SYS_RES_MEMORY and wants the virtual > > > > > address of it, but the alpha still is returning physical addresses it s > eems > > > . > > > > > > > > > > It seems to me we might need some alternative to rman_get_virtual since > it > > > > > doesn't have enough context and is just a hack. Perhaps allocating mem > ory > > > > > and activating a mapping etc needs to be seperate bus methods? That wa > y we > > > > > can allocate memory, and later activate it (pmap_mapdev on x86, BWX, or > > > > > DENSE on Alpha as requested) and free it's kvm mappings? > > > > > > > > The fxp driver should probable use SYS_RES_DENSE to get the right virtual > > > > pointer. It would certainly be a lot cleaner to separate the resource > > > > allocation from the virtual mapping. > > > > > > The question is though, allocating memory resources on the alpha - does it > > > depend on the mapping type (dense vs. bwx)? Or is that decision better > > > left to mapping time? And can we fit this in with bus_space etc? (NetBSD > > > has a bus_space_map() function to map bus space into kvm, maybe we need a > > > parallel to that such that we don't have to expose DENSE/BWX etc mappings > > > to drivers). Or maybe map it in both dense and bwx space and let bus_space > > > use whichever method is convenient? > > > > There is no actual overhead for 'mapping' the resources since we just > > point at the right part of the direct physical->virtual mapped segment. > > The main issue as I see it is that the existing mechanism is ugly. > > As I see it, the existing method is broken as it requires putting alpha > arch stuff into generic drivers. Also, how do we know if a given box *has* > got SYS_RES_DENSE support? (ie: bwx instructions) Err, you meant SYS_RES_BWX rather than SYS_RES_DENSE. Everything we support has dense memory. > Also.. SYS_RES_MEMORY corresponds to use of physical memory.. Is there a > 1:1 relationship between physical memory and BWX and physical->virtual > mapping space? (ie: is there any management of that space required?) There > is on the x86 since we have to call pmap_mapdev() which allocates KVM which > is never freed under the present design. There's no management required. The virtual addresses get mapped via the alpha's K0SEG. Eg: vm_offset_t pci_cvt_to_bwx(vm_offset_t sparse) { if(chipset.cvt_to_bwx) return ALPHA_PHYS_TO_K0SEG(chipset.cvt_to_bwx(sparse)); else return NULL; } > rman_[gs]et_virtual() is (IMHO) evil for this very reason since it requires > the parent bus to pre-setup KVM space (on the x86) which may or may not be > used, and we never free it. > > I think it should be: > > res = BUS_ALLOC_RESOURCE( blah SYS_RES_MEMORY blah) > vaddr = BUS_MAP_MEMORY(dev, res, [alignment, any|dense|bwx|whatever, etc]) > > and corresponding unmap calls or something - just like with BUS_SETUP_INTR() > etc. On the alpha it'd be a NOP since the hardware does this kinda stuff > for us, but on the x86 we need it for managing kvm wirings. This sounds good to me -- I'd like to eliminate driver ifdefs as well. Would we assume that the 'any' arg to BUS_MAP_MEMORY would translate to dense space on the alpha? I suppose for porting a generic driver, BWX space doesn't really even make much sense. Unless a driver has asm's to exploit it (or exports it via mmap to a user program which does), or unless the kernel is compiled with -mcpi=ev56, no bwx instructions are going to be used on it. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Aug 18 18:47:56 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 5B8941591D for ; Wed, 18 Aug 1999 18:47:50 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id VAA05807 for ; Wed, 18 Aug 1999 21:47:50 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Wed, 18 Aug 1999 21:47:50 -0400 (EDT) From: Chuck Robey To: FreeBSD-Alpha Subject: network cards Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I had just finished getting what I thought was the final piece of my new alpha system, when I realized I don't have a network card. I don't know if there are any compatibility problems with network cards and my PC164SX motherboard ... could someone recommend a good 10BaseT network card that works on that system? I like to avoid the cheapest, and for this, I don't need the best ... Thanks. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Aug 18 19:16:36 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 19EE514F33 for ; Wed, 18 Aug 1999 19:16:33 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id TAA02613; Wed, 18 Aug 1999 19:11:03 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908190211.TAA02613@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chuck Robey Cc: FreeBSD-Alpha Subject: Re: network cards In-reply-to: Your message of "Wed, 18 Aug 1999 21:47:50 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 18 Aug 1999 19:11:03 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I had just finished getting what I thought was the final piece of my new > alpha system, when I realized I don't have a network card. I don't know > if there are any compatibility problems with network cards and my > PC164SX motherboard ... could someone recommend a good 10BaseT network > card that works on that system? > > I like to avoid the cheapest, and for this, I don't need the best ... > Thanks. I'd suggest eg. a Cnet Pro-110, which is based on the Asix chipset. Most of Bill Paul's drivers work on the Alpha, and most of the cards they support are in the $20-40 range. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Aug 18 19:34:37 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 8844014FB5 for ; Wed, 18 Aug 1999 19:34:29 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 563E61C1F; Thu, 19 Aug 1999 10:35:05 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith Cc: Chuck Robey , FreeBSD-Alpha Subject: Re: network cards In-reply-to: Your message of "Wed, 18 Aug 1999 19:11:03 MST." <199908190211.TAA02613@dingo.cdrom.com> Date: Thu, 19 Aug 1999 10:35:05 +0800 From: Peter Wemm Message-Id: <19990819023505.563E61C1F@overcee.netplex.com.au> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith wrote: > > I had just finished getting what I thought was the final piece of my new > > alpha system, when I realized I don't have a network card. I don't know > > if there are any compatibility problems with network cards and my > > PC164SX motherboard ... could someone recommend a good 10BaseT network > > card that works on that system? > > > > I like to avoid the cheapest, and for this, I don't need the best ... > > Thanks. > > I'd suggest eg. a Cnet Pro-110, which is based on the Asix chipset. > Most of Bill Paul's drivers work on the Alpha, and most of the cards > they support are in the $20-40 range. Watch out for the Intel Ether Express Pro 100's. Although the driver is listed as working, it doesn't (and they're not particularly cheap either). (it's the old virtual/physical problem where rman_get_virtual() returns a physical address rather than the mapping window and the kernel page faults) Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Aug 18 19:53: 8 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id DC9C6159CD for ; Wed, 18 Aug 1999 19:52:58 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id WAA06008; Wed, 18 Aug 1999 22:50:48 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Wed, 18 Aug 1999 22:50:48 -0400 (EDT) From: Chuck Robey To: Peter Wemm Cc: Mike Smith , FreeBSD-Alpha Subject: Re: network cards In-Reply-To: <19990819023505.563E61C1F@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 19 Aug 1999, Peter Wemm wrote: > Mike Smith wrote: > > > I had just finished getting what I thought was the final piece of my new > > > alpha system, when I realized I don't have a network card. I don't know > > > if there are any compatibility problems with network cards and my > > > PC164SX motherboard ... could someone recommend a good 10BaseT network > > > card that works on that system? > > > > > > I like to avoid the cheapest, and for this, I don't need the best ... > > > Thanks. > > > > I'd suggest eg. a Cnet Pro-110, which is based on the Asix chipset. > > Most of Bill Paul's drivers work on the Alpha, and most of the cards > > they support are in the $20-40 range. > > Watch out for the Intel Ether Express Pro 100's. Although the driver is > listed as working, it doesn't (and they're not particularly cheap either). > (it's the old virtual/physical problem where rman_get_virtual() returns a > physical address rather than the mapping window and the kernel page faults) Thanks, Peter, I think I'll jump on Mike's suggestion. David O'Brien was amusing me by telling me about the "high fever"s run by his, yours, and one other's (I don't remember whose) Multias, dying when a simple "make -j 3 world" was tried. Stuff like that, I think, really oughta get out on the lists more, just to hammer home to folks that they oughta not try to get the rock-bottom cheapest platform, when going to the Alpha. They wouldn't try running FreeBSD/Intel on a 386sx, but they're happy to buy those Multias. After hearing that, I felt more justified by my going nuts on fans for my PC164SX system. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Aug 19 7:29: 8 1999 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 9BEC214C4C; Thu, 19 Aug 1999 07:28:47 -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.1/8.9.1) with ESMTP id KAA27015; Thu, 19 Aug 1999 10:25:59 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id KAA80057; Thu, 19 Aug 1999 10:25:59 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 19 Aug 1999 10:25:58 -0400 (EDT) To: current@freebsd.org Cc: alpha@freebsd.org Subject: cc -O broken in -current for Alpha KLDs X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14268.1961.256187.86499@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I do most of my development on alphas & I just turned some local code into a loadable kernel module. It works fine when compiled into the kernel statically, but fails miserably when loaded into an alpha kernel as a module. This alpha is running -current from monday or so. After a day or so of debugging, I decided to run it on an x86 -- it ran just fine. I've narrowed the problem down to one involving optimization and have extracted a simple, reproducable test case. When the test module is loaded without optimization (CFLAGS += -g -O0), it prints the following (which is correct): &Xmit_completes[2].unused = 0xfffffe00056fd0f0 &Xmit_completes[2].start_sanity = 0xfffffe00056fd0f8 &Xmit_completes[2].send_msg = 0xfffffe00056fd100 &Xmit_completes[2].io_func = 0xfffffe00056fd108 &Xmit_completes[2].arg = 0xfffffe00056fd110 &Xmit_completes[2].end_sanity = 0xfffffe00056fd118 Xmit_completes[2].unused = 0 Xmit_completes[2].start_sanity = 2 Xmit_completes[2].send_msg = 0 Xmit_completes[2].io_func = 0 Xmit_completes[2].arg = 0 Xmit_completes[2].end_sanity = -2 With the normal CFLAGS, it prints: &Xmit_completes[2].unused = 0xfffffe00056fd050 &Xmit_completes[2].start_sanity = 0xfffffe00056fd058 &Xmit_completes[2].send_msg = 0xfffffe00056fd060 &Xmit_completes[2].io_func = 0xfffffe00056fd068 &Xmit_completes[2].arg = 0xfffffe00056fd070 &Xmit_completes[2].end_sanity = 0xfffffe00056fd078 Xmit_completes[2].unused = -2 Xmit_completes[2].start_sanity = 0 Xmit_completes[2].send_msg = 0 Xmit_completes[2].io_func = 0 Xmit_completes[2].arg = 0 Xmit_completes[2].end_sanity = 0 If you look at the array in gdb (or print it all) you notice that the "unused" field has taken all the writes intended for the "end_sanity" fields, and all the writes intended for "start_sanity" have disappeared. I'm using the following Makefile to build the module: .PATH: /usr/project/ari1/users/gallatin/hacks/simple KMOD = simple SRCS += simple.c CFLAGS += -g .include The module contains the following code: /**************** start ************************/ #include #include #include #include #define SHMEM_PAYLOAD_SIZE 30 typedef struct _shmem_ctrl_msg { uint pkt_header; uint ctl_length; /* this is all sent as a message */ uint pkt_length; uint gather_length; uint pkt_type; uint shmem_payload[SHMEM_PAYLOAD_SIZE]; uint pad; } ctrl_msg; typedef void (*io_completion_t)(void *, int, caddr_t); typedef struct _io_complete { long unused; long start_sanity; ctrl_msg *send_msg; io_completion_t io_func; caddr_t arg; long end_sanity; }io_completions; #define NUM_RING_ENTRIES 128 io_completions Xmit_completes[NUM_RING_ENTRIES]; static void simple_init(void) { int i; printf("&Xmit_completes[2].unused = %p\n", &Xmit_completes[2].unused); printf("&Xmit_completes[2].start_sanity = %p\n", &Xmit_completes[2].start_sanity); printf("&Xmit_completes[2].send_msg = %p\n", &Xmit_completes[2].send_msg); printf("&Xmit_completes[2].io_func = %p\n", &Xmit_completes[2].io_func); printf("&Xmit_completes[2].arg = %p\n", &Xmit_completes[2].arg); printf("&Xmit_completes[2].end_sanity = %p\n", &Xmit_completes[2].end_sanity); bzero(Xmit_completes, NUM_RING_ENTRIES*sizeof(io_completions)); for (i = 0; i < NUM_RING_ENTRIES; i++){ Xmit_completes[i].io_func = NULL; Xmit_completes[i].send_msg = NULL; Xmit_completes[i].start_sanity = (long)i; Xmit_completes[i].end_sanity = -1LL*(long)i; } printf("Xmit_completes[2].unused = %ld\n", Xmit_completes[2].unused); printf("Xmit_completes[2].start_sanity = %ld\n", Xmit_completes[2].start_sanity); printf("Xmit_completes[2].send_msg = %p\n", Xmit_completes[2].send_msg); printf("Xmit_completes[2].io_func = %p\n", Xmit_completes[2].io_func); printf("Xmit_completes[2].arg = %p\n", Xmit_completes[2].arg); printf("Xmit_completes[2].end_sanity = %ld\n", Xmit_completes[2].end_sanity); } static int simple_modevent(module_t mod, int type, void *unused) { switch (type) { case MOD_LOAD: /* load */ simple_init(); break; case MOD_UNLOAD: /* unload */ break; default: break; } return 0; } moduledata_t simple_mod = {"simple", simple_modevent, 0}; DECLARE_MODULE(simple, simple_mod, SI_SUB_DRIVERS, SI_ORDER_ANY); /************ end **********************/ Any help would be appreciated. I'm currently trying to see if the problem occurs in egcs 2.95 (from ports). But it currently doesn't build.. Thanks, 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 Thu Aug 19 13: 9:21 1999 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 4C6531516C for ; Thu, 19 Aug 1999 13:09:10 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id QAA03794 for ; Thu, 19 Aug 1999 16:07:57 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id QAA80859; Thu, 19 Aug 1999 16:07:56 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 19 Aug 1999 16:07:55 -0400 (EDT) To: freebsd-alpha@freebsd.org Subject: New Iprobe for FreeBSD with EV6 support X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14268.25064.416927.15727@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Get it while its hot: A new version of Iprobe which supports the EV6 is now available. See http://www.cs.duke.edu/ari/iprobe.html for a pointer to the tarball & some instructions. See http://www.alphalinux.org/iprobe for a description of Iprobe. I strongly recommend anybody who is making optimizations to anything (including the FreeBSD kernel) use Iprobe on an alpha in addition to traditional profiling on other platforms. Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Aug 19 19:20:31 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 1DA3915232; Thu, 19 Aug 1999 19:20:22 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id DAA21492; Fri, 20 Aug 1999 03:28:06 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 20 Aug 1999 03:28:06 +0100 (BST) From: Doug Rabson To: Andrew Gallatin Cc: current@FreeBSD.ORG, alpha@FreeBSD.ORG Subject: Re: cc -O broken in -current for Alpha KLDs In-Reply-To: <14268.1961.256187.86499@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 19 Aug 1999, Andrew Gallatin wrote: > > I do most of my development on alphas & I just turned some local code > into a loadable kernel module. It works fine when compiled into the > kernel statically, but fails miserably when loaded into an alpha > kernel as a module. This alpha is running -current from monday or > so. > > After a day or so of debugging, I decided to run > it on an x86 -- it ran just fine. I've narrowed the problem down to > one involving optimization and have extracted a simple, reproducable > test case. > > When the test module is loaded without optimization (CFLAGS += -g > -O0), it prints the following (which is correct): It looks like we aren't handling the relocations correctly. When I get a chance, I will try to look at it. If you want to have another look, the code at fault is probably in alpha/alpha/elf_machdep.c and you can get a list of relocations in the module with 'objdump --dynamic-reloc foo.ko'. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Aug 20 0:33:41 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from gateway.blackstar.nl (blackstar.xs4all.nl [194.109.62.97]) by hub.freebsd.org (Postfix) with ESMTP id A199A15287 for ; Fri, 20 Aug 1999 00:33:38 -0700 (PDT) (envelope-from bvermeul@devel.blackstar.nl) Received: from devel.blackstar.nl (root@devel.blackstar.nl [192.168.2.2]) by gateway.blackstar.nl (8.8.7/8.8.7) with ESMTP id JAA04413 for ; Fri, 20 Aug 1999 09:04:41 +0200 Received: from localhost (bvermeul@localhost) by devel.blackstar.nl (8.9.3/8.9.3) with ESMTP id JAA12658 for ; Fri, 20 Aug 1999 09:33:31 +0200 Date: Fri, 20 Aug 1999 09:33:30 +0200 (CEST) From: To: freebsd-alpha@freebsd.org Subject: Installing FreeBSD on a Multia? 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 Hello *, I am trying to install FreeBSD on my multia, but am encountering some problems. I've got the boot-images, can even get the kernel disk to load, but when it starts booting my screen blanks out (The Multia has a TGA video in it, works like a framebuffer). I was wondering if you've got some advice, pointers or general help getting FreeBSD to install on this box. Thanks in advance, Bas Vermeulen -- "God, root, what is difference?" -- Pitr, User Friendly -- Pitr, User Friendly "God is more forgiving." -- Dave Aronson -- Dave Aronson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Aug 20 5:33:29 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 7954D14E1A; Fri, 20 Aug 1999 05:33:24 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id A5E621C1F; Fri, 20 Aug 1999 20:32:25 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Rabson Cc: Andrew Gallatin , current@FreeBSD.ORG, alpha@FreeBSD.ORG Subject: Re: cc -O broken in -current for Alpha KLDs In-reply-to: Your message of "Fri, 20 Aug 1999 03:28:06 +0100." Date: Fri, 20 Aug 1999 20:32:25 +0800 From: Peter Wemm Message-Id: <19990820123225.A5E621C1F@overcee.netplex.com.au> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug Rabson wrote: > On Thu, 19 Aug 1999, Andrew Gallatin wrote: > > > > > I do most of my development on alphas & I just turned some local code > > into a loadable kernel module. It works fine when compiled into the > > kernel statically, but fails miserably when loaded into an alpha > > kernel as a module. This alpha is running -current from monday or > > so. > > > > After a day or so of debugging, I decided to run > > it on an x86 -- it ran just fine. I've narrowed the problem down to > > one involving optimization and have extracted a simple, reproducable > > test case. > > > > When the test module is loaded without optimization (CFLAGS += -g > > -O0), it prints the following (which is correct): > > It looks like we aren't handling the relocations correctly. When I get a > chance, I will try to look at it. If you want to have another look, the > code at fault is probably in alpha/alpha/elf_machdep.c and you can get a > list of relocations in the module with 'objdump --dynamic-reloc foo.ko'. I thought of that before I went to sleep this morning too.. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Aug 20 7:29:49 1999 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 E36B814BCF; Fri, 20 Aug 1999 07:29:44 -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.1/8.9.1) with ESMTP id KAA08361; Fri, 20 Aug 1999 10:27:46 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id KAA91199; Fri, 20 Aug 1999 10:27:46 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 20 Aug 1999 10:27:35 -0400 (EDT) To: Doug Rabson Cc: current@FreeBSD.ORG, alpha@FreeBSD.ORG Subject: Re: cc -O broken in -current for Alpha KLDs In-Reply-To: References: <14268.1961.256187.86499@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14269.25728.498019.956479@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug Rabson writes: > On Thu, 19 Aug 1999, Andrew Gallatin wrote: > > > > > I do most of my development on alphas & I just turned some local code > > into a loadable kernel module. It works fine when compiled into the > > kernel statically, but fails miserably when loaded into an alpha > > kernel as a module. This alpha is running -current from monday or > > so. > > > > After a day or so of debugging, I decided to run > > it on an x86 -- it ran just fine. I've narrowed the problem down to > > one involving optimization and have extracted a simple, reproducable > > test case. > > > > When the test module is loaded without optimization (CFLAGS += -g > > -O0), it prints the following (which is correct): > > It looks like we aren't handling the relocations correctly. When I get a > chance, I will try to look at it. If you want to have another look, the > code at fault is probably in alpha/alpha/elf_machdep.c and you can get a > list of relocations in the module with 'objdump --dynamic-reloc foo.ko'. Thanks for the pointer, it was right on the money. It turns out that at the default optimization level, the objdump output looks like this: <...> 0000000000010ea8 RELATIVE *ABS* 0000000000010e80 GLOB_DAT Xmit_completes+0x0000000000000028 0000000000010e88 GLOB_DAT Xmit_completes+0x0000000000000008 0000000000010e90 GLOB_DAT Xmit_completes+0x0000000000000010 0000000000010e98 GLOB_DAT Xmit_completes+0x0000000000000018 0000000000010ea0 GLOB_DAT Xmit_completes 0000000000010e70 JMP_SLOT printf <...> I've just committed a patch to alpha/alpha/elf_machdep.c which takes into account the addends for objects of type R_ALPHA_GLOB_DAT. This fixes my problem. Should it be MFC'ed? Thanks again, 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 Fri Aug 20 9:49:11 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5288414C01 for ; Fri, 20 Aug 1999 09:49:03 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id JAA04254; Fri, 20 Aug 1999 09:48:36 -0700 Date: Fri, 20 Aug 1999 09:48:35 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: bvermeul@blackstar.nl Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Installing FreeBSD on a Multia? 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 Have to use a serial console. No support for TGA framebuffer. There's a bootstrap raw disk image in http://www.freebsd.org/~mjacob if you want to try dd'ing that from another OS onto a disk so you can get up and running quickly- although the serial console install seems to work pretty well. On Fri, 20 Aug 1999 bvermeul@blackstar.nl wrote: > Hello *, > > I am trying to install FreeBSD on my multia, but am encountering some > problems. I've got the boot-images, can even get the kernel disk to load, > but when it starts booting my screen blanks out (The Multia has a TGA > video in it, works like a framebuffer). I was wondering if you've got some > advice, pointers or general help getting FreeBSD to install on this box. > > Thanks in advance, > > Bas Vermeulen > > -- > "God, root, what is difference?" -- Pitr, User Friendly > -- Pitr, User Friendly > > "God is more forgiving." -- Dave Aronson > -- Dave Aronson > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Aug 20 9:54:30 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8AE2F15259 for ; Fri, 20 Aug 1999 09:54:23 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA56387; Fri, 20 Aug 1999 10:52:57 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA37326; Fri, 20 Aug 1999 10:52:58 -0600 (MDT) Message-Id: <199908201652.KAA37326@harmony.village.org> To: Peter Wemm Subject: Re: rman_get_virtual() on alpha Cc: Doug Rabson , alpha@FreeBSD.ORG In-reply-to: Your message of "Thu, 19 Aug 1999 00:09:49 +0800." <19990818160949.97E171C1F@overcee.netplex.com.au> References: <19990818160949.97E171C1F@overcee.netplex.com.au> Date: Fri, 20 Aug 1999 10:52:58 -0600 From: Warner Losh Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <19990818160949.97E171C1F@overcee.netplex.com.au> Peter Wemm writes: : I pretty much think the whole point of doing a mapping at all (in dense : mode) is so we can go direct and bypass the bus_space_* macros, with the : obvious peril of doing that of course. bus_space_* macros etc have a : specific setup in NetBSD which we don't really have a parallel of, and : probably should as this would solve this problem for working with the : bus_space style interfaces as well. I've been bringing in the newer NetBSD bus space stuff as part of the newconfig + pccard work that I've been doing. I can post what I've done so far. The bus_space_map and bus_subspace_map could likely be better. The one down side of how I've done it is that both the bus_*_t types that were simple integers are now structs... Is there interest in my work here? I've been running it on my intel machine and I've had no instabilities with it (which is kinda scary given the extent of the changes I've made to the bus stuff). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Aug 20 9:55:18 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id B8170154A6 for ; Fri, 20 Aug 1999 09:55:14 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id MAA16752; Fri, 20 Aug 1999 12:52:30 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Fri, 20 Aug 1999 12:52:30 -0400 (EDT) From: Chuck Robey To: Matthew Jacob Cc: bvermeul@blackstar.nl, freebsd-alpha@FreeBSD.ORG Subject: Re: Installing FreeBSD on a Multia? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 20 Aug 1999, Matthew Jacob wrote: > > Have to use a serial console. No support for TGA framebuffer. > There's a bootstrap raw disk image in http://www.freebsd.org/~mjacob if > you want to try dd'ing that from another OS onto a disk so you can get up > and running quickly- although the serial console install seems to work > pretty well. From what I've recently learned, using a Multia is a Really Bad Idea. Yes, they are cheap, but that's the ONLY good thing about them. Both David O'Brien and Peter Wemm were able to burn their's out just by doing make worlds. They are underpowered, overheated, undersized, but very very cheap. Ever wonder why? You get what you pay for. Doing it with the PC164* motherboards is pretty comparable to building a PC from a good Intel motherboard, and you'll have much better experiences in doing it. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Aug 20 10:20:50 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 6F8A01523D for ; Fri, 20 Aug 1999 10:20:47 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA04370; Fri, 20 Aug 1999 10:17:13 -0700 Date: Fri, 20 Aug 1999 10:17:12 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Chuck Robey Cc: bvermeul@blackstar.nl, freebsd-alpha@FreeBSD.ORG Subject: Re: Installing FreeBSD on a Multia? 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 > >From what I've recently learned, using a Multia is a Really Bad Idea. > Yes, they are cheap, but that's the ONLY good thing about them. Both > David O'Brien and Peter Wemm were able to burn their's out just by doing > make worlds. They are underpowered, overheated, undersized, but very > very cheap. Ever wonder why? > > You get what you pay for. Doing it with the PC164* motherboards is > pretty comparable to building a PC from a good Intel motherboard, and > you'll have much better experiences in doing it. No question about that. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Aug 20 15:26:31 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 05E4A15264 for ; Fri, 20 Aug 1999 15:26:22 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id SAA17690 for ; Fri, 20 Aug 1999 18:25:17 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Fri, 20 Aug 1999 18:25:17 -0400 (EDT) From: Chuck Robey To: FreeBSD-Alpha Subject: metal stickers Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You know those little tin plates that WC sells, they have the FreeBSD logo on them, for mounting on PC cases? Sure would be nice if there was a version for the Alpha. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Aug 20 17:24:59 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 2531014C19 for ; Fri, 20 Aug 1999 17:24:57 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA42133; Fri, 20 Aug 1999 17:24:36 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Chuck Robey Cc: FreeBSD-Alpha Subject: Re: metal stickers In-reply-to: Your message of "Fri, 20 Aug 1999 18:25:17 EDT." Date: Fri, 20 Aug 1999 17:24:36 -0700 Message-ID: <42130.935195076@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just put your alpha in a PC case or find someplace on the outside.. :) The case plates themselves are architecture-neutral. > You know those little tin plates that WC sells, they have the FreeBSD > logo on them, for mounting on PC cases? > > Sure would be nice if there was a version for the Alpha. > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@picnic.mat.net | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. > (301) 220-2114 | > ----------------------------+----------------------------------------------- > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Aug 20 17:49:40 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id E959315013 for ; Fri, 20 Aug 1999 17:49:34 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id UAA18203; Fri, 20 Aug 1999 20:46:02 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Fri, 20 Aug 1999 20:46:02 -0400 (EDT) From: Chuck Robey To: "Jordan K. Hubbard" Cc: FreeBSD-Alpha Subject: Re: metal stickers In-Reply-To: <42130.935195076@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 20 Aug 1999, Jordan K. Hubbard wrote: > Just put your alpha in a PC case or find someplace on the outside.. :) > The case plates themselves are architecture-neutral. You missed the point, Jordan, my Alpha IS in a PC case, and I AM going to use the normal FreeBSD sticker, but if there was one that allowed you to show it was FreeBSD/Alpha, that'd be neat. I know where to put the sticker, it's what the sticker shows that I'm wishing could be Alpha-ized. If that was entirely uneconomical (I could understand that) then is there any likelyhood of one of the flat, paper-like sticker-sheets (you know the kind I mean, has about 6 FreeBSD logos on it) could be Alpha-customized? > > You know those little tin plates that WC sells, they have the FreeBSD > > logo on them, for mounting on PC cases? > > > > Sure would be nice if there was a version for the Alpha. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Aug 20 17:57:42 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 4E68E15013 for ; Fri, 20 Aug 1999 17:57:40 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA42290; Fri, 20 Aug 1999 17:56:43 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Chuck Robey Cc: "Jordan K. Hubbard" , FreeBSD-Alpha Subject: Re: metal stickers In-reply-to: Your message of "Fri, 20 Aug 1999 20:46:02 EDT." Date: Fri, 20 Aug 1999 17:56:43 -0700 Message-ID: <42287.935197003@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > You missed the point, Jordan, my Alpha IS in a PC case, and I AM going > to use the normal FreeBSD sticker, but if there was one that allowed you > to show it was FreeBSD/Alpha, that'd be neat. I know where to put the > sticker, it's what the sticker shows that I'm wishing could be > Alpha-ized. Ah, considering the (extremely small) size of the Alpha market currently, I don't think it's worth it yet. :( - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Aug 20 18: 6:17 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 0C6C915013 for ; Fri, 20 Aug 1999 18:06:14 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id VAA18243; Fri, 20 Aug 1999 21:04:47 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Fri, 20 Aug 1999 21:04:47 -0400 (EDT) From: Chuck Robey To: "Jordan K. Hubbard" Cc: FreeBSD-Alpha Subject: Re: metal stickers In-Reply-To: <42287.935197003@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 20 Aug 1999, Jordan K. Hubbard wrote: > > You missed the point, Jordan, my Alpha IS in a PC case, and I AM going > > to use the normal FreeBSD sticker, but if there was one that allowed you > > to show it was FreeBSD/Alpha, that'd be neat. I know where to put the > > sticker, it's what the sticker shows that I'm wishing could be > > Alpha-ized. > > Ah, considering the (extremely small) size of the Alpha market > currently, I don't think it's worth it yet. :( OK, how about a smaller step then ... I haven't any artistic ability (I peaked at finger painting), but if your art department there ever had time to do any versions of Chuckie with some kind of Alpha lettering overlaid (or something like that) then just the artwork would be nice. I could run that thru my HP color printer, and maybe have something I could then display. Doesn't have to be today, either (or this month). This year would be nice. You might do one with X86 on it too, for the Intel market. > > - Jordan > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Aug 20 21: 3:33 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 0F8E015373 for ; Fri, 20 Aug 1999 21:03:31 -0700 (PDT) (envelope-from kris@airnet.net) Received: from airnet.net (tc14-216-180-35-189.dialup.HiWAAY.net [216.180.35.189]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id XAA01241 for ; Fri, 20 Aug 1999 23:03:22 -0500 (CDT) Message-ID: <37BE2508.76F9F915@airnet.net> Date: Fri, 20 Aug 1999 23:03:20 -0500 From: Kris Kirby Organization: Non Illegitemus Carborundum. X-Mailer: Mozilla 4.08 [en] (X11; U; FreeBSD 3.2-RELEASE i386) MIME-Version: 1.0 To: alpha@freebsd.org Subject: Changing default SRM font? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've looked around and didn't find anything official or otherwise about changing the default font for the SRM console on my Multia. I tried setting tga_monitor_mode(?) put it told me that was a protected area. A web page would be very nice... -- Kris Kirby ------------------------------------------- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Aug 21 2: 8:15 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id B110C14C9C; Sat, 21 Aug 1999 02:08:04 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA70590; Sat, 21 Aug 1999 10:14:39 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 21 Aug 1999 10:14:39 +0100 (BST) From: Doug Rabson To: Andrew Gallatin Cc: current@FreeBSD.ORG, alpha@FreeBSD.ORG Subject: Re: cc -O broken in -current for Alpha KLDs In-Reply-To: <14269.25728.498019.956479@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 20 Aug 1999, Andrew Gallatin wrote: > > Doug Rabson writes: > > On Thu, 19 Aug 1999, Andrew Gallatin wrote: > > > > > > > > I do most of my development on alphas & I just turned some local code > > > into a loadable kernel module. It works fine when compiled into the > > > kernel statically, but fails miserably when loaded into an alpha > > > kernel as a module. This alpha is running -current from monday or > > > so. > > > > > > After a day or so of debugging, I decided to run > > > it on an x86 -- it ran just fine. I've narrowed the problem down to > > > one involving optimization and have extracted a simple, reproducable > > > test case. > > > > > > When the test module is loaded without optimization (CFLAGS += -g > > > -O0), it prints the following (which is correct): > > > > It looks like we aren't handling the relocations correctly. When I get a > > chance, I will try to look at it. If you want to have another look, the > > code at fault is probably in alpha/alpha/elf_machdep.c and you can get a > > list of relocations in the module with 'objdump --dynamic-reloc foo.ko'. > > Thanks for the pointer, it was right on the money. It turns out that > at the default optimization level, the objdump output looks like this: > > <...> > 0000000000010ea8 RELATIVE *ABS* > 0000000000010e80 GLOB_DAT Xmit_completes+0x0000000000000028 > 0000000000010e88 GLOB_DAT Xmit_completes+0x0000000000000008 > 0000000000010e90 GLOB_DAT Xmit_completes+0x0000000000000010 > 0000000000010e98 GLOB_DAT Xmit_completes+0x0000000000000018 > 0000000000010ea0 GLOB_DAT Xmit_completes > 0000000000010e70 JMP_SLOT printf > <...> > > I've just committed a patch to alpha/alpha/elf_machdep.c which takes > into account the addends for objects of type R_ALPHA_GLOB_DAT. This > fixes my problem. Should it be MFC'ed? I think it can be MFC'ed right away. There are no dependancies on the rest of the system and its a serious problem. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Aug 21 4:28:27 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from noses.com (noses.com [195.247.233.1]) by hub.freebsd.org (Postfix) with ESMTP id 4034414FA3 for ; Sat, 21 Aug 1999 04:28:22 -0700 (PDT) (envelope-from ap@noses.com) Received: (from ap@localhost) by noses.com (8.8.8/8.8.5) id NAA18179 for freebsd-alpha@freebsd.org; Sat, 21 Aug 1999 13:22:38 +0200 (CEST) From: Achim Patzner Message-Id: <199908211122.NAA18179@noses.com> Subject: Re: Installing FreeBSD on a Multia To: freebsd-alpha@freebsd.org Date: Sat, 21 Aug 1999 13:22:38 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org : From what I've recently learned, using a Multia is a Really Bad Idea. : Yes, they are cheap, but that's the ONLY good thing about them. Both : David O'Brien and Peter Wemm were able to burn their's out just by doing : make worlds. They are underpowered, overheated, undersized, but very : very cheap. Ever wonder why? Mine died after I tried installing NetBSD (which doesn't really mean that NetBSD is that bad an OS 8-) ). I paid about USD 60 for each hour it ran. But as the NetBSD people (obviously - they started quite a bit earlier) had lots of them they started repairing them (better: improving their health 8-) ). Take a look in the NetBSD/alpha archives to find out more about un-frying Multias. Achim Subject: more Multia repair part numbers and comments To: None From: Ross Harvey List: port-alpha Date: 04/28/1998 02:35:15 OK, so I borrowed a supposedly dead Multia. Murphy's law is in fine form, though...when you _want_ a dead one, _specify_ a dead one, really can only _use_ a dead one (for the purpose of doing a friend a favor and testing the big multia fix) ...then...of course...it arrives and works just fine. Now that I've seen the parts, the bad news is that they aren't likely to be in any catalog...good thing for me no one took up my offer on that bet. AFAICT it is going to be necessary to order them through one of the manufacturer's franchised distributors, and they can be difficult when you don't already have an account. Sometimes you can order samples through a web page, and certainly you can locate the distributer that way. The generic thing you want is: (qty 6) a 20-lead .220 (i.e., medium body) soic 4.7K bussed (pullup) resistor network, with lead 20 as the common. I think the Bournes parts are probably safe, I guess it was a bad batch, or possibly that thick-film part didn't like actually being _in_ the solderwave, which is what would have happened given that these components are on the bottom of the board. And, I can now see why the Jupiter guys replaced the logic IC: on Tim's Multia the printing on the chip is starting to bake into a brownish off-white right in the center, i.e., over the die. I think it needs to go too, although using thermally conductive epoxy you could conceivably heatsink it...not much room to work with though. The 5% is perfectly fine as a tolerance, but if it is out of stock and the 2% or 1% is in stock... WhichOne Mfr Part Number R-network Bournes 4820P-002-472 R-network Dale SOMC2001472J (5%) R-network Dale SOMC2001472G (2%) R-network Dale SOMC2001472F (1%) ...there are probably more... Logic-IC TI SN74ABT623DW Logic-IC Philips 74ABT623D Logic-IC Pericom PI74FCT623TS Logic-IC Pericom PI74FCT623ATS Logic-IC Pericom PI74FCT623CTS Logic-IC Pericom PI74FCT623DTS Logic-IC IDT IDT74FCT623TSO Logic-IC IDT IDT74FCT623ATSO Logic-IC IDT IDT74FCT623CTSO ...there probably are not any more... This is almost trivial with the right lab, but it definitely isn't the easiest home project. Besides the difficulty of obtaining the components, you have 140 leads to remove and resolder...and you don't want to lift or destroy a single pad while doing it. At least it is a lot easier than if they were those ugly old dips. Ross Harvey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message