From owner-freebsd-stable@freebsd.org  Mon Oct 17 07:19:18 2016
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id E3945C1371C
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Mon, 17 Oct 2016 07:19:18 +0000 (UTC)
 (envelope-from borjam@sarenet.es)
Received: from cu01176a.smtpx.saremail.com (cu01176a.smtpx.saremail.com
 [195.16.150.151])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id A7FCC1035
 for <freebsd-stable@freebsd.org>; Mon, 17 Oct 2016 07:19:17 +0000 (UTC)
 (envelope-from borjam@sarenet.es)
Received: from [172.16.8.36] (unknown [192.148.167.11])
 by proxypop03.sare.net (Postfix) with ESMTPA id E1BA69DCCFA;
 Mon, 17 Oct 2016 09:13:35 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.0 \(3226\))
Subject: Re: I'm upset about FreeBSD
From: Borja Marcos <borjam@sarenet.es>
In-Reply-To: <CANt7McFNq+YSGc_9+H+UuTDO=df9Q29psRMVmiYR=q53DdBcRQ@mail.gmail.com>
Date: Mon, 17 Oct 2016 09:13:35 +0200
Cc: freebsd-stable@freebsd.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <17B6FA9E-1FDA-4C56-8925-B975B33A3D8E@sarenet.es>
References: <CANt7McFNq+YSGc_9+H+UuTDO=df9Q29psRMVmiYR=q53DdBcRQ@mail.gmail.com>
To: Rostislav Krasny <rosti.bsd@gmail.com>
X-Mailer: Apple Mail (2.3226)
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Oct 2016 07:19:19 -0000


> On 17 Oct 2016, at 02:44, Rostislav Krasny <rosti.bsd@gmail.com> =
wrote:
>=20
> Hi,
>=20
> First of all I faced an old problem that I reported here a year ago:
> http://comments.gmane.org/gmane.os.freebsd.stable/96598
> Completely new USB flash drive flashed by the
> FreeBSD-11.0-RELEASE-i386-mini-memstick.img file kills every Windows
> again. If I use the Rufus util to write the img file (using DD mode)
> the Windows dies immediately after the flashing. If I use the
> Win32DiskImager (suggested by the Handbook) it doesn't reinitialize
> the USB storage and Windows dies only if I remove and put that USB
> flash drive again or boot Windows when it is connected. Nothing was
> done to fix this nasty bug for a year.

I=E2=80=99m afraid that=C2=B4s a Windows problem. And potentially a =
critical one. That barfing
upon USB insertion might point to a buffer overflow condition.

Now that people from Microsoft are reading these lists and polishing =
support for
the Microsoft hypervisor, maybe they should slap some wrists in-house =
(hard!).
*nudge*-*nudge*-*wink*-*wink*.





Borja.