From owner-freebsd-mips@FreeBSD.ORG Mon Apr 26 19:49:33 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D250106566C for ; Mon, 26 Apr 2010 19:49:33 +0000 (UTC) (envelope-from juli@clockworksquid.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 13E608FC14 for ; Mon, 26 Apr 2010 19:49:32 +0000 (UTC) Received: by gyh20 with SMTP id 20so6484486gyh.13 for ; Mon, 26 Apr 2010 12:49:27 -0700 (PDT) Received: by 10.100.24.17 with SMTP id 17mr97928anx.53.1272311367531; Mon, 26 Apr 2010 12:49:27 -0700 (PDT) MIME-Version: 1.0 Sender: juli@clockworksquid.com Received: by 10.100.131.16 with HTTP; Mon, 26 Apr 2010 12:49:07 -0700 (PDT) In-Reply-To: References: From: Juli Mallett Date: Mon, 26 Apr 2010 12:49:07 -0700 X-Google-Sender-Auth: 7f88278d8eef5fa2 Message-ID: To: "C. Jayachandran" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-mips@freebsd.org Subject: Re: Crashes with the current -HEAD X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Apr 2010 19:49:33 -0000 On Mon, Apr 26, 2010 at 12:36, C. Jayachandran w= rote: > I checked a few versions, =A0r206714 does not have the crash, r206717 > has. I haven't looked at the changes yet, but if you have any > suggestions let me know. There are two things there that could be problematic. The first is that interrupt enable/disable has been changed. I don't know anything about hazards on RMI systems, but if there's an interrupt disable hazard, you may want to change CLEAR_STATUS and DO_AST macros (in exception.S and asm.h respectively) to use many more nops or ehbs and see if that makes the problem go away. The second is the changes to the lmem pages. If you reduce MAXMEM so that all of your memory is addressable within KSEG0 and KSEG1, you won't use lmem at all. If that makes the problem go away, it suggests there is trouble in that area. I'm glad to do whatever I can, but I've been unable to get any RMI hardware, so all I can do is suggest you look at those two areas your try to narrow down to the specific change that caused the problem. Thanks, Juli.