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 08:57:51 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Yinghai Lu <yhlu.kernel@...il.com>
Cc:	Frans Pop <elendil@...net.nl>, linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Linux 2.6.31-rc4: strange change in iomem allocation

On Thu, 23 Jul 2009 07:42:28 -0700
Yinghai Lu <yhlu.kernel@...il.com> wrote:

> On Thu, Jul 23, 2009 at 7:14 AM, Frans Pop<elendil@...net.nl> 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
> >
> > System is HP 2510p notebook (x86_64).
> 
> should be ok. we don't need that
>    fec00000-fec000ff : pnp 00:0c

So the PNP ranges are duplicating the IOAPIC range?  Seems harmless
enough...

-- 
Jesse Barnes, Intel Open Source Technology Center
--
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