On Wed, Sep 21, 2022 at 8:03 PM Michal Koutný <mkoutny@xxxxxxxx> wrote: > On Wed, Sep 21, 2022 at 05:44:56PM +0300, Anatoly Pugachev <matorola@xxxxxxxxx> wrote: > > On Sun, Sep 18, 2022 at 12:39 PM Anatoly Pugachev <matorola@xxxxxxxxx> wrote: > > > > > > > > > I'm unable to boot my sparc64 VM anymore (5.19 still boots, 6.0-rc1 does not), > > > bisected up to this patch, > > > > > > mator@ttip:~/linux-2.6$ git bisect bad > > > 1d0403d20f6c281cb3d14c5f1db5317caeec48e9 is the first bad commit > > > commit 1d0403d20f6c281cb3d14c5f1db5317caeec48e9 > > > > reverting this patch makes my sparc64 box boot successfully. > > The failed address falls into vmmemmap region (per your boot log > output). It looks like the respective page/folio (of init_net struct) is > unbacked there (and likely folio_test_slab fails dereferencing ->flags). > > Would you mind sharing your kernel's config? > (I'm most curious about CONFIG_SPARSMEM_VMEMMAP, I'm not familiar with > your arch at all though.) mator@ttip:~/dmesg$ zcat config-6.0.0-rc6-00010-gb7f0f527dc3c.gz | grep VMEMMAP CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y CONFIG_SPARSEMEM_VMEMMAP=y I do upload config and boot logs to https://github.com/mator/sparc64-dmesg building a new kernel version/releases as 'make olddefconfig && make -j' current version of booted 6.0.0-rc6 is available as https://github.com/mator/sparc64-dmesg/blob/master/config-6.0.0-rc6-00010-gb7f0f527dc3c.gz
