I disagree. It is a bootblock bug which should be fixed. A refactoring caused it to use more memory, and there is a problem.
I wish everyone would stop making excuses. > On Tue, Nov 27, 2018 at 11:48:38AM +0100, Riccardo Mottola wrote: > > Hi all, > > > > I have a strange and blocking issue after upgrade to 6.4 on my x86-64 > > laptop, which was running 6.3 just fine. > > > > I got the bsd.rd kernel, booted it and installed, quick, easy no issue. > > Now, if I reboot, the kernel will reboot just after having written the first > > line of numbers on the screen. > > > > The bad news is that both booting the new kernel as well as the bsd.rd > > kernel gives the issue, so the existing bsd.rd which for installation booted > > just fine. > > > > The only thing I can think is that the boot blocks were updated and that > > they fail to load. > > > > I also tried making an USB key with 64, I get to the bootloader prompt, but > > everything I try will make the laptop reboot, both booting from hd0a as > > wella s hd1a! > > I also tried making an USB key with 63, but that too fails the same way? > > > > Windows partition continues to boot fine, or I would almost think of having > > some sort of hardware failure!!! > > > > I did not make changes to the Bios, UEFI boot is still disabled. I found > > "Intel Anti-Theft" enabled and disabled it. > > > > And now? > > Please check, that you don't use only one big a partition, and if you do, > please backup and rearrange your disklabels. This approach is not > working with 6.4 anymore and was already discussed several times > recently on this very ML. > > hth, > Marc >