Date: Mon, 21 Nov 2016 22:11:45 -0500 From: Allan Jude <allanjude@freebsd.org> To: freebsd-hackers@freebsd.org Subject: Re: FreeBSD 11 sparc64 instability Message-ID: <83d26fd3-35d5-e416-a118-5f49ee6f2dc4@freebsd.org> In-Reply-To: <CAM9edeP=hVVJJuffbjJKwF1_m2ztBBfOxKZPyfzgCqfnP3zSvQ@mail.gmail.com> References: <CAM9edeP=hVVJJuffbjJKwF1_m2ztBBfOxKZPyfzgCqfnP3zSvQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --NaLlstmou7XJsF9HAjIUHrQBlDIpa4a6F Content-Type: multipart/mixed; boundary="e0B1McUSNclsPxCnhhoi0mJvpkfGeKNeX"; protected-headers="v1" From: Allan Jude <allanjude@freebsd.org> To: freebsd-hackers@freebsd.org Message-ID: <83d26fd3-35d5-e416-a118-5f49ee6f2dc4@freebsd.org> Subject: Re: FreeBSD 11 sparc64 instability References: <CAM9edeP=hVVJJuffbjJKwF1_m2ztBBfOxKZPyfzgCqfnP3zSvQ@mail.gmail.com> In-Reply-To: <CAM9edeP=hVVJJuffbjJKwF1_m2ztBBfOxKZPyfzgCqfnP3zSvQ@mail.gmail.com> --e0B1McUSNclsPxCnhhoi0mJvpkfGeKNeX Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2016-11-21 21:24, David Cross wrote: > After upgrading to FreeBSD 11 on some of my sparc64 machines (Sun Ultra= > 10), I noticed some truly disturbing behavior. >=20 > 1) ipfw won't work, at all. >=20 > kldload ipfw > ipfw add 100 allow all from any to any >=20 > ipfw -a list >=20 > you will get errors about invalid arguments. >=20 > *HOWEVER* if you use the ipfw that was from a 10.x install (10.3 in my > case), it works perfectly. ??? >=20 > 2) fsck will destroy your filesystems > clean filesystem, "fsck -t ufs /dev/foo" you will see more errors than= you > knew were possible. >=20 > *HOWEVER* if you take a version of fsck from 10.x (again, 10.3 in my ca= se) > ***AND*** libufs.so from that (LD_LIBRARY_PATH), everything is fine >=20 > I suspected this may have been because I did a 11 buildworld on a 10.3 > machine and "something leaked" with respect to headers, so I id a fresh= > buildworld, and when that too didn't fix it, I grabbed install images a= nd > used binaries and reproduced both of these errors. >=20 > What is going on here? > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.o= rg" >=20 Try running: uname -K and uname -U This will print the API versions of your kernel and userland. If they do not match, this is definitely the source of your issues. --=20 Allan Jude --e0B1McUSNclsPxCnhhoi0mJvpkfGeKNeX-- --NaLlstmou7XJsF9HAjIUHrQBlDIpa4a6F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJYM7d1AAoJEBmVNT4SmAt+ptsP/AlXyH+z6KrRE5I18QP+6RD/ TobPJNpFgeL90+2LOsb3k0YdAju78cJwb7dN1H7leCQe87drmZjRyzTWIjsVsaY+ U/Poht80ZR3ia9CuNvbvlac/b9ZzefZXDtmfxJ31hBX4MdUMyT4E8JihNH3v7l/B Tx2tt+B/AhsigIThCudZaCj1QFPU1Ex9KQtfKt+JMFIZmqr3R5hlU0lmjhS/3SBX HTIy+JTG0H4evWSXtO/xn2MhXGxsoexg6EmI+5VXukiKbE3miEJpTgWRUkQoK4hZ 4Ruo5u99Pss33RuYeKhTwI19QjuEuXe86sAxNvqJIp24YHL+06zz3M0BCebar8YQ olU1x+NJJEmykQ8T0OnVdppVEaxv0adtVS9um0TOvJ0Mmek9UIPDx9vgKDkwD2MV g31yK7XPzWJsHGuhpwwwtBmugEZcsof7umuuoFksSGYdnzgw9TE+Lkpo4oVC0ZZO RSg4WGLboC4YmvQqY9ixKt/TbOHPTXfURM0d6E92qlXk1tjlncOfpHsIYGrjBNs3 RuZDW/qPQdzt+bevXCs8Tavgiv0BgMfwKlGnwBuTT5a0zzbwU2oMZlXcz0ZLqwlP vDGyvuX7PkIuWsQd4FqE1BwYJ2k/Blv86M24s6BChDDofIeyeBiBlPZ+Xy9HJuDY +KFqFNYxtYrbb5cj3QeW =UTV3 -----END PGP SIGNATURE----- --NaLlstmou7XJsF9HAjIUHrQBlDIpa4a6F--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?83d26fd3-35d5-e416-a118-5f49ee6f2dc4>