From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: lkp@lists.01.org
Subject: Re: [x86/platform] d7109fe3a0: kernel-selftests.gpio.gpio-mockup.sh.fail
Date: Wed, 06 Oct 2021 18:54:41 +0300 [thread overview]
Message-ID: <YV3GwQ68KssgPUHW@smile.fi.intel.com> (raw)
In-Reply-To: <YT4YaHTiaDibkzfK@smile.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2214 bytes --]
Change Bart's address accordingly to last MAINTAINER update.
On Sun, Sep 12, 2021 at 06:10:32PM +0300, Andy Shevchenko wrote:
> +Cc: Bart
>
> On Sun, Sep 12, 2021 at 11:01:58PM +0800, kernel test robot wrote:
> > Greeting,
> >
> > FYI, we noticed the following commit (built with gcc-9):
>
> Thanks for the report.
>
> First of all, please teach your bot to cut up things a bit. ~13k lines
> is something not expected here, really!
>
> > commit: d7109fe3a0991a0f7b4ac099b78c908e3b619787 ("x86/platform: Increase maximum GPIO number for X86_64")
> > https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git x86/urgent
> >
> >
> > in testcase: kernel-selftests
> > version: kernel-selftests-x86_64-d0cba0d1-1_20210907
> > with following parameters:
> >
> > group: group-01
> > ucode: 0xe2
> >
> > test-description: The kernel contains a set of "self tests" under the tools/testing/selftests/ directory. These are intended to be small unit tests to exercise individual code paths in the kernel.
> > test-url: https://www.kernel.org/doc/Documentation/kselftest.txt
> >
> >
> > on test machine: 4 threads Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz with 32G memory
> >
> > caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
> >
> >
> > If you fix the issue, kindly add following tag
> > Reported-by: kernel test robot <oliver.sang@intel.com>
>
> > 2021-09-10 00:58:57 make run_tests -C gpio
> > make: Entering directory '/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-d7109fe3a0991a0f7b4ac099b78c908e3b619787/tools/testing/selftests/gpio'
> > TAP version 13
> > 1..1
> > # selftests: gpio: gpio-mockup.sh
> > # 1. Module load tests
> > # 1.1. dynamic allocation of gpio
> > # 2. Module load error tests
> > # 2.1 gpio overflow
> > # test failed: unexpected chip - gpiochip0
> > # GPIO gpio-mockup test FAIL
> > not ok 1 selftests: gpio: gpio-mockup.sh # exit=1
>
> Test does the overflow check with 1024 as a parameter and comments deliberately
> tells about limitation. What it should do instead is to use the actual GPIO
> number from the kernel configuration.
--
With Best Regards,
Andy Shevchenko
WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: kernel test robot <oliver.sang@intel.com>,
Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linus Walleij <linus.walleij@linaro.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, lkp@lists.01.org, lkp@intel.com
Subject: Re: [x86/platform] d7109fe3a0: kernel-selftests.gpio.gpio-mockup.sh.fail
Date: Wed, 6 Oct 2021 18:54:41 +0300 [thread overview]
Message-ID: <YV3GwQ68KssgPUHW@smile.fi.intel.com> (raw)
In-Reply-To: <YT4YaHTiaDibkzfK@smile.fi.intel.com>
Change Bart's address accordingly to last MAINTAINER update.
On Sun, Sep 12, 2021 at 06:10:32PM +0300, Andy Shevchenko wrote:
> +Cc: Bart
>
> On Sun, Sep 12, 2021 at 11:01:58PM +0800, kernel test robot wrote:
> > Greeting,
> >
> > FYI, we noticed the following commit (built with gcc-9):
>
> Thanks for the report.
>
> First of all, please teach your bot to cut up things a bit. ~13k lines
> is something not expected here, really!
>
> > commit: d7109fe3a0991a0f7b4ac099b78c908e3b619787 ("x86/platform: Increase maximum GPIO number for X86_64")
> > https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git x86/urgent
> >
> >
> > in testcase: kernel-selftests
> > version: kernel-selftests-x86_64-d0cba0d1-1_20210907
> > with following parameters:
> >
> > group: group-01
> > ucode: 0xe2
> >
> > test-description: The kernel contains a set of "self tests" under the tools/testing/selftests/ directory. These are intended to be small unit tests to exercise individual code paths in the kernel.
> > test-url: https://www.kernel.org/doc/Documentation/kselftest.txt
> >
> >
> > on test machine: 4 threads Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz with 32G memory
> >
> > caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
> >
> >
> > If you fix the issue, kindly add following tag
> > Reported-by: kernel test robot <oliver.sang@intel.com>
>
> > 2021-09-10 00:58:57 make run_tests -C gpio
> > make: Entering directory '/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-d7109fe3a0991a0f7b4ac099b78c908e3b619787/tools/testing/selftests/gpio'
> > TAP version 13
> > 1..1
> > # selftests: gpio: gpio-mockup.sh
> > # 1. Module load tests
> > # 1.1. dynamic allocation of gpio
> > # 2. Module load error tests
> > # 2.1 gpio overflow
> > # test failed: unexpected chip - gpiochip0
> > # GPIO gpio-mockup test FAIL
> > not ok 1 selftests: gpio: gpio-mockup.sh # exit=1
>
> Test does the overflow check with 1024 as a parameter and comments deliberately
> tells about limitation. What it should do instead is to use the actual GPIO
> number from the kernel configuration.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-10-06 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-12 15:01 [x86/platform] d7109fe3a0: kernel-selftests.gpio.gpio-mockup.sh.fail kernel test robot
2021-09-12 15:01 ` kernel test robot
2021-09-12 15:10 ` Andy Shevchenko
2021-09-12 15:10 ` Andy Shevchenko
2021-10-06 15:54 ` Andy Shevchenko [this message]
2021-10-06 15:54 ` Andy Shevchenko
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=YV3GwQ68KssgPUHW@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=lkp@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.