From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (971110.SGI.8.8.8/960327.SGI.AUTOCF) via SMTP id NAA512052 for ; Thu, 29 Jan 1998 13:25:33 -0800 (PST) Return-Path: Received: (from majordomo-owner@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id NAA09633 for linux-list; Thu, 29 Jan 1998 13:24:56 -0800 Received: from sgi.sgi.com (sgi.engr.sgi.com [192.26.80.37]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA09621 for ; Thu, 29 Jan 1998 13:24:55 -0800 Received: from informatik.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.4.1]) by sgi.sgi.com (950413.SGI.8.6.12/970507) via ESMTP id NAA26933 for ; Thu, 29 Jan 1998 13:24:53 -0800 env-from (ralf@mailhost.uni-koblenz.de) Received: from zaphod (ralf@zaphod.uni-koblenz.de [141.26.4.13]) by informatik.uni-koblenz.de (8.8.8/8.8.8) with SMTP id WAA04468; Thu, 29 Jan 1998 22:24:50 +0100 (MET) Received: by zaphod (SMI-8.6/KO-2.0) id WAA08923; Thu, 29 Jan 1998 22:24:48 +0100 Message-ID: <19980129222448.55873@uni-koblenz.de> Date: Thu, 29 Jan 1998 22:24:48 +0100 From: ralf@uni-koblenz.de To: Thomas Bogendoerfer Cc: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com Subject: Re: strange problem with my oli M700 References: <19980129212705.29618@alpha.franken.de> <19980129221750.18001@uni-koblenz.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <19980129221750.18001@uni-koblenz.de>; from ralf@uni-koblenz.de on Thu, Jan 29, 1998 at 10:17:50PM +0100 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk On Thu, Jan 29, 1998 at 10:17:50PM +0100, ralf@uni-koblenz.de wrote: > > I'm trying to read the firmware prom of my Olivetti M700 (Magnum 4000 clone). > > When access the address 0x9fc00000 (which is the KSEG0 address of the prom) > > the box freezes immidiately. Does anybody know why ? And how could I access > > the prom otherwise ? > > Did you try uncached accesses via KSEG1? I wouldn't wonder if the used > PROMs can't cope with the bursts generated for filling a cacheline. Which btw reminds me that enabling the second level cache on a Indy also makes call into the ARC firmware crash. Dunno why. Ralf