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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:  <49C872EA.4010304@gmail.com>
Date:	Mon, 23 Mar 2009 23:43:06 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org
Subject:  Re: ACPI: I/O resource 0000:00:1f.3 [0xefa0-0xefbf] conflicts with
 ACPI   region SMBI [0xefa0-0xefaf]

justinmattock@...il.com wrote:
> 
> Any suggestions on what this might be:
> (dmesg):
> 
> [    6.940280] power_supply ADP1: 1 dynamic props
> [    6.940283] power_supply ADP1: prop ONLINE=1
> [    6.940340] input: Sleep Button (CM) as 
> /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input5
> [    6.968564] i801_smbus 0000:00:1f.3: PCI INT B -> GSI 19 (level, low) 
> -> IRQ 19
> [    6.977814] ACPI: I/O resource 0000:00:1f.3 [0xefa0-0xefbf] conflicts 
> with ACPI region SMBI [0xefa0-0xefaf]
> [    6.987218] ACPI: Device needs an ACPI driver

It means the i801_smbus driver is using an I/O resource range that BIOS 
ACPI code may be using. The warning is there because in some cases this 
can cause problems, i.e. if the native driver and ACPI AML code try to 
access the device at the same time in a conflicting fashion.

> [    7.000114] ath9k: 0.1
> [    7.000163] ACPI: Sleep Button (CM) [SLPB]
> [    7.018052] ath9k 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> 
> IRQ 17
> [    7.027094] ath9k 0000:03:00.0: setting latency timer to 64
> 
> either i801_smbus(to me) is the issue, or it's something else.
> 
> any ideas?
> 
> -- Justin P. Mattock

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ