mutex lock assertion panic in vm_page_free() on sparc64

[Ruslan Ermilov]

Hi Alan,

On Tue, Feb 22, 2005 at 03:29:41PM -0600, Alan Cox wrote:
> On Tue, Feb 22, 2005 at 02:22:56PM -0500, Jung-uk Kim wrote:
> > 
> > FYI, anholt says 'backing vm/uma_core.c to r1.114 has fixed the 
> > issue':
> > 
> > http://docs.freebsd.org/cgi/mid.cgi?1109089389.4267.7.camel
> 
> Ok, thanks.  I'd still like to see the contents of the offending
> page.  When UMA overwrites the page's object field with a slab
> pointer, it sets a flag within the page.  I'd very much like
> to know if this flag is set.
> 
I had trouble saving a kernel core -- 6 or 7 times I tried this,
it resulted in the same panic.  Finally, I gave up and reverted
to vm/uma_core.c,v 1.114, this game me a working savecore.
Unfortunately, either kdgb(1) doesn't work on sparc64 at the
moment, or this core is troublesome -- it would endlessly print
this:

kgdb: kvm_read: invalid address (203d2025)
kgdb: kvm_read: invalid address (6e666f20)
kgdb: kvm_read: invalid address (203d2025)
kgdb: kvm_read: invalid address (6e666f20)
kgdb: kvm_read: invalid address (203d2025)
kgdb: kvm_read: invalid address (6e666f20)
kgdb: kvm_read: invalid address (203d2025)
kgdb: kvm_read: invalid address (6e666f20)
...

At least I can confirm that reverting to rev. 1.114 fixes a
problem.


Cheers,
-- 
Ruslan Ermilov
ru at FreeBSD.org
FreeBSD committer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20050223/6010507c/attachment-0001.bin