FreeBSD 11.2-RELEASE Errata

The FreeBSD Project

FreeBSD is a registered trademark of + the FreeBSD Foundation.

Intel, Celeron, Centrino, Core, EtherExpress, i386, + i486, Itanium, Pentium, and Xeon are trademarks or registered + trademarks of Intel Corporation or its subsidiaries in the United + States and other countries.

SPARC, SPARC64, and + UltraSPARC are trademarks of SPARC International, Inc in the United + States and other countries. SPARC International, Inc owns all of the + SPARC trademarks and under licensing agreements allows the proper use + of these trademarks by its members.

Many of the designations used by + manufacturers and sellers to distinguish their products are claimed + as trademarks. Where those designations appear in this document, + and the FreeBSD Project was aware of the trademark claim, the + designations have been followed by the “™” or the + “®” symbol.

Last modified on 2018-06-21 19:10:58 EDT by gjb.

Abstract

This document lists errata items for FreeBSD 11.2-RELEASE, + containing significant information discovered after the + release or too late in the release cycle to be otherwise + included in the release documentation. This information + includes security advisories, as well as news relating to the + software or documentation that could affect its operation or + usability. An up-to-date version of this document should + always be consulted before installing this version of + FreeBSD.

This errata document for FreeBSD 11.2-RELEASE will be maintained + until the release of FreeBSD 11.3-RELEASE.

Table of Contents

1. Introduction
2. Security Advisories
3. Errata Notices
4. Open Issues
5. Late-Breaking News

1. Introduction

This errata document contains “late-breaking + news” about FreeBSD 11.2-RELEASE. Before installing this + version, it is important to consult this document to learn about + any post-release discoveries or problems that may already have + been found and fixed.

Any version of this errata document actually distributed + with the release (for example, on a CDROM distribution) will be + out of date by definition, but other copies are kept updated on + the Internet and should be consulted as the “current + errata” for this release. These other copies of the + errata are located at https://www.FreeBSD.org/releases/, plus any + sites which keep up-to-date mirrors of this location.

Source and binary snapshots of FreeBSD 11.2-STABLE also + contain up-to-date copies of this document (as of the time of + the snapshot).

For a list of all FreeBSD CERT security advisories, see https://www.FreeBSD.org/security/.

2. Security Advisories

Advisory	Date	Topic
No advisories

3. Errata Notices

Errata	Date	Topic
No erratas

4. Open Issues

FreeBSD/i386 installed on ZFS may crash during boot + when the ZFS pool mount is attempted while booting an + unmodified GENERIC kernel.
A system tunable has been added as of revision + r286584 to make the + kern.kstack_pages tunable configurable + without recompiling the kernel.
To mitigate system crashes with such configurations, + choose Escape to loader prompt in the + boot menu and enter the following lines from loader(8) + prompt, after an OK:
```
set kern.kstack_pages=4
+boot
```
Add this line to + /boot/loader.conf for the change to + persist across reboots:
```
kern.kstack_pages=4
```
[2017-07-25] FreeBSD/arm64 currently lacks + EFI real-time clock + (RTC) support, which may cause the system + to boot with the wrong time set.
As a workaround, either enable ntpdate(8) or + include ntpd_sync_on_start="YES" in + rc.conf(5).
[2017-07-25] A late issue was discovered with + FreeBSD/arm64 and "root on + ZFS" installations where the root + ZFS pool would fail to be located.
There currently is no workaround.
[2017-11-06] An issue with FreeBSD virtual machines with + vagrant was discovered that + affects the VirtualBox where the + virtual machine will not start on the initial boot invoked + with vagrant up.
The issue is due to the virtual machine + MAC being unset, as FreeBSD does not provide + a default Vagrantfile.
It has been observed, however, that a subsequent + invocation of vagrant up will allow the + virtual machine to successfully boot, allowing access via + vagrant ssh.
[2018-06-21] An issue had been discovered late in the + release cycle where removing ZFS vdevs + from a pool under certain conditions would cause a system + crash when zfsd(8) is enabled in + rc.conf(5).
At present, it is believed to be limited to removal of + a mirror vdev from a pool consisting of + multiple mirror vdevs.
See PR 228750 + for more information and updates as the issue is + investigated.

5. Late-Breaking News

No news.

All users of FreeBSD 11.2-STABLE should + subscribe to the <stable@FreeBSD.org> + mailing list.