From: David John <davidjon@xenontk.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Frans Pop <elendil@planet.nl>,
linux-kernel@vger.kernel.org, Yinghai Lu <yinghai@kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: Linux 2.6.31-rc4: strange change in iomem allocation
Date: Fri, 24 Jul 2009 10:04:58 +0530 [thread overview]
Message-ID: <4A6939F2.3050006@xenontk.org> (raw)
In-Reply-To: <alpine.LFD.2.01.0907230926140.21520@localhost.localdomain>
On 07/23/2009 09:59 PM, Linus Torvalds wrote:
>
> On Thu, 23 Jul 2009, Linus Torvalds wrote:
>> Don't worry about the new warning.
>>
>> It is in fact _normal_ to see a number of warnings about PnP resources
>> "could not be reserved"
>
> In fact, I notice that you had them even before, eg:
>
> system 00:00: iomem range 0x0-0x9ffff could not be reserved
> system 00:00: iomem range 0xe0000-0xfffff could not be reserved
> system 00:00: iomem range 0x100000-0x7e7fffff could not be reserved
>
> which are about exactly the same thing - e820 RAM reservations take
> precedence over the PnP ones.
>
> So the only new thing is that we claim the APIC thing to that category
> too.
>
If the kernel knows that those ranges have already been reserved, can't
the PnP messages be suppressed? I used to think these were errors as
well (because of some BIOS misbehaviour) until I checked the code...
next prev parent reply other threads:[~2009-07-24 5:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 2:44 Linux 2.6.31-rc4 Linus Torvalds
2009-07-23 14:14 ` Linux 2.6.31-rc4: strange change in iomem allocation Frans Pop
2009-07-23 14:42 ` Yinghai Lu
2009-07-23 15:57 ` Jesse Barnes
2009-07-23 14:53 ` Frans Pop
2009-07-23 16:12 ` Linus Torvalds
2009-07-23 16:29 ` Linus Torvalds
2009-07-24 4:34 ` David John [this message]
2009-07-24 5:51 ` Kind of like the following. Apply if you feel it is ok to _not_ David John
2009-07-24 7:53 ` [PATCH?] Re: Linux 2.6.31-rc4: strange change in iomem allocation Frans Pop
2009-07-24 6:11 ` [PATCH] Remove Spurious PnP Memory Reserved Warning David John
2009-07-25 7:12 ` David John
2009-07-28 4:06 ` [PATCH v2] " David John
2009-07-28 16:31 ` Jesse Barnes
2009-07-29 6:42 ` David John
2009-08-01 10:56 ` Frans Pop
2009-08-06 21:41 ` Jesse Barnes
2009-07-23 17:21 ` Linux 2.6.31-rc4 Krzysztof Olędzki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A6939F2.3050006@xenontk.org \
--to=davidjon@xenontk.org \
--cc=elendil@planet.nl \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox