Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 15 Sep 2013 10:23:08 -0400
From:      Paul Mather <pmather@vt.edu>
To:        Diane Bruce <db@db.net>
Cc:        freebsd-arm <freebsd-arm@freebsd.org>
Subject:   Re: sshd isnt working?
Message-ID:  <92A05C0F-B921-4998-8AF5-E0B4994E37D5@g.mail.vt.edu>
In-Reply-To: <20130915120005.GA16617@night.db.net>
References:  <CAHjFwoCK2qdgeyyQLJ6FEZxJFRs8gELP37LxoDvjOUsfv6PuBQ@mail.gmail.com> <20130915120005.GA16617@night.db.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 15, 2013, at 8:00 AM, Diane Bruce wrote:

> On Sun, Sep 15, 2013 at 01:39:42PM +0800, Su Kang Yin wrote:
>> Hi,
>>=20
>> sshd throwing signal 6 on server side
>>=20
>> messages log:
>> Sep 15 05:32:31 beaglebone kernel: pid 896 (sshd), uid 22: exited on =
signal 6
>>=20
>> On FreeBSD version:
>> FreeBSD beaglebone 10.0-ALPHA1 FreeBSD 10.0-ALPHA1 #0 r255586: Sun =
Sep
>> 15 12:53:16 HKT 2013
>> root@freebsd:/usr/home/cantona/crochet-freebsd/work/obj/arm.a
>> rmv6/usr/src.head/sys/BEAGLEBONE  arm
>>=20
> ...
>>=20
>> Anyone have an idea about this problem?
>=20
> Yes.
>=20
> =
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D199241+0+archive/2013/freeb=
sd-arm/20130728.freebsd-arm
>=20
> I see you rediscovered this as well.
>=20
> I did poke at it a bit more and found
>=20
> =
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D47500+0+archive/2013/freebs=
d-arm/20130825.freebsd-arm
>=20
> zbb and Matthias Meyser reported another weird jemalloc error which is
> in PR 182060
>=20
> http://www.freebsd.org/cgi/query-pr.cgi?pr=3D182060&cat=3D
>=20
> I believe this is the exact same problem manifesting itself elsewhere.
>=20
> I suspect we have a locking problem in the mutex code used on armv6.
>=20
>=20
>> Thanks,
>> Yin
>=20
> - Diane
> --=20
> - db@FreeBSD.org db@db.net http://www.db.net/~db


For me, I've only encountered this problem when connecting from certain =
clients---Mac OS X 10.7 and 10.8 so far.  I can SSH to my Raspberry Pi =
and BeagleBone Black just fine from another RELENG_9 FreeBSD system, and =
from a Debian Wheezy system.  The failure mode for those that don't work =
is the same as reported above---a signal 6 on the server side.  Also, =
this hasn't always been the case, but I can't recall a revision number =
when the problem began.

Cheers,

Paul.





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?92A05C0F-B921-4998-8AF5-E0B4994E37D5>