I added the "proposed" source and from there installed kernel 3.19.0-46 (using Synaptic). Booted with acpi_force_32bit_fadt_addr and system froze.
I get the feeling this kernel wasn't the one I was supposed to be testing with. Could it be because I am on Trusty? Is the proposed kernel released to be available for me to test? I see the tags about vivid and wily but the problem occurs for Trusty users too.
Also wondering about something Mr. Zheng wrote on the bug on bugzilla.kernel.org:
"What we can offer here is to provide a quirk for your platform to revert the behavior back to favor 32-bit GAS values on this platform before your issue is root caused."
Wouldn't it be nicer to also detect this computer automatically and force 32-bit registers so the boot parameter wouldn't be needed? Many people won't want to bother with boot parameters - they'll just see how Ubuntu doesn't boot on their machines and be disappointed. Or should we wait until the quirk is added upstream?
I added the "proposed" source and from there installed kernel 3.19.0-46 (using Synaptic). Booted with acpi_force_ 32bit_fadt_ addr and system froze.
I get the feeling this kernel wasn't the one I was supposed to be testing with. Could it be because I am on Trusty? Is the proposed kernel released to be available for me to test? I see the tags about vivid and wily but the problem occurs for Trusty users too.
Also wondering about something Mr. Zheng wrote on the bug on bugzilla. kernel. org:
"What we can offer here is to provide a quirk for your platform to revert the behavior back to favor 32-bit GAS values on this platform before your issue is root caused."
Wouldn't it be nicer to also detect this computer automatically and force 32-bit registers so the boot parameter wouldn't be needed? Many people won't want to bother with boot parameters - they'll just see how Ubuntu doesn't boot on their machines and be disappointed. Or should we wait until the quirk is added upstream?