From: Alex Shi <seakeel@gmail.com>
To: Oliver Sang <oliver.sang@intel.com>
Cc: Alex Shi <alexs@kernel.org>,
oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [alexshi:mmunstable2] 934c05f8c5: BUG:unable_to_handle_page_fault_for_address
Date: Tue, 23 Jul 2024 16:23:00 +0800 [thread overview]
Message-ID: <bd36db00-5464-4eb5-adb1-0ddfd3be1cfa@gmail.com> (raw)
In-Reply-To: <Zp8h/ZZTQ0lwmcJa@xsang-OptiPlex-9020>
On 7/23/24 11:22 AM, Oliver Sang wrote:
> hi, Alex,
>
> On Tue, Jul 23, 2024 at 09:58:25AM +0800, Alex Shi wrote:
>>
>> On 7/23/24 9:05 AM, kernel test robot wrote:
>>> hi, Alex Shi,
>>>
>>> we noticed there is a mmunstable3 branch now, but there is no same title patch
>>> there. not sure if this report is still useful, below report just FYI.
>> Hi Oliver,
>>
>> Thanks a lot for your testing and founding on my unreleased code branch!
>> The problem should be resolved on my latest code yesterday.
>> But multiple archs maybe still are fragile in the branch. Are there bootable in virtual machine, like arm, s390, etc?
> we did boot test in vm, but only for x86_64 or i386.
>
> you may notice we also send another report
> "[alexshi:mmunstable3] [mm/memory] f6ba7ce983: kernel_BUG_at_mm/page_alloc.c"
this problem was fixed too. Anyway thanks a lot notice me of this.
>
> for both commit, we made some further check and cofirmed they cannot boot
> successfully on both vm/bm, again, we only test x86_64/i386 for now.
Thanks a lot for the info!
Alex
next prev parent reply other threads:[~2024-07-23 8:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 1:05 kernel test robot
2024-07-23 1:58 ` Alex Shi
2024-07-23 3:22 ` Oliver Sang
2024-07-23 8:23 ` Alex Shi [this message]
2024-07-25 13:55 ` Oliver Sang
2024-07-26 6:11 ` Alex Shi
2024-07-26 7:38 ` Oliver Sang
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=bd36db00-5464-4eb5-adb1-0ddfd3be1cfa@gmail.com \
--to=seakeel@gmail.com \
--cc=alexs@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
/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