On Mon, Dec 12, 2016 at 01:46:21AM +0300, Slawa Olhovchenkov wrote: > > > > > > Can you show the verbose dmesg up to the failure point ? > > > > > > In particular, the SMAP lines should be relevant. > > > > > > > > > > KDB: debugger backends: ddb > > > > > KDB: current backend: ddb > > > > > exit from kdb_init > > > > > KDB: enter: Boot flags requested debugger > > > > > [ thread pid 0 tid 0 ] > > > > > Stopped at 0xffffffff805361eb = kdb_enter+0x3b: movq > > > > > $0,0xffffffff80dcef20 = kdb_why Hang at boot is result of combination next two BIOS setting: NUMA enabled Socket Interleave below 4G enabled (memory options) Disabling any allow boot.Received on Sun Dec 11 2016 - 22:09:55 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:09 UTC