Date: Sun, 5 Apr 2015 16:15:18 -0700 From: David Wolfskill <david@catwhisker.org> To: Alan Cox <alc@rice.edu> Cc: alc@FreeBSD.org, Gleb Smirnoff <glebius@FreeBSD.org>, current@freebsd.org Subject: Re: panic: Lock vm object not exclusively locked @ /usr/src/sys/vm/vm_page.c:2637 Message-ID: <20150405231518.GI1197@albert.catwhisker.org> In-Reply-To: <5521BDC4.2080103@rice.edu> References: <20150405133758.GA40261@albert.catwhisker.org> <20150405154721.GO64665@FreeBSD.org> <5521749C.4020408@rice.edu> <20150405193425.GR64665@glebius.int.ru> <5521961C.8010808@rice.edu> <20150405201744.GV64665@glebius.int.ru> <5521BDC4.2080103@rice.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--5uO961YFyoDlzFnP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 05, 2015 at 05:57:08PM -0500, Alan Cox wrote: > ... > > A> Just curious, amd64 or i386? > > > > Panics on amd64...., while building a kernel for i386, if that matters = :) > > >=20 > Maybe. I didn't trip the assertion building amd64 kernels or world.=20 > Maybe the difference is that the machine in question is still running a > world from before the last clang update. > ... After enoountering the panic (twice), I built head/amd64 (starting from stable/10/amd64); that built & booted without incident. I then went back to head/i386 (different slice), ran "make clean", then completely re-built world & kernel (in single-user mode, since it was during the transition to multi-user mode that I encountered the panic), while running: FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #1561 r281106M/281106:1100067: = Sun Apr 5 06:01:06 PDT 2015 root@g1-254.catwhisker.org:/common/S4/obj/= usr/src/sys/CANARY i386 On reboot, I was running: FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r281106M/281106:1100067: Sun= Apr 5 11:54:52 PDT 2015 root@:/common/S4/obj/usr/src/sys/CANARY i386 which still exhibited the panic. When I noted that you had committed r28118, I hand-applied that, rebooted to that last head/i386 (in single-user mode), and rebuilt the kernel (only) -- with -DNOCLEAN. The result: FreeBSD g1-254.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT #1561 r281= 106M/281106:1100067: Sun Apr 5 14:44:52 PDT 2015 root@:/common/S4/obj/= usr/src/sys/CANARY i386 survived the transition to multi-user mode successfully (which promises to make tomorrow morning a bit less stressful for me). All of this is done on the same hardware -- merely different slices of the disk. The machine has 8GB RAM, but only a bit less than half of that would have been accessible to the i386 flavor (as I am not attempting to do PAE). Peace, david --=20 David H. Wolfskill david@catwhisker.org Those who murder in the name of God or prophet are blasphemous cowards. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --5uO961YFyoDlzFnP Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJVIcIFXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RThEMDY4QTIxMjc1MDZFRDIzODYzRTc4 QTY3RjlDOERFRjQxOTNCAAoJEIpn+cje9Bk7nw8P/3x0H1Idtb+WUYQqGf3sJXv3 tkSCP+57059L9rJLjyoPF4zuCwFxSoZ3UEKlItnr2mTkijmXilWWRjT4vW7Lpv3N MEQmU+5DmrisoV34BSgOBHHLRt0HRWRkGFRHI74hKn6tqA70nfWIf/eb9ilYjsaP xNHHzTVX3p/iwzfWGbRAQEO0NRmxxQ2jL1EJIJ5Sbu2LXbylNPXLgyMB3Igi0jKK LakJjZ0J8o1srbXMEEXBM1IGwNG0+BI4Tbw1n9Ts9DStkLZ42uJsbx223ryae9Vd WD6WmWHOYqwE0B18yRSI0Q9fFyoLBtrc9owmabpzqWv+0Q9CFAhvaApjaWoM0EAX az6/1XcnhnULyQB74g+4msnIaDq1eS6o6rYhZNZ1Gqqd/FsG0/bj58P2StZuE4mX fR7T0NyBmp4GhMuUU1voEbKV3nU1tdjE2o3VLpmdK5qABvvtnhbZ/k14TvCKDTdD s18D8fOS0eZl0jlBTSnBIhkvDNMMlZoTlRubG1Sga+0bSAwscgWpaudzkdt/k3oq y6Zk2GDkh0OPx9jMhaK/rJBRUEd0sTjs34i4wC4FRUxnQpTtSPs0agt6tlm1ECwy xdKJJNbovfV0Mq9fjbsLAURHJsdj5JV6KU33rq6PbchUSnYmnsfcoamei8ex6F5H t0HN9xig0tL9VHDoarqM =jFH4 -----END PGP SIGNATURE----- --5uO961YFyoDlzFnP--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150405231518.GI1197>