From: Baoquan He <bhe@redhat.com>
To: Paul Gazzillo <paul@pgazz.com>
Cc: kernel test robot <lkp@intel.com>,
Necip Fazil Yildiran <fazilyildiran@gmail.com>,
oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [akpm-mm:mm-unstable 82/320] kismet: WARNING: unmet direct dependencies detected for CRASH_DUMP when selected by FA_DUMP
Date: Tue, 20 Feb 2024 13:02:29 +0800 [thread overview]
Message-ID: <ZdQyZYQY4XR8V4in@MiWiFi-R3L-srv> (raw)
In-Reply-To: <ZdNZybp3lMM1+I+V@MiWiFi-R3L-srv>
On 02/19/24 at 09:38pm, Baoquan He wrote:
> On 02/19/24 at 08:21am, Paul Gazzillo wrote:
> > On 02/19/2024, Baoquan He wrote:
> > > On 02/17/24 at 02:48pm, kernel test robot wrote:
> > > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
> > > > head: 9951769060d8f5eb001acaca67c1439d2cfe1c6b
> > > > commit: a5af0b602e5ecb379fd2470669654a6abe7e97a2 [82/320] crash: clean up kdump related config items
> > > > config: powerpc-kismet-CONFIG_CRASH_DUMP-CONFIG_FA_DUMP-0-0 (https://download.01.org/0day-ci/archive/20240217/202402171431.MzqHz3g2-lkp@intel.com/config)
> > > > reproduce: (https://download.01.org/0day-ci/archive/20240217/202402171431.MzqHz3g2-lkp@intel.com/reproduce)
> > >
> > > When I tried the step 1 of reproducer, I got failure on installing the
> > > kmax. Is there other ways I can reproduce the issue? Or have you tested
> > > the latest linux-next/master because there's some udpate about the
> > > config items change?
> > >
> > > -------
> > > # 1. reproduce by kismet
> > > # install kmax per https://github.com/paulgazz/kmax/blob/master/README.md
> > > kismet --linux-ksrc=linux --selectees CONFIG_CRASH_DUMP --selectors CONFIG_FA_DUMP -a=powerpc
> > > -------
> > >
> >
> > I am able to install on a fairly fresh x86 ubuntu 23.10 installation.
> > Could you let me know the platform and OS you are building on?
>
> Thanks, I took the building on fedora 39.
Forgot saying it's on x86_64. I usually run lkp testing on x86.
next prev parent reply other threads:[~2024-02-20 5:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 6:48 kernel test robot
2024-02-19 7:09 ` Baoquan He
2024-02-19 13:21 ` Paul Gazzillo
2024-02-19 13:38 ` Baoquan He
2024-02-20 5:02 ` Baoquan He [this message]
2024-02-20 6:22 ` Yujie Liu
2024-02-20 13:05 ` Baoquan He
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=ZdQyZYQY4XR8V4in@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=fazilyildiran@gmail.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@pgazz.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