[UPDATE] Re: FreeBSD 12.0-RC2 Now Available

2018-11-24 Thread Glen Barber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The freebsd-update(8) binary upgrade patches are now available for 12.0-RC2. The freebsd-update(8) utility supports binary upgrades of amd64 and i386 systems running earlier FreeBSD releases. Systems running earlier FreeBSD releases can upgrade as

FreeBSD 12.0-RC2 Now Available

2018-11-24 Thread Glen Barber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The second RC build of the 12.0-RELEASE release cycle is now available. Installation images are available for: o 12.0-RC2 amd64 GENERIC o 12.0-RC2 i386 GENERIC o 12.0-RC2 powerpc GENERIC o 12.0-RC2 powerpc64 GENERIC64 o 12.0-RC2 powerpcspe

Re: GNU binutils 2.17.50 retirement planning

2018-11-24 Thread Charlie Li
On 23/11/2018 11:23, Ed Maste wrote: > Retiring GNU as requires further investigation and effort as we have > some assembly files (for amd64 at least) which cannot be assembled by > Clang's integrated assembler. If Clang gains support for the required > functionality we'll switch to using IAS for

Re: maxswzone NOT used correctly and defaults incorrect?

2018-11-24 Thread John-Mark Gurney
Konstantin Belousov wrote this message on Sat, Nov 24, 2018 at 12:40 +0200: > On Sat, Nov 24, 2018 at 01:04:29AM -0800, John-Mark Gurney wrote: > > I have an BeagleBoard Black. I'm running a recent snapshot: > > FreeBSD generic 13.0-CURRENT FreeBSD 13.0-CURRENT r340239 GENERIC arm > > > > aka:

Re: maxswzone NOT used correctly and defaults incorrect?

2018-11-24 Thread Mark Millard
On 2018-Nov-24, at 02:40, Konstantin Belousov wrote: > On Sat, Nov 24, 2018 at 01:04:29AM -0800, John-Mark Gurney wrote: >> . . . > OOM is guided by the pagedaemon progress, not by the swap amount left. It would help if the "was killed: out of swap space" messages did not incorrectly point

Re: maxswzone NOT used correctly and defaults incorrect?

2018-11-24 Thread Tijl Coosemans
On Sat, 24 Nov 2018 01:04:29 -0800 John-Mark Gurney wrote: > I have an BeagleBoard Black. I'm running a recent snapshot: > FreeBSD generic 13.0-CURRENT FreeBSD 13.0-CURRENT r340239 GENERIC arm > > aka: > FreeBSD-13.0-CURRENT-arm-armv7-BEAGLEBONE-20181107-r340239.img.xz > > It has 512MB of

Re: SCSI and dmesg

2018-11-24 Thread Yuri Pankov
Warner Losh wrote: > Greetings > > a few weeks ago I pointed people to the nycbug dmesg service. I said I was > looking at data to drive SCSI retirement. I've gatherd some preliminary > data, which I've uploaded to > https://github.com/bsdimp/device-data/blob/master/cam.md along with some >

Re: Kernel Panic - Sublime Text - 12.0-PRERELEASE r340650M

2018-11-24 Thread James Wright
Updated to r340868 and the issue has been resolved, thank you for your time! James On 24/11/2018 09:53, Tijl Coosemans wrote: On Sat, 24 Nov 2018 02:05:51 + James Wright wrote: When trying to run sublime text via the linuxulator my system panics and reboots. Unfortunately I do not have

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

2018-11-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 --- Comment #16 from Matías Pizarro --- Hi all, FYI, I had the same issue with 13-CURRENT but it now works fine in today';s stable/12 | 12-PRERELEASE which I understand should be the same as 12-RC2. Thanks for your work on this, All the

Re: maxswzone NOT used correctly and defaults incorrect?

2018-11-24 Thread Konstantin Belousov
On Sat, Nov 24, 2018 at 01:04:29AM -0800, John-Mark Gurney wrote: > I have an BeagleBoard Black. I'm running a recent snapshot: > FreeBSD generic 13.0-CURRENT FreeBSD 13.0-CURRENT r340239 GENERIC arm > > aka: > FreeBSD-13.0-CURRENT-arm-armv7-BEAGLEBONE-20181107-r340239.img.xz > > It has 512MB

Re: Kernel Panic - Sublime Text - 12.0-PRERELEASE r340650M

2018-11-24 Thread Tijl Coosemans
On Sat, 24 Nov 2018 02:05:51 + James Wright wrote: > When trying to run sublime text via the linuxulator my system panics > and reboots. Unfortunately I do not have much extra info as it crashes > immediately and seems to corrupt the UFS filesystem in the process > (which has to be fixed

maxswzone NOT used correctly and defaults incorrect?

2018-11-24 Thread John-Mark Gurney
I have an BeagleBoard Black. I'm running a recent snapshot: FreeBSD generic 13.0-CURRENT FreeBSD 13.0-CURRENT r340239 GENERIC arm aka: FreeBSD-13.0-CURRENT-arm-armv7-BEAGLEBONE-20181107-r340239.img.xz It has 512MB of memory on board. I created a 4GB swap file. According to loader(8), this