On Sun, Aug 10, 2014 at 8:55 AM, Yinghai Lu <yinghai@xxxxxxxxxx> wrote: > On Sat, Aug 9, 2014 at 3:45 PM, Mantas Mikulėnas <grawity@xxxxxxxxx> wrote: >> On Sat, Aug 9, 2014 at 10:23 PM, Matt Fleming <matt@xxxxxxxxxxxxxxxxx> wrote: >> [However... Whether it's five chunks, four (after making the initrd >> smaller), or just one (with your efi=nochunk), I noticed that it >> *always* hangs during the *last* read, and the allocated memory always >> ends at roughly the same address (0x137fffXXX). I wonder if it's >> selecting a memory location already in use, or something like that...] >> >> (The laptop is Asus K52JT, AMI firmware v206, no updates available.) > > wonder if efi_file_read return with wrong chunksize. > > Can you try attached patch ? Thanks, but it didn't change anything. (I tried adding some efi_printk's, and as far as I can see, efi_file_read *doesn't* return at all.) -- Mantas Mikulėnas <grawity@xxxxxxxxx> -- 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
