From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; dkim=none Received: from pepin.polanet.pl (pepin.polanet.pl [193.34.52.2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3F64D92; Tue, 21 Nov 2023 07:24:11 -0800 (PST) Date: Tue, 21 Nov 2023 16:24:07 +0100 From: Tomasz Pala To: Bjorn Helgaas Cc: linux-pci@vger.kernel.org, Dan J Williams , Kan Liang , Tony Luck , David E Box , Yunying Sun , Dave Jiang , Mika Westerberg , Giovanni Cabiddu , Herbert Xu , Hans de Goede , Florent DELAHAYE , Konrad J Hambrick , Matt Hansen <2lprbe78@duck.com>, Nicholas Johnson , Benoit =?iso-8859-2?Q?Gr=E9goire?= , Werner Sembach , mumblingdrunkard@protonmail.com, linux-kernel@vger.kernel.org, Bjorn Helgaas , Sebastian Manciulea Subject: Re: [PATCH 2/2] x86/pci: Treat EfiMemoryMappedIO as reservation of ECAM space Message-ID: <20231121152407.GA13288@polanet.pl> References: <20231118142143.GA14101@polanet.pl> <20231120162933.GA197390@bhelgaas> Precedence: bulk X-Mailing-List: linux-pci@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <20231120162933.GA197390@bhelgaas> User-Agent: Mutt/1.5.20 (2009-06-14) On Mon, Nov 20, 2023 at 10:29:33 -0600, Bjorn Helgaas wrote: > Thank you! A BIOS update is almost never the answer because even if > an update exists, we have to assume that most users in the field will > never install the update. Not to mention enabling 64-bit BARs, which is even more cumbersome ixgbe-specific magic that requires entirely dedicated tools... >> .text .data .bss are not marked as E820_TYPE_RAM! and >> DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x00000000df243000-0x00000000df251fff], contact BIOS vendor for fixes >> DMAR: [Firmware Bug]: Your BIOS is broken; bad RMRR [0x00000000df243000-0x00000000df251fff] [...] > I think Linux basically converts the info from EFI GetMemoryMap > to an e820 format; I think booting with "efi=debug" would show more > details of this. The dmesg I've attached today is with efi=debug, but the weird thing is - both of the above warnings manifested themself only once, with the first (verbose debugging: "MCFG debug") patch applied... Anyway. The "memremap attempted on mixed range 0x0000000000000000 size: 0x8000 WARNING: CPU: 0 PID: 1 at kernel/iomem.c:78 memremap+0x154/0x170" also seems to be triggered by "efi=debug", so my guess is that it's unrelated. -- Tomasz Pala