linux-kernel - Re: [bisected][resend] pnp: Huge number of "io resource overlap" messages

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, 9 Sep 2008 11:40:25 -0600
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	Frans Pop <elendil@...net.nl>
Cc:	linux-kernel@...r.kernel.org, Rene Herman <rene.herman@...il.com>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [bisected][resend] pnp: Huge number of "io resource overlap" messages

On Tuesday 09 September 2008 10:26:17 am Frans Pop wrote:
> > What do "lspci -vv" and /proc/ioports and /proc/iomem show for you?
> 
> Thanks for the background info and data for comparison.
> Here's what I have (full info attached). AFAICT it looks equally sane and 
> consistent.
> 
> 00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM 
> (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller [8086:24c5] (rev 03)
>         Region 0: I/O ports at 1000 [size=256]
>         Region 1: I/O ports at 1880 [size=64]
>         Region 2: Memory at 28080800 (32-bit, non-prefetchable) [size=512]
>         Region 3: Memory at 28080a00 (32-bit, non-prefetchable) [size=256]
> 
> 00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) 
> AC'97 Modem Controller [8086:24c6] (rev 03)
>         Region 0: I/O ports at 1400 [size=256]
>         Region 1: I/O ports at 1800 [size=128]

Yup, this all looks reasonable to me, too.  But these regions must be
different than they were when the PNP quirk ran.  I wonder if the BIOS
left them unprogrammed, we ran the PNP quirk and discovered all these
"conflicts," then PCI came along and assigned resources.

Your dmesg shows power state changes for the PCI devices.  Maybe
the BIOS left them in D3 and unprogrammed:

  Intel ICH Modem 0000:00:1f.6: power state changed by ACPI to D0
  Intel ICH 0000:00:1f.5: power state changed by ACPI to D0
  Intel ICH 0000:00:1f.5: enabling device (0000 -> 0003)

If the PCI device isn't fully initialized, it doesn't seem right to
check it for resource conflicts.  But I don't know how to tell that.

Can you figure out where the 1f.5 and 1f.6 resources get assigned?

> /proc/ioports:
> 1000-10ff : 0000:00:1f.5
>   1000-10ff : Intel 82801DB-ICH4
> 1400-14ff : 0000:00:1f.6
>   1400-14ff : Intel 82801DB-ICH4 Modem
> 1800-187f : 0000:00:1f.6
>   1800-187f : Intel 82801DB-ICH4 Modem
> 1880-18bf : 0000:00:1f.5
>   1880-18bf : Intel 82801DB-ICH4
> 
> /proc/iomem:
> 28080800-280809ff : 0000:00:1f.5
>   28080800-280809ff : Intel 82801DB-ICH4
> 28080a00-28080aff : 0000:00:1f.5
>   28080a00-28080aff : Intel 82801DB-ICH4
--
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/