System: Intel i5 Skylake NUC (NUC6i5SYH)
This system boots fine from internal M2 (128GB) drive with 5.3-rc4.
With 5.3-rc5, it does not boot from M2 and is stuck on the Intel splash screen (no other text is displayed, no panic etc.). It will boot 5.3-rc5 from a USB flash memory stick (via the F10 boot menu), but not from the internal M2.
Bisecting between 5.3-rc4 and 5.3-rc5, the bad commit is:
neil@nm-linux:~/projects/pullrequest_repos/torvalds-linux$ git bisect bad
a90118c445cc7f07781de26a9684d4ec58bfcfd1 is the first bad commit
Author: John Hubbard <firstname.lastname@example.org>
Date: Tue Jul 30 22:46:27 2019 -0700
x86/boot: Save fields explicitly, zero out everything else
Recent gcc compilers (gcc 9.1) generate warnings about an out of bounds
memset, if the memset goes accross several fields of a struct. This
generated a couple of warnings on x86_64 builds in sanitize_boot_params().
Fix this by explicitly saving the fields in struct boot_params
that are intended to be preserved, and zeroing all the rest.
[ tglx: Tagged for stable as it breaks the warning free build there as well ]
Suggested-by: Thomas Gleixner <email@example.com>
Suggested-by: H. Peter Anvin <firstname.lastname@example.org>
Signed-off-by: John Hubbard <email@example.com>
Signed-off-by: Thomas Gleixner <firstname.lastname@example.org>
:040000 040000 e0963edca990540dd759765a3d765af4698df892 d07e645eb3a500c31bd65526205e286ff6941187 M arch
The kernel is built with gcc-9.2.0.
5.3-rc5 with "x86/boot: Save fields explicitly, zero out everything else" reverted will build with gcc-9.2.0, and boot from M2.
This should be fixed in 5.3-rc6 with https://lkml.org/lkml/2019/8/21/940
Fixed in 5.3-rc6. Many thanks!