Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754549AbZGWQaU (ORCPT ); Thu, 23 Jul 2009 12:30:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754305AbZGWQaT (ORCPT ); Thu, 23 Jul 2009 12:30:19 -0400 Received: from smtp1.linux-foundation.org ([140.211.169.13]:52529 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754535AbZGWQaS (ORCPT ); Thu, 23 Jul 2009 12:30:18 -0400 Date: Thu, 23 Jul 2009 09:29:13 -0700 (PDT) From: Linus Torvalds X-X-Sender: torvalds@localhost.localdomain To: Frans Pop cc: linux-kernel@vger.kernel.org, Yinghai Lu , Jesse Barnes Subject: Re: Linux 2.6.31-rc4: strange change in iomem allocation In-Reply-To: Message-ID: References: <200907231614.23570.elendil@planet.nl> <200907231653.48933.elendil@planet.nl> User-Agent: Alpine 2.01 (LFD 1184 2008-12-16) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 871 Lines: 27 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. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/