From owner-freebsd-mips@FreeBSD.ORG Thu May 8 05:34:15 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 90EF237B401 for ; Thu, 8 May 2003 05:34:15 -0700 (PDT) Received: from netlx014.civ.utwente.nl (netlx014.civ.utwente.nl [130.89.1.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C32843F85 for ; Thu, 8 May 2003 05:34:14 -0700 (PDT) (envelope-from freebsd.org@graphicscave.com) Received: from graphicscave (graphicscave.student.utwente.nl [130.89.167.223]) by netlx014.civ.utwente.nl (8.11.4/HKD) with ESMTP id h48CYDi00311 for ; Thu, 8 May 2003 14:34:13 +0200 From: "Steffen M. Boelaars" Organization: GraphicsCave To: freebsd-mips@freebsd.org Date: Thu, 8 May 2003 14:34:12 +0200 User-Agent: KMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200305081434.12830.freebsd.org@graphicscave.com> X-UTwente-MailScanner: Found to be clean Subject: 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: Thu, 08 May 2003 12:34:15 -0000 Hello, I just discovered that this project exists. How great! Now the thing is, that I want to create this 'hackme' system (to use at big hacking-lan-parties), running FreeBSD. But to run it on SGI hardware would be great. FreeBSD is a very secure OS. But if you got some exploit, that you invented/found on a hackme box, to root it eventualy, then you can play internet-terrorist. But not if the exploit you got only works on an SGI system ;) And apart from this I am also myself just very interested in getting another OS than Irix to run on one of my many SGI systems. I have an Indigo2 r10000 195 MHz here that is dieing to be used. Sooo.... after all this blablabla: how's things with the project, where can I do something/anything at all to make things work a bit more? :-D Greetings, Steffen M. Boelaars out there somewhere in The Netherlands. From owner-freebsd-mips@FreeBSD.ORG Thu May 8 17:14:10 2003 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 931) id 5C9C737B401; Thu, 8 May 2003 17:14:10 -0700 (PDT) Date: Thu, 8 May 2003 19:14:10 -0500 From: Juli Mallett To: "Steffen M. Boelaars" Message-ID: <20030508191410.A51169@FreeBSD.org> References: <200305081434.12830.freebsd.org@graphicscave.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200305081434.12830.freebsd.org@graphicscave.com>; from freebsd.org@graphicscave.com on Thu, May 08, 2003 at 02:34:12PM +0200 X-Title: Code Maven X-Towel: Yes X-Negacore: Yes X-Authentication-Warning: localhost: juli pwned teh intarweb cc: freebsd-mips@freebsd.org 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 List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2003 00:14:10 -0000 * "Steffen M. Boelaars" [ Date: 2003-05-08 ] [ w.r.t. What's going on here. Can I help? Test? ] > And apart from this I am also myself just very interested in getting another > OS than Irix to run on one of my many SGI systems. > I have an Indigo2 r10000 195 MHz here that is dieing to be used. robert@ is working on an R10K machine as well (an Octane?). I'm working on IP22s. > Sooo.... after all this blablabla: how's things with the project, where can I > do something/anything at all to make things work a bit more? 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. Thanx, juli. -- juli mallett. email: jmallett@freebsd.org; efnet: juli; From owner-freebsd-mips@FreeBSD.ORG Fri May 9 22:46:08 2003 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 931) id C625037B401; Fri, 9 May 2003 22:46:08 -0700 (PDT) Date: Sat, 10 May 2003 00:46:08 -0500 From: Juli Mallett To: freebsd-mips@FreeBSD.org Message-ID: <20030510004608.A85630@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-Title: Code Maven X-Towel: Yes X-Negacore: Yes X-Authentication-Warning: localhost: juli pwned teh intarweb Subject: some heads ups and the like. X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 May 2003 05:46:09 -0000 FYI: Updating the compiler config and related to Suck a lot less: o) Use gp-relative accesses of stuff. o) Use the elf64.h provided with GCC. o) Fix optimisation. o) Use dwarf2 debugging (so plain -g works). o) Remove redundant code. o) Turn off OBJECT_FORMAT_COFF. Made elf2ecoff work for kernels (and presumably loaders as such): o) Ignore PT_MIPS_REGINFO (this affects most anything) o) Ignore PT_INTERP, PT_DYNAMIC (this affects solely the kernel and other dynamic executables, it is safely ignored in the kernel as they're unused... Just have to say that people booting without sash on an ECOFF-pure system must use no loader?) Snag DDB support from NetBSD. o) Note: it is useless, as exceptions are b0rked, maybe because of addressing issues with 64-bits vs. 32?? o) BadVAddr exceptions do work to the point of printf but not DDB. This is as useful as ARCS. As such, ARCS exceptions are now switched off. I've also done random fixes to the kernel: o) Huge temp stack this is XXX, but just in case. o) Call mutex_init, this fixes the random mutex errors I was seeing, of most sorts, but there is something wrong as down the road (with witness) Giant seems to be unused but that should not be the case. o) SYSINIT printfs so you can tell where stuff goes. o) Page zeroing from Alpha pmap. I am looking at approaches towards doing a full pmap, this is just to make the wrong places more apparent. Thanx, juli. -- juli mallett. email: jmallett@freebsd.org; efnet: juli;