Date: Tue, 7 Mar 2000 08:20:07 +0100 From: Wilko Bulte <wilko@yedi.iaf.nl> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: "Waite, Michael" <Michael.Waite@compaq.com>, freebsd-alpha@FreeBSD.ORG Subject: Re: Alpha ISO is fantastic! Message-ID: <20000307082006.A52415@yedi.iaf.nl> In-Reply-To: <14528.17265.955978.964252@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Fri, Mar 03, 2000 at 06:03:27PM -0500 References: <212CC57E84B8D111AD780000F84AA049083C2C11@mroexc2.tay.dec.com> <20000303232726.A5993@yedi.iaf.nl> <14528.17265.955978.964252@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 03, 2000 at 06:03:27PM -0500, Andrew Gallatin wrote: > > Wilko Bulte writes: > > I'd be very interested to see how the XP1000 behaves running X as I see > > problems on all my Alphas (Miata GL , Miata MX5 and EB64+/Aspen Alpine) > > when running X. > > I suspect that it will do much better because a tsunami chipset > behaves a lot like an x86 on bad accesses -- reads to bad addresses in > device memory return -1 and writes are ignored. All other platforms > give you a machine check. This confused the heck out of me when I was > doing the tsunami support. > > On a related note -- Wilko, can you try compiling X with either -O or > -O0? I just tracked down a nasty bug troubling somebody else which > was caused by gcc generating bad code. I have a sneaking suspicion > that the compiler might be behind at least some of your pain. Just tried the S3 server freshly compiled with -O0 and the same h/w as my previous test. No joy, spontaneous reboot again. -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000307082006.A52415>