lkml.org 
[lkml]   [2009]   [Jul]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Linux 2.6.31-rc4: strange change in iomem allocation
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...


\
 
 \ /
  Last update: 2009-07-24 07:11    [W:0.970 / U:0.112 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site