Attachment 249374 Details for Bug 272507 – Errata Template partially filled to add EN to 14.0

Errata Template partially filled to add EN to 14.0

file_272507.txt (text/plain), 4.59 KB, created by Justin Tocci on 2024-03-21 14:45:03 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Justin Tocci

Created: 2024-03-21 14:45:03 UTC

Size: 4.59 KB

patch

obsolete

>=============================================================================
>FreeBSD-EN-ERRATA_NOTICE                                      Errata Notice
>                                                          The FreeBSD Project
>
>Topic:          Defer reserving resources for ACPI devices
>
>Category:       core
>Module:         acpi
>Announced:      2024-XX-XX
>Credits:
>Affects:        FreeBSD 14.0
>Corrected:      2024-XX-XX XX:XX:XX UTC (stable/14, 14.0-STABLE)
>                2024-XX-XX XX:XX:XX UTC (releng/14.0, 14.0-RELEASE-pXX)
>
>I.   Background
>
><URL:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272507>
>When running FreBSD 13 on a new X670E Steel Legend motherboard dmesg showed errors and SATA drives showed in BIOS but would not show in /dev. SATA works fine in Windows and Arch.
>
>A patch to 13 was made but hasn't shown in 14.
>
>II.  Problem Description
>
>The goal of reserving firmware-assigned resources is to ensure that
>"wildcard" resource allocation requests will not claim an address
>range that is actually in use even if no attached driver is actively
>using that range.  However, the current approach can break in some
>cases.
>
>In particular, ACPI can enumerate devices behind PCI bridges that
>don't show up in a normal PCI scan, but those device_t objects can end
>up as direct children of acpi0.  Reserving resources for those devices
>directly from acpi0 ends up conflicting with later attempts to reserve
>the PCI bridge windows.
>
>III. Impact
>
>SATA devices on some motherboards (X670E) will not show in /dev making them unavailable.
>
>IV.  Workaround
>
>As a workaround, defer reserving unclaimed resources until after the
>initial probe and attach scan.  Eventually this pass of reserving
>unclaimed resources can be moved earlier, but it requires changes to
>other drivers in the tree to permit enumerating devices and reserving
>firmware-assigned resources in a depth-first traversal before
>attaching devices whose drivers request wildcard allocations.
>
>V.   Solution
>
>https://cgit.freebsd.org/src/commit/?id=f15ff67ef9379e2fe4909c96fb8e4153c32bafe1
>
>Upgrade your system to a supported FreeBSD stable or release / security
>branch (releng) dated after the correction date.
>
>NEEDS REBOOT
>
>Perform one of the following:
>
>1) To update your system via a binary patch:
>
>Systems running a RELEASE version of FreeBSD on the amd64 or arm64 platforms,
>or the i386 platform on FreeBSD 14, can be updated via the freebsd-update(8)
>utility:
>
># freebsd-update fetch
># freebsd-update install
>NEEDS REBOOT
>
>2) To update your system via a source code patch:
>
>The following patches have been verified to apply to the applicable
>FreeBSD release branches.
>
>a) Download the relevant patch from the location below, and verify the
>detached PGP signature using your PGP utility.
>
>[FreeBSD 14.1]
># fetch https://security.FreeBSD.org/patches/EN-XX:XX/XXXX.patch
># fetch https://security.FreeBSD.org/patches/EN-XX:XX/XXXX.patch.asc
># gpg --verify XXXX.patch.asc
>
>b) Apply the patch.  Execute the following commands as root:
>
># cd /usr/src
># patch < /path/to/patch
>
><for a kernel bug:>
>
>c) Recompile your kernel as described in
><URL:https://www.FreeBSD.org/handbook/kernelconfig.html> and reboot the
>system.
>
>VI.  Correction details
>
>This issue is corrected as of the corresponding Git commit hash or Subversion
>revision number in the following stable and release branches:
>
>Branch/path                             Hash                     Revision
>-------------------------------------------------------------------------
>stable/14/                              XXXXXXXXXXXX    stable/14-nXXXXXX
>releng/14.1/                            XXXXXXXXXXXX  releng/14.0-nXXXXXX
>-------------------------------------------------------------------------
>
>Run the following command to see which files were modified by a
>particular commit:
>
># git show --stat <commit hash>
>
>Or visit the following URL, replacing NNNNNN with the hash:
>
><URL:https://cgit.freebsd.org/src/commit/?id=NNNNNN>
>
>To determine the commit count in a working tree (for comparison against
>nNNNNNN in the table above), run:
>
># git rev-list --count --first-parent HEAD
>
>VII. References
>
>Initial info on this document was copied by Justin Tocci from here:
>https://cgit.freebsd.org/src/commit/?id=f15ff67ef9379e2fe4909c96fb8e4153c32bafe1
>If I am misrepresenting Oleg Sidorkin <osidorkin@gmail.com> or anyone else it is my fault.
>
>
><URL:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272507>
>
>The latest revision of this advisory is available at
><URL:https://security.FreeBSD.org/advisories/FreeBSD-EN-XX:XX.XXXXX.asc>

Actions: View

Attachments on bug 272507: 243436 | 244596 | 244598 | 245842 | 248276 | 248321 | 248323 | 248494 | 248628 | 249374