From owner-freebsd-doc@FreeBSD.ORG  Thu Apr  3 07:47:06 2014
Return-Path: <owner-freebsd-doc@FreeBSD.ORG>
Delivered-To: doc@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 22EC99EF;
 Thu,  3 Apr 2014 07:47:06 +0000 (UTC)
Received: from shell.gmplib.org (gmplib-02.nada.kth.se [130.237.222.242])
 by mx1.freebsd.org (Postfix) with ESMTP id DB1F476E;
 Thu,  3 Apr 2014 07:47:05 +0000 (UTC)
Received: by shell.gmplib.org (Postfix, from userid 1001)
 id D757018D7A; Thu,  3 Apr 2014 09:47:02 +0200 (CEST)
To: Glen Barber <gjb@FreeBSD.org>
Subject: Re: Downplaying a serious issue
References: <861txffcgh.fsf@shell.gmplib.org>
 <alpine.BSF.2.00.1404022118570.76387@wonkity.com>
 <20140403035800.GR14379@glenbarber.us>
From: Torbjorn Granlund <tg@gmplib.org>
Sender: tg@gmplib.org
Date: Thu, 03 Apr 2014 09:47:02 +0200
In-Reply-To: <20140403035800.GR14379@glenbarber.us> (Glen Barber's message of
 "Wed\, 2 Apr 2014 23\:58\:00 -0400")
Message-ID: <86k3b697nt.fsf@shell.gmplib.org>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: doc@FreeBSD.org
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Documentation project <freebsd-doc.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>,
 <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/>
List-Post: <mailto:freebsd-doc@freebsd.org>
List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>,
 <mailto:freebsd-doc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 07:47:06 -0000

Glen Barber <gjb@FreeBSD.org> writes:

  It is not a doc problem.
=20=20
  The issue is specific to certain hardware configurations, and unless
  anyone has made any breakthroughs that I am unaware of, the cause is
  still unknown.
=20=20
It happens on:

AMD piledriver running Linux+KVM
AMD piledriver running Linux+Xen
Intel Nehalem running NetBSD+Xen
Intel Sandybridge running NetBSD+Xen
Intel Haswell running NetBSD+Xen
AMD K10 Barcelona running NetBSD+Xen
AMD Bulldozer running NetBSD+Xen

I've seen the laughable claim that this is a "bug in Virtualbox", and now
the major downplay at http://www.freebsd.org/releases/10.0R/errata.html,
where this is a minor hardware specific problem.

I have not found one piece of PC hardware where it does not happen under
virtualisation.  Please let me know some configuration where FreeBSD/i386
works under a type 1 virtualiser?  Perhaps Bhyve is FreeBSD-compatible?

  Not "weird", but it is specific to certain hardware configurations.
=20=20
  > >It is not specific to virtualbox.
=20=20
  This is the first I am hearing of this problem on non-VirtualBox
  hypervisors.
=20=20
I've mentioned it on FreeBSD lists before.  But after having lost many
hours on reporting the ssh panic for FreeBSD/amd64 and FreeBSD/i386
(amd64/183397), I didn't file a PR for this, also after I saw this was
known and downplayed by a FreeBSD dev.


Torbj=C3=B6rn
Please encrypt, key id 0xC8601622