From owner-freebsd-stable@freebsd.org Tue Oct 18 11:11:38 2016 Return-Path: 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 4D00BC16715 for ; Tue, 18 Oct 2016 11:11:38 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C0632BF6 for ; Tue, 18 Oct 2016 11:11:36 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id u9IAvTu1093814; Tue, 18 Oct 2016 21:57:30 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Tue, 18 Oct 2016 21:57:29 +1100 (EST) From: Ian Smith To: Yamagi Burmeister cc: freebsd-stable@freebsd.org Subject: Re: I'm upset about FreeBSD In-Reply-To: <20161017185215.97528d6cf6377058e4760785@yamagi.org> Message-ID: <20161018212750.J6806@sola.nimnet.asn.au> References: <20161017185215.97528d6cf6377058e4760785@yamagi.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2016 11:11:38 -0000 On Mon, 17 Oct 2016 18:52:15 +0200, Yamagi Burmeister wrote: > On Mon, 17 Oct 2016 03:44:14 +0300 > Rostislav Krasny wrote: > > > 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. > > As was already said in the other answers this is a bug in Windows. > Particulary in the partition parser. partmgr.sys (running in kernel > mode) crashes while parsing the FreeBSD installation images GPT > setup. This may be a variant of the bug known as "Kindle is crashing > Win 10": > > http://answers.microsoft.com/en-us/windows/forum/windows_10-performance/plugging-in-kindle-is-crashing-windows-10-after/5db0d867-0822-4512-919e-3d7786353f95?page=1 It's interesting that people primarily oriented to Windows tend to say 'X crashes my Windows' rather than 'my Windows crashes when X happens', so your far more cluey approach is refreshing in this regard .. > That bug was patched on september 13 and I'm unable to reproduce the > crash on a fully patched Win 10 VM. But there's no patch for Win 7, > even with all patches applied my Win 7 VM is still crashing as soon > as the FreeBSD installation image is connected. Amazing; what we'd call a kernel panic due to merely inserting a device. > I did some debugging and I'm pretty sure that the problem is not the > pmbr used for classic BIOS boot but the GPT itself. But my knowledge > of GPT and especially Windows internals is limit. So maybe someone > with more insight can look into this. If FreeBSD GPT images (and Kindle readers) can trigger this, so could a theoretically unlimited combination of data on block 2 of USB media; modifying FreeBSD to fix a Windows bug should be out of the question. > Or even better: Complain to Microsoft. Even if the GPT is invalid it > should crash the kernel. Well, exactly so, given s/should/should not/ .. and they'll have at least three images to test against: 10.3 (i386 only) and 11.0 (amd64 and i386) apart from the Kindles; should be a clue or two in there .. cheers, Ian