On Tue, Oct 17, 2023 at 04:42:29PM +0300, Andy Shevchenko wrote: > On Tue, Oct 17, 2023 at 03:32:45PM +0200, Jan Kara wrote: > > On Tue 17-10-23 14:46:20, Andy Shevchenko wrote: > > > On Tue, Oct 17, 2023 at 01:32:53PM +0300, Andy Shevchenko wrote: > > > > On Tue, Oct 17, 2023 at 01:29:27PM +0300, Andy Shevchenko wrote: > > > > > On Tue, Oct 17, 2023 at 01:27:19PM +0300, Andy Shevchenko wrote: > > > > > > On Wed, Aug 30, 2023 at 12:24:34PM +0200, Jan Kara wrote: > > > > > > > Hello Linus, ... > > > > > > This merge commit (?) broke boot on Intel Merrifield. > > > > > > It has earlycon enabled and only what I got is watchdog > > > > > > trigger without a bit of information printed out. > > > > > > Okay, seems false positive as with different configuration it > > > boots. It might be related to the size of the kernel itself. > > > > Ah, ok, that makes some sense. > > I should have mentioned that it boots with the configuration say "A", > while not with "B", where "B" = "A" + "C" and definitely the kernel > and initrd sizes in the "B" case are bigger. If it's a size (which is only grew from 13M->14M), it's weird. Nevertheless, I reverted these in my local tree 85515a7f0ae7 (HEAD -> topic/mrfld) Revert "defconfig: enable DEBUG_SPINLOCK" 786e04262621 Revert "defconfig: enable DEBUG_ATOMIC_SLEEP" 76ad0a0c3f2d Revert "defconfig: enable DEBUG_INFO" f8090166c1be Revert "defconfig: enable DEBUG_LIST && DEBUG_OBJECTS_RCU_HEAD" and it boots again! So, after this merge something affects one of this? I'll continuing debugging which one is a culprit, just want to share the intermediate findings. -- With Best Regards, Andy Shevchenko
