From owner-freebsd-alpha Sun Oct 1 3:14:47 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 3E4B737B502 for ; Sun, 1 Oct 2000 03:14:43 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13fg8n-0007ig-00 for freebsd-alpha@freebsd.org; Sun, 01 Oct 2000 10:14:41 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e91AFQ211442 for freebsd-alpha@freebsd.org; Sun, 1 Oct 2000 12:15:26 +0200 (CEST) (envelope-from wkb) Date: Sun, 1 Oct 2000 12:15:26 +0200 From: Wilko Bulte To: FreeBSD-alpha mailing list Subject: status of -current Message-ID: <20001001121526.A11426@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi there, Having been quite busy with Real Life[tm] stuff I wonder where -current for alpha is at the moment? Things like the (in)famous loader thing etc come to mind. Reason for asking is that I found myself a spare alpha at work which I can dedicate to hold a CVS repo and use as a builder. I could then go on to use the various alpha models my employer conveniently supplies me with ;-) to do some testing. NB: is there any way to cvsup via a HTTP/FTP proxy? Bloody corporate firewall etc.. Thanks, -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Oct 1 3:33:41 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 31CB037B66D for ; Sun, 1 Oct 2000 03:33:35 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id GAA39416; Sun, 1 Oct 2000 06:33:28 -0400 (EDT) Date: Sun, 1 Oct 2000 06:33:27 -0400 (EDT) From: "Matthew N. Dodd" To: Khamba Staring Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: 3c509 isa cards on an AXPPCI33..? In-Reply-To: <200009301704.e8UH43u11199@francine.edoropolis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 30 Sep 2000, Khamba Staring wrote: > Does anyone know FreeBSD 4.1 alpha release has 3c509 isa card support? > I remember the 3.1 release didn't have support yet.. I suspect it would work just fine. I'll toss one in my AXPPCI33 and do some testing at some point. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Oct 1 4:29:53 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id D2CE037B503 for ; Sun, 1 Oct 2000 04:29:48 -0700 (PDT) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e91BTTx03103 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Sun, 1 Oct 2000 13:29:41 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e91BTr547538; Sun, 1 Oct 2000 13:29:55 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.11.0/8.9.2) id e91BTpa85247; Sun, 1 Oct 2000 13:29:51 +0200 (CEST) (envelope-from ticso) Date: Sun, 1 Oct 2000 13:29:50 +0200 From: Bernd Walter To: Wilko Bulte Cc: FreeBSD-alpha mailing list Subject: Re: status of -current Message-ID: <20001001132950.B85200@cicely8.cicely.de> References: <20001001121526.A11426@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20001001121526.A11426@freebie.demon.nl>; from wkb@freebie.demon.nl on Sun, Oct 01, 2000 at 12:15:26PM +0200 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Oct 01, 2000 at 12:15:26PM +0200, Wilko Bulte wrote: > Having been quite busy with Real Life[tm] stuff I wonder where > -current for alpha is at the moment? Things like the (in)famous > loader thing etc come to mind. The loader works more or less now. I have some problems with the name of the kernel which is searched as kernel.ko while it gets installed as kernel. The loader crashes for me if it doesn't find the kernel ;( But maybe it's my fault as I did not put much time in maintaing the /boot dir. The kernel does not work for me on an axppci33 system but does on a pc164. The ithread patches are still problematic as I can't get my pc164 to boot at least into su-mode. > NB: is there any way to cvsup via a HTTP/FTP proxy? Bloody corporate > firewall etc.. You need at least a single outgoing tcp connect or go via ctm. Not even outgoing ssh or telnet works? If you can establish a tunnel anyhow I can setup the other end on cvsup4.de.freebsd.org -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Oct 1 13:42:49 2000 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 4389037B66C for ; Sun, 1 Oct 2000 13:42:47 -0700 (PDT) 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 OAA01412; Sun, 1 Oct 2000 14:42:45 -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 OAA02087; Sun, 1 Oct 2000 14:42:44 -0600 (MDT) Message-Id: <200010012042.OAA02087@harmony.village.org> To: Khamba Staring Subject: Re: 3c509 isa cards on an AXPPCI33..? Cc: freebsd-alpha@FreeBSD.ORG In-reply-to: Your message of "Sat, 30 Sep 2000 19:04:00 +0200." <200009301704.e8UH43u11199@francine.edoropolis.org> References: <200009301704.e8UH43u11199@francine.edoropolis.org> Date: Sun, 01 Oct 2000 14:42:44 -0600 From: Warner Losh Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200009301704.e8UH43u11199@francine.edoropolis.org> Khamba Staring writes: : Does anyone know FreeBSD 4.1 alpha release has 3c509 isa card support? : I remember the 3.1 release didn't have support yet.. You can build a kernel with 3c509 drivers in it (ep). I don't know if they actually work or not. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Oct 2 12:10:42 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from grootstal.nijmegen.inter.nl.net (grootstal.nijmegen.inter.nl.net [193.67.237.11]) by hub.freebsd.org (Postfix) with ESMTP id BE79B37B66C for ; Mon, 2 Oct 2000 12:10:37 -0700 (PDT) Received: from ntpc by grootstal.nijmegen.inter.nl.net via ztm51-33.Zoetermeer.NL.net [195.108.245.198] with SMTP id VAA18121 (8.8.8/1.19); Mon, 2 Oct 2000 21:10:30 +0200 (MET DST) Reply-To: From: "Peter Blok" To: "'Khamba Staring'" Cc: Subject: RE: 3c509 isa cards on an AXPPCI33..? Date: Mon, 2 Oct 2000 21:09:57 +0200 Message-ID: <004a01c02ca4$5b692510$8aac9f0a@ntpc> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <200009301704.e8UH43u11199@francine.edoropolis.org> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have tried it on 4.0. It compiled ok but it didn't work back then. Peter -----Original Message----- From: owner-freebsd-alpha@FreeBSD.ORG [mailto:owner-freebsd-alpha@FreeBSD.ORG]On Behalf Of Khamba Staring Sent: Saturday, September 30, 2000 19:04 To: freebsd-alpha@freebsd.org Subject: 3c509 isa cards on an AXPPCI33..? Hi, Does anyone know FreeBSD 4.1 alpha release has 3c509 isa card support? I remember the 3.1 release didn't have support yet.. Regards, -- Khamba Staring ps: I'm currently not on the freebsd-alpha mailing list. Please mail any answer to me as well.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Oct 2 16:33: 8 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.rdc1.va.home.com (ha1.rdc1.va.home.com [24.2.32.66]) by hub.freebsd.org (Postfix) with ESMTP id 1AAC137B503; Mon, 2 Oct 2000 16:33:03 -0700 (PDT) Received: from laptop.baldwin.cx ([24.6.244.187]) by mail.rdc1.va.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20001002233302.IJNU26082.mail.rdc1.va.home.com@laptop.baldwin.cx>; Mon, 2 Oct 2000 16:33:02 -0700 Content-Length: 2567 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 02 Oct 2000 16:33:03 -0700 (PDT) From: John Baldwin To: Doug Rabson Subject: Re: Status update Cc: alpha@freebsd.org, cp@bsdi.com, smp@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 26-Sep-00 Doug Rabson wrote: > On Tue, 26 Sep 2000, Doug Rabson wrote: > >> On Sat, 23 Sep 2000, John Baldwin wrote: >> > >> > There are also a few more weirdism's on the alpha. In a few places in >> > sys/kern, we call spl0() instead of splx(). I've added some debugging >> > code to >> > do a printf() if we aren't actually at IPL_0 (what spl0 used to do) after >> > the >> > mtx_exit(). It does trigger in several cases during /etc/rc at least, but >> > the >> > machine seems to be running stable regardless (I'll be running a >> > buildworld -j >> > 8 tonight to stress test it). My question is: is it ok for the code to >> > run >> > with some interrupts disabled or do we need to replace the calls to spl0() >> > with enable_intr()? >> >> I'm testing this now and I'm seeing a flood of diagnostic messages like: >> >> ../../kern/kern_fork.c:537:fork1() spl0 needs fixing >> >> I think these are all due to the fact that sched_lock is held at that >> point. The preceding mtx_exit() just decrements the recursion count. >> I haven't worked out exactly why sched_lock is held here because it >> shouldn't be. Possibly its because we don't clear pcb_schednest in >> cpu_fork(). > > As I suspected, clearing pcb_schednest makes this lot go away. Try this > version of vm_machdep.c: > > Index: vm_machdep.c > =================================================================== > RCS file: /home/ncvs/src/sys/alpha/alpha/vm_machdep.c,v > retrieving revision 1.33 > diff -u -r1.33 vm_machdep.c > --- vm_machdep.c 2000/09/07 01:32:39 1.33 > +++ vm_machdep.c 2000/09/26 08:38:55 > @@ -210,6 +210,13 @@ > up->u_pcb.pcb_context[2] = (u_long) p2; /* s2: a0 */ > up->u_pcb.pcb_context[7] = > (u_int64_t)switch_trampoline; /* ra: assembly magic */ > + > + /* > + * Clear the saved recursion count for sched_lock > + * since the child needs only one count which is > + * released in switch_trampoline. > + */ > + up->u_pcb.pcb_schednest = 0; > } > } The x86 code does this, so the alpha code should as well. Go ahead and commit this, it shouldnt' break anything. :-P I'll remove the extra cruft from the MTX_EXIT() assembly in mutex.h afterwards. > -- > Doug Rabson Mail: dfr@nlsystems.com -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 3 0:55:28 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from inetfw.sonycsl.co.jp (inetfw.SonyCSL.CO.JP [203.137.129.4]) by hub.freebsd.org (Postfix) with ESMTP id 790C837B503 for ; Tue, 3 Oct 2000 00:55:24 -0700 (PDT) Received: from hotaka.csl.sony.co.jp (hotaka.csl.sony.co.jp [43.27.98.57]) by inetfw.sonycsl.co.jp (8.9.3+3.2W/3.7Ws3/inetfw/2000050701/smtpfeed 1.07) with ESMTP id QAA80646; Tue, 3 Oct 2000 16:55:14 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by hotaka.csl.sony.co.jp (8.9.3+3.2W/3.7Ws3/hotaka/2000061722) with ESMTP id QAA62152; Tue, 3 Oct 2000 16:55:14 +0900 (JST) To: gallatin@cs.duke.edu Cc: freebsd-alpha@freebsd.org, dfr@nlsystems.com, core@kame.net Subject: Re: size problems with INVARIANTS/DIAGNOSTIC -current kernels In-Reply-To: <14806.26688.509296.391897@grasshopper.cs.duke.edu> References: <14806.26688.509296.391897@grasshopper.cs.duke.edu> X-Mailer: Mew version 1.94.2 on Emacs 20.6 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20001003165514K.kjc@csl.sony.co.jp> Date: Tue, 03 Oct 2000 16:55:14 +0900 From: Kenjiro Cho X-Dispatcher: imput version 20000228(IM140) Lines: 94 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I encountered a similar problem with a KAME snap for FreeBSD-4.1R (without INVARIANTS/DIAGNOSTIC). Apparently, my XP900 freezes at the first malloc called from the syscons sysinit. malloc sc_vtb_init sc_alloc_scr_buffer scmeminit (syscons.c) mi_startup If the kernel size is reduced by disabling IPSEC, the system boots fine. The magic number for the kernel size seems to be around 4MB. 4.1R GENERIC kernel: (OK) text data bss dec hex filename 3472108 300196 174306 3946610 3c3872 kernel KAME kernel: (NG) text data bss dec hex filename 3776569 338384 226922 4341875 424073 kernel KAME -IPSEC: (OK) text data bss dec hex filename 3502027 301172 181338 3984537 3ccc99 kernel -Kenjiro Andrew Gallatin wrote: > With an INVARIANTS/DIAGNOSTIC kernel, my -current machines are locking > up (or halting) at boot with a stack that looks like the following: > > malloc > resource_create > resource_set_string > hints_load > mi_startup > (discovered with printfs) > > At the point it hangs, there should be a trap the first time malloc > touches kmemusage (kup->ku_indx = indx;, line 203 of kern_malloc.c). > I assume this is happening the first time the kernel touches mapped > (not kseg) memory. > > Rather than taking a trap & doing the normal vm magic, the machine > just sits there. It sometimes will eventually halt. When it does, I > see > > >>>e pc > PC psr: 0 ( PC) FFFFFC00006960F8 > >>>e ra > gpr: 1A ( R26) FFFFFC00005E1F4C > > > The RA maps to XentMM: > > (gdb) l *0xFFFFFC00005E1F4C > 0xfffffc00005e1f4c is in XentMM (../../alpha/alpha/exception.s:94). > 89 PALVECT(XentMM) /* setup frame, save registers */ > 90 > 91 /* a0, a1, & a2 already set up */ > 92 ldiq a3, ALPHA_KENTRY_MM > 93 mov sp, a4 ; .loc 1 __LINE__ > 94 CALL(trap) > 95 > 96 jmp zero, exception_return > 97 END(XentMM) > > > The PC is off in the data segment (doesn't map to anything in the > kernel text). trap is 0xfffffc00005f4460 > > Hmmm.... After more debugging, I'm fairly sure this is a size issue. > A much smaller kernel (all unneeded devs, IPv6, etc, stripped out but > with INVARIANTS/DIAGNOSTIC options), boots just fine. > > I need some help here.. > > Thanks, > > Drew > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 3 1: 8: 2 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by hub.freebsd.org (Postfix) with ESMTP id D2E2337B502 for ; Tue, 3 Oct 2000 01:07:59 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-34.mail.demon.net with esmtp (Exim 2.12 #1) id 13gN7B-0007rE-0Y; Tue, 3 Oct 2000 09:07:54 +0100 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA07203; Tue, 3 Oct 2000 09:13:53 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 3 Oct 2000 09:07:50 +0100 (BST) From: Doug Rabson To: Kenjiro Cho Cc: gallatin@cs.duke.edu, freebsd-alpha@freebsd.org, core@kame.net Subject: Re: size problems with INVARIANTS/DIAGNOSTIC -current kernels In-Reply-To: <20001003165514K.kjc@csl.sony.co.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 3 Oct 2000, Kenjiro Cho wrote: > > I encountered a similar problem with a KAME snap for FreeBSD-4.1R > (without INVARIANTS/DIAGNOSTIC). > Apparently, my XP900 freezes at the first malloc called from the > syscons sysinit. > malloc > sc_vtb_init > sc_alloc_scr_buffer > scmeminit (syscons.c) > mi_startup > > If the kernel size is reduced by disabling IPSEC, the system boots fine. > The magic number for the kernel size seems to be around 4MB. > > 4.1R GENERIC kernel: (OK) > text data bss dec hex filename > 3472108 300196 174306 3946610 3c3872 kernel > KAME kernel: (NG) > text data bss dec hex filename > 3776569 338384 226922 4341875 424073 kernel > KAME -IPSEC: (OK) > text data bss dec hex filename > 3502027 301172 181338 3984537 3ccc99 kernel Could you compile a kernel with DEBUG_CLUSTER defined in machdep.c so that I can see what the system memory map looks like. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 3 1:59:17 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from inetfw.sonycsl.co.jp (inetfw.SonyCSL.CO.JP [203.137.129.4]) by hub.freebsd.org (Postfix) with ESMTP id 740A537B66F for ; Tue, 3 Oct 2000 01:59:14 -0700 (PDT) Received: from hotaka.csl.sony.co.jp (hotaka.csl.sony.co.jp [43.27.98.57]) by inetfw.sonycsl.co.jp (8.9.3+3.2W/3.7Ws3/inetfw/2000050701/smtpfeed 1.07) with ESMTP id RAA82490; Tue, 3 Oct 2000 17:59:13 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by hotaka.csl.sony.co.jp (8.9.3+3.2W/3.7Ws3/hotaka/2000061722) with ESMTP id RAA65693; Tue, 3 Oct 2000 17:59:13 +0900 (JST) To: dfr@nlsystems.com Cc: gallatin@cs.duke.edu, freebsd-alpha@freebsd.org, core@kame.net Subject: Re: size problems with INVARIANTS/DIAGNOSTIC -current kernels In-Reply-To: References: <20001003165514K.kjc@csl.sony.co.jp> X-Mailer: Mew version 1.94.2 on Emacs 20.6 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20001003175912F.kjc@csl.sony.co.jp> Date: Tue, 03 Oct 2000 17:59:12 +0900 From: Kenjiro Cho X-Dispatcher: imput version 20000228(IM140) Lines: 30 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug Rabson wrote: > Could you compile a kernel with DEBUG_CLUSTER defined in machdep.c so that > I can see what the system memory map looks like. OK. I got the following output for the KAME kernel: text data bss dec hex filename 3776913 338432 226922 4342267 4241fb kernel FreeBSD/alpha SRM disk boot, Revision 0.3 (root@beta.osd.bsdi.com, Thu Jul 27 08:00:34 GMT 2000) Memory: 262144 k Loading /boot/defaults/loader.conf /kernel data=0x3eccf0+0x3766a syms=[0x8+0x4bae0+0x8+0x35d55] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel]... Entering kernel at 0xfffffc0000330840... Memory cluster count: 3 MEMC 0: pfn 0x0 cnt 0x100 usage 0x1 MEMC 1: pfn 0x100 cnt 0x7ea3 usage 0x0 Cluster 1 contains kernel Loading chunk after kernel: 0x3d5 / 0x7fa3 MEMC 2: pfn 0x7fa3 cnt 0x5d usage 0x1 Unrecognized boot flag '0'. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. -Kenjiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 3 10:10:52 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id 0F2D037B66C; Tue, 3 Oct 2000 10:10:48 -0700 (PDT) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.11.0/8.9.3) with ESMTP id e93HC5s05621; Tue, 3 Oct 2000 19:12:06 +0200 (CEST) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Tue, 3 Oct 2000 19:12:05 +0200 (CEST) From: "O. Hartmann" To: freebsd-alpha@freebsd.org Cc: freebsd-questions@freebsd.org Subject: Digital Multia/Alpha problems 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 Dear Sirs. My problem is trivial, but essential. I lost my console on one of my Multias. There is only one message line on the bottom of the screen, but no possible input, no chance to engage ARC/SRM console. How can I bring back the console to the internal video adaptor? - MfG O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver-Abteilung des IPA IT Netz- und Systembetreuung Johannes Gutenberg-Universitaet Mainz Becherweg 21 D-55099 Mainz BRD/Germany Tel: +496131/3924662 FAX: +496131/3923235 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 3 10:31:52 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 5BF3F37B502; Tue, 3 Oct 2000 10:31:38 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13gVuj-000G3p-00; Tue, 03 Oct 2000 17:31:37 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e93HXXt01120; Tue, 3 Oct 2000 19:33:33 +0200 (CEST) (envelope-from wkb) Date: Tue, 3 Oct 2000 19:33:33 +0200 From: Wilko Bulte To: "O. Hartmann" Cc: freebsd-alpha@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Digital Multia/Alpha problems Message-ID: <20001003193332.A1101@freebie.demon.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from ohartman@ipamzlx.physik.uni-mainz.de on Tue, Oct 03, 2000 at 07:12:05PM +0200 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Oct 03, 2000 at 07:12:05PM +0200, O. Hartmann wrote: > Dear Sirs. > My problem is trivial, but essential. I lost my console > on one of my Multias. There is only one message line on > the bottom of the screen, but no possible input, no chance to > engage ARC/SRM console. How can I bring back the console to the > internal video adaptor? If you don't connect a keyboard all output/input for the console goes (should go) to the serial port. 9600N81. You know FreeBSD/alpha does not support the builtin-TGA as a console device!? Please read HARDWARE.TXT Wilko [who is reviving some Multia's as we speak] -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 3 11:55:25 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 6205737B502 for ; Tue, 3 Oct 2000 11:55:22 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13gXDk-000HR1-00 for freebsd-alpha@freebsd.org; Tue, 03 Oct 2000 18:55:20 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e93I7f401328 for freebsd-alpha@freebsd.org; Tue, 3 Oct 2000 20:07:41 +0200 (CEST) (envelope-from wkb) Date: Tue, 3 Oct 2000 20:07:41 +0200 From: Wilko Bulte To: FreeBSD-alpha mailing list Subject: max memory on Alpha? Message-ID: <20001003200741.A1318@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What is the currently max supported memory size on Alpha? 2Gb maybe? Or will 4Gb also be OK? Reason for asking is that I want to try a AS8400 who is equipped with 3x 4Gb memory module. -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 3 12: 1:15 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2CA3C37B66D for ; Tue, 3 Oct 2000 12:01:13 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA29334; Tue, 3 Oct 2000 12:01:09 -0700 Date: Tue, 3 Oct 2000 11:57:55 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: FreeBSD-alpha mailing list Subject: Re: max memory on Alpha? In-Reply-To: <20001003200741.A1318@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 3 Oct 2000, Wilko Bulte wrote: > What is the currently max supported memory size on Alpha? 2Gb maybe? > Or will 4Gb also be OK? > > Reason for asking is that I want to try a AS8400 who is equipped > with 3x 4Gb memory module. I've run 8400s up to 2GB. Any more than that and you'll find that S/G DMA hasn't been finished ;-). Also, haha, you'll find that ECC errors aren't corrected, since TLASER screwed the pooch wrt ALPHA spec and requires you to run around and fix ECC errors induced by the I/O boards. Since I now, for the first time in 4 years, have a real external customer who actually might run TLAser, I guess I'd better finish this, hadn't I? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 3 12:26:56 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 4160C37B503 for ; Tue, 3 Oct 2000 12:26:54 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13gXiG-0006f7-00; Tue, 03 Oct 2000 19:26:53 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e93JSlA01931; Tue, 3 Oct 2000 21:28:47 +0200 (CEST) (envelope-from wkb) Date: Tue, 3 Oct 2000 21:28:47 +0200 From: Wilko Bulte To: Matthew Jacob Cc: FreeBSD-alpha mailing list Subject: Re: max memory on Alpha? Message-ID: <20001003212847.A1868@freebie.demon.nl> References: <20001003200741.A1318@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Tue, Oct 03, 2000 at 11:57:55AM -0700 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Oct 03, 2000 at 11:57:55AM -0700, Matthew Jacob wrote: > On Tue, 3 Oct 2000, Wilko Bulte wrote: > > > What is the currently max supported memory size on Alpha? 2Gb maybe? > > Or will 4Gb also be OK? > > > > Reason for asking is that I want to try a AS8400 who is equipped > > with 3x 4Gb memory module. > > I've run 8400s up to 2GB. Any more than that and you'll find that S/G > DMA hasn't been finished ;-). Well, on 12Gb it panics with pmap_foo on 4.1-R ;-) Might this mean it cannot create the necessary page table admin on > 2Gb? Do you know *if* there is a hard limit at 2Gb? > Also, haha, you'll find that ECC errors aren't corrected, since TLASER screwed > the pooch wrt ALPHA spec and requires you to run around and fix ECC errors > induced by the I/O boards. Que? This is real UNIX[tm]: expect nothing but flawless hardware (like the error free disk packs on the PDP; worth their weight in gold ;-) > Since I now, for the first time in 4 years, have a real external customer who > actually might run TLAser, I guess I'd better finish this, hadn't I? Well, I'd like to impress a few of the T64 folks. BTW: it has 8 EV5/625 CPUs, so it is a good SMP testbed as well. W/ -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 3 12:32:12 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 09C8E37B502 for ; Tue, 3 Oct 2000 12:32:10 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA29469; Tue, 3 Oct 2000 12:32:01 -0700 Date: Tue, 3 Oct 2000 12:28:46 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: FreeBSD-alpha mailing list Subject: Re: max memory on Alpha? In-Reply-To: <20001003212847.A1868@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Tue, Oct 03, 2000 at 11:57:55AM -0700, Matthew Jacob wrote: > > On Tue, 3 Oct 2000, Wilko Bulte wrote: > > > > > What is the currently max supported memory size on Alpha? 2Gb maybe? > > > Or will 4Gb also be OK? > > > > > > Reason for asking is that I want to try a AS8400 who is equipped > > > with 3x 4Gb memory module. > > > > I've run 8400s up to 2GB. Any more than that and you'll find that S/G > > DMA hasn't been finished ;-). > > Well, on 12Gb it panics with pmap_foo off the top of my head> on 4.1-R ;-) Might this mean it cannot create the > necessary page table admin on > 2Gb? > > Do you know *if* there is a hard limit at 2Gb? I dunno. Doug would be the one to know. I was supposed to look into this for the Rawhide, but all I ever got was 1.5GB. I could do a book exercise and look at it, but (see below). > > > Also, haha, you'll find that ECC errors aren't corrected, since TLASER screwed > > the pooch wrt ALPHA spec and requires you to run around and fix ECC errors > > induced by the I/O boards. > > Que? This is real UNIX[tm]: expect nothing but flawless hardware > (like the error free disk packs on the PDP; worth their weight in gold ;-) Feh. Quote from a DEC Field Service Tech, 1977, Portland Oregon, after replacing the RP06 for the 4th time: "Damned Unix does single 512 byte sector I/O all over the pack- RP06 was designed for RSTS with 8 block clustering....." > > > Since I now, for the first time in 4 years, have a real external customer who > > actually might run TLAser, I guess I'd better finish this, hadn't I? > > Well, I'd like to impress a few of the T64 folks. BTW: it has 8 EV5/625 > CPUs, so it is a good SMP testbed as well. Yes- I'm still struggling to clear a block of time to help more with this. I had to move offices and other stuff happened as well - I'm still about 1.5 meters underwater. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 3 12:42:49 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id E9ABA37B503 for ; Tue, 3 Oct 2000 12:42:46 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13gXxd-0006ul-00; Tue, 03 Oct 2000 19:42:45 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e93Jiex02092; Tue, 3 Oct 2000 21:44:40 +0200 (CEST) (envelope-from wkb) Date: Tue, 3 Oct 2000 21:44:40 +0200 From: Wilko Bulte To: Matthew Jacob Cc: FreeBSD-alpha mailing list Subject: Re: max memory on Alpha? Message-ID: <20001003214440.A2046@freebie.demon.nl> References: <20001003212847.A1868@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Tue, Oct 03, 2000 at 12:28:46PM -0700 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Oct 03, 2000 at 12:28:46PM -0700, Matthew Jacob wrote: > > > On Tue, Oct 03, 2000 at 11:57:55AM -0700, Matthew Jacob wrote: > > > On Tue, 3 Oct 2000, Wilko Bulte wrote: > > > > > > > What is the currently max supported memory size on Alpha? 2Gb maybe? > > > > Or will 4Gb also be OK? > > Do you know *if* there is a hard limit at 2Gb? > > I dunno. Doug would be the one to know. I was supposed to look into this for > the Rawhide, but all I ever got was 1.5GB. I could do a book exercise and look > at it, but (see below). I have a 4 and a 6Gb Rawhide as well. At some point in time (assuming they are not being used for customer support) I could give them a spin. And -current should build and boot please.. > > CPUs, so it is a good SMP testbed as well. > > Yes- I'm still struggling to clear a block of time to help more with this. I > had to move offices and other stuff happened as well - I'm still about 1.5 > meters underwater. Well, I am not much of help when it comes to programming, but I do have access to a few SMP alphas. -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 3 12:44:55 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 898C337B66D for ; Tue, 3 Oct 2000 12:44:51 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA29538; Tue, 3 Oct 2000 12:44:49 -0700 Date: Tue, 3 Oct 2000 12:41:34 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: FreeBSD-alpha mailing list Subject: Re: max memory on Alpha? In-Reply-To: <20001003214440.A2046@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Tue, Oct 03, 2000 at 12:28:46PM -0700, Matthew Jacob wrote: > > > > > On Tue, Oct 03, 2000 at 11:57:55AM -0700, Matthew Jacob wrote: > > > > On Tue, 3 Oct 2000, Wilko Bulte wrote: > > > > > > > > > What is the currently max supported memory size on Alpha? 2Gb maybe? > > > > > Or will 4Gb also be OK? > > > > Do you know *if* there is a hard limit at 2Gb? > > > > I dunno. Doug would be the one to know. I was supposed to look into this for > > the Rawhide, but all I ever got was 1.5GB. I could do a book exercise and look > > at it, but (see below). > > I have a 4 and a 6Gb Rawhide as well. At some point in time (assuming > they are not being used for customer support) I could give them a spin. > And -current should build and boot please.. I have 3 8400s to play with- 2 with 2GB each. What I can do is to swipe one system's boards and put it in the one running FreeBSD.. but time, time time... -matt > > > > Yes- I'm still struggling to clear a block of time to help more with this. I > > had to move offices and other stuff happened as well - I'm still about 1.5 > > meters underwater. > > Well, I am not much of help when it comes to programming, but I do have > access to a few SMP alphas. Expand your horizons! Leap in! Don't horrify Jordan and Poul and others and let me keep doing systems programming in FreeBSD! Stop me before I commit again.... -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 3 13:26:25 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 824AB37B502 for ; Tue, 3 Oct 2000 13:26:23 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13gYdm-000IyA-00; Tue, 03 Oct 2000 20:26:18 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e93KSEw02577; Tue, 3 Oct 2000 22:28:14 +0200 (CEST) (envelope-from wkb) Date: Tue, 3 Oct 2000 22:28:14 +0200 From: Wilko Bulte To: Matthew Jacob Cc: FreeBSD-alpha mailing list Subject: Re: max memory on Alpha? Message-ID: <20001003222814.A2562@freebie.demon.nl> References: <20001003214440.A2046@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Tue, Oct 03, 2000 at 12:41:34PM -0700 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Oct 03, 2000 at 12:41:34PM -0700, Matthew Jacob wrote: > > > > On Tue, Oct 03, 2000 at 12:28:46PM -0700, Matthew Jacob wrote: > > > > > > > On Tue, Oct 03, 2000 at 11:57:55AM -0700, Matthew Jacob wrote: > > > > > On Tue, 3 Oct 2000, Wilko Bulte wrote: > > > > > > > > > > > What is the currently max supported memory size on Alpha? 2Gb maybe? > > > > > > Or will 4Gb also be OK? ... > I have 3 8400s to play with- 2 with 2GB each. > > What I can do is to swipe one system's boards and put it in the one running > FreeBSD.. but time, time time... Do you by any chance know of a way to instruct the TLaser SRM to pretend it has less memory than is physically installed? I don't want to swap boards to often, the TLaser backplane is a bit delicate. -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 3 13:41:20 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7BE0337B66C for ; Tue, 3 Oct 2000 13:41:18 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA29760; Tue, 3 Oct 2000 13:41:15 -0700 Date: Tue, 3 Oct 2000 13:38:01 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: FreeBSD-alpha mailing list Subject: Re: max memory on Alpha? In-Reply-To: <20001003222814.A2562@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > ... > > > I have 3 8400s to play with- 2 with 2GB each. > > > > What I can do is to swipe one system's boards and put it in the one running > > FreeBSD.. but time, time time... > > Do you by any chance know of a way to instruct the TLaser SRM to pretend it > has less memory than is physically installed? I don't want to swap boards to > often, the TLaser backplane is a bit delicate. The TLaser backplane is built like a buffalo. It's the KTHA && KTIO cables that are delicate. I don't know what the SRM value might be (if any) to set. It'd probably be easier to try and limit the sizes to the first contiguous 2GB in alpha_init in machdep.c Look- I'll try and check this all out wednesday. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 3 13:53:21 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id E2C9E37B66C; Tue, 3 Oct 2000 13:53:18 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e93Ks7h07894; Tue, 3 Oct 2000 13:54:08 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010032054.e93Ks7h07894@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "O. Hartmann" Cc: freebsd-alpha@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Digital Multia/Alpha problems In-reply-to: Your message of "Tue, 03 Oct 2000 19:12:05 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 03 Oct 2000 13:54:07 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Dear Sirs. > My problem is trivial, but essential. I lost my console > on one of my Multias. There is only one message line on > the bottom of the screen, but no possible input, no chance to > engage ARC/SRM console. How can I bring back the console to the > internal video adaptor? Power up with a keyboard connected, wait for the keyboard to be initialised and then hit ^C and Enter a lot. SRM listens to the keyboard even when it's talking to the serial port, and this should cause it to break the boot process and return to the commandline, as well as switching video output on. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 3 14: 0:33 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 6A5FE37B502 for ; Tue, 3 Oct 2000 14:00:29 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13gZAq-000JXY-00; Tue, 03 Oct 2000 21:00:28 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e93L2NZ02858; Tue, 3 Oct 2000 23:02:23 +0200 (CEST) (envelope-from wkb) Date: Tue, 3 Oct 2000 23:02:23 +0200 From: Wilko Bulte To: Matthew Jacob Cc: FreeBSD-alpha mailing list Subject: Re: max memory on Alpha? Message-ID: <20001003230223.B2800@freebie.demon.nl> References: <20001003222814.A2562@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Tue, Oct 03, 2000 at 01:38:01PM -0700 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Oct 03, 2000 at 01:38:01PM -0700, Matthew Jacob wrote: > > > ... > > > > > I have 3 8400s to play with- 2 with 2GB each. > > > > > > What I can do is to swipe one system's boards and put it in the one running > > > FreeBSD.. but time, time time... > > > > Do you by any chance know of a way to instruct the TLaser SRM to pretend it > > has less memory than is physically installed? I don't want to swap boards to > > often, the TLaser backplane is a bit delicate. > > The TLaser backplane is built like a buffalo. It's the KTHA && KTIO cables But the connector pins are not.. > I don't know what the SRM value might be (if any) to set. OK. > It'd probably be easier to try and limit the sizes to the first contiguous 2GB > in alpha_init in machdep.c > > Look- I'll try and check this all out wednesday. No rush, I am *not* pushing you! ;-) -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 3 22:33:32 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.gplsucks.org (mail.gplsucks.org [63.227.213.93]) by hub.freebsd.org (Postfix) with ESMTP id 6DF0237B503 for ; Tue, 3 Oct 2000 22:33:31 -0700 (PDT) Received: from localhost (bwoods2@localhost) by mail.gplsucks.org (8.11.0/8.11.0) with ESMTP id e945XWa16319 for ; Tue, 3 Oct 2000 22:33:32 -0700 (PDT) Date: Tue, 3 Oct 2000 22:33:31 -0700 (PDT) From: Bill Woods mail To: freebsd-alpha@freebsd.org Subject: Alpha snapshot..... 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 any ide when the next snapshot of 5-current will be up on current.freebsd.org for the Alpha platform? Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Oct 4 0:15:50 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id DF1F337B502 for ; Wed, 4 Oct 2000 00:15:48 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id AAA07459; Wed, 4 Oct 2000 00:15:46 -0700 (PDT) (envelope-from obrien) Date: Wed, 4 Oct 2000 00:15:46 -0700 From: "David O'Brien" To: Bill Woods mail Cc: alpha@freebsd.org Subject: Re: Alpha snapshot..... Message-ID: <20001004001546.A7414@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from bwoods2@uswest.net on Tue, Oct 03, 2000 at 10:33:31PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Oct 03, 2000 at 10:33:31PM -0700, Bill Woods mail wrote: > any ide when the next snapshot of 5-current will be up on > current.freebsd.org for the Alpha platform? I can maybe make one in a week or so. -- -- David (obrien@FreeBSD.org) Gnu is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Oct 4 1:28: 3 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by hub.freebsd.org (Postfix) with ESMTP id 4B29337B502 for ; Wed, 4 Oct 2000 01:28:00 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1) id 13gju7-0008AE-0X; Wed, 4 Oct 2000 09:27:57 +0100 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA12105; Wed, 4 Oct 2000 09:34:06 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 4 Oct 2000 09:27:47 +0100 (BST) From: Doug Rabson To: Kenjiro Cho Cc: gallatin@cs.duke.edu, freebsd-alpha@freebsd.org, core@kame.net Subject: Re: size problems with INVARIANTS/DIAGNOSTIC -current kernels In-Reply-To: <20001003175912F.kjc@csl.sony.co.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 3 Oct 2000, Kenjiro Cho wrote: > > Doug Rabson wrote: > > Could you compile a kernel with DEBUG_CLUSTER defined in machdep.c so that > > I can see what the system memory map looks like. > > OK. I got the following output for the KAME kernel: > text data bss dec hex filename > 3776913 338432 226922 4342267 4241fb kernel > > FreeBSD/alpha SRM disk boot, Revision 0.3 > (root@beta.osd.bsdi.com, Thu Jul 27 08:00:34 GMT 2000) > Memory: 262144 k > Loading /boot/defaults/loader.conf > /kernel data=0x3eccf0+0x3766a syms=[0x8+0x4bae0+0x8+0x35d55] > > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [kernel]... > Entering kernel at 0xfffffc0000330840... > Memory cluster count: 3 > MEMC 0: pfn 0x0 cnt 0x100 usage 0x1 > MEMC 1: pfn 0x100 cnt 0x7ea3 usage 0x0 > Cluster 1 contains kernel > Loading chunk after kernel: 0x3d5 / 0x7fa3 > MEMC 2: pfn 0x7fa3 cnt 0x5d usage 0x1 This all looks reasonable. I'll have to think about this some more - possibly something is wrong in the loader? -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Oct 4 7:44:47 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 8603137B66D for ; Wed, 4 Oct 2000 07:44:40 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA07028; Wed, 4 Oct 2000 10:44:34 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e94EiYd44357; Wed, 4 Oct 2000 10:44: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: Wed, 4 Oct 2000 10:44:34 -0400 (EDT) To: Doug Rabson Cc: Kenjiro Cho , freebsd-alpha@FreeBSD.ORG, core@kame.net Subject: Re: size problems with INVARIANTS/DIAGNOSTIC -current kernels In-Reply-To: References: <20001003175912F.kjc@csl.sony.co.jp> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14811.11704.600307.685105@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug Rabson writes: > On Tue, 3 Oct 2000, Kenjiro Cho wrote: > > > > > Doug Rabson wrote: > > > Could you compile a kernel with DEBUG_CLUSTER defined in machdep.c so that > > > I can see what the system memory map looks like. > > > > OK. I got the following output for the KAME kernel: > > text data bss dec hex filename > > 3776913 338432 226922 4342267 4241fb kernel > > > > FreeBSD/alpha SRM disk boot, Revision 0.3 > > (root@beta.osd.bsdi.com, Thu Jul 27 08:00:34 GMT 2000) > > Memory: 262144 k > > Loading /boot/defaults/loader.conf > > /kernel data=0x3eccf0+0x3766a syms=[0x8+0x4bae0+0x8+0x35d55] > > > > Hit [Enter] to boot immediately, or any other key for command prompt. > > Booting [kernel]... > > Entering kernel at 0xfffffc0000330840... > > Memory cluster count: 3 > > MEMC 0: pfn 0x0 cnt 0x100 usage 0x1 > > MEMC 1: pfn 0x100 cnt 0x7ea3 usage 0x0 > > Cluster 1 contains kernel > > Loading chunk after kernel: 0x3d5 / 0x7fa3 > > MEMC 2: pfn 0x7fa3 cnt 0x5d usage 0x1 > From my AS500: MEMC 0: pfn 0x0 cnt 0xa5 usage 0x1 MEMC 1: pfn 0xa5 cnt 0x3ee6 usage 0x0 Cluster 1 contains kernel Loading chunk after kernel: 0x3d3 / 0x3f8b MEMC 2: pfn 0x3f8b cnt 0x75 usage 0x1 Unrecognized boot flag '"'. Unrecognized boot flag '"'. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. > This all looks reasonable. I'll have to think about this some more - > possibly something is wrong in the loader? > If so, the breakage has not happened recently. I'm seeing this with a 'loader' from late august, a netboot from late august & a netboot that's over 1 year old. Bear in mind that we seem to run just fine until the first time we attempt to call a function from a stack created for us by the palcode. However, that same function is callable when not running in an interrupt/trap/etc palcode-created context. I've "proved" this to myself by making sure that trap() is actually callable from the mainline kernel code (eg, not running out XentMM). I put a call to trap() in kern_malloc() & I put a call to printtrap() at the top of trap. I see trap being called from kern_malloc, but when its called by XentMM, random stuff happens. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Oct 4 15:23:23 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by hub.freebsd.org (Postfix) with ESMTP id 0F7BC37B502 for ; Wed, 4 Oct 2000 15:23:21 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-34.mail.demon.net with esmtp (Exim 2.12 #1) id 13gwwX-000GHU-0Y; Wed, 4 Oct 2000 23:23:18 +0100 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id XAA13974; Wed, 4 Oct 2000 23:29:34 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 4 Oct 2000 23:23:05 +0100 (BST) From: Doug Rabson To: Andrew Gallatin Cc: Kenjiro Cho , freebsd-alpha@FreeBSD.ORG, core@kame.net Subject: Re: size problems with INVARIANTS/DIAGNOSTIC -current kernels In-Reply-To: <14811.11704.600307.685105@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 Wed, 4 Oct 2000, Andrew Gallatin wrote: > > possibly something is wrong in the loader? > > > > > If so, the breakage has not happened recently. I'm seeing this with a > 'loader' from late august, a netboot from late august & a netboot > that's over 1 year old. > > Bear in mind that we seem to run just fine until the first time we > attempt to call a function from a stack created for us by the > palcode. However, that same function is callable when not running > in an interrupt/trap/etc palcode-created context. > > I've "proved" this to myself by making sure that trap() is actually > callable from the mainline kernel code (eg, not running out XentMM). > I put a call to trap() in kern_malloc() & I put a call to printtrap() > at the top of trap. I see trap being called from kern_malloc, but > when its called by XentMM, random stuff happens. Bizarre. We are running on our own stack before mi_startup is called() which should be before anything substantial is printed. I wonder if somehow the ksp value in the context has been corrupted. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Oct 4 15:43:53 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by hub.freebsd.org (Postfix) with ESMTP id 8CEA637B502 for ; Wed, 4 Oct 2000 15:43:51 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1) id 13gxGP-00098k-0X; Wed, 4 Oct 2000 23:43:49 +0100 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id XAA14137; Wed, 4 Oct 2000 23:49:45 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 4 Oct 2000 23:43:16 +0100 (BST) From: Doug Rabson To: Wilko Bulte Cc: FreeBSD-alpha mailing list Subject: Re: max memory on Alpha? In-Reply-To: <20001003200741.A1318@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 3 Oct 2000, Wilko Bulte wrote: > What is the currently max supported memory size on Alpha? 2Gb maybe? > Or will 4Gb also be OK? > > Reason for asking is that I want to try a AS8400 who is equipped > with 3x 4Gb memory module. Currently we are limited to 1Gb or 2Gb, depending on the platform. The tsunami driver uses a 2Gb window for dma and I think AS4x00 and AS8x00 also support 2Gb. Supporting more memory requires that all dma capable hardware is the busdma interface in its drivers. Given that, someone needs to write a small amount of code in busdma_machdep.c to either bounce transfers down to the 2Gb range or to use the sgmap to map the transfers into a reachable place. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Oct 4 15:46:45 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from anchor-post-31.mail.demon.net (anchor-post-31.mail.demon.net [194.217.242.89]) by hub.freebsd.org (Postfix) with ESMTP id DCF5237B66D for ; Wed, 4 Oct 2000 15:46:41 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-31.mail.demon.net with esmtp (Exim 2.12 #1) id 13gxJ6-000G21-0V; Wed, 4 Oct 2000 23:46:37 +0100 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id XAA14160; Wed, 4 Oct 2000 23:52:58 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 4 Oct 2000 23:46:29 +0100 (BST) From: Doug Rabson To: Wilko Bulte Cc: Matthew Jacob , FreeBSD-alpha mailing list Subject: Re: max memory on Alpha? In-Reply-To: <20001003212847.A1868@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 3 Oct 2000, Wilko Bulte wrote: > On Tue, Oct 03, 2000 at 11:57:55AM -0700, Matthew Jacob wrote: > > On Tue, 3 Oct 2000, Wilko Bulte wrote: > > > > > What is the currently max supported memory size on Alpha? 2Gb maybe? > > > Or will 4Gb also be OK? > > > > > > Reason for asking is that I want to try a AS8400 who is equipped > > > with 3x 4Gb memory module. > > > > I've run 8400s up to 2GB. Any more than that and you'll find that S/G > > DMA hasn't been finished ;-). > > Well, on 12Gb it panics with pmap_foo off the top of my head> on 4.1-R ;-) Might this mean it cannot create the > necessary page table admin on > 2Gb? > > Do you know *if* there is a hard limit at 2Gb? I don't think there is a *hard* limit for the basic VM system but I imagine it might have problems finding a large enough contiguous region to map the vm_page_t structures. The main limitation is in the i/o system as previously noted. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Oct 4 15:47:33 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9D30537B502 for ; Wed, 4 Oct 2000 15:47:31 -0700 (PDT) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA01760; Wed, 4 Oct 2000 15:47:26 -0700 Date: Wed, 4 Oct 2000 15:47:25 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Doug Rabson Cc: Wilko Bulte , FreeBSD-alpha mailing list Subject: Re: max memory on Alpha? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 4 Oct 2000, Doug Rabson wrote: > On Tue, 3 Oct 2000, Wilko Bulte wrote: > > > What is the currently max supported memory size on Alpha? 2Gb maybe? > > Or will 4Gb also be OK? > > > > Reason for asking is that I want to try a AS8400 who is equipped > > with 3x 4Gb memory module. > > Currently we are limited to 1Gb or 2Gb, depending on the platform. The > tsunami driver uses a 2Gb window for dma and I think AS4x00 and AS8x00 > also support 2Gb. > > Supporting more memory requires that all dma capable hardware is the > busdma interface in its drivers. Given that, someone needs to write a > small amount of code in busdma_machdep.c to either bounce transfers down > to the 2Gb range or to use the sgmap to map the transfers into a reachable > place. Some SGMAP stuff is initialized- but you're right about dma-busifying. I'm about ready to shove an extra 512 MB memory module into an 8200 to take it to 2.5GB just to see what'll happen. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Oct 4 15:48: 3 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by hub.freebsd.org (Postfix) with ESMTP id EB84737B66E for ; Wed, 4 Oct 2000 15:47:59 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-34.mail.demon.net with esmtp (Exim 2.12 #1) id 13gxKQ-000HXa-0Y; Wed, 4 Oct 2000 23:47:58 +0100 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id XAA14164; Wed, 4 Oct 2000 23:54:20 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 4 Oct 2000 23:47:51 +0100 (BST) From: Doug Rabson To: Wilko Bulte Cc: Matthew Jacob , FreeBSD-alpha mailing list Subject: Re: max memory on Alpha? In-Reply-To: <20001003222814.A2562@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 3 Oct 2000, Wilko Bulte wrote: > On Tue, Oct 03, 2000 at 12:41:34PM -0700, Matthew Jacob wrote: > > > > > > > On Tue, Oct 03, 2000 at 12:28:46PM -0700, Matthew Jacob wrote: > > > > > > > > > On Tue, Oct 03, 2000 at 11:57:55AM -0700, Matthew Jacob wrote: > > > > > > On Tue, 3 Oct 2000, Wilko Bulte wrote: > > > > > > > > > > > > > What is the currently max supported memory size on Alpha? 2Gb maybe? > > > > > > > Or will 4Gb also be OK? > ... > > > I have 3 8400s to play with- 2 with 2GB each. > > > > What I can do is to swipe one system's boards and put it in the one running > > FreeBSD.. but time, time time... > > Do you by any chance know of a way to instruct the TLaser SRM to pretend it > has less memory than is physically installed? I don't want to swap boards to > often, the TLaser backplane is a bit delicate. You could hack alpha_init() where it goes through the memory clusters and stop it from using any cluster which starts too high. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Oct 4 15:49:26 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B9F5637B502 for ; Wed, 4 Oct 2000 15:49:24 -0700 (PDT) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA01776; Wed, 4 Oct 2000 15:49:17 -0700 Date: Wed, 4 Oct 2000 15:49:17 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Doug Rabson Cc: Wilko Bulte , FreeBSD-alpha mailing list Subject: Re: max memory on Alpha? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > You could hack alpha_init() where it goes through the memory clusters and > stop it from using any cluster which starts too high. > Heh. I was just going to suggest that... that's what I did for the NetBSD port at first. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Oct 4 22:46:43 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id 4166F37B503 for ; Wed, 4 Oct 2000 22:46:41 -0700 (PDT) Received: from CALCULATOR (r773.str.dial.surf-callino.de [213.21.13.11]) by post.webmailer.de (8.9.3/8.8.7) with SMTP id HAA02446 for ; Thu, 5 Oct 2000 07:46:38 +0200 (MET DST) From: webmaster@ah-network.de Message-ID: <000701c02e8f$997b9cb0$0100a8c0@CALCULATOR> To: Subject: bad x server Date: Thu, 5 Oct 2000 07:46:24 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.5600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.5600 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hello there, i have a problem with the x server on my 21164/533 with a matrox millennium 2mb: everytime i install the system(4.0 & 4.1, both release) the desktops (i tried all from the cd: kde, gnome...) look like after a really bad crash and i have no icons and no text in the editors... what can i do? redhat and suse do not have any problems but i would really like to use freebsd. thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 5 11:22:51 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id AB18437B503 for ; Thu, 5 Oct 2000 11:22:46 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA29814; Thu, 5 Oct 2000 11:44:09 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e95Fi9953986; Thu, 5 Oct 2000 11:44:09 -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, 5 Oct 2000 11:44:09 -0400 (EDT) To: Doug Rabson Cc: Kenjiro Cho , freebsd-alpha@FreeBSD.ORG, core@kame.net Subject: Re: size problems with INVARIANTS/DIAGNOSTIC -current kernels In-Reply-To: References: <14811.11704.600307.685105@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14812.37571.725840.45245@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug Rabson writes: > On Wed, 4 Oct 2000, Andrew Gallatin wrote: > > > > possibly something is wrong in the loader? > > > > > > > > > If so, the breakage has not happened recently. I'm seeing this with a > > 'loader' from late august, a netboot from late august & a netboot > > that's over 1 year old. > > > > Bear in mind that we seem to run just fine until the first time we > > attempt to call a function from a stack created for us by the > > palcode. However, that same function is callable when not running > > in an interrupt/trap/etc palcode-created context. > > > > I've "proved" this to myself by making sure that trap() is actually > > callable from the mainline kernel code (eg, not running out XentMM). > > I put a call to trap() in kern_malloc() & I put a call to printtrap() > > at the top of trap. I see trap being called from kern_malloc, but > > when its called by XentMM, random stuff happens. > > Bizarre. We are running on our own stack before mi_startup is > called() which should be before anything substantial is printed. I wonder > if somehow the ksp value in the context has been corrupted. Any ideas on how to debug this further? I'm at my wits end here.. In case its of any use, here's what the registers look like after one of these wacky crashes: >>>e pc PC psr: 0 ( PC) FFFFFC00006962A8 >>>e -n 32 r0 gpr: 0 ( R0) 000000000000001C gpr: 1 ( R1) FFFFFC00006B17D8 gpr: 2 ( R2) FFFFFC000068C7E3 gpr: 3 ( R3) 000000000000001C gpr: 4 ( R4) 0000000000000001 gpr: 5 ( R5) FFFFFC0007F15FE8 gpr: 6 ( R6) FFFFFC00006B5258 gpr: 7 ( R7) FFFFFC00006E72A8 gpr: 8 ( R8) FFFFFC00007AA000 gpr: 9 ( R9) FFFFFC00007A9CA0 gpr: A ( R10) 00000000DEADBEEF gpr: B ( R11) 0000000000000001 gpr: C ( R12) 0000000000000000 gpr: D ( R13) 00000000DEADBEEF gpr: E ( R14) 00000000DEADBEEF gpr: F ( R15) 00000000DEADBEEF gpr: 10 ( R16) 00000000DEADBFE7 gpr: 11 ( R17) 0000000000000001 gpr: 12 ( R18) 0000000000000000 gpr: 13 ( R19) 0000000000000002 gpr: 14 ( R20) FFFFFC00007A9B40 gpr: 15 ( R21) 0000000000000008 gpr: 16 ( R22) 000000000000001E gpr: 17 ( R23) FFFFFC0000417584 gpr: 18 ( R24) 000000000000000D gpr: 19 ( R25) 0000000000000010 gpr: 1A ( R26) FFFFFC00005E1FAC gpr: 1B ( R27) FFFFFC00006962A8 gpr: 1C ( R28) FFFFFC00007A9C60 gpr: 1D ( R29) FFFFFC00006D9068 gpr: 1E ( R30) FFFFFC00007A9B40 gpr: 1F ( R31) 0000000000000000 the PC (FFFFFC00006962A8) is in the data segment. The RA is what I would expect: (gdb) l *0xFFFFFC00005E1FAC 0xfffffc00005e1fac is in XentMM (../../alpha/alpha/exception.s:94). 89 PALVECT(XentMM) /* setup frame, save registers */ 90 91 /* a0, a1, & a2 already set up */ 92 ldiq a3, ALPHA_KENTRY_MM 93 mov sp, a4 ; .loc 1 __LINE__ 94 CALL(trap) 95 96 jmp zero, exception_return 97 END(XentMM) 98 The kernel stack pointer seems reasonable (I guess): >>>e sp gpr: 1E ( R30) FFFFFC00007A9B40 <..> fffffc00007190d0 B tc_3000_500_intr fffffc0000719160 A _end fffffffe00000000 A PTmap <..> proc0paddr points to 0xFFFFFC00007A6000 according the the SRM console. Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 5 13:49:19 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 7462437B502 for ; Thu, 5 Oct 2000 13:49:17 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13hHx3-000KAh-00; Thu, 05 Oct 2000 20:49:13 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e95Kc6I06897; Thu, 5 Oct 2000 22:38:06 +0200 (CEST) (envelope-from wkb) Date: Thu, 5 Oct 2000 22:38:06 +0200 From: Wilko Bulte To: Doug Rabson Cc: FreeBSD-alpha mailing list Subject: Re: max memory on Alpha? Message-ID: <20001005223806.C6823@freebie.demon.nl> References: <20001003200741.A1318@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from dfr@nlsystems.com on Wed, Oct 04, 2000 at 11:43:16PM +0100 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Oct 04, 2000 at 11:43:16PM +0100, Doug Rabson wrote: > On Tue, 3 Oct 2000, Wilko Bulte wrote: > > > What is the currently max supported memory size on Alpha? 2Gb maybe? > > Or will 4Gb also be OK? > > > > Reason for asking is that I want to try a AS8400 who is equipped > > with 3x 4Gb memory module. > > Currently we are limited to 1Gb or 2Gb, depending on the platform. The > tsunami driver uses a 2Gb window for dma and I think AS4x00 and AS8x00 > also support 2Gb. I'm working to source myself a 2Gb module. Easier than to pull a truckload of SIMMs from the TL board. Given some time I can try a 2Gb AS4100 as well. Sidestep: anybody ever tried an ES40 'Clipper' ? Tsunami based and max 4 CPUs. Just found one with 4 CPUs and 8Gb of RAM. Brought it down to 2Gb already but lack of time prevented further experiments. -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 5 13:52:58 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 38ED437B502 for ; Thu, 5 Oct 2000 13:52:57 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA05362; Thu, 5 Oct 2000 13:52:43 -0700 Date: Thu, 5 Oct 2000 13:49:22 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: Doug Rabson , FreeBSD-alpha mailing list Subject: Re: max memory on Alpha? In-Reply-To: <20001005223806.C6823@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org BTW- I ran out of time yesterday about putting in > 2GB. Next monday... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 5 14:26:22 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 6057437B502 for ; Thu, 5 Oct 2000 14:26:18 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13hIWu-0004aH-00; Thu, 05 Oct 2000 21:26:17 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e95LO4w07154; Thu, 5 Oct 2000 23:24:04 +0200 (CEST) (envelope-from wkb) Date: Thu, 5 Oct 2000 23:24:04 +0200 From: Wilko Bulte To: Matthew Jacob Cc: Doug Rabson , FreeBSD-alpha mailing list Subject: Re: max memory on Alpha? Message-ID: <20001005232404.A7134@freebie.demon.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Wed, Oct 04, 2000 at 03:49:17PM -0700 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Oct 04, 2000 at 03:49:17PM -0700, Matthew Jacob wrote: > > > > > You could hack alpha_init() where it goes through the memory clusters and > > stop it from using any cluster which starts too high. > > > > Heh. I was just going to suggest that... that's what I did for the NetBSD port > at first. Does this mean NetBSD can do > 2Gb? -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 5 14:26:24 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id DFBB237B503 for ; Thu, 5 Oct 2000 14:26:18 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13hIWv-0004aH-00; Thu, 05 Oct 2000 21:26:17 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e95LS5407182; Thu, 5 Oct 2000 23:28:05 +0200 (CEST) (envelope-from wkb) Date: Thu, 5 Oct 2000 23:28:05 +0200 From: Wilko Bulte To: Doug Rabson Cc: Matthew Jacob , FreeBSD-alpha mailing list Subject: Re: max memory on Alpha? Message-ID: <20001005232805.B7134@freebie.demon.nl> References: <20001003212847.A1868@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from dfr@nlsystems.com on Wed, Oct 04, 2000 at 11:46:29PM +0100 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Oct 04, 2000 at 11:46:29PM +0100, Doug Rabson wrote: > On Tue, 3 Oct 2000, Wilko Bulte wrote: > > > On Tue, Oct 03, 2000 at 11:57:55AM -0700, Matthew Jacob wrote: > > > On Tue, 3 Oct 2000, Wilko Bulte wrote: > > > > > > > What is the currently max supported memory size on Alpha? 2Gb maybe? > > > > Or will 4Gb also be OK? > > > > > > > > Reason for asking is that I want to try a AS8400 who is equipped > > > > with 3x 4Gb memory module. > > > > > > I've run 8400s up to 2GB. Any more than that and you'll find that S/G > > > DMA hasn't been finished ;-). > > > > Well, on 12Gb it panics with pmap_foo > off the top of my head> on 4.1-R ;-) Might this mean it cannot create the > > necessary page table admin on > 2Gb? > > > > Do you know *if* there is a hard limit at 2Gb? > > I don't think there is a *hard* limit for the basic VM system but I > imagine it might have problems finding a large enough contiguous region to > map the vm_page_t structures. The main limitation is in the i/o system as > previously noted. From looking at the code it would be instructive to compile a kernel with DEBUG_CLUSTER and see what is says (hopefully before panicing ;-) I need a sensible -current built first (my -current disk that I carry around from machine to machine is a bit whacko). Hmm, or maybe -stable is easier.. Will see what I can do. W/ -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 5 14:49:57 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B96D437B503 for ; Thu, 5 Oct 2000 14:49:53 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA05575; Thu, 5 Oct 2000 14:49:49 -0700 Date: Thu, 5 Oct 2000 14:46:28 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: Doug Rabson , FreeBSD-alpha mailing list Subject: Re: max memory on Alpha? In-Reply-To: <20001005232404.A7134@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Wed, Oct 04, 2000 at 03:49:17PM -0700, Matthew Jacob wrote: > > > > > > > > You could hack alpha_init() where it goes through the memory clusters and > > > stop it from using any cluster which starts too high. > > > > > > > Heh. I was just going to suggest that... that's what I did for the NetBSD port > > at first. > > Does this mean NetBSD can do > 2Gb? Uh, no...should, but not proven yet either.. this meant that until I fixed the dwlpx implementation there, stuff over 1GB was broken. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 5 15:28:54 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id DB53337B502 for ; Thu, 5 Oct 2000 15:28:47 -0700 (PDT) Received: (from daemon@localhost) by smtp02.primenet.com (8.9.3/8.9.3) id PAA10580; Thu, 5 Oct 2000 15:15:24 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp02.primenet.com, id smtpdAAAbQaWGm; Thu Oct 5 15:06:47 2000 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id PAA16408; Thu, 5 Oct 2000 15:09:35 -0700 (MST) From: Terry Lambert Message-Id: <200010052209.PAA16408@usr05.primenet.com> Subject: Re: max memory on Alpha? To: wkb@freebie.demon.nl (Wilko Bulte) Date: Thu, 5 Oct 2000 22:09:35 +0000 (GMT) Cc: dfr@nlsystems.com (Doug Rabson), mjacob@feral.com (Matthew Jacob), freebsd-alpha@FreeBSD.ORG (FreeBSD-alpha mailing list) In-Reply-To: <20001005232805.B7134@freebie.demon.nl> from "Wilko Bulte" at Oct 05, 2000 11:28:05 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Do you know *if* there is a hard limit at 2Gb? > > I don't think there is a *hard* limit for the basic VM system but I > imagine it might have problems finding a large enough contiguous region to > map the vm_page_t structures. The main limitation is in the i/o system as > previously noted. It seems to me that the contiguity requirement is bogus. If contiguity is other than an implementation artificat (i.e. it is a true hardware requirement), then it seems to me that it is time to provide a mechanism for defragging KVA space, or place the vm_page_t structures in a seperate virtual address space. On a related note, I've always though that drivers (and their related kernel threads, should such obnoxious things become more commonplace) ought to run in their own VA space, on a per driver basis, so that a bad driver couldn't pee in the pool. This would keep bad drivers from actually crashing the system, short of a halt or going into a tight loop (even then, a timer interrupt should be able to recover the halt, and a preemption should be able to recover the loop, if it is a kernel thread -- or even generally, if kernel preemption were to be supported). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 5 16:45:21 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id C5AE737B503 for ; Thu, 5 Oct 2000 16:45:18 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 13hKhJ-000Ja8-0K; Thu, 5 Oct 2000 23:45:13 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id AAA19068; Fri, 6 Oct 2000 00:51:19 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 6 Oct 2000 00:44:34 +0100 (BST) From: Doug Rabson To: Terry Lambert Cc: Wilko Bulte , Matthew Jacob , FreeBSD-alpha mailing list Subject: Re: max memory on Alpha? In-Reply-To: <200010052209.PAA16408@usr05.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 5 Oct 2000, Terry Lambert wrote: > > > Do you know *if* there is a hard limit at 2Gb? > > > > I don't think there is a *hard* limit for the basic VM system but I > > imagine it might have problems finding a large enough contiguous region to > > map the vm_page_t structures. The main limitation is in the i/o system as > > previously noted. > > It seems to me that the contiguity requirement is bogus. > > If contiguity is other than an implementation artificat (i.e. > it is a true hardware requirement), then it seems to me that > it is time to provide a mechanism for defragging KVA space, > or place the vm_page_t structures in a seperate virtual > address space. The vm_page_t's are initialised *very* early and are generally mapped by a very simple subset of pmap. Currently, the VM system assumes that it can map a single contiguous physical extent for them although it could conceivably be slightly smarter. > > On a related note, I've always though that drivers (and their > related kernel threads, should such obnoxious things become > more commonplace) ought to run in their own VA space, on a > per driver basis, so that a bad driver couldn't pee in the > pool. This would keep bad drivers from actually crashing > the system, short of a halt or going into a tight loop (even > then, a timer interrupt should be able to recover the halt, > and a preemption should be able to recover the loop, if it > is a kernel thread -- or even generally, if kernel preemption > were to be supported). This would probably waste far too much performance to be actually useful. On the other hand, there are OSs which do this so perhaps the cost is manageable. Much too hard to implement within the existing kernel infrastructure though. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 5 17: 6:40 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 6A03537B66D for ; Thu, 5 Oct 2000 17:06:32 -0700 (PDT) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id RAA05926; Thu, 5 Oct 2000 17:06:20 -0700 Date: Thu, 5 Oct 2000 17:06:19 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Terry Lambert Cc: Wilko Bulte , Doug Rabson , FreeBSD-alpha mailing list Subject: Re: max memory on Alpha? In-Reply-To: <200010052209.PAA16408@usr05.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 5 Oct 2000, Terry Lambert wrote: > > > Do you know *if* there is a hard limit at 2Gb? > > > > I don't think there is a *hard* limit for the basic VM system but I > > imagine it might have problems finding a large enough contiguous region to > > map the vm_page_t structures. The main limitation is in the i/o system as > > previously noted. > > It seems to me that the contiguity requirement is bogus. > > If contiguity is other than an implementation artificat (i.e. > it is a true hardware requirement), then it seems to me that > it is time to provide a mechanism for defragging KVA space, > or place the vm_page_t structures in a seperate virtual > address space. Physical page contiguity should not be a requirement- but this is may just be an implementation cleverness issue. > > On a related note, I've always though that drivers (and their > related kernel threads, should such obnoxious things become > more commonplace) ought to run in their own VA space, on a > per driver basis, so that a bad driver couldn't pee in the > pool. This would keep bad drivers from actually crashing > the system, short of a halt or going into a tight loop (even > then, a timer interrupt should be able to recover the halt, > and a preemption should be able to recover the loop, if it > is a kernel thread -- or even generally, if kernel preemption > were to be supported). > This makes no sense for anything but a system that has an IOMMU - unless I've totally misunderstood you. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Oct 6 1:52: 2 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by hub.freebsd.org (Postfix) with ESMTP id 7A99F37B66C for ; Fri, 6 Oct 2000 01:52:00 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 13hTET-0004T7-0B; Fri, 6 Oct 2000 08:51:58 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA21037; Fri, 6 Oct 2000 09:58:35 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 6 Oct 2000 09:51:44 +0100 (BST) From: Doug Rabson To: Andrew Gallatin Cc: Kenjiro Cho , freebsd-alpha@FreeBSD.ORG, core@kame.net Subject: Re: size problems with INVARIANTS/DIAGNOSTIC -current kernels In-Reply-To: <14812.37571.725840.45245@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, 5 Oct 2000, Andrew Gallatin wrote: > > Doug Rabson writes: > > On Wed, 4 Oct 2000, Andrew Gallatin wrote: > > > > > > possibly something is wrong in the loader? > > > > > > > > > > > > > If so, the breakage has not happened recently. I'm seeing this with a > > > 'loader' from late august, a netboot from late august & a netboot > > > that's over 1 year old. > > > > > > Bear in mind that we seem to run just fine until the first time we > > > attempt to call a function from a stack created for us by the > > > palcode. However, that same function is callable when not running > > > in an interrupt/trap/etc palcode-created context. > > > > > > I've "proved" this to myself by making sure that trap() is actually > > > callable from the mainline kernel code (eg, not running out XentMM). > > > I put a call to trap() in kern_malloc() & I put a call to printtrap() > > > at the top of trap. I see trap being called from kern_malloc, but > > > when its called by XentMM, random stuff happens. > > > > Bizarre. We are running on our own stack before mi_startup is > > called() which should be before anything substantial is printed. I wonder > > if somehow the ksp value in the context has been corrupted. > > Any ideas on how to debug this further? I'm at my wits end here.. > > In case its of any use, here's what the registers look like after one > of these wacky crashes: Clearly something bad is happening and we are taking a trap, then fielding it badly. You could try inserting 'call_pal halt' instructions in XentMM so that we can see what the state looks like on the first fault. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Oct 6 8:12:58 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from neutron.cichlids.com (p3E9C112B.dip.t-dialin.net [62.156.17.43]) by hub.freebsd.org (Postfix) with ESMTP id 0357B37B66C for ; Fri, 6 Oct 2000 08:12:57 -0700 (PDT) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id 8F27CAB9C; Fri, 6 Oct 2000 17:14:14 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id CF2E214A65; Fri, 6 Oct 2000 17:12:55 +0200 (CEST) Date: Fri, 6 Oct 2000 17:12:55 +0200 To: alpha@freebsd.org, root@beast.freebsd.org Subject: top: cannot read blmeta_t: Message-ID: <20001006171255.A30463@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. From: alex@big.endian.de (Alexander Langer) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! Anyone w/ access on beast can see the following: top: cannot read blmeta_t: (repeated forever). JFYI Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Oct 6 9:33:58 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id C95EC37B502; Fri, 6 Oct 2000 09:33:55 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id JAA08644; Fri, 6 Oct 2000 09:33:55 -0700 Date: Fri, 6 Oct 2000 09:30:31 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: alpha@FreeBSD.org Subject: Re: cvs commit: src/sys/alpha/alpha trap.c src/sys/alpha/include 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 For my PC164... Yep, well, the current boot loader has had the stack problem show up again for the current loader, and if I try and use the older loader, it whines, and anyway, it freezes below. ---- HALT instruction executed PC = fffffc00005b7cc8 >>>b dka900 (boot dka900.9.0.5.0 -flags a) block 0 of dka900.9.0.5.0 is a valid boot block reading 15 blocks from dka900.9.0.5.0 bootstrap code read in base = 180000, image_start = 0, image_bytes = 1e00 initializing HWRPB at 2000 initializing page table at 172000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code Loading /boot/loader Console: SRM firmware console VMS PAL rev: 0x1000900010115 OSF PAL rev: 0x1000800020117 Switch to OSF PAL code succeeded. FreeBSD/alpha SRM disk boot, Revision 0.1 (mjacob@farrago.feral.com, Wed Jun 7 07:18:49 PDT 2000) Memory: 262144 k Loader version 1.1+ required Aborted! start not found / Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel]... /kernel data=0x3cb968+0x325a8 syms=[0x8+0x4cb78+0x8+0x39393] module: cam module: miibus module: usb module: isp module: splash Entering kernel at 0xfffffc0000330360... Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Thu Oct 5 18:06:28 PDT 2000 mjacob@farrago.feral.com:/usr/obj/usr/src/sys/GENERIC EB164 Digital AlphaPC 164 432 MHz, 432MHz 8192 byte page size, 1 processor. CPU: EV56 (21164A) major=7 minor=1 extensions=0x1 OSF PAL rev: 0x1000800020117 real memory = 265904128 (259672K bytes) avail memory = 252018688 (246112K bytes) Preloaded elf kernel "kernel" at 0xfffffc0000786000. md0: Malloc disk cia0: <2117x Core Logic chipset> cia0: ALCOR/ALCOR2, pass 3 cia0: extended capabilities: 21 pcib0: <2117x PCI host bus adapter> on cia0 pci0: on pcib0 isp0: port 0x10200-0x102ff mem 0x82082000-0x82082fff irq 2 at device 5.0 on pci0 isp0: interrupting at CIA irq 2 ------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Oct 6 9:40:57 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 8862637B503 for ; Fri, 6 Oct 2000 09:40:55 -0700 (PDT) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e96Geci42988; Fri, 6 Oct 2000 09:40:38 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 06 Oct 2000 09:40:56 -0700 (PDT) From: John Baldwin To: Matthew Jacob Subject: Re: cvs commit: src/sys/alpha/alpha trap.c src/sys/alpha/include Cc: alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 06-Oct-00 Matthew Jacob wrote: > > For my PC164... > > Yep, well, the current boot loader has had the stack problem show up again > for > the current loader, and if I try and use the older loader, it whines, and > anyway, it freezes below. Hmm. Maybe the hooks to enable/disable PCI interrupt sources aren't working? If they don't, then teh first PCI interrupt you get will result in teh machine being pounded with an infinite number of PCI interrupts and effectively halting the machine. The code in question to check are the cia_enable_intr() and cia_disable_intr() in sys/alpha/pci/cia.c. FWIW, I still use an old loader from before the PnP stuff on my alpha. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Oct 6 10:14:33 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 2622037B66C for ; Fri, 6 Oct 2000 10:14:31 -0700 (PDT) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e96HEAi44206; Fri, 6 Oct 2000 10:14:10 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20001006171255.A30463@cichlids.cichlids.com> Date: Fri, 06 Oct 2000 10:14:28 -0700 (PDT) From: John Baldwin To: (Alexander Langer) Subject: RE: top: cannot read blmeta_t: Cc: root@beast.freebsd.org, alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 06-Oct-00 Alexander Langer wrote: > Hi! > > Anyone w/ access on beast can see the following: > > top: cannot read blmeta_t: > (repeated forever). It doesn't repeat forever. At least on my alpha it stops after several seconds and then top pulls up the normal display and runs fine. > JFYI > > Alex -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Oct 6 10:19:59 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5E87537B66D; Fri, 6 Oct 2000 10:19:55 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA08867; Fri, 6 Oct 2000 10:19:54 -0700 Date: Fri, 6 Oct 2000 10:16:30 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: alpha@FreeBSD.org Subject: [ RED FACE ] 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 just managed to find out that my cvsup hasn't been running for a week. I'm *such* an idiot. Never mind. Things probably will work better now. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Oct 6 12: 1: 7 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7177D37B502; Fri, 6 Oct 2000 12:01:00 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA09393; Fri, 6 Oct 2000 12:00:59 -0700 Date: Fri, 6 Oct 2000 11:57:35 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: alpha@FreeBSD.org Subject: red face better... 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 ...but not quite there yet.... Got around the 4MB hang issue, but now hang probing the SCSI bus (see below) I don't think that we're quite all happiness with 'compatibility' yet- so I think I'll do some fooling around to try and finishing some locking in the Qlogic driver (it should be just about ready to go....)... -matt Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel] in 9 seconds... Booting [kernel]... Entering kernel at 0xfffffc00003282a0.. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. Setting atkbd 0 at to atkbdc (string) Setting atkbd 0 irq to 1 (int) Setting atkbdc 0 at to isa (string) Setting atkbdc 0 port to 96 (int) Setting fd 0 at to fdc0 (string) Setting fd 0 drive to 0 (int) Setting fdc 0 at to isa (string) Setting fdc 0 drq to 2 (int) Setting fdc 0 irq to 6 (int) Setting fdc 0 port to 1008 (int) Setting mcclock 0 at to isa (string) Setting mcclock 0 port to 112 (int) Setting ppc 0 at to isa (string) Setting ppc 0 irq to 7 (int) Setting psm 0 at to atkbdc (string) Setting psm 0 irq to 12 (int) Setting sc 0 at to isa (string) Setting sio 0 at to isa (string) Setting sio 0 irq to 4 (int) Setting sio 0 port to 1016 (int) Setting sio 1 at to isa (string) Setting sio 1 flags to 80 (int) Setting sio 1 irq to 3 (int) Setting sio 1 port to 760 (int) Setting vga 0 at to isa (string) FreeBSD 5.0-CURRENT #0: Fri Oct 6 11:35:18 PDT 2000 mjacob@farrago.feral.com:/tstsys/compile/FARRAGO EB164 Digital AlphaPC 164 432 MHz, 432MHz 8192 byte page size, 1 processor. CPU: EV56 (21164A) major=7 minor=1 extensions=0x1 OSF PAL rev: 0x1000800020117 real memory = 265904128 (259672K bytes) Physical memory chunk(s): 0x006c4000 - 0x0ff0dfff, 260349952 bytes (31781 pages) avail memory = 252608512 (246688K bytes) Preloaded elf kernel "kernel" at 0xfffffc00006a4000. Preloaded elf module "ispfw.ko" at 0xfffffc00006a40c0. null: random: mem: cia0: <2117x Core Logic chipset> cia0: ALCOR/ALCOR2, pass 3 cia0: extended capabilities: 21 pcib0: <2117x PCI host bus adapter> on cia0 pci0: physical bus=0 found-> vendor=0x1077, dev=0x1020, revid=0x05 bus=0, slot=5, func=0 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=2 map[10]: type 4, range 32, base 00010200, size 8, enabled map[14]: type 1, range 32, base 82082000, size 12, enabled found-> vendor=0x1077, dev=0x1080, revid=0x01 bus=0, slot=6, func=0 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=0 map[10]: type 4, range 32, base 00010100, size 8, enabled map[14]: type 1, range 32, base 82081000, size 12, enabled found-> vendor=0x1077, dev=0x2200, revid=0x05 bus=0, slot=7, func=0 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=1 map[10]: type 4, range 32, base 00010000, size 8, enabled map[14]: type 1, range 32, base 82080000, size 12, enabled found-> vendor=0x8086, dev=0x0484, revid=0x43 bus=0, slot=8, func=0 class=00-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x1011, dev=0x0009, revid=0x22 bus=0, slot=9, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=3 map[10]: type 4, range 32, base 00010300, size 7, enabled map[14]: type 1, range 32, base 82083000, size 7, enabled found-> vendor=0x1095, dev=0x0646, revid=0x01 bus=0, slot=11, func=0 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=5 map[20]: type 4, range 32, base 00010380, size 4, enabled pci0: on pcib0 Qlogic ISP Driver, FreeBSD Version 5.3, Core Version 2.0 isp0: port 0x10200-0x102ff mem 0x82082000-0x82082fff irq 2 at device 5.0 on pci0 isp0: using Memory space register mapping isp0: interrupting at CIA irq 2 isp0: Ultra Mode Capable isp0: Board Revision 1040B, loaded F/W Revision 4.65.0 isp0: Last F/W revision was 5.57.1 isp1: port 0x10100-0x101ff mem 0x82081000-0x82081fff irq 0 at device 6.0 on pci0 isp1: using Memory space register mapping isp1: interrupting at CIA irq 0 isp1: bus 0 is in LVD Mode isp1: Board Revision 1080, loaded F/W Revision 8.13.0 isp1: Last F/W revision was 8.13.0 isp2: port 0x10000-0x100ff mem 0x82080000-0x82080fff irq 1 at device 7.0 on pci0 isp2: using Memory space register mapping isp2: interrupting at CIA irq 1 isp2: Board Revision 2200, loaded F/W Revision 2.1.14 isp2: Last F/W revision was 2.1.14 isp2: NVRAM Derived Node WWN 0x200000e08b01ae8b isp2: NVRAM Derived Port WWN 0x200300e08b01ae8b isab0: at device 8.0 on pci0 Bus Modes: Bus Park, Resource Lock, Configuration RAM: 0C00h,0800h-08FFh Port 92: enabled isa0: on isab0 pci0: (vendor=0x1011, dev=0x0009) at 9.0 irq 3 atapci0: port 0x10380-0x1038f irq 5 at device 11.0 on pci0 atapci0: Busmastering DMA enabled ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x10380 ata0: mask=03 status0=51 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0: at 0x1f0 irq 14 on atapci0 ata0: interrupting at ISA irq 14 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x10388 ata1: mask=00 status0=ff status1=ff ata1: probe allocation failed Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 sc-: sc0 already exists, using sc1 instead vga-: vga0 already exists, using vga1 instead isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices atkbdc0: at port 0x60,0x64 on isa0 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 atkbd0: irq 1 on atkbdc0 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 kbd0: atkbd0, generic (0), config:0x0, flags:0x1f0000 atkbd0: interrupting at ISA irq 1 psm0: current command byte:0061 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 psm0: failed to reset the aux device. fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: interrupting at ISA irq 6 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 mcclock0: at port 0x70-0x71 on isa0 Calibrating clock(s) ... PCC clock: 433005984 Hz (firmware 432900432 Hz) i8254 clock: 1192005 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency ppc0 failed to probe at irq 7 on isa0 sc0: no video adapter is found. sc0: failed to probe on isa0 sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A, console sio0: interrupting at ISA irq 4 sio1: reserved for low-level i/o sio1 failed to probe at port 0x2f8-0x2ff irq 3 flags 0x50 on isa0 vga0: failed to probe on isa0 sc1: no video adapter is found. sc1: failed to probe on isa0 vga1: failed to probe on isa0 isa_probe_children: probing PnP devices Timecounter "i8254" frequency 1193182 Hz Timecounter "alpha" frequency 433005984 Hz bpf: lo0 attached ata0-master: success setting WDMA2 on CMD chip ad0: ATA-4 disk at ata0-master ad0: 3098MB (6346368 sectors), 6296 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, WDMA2 ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 Creating DISK ad0 Waiting 2 seconds for SCSI devices to settle [ hangs ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Oct 6 12:20: 9 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 5AC5637B502 for ; Fri, 6 Oct 2000 12:20:07 -0700 (PDT) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e96JJqi49213; Fri, 6 Oct 2000 12:19:52 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 06 Oct 2000 12:20:10 -0700 (PDT) From: John Baldwin To: Matthew Jacob Subject: RE: red face better... Cc: alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 06-Oct-00 Matthew Jacob wrote: > > ...but not quite there yet.... > > Got around the 4MB hang issue, but now hang probing the SCSI bus (see below) I had this same hang when the PCI interrupts weren't be properly turned off when we schedule an ithread to run. One easy way to configure is to grab http://www.FreeBSD.org/~jhb/patches/ktr_verbose.patch and apply it. Then, disable the CTR0() for the clock interrupt in sys/alpha/alpha/interrupt.c (it's far too noisy), and add this hack to sys/cam/cam_xpt.c: Index: cam_xpt.c =================================================================== RCS file: /usr/cvs/src/sys/cam/cam_xpt.c,v retrieving revision 1.93 diff -u -r1.93 cam_xpt.c --- cam_xpt.c 2000/10/05 23:09:50 1.93 +++ cam_xpt.c 2000/10/06 19:10:59 @@ -40,6 +40,7 @@ #include #include #include +#include #ifdef PC98 #include /* geometry translation */ @@ -6119,6 +6120,7 @@ printf("Waiting %d seconds for SCSI " "devices to settle\n", SCSI_DELAY/1000); } + ktr_verbose = 1; xpt_for_all_busses(xptconfigfunc, NULL); } } This will basically dump the ktr output to the console, and should show an endless loop of PCI interrupts being scheduled. You will also need to add the following options to your kernel: options KTR options KTR_ENTRIES=1024 options KTR_MASK=KTR_INTR options KTR_COMPILE=0x3fffff options KTR_EXTEND Hmm, I suppose this isn't but so easy. :-P -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Oct 6 12:57:51 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0E8EB37B503; Fri, 6 Oct 2000 12:57:49 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA09631; Fri, 6 Oct 2000 12:57:48 -0700 Date: Fri, 6 Oct 2000 12:54:23 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: alpha@FreeBSD.org Subject: RE: red face better... 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 Not too complicated at all- good debugging tools in there- I'll let you know what's up .... -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Oct 6 14:10:47 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id EC40237B502 for ; Fri, 6 Oct 2000 14:10:37 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA29425; Fri, 6 Oct 2000 17:10:37 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e96LAb658069; Fri, 6 Oct 2000 17:10:37 -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, 6 Oct 2000 17:10:37 -0400 (EDT) To: Doug Rabson Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: size problems with INVARIANTS/DIAGNOSTIC -current kernels In-Reply-To: References: <14812.37571.725840.45245@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14814.15695.767816.773180@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug Rabson writes: > On Thu, 5 Oct 2000, Andrew Gallatin wrote: > > > > > Doug Rabson writes: > > > On Wed, 4 Oct 2000, Andrew Gallatin wrote: > > > > > > > > possibly something is wrong in the loader? > > > > > > > > > > > > > > > > > If so, the breakage has not happened recently. I'm seeing this with a > > > > 'loader' from late august, a netboot from late august & a netboot > > > > that's over 1 year old. > > > > > > > > Bear in mind that we seem to run just fine until the first time we > > > > attempt to call a function from a stack created for us by the > > > > palcode. However, that same function is callable when not running > > > > in an interrupt/trap/etc palcode-created context. > > > > > > > > I've "proved" this to myself by making sure that trap() is actually > > > > callable from the mainline kernel code (eg, not running out XentMM). > > > > I put a call to trap() in kern_malloc() & I put a call to printtrap() > > > > at the top of trap. I see trap being called from kern_malloc, but > > > > when its called by XentMM, random stuff happens. > > > > > > Bizarre. We are running on our own stack before mi_startup is > > > called() which should be before anything substantial is printed. I wonder > > > if somehow the ksp value in the context has been corrupted. > > > > Any ideas on how to debug this further? I'm at my wits end here.. > > > > In case its of any use, here's what the registers look like after one > > of these wacky crashes: > > Clearly something bad is happening and we are taking a trap, then fielding > it badly. You could try inserting 'call_pal halt' instructions in XentMM > so that we can see what the state looks like on the first fault. I altered XentMM thusly: Index: /home/home1/gallatin/ithreads/sys/alpha/alpha/exception.s =================================================================== RCS file: /home/ncvs/src/sys/alpha/alpha/exception.s,v retrieving revision 1.3 diff -u -r1.3 exception.s --- /home/home1/gallatin/ithreads/sys/alpha/alpha/exception.s 1999/08/28 00:38:26 1.3 +++ /home/home1/gallatin/ithreads/sys/alpha/alpha/exception.s 2000/10/06 20:52:41 @@ -87,7 +87,7 @@ */ PALVECT(XentMM) /* setup frame, save registers */ - +call_pal PAL_halt /* a0, a1, & a2 already set up */ ldiq a3, ALPHA_KENTRY_MM mov sp, a4 ; .loc 1 __LINE__ /ithreads data=0x3e6a78+0x32678 syms=[0x8+0x4ea98+0x8+0x39115] Entering ithreads at 0xfffffc0000330320... XentMM = 0xfffffc00005e1f2c Memory cluster count: 3 MEMC 0: pfn 0x0 cnt 0xa5 usage 0x1 MEMC 1: pfn 0xa5 cnt 0x3ee6 usage 0x0 Cluster 1 contains kernel Loading chunk after kernel: 0x3d3 / 0x3f8b MEMC 2: pfn 0x3f8b cnt 0x75 usage 0x1 Unrecognized boot flag '"'. Unrecognized boot flag '"'. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. kmem_init: kmemusage = 0xfffffe0000296000 halted CPU 0 halt code = 5 HALT instruction executed PC = fffffc00005e1f3c >>>e -n 32 r0 gpr: 0 ( R0) 000000000000002A gpr: 1 ( R1) FFFFFE0000296000 gpr: 2 ( R2) FFFFFC000066E005 gpr: 3 ( R3) 000000000000002A gpr: 4 ( R4) 0000000000000001 gpr: 5 ( R5) FFFFFC0007F15FE8 gpr: 6 ( R6) FFFFFC00006B51F8 gpr: 7 ( R7) FFFFFC00006E7240 gpr: 8 ( R8) FFFFFC00007AA000 gpr: 9 ( R9) 0000000000001030 gpr: A ( R10) FFFFFC00006EEAC0 gpr: B ( R11) FFFFFC00006C29E8 gpr: C ( R12) FFFFFC00006CED90 gpr: D ( R13) 0000000000000000 gpr: E ( R14) 000000002004FA30 gpr: F ( R15) 0000000020035C80 gpr: 10 ( R16) FFFFFE0000296000 gpr: 11 ( R17) 0000000000000004 gpr: 12 ( R18) 0000000000000001 gpr: 13 ( R19) FFFFFC00007A9C68 gpr: 14 ( R20) FFFFFC00007A9D40 gpr: 15 ( R21) 0000000000000008 gpr: 16 ( R22) 000000000000001E gpr: 17 ( R23) FFFFFC0000417524 gpr: 18 ( R24) 000000000000000F gpr: 19 ( R25) 0000000000000010 gpr: 1A ( R26) FFFFFC00005E1F3C gpr: 1B ( R27) FFFFFC0000416020 gpr: 1C ( R28) FFFFFC00007A9D70 gpr: 1D ( R29) FFFFFC00006D9008 gpr: 1E ( R30) FFFFFC00007A9C50 gpr: 1F ( R31) 0000000000000000 >>>e ksp ipr: 11 ( KSP) FFFFFC00007A9C50 >>>e -v -n 32 FFFFFC00007A9C50 vmem: 7A9C50 000000000000002A vmem: 7A9C58 FFFFFE0000296000 vmem: 7A9C60 FFFFFC000066E005 vmem: 7A9C68 000000000000002A vmem: 7A9C70 0000000000000001 vmem: 7A9C78 FFFFFC0007F15FE8 vmem: 7A9C80 FFFFFC00006B51F8 vmem: 7A9C88 FFFFFC00006E7240 vmem: 7A9C90 FFFFFC00007AA000 vmem: 7A9C98 0000000000001030 vmem: 7A9CA0 FFFFFC00006EEAC0 vmem: 7A9CA8 FFFFFC00006C29E8 vmem: 7A9CB0 FFFFFC00006CED90 vmem: 7A9CB8 0000000000000000 vmem: 7A9CC0 000000002004FA30 vmem: 7A9CC8 0000000020035C80 vmem: 7A9CD0 FFFFFC00007A9C68 vmem: 7A9CD8 FFFFFC00007A9D40 vmem: 7A9CE0 0000000000000008 vmem: 7A9CE8 000000000000001E vmem: 7A9CF0 FFFFFC0000417524 vmem: 7A9CF8 000000000000000F vmem: 7A9D00 0000000000000010 vmem: 7A9D08 FFFFFC00003F2FD0 vmem: 7A9D10 FFFFFC0000416020 vmem: 7A9D18 0000000000000823 vmem: 7A9D20 FFFFFC00007A9D70 vmem: 7A9D28 0000000000000000 vmem: 7A9D30 0000000000000001 vmem: 7A9D38 FFFFFC00007A9C18 vmem: 7A9D40 0000000000000006 vmem: 7A9D48 FFFFFC00003F2FDC vmem: 7A9D50 FFFFFC00006D9008 vmem: 7A9D58 0000000000000006 vmem: 7A9D60 00000000000003F9 vmem: 7A9D68 0000000000000000 vmem: 7A9D70 FFFFFC00003DFE34 vmem: 7A9D78 FFFFFC00006CEDC0 vmem: 7A9D80 FFFFFC00006E6B08 vmem: 7A9D88 FFFFFC00006AAFF0 vmem: 7A9D90 FFFFFC000033038C vmem: 7A9D98 00000000000003D5 vmem: 7A9DA0 0000000000000001 vmem: 7A9DA8 00000000200505E0 vmem: 7A9DB0 0000000020050780 vmem: 7A9DB8 0000000000000000 vmem: 7A9DC0 0000000000000000 vmem: 7A9DC8 0000000000000000 vmem: 7A9DD0 0000000000000000 vmem: 7A9DD8 0000000000000000 vmem: 7A9DE0 0000000000000000 The faulting address is 0xfffffc00003f2fdc (*(int *)kmemusage = 0x0;) /* code added to fault immediately after allocating kmemusage */ kmemusage is at 0xfffffe0000296000 Awaiting further instructions... ;) Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Oct 7 0:17:22 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.gplsucks.org (mail.gplsucks.org [63.227.213.93]) by hub.freebsd.org (Postfix) with ESMTP id 814DD37B66C for ; Sat, 7 Oct 2000 00:17:20 -0700 (PDT) Received: from localhost (bwoods2@localhost) by mail.gplsucks.org (8.11.1/8.11.1) with ESMTP id e977HDS68902 for ; Sat, 7 Oct 2000 00:17:24 -0700 (PDT) Date: Sat, 7 Oct 2000 00:17:12 -0700 (PDT) From: Bill Woods mail To: freebsd-alpha@freebsd.org Subject: Boot disk problems 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 OK, I have an Alphastation 200 4/233 that is presently running 4.1-stable just fine. I figured, I want to play with -current, so I grab the boot disks from current.freebsd.org and boot em...it says NO HARD DRIVE.... I dont understand whats up here, its running 4.1. but the 5.0-current boot disks dont see the HD's. here is a copy of SHOW DEVICE dka0.0.0.6.0 DKA0 WDIGITAL ENTERPRISE 1.91 dka200.2.0.6.0 DKA200 SEAGATE ST324430N 0300 dka500.5.0.6.0 DKA500 COMPAQ CD-ROM CR-503BCQ 1.1i dva0.0.0.0.1 DVA0 ewa0.0.0.11.0 EWA0 00-00-F8-23-5C-B5 pka0.7.0.6.0 PKA0 SCSI Bus ID 7 Help please........ I know I could source upgrade, but I would rather have a clean install Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Oct 7 1:39:49 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 4078637B503; Sat, 7 Oct 2000 01:39:47 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13hpWD-0005NF-00; Sat, 07 Oct 2000 08:39:45 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e978fmN91638; Sat, 7 Oct 2000 10:41:48 +0200 (CEST) (envelope-from wkb) Date: Sat, 7 Oct 2000 10:41:48 +0200 From: Wilko Bulte To: Matthew Jacob Cc: John Baldwin , alpha@freebsd.org Subject: Re: red face better... Message-ID: <20001007104148.A91612@freebie.demon.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Fri, Oct 06, 2000 at 11:57:35AM -0700 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Oct 06, 2000 at 11:57:35AM -0700, Matthew Jacob wrote: > ...but not quite there yet.... > > Got around the 4MB hang issue, but now hang probing the SCSI bus (see below) > > I don't think that we're quite all happiness with 'compatibility' yet- so I > think I'll do some fooling around to try and finishing some locking in the > Qlogic driver (it should be just about ready to go....)... If it is any consolation: I just screwed my Miata once again. Based on a -current world supped yesterday again this &*^ 'kernel stack not valid, halt' thing just after typing 'boot' SIGH -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Oct 7 3: 2:40 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from laurasia.com.au (lauras.lnk.telstra.net [139.130.93.142]) by hub.freebsd.org (Postfix) with ESMTP id A2DE237B502 for ; Sat, 7 Oct 2000 03:02:35 -0700 (PDT) Received: (from mike@localhost) by laurasia.com.au (8.9.3/8.9.1) id SAA08141 for freebsd-alpha@freebsd.org; Sat, 7 Oct 2000 18:02:32 +0800 (WST) Date: Sat, 7 Oct 2000 18:02:32 +0800 From: Michael Kennett To: freebsd-alpha@freebsd.org Subject: Alpha SIO errors Message-ID: <20001007180232.A8108@alpha.laurasia.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello All, I've been receiving a lot of SIO errors over a 56K modem connection: Oct 3 08:05:37 alpha /kernel: sio0: 1 more silo overflow (total 1) ... Oct 7 02:43:29 alpha /kernel: sio0: 1 more silo overflow (total 1184) From the dmesg output, the system is detecting a 16550A: Oct 3 04:56:43 alpha /kernel: FreeBSD 4.1-STABLE #0: Sun Aug 13 10:40:24 WST 2000 Oct 3 04:56:43 alpha /kernel: root@alpha.laurasia.com.au:/usr/src/sys/compile/PC164SX Oct 3 04:56:43 alpha /kernel: EB164 Oct 3 04:56:43 alpha /kernel: Digital AlphaPC 164SX 533 MHz, 531MHz Oct 3 04:56:43 alpha /kernel: 8192 byte page size, 1 processor. Oct 3 04:56:44 alpha /kernel: CPU: PCA56 (21164PC) major=9 minor=2 extensions=0x1 Oct 3 04:56:44 alpha /kernel: OSF PAL rev: 0x1000600020117 Oct 3 04:56:44 alpha /kernel: real memory = 266264576 (260024K bytes) Oct 3 04:56:44 alpha /kernel: avail memory = 254304256 (248344K bytes) ... Oct 3 04:56:45 alpha /kernel: sio0 at port 0x3f8-0x3ff irq 4 on isa0 Oct 3 04:56:45 alpha /kernel: sio0: type 16550A Oct 3 04:56:45 alpha /kernel: sio0: interrupting at ISA irq 4 Oct 3 04:56:45 alpha /kernel: sio1: reserved for low-level i/o Currently, the stty output is: # stty -a -f /dev/cuaa0 speed 115200 baud; 0 rows; 0 columns; lflags: -icanon -isig -iexten -echo -echoe -echok -echoke -echonl -echoctl -echoprt -altwerase -noflsh -tostop -flusho -pendin -nokerninfo -extproc iflags: -istrip -icrnl -inlcr -igncr -ixon -ixoff -ixany -imaxbel ignbrk -brkint -inpck -ignpar -parmrk oflags: -opost -onlcr -oxtabs cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb crtscts -dsrflow -dtrflow -mdmbuf cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = ; eol2 = ; erase = ^?; intr = ^C; kill = ^U; lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q; status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W; The sio0 port is being used by ppp. I'm at a bit of a loss on how to tackle this problem. The machine is *very* lightly loaded (i.e. sitting idle most of the time), and I'd like to resolve the overflows, as it is causing HDLC errors (bad frame check sequence fields) in ppp, and consequently for the link to drop out occassionally. Any advice would be appreciated, Regards, Michael Kennett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Oct 7 5:30:40 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 3180237B503 for ; Sat, 7 Oct 2000 05:30:38 -0700 (PDT) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 13ht7b-0003MV-00; Sat, 7 Oct 2000 14:30:35 +0200 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.0/8.11.0) id e97BZrk00800 for freebsd-alpha@freebsd.org; Sat, 7 Oct 2000 13:35:53 +0200 (CEST) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: Alpha SIO errors Date: Sat, 7 Oct 2000 11:35:49 +0000 (UTC) Message-ID: <8rn1ql$ne$1@kemoauc.mips.inka.de> References: <20001007180232.A8108@alpha.laurasia.com.au> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Michael Kennett wrote: > I've been receiving a lot of SIO errors over a 56K modem connection: Same here for my PC164 running PRE_SMPNG. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Oct 7 6:49: 4 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from cgi.sstar.com (cgi.sstar.com [209.205.176.12]) by hub.freebsd.org (Postfix) with ESMTP id 813F537B66C for ; Sat, 7 Oct 2000 06:49:02 -0700 (PDT) Received: from bluto.jimking.net (bluto.jimking.net [216.54.255.8]) by cgi.sstar.com (8.11.0/8.9.3) with ESMTP id e97Dms582929; Sat, 7 Oct 2000 08:48:54 -0500 (CDT) (envelope-from jim@jimking.net) Received: from marble (marble.lgc.com [134.132.228.4]) by bluto.jimking.net (8.11.0/8.11.0) with SMTP id e97DmoP86205; Sat, 7 Oct 2000 08:48:52 -0500 (CDT) (envelope-from jim@jimking.net) Message-ID: <02ab01c03065$552852b0$04e48486@marble> From: "Jim King" To: "Michael Kennett" , References: <20001007180232.A8108@alpha.laurasia.com.au> Subject: Re: Alpha SIO errors Date: Sat, 7 Oct 2000 08:48:50 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Michael Kennett wrote: > Hello All, > > I've been receiving a lot of SIO errors over a 56K modem connection: > [snip] > > The sio0 port is being used by ppp. > > I'm at a bit of a loss on how to tackle this problem. The machine is *very* > lightly loaded (i.e. sitting idle most of the time), and I'd like to resolve > the overflows, as it is causing HDLC errors (bad frame check sequence fields) > in ppp, and consequently for the link to drop out occassionally. > > Any advice would be appreciated, It gets worse: I tried to use a GPS receiver to drive ntpd. The GPS sends data at only 9600 bps, and my machine was also very lightly loaded, but FreeBSD would consistently lock up within a few hours. Based on my experience and messages I've seen on this list like yours I'd have to say that SIO on FreeBSD/Alpha is pretty much useless. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Oct 7 7:30:40 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id CD95B37B66D for ; Sat, 7 Oct 2000 07:30:38 -0700 (PDT) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 13huzl-0005jO-00; Sat, 7 Oct 2000 16:30:37 +0200 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.0/8.11.0) id e97Dcib00792 for freebsd-alpha@freebsd.org; Sat, 7 Oct 2000 15:38:44 +0200 (CEST) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: Alpha SIO errors Date: Sat, 7 Oct 2000 13:38:44 +0000 (UTC) Message-ID: <8rn914$n3$1@kemoauc.mips.inka.de> References: <20001007180232.A8108@alpha.laurasia.com.au> <8rn1ql$ne$1@kemoauc.mips.inka.de> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Christian Weisgerber wrote: > > I've been receiving a lot of SIO errors over a 56K modem connection: > Same here for my PC164 running PRE_SMPNG. It gets worse. When doing large FTP transfers over a serial ppp(8) link, the whole machine eventually locks up. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Oct 7 7:56:11 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from anchor-post-30.mail.demon.net (anchor-post-30.mail.demon.net [194.217.242.88]) by hub.freebsd.org (Postfix) with ESMTP id 3626137B503 for ; Sat, 7 Oct 2000 07:56:06 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-30.mail.demon.net with esmtp (Exim 2.12 #1) id 13hvON-0007vL-0U; Sat, 7 Oct 2000 15:56:04 +0100 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id QAA27988; Sat, 7 Oct 2000 16:02:35 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 7 Oct 2000 15:55:25 +0100 (BST) From: Doug Rabson To: Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: size problems with INVARIANTS/DIAGNOSTIC -current kernels In-Reply-To: <14814.15695.767816.773180@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, 6 Oct 2000, Andrew Gallatin wrote: > /ithreads data=0x3e6a78+0x32678 syms=[0x8+0x4ea98+0x8+0x39115] > Entering ithreads at 0xfffffc0000330320... > XentMM = 0xfffffc00005e1f2c > Memory cluster count: 3 > MEMC 0: pfn 0x0 cnt 0xa5 usage 0x1 > MEMC 1: pfn 0xa5 cnt 0x3ee6 usage 0x0 > Cluster 1 contains kernel > Loading chunk after kernel: 0x3d3 / 0x3f8b > MEMC 2: pfn 0x3f8b cnt 0x75 usage 0x1 > Unrecognized boot flag '"'. > Unrecognized boot flag '"'. > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > kmem_init: kmemusage = 0xfffffe0000296000 > > halted CPU 0 Hmm. I wonder if the kernel is running out of its bootstrap address space limits before it manages to finish initialising the vm system. Try increasing the value of NKPT in pmap.h to see if it helps. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Oct 7 11:12:42 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 4C00637B502 for ; Sat, 7 Oct 2000 11:12:40 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA10223; Sat, 7 Oct 2000 14:12:39 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e97ICda63131; Sat, 7 Oct 2000 14:12:39 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 7 Oct 2000 14:12:39 -0400 (EDT) To: Doug Rabson Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: size problems with INVARIANTS/DIAGNOSTIC -current kernels In-Reply-To: References: <14814.15695.767816.773180@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14815.26475.95721.701188@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug Rabson writes: > On Fri, 6 Oct 2000, Andrew Gallatin wrote: > > > /ithreads data=0x3e6a78+0x32678 syms=[0x8+0x4ea98+0x8+0x39115] > > Entering ithreads at 0xfffffc0000330320... > > XentMM = 0xfffffc00005e1f2c > > Memory cluster count: 3 > > MEMC 0: pfn 0x0 cnt 0xa5 usage 0x1 > > MEMC 1: pfn 0xa5 cnt 0x3ee6 usage 0x0 > > Cluster 1 contains kernel > > Loading chunk after kernel: 0x3d3 / 0x3f8b > > MEMC 2: pfn 0x3f8b cnt 0x75 usage 0x1 > > Unrecognized boot flag '"'. > > Unrecognized boot flag '"'. > > Copyright (c) 1992-2000 The FreeBSD Project. > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > > The Regents of the University of California. All rights reserved. > > kmem_init: kmemusage = 0xfffffe0000296000 > > > > halted CPU 0 > > Hmm. I wonder if the kernel is running out of its bootstrap address space > limits before it manages to finish initialising the vm system. Try > increasing the value of NKPT in pmap.h to see if it helps. I doubled it from 9 to 18 & still see the same behaviour.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Oct 7 12: 4:47 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 80FED37B502 for ; Sat, 7 Oct 2000 12:04:45 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id MAA94573; Sat, 7 Oct 2000 12:04:42 -0700 (PDT) (envelope-from obrien) Date: Sat, 7 Oct 2000 12:04:42 -0700 From: "David O'Brien" To: Bill Woods mail Cc: alpha@freebsd.org Subject: Re: Boot disk problems Message-ID: <20001007120442.D73312@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bwoods2@uswest.net on Sat, Oct 07, 2000 at 12:17:12AM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Oct 07, 2000 at 12:17:12AM -0700, Bill Woods mail wrote: > OK, I have an Alphastation 200 4/233 that is presently running 4.1-stable > just fine. I figured, I want to play with -current, so I grab the boot > disks from current.freebsd.org and boot em...it says NO HARD DRIVE.... Boot again, and then use the scroll back feature (using the scroll lock key and up arrow; or scroll bar on your xterm if serial console). Look to see if the `sym' driver attached or not. -- -- David (obrien@FreeBSD.org) Gnu is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Oct 7 13:33:30 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 2112137B503; Sat, 7 Oct 2000 13:33:27 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id QAA11387; Sat, 7 Oct 2000 16:33:26 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e97KXQ263517; Sat, 7 Oct 2000 16:33:26 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 7 Oct 2000 16:33:26 -0400 (EDT) To: freebsd-alpha@freebsd.org Cc: jhb@freebsd.org Subject: kernacc in mtx_validate X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14815.34524.543972.437937@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The calls to kerneacc in mtx_validate may fail when mtx_next points to "all_mtx" because it is a k0seg address, it is not in mapped memory. Because of this, anybody running with SMP_DEBUG & INVARIANTS will notice this at boot: panic: Assertion kernacc((caddr_t)all_mtx.mtx_next, 4, 1) == 1 failed at ../../alpha/alpha/synch_machdep.c:444 and/or panic: mtx_validate: mp=0xfffffc000068a978 mp->mtx_next=0xfffffc000068a7a8 The following works around the problem by merrily accepting any k0seg addr as possibly valid: Index: alpha/alpha/synch_machdep.c =================================================================== RCS file: /home/ncvs/src/sys/alpha/alpha/synch_machdep.c,v retrieving revision 1.5 diff -u -r1.5 synch_machdep.c --- alpha/alpha/synch_machdep.c 2000/10/04 01:20:49 1.5 +++ alpha/alpha/synch_machdep.c 2000/10/07 20:21:03 @@ -428,6 +428,9 @@ #ifdef SMP_DEBUG +#define ISK0SEG(va) \ + ((va >= ALPHA_K0SEG_BASE && va <= ALPHA_K0SEG_END)) + int mtx_validate __P((struct mtx *, int)); int @@ -441,10 +444,12 @@ return 0; mtx_enter(&all_mtx, MTX_DEF); - ASS(kernacc((caddr_t)all_mtx.mtx_next, 4, 1) == 1); + ASS(ISK0SEG((vm_offset_t)all_mtx.mtx_next) || + kernacc((caddr_t)all_mtx.mtx_next, 4, 1) == 1); ASS(all_mtx.mtx_next->mtx_prev == &all_mtx); for (i = 0, mp = all_mtx.mtx_next; mp != &all_mtx; mp = mp->mtx_next) { - if (kernacc((caddr_t)mp->mtx_next, 4, 1) != 1) { + if (!ISK0SEG((vm_offset_t)all_mtx.mtx_next) && + kernacc((caddr_t)mp->mtx_next, 4, 1) != 1) { panic("mtx_validate: mp=%p mp->mtx_next=%p", mp, mp->mtx_next); } Comments? 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 Sat Oct 7 13:54:59 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.gplsucks.org (mail.gplsucks.org [63.227.213.93]) by hub.freebsd.org (Postfix) with ESMTP id 48ED737B66C; Sat, 7 Oct 2000 13:54:57 -0700 (PDT) Received: from localhost (bwoods2@localhost) by mail.gplsucks.org (8.11.1/8.11.1) with ESMTP id e97Ksce96322; Sat, 7 Oct 2000 13:54:48 -0700 (PDT) Date: Sat, 7 Oct 2000 13:54:37 -0700 (PDT) From: Bill Woods mail To: "David O'Brien" Cc: Bill Woods mail , alpha@freebsd.org Subject: Re: Boot disk problems In-Reply-To: <20001007120442.D73312@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, this doesnt make it easy, says hit any key to reboot, I hit scroll lock and it starts to reboot) from what I can see, It doesnt look like it, I see this for sym: I honestly cant tell, damm thing scrolls to fast. Doesnt seem like it is though. On Sat, 7 Oct 2000, David O'Brien wrote: > On Sat, Oct 07, 2000 at 12:17:12AM -0700, Bill Woods mail wrote: > > OK, I have an Alphastation 200 4/233 that is presently running 4.1-stable > > just fine. I figured, I want to play with -current, so I grab the boot > > disks from current.freebsd.org and boot em...it says NO HARD DRIVE.... > > Boot again, and then use the scroll back feature (using the scroll lock > key and up arrow; or scroll bar on your xterm if serial console). Look > to see if the `sym' driver attached or not. > > -- > -- David (obrien@FreeBSD.org) > Gnu is Not Unix / Linux Is Not UniX > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Oct 7 14: 3:24 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id 8AF3B37B502; Sat, 7 Oct 2000 14:03:21 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e97L5Hh04220; Sat, 7 Oct 2000 14:05:17 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010072105.e97L5Hh04220@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Bill Woods mail Cc: "David O'Brien" , alpha@freebsd.org Subject: Re: Boot disk problems In-reply-to: Your message of "Sat, 07 Oct 2000 13:54:37 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 07 Oct 2000 14:05:17 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Unless someone snuck some code in while I wasn't looking, there is no part of the installation process that says "NO HARD DRIVE". Would you mind reporting the actual error message? Your vivid imagination may make for wonderful bedtime stories for small children, but it doesn't actually help us any at all. > Well, this doesnt make it easy, says hit any key to reboot, I hit > scroll lock and it starts to reboot) from what I > can see, It doesnt look like it, I see this for sym: > > I honestly cant tell, damm thing scrolls to fast. Doesnt seem like it is > though. > > > > On Sat, 7 Oct 2000, David O'Brien wrote: > > > On Sat, Oct 07, 2000 at 12:17:12AM -0700, Bill Woods mail wrote: > > > OK, I have an Alphastation 200 4/233 that is presently running 4.1-stable > > > just fine. I figured, I want to play with -current, so I grab the boot > > > disks from current.freebsd.org and boot em...it says NO HARD DRIVE.... > > > > Boot again, and then use the scroll back feature (using the scroll lock > > key and up arrow; or scroll bar on your xterm if serial console). Look > > to see if the `sym' driver attached or not. > > > > -- > > -- David (obrien@FreeBSD.org) > > Gnu is Not Unix / Linux Is Not UniX > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Oct 7 14:21: 8 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.gplsucks.org (mail.gplsucks.org [63.227.213.93]) by hub.freebsd.org (Postfix) with ESMTP id 343A037B503; Sat, 7 Oct 2000 14:21:03 -0700 (PDT) Received: from localhost (bwoods2@localhost) by mail.gplsucks.org (8.11.1/8.11.1) with ESMTP id e97LKiq00851; Sat, 7 Oct 2000 14:20:54 -0700 (PDT) Date: Sat, 7 Oct 2000 14:20:43 -0700 (PDT) From: Bill Woods mail To: Mike Smith Cc: Bill Woods mail , "David O'Brien" , alpha@freebsd.org Subject: Re: Boot disk problems In-Reply-To: <200010072105.e97L5Hh04220@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org OKOK, I paraphrased..... This is whats on the screen... A RED background with a grey box. in the box , in black letteringis "Probing devices, please wait (this can take a while)" and at the bottom in white letters I see this: Fatal Error: Unable to open disk da0 - PRESS ANY KEY TO REBOOT ------------------------------------------------------------------- On Sat, 7 Oct 2000, Mike Smith wrote: > > Unless someone snuck some code in while I wasn't looking, there is no > part of the installation process that says "NO HARD DRIVE". > > Would you mind reporting the actual error message? Your vivid > imagination may make for wonderful bedtime stories for small children, > but it doesn't actually help us any at all. > > > Well, this doesnt make it easy, says hit any key to reboot, I hit > > scroll lock and it starts to reboot) from what I > > can see, It doesnt look like it, I see this for sym: > > > > I honestly cant tell, damm thing scrolls to fast. Doesnt seem like it is > > though. > > > > > > > > On Sat, 7 Oct 2000, David O'Brien wrote: > > > > > On Sat, Oct 07, 2000 at 12:17:12AM -0700, Bill Woods mail wrote: > > > > OK, I have an Alphastation 200 4/233 that is presently running 4.1-stable > > > > just fine. I figured, I want to play with -current, so I grab the boot > > > > disks from current.freebsd.org and boot em...it says NO HARD DRIVE.... > > > > > > Boot again, and then use the scroll back feature (using the scroll lock > > > key and up arrow; or scroll bar on your xterm if serial console). Look > > > to see if the `sym' driver attached or not. > > > > > > -- > > > -- David (obrien@FreeBSD.org) > > > Gnu is Not Unix / Linux Is Not UniX > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-alpha" in the body of the message > > > > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > V I C T O R Y N O T V E N G E A N C E > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Oct 7 14:52:52 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 66B4937B502; Sat, 7 Oct 2000 14:52:45 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA12005; Sat, 7 Oct 2000 17:52:39 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e97Lqcv63663; Sat, 7 Oct 2000 17:52:38 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 7 Oct 2000 17:52:38 -0400 (EDT) To: John Baldwin Cc: Matthew Jacob , alpha@FreeBSD.ORG Subject: RE: red face better... In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14815.39431.983740.401656@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John Baldwin writes: > > On 06-Oct-00 Matthew Jacob wrote: > > > > ...but not quite there yet.... > > > > Got around the 4MB hang issue, but now hang probing the SCSI bus (see below) > > I had this same hang when the PCI interrupts weren't be properly turned off <..> I'm seeing the same problems as Matt on an AS500 5/266 and a Miata GL. Both of these machines are running with serial consoles -- Does your test box have a serial or graphics console? If graphics, can you see if it still works w/a serial console? From the miata: <..> net_open: server path: /freebsd/diskless.a/ Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel] in 9 seconds... Type '?' for a list of commands, 'help' for more detailed help. ok boot ithreads /ithreads data=0x35daa0+0x48e4a syms=[0x8+0x3bd90+0x8+0x2b6e7] Entering ithreads at 0xfffffc00003297a0... sio1: gdb debugging port Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #13: Sat Oct 7 16:44:01 EDT 2000 gallatin@thunder.cs.duke.edu:/a/muffin/export/ari_scratch2/gallatin/current/sys/compile/UP1000 Digital Personal Workstation (Miata) Digital Personal WorkStation 500au, 500MHz 8192 byte page size, 1 processor. CPU: EV56 (21164A) major=7 minor=0 extensions=0x1 OSF PAL rev: 0x1000000020116 real memory = 534937600 (522400K bytes) avail memory = 514621440 (502560K bytes) Preloaded elf kernel "ithreads" at 0xfffffc0000710000. cia0: <2117x Core Logic chipset> cia0: Pyxis, pass 1 cia0: extended capabilities: 1 pcib0: <2117x PCI host bus adapter> on cia0 pci0: on pcib0 dc0: port 0x9000-0x907f mem 0x80151000-0x8015107f irq 0 at device 3.0 on pci0 dc0: interrupting at CIA irq 0 dc0: Ethernet address: 00:00:f8:76:43:0f miibus0: on dc0 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x90a0-0x90af,0x3f4-0x3f7,0x1f0-0x1f7 irq 238 at device 7.1 on pci0 atapci0: Busmastering DMA enabled ata0: at 0x1f0 irq 14 on atapci0 ata0: interrupting at ISA irq 14 atapci1: port 0x374-0x377,0x170-0x177 mem 0x80140000-0x8014ffff irq 239 at device 7.2 on pci0 atapci1: Busmastering DMA not supported pci0: at 7.3 irq 234 pci0: (vendor=0x10e8, dev=0x8043) at 11.0 irq 4 pcib1: at device 20.0 on pci0 pci1: on pcib1 isp0: port 0x8000-0x80ff mem 0x80010000-0x80010fff irq 3 at device 4.0 on pci1 isp0: interrupting at CIA irq 3 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd0: interrupting at ISA irq 1 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: interrupting at ISA irq 6 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 mcclock0: at port 0x70-0x71 on isa0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A, console sio0: interrupting at ISA irq 4 sio1: reserved for low-level i/o Timecounter "i8254" frequency 1193182 Hz Timecounter "alpha" frequency 499857408 Hz acd0: CDROM at ata0-master using PIO3 sched_ithd pid 14(intr: sched_softintr pid 11(softinterrupt) spending=0x40 isched_softintr pid 11(softinterrupt) spending=0x40 sp0) need=0 alpha_dispatch_intr: setrunqueue 14 ithd_loop pid 14(intr: isp0) need=1 ithd_loop pid 14 ih=0xfffffe0000af0700: 0xfffffc0000366760(0xfffffe0000af6a00) flg=0 ithd_loop pid 14: done intr_soft pid 11: resumed intr_soft pid 11(softinterrupt) spending=0x40 intr_soft pid 11: done sched_softintr pid 11(softinterrupt) spending=0x40 sched_softintr: setrunqueue 11 intr_soft pid 11: resumed intr_soft pid 11(softinterrupt) spending=0x40 intr_soft pid 11: done sched_softintr pid 11(softinterrupt) spending=0x40 sched_softintr: setrunqueue 11 intr_soft pid 11: resumed intr_soft pid 11(softinterrupt) spending=0x40 intr_soft pid 11: done sched_softintr pid 11(softinterrupt) spending=0x40 sched_softintr: setrunqueue 11 sched_softintr pid 11(softinterrupt) spending=0x40 intr_soft pid 11: resumed intr_soft pid 11(softinterrupt) spending=0x40 intr_soft pid 11: done sched_softintr pid 11(softinterrupt) spending=0x40 sched_softintr: setrunqueue 11 intr_soft pid 11: resumed <...> Cheers, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message