Am 05.03.2018 um 09:19 schrieb Kirill A. Shutemov: > On Sat, Mar 03, 2018 at 12:46:28PM +0100, Heiner Kallweit wrote: >> Am 03.03.2018 um 11:02 schrieb Ingo Molnar: >>> >>> * Heiner Kallweit <hkallweit1@xxxxxxxxx> wrote: >>> >>>> Am 03.03.2018 um 00:50 schrieb Dexuan-Linux Cui: >>>>> On Fri, Mar 2, 2018 at 12:57 PM, Heiner Kallweit <hkallweit1@xxxxxxxxx <mailto:hkallweit1@xxxxxxxxx>> wrote: >>>>> >>>>> Recently my Mini PC Zotac CI-321 started to reboot immediately before >>>>> anything was written to the console. >>>>> >>>>> Bisecting lead to b91993a87aff "x86/boot/compressed/64: Prepare >>>>> trampoline memory" being the change breaking boot. >>>>> >>>>> If you need any more information, please let me know. >>>>> >>>>> Rgds, Heiner >>>>> >>>>> >>>>> This may fix the issue: https://lkml.org/lkml/2018/2/13/668 >>>>> >>>>> Kirill posted a v2 patchset 3 days ago and I suppose the patchset should include the fix. >>>>> >>>> Thanks for the link. I bisected based on the latest next kernel including >>>> v2 of the patchset (IOW - the potential fix is included already). >>> >>> Are you sure? b91993a87aff is the old patch-set - which I just removed from -next >>> and which should thus be gone in the Monday iteration of -next. >>> >>> I have not merged v2 in -tip yet, did it get applied via some other tree? >>> >>> Thanks, >>> >>> Ingo >>> >> I wanted to apply the fix mentioned in the link but found that the statement was movq already. >> Therefore my (most likely false) understanding that it's v2. >> I'll re-test once v2 is out and let you know. > > movq fix is unrelated to the problem. > > Please check if current linux-next plus this patchset causes a problem for > you: > > http://lkml.kernel.org/r/20180227154217.69347-1-kirill.shutemov@xxxxxxxxxxxxxxx > linux-next from today boots fine with the patchset applied. Rgds, Heiner -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx"> email@xxxxxxxxx </a>