Heads up
Otacílio
otacilio.neto at bsd.com.br
Mon Apr 25 04:55:12 UTC 2016
Em 24/04/2016 14:49, Ivan Klymenko escreveu:
> On Fri, 15 Apr 2016 11:44:43 +0300
> Ivan Klymenko <fidaj at ukr.net> wrote:
>
>> On Thu, 14 Apr 2016 16:42:33 -0600
>> Warner Losh <imp at bsdimp.com> 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 at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at 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 at 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 at 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 at 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
More information about the freebsd-current
mailing list