From owner-freebsd-current@freebsd.org Mon Apr 25 04:55:12 2016 Return-Path: Delivered-To: freebsd-current@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 694A4B1BD70 for ; Mon, 25 Apr 2016 04:55:12 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 382D01F31 for ; Mon, 25 Apr 2016 04:55:12 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: by mail-pf0-x236.google.com with SMTP id c189so17100443pfb.3 for ; Sun, 24 Apr 2016 21:55:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=ZB8ypZCT5RSLsnpA0jxtP63DlklMCSKOuJCmNgRmfpg=; b=MBpDxonwEBUTPIliusHMLyCX6JjNd8M2VPzNcZbVBCCa6qBxBhIegv5Mj1Xmc4ydUA gYvFr5/A3mzJHh2wbzKCkMfBYx/3gUdeCHgCfzVKpSnaaEW84LfWg5psP6tWhchkiuzE 26u5FfGPH4cDsrFZ+ZcF1T2pbctEUaJtrjul0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=ZB8ypZCT5RSLsnpA0jxtP63DlklMCSKOuJCmNgRmfpg=; b=ChoxsBSesQUm+9qHG2a5AhgzKqczk2DSwa3HL12RSy5LW23svVUkmcFWL0mZKkretM Mfait3JsPk4Pk2DHNav3hQ6AZKQd6+uWyZTDX4GoTneOVdyFgOXijmj2yRIm2BhPULHB oqkYcIz9jLAlx+qEtm83Q99t9konZuTBCRvW2lLvmmxrvBxhFHJhrkWjrNBtM5WOJraY /DONWSGYWvMB8jek+XhwoaYS/Awm11ipzKBACMcdv6PAfBw7MDSdziai1O73hN2YyoUF TGBm2xCm2SvEE6kF56zdkgzE+g+UZRfhA9K+2PHG7jb68dkm+SeD6z84lOfS++q/aPM5 6zMA== X-Gm-Message-State: AOPr4FWrspd66geKUna61zmqQzqBCTn29gZm3vWTswUnkHQgC6Mpu7xSlnryFQz//70xsg== X-Received: by 10.98.101.198 with SMTP id z189mr834732pfb.76.1461560111589; Sun, 24 Apr 2016 21:55:11 -0700 (PDT) Received: from [192.168.0.18] ([187.60.94.34]) by smtp.googlemail.com with ESMTPSA id 28sm20389158pfs.1.2016.04.24.21.55.09 for (version=TLSv1/SSLv3 cipher=OTHER); Sun, 24 Apr 2016 21:55:10 -0700 (PDT) Subject: Re: Heads up To: freebsd-current@freebsd.org References: <20160415114443.660453cb@nonamehost.local> <20160424204934.46eebae8@nonamehost.local> From: =?UTF-8?B?T3RhY8OtbGlv?= Message-ID: <571DA324.20603@bsd.com.br> Date: Mon, 25 Apr 2016 01:55:00 -0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <20160424204934.46eebae8@nonamehost.local> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2016 04:55:12 -0000 Em 24/04/2016 14:49, Ivan Klymenko escreveu: > On Fri, 15 Apr 2016 11:44:43 +0300 > Ivan Klymenko wrote: > >> On Thu, 14 Apr 2016 16:42:33 -0600 >> Warner Losh wrote: >> >>> The CAM I/O scheduler has been committed to current. This work is >>> described in >>> https://people.freebsd.org/~imp/bsdcan2015/iosched-v3.pdf though the >>> default scheduler doesn't change the default (old) behavior. >>> >>> One possible issue, however, is that it also enables NCQ Trims on >>> ada SSDs. There are a few rogue drives that claim support for this >>> feature, but actually implement data corrupt instead of queued >>> trims. The list of known rogues is believed to be complete, but >>> some caution is in order. >>> >>> Warner >> Hi. >> Thanks for you work. >> But i have problem with VirtualBox if i use the kernel with option >> CAM_NETFLIX_IOSCHED >> http://imgur.com/JpcfW1h > This problem is not over. > After the update on other hardware from r296979 to r298512 (!!! without > option CAM_NETFLIX_IOSCHED !!!) due to errors in recording the virtual > machine to a virtual disk I lost completely virtual machine with > permanent damage to the integrity of the file system in the inside of > the virtual machine. > > This is a serious bug! > > Who cares not to fall into the same situation - is testing yourself > and needed more testers. > Because there is a suspicion that the problem is also relevant for > bhyve VM. > With me on this no more neither the strength nor the desire nor > time. > > Thanks. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Dears. I have updated my FreeBSD 11 guest on Virtualbox to rev 298522 FreeBSD nostromo 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r298522: Sun Apr 24 07:25:34 BRT 2016 ota@nostromo:/usr/obj/usr/src/sys/NOSTROMO amd64 The virtualbox is 5.0.18 r10667 running on Windows 10. The FreeBSD guest is running virtualbox additions virtualbox-ose-additions-4.3.38 VirtualBox additions for FreeBSD guests I'm using this machine to build FreeBSD images to Beaglebone Black using crouchet and cross compile packages using poudriere. I have finished a full build of FreeBSD 11 r298522 to Beaglebone and actually I'm upgrading my poudriere jail to 298522. Until now all runs fine. This is my conf of kernels: [ota@nostromo /usr/src/sys]$ diff amd64/conf/GENERIC amd64/conf/NOSTROMO 85,92c85,92 < options DDB # Support DDB. < options GDB # Support remote GDB. < options DEADLKRES # Enable the deadlock resolver < options INVARIANTS # Enable calls of extra sanity checking < options INVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS < options WITNESS # Enable checks to detect deadlocks and cycles < options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed < options MALLOC_DEBUG_MAXZONES=8 # Separate malloc(9) zones --- > #options DDB # Support DDB. > #options GDB # Support remote GDB. > #options DEADLKRES # Enable the deadlock resolver > #options INVARIANTS # Enable calls of extra sanity checking > #options INVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS > #options WITNESS # Enable checks to detect deadlocks and cycles > #options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed > #options MALLOC_DEBUG_MAXZONES=8 # Separate malloc(9) zones [ota@nostromo /usr/src/sys]$ diff arm/conf/BEAGLEBONE arm/conf/BEAGLEBONE-DEBUG 153a154,156 > > #options IEEE80211_AMPDU_AGE # Add a A-MPDU RX aging > #options IEEE80211_DEBUG Until now both machines are running without problems and with full stress. The Beaglebone is compiling kernel and the amd64 have compiled freebsd to beaglebone. If exists some tests that I can made to help please let me know. []'s -Otacílio