From owner-freebsd-mips@FreeBSD.ORG Tue May 13 14:27:21 2003 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 765B537B401 for ; Tue, 13 May 2003 14:27:21 -0700 (PDT) Received: from netlx010.civ.utwente.nl (netlx010.civ.utwente.nl [130.89.1.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0553D43FB1 for ; Tue, 13 May 2003 14:27:20 -0700 (PDT) (envelope-from freebsd.org@graphicscave.com) Received: from graphicscave (graphicscave.student.utwente.nl [130.89.167.223]) by netlx010.civ.utwente.nl (8.11.4/HKD) with ESMTP id h4DLRIu21961 for ; Tue, 13 May 2003 23:27:18 +0200 From: "Steffen M. Boelaars" Organization: GraphicsCave To: freebsd-mips@freebsd.org Date: Tue, 13 May 2003 23:27:17 +0200 User-Agent: KMail/1.5.1 References: <200305081434.12830.freebsd.org@graphicscave.com> <20030508191410.A51169@FreeBSD.org> In-Reply-To: <20030508191410.A51169@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200305132327.17373.freebsd.org@graphicscave.com> X-UTwente-MailScanner: Found to be clean Subject: Re: What's going on here. Can I help? Test? X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd.org@graphicscave.com List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2003 21:27:21 -0000 > robert@ is working on an R10K machine as well (an Octane?). I'm > working on IP22s. I have a whole shitload of SGI's here: Indigo R3000 33MHz Indy R4400 150MHz o2 R5000 180MHz Indigo2 R4400 250MHz Indigo2 R10000 195MHz Octane R12000 300MHz Scream if I can do something with them for this project. They are just sitting here (Except for the Octane, that's my main workstation :) > Nothing really works now. A ton of kernel code is still needed, > currently I'm trying to get exceptions working properly (the NetBSD > code leaves a bit to be desired and doesn't work right @64-bits). > Also I am seeing a lot of unexpected access (deterministic) to bogus > bits of memory, possibly as a result of stack corruption, or a > stack size issue, I'm not sure. Using random printfs seems to make > these things better/worse non-deterministically, but a printf in a > given location deterministically changes how things work. This may > be evidence of a compiler bug, but I'm not sure. Certainly there > are bugs in the compiler. With -O the compiler ICEs, I seem to > recall. imp@ suggests maybe it's a cache issue, but I've tried > with L1 cache disabled, with the kernel running in KSEG1, and so > on, to no avail. That looks like a lot of work. i've never worked at an OS before, but Hey, I got to start some day somewhere, not? I have no clue what I could do, but there must be something (Even if it's just testing/trying some things some day) Steffen M. Boelaars