| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 05 Oct 2012 18:15:22 -0500 From: Peter Tyser <ptyser@...-inc.com> To: Miles Lane <miles.lane@...il.com> Cc: LKML <linux-kernel@...r.kernel.org>, Jean Delvare <khali@...ux-fr.org> Subject: Re: 3.6.0+ (GIT) -- lpc_ich: Resource conflict(s) found affecting gpio_ich Hi Miles, On Thu, 2012-10-04 at 10:14 -0400, Miles Lane wrote: > ACPI Warning: 0x0000000000000828-0x000000000000082f SystemIO conflicts > with Region \PMIO 1 (20120711/utaddress-251) > ACPI: If an ACPI driver is available for this device, you should use > it instead of the native driver > ACPI Warning: 0x0000000000000500-0x000000000000053f SystemIO conflicts > with Region \GPIO 1 (20120711/utaddress-251) > ACPI: If an ACPI driver is available for this device, you should use > it instead of the native driver > lpc_ich: Resource conflict(s) found affecting gpio_ich Jean Delvare submitted a patch which may allow you to use the GPIO pins in banks not claimed by the BIOS: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=4f600ada70beeb1dfe08e11e871bf31015aa0a3d This patch is not in 3.6, but will be included in 3.7. You could also try adding "acpi_enforce_resources=lax" or "acpi_enforce_resources=no" to your kernel parameters to disable the ACPI conflict checking. Note this could have other unintended consequences. Best, Peter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists