On 28 June 2018 at 18:15, Geoff Levand <geoff@xxxxxxxxxxxxx> wrote: > Hi Ard, > > On 06/28/2018 03:25 AM, Ard Biesheuvel wrote: > >> Given how the upstream kernel is aimed at future development, I don't >> think we should fix this in the upstream kernel at all. Distros are >> free to do what they like, of course, and I'm sure RedHat already have >> a fix for this in their downstream kernel. > > Debian expects the kernel to work correctly, and so won't add a fix. > That means CONFIG_ACPI_APEI can't be enabled, and so users must either > go without APEI or use a custom built kernel. See: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900581 > Hi Geoff, I am aware of the context of this discussion, and I feel your pain, given that you don't care about m400 in the first place. So I guess we should take this up with the Debian folks directly. They apparently do care about m400, and are reluctant to have to add 'hest_disable=1' to the kernel command line. But that does not make it an upstream problem. The fact that this is an EOL platform of which only a couple of hundred are in circulation, combined with the fact that there is a trivial workaround available (the command line option) makes it a non-issue in my opinion, especially given the fact that not a single distro ships pristine mainline kernels, and so they can carry the quirk themselves. I -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
