[The ports had recently been updated to -r417989 and a "portupgrade -Wa" had 
run to completion before the following FreeBSD 11.0 -r302180 to -r302331 
upgrade was started.]

On Mac OS X 10.11.5 using FreeBSD 11.0 -r302331 under VirtualBox 5.0.24 r108355 
after upgrading from FreeBSD 11.0 -r302180: The upgrade to -r302331 required me 
to rebuild emulators/virtualbox-ose-additions in order to get lumina to work 
again. Without the rebuild lumina just made a black screen and kept the cores 
100% busy. Even a ACPI Shutdown selection did not stop it: I had to use more 
drastic means.

I did not rebuild lumina, just emulators/virtualbox-ose-additions . (As 
configured I manually type startx to get lumina. So I easily rebooted and 
worked form the console to rebuild emulators/virtualbox-ose-additions and then 
reboot again to try lumina.)


FYI, from after the 11.0 upgrade:

> # uname -apKU
> FreeBSD FreeBSDx64 11.0-ALPHA6 FreeBSD 11.0-ALPHA6 #5 r302331M: Sun Jul  3 
> 14:41:34 PDT 2016     
> markmi@FreeBSDx64:/usr/obj/clang/amd64.amd64/usr/src/sys/GENERIC-NODEBUG  
> amd64 amd64 1100120 1100120

But the "1100120 1100120" was the same before when it was at -r302180M.


I do remember at least one request/suggestion of a __FreeBSD_version bump that 
was never taken:

> svn commit: r302283 - head/sys/net80211
> 
> Bryan Drewery bdrewery at FreeBSD.org 
> Wed Jun 29 17:36:29 UTC 2016
> . . .
> On 6/29/16 10:25 AM, Andriy Voskoboinyk wrote:
> >   NOTE: Since this change breaks KBI, all wireless drivers need to be
> >   recompiled.
> 
> __FreeBSD_version should probably be bumped in sys/sys/param.h
> 
> -- 
> Regards,
> Bryan Drewery

(I do not claim that -r302283 was involved in my issue, just that there was 
apparently at least one reason to bump the number up.)

===
Mark Millard
markmi at dsl-only.net

_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to