Date: Mon, 12 May 2014 13:49:55 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Michael Moll <kvedulv@kvedulv.de> Cc: freebsd-sparc64@freebsd.org Subject: Re: panic on fresh -CURRENT Message-ID: <20140512104955.GE74331@kib.kiev.ua> In-Reply-To: <20140511205359.GA63005@darkthrone.kvedulv.de> References: <20140510213824.GA23740@darkthrone.kvedulv.de> <20140510215647.GU74331@kib.kiev.ua> <20140511073743.GA38923@darkthrone.kvedulv.de> <20140511172622.GA74331@kib.kiev.ua> <20140511205359.GA63005@darkthrone.kvedulv.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--w9gceUn8eOVn8+8k Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, May 11, 2014 at 10:53:59PM +0200, Michael Moll wrote: > Hi, >=20 > On Sun, May 11, 2014 at 08:26:23PM +0300, Konstantin Belousov wrote: > > Please try the following patch, it slightly modernizes the tsb page free > > sequence to the current VM KPI, and also adds assertions which reflect > > my understanding of the correct state of the tsb object and pages. > > The patch is not a fix, it only should somewhat improve debugging. > > And yes, enable INVARIANTS. >=20 > OK, I'm now at r265844 + your patch and enabled INVARIANTS. However, > the initial panic is not reproducible anymore, but I get different > ones and can't get hold of a dump, there are quite some messages > "cheetah_ipi_single: couldn't send IPI to module 0x1" after the panics. This is somewhat consistent, in fact, with the panics, see below. > panic: vm_page_alloc: page 0xfffff800f99164a0 is wired So this looks as if the mishandling of the wire_count just moved to some other pages, in this case, the freed pages got their wire_count corrupted (incremented ?). > panic: vm_page_alloc: page 0xfffff800fd9c4a60 has unexpected queue 1 But this case is more interesting, since now a field of struct vm_page other than wire_count seems to be corrupted, with the same value '1'. What was the last working kernel revision for you ? I do not know MD sparc64 code, might be, you could move forward with bisect. --w9gceUn8eOVn8+8k Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBAgAGBQJTcKdSAAoJEJDCuSvBvK1BtnUQAJaiNLKbBCHwbQIZADJsHHOP 7hFWHxvWEWuHdOwqK7sU9/MSSjH9ldPUGP0yG2ZH0v/mlcu2+Qx67R1FlZvmREe5 ZH96hNI2n2A2awvaZYoICCdqXgrGRQy4unC4hNRsFxMo0GeOuHhW5RhT7AGU5ukv 51TzsOM8ychLn1ToeqYesVa1cpQ90EAwiaaAzTiV0g0JELzImZqE/7DRheohKB95 13EzF7mHZRE7Oef1QmJGnYrOIKwuek9PnALH93oBRWl7mAz21okCmjEieqWODLGo Ao0oZQYpc/G9l1YRnd0BMvUyt+cmPb+5xgoxKuITAKFSFm4TmnmyaNUkBFWLCC/8 SuakBIn6/b8EPO0EUSn6E34Nc0i5E/LqhLipEIJQ7rlxCmvYOlgBHf7PAzu6j1tl g0S/JsCWiDPi93yXlIL4vT1ZF+6g5oKA/rUp81RYWmikqnl7QWT9j8ManL5ASdbJ 7a3H85WLkzZH+iOiTIbjjrReTCDmCdgMCo3OLZXK4I5lsF9wXChUaba5CaRp98NV fmeQBAKm7VUIqB6DM0q0XG87LzZx4N6HcwAu9BDXbsKk5bvvFNjeAcSD7vHg929q n2OY03ufqeW0DNX7qejEpwwamqR3TkxjIEvBWTElpvhnzgJrsPl38CNwVlx1bSW3 A2dJPLx1KNUMPgY/Y8df =BkHT -----END PGP SIGNATURE----- --w9gceUn8eOVn8+8k--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140512104955.GE74331>