Date: Mon, 26 Apr 2010 12:49:07 -0700 From: Juli Mallett <jmallett@FreeBSD.org> To: "C. Jayachandran" <c.jayachandran@gmail.com> Cc: freebsd-mips@freebsd.org Subject: Re: Crashes with the current -HEAD Message-ID: <l2keaa228be1004261249sad10dfao9ad91186d97af5ea@mail.gmail.com> In-Reply-To: <t2g98a59be81004261236pf417a26cye108cb2ccb823d41@mail.gmail.com> References: <g2v98a59be81004230638q91b48b47i99ec64a137790bbc@mail.gmail.com> <q2jeaa228be1004231125hed2bbe9fj6680b29fdd63511a@mail.gmail.com> <t2g98a59be81004261236pf417a26cye108cb2ccb823d41@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 26, 2010 at 12:36, C. Jayachandran <c.jayachandran@gmail.com> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?l2keaa228be1004261249sad10dfao9ad91186d97af5ea>