On Sat, May 28, 2016 at 01:46:07PM -0700, Andy Lutomirski wrote: > My garbage workstation splats like this on boot: > > [ 0.160523] ioremap: invalid physical address d0c801800000001 > > This was fixed for a while, but I think the problem was reintroduced by: > > commit 66dbe99cfe30e113d2e571e68b9b6a1a8985a157 > Author: Môshe van der Sterre <me@xxxxxxxx> > Date: Mon Feb 1 22:07:03 2016 +0000 > > x86/efi/bgrt: Don't ignore the BGRT if the 'valid' bit is 0 > > Is there any good way to fix this again? This was the kind of concern I had about ignoring the valid bit. I supported this patch based on the statement that Windows 10 ignores the valid bit as well. Presumably either Windows has some way of detecting this kind of problem, or it would break on that system. If the former, does anyone know what algorithm Windows uses to safely check for BGRT? I can see two possible ways to fix this. If we can detect in advance that the address in the BGRT looks bogus (pointing to physical memory that doesn't exist, for instance), then we could ignore it entirely (without any warning if valid==0, or with a warning if valid==1). If we can't detect that in advance, then we need to revert this patch and go back to respecting the valid bit. (However, trying to check the address in advance seems preferable given that some BIOS might have a bogus address even with valid==1.) -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
