From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [PATCH] Prevent reserving RAM in the region already reserved by BIOS Date: Wed, 19 May 2010 17:09:19 -0700 Message-ID: <4BF47DAF.5040409@zytor.com> References: <4BF42296.1030905@oracle.com> <4BF4235D.3080904@zytor.com> <4BF46D9B.4090806@zytor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from terminus.zytor.com ([198.137.202.10]:52632 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752912Ab0ETAKI (ORCPT ); Wed, 19 May 2010 20:10:08 -0400 In-Reply-To: Sender: linux-arch-owner@vger.kernel.org List-ID: To: Mathieu Rondonneau Cc: Yinghai , linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, Ingo Molnar , Linus Torvalds On 05/19/2010 05:01 PM, Mathieu Rondonneau wrote: > it' s not in ISA space. > once loading the NVIDIA driver, the warnign oops shows up. > 4K starting at 0x9f800 (i.e. to 0xa007ff) overlap with the ISA space > (starting at 0xa0000). > > When I don' t load the driver, no oops. > So I am assuming nvidia driver request 4K of memory, that happens to > be available in the bios area. > > I think that there is a check missing somewhere to report that > available RAM buffer is already reserved (by BIOS) so we need to get > it from somewhere else. > > Does it make sense? > -Mathieu No. The top page (0x9f000) is generally also reserved... there is pretty much always BIOS data structures there. It sounds like the Nvidia driver is trying to map those, and doing it incorrectly. -ENVIDIA. -hpa