linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Thomas Richard <thomas.richard@bootlin.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	<linux-gpio@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linux-next:master] [gpio]  b31c68fd85: kernel-selftests.gpio.gpio-aggregator.sh.fail
Date: Sun, 28 Sep 2025 13:25:10 +0800	[thread overview]
Message-ID: <202509281206.a7334ae8-lkp@intel.com> (raw)



Hello,

kernel test robot noticed "kernel-selftests.gpio.gpio-aggregator.sh.fail" on:

commit: b31c68fd851e74526ad963362ea205eb97b9a710 ("gpio: aggregator: handle runtime registration of gpio_desc in gpiochip_fwd")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master

[test failed on linux-next/master 262858079afde6d367ce3db183c74d8a43a0e83f]

in testcase: kernel-selftests
version: kernel-selftests-x86_64-592a93fea16b-1_20250918
with following parameters:

	group: gpio



config: x86_64-rhel-9.4-kselftests
compiler: gcc-14
test machine: 36 threads 1 sockets Intel(R) Core(TM) i9-9980XE CPU @ 3.00GHz (Skylake) with 32G memory

(please refer to attached dmesg/kmsg for entire log/backtrace)



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 <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202509281206.a7334ae8-lkp@intel.com


# timeout set to 300
# selftests: gpio: gpio-aggregator.sh
# trap: SIGTERM: bad trap
# 1. GPIO aggregator creation/deletion
# 1.1. Creation/deletion via configfs
# 1.1.1. Minimum creation/deletion
# 1.1.2. Complex creation/deletion
# 1.1.3. Can't instantiate a chip without any line
# 1.1.4. Can't instantiate a chip with invalid configuration
# 1.1.5. Can't instantiate a chip asynchronously via deferred probe
# 1.1.6. Can't instantiate a chip with _sysfs prefix
# 1.2. Creation/deletion via sysfs
# 1.2.1. Minimum creation/deletion
# 1.2.2. Complex creation/deletion
# 1.2.3. Asynchronous creation with deferred probe
# 1.2.4. Can't instantiate a chip with invalid configuration
# 2. GPIO aggregator configuration
# 2.1. Configuring aggregators instantiated via configfs
# 2.1.1. While offline
# 2.1.1.1. Line can be added/removed
# 2.1.1.2. Line key can be modified
# 2.1.1.3. Line name can be modified
# 2.1.1.4. Line offset can be modified
# 2.1.1.5. Can re-enable a chip after valid reconfiguration
# 2.1.1.7. Can't re-enable a chip with invalid reconfiguration
# 2.1.2. While online
# 2.1.2.1. Can't add/remove line
# 2.1.2.2. Can't modify line key
# 2.1.2.3. Can't modify line name
# 2.1.2.4. Can't modify line offset
# 2.2. Configuring aggregators instantiated via sysfs
# 2.2.1. While online
# 2.2.1.1. Can toggle live
# 2.2.1.2. Can't add/remove line
# 2.2.1.3. Can't modify line key
# 2.2.1.4. Can't modify line name
# 2.2.1.5. Can't modify line offset
# 2.2.2. While waiting for deferred probe
# 2.2.2.1. Can't add/remove line despite live = 0
# 2.2.2.2. Can't modify line key
# 2.2.2.3. Can't modify line name
# 2.2.2.4. Can't modify line offset
# 2.2.2.5. Can't toggle live
# 2.2.3. While offline
# 2.2.3.1. Can't add/remove line despite live = 0
# 2.2.3.2. Line key can be modified
# 2.2.3.3. Line name can be modified
# 2.2.3.4. Line offset can be modified
# 2.2.3.5. Can re-enable a chip with valid reconfiguration
# 2.2.3.6. Can't re-enable a chip with invalid reconfiguration
# 3. Module unload
# 3.1. Can't unload module if there is at least one device created via configfs
# 3.2. Can unload module if there is no device created via configfs
# 4. GPIO forwarder functional
# 4.1. Forwarding set values
# 4.2. Forwarding set config
# incorrect value read from sysfs
# GPIO gpio-aggregator test FAIL
not ok 3 selftests: gpio: gpio-aggregator.sh # exit=1



The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250928/202509281206.a7334ae8-lkp@intel.com



-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


                 reply	other threads:[~2025-09-28  5:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202509281206.a7334ae8-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=thomas.richard@bootlin.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;
as well as URLs for NNTP newsgroup(s).