Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 28 Apr 2004 23:42:27 +0200
From:      Wilko Bulte <wkb@freebie.xs4all.nl>
To:        Andrew Gallatin <gallatin@cs.duke.edu>
Cc:        alpha@freebsd.org
Subject:   Re: pmap_emulate_reference() panics still ongoing
Message-ID:  <20040428214227.GA23106@freebie.xs4all.nl>
In-Reply-To: <16527.48288.319462.214843@grasshopper.cs.duke.edu>
References:  <20040428084120.GA25958@ip.net.ua> <16527.42479.941859.703698@grasshopper.cs.duke.edu> <20040428135850.GA43106@ip.net.ua> <16527.48288.319462.214843@grasshopper.cs.duke.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 28, 2004 at 10:16:00AM -0400, Andrew Gallatin wrote:
> 
> Ruslan Ermilov writes:
>  > On Wed, Apr 28, 2004 at 08:39:11AM -0400, Andrew Gallatin wrote:
>  > > 
>  > > Ruslan Ermilov writes:
>  > >  > Andrew,
>  > >  > 
>  > >  > This is with latest src/sys/alpha/alpha/pmap.c,v 1.146.
>  > >  > 
>  > >  > db> where
>  > >  > Debugger() at Debugger+0x38
>  > >  > __panic() at __panic+0x228
>  > >  > pmap_emulate_reference() at pmap_emulate_reference+0x15c
>  > >  > trap() at trap+0x3dc
>  > >  > XentMM() at XentMM+0x2c
>  > >  > --- memory management fault (from ipl 0) ---
>  > >  > --- user mode ---
>  > > 
>  > > Damn.  Did the change make it any worse for you?
>  > > 
>  > No, I can't say this made things any worse.  ;)
> 
> Good.
> 
>  > This is not a very fast runner (166MHz EV4, 64MB RAM, swap
>  > is used).  Since I've upgraded it to 5-CURRENT, running the
>  > GENERIC kernel, my 5 attempts to build world ended up with
>  > this panic (often the panic message was unreadable, this one,
>  > after I've upgraded kernel to the latest pmap.c, was probably
>  > a good exception).  Now I've built the debug version of the
>  > kernel.  Will it be of some help?
> 
> Wow, and I thought my 600MHz ev67 was slow.  At least you can

This is a true-blue NoName LCA EV4 board ;)

>  > (Hardly relevant, but it was happy running 4.10-RC.)
> 
> Very relevant -- it means the bug is new to 5.x

Which also proves that having some older hardware around helps
testing.

-- 
Wilko Bulte				wilko@FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040428214227.GA23106>