Date: Tue, 5 Nov 2013 09:02:22 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: Gleb Smirnoff <glebius@FreeBSD.org> Cc: Boris Bobrov <breton@cynicmansion.ru>, Glen Barber <gjb@freebsd.org>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>, Maciej Milewski <milu@dat.pl> Subject: Re: 10.0-BETA1 i386 on VirtualBox Message-ID: <20131105070222.GW59496@kib.kiev.ua> In-Reply-To: <20131104165341.GK52889@glebius.int.ru> References: <526939BF.4030306@dat.pl> <201311021106.17222.breton@cynicmansion.ru> <52761D4C.8030404@dat.pl> <201311031629.20378.breton@cynicmansion.ru> <20131103134601.GN52889@glebius.int.ru> <20131103144131.GG59496@kib.kiev.ua> <52778541.3090803@dat.pl> <20131104163825.GS59496@kib.kiev.ua> <20131104165341.GK52889@glebius.int.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--mN1JkpzzjA4mCWyC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 04, 2013 at 08:53:41PM +0400, Gleb Smirnoff wrote: > On Mon, Nov 04, 2013 at 06:38:25PM +0200, Konstantin Belousov wrote: > K> Also please show me the CPU features banner from the boot in the VB, > K> like this: >=20 > I have already collected them all. See attaches. >=20 > Legend: >=20 > dmesg.bb pwd_mkdb crashes during install > dmesg.milu.png pwd_mkdb crashes during install > dmesg.think installation succeeds, but world build crashes instantly > dmesg.ru all works > dmesg.morannon all works First, all reported instances have ata attachment for the ada0, except of milu (possibly). So this means that kernel does transient remapping, and very different code path is executed comparing with what I thought initially. The path is simpler than the pure unmapped i/o. Second, I use QEMU with the ata0 attachment for the disks regularly, and I do not have an issue. I also did not see a report from the real h/w. Third point is that all reports are i386. Is there anybody with amd64, vbox, ata and the same corruption hiddent by disabling unmapped i/o ? In what way the non-working images were installed ? Is it possible to produce the problematic installs by doing it one way, and non-problematic by another ? --mN1JkpzzjA4mCWyC Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBAgAGBQJSeJf9AAoJEJDCuSvBvK1BAs0P/3BfgaJzFcNavz22WbL1kk16 UlpH3KFeLiJ64Laqq6iUS0ohsiqFC4F/WXSi+1yaGajpYYhQo7GORLjzE+4GLF6y zfOLZYBJJHRshioBK+AYVcvXkVfJ4CAOzEG74FDjEbHuW5N95iBqvj21iDnqa6jy 8mNBkJtbHKBGSt2GPH5YI5ABl3fxaeXBWmcnYeEwGJ47gCxUIz7dXZ8wCI3WJufD wR2QBIHmqsjXvfR85Rv3KOU0Dp9IkJwaVvHUcMNt239OxTLeEYjaHBgpsm1FMlJ+ 9vyhDCjeIiDMzRqwpjIKpm9NTA5gLEOL4/EvPdxBe1QSFoBQWe7+gSvYjeagYHn+ QcMRxKDTrzyfwYE9oRO+83/UscjNFt1Iw9TL9Q4T1puJ5+xguR/z4r4hQCWYC8vY HWQ7kf0lN5lHlTtXBDb7PuLkaprDYsiLQrf7t6aym1FoyMQR4btCeXwUcj+JxdzI CUJX24npnU0InxzRltixPAwg2T0J0rZF1HL6k1wp/9xqO2sPUyy74RIyIR0wYWyS z3wYO9+o30jfXB6IHp0YqotPpkXsBz5r+HNKia7DHXXGjcYIu3TSajsCABbbA0NN jtSWpd28yUzcYQMigKB0noghu2zkLiIHAdeudZjzrTaT/uIA3L9joskxL78NUQWw RmdjbEZQuNL9NJ0IvCXI =hRjx -----END PGP SIGNATURE----- --mN1JkpzzjA4mCWyC--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131105070222.GW59496>