Date: Fri, 01 Nov 2013 16:02:34 -0600 From: Ian Lepore <ian@FreeBSD.org> To: Jia-Shiun Li <jiashiun@gmail.com> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@FreeBSD.org>, Howard Su <howard0su@gmail.com> Subject: Re: sshd crash Message-ID: <1383343354.31172.102.camel@revolution.hippie.lan> In-Reply-To: <CAHNYxxNiuKP8wfTaZuL%2BBXiLcYA9eU3LBb-659ZBYr-WBSmZeQ@mail.gmail.com> References: <CAAvnz_rj43Ww6=mMfnp2u5TA2pWb20vWOqyAtuK08wgzy0dH6A@mail.gmail.com> <1383313834.31172.65.camel@revolution.hippie.lan> <CAHNYxxMMF_GJv10drYuQFO%2Bav%2BTdp8OBvJfFZObEZ=tgaBovSA@mail.gmail.com> <1383328423.31172.92.camel@revolution.hippie.lan> <CAHNYxxNiuKP8wfTaZuL%2BBXiLcYA9eU3LBb-659ZBYr-WBSmZeQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2013-11-02 at 02:40 +0800, Jia-Shiun Li wrote: > On Sat, Nov 2, 2013 at 1:53 AM, Ian Lepore <ian@freebsd.org> wrote: > > On Sat, 2013-11-02 at 01:44 +0800, Jia-Shiun Li wrote: > >> may I add: putty causes this to happen. mine 0.62. But ssh from another > >> FreeBSD host has no problem. > >> > >> I suspect it to be some issues related to memory or malloc issues > >> specific to bbb. 'tmux a -d' without existing detached sessions > >> causes tmux client to core dump. But sshd and it are both fine on rpi. > >> > >> -Jia-Shiun. > > > > This is the first I've heard of being able to ssh to an arm platform > > that doesn't have PrivSep disabled, since about July or so. I've never > > heard a report yet that anything on the client side could make a > > difference. > > > > It's definitely not a beaglebone thing, it happens on every arm board > > I've got... dreamplug, rpi, bbw, imx53, wandboard. > > > Ok let me make sure I did not mix things up. ;) > > IIRC I once saw similar issue on rpi shortly. But after another > weekly update it was gone. I did not pay too much attention on rpi, > and thought it was bbb specific. > > I did not change sshd_config, UsePrivilegeSeparation supposed > remaining on as default is. > > sshd logs attached initiating ssh to bbb from: > - PuTTY on Windows w/ key auth, > - PuTTY on Windows w/ password auth, and > - (open)ssh on rpi > > Both rpi & bbb are now running r257094: > --- 8< --- > jsli@beaglebone:~ % uname -a > FreeBSD beaglebone 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r257094: Sat > Oct 26 03:06:24 CST 2013 > jsli@4cbsd:/root/crochet-freebsd/work/obj/arm.armv6/usr/src/sys/BEAGLEBONE > arm > jsli@beaglebone:~ % > > jsli@raspberry-pi:~ % uname -a > FreeBSD raspberry-pi 11.0-CURRENT FreeBSD 11.0-CURRENT #2 r257094: Sat > Oct 26 00:16:37 CST 2013 > jsli@4cbsd:/rpi/obj/arm.armv6/usr/src/sys/RPI-B arm > jsli@raspberry-pi:~ % > --- 8< --- > > -Jia-Shiun. Okay, I can confirm that the client you use makes a difference in some way. With privsep enabled on my BBW I get the jemalloc assert on the server when connecting from an older client, including both of these: x86 - OpenSSH_5.4p1 FreeBSD-20100308, OpenSSL 0.9.8q 2 Dec 2010 arm - OpenSSH_5.4p1_hpn13v11 FreeBSD-20100308, OpenSSL 0.9.8q 2 Dec 2010 The x86 system is running 8.3 and the arm system 8.2. When using my rpi to connect to the bb, it works. Its version is: OpenSSH_6.3p1, OpenSSL 1.0.1e-freebsd 11 Feb 2013 I have no idea what all this means, but it is the first new datapoint we've had for a while. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1383343354.31172.102.camel>