From: kernel test robot <oliver.sang@intel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Masami Hiramatsu <mhiramat@kernel.org>, <oliver.sang@intel.com>
Subject: [linus:master] [drivers] dc1771f718: kernel-selftests-bpf.hid.hidraw.fail
Date: Fri, 25 Jul 2025 17:40:42 +0800 [thread overview]
Message-ID: <202507250945.a36cd041-lkp@intel.com> (raw)
Hello,
just FYI, in our tests, after this revert patch, some tests randomly failed
332ec18d57de2f77 dc1771f718548f7d4b93991b174
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:30 70% 21:33 kernel-selftests-bpf.hid.hidraw.fail
:30 20% 6:33 kernel-selftests-bpf.hid.hidraw.hidraw.poll_revoked.fail
:30 43% 13:33 kernel-selftests-bpf.hid.hidraw.hidraw.raw_event.fail
:30 30% 9:33 kernel-selftests-bpf.hid.hidraw.hidraw.raw_event_revoked.fail
kernel test robot noticed "kernel-selftests-bpf.hid.hidraw.fail" on:
commit: dc1771f718548f7d4b93991b174c6e7b5e1ba410 ("Revert "drivers: core: synchronize really_probe() and dev_uevent()"")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 89be9a83ccf1f88522317ce02f854f30d6115c41]
[test failed on linux-next/master d086c886ceb9f59dea6c3a9dae7eb89e780a20c9]
in testcase: kernel-selftests-bpf
version:
with following parameters:
group: hid
config: x86_64-rhel-9.4-bpf
compiler: gcc-12
test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (Kaby Lake) 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/202507250945.a36cd041-lkp@intel.com
# timeout set to 200
# selftests: hid: hidraw
# TAP version 13
# 1..6
# # Starting 6 tests from 1 test cases.
# # RUN hidraw.test_create_uhid ...
# # OK hidraw.test_create_uhid
# ok 1 hidraw.test_create_uhid
# # RUN hidraw.raw_event ...
# # OK hidraw.raw_event
# ok 2 hidraw.raw_event
# # RUN hidraw.raw_event_revoked ...
# # OK hidraw.raw_event_revoked
# ok 3 hidraw.raw_event_revoked
# # RUN hidraw.ioctl_revoked ...
# # OK hidraw.ioctl_revoked
# ok 4 hidraw.ioctl_revoked
# # RUN hidraw.poll_revoked ...
# # hidraw.c:152:poll_revoked:Expected ready (0) == 1 (1)
# # hidraw.c:152:poll_revoked:poll return value
# # poll_revoked: Test terminated by assertion
# # FAIL hidraw.poll_revoked
# not ok 5 hidraw.poll_revoked
# # RUN hidraw.write_event_revoked ...
# # OK hidraw.write_event_revoked
# ok 6 hidraw.write_event_revoked
# # FAILED: 5 / 6 tests passed.
# # Totals: pass:5 fail:1 xfail:0 xpass:0 skip:0 error:0
not ok 2 selftests: hid: hidraw # exit=1
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250725/202507250945.a36cd041-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-07-25 9:41 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=202507250945.a36cd041-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mhiramat@kernel.org \
--cc=oe-lkp@lists.linux.dev \
/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
all inboxes | Powered by JetHome®