linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yujie Liu <yujie.liu@intel.com>
To: Baoquan He <bhe@redhat.com>
Cc: kernel test robot <lkp@intel.com>, Paul Gazzillo <paul@pgazz.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 14:22:02 +0800	[thread overview]
Message-ID: <ZdRFCu3Uohd6wtml@yujie-X299> (raw)
In-Reply-To: <ZdL+sSSFghXttSqR@MiWiFi-R3L-srv>

Hi Baoquan,

On Mon, Feb 19, 2024 at 03:09:37PM +0800, 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?

It is not necessary to install kmax to reproduce the issue. You can
choose either 1 or 2 to reproduce it. We will update the wording to make
this clearer.

If kmax installation failure is blocking method 1, could you please try
method 2 to see if the issue can be reproduced?

$ wget https://download.01.org/0day-ci/archive/20240217/202402171431.MzqHz3g2-lkp@intel.com/config -O .config
$ make ARCH=powerpc olddefconfig

WARNING: unmet direct dependencies detected for CRASH_DUMP
  Depends on [n]: ARCH_SUPPORTS_CRASH_DUMP [=y] && KEXEC_CORE [=n]
  Selected by [y]:
  - FA_DUMP [=y] && PPC64 [=y] && (PPC_RTAS [=y] || PPC_POWERNV [=y])

Best Regards,
Yujie

> 
> -------
>  # 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
> -------
> 
> 
> ======
>       kextractors/kextractor-3.19/bconf.tab.c: In function ‘enter_if_branch’:
>       kextractors/kextractor-3.19/bconf.tab.c:150:5: error: implicit declaration of function ‘bconferror’; did you mean ‘ferror’? [-Wimplicit-function-declaration]
>         150 |     bconferror("MAX_IF_DEPTH exceeded");
>             |     ^~~~~~~~~~
>             |     ferror
>       kextractors/kextractor-3.19/bconf.tab.c: At top level:
>       kextractors/kextractor-3.19/bconf.tab.c:2064:1: error: return type defaults to ‘int’ [-Wimplicit-int]
>        2064 | bconf_parse(char *file)
>             | ^~~~~~~~~~~
>       kextractors/kextractor-3.19/bconf.tab.c:2107:1: error: return type defaults to ‘int’ [-Wimplicit-int]
>        2107 | bconf_test_lexer(char *file)
>             | ^~~~~~~~~~~~~~~~
>       kextractors/kextractor-3.19/bconf.tab.c:2119:1: error: return type defaults to ‘int’ [-Wimplicit-int]
>        2119 | bconferror(char *msg) {
>             | ^~~~~~~~~~
>       error: command '/usr/lib64/ccache/gcc' failed with exit code 1
>       [end of output]
>   
>   note: This error originates from a subprocess, and is likely not a problem with pip.
>   ERROR: Failed building wheel for kmax
> Failed to build kmax
> ERROR: Could not build wheels for kmax, which is required to install pyproject.toml-based projects
> =================
> 
> 
> > 
> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > the same patch/commit), kindly add following tags
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202402171431.MzqHz3g2-lkp@intel.com/
> > 
> > kismet warnings: (new ones prefixed by >>)
> > >> kismet: WARNING: unmet direct dependencies detected for CRASH_DUMP when selected by FA_DUMP
> > 
> > -- 
> > 0-DAY CI Kernel Test Service
> > https://github.com/intel/lkp-tests/wiki
> > 
> 
> 


  parent reply	other threads:[~2024-02-20  6:29 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
2024-02-20  6:22   ` Yujie Liu [this message]
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=ZdRFCu3Uohd6wtml@yujie-X299 \
    --to=yujie.liu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --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