I have a GA-E350N-WIN8 gigabyte motherboard, after kernel commit 9479c7cebfb568f8b8b424be7f1cac120e9eea95 the amd64 kernel no longer boots (commit ab72a27da4c6c19b0e3d6d7556fdd4afb581c8ac) works. This bug was found with ubuntu and reported at: https://bugs.launchpad.net/bugs/1730069 Wit the broken kernel, ubuntu wont book, the screen just stays blank.
I can confirm this bug on different hardware (a Chromebook Samsung 500C). It, too, gets a black screen on boot. My kernel bisection has also identified this as the first bad commit: 9479c7cebfb568f8b8b424be7f1cac120e9eea95 is the first bad commit commit 9479c7cebfb568f8b8b424be7f1cac120e9eea95 Author: Matt Fleming <matt@codeblueprint.co.uk> Date: Fri Feb 26 21:22:05 2016 +0000 efi: Refactor efi_memmap_init_early() into arch-neutral code
I can also add that when the kernel is started via kexec instead of via normal hardware boot, the problem does not occur.
I've emailed the maintainers and patch authors here: https://www.spinics.net/lists/linux-efi/msg15846.html
The problems on my hardware were fixed, see: https://bugzilla.kernel.org/show_bug.cgi?id=203463