Date: Tue, 13 May 2003 23:27:17 +0200 From: "Steffen M. Boelaars" <freebsd.org@graphicscave.com> To: freebsd-mips@freebsd.org Subject: Re: What's going on here. Can I help? Test? Message-ID: <200305132327.17373.freebsd.org@graphicscave.com> In-Reply-To: <20030508191410.A51169@FreeBSD.org> References: <200305081434.12830.freebsd.org@graphicscave.com> <20030508191410.A51169@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305132327.17373.freebsd.org>