Date: Thu, 03 Apr 2014 16:25:54 +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: <86txaatrpp.fsf@shell.gmplib.org> In-Reply-To: <20140403140301.GE14379@glenbarber.us> (Glen Barber's message of "Thu\, 3 Apr 2014 10\:03\:01 -0400") References: <861txffcgh.fsf@shell.gmplib.org> <alpine.BSF.2.00.1404022118570.76387@wonkity.com> <20140403035800.GR14379@glenbarber.us> <86k3b697nt.fsf@shell.gmplib.org> <20140403113605.GZ14379@glenbarber.us> <20140403140301.GE14379@glenbarber.us>
next in thread | previous in thread | raw e-mail | index | archive | help
Glen Barber <gjb@FreeBSD.org> writes: On Thu, Apr 03, 2014 at 07:36:05AM -0400, Glen Barber wrote: > On Thu, Apr 03, 2014 at 09:47:02AM +0200, Torbjorn Granlund wrote: > > Glen Barber <gjb@FreeBSD.org> writes: > > 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=20 > > It happens on: > >=20 > > 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 > >=20 >=20 > We need more specifics. >=20 =20=20 Here is the type of information we need: CPU information RAM ACPI information Drive controller information =20=20 The CPU list is above. I have used RAM from 192 MiB to 512 MiB. Your machine where you have not observed problems clearly has an amount of memory in a quite different range. Perhaps this bug is related to the amount of RAM? For all Xen runs, I have had 'apic =3D 1' in the guest config files. I don't know about KVM, I used the default. (I cannot easily retest this, since the machine in question now runs Linux+Xen instead of Linux+KVM. I have no other KVM machine.) Not sure about emulated drive controller, and how to control that. I've used file:/xen/freebsd/32/v100/disk.img,hda,w' mostly, but also tried xvda instead of hda. I have been persistent, trying at least 30 installs of 10.0-foo for several values of foo (BETA, RC, RELEASE, STABLE) and on the various systems above. It seems quite likely that this is very easy to confirm, given that every one of my attempts has been a failure. Note that the actual installation procedure apparently works. After reboot some simple repeated filesystem command, say sha1 /bin/cat sha1 /bin/cat will almost certainly yield different results. I've tested vfs.unmapped_buf_allowed=3D0 only for one machine (since I saw that only recently) and it works in that case. It is the AMD piledriver running Linux+Xen, 512 MiB RAM. 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?86txaatrpp.fsf>