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 17:17:34 +0500 [thread overview]
Message-ID: <CABXGCsOPcu8R9rpdihNR5r822FAHBZ42wBa5XUa5RDVierD_tg@mail.gmail.com> (raw)
In-Reply-To: <98eb1ba4-5bd3-ee7-1a88-47b054dc938@google.com>
[-- Attachment #1: Type: text/plain, Size: 687 bytes --]
On Fri, Sep 1, 2023 at 2:08 PM Hugh Dickins <hughd@google.com> wrote:
>
>
> Sorry about that, please try this instead, adds EXPORT_SYMBOL(pte_unmap).
>
Thanks, now I have a working kernel builded at commit a349d72fd9ef.
> 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.
Interesting, I checked twice but I didn't find any entry with
"pte_map" in the kernel log after applying your patch.
--
Best Regards,
Mike Gavrilov.
[-- Attachment #2: dmesg.zip --]
[-- Type: application/zip, Size: 47546 bytes --]
next prev parent reply other threads:[~2023-09-01 12:17 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
2023-09-01 9:08 ` Hugh Dickins
2023-09-01 12:17 ` Mikhail Gavrilov [this message]
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=CABXGCsOPcu8R9rpdihNR5r822FAHBZ42wBa5XUa5RDVierD_tg@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