From owner-freebsd-current@freebsd.org  Wed Aug 19 20:09:54 2015
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id B195A9BE8EE
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Wed, 19 Aug 2015 20:09:54 +0000 (UTC)
 (envelope-from feld@FreeBSD.org)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com
 [66.111.4.27])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 8A7C2221
 for <freebsd-current@freebsd.org>; Wed, 19 Aug 2015 20:09:54 +0000 (UTC)
 (envelope-from feld@FreeBSD.org)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46])
 by mailout.nyi.internal (Postfix) with ESMTP id 5099C202C5
 for <freebsd-current@freebsd.org>; Wed, 19 Aug 2015 16:09:53 -0400 (EDT)
Received: from web3 ([10.202.2.213])
 by compute6.internal (MEProxy); Wed, 19 Aug 2015 16:09:53 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=content-transfer-encoding:content-type
 :date:from:message-id:mime-version:subject:to:x-sasl-enc
 :x-sasl-enc; s=smtpout; bh=R6KL2f47kYlvhipab9D5axpmjOM=; b=TFQIX
 yLWmHnWcqGC6B4lsQ2HWTF0HGBeKTfDjI5rFbsF27bkX0Qim3AEHvZc8UTsI4Llh
 DasSCn7C+SjcFC23f+/pZBaAzv+LMaNzOFy8hjd0REDdeGRpBY/ffBp5LWyvDu6z
 ef3yEZyDgpsAjY29QvyYdVUvWtjYBZsgpV1ULY=
Received: by web3.nyi.internal (Postfix, from userid 99)
 id 2746410C780; Wed, 19 Aug 2015 16:09:53 -0400 (EDT)
Message-Id: <1440014993.2793501.360634953.2FF3B076@webmail.messagingengine.com>
X-Sasl-Enc: 7IU6BljTBy0CPM9jWbTn9tMMMXHmqqQD3sPTaplXLK5x 1440014993
From: Mark Felder <feld@FreeBSD.org>
To: freebsd-current@freebsd.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-4fee8ba5
Subject: pkg with an ssh repo crashes CURRENT
Date: Wed, 19 Aug 2015 15:09:53 -0500
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Aug 2015 20:09:54 -0000

Hello,

I found a reproducible way to crash CURRENT. I've done so on a Raspberry
Pi 2 running r286596 and an my x86_64 firewall running r286285.

Setup is simple. Enable a functional pkg repo that uses ssh like so:

myrepo: {
url:
"ssh://feld@172.16.1.122/usr/local/poudriere/data/packages/${ABI}/",
enabled: no
}

Now just do a pkg upgrade or install. So far the crashes have always
happened updating pkg itself; I haven't gotten past that part.

My firewall has a watchdog so it auto-reboots and I don't have console
or video on my Rpi2 at the moment so I can't tell where it's crashing
at. I haven't seen any dumps or core files. I got a glimpse of the crash
on the firewall once and I think I saw it spew out some LORs, but I'm
not certain. I'll try to get more data posted soon, but if someone is
feeling adventurous they can probably reproduce this in a matter of
minutes.