Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 23 Feb 2005 10:45:52 +0200
From:      Ruslan Ermilov <ru@freebsd.org>
To:        Alan Cox <alc@cs.rice.edu>
Cc:        Peter Grehan <grehan@freebsd.org>
Subject:   Re: mutex lock assertion panic in vm_page_free() on sparc64
Message-ID:  <20050223084552.GA88626@ip.net.ua>
In-Reply-To: <20050222212941.GU3121@noel.cs.rice.edu>
References:  <20050222110318.GA41460@ip.net.ua> <20050222142710.GA42507@ip.net.ua> <20050222190904.GC26262@cs.rice.edu> <200502221422.56994.jkim@niksun.com> <20050222212941.GU3121@noel.cs.rice.edu>

next in thread | previous in thread | raw e-mail | index | archive | help

--PNTmBPCT7hxwcZjr
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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:
> >=20
> > FYI, anholt says 'backing vm/uma_core.c to r1.114 has fixed the=20
> > issue':
> >=20
> > http://docs.freebsd.org/cgi/mid.cgi?1109089389.4267.7.camel
>=20
> 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.
>=20
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)
=2E..

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


Cheers,
--=20
Ruslan Ermilov
ru@FreeBSD.org
FreeBSD committer

--PNTmBPCT7hxwcZjr
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)

iD8DBQFCHELAqRfpzJluFF4RAjaOAJ4/10rDbN8ykwxzYyGxGLNHA+dA0gCfXu6O
hRFfZjXYQ8utZ01NSvpbGLQ=
=5Y1f
-----END PGP SIGNATURE-----

--PNTmBPCT7hxwcZjr--



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