On Fri, Apr 30, 2021 at 5:57 PM George Kennedy <george.kennedy@xxxxxxxxxx> wrote: > > > > On 4/30/2021 9:40 AM, Greg Kroah-Hartman wrote: > > On Thu, Apr 29, 2021 at 01:24:06PM -0400, George Kennedy wrote: > >> > >> On 4/28/2021 8:52 AM, George Kennedy wrote: > >>> > >>> On 4/28/2021 12:57 AM, Greg Kroah-Hartman wrote: > >>>> On Tue, Apr 27, 2021 at 06:18:05PM -0400, George Kennedy wrote: > >>>>> CC+ stable@xxxxxxxxxxxxxxx > >>>>> > >>>>> On 4/27/2021 6:17 PM, George Kennedy wrote: > >>>>>> Hello Greg, > >>>>>> > >>>>>> We need the following 2 upstream commits applied to 5.4.y to > >>>>>> fix an iBFT > >>>>>> boot failure: > >>>>>> > >>>>>> 2021-03-29 rafael.j.wysocki@xxxxxxxxx - 1a1c130a 2021-03-23 Rafael J. > >>>>>> Wysocki ACPI: tables: x86: Reserve memory occupied by ACPI tables > >>>>>> 2021-04-13 rafael.j.wysocki@xxxxxxxxx - 6998a88 2021-04-13 Rafael J. > >>>>>> Wysocki ACPI: x86: Call acpi_boot_table_init() after > >>>>>> acpi_table_upgrade() > >>>>>> > >>>>>> Currently, only the first commit (1a1c130a) is destined for > >>>>>> 5.10 & 5.11. > >>>>>> > >>>>>> The 2nd commit (6998a88) is needed as well and both commits are needed > >>>>>> in 5.4.y. > >>>> Is this a regression (i.e. did this hardware work on older kernels?), > >>>> and if so, what commit caused the problem? > >>>> > >>>> These commits are already in 5.10.y, what changed in older kernels to > >>>> require this to be backported? > >> Hello Greg, > >> > >> Can the same 2 patches also be applied to 4.14.y, which one of distros is > >> based on? > >> > >> 4.14.y crashes during ibft boot with KASAN enabled without the 2 patches. > > What about 4.19.y? You do not want to skip anything in the middle, > > right? > > > > And I need an ack from the authors and maintainers of these changes > > before I can take them into the stable trees. Any reason you didn't cc: > > them all? > CC+ maintainers > > Rafael and Mike, > > We need Rafael's 2 upstream ACPI commits (1a1c130a & 6998a88) backported > to more of the stable branches - at least in 5.4.y, 4.14.y, and 4.19.y. > > Can you (along with the other maintainers) ACK the request? Sure, please send an inclusion request to stable@xxxxxxxxxxxxxxx as per the documentation with a CC to me and I'll respond with an ACK if needed. Thanks!
