From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: Hugh Dickins <hughd@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
regressions@lists.linux.dev
Subject: Re: 6.6/regression/bisected - after commit a349d72fd9efc87c8fd1d16d3164752d84a7275b system stopped booting
Date: Fri, 1 Sep 2023 13:45:08 +0500 [thread overview]
Message-ID: <CABXGCsOyamBvQ=Y-M9HQBTfEDfaRwGqzXqayBm7L259Q+t+gJQ@mail.gmail.com> (raw)
In-Reply-To: <3548ca67-ce58-3bc6-fef5-348b98d7678b@google.com>
[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]
On Fri, Sep 1, 2023 at 12:29 PM Hugh Dickins <hughd@google.com> wrote:
>
>
> Thanks for all the info, which has helped in several ways. The only
> thing I can do is to offer you a debug (and then keep running) patch -
> suitable for the config you showed there, not for anyone else's config.
>
> I've never used stackdepot before, but I've tried this out in good and
> bad cases, and expect it to work for you, shedding light on where is
> going wrong - machine should boot up fine, and in dmesg you'll find one
> stacktrace between "WARNING: pte_map..." and "End of pte_map..." lines.
>
> To apply on top of a349d72fd9ef ("mm/pgtable: add rcu_read_lock() and
> rcu_read_unlock()s"), the bad end point of your bisection; but if you
> prefer, I can provide a version to go on top of whatever later Linus
> commit suits you.
>
> Patch not for general consumption, just for Mike's debugging:
> please report back the stacktrace shown - thanks!
>
Thanks for digging into the problem.
With the attached patch I got FTBFS when build kernel at commit a349d72fd9ef.
LD [M] drivers/gpu/drm/amd/amdgpu/amdgpu.o
MODPOST Module.symvers
ERROR: modpost: "pte_unmap" [arch/x86/kvm/kvm.ko] undefined!
ERROR: modpost: "pte_unmap" [drivers/vfio/vfio_iommu_type1.ko] undefined!
make[2]: *** [scripts/Makefile.modpost:144: Module.symvers] Error 1
make[1]: *** [/home/mikhail/packaging-work/git/linux/Makefile:1984:
modpost] Error 2
make: *** [Makefile:234: __sub-make] Error 2
--
Best Regards,
Mike Gavrilov.
[-- Attachment #2: build-log.zip --]
[-- Type: application/zip, Size: 130549 bytes --]
next prev parent reply other threads:[~2023-09-01 8:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 22:45 Mikhail Gavrilov
2023-08-31 23:35 ` Bagas Sanjaya
2023-09-01 7:29 ` Hugh Dickins
2023-09-01 8:45 ` Mikhail Gavrilov [this message]
2023-09-01 9:08 ` Hugh Dickins
2023-09-01 12:17 ` Mikhail Gavrilov
2023-09-01 22:48 ` Hugh Dickins
2023-09-02 9:51 ` Mikhail Gavrilov
2023-09-02 15:50 ` Hugh Dickins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABXGCsOyamBvQ=Y-M9HQBTfEDfaRwGqzXqayBm7L259Q+t+gJQ@mail.gmail.com' \
--to=mikhail.v.gavrilov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bagasdotme@gmail.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox