Date: Thu, 03 Apr 2014 09:47:02 +0200 From: Torbjorn Granlund <tg@gmplib.org> To: Glen Barber <gjb@FreeBSD.org> Cc: doc@FreeBSD.org Subject: Re: Downplaying a serious issue Message-ID: <86k3b697nt.fsf@shell.gmplib.org> In-Reply-To: <20140403035800.GR14379@glenbarber.us> (Glen Barber's message of "Wed\, 2 Apr 2014 23\:58\:00 -0400") References: <861txffcgh.fsf@shell.gmplib.org> <alpine.BSF.2.00.1404022118570.76387@wonkity.com> <20140403035800.GR14379@glenbarber.us>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86k3b697nt.fsf>