Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 22 Aug 2017 06:38:36 -0700
From:      David Wolfskill <david@catwhisker.org>
To:        Konstantin Belousov <kostikbel@gmail.com>
Cc:        current@freebsd.org
Subject:   Re: SIGSEGV in /bin/sh after r322740 -> r322776 update
Message-ID:  <20170822133836.GQ1130@albert.catwhisker.org>
In-Reply-To: <20170822131958.GE1700@kib.kiev.ua>
References:  <20170822114627.GC1130@albert.catwhisker.org> <20170822115923.GC1700@kib.kiev.ua> <20170822122836.GH1130@albert.catwhisker.org> <20170822123449.GD1700@kib.kiev.ua> <20170822124617.GN1130@albert.catwhisker.org> <20170822131958.GE1700@kib.kiev.ua>

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

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

On Tue, Aug 22, 2017 at 04:19:58PM +0300, Konstantin Belousov wrote:
> ...
> > > Ok, can you rebuild kernel and libc from scratch ?  I.e. remove your
> > > object directories.
> >=20
> > I think I'll need a working /bin/sh to do that.  As noted, I could
> > try the stable/11 /bin/sh; on the other hand, if it's dying in a
> > library, that's not likely to help a whole lot. :-}
> I highly suspect that this is not /bin/sh at all.  Backtrace strongly
> suggests that the malloc() has issues, but again I suspect that the
> reason is not an issue in malloc, but its use of TLS.

I think I hope that this use of "TLS" is not the one associated with
(say) SSL....  :-}

> The amd64 changes were to the TLS base register handling.  So you might
> try to boot previous kernel.  If this works out without replacing libc
> then it is definitely TLS, but I still do not know what is wrong.
> ....

OK; we have a bit of progress, then:
* When I tried to rename the kernel directories in /boot, I got more
  segfaults.  So I figured I'd use the boot menu to select kernel.old, and
  just tried "sudo shutdown -r now" -- and got a segfault.  "sudo reboot"
  did, as well.  So did "sudo kill 1".  On a whim, I tried "sudo halt";
  that actually worked.

* After the (successful) reboot from kernel.old, I was able to rename
  kernel directories without issue.  This may be useflu evidence.

* Flushed with that success, I have started a fresh clean build of
  r322776.  (I had managed to clear /usr/obj prior to the reboot.)

* I should be able to provide updated status within about 30 minutes.

Thanks again for all your help!

Peace,
david
--=20
David H. Wolfskill				david@catwhisker.org
If we wish to eliminate sources of Fake News, start at the top: D. Trump.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.

--1R3djOICCIfo/gUr
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQF8BAEBCgBmBQJZnDPcXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix
NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4XnksH/3/If/UYHL4YlTcZxDqUESgk
glp6hVwnX41ByWNA/80h206R2UuWaY8T/upqi+doOi/w0WRWH2pAit/T/i1dXCQi
8Alt2WIWNwtFD57Nh70JZSBgW/qac+D/5U7AHCdCjOdrHJNJErxQy8BTxM5gX0C7
3N7UD61RtuQrLYY0E8v8sA72Dj06ld7mqerw9Es2t/0QoBOsdONV2pxm/ixKYnMs
7El6yy7GaDtRYj5GjE9HTZHznE45MBl+qrsLRReA+aKnZvT30djgZ1RZf+JFMf5B
y0w8L4VkpiVh4bVahHGiSd1WH6lJkpnQPoRrya6LVO4ilklGcLZVBoNhrUS2IyY=
=e0J4
-----END PGP SIGNATURE-----

--1R3djOICCIfo/gUr--



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