From owner-freebsd-current@freebsd.org  Sat Jun 16 02:31:50 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6B31D10041B8
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Sat, 16 Jun 2018 02:31:50 +0000 (UTC)
 (envelope-from linimon@lonesome.com)
Received: from mail.soaustin.net (mail.soaustin.net [18.222.6.11])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "mail.soaustin.net",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 1DF276EDDB;
 Sat, 16 Jun 2018 02:31:49 +0000 (UTC)
 (envelope-from linimon@lonesome.com)
Received: from lonesome.com (unknown [18.188.142.31])
 by mail.soaustin.net (Postfix) with ESMTPSA id 4CA0924933;
 Sat, 16 Jun 2018 02:31:49 +0000 (UTC)
Date: Sat, 16 Jun 2018 02:31:48 +0000
From: Mark Linimon <linimon@lonesome.com>
To: =?iso-8859-1?Q?Mika=EBl?= Urankar <mikael.urankar@gmail.com>
Cc: Kurt Jaeger <lists@opsec.eu>, markj@freebsd.org,
 FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: swapping is completely broken in -CURRENT r334649?
Message-ID: <20180616023147.GB17758@lonesome.com>
References: <d3ee2b8f-bdbe-ce25-f496-6267f9bb0212@FreeBSD.org>
 <20180605181716.73b8ea91@ernst.home>
 <2925b27f-43cf-8813-eaa7-4f3d12bef8f0@FreeBSD.org>
 <20180605214808.GA94301@pesky>
 <20180615051025.GA79327@ns.kevlo.org>
 <20180615084022.GA32922@pesky.lan>
 <20180615084808.GF4028@home.opsec.eu>
 <20180615090358.GB32922@pesky.lan>
 <20180615090734.GG4028@home.opsec.eu>
 <CAJwjRmS8XJPkdz1BQjDOM-Qqh-9_uaXphvCAkcBqzLQ=Zpc3DQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAJwjRmS8XJPkdz1BQjDOM-Qqh-9_uaXphvCAkcBqzLQ=Zpc3DQ@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.26
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: Sat, 16 Jun 2018 02:31:50 -0000

On Fri, Jun 15, 2018 at 11:14:40AM +0200, Mikaël Urankar wrote:
> Last time I tried (2 weeks ago) qemu-ppc64-static was broken, not sure the
> situation has evolved since that.

I've been told by more than one person that it works, but the 2? 3? times
I've tried it it just hung.

I have real hardware so in general it doesn't make a difference to me,
but I'd like to know one way or the other.

mcl