FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=main 2026-03-21T16:10:25Z 2026-03-21T16:10:25Z Colin Percival cperciva@FreeBSD.org 2026-03-21T16:06:37Z urn:sha1:118699732de1ec99b06d5d73ee61b1b74842c1de MFC after: 3 days Sponsored by: Amazon 2026-03-14T16:33:32Z Colin Percival cperciva@FreeBSD.org 2026-03-14T16:30:13Z urn:sha1:251907ca480eff7f6177f52959b71a6cfce45579 We're avoiding *unicode*, not avoiding *ascii*. Reported by: marck Fixes: 277830b4d3ae ("EC2: Don't use unicode in boot loader") MFC after: 3 days 2026-03-13T21:25:46Z Colin Percival cperciva@FreeBSD.org 2026-03-13T20:45:05Z urn:sha1:277830b4d3ae9999c80bf915b5491850e91c6516 The boot loader menu is disabled by default in EC2, but if it is ever turned on, the default (unicode) output breaks EC2's web interface to the serial console. Set loader_menu_frame="ascii" instead. MFC after: 3 days Sponsored by: Amazon 2026-01-29T17:03:20Z Ed Maste emaste@FreeBSD.org 2025-12-11T17:16:53Z urn:sha1:54e006369c9aab4f3a22f026eb6924c0f9cafda8 We always use NO_ROOT for release artifact builds, so remove the alternate code paths. For the first step we set NO_ROOT unconditionally in cases that invoke submakes, and turn NO_ROOT being unset into an error in lover-level targets so that we can catch potential out-of-tree build scripts (or missed in-tree cases) that expect to run not-NO_ROOT builds. The second step will be to remove those entirely. Reviewed by: cperciva Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D54179 2025-09-16T20:50:33Z Mark Johnston markj@FreeBSD.org 2025-09-16T16:53:35Z urn:sha1:8027de008d9f3c5cd5509d586f14846abd0f3db2 - Avoid chrooting to uninstall pkg, as it will not be installed in the first place when in non-root mode. - Add metalog entries. Reviewed by: cperciva MFC after: 3 days Sponsored by: The FreeBSD Foundation Sponsored by: Klara, Inc. Differential Revision: https://reviews.freebsd.org/D52452 2025-09-11T13:05:31Z Mark Johnston markj@FreeBSD.org 2025-09-11T13:05:31Z urn:sha1:1d6b6ea2d0e617d29681da3cf121abec309d272f Some services, such as growfs, only run upon the first boot of an image. The first boot is indicated by the presence of the file /firstboot, which is unlinked after boot. Individual cloudware types shouldn't be responsible for creating it. Do so in a centralized place. Aside from simplifying things, this ensures that we create a metalog entry for the firstboot file. Reviewed by: cperciva, emaste MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Sponsored by: Klara, Inc. Differential Revision: https://reviews.freebsd.org/D52450 2025-08-28T18:36:15Z Colin Percival cperciva@FreeBSD.org 2025-08-28T18:32:55Z urn:sha1:778bfd4e1033715de6cf21e2e2454bdea2a0f1ab We ship cloudware images without a downloaded copy of the pkg repo database, since it will typically be wildly out of date by the time cloudware releases get launched. These paths changed due to the "FreeBSD" -> "FreeBSD-ports" renaming in /etc/pkg/FreeBSD.conf. While I'm here, nuke the FreeBSD-ports-kmods repo database too; I forgot to add that when we added that to /etc/pkg/FreeBSD.conf. Fixes: c83705a5756e ("Rename FreeBSD* pkg repos to FreeBSD-ports*") 2025-05-14T23:54:04Z Colin Percival cperciva@FreeBSD.org 2025-05-14T23:36:26Z urn:sha1:9a685c09f06a55b18589d75f9307563d84a17fa9 Early versions of Xen, including those used in the early days of EC2, had a bug in their UART emulation whereby the TX FIFO wouldn't send the expected interrupt when emptying; as a result, FreeBSD would write 16 characters to the serial console and then stop because we thought the FIFO was forever full. In 2013 (1c60b24baa50) I added a loader tunable "hw.broken_txfifo" which spinwaits for the FIFO TX rather than relying on the interrupt, and enabled this in loader.conf in EC2 images. A decade later, this workaround is almost certainly no longer needed in EC2 -- most instances don't run Xen, and the bug was long since fixed in Xen anyway -- but we've been holding on to the workaround "just in case". Unfortunately, the spinwait behaviour is causing latency spikes and triggering warnings from the ena(4) driver. This commit removes the hw.broken_txfifo setting from loader.conf in EC2 images, but leaves the loader tunable and associated code, since it has been necessary in some other environments. (It seems that the TX FIFO missing-interrupts bug has been independently written at least three times!) MFC after: 1 minute Sponsored by: Amazon 2025-04-23T15:19:28Z Colin Percival cperciva@FreeBSD.org 2025-04-23T15:17:51Z urn:sha1:ce9a34b1614e37dc3f8763586448063408c7bf16 Having this enabled on Graviton systems prior to Graviton 4 results in a resource leak and a kernel panic after repeated hotplug/unplug. MFC after: 3 days Sponsored by: Amazon 2025-04-02T20:14:24Z Colin Percival cperciva@FreeBSD.org 2025-03-31T04:11:23Z urn:sha1:80febaa1714e897d67a8217edc305a0e81498a6f Since PCIe device detaching is done via API, there is no opportunity to "press the attention button a second time" and thus the 5 second timeout mandated by PCIe serves no purpose. MFC after: 2 weeks Sponsored by: Amazon