linux-kernel - Re: New conflict message in latest GIT

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 22 Jul 2008 22:00:06 +0200
From:	Rene Herman <rene.herman@...access.nl>
To:	Fabio Comolli <fabio.comolli@...il.com>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>,
	Bjorn Helgaas <bjorn.helgaas@...com>
Subject: Re: New conflict message in latest GIT

On 22-07-08 20:56, Fabio Comolli wrote:

> Linus' GIT tree 2.6.26-05752-g93ded9b shows this message:
> 
> i801_smbus 0000:00:1f.3: PCI INT B -> GSI 19 (level, low) -> IRQ 19
> ACPI: I/O resource 0000:00:1f.3 [0x18e0-0x18ff] conflicts with ACPI
> region SMBI [0x18e0-0x18ef]
> ACPI: Device needs an ACPI driver
> 
> There is no equivalent in 2.6.26 or previous kernels.

[ snip ]

> 00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)

I believe this message in itself needn't be a problem but the code 
producing this warning isn't new...

Bjorn, this reminds me of the:

pnp-have-quirk_system_pci_resources-include-io-resources.patch

in Andrew's tree that I need to have my soundcard not fail due to the IO 
resource being claimed by PNPACPI. The fact that I needed it was new to 
2.6.26 (but going back to 2.6.25 I all of a sudden also needed it there 
which made me conclude that some BIOS reconfig had occured).

ACPI isn't doing odd things I hope?

Rene.
--
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/