From: Petr Mladek <pmladek@suse.com>
To: kernel test robot <oliver.sang@intel.com>
Cc: 0day robot <lkp@intel.com>, LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Laurence Oberman <loberman@redhat.com>,
Vincent Whitchurch <vincent.whitchurch@axis.com>,
Michal Hocko <mhocko@suse.com>
Subject: Re: 3cc3ef45b2: RIP:version_proc_show
Date: Tue, 5 Jan 2021 10:37:52 +0100 [thread overview]
Message-ID: <X/QzcCw5/3xD4lgC@alley> (raw)
In-Reply-To: <20210103150323.GE30643@xsang-OptiPlex-9020>
On Sun 2021-01-03 23:03:23, kernel test robot wrote:
>
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-9):
>
> commit: 3cc3ef45b202a39814f9ce979495d4cc130c2998 ("[PATCH v2 7/7] Test softlockup")
> url: https://github.com/0day-ci/linux/commits/Petr-Mladek/watchdog-softlockup-Report-overall-time-and-some-cleanup/20201211-004447
> base: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git a2f5ea9e314ba6778f885c805c921e9362ec0420
>
> in testcase: will-it-scale
> version: will-it-scale-x86_64-b695a1b-1_20201217
> with following parameters:
>
> nr_task: 16
> mode: thread
> test: dup1
> cpufreq_governor: performance
> ucode: 0x2006a08
>
> test-description: Will It Scale takes a testcase and runs it from 1 through to n parallel copies to see if the testcase will scale. It builds both a process and threads based test in order to see any differences between the two.
> test-url: https://github.com/antonblanchard/will-it-scale
>
>
> on test machine: 104 threads Skylake with 192G memory
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
> +----------------+------------+------------+
> | | 36cc821a5c | 3cc3ef45b2 |
> +----------------+------------+------------+
> | boot_successes | 7 | 0 |
> +----------------+------------+------------+
>
>
> If you fix the issue, kindly add following tag
> Reported-by: kernel test robot <oliver.sang@intel.com>
>
>
> [ 71.563905] watchdog: BUG: soft lockup - CPU#1 stuck for 26s! [perf:2556]
> [ 71.567713] watchdog: BUG: soft lockup - CPU#89 stuck for 26s! [perf:2463]
> [ 71.812209] CPU: 1 PID: 2556 Comm: perf Not tainted 5.10.0-rc7-g3cc3ef45b202 #1
> [ 71.814904] acpi_power_meter ip_tables
> [ 71.817550] Hardware name: Intel Corporation S2600BT/S2600BT, BIOS SE5C620.86B.1D.01.0147.121320181755 12/13/2018
> [ 71.817559] RIP: 0010:version_proc_show+0x2f/0x6a
JFYI, it works as expected.
This patch is not intended for upstream. It allows to test the
rest of the patchset easily. And it causes exactly the above mentioned
softlockup.
Best Regards,
Petr
prev parent reply other threads:[~2021-01-05 9:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 16:00 [PATCH v2 0/7] watchdog/softlockup: Report overall time and some cleanup Petr Mladek
2020-12-10 16:00 ` [PATCH v2 1/7] watchdog: Rename __touch_watchdog() to a better descriptive name Petr Mladek
2020-12-10 16:00 ` [PATCH v2 2/7] watchdog: Explicitly update timestamp when reporting softlockup Petr Mladek
2020-12-10 16:00 ` [PATCH v2 3/7] watchdog/softlockup: Report the overall time of softlockups Petr Mladek
2020-12-10 16:00 ` [PATCH v2 4/7] watchdog/softlockup: Remove logic that tried to prevent repeated reports Petr Mladek
2020-12-10 16:00 ` [PATCH v2 5/7] watchdog: Fix barriers when printing backtraces from all CPUs Petr Mladek
2020-12-10 16:00 ` [PATCH v2 6/7] watchdog: Cleanup handling of false positives Petr Mladek
2020-12-10 16:00 ` [PATCH v2 7/7] Test softlockup Petr Mladek
2021-01-03 15:03 ` 3cc3ef45b2: RIP:version_proc_show kernel test robot
2021-01-05 9:37 ` Petr Mladek [this message]
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=X/QzcCw5/3xD4lgC@alley \
--to=pmladek@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=loberman@redhat.com \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=vincent.whitchurch@axis.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).