linux-kernel - Re: Linux 2.6.31-rc4: strange change in iomem allocation

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:	Thu, 23 Jul 2009 16:53:48 +0200
From:	Frans Pop <elendil@...net.nl>
To:	linux-kernel@...r.kernel.org
Cc:	Yinghai Lu <yinghai@...nel.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Linux 2.6.31-rc4: strange change in iomem allocation

On Thursday 23 July 2009, Frans Pop wrote:
> I'm seeing the following change in dmesg between -rc3 and -rc4:
> -system 00:0c: iomem range 0xfec00000-0xfec000ff has been reserved
> +system 00:0c: iomem range 0xfec00000-0xfec000ff could not be reserved
>
> There is nothing in the earlier part of dmesg that would explain this
> change.
>
> The change is also visible in /proc/iomem:
>  fec00000-fec00fff : IOAPIC 0
>    fec00000-fec00fff : reserved
> -    fec00000-fec000ff : pnp 00:0c
>
> I somewhat suspect 857fdc53a0a90c3ba7fcf5b1fb4c7a62ae03cf82:
>     x86/pci: insert ioapic resource before assigning unassigned resources

Reverting that commit did indeed restore the old situation.
--
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/