[email protected] wrote:
On 04/04/2017 11:04 PM, Michael Shell wrote:
On Tue, 4 Apr 2017 10:43:29 -0500
Bruce Dubbs <[email protected]> wrote:
This is what I found via google:
https://access.redhat.com/articles/65378
https://forum.manjaro.org/t/acpi-error-on-boot-after-updating-to-4-9/12894
And for me, this one:
https://bugzilla.kernel.org/show_bug.cgi?id=43229
It seems it is a BIOS problem, but OEMS are reluctant to fix things
like this, especially if MS Windows "works".
On the off chance it could get percolated up to the powers-that-be,
I would make sure that it still happens when running the latest BIOS
and then file a report with the motherboard maker.
In bugzilla URL above, there is a kernel patch:
https://bugzilla.kernel.org/attachment.cgi?id=99271&action=diff&collapsed=&headers=1&format=raw
that (re)enables support for the
libata.noacpi=1
kernel option (older kernels supported this option). Invoking that
option on boot will tell the kernel to ignore ACPI for the ATA devices.
Some people report that invoking that option improves drive performance
on boot (i.e., eliminating drive timeouts and reducing boot times) and
on wakeup:
https://bugzilla.redhat.com/show_bug.cgi?id=629315
I would invoke it on any system that is so improved.
Applying the patch with 'patch -p0 < ACPI.patch' produces: "can't find
file to patch at line 7" Using 'patch -p1 < ACPI.patch" displays several
Hunk failures.
Can the patch not be used with 4.9.9 or am I doing something wrong?
Just go to linux-4.10.8. The libata-acpi.c file looks quite a bit
different and at least some of the patch is applied there.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
