From: Thomas Gleixner <tglx@linutronix.de>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Anna-Maria Gleixner <anna-maria@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: Fix 80d20d35af1e ("nohz: Fix local_timer_softirq_pending()") may have revealed another problem
Date: Sat, 18 Aug 2018 13:26:47 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1808181323430.2151@nanos.tec.linutronix.de> (raw)
In-Reply-To: <8b93f213-fe67-f132-f3f5-5b17995ec63d@gmail.com>
On Thu, 16 Aug 2018, Heiner Kallweit wrote:
> Recently I started to get warning "NOHZ: local_softirq_pending 202" and
> I think it's related to mentioned commit (didn't bisect it yet).
> See log from suspending.
>
> I have no reason to think the fix is wrong, it may just have revealed
> another issue which existed before and was hidden by the bug.
Looks so. That seems to be related to CPU offlining. No idea yet...
> Rgds, Heiner
>
> [ 75.073353] random: crng init done
> [ 75.073402] random: 7 urandom warning(s) missed due to ratelimiting
> [ 78.619564] PM: suspend entry (deep)
> [ 78.619675] PM: Syncing filesystems ... done.
> [ 78.653684] Freezing user space processes ... (elapsed 0.002 seconds) done.
> [ 78.656094] OOM killer disabled.
> [ 78.656113] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
> [ 78.658177] Suspending console(s) (use no_console_suspend to debug)
> [ 78.663066] nuvoton-cir 00:07: disabled
> [ 78.671817] sd 0:0:0:0: [sda] Synchronizing SCSI cache
> [ 78.672210] sd 0:0:0:0: [sda] Stopping disk
> [ 78.786651] ACPI: Preparing to enter system sleep state S3
> [ 78.789613] PM: Saving platform NVS memory
> [ 78.789759] Disabling non-boot CPUs ...
> [ 78.805154] NOHZ: local_softirq_pending 202
> [ 78.805182] NOHZ: local_softirq_pending 202
> [ 78.807102] smpboot: CPU 1 is now offline
>
next prev parent reply other threads:[~2018-08-18 11:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 6:13 Fix 80d20d35af1e ("nohz: Fix local_timer_softirq_pending()") may have revealed another problem Heiner Kallweit
2018-08-18 11:26 ` Thomas Gleixner [this message]
2018-08-18 22:34 ` Heiner Kallweit
2018-08-24 4:12 ` Frederic Weisbecker
2018-08-24 5:59 ` Heiner Kallweit
2018-08-24 8:01 ` Thomas Gleixner
2018-08-24 14:30 ` Frederic Weisbecker
2018-08-24 17:06 ` Heiner Kallweit
2018-08-28 2:25 ` Frederic Weisbecker
2018-09-27 16:05 ` Thomas Gleixner
2018-09-28 13:18 ` Frederic Weisbecker
2018-09-28 20:35 ` Heiner Kallweit
2018-10-15 20:58 ` Heiner Kallweit
2018-12-24 21:11 ` Heiner Kallweit
2018-12-27 6:53 ` Frederic Weisbecker
2018-12-27 23:11 ` Heiner Kallweit
2018-12-28 1:31 ` Frederic Weisbecker
2018-12-28 6:34 ` Heiner Kallweit
2018-12-28 6:39 ` Heiner Kallweit
2019-01-09 22:20 ` Heiner Kallweit
2019-01-11 21:36 ` Frederic Weisbecker
2019-01-16 6:24 ` Frederic Weisbecker
2019-01-16 18:42 ` Heiner Kallweit
2019-01-24 19:37 ` Heiner Kallweit
2019-02-14 19:05 ` Heiner Kallweit
2019-02-14 21:47 ` Thomas Gleixner
2019-02-14 22:33 ` Heiner Kallweit
2019-02-15 0:31 ` Frederic Weisbecker
2019-02-16 9:14 ` Heiner Kallweit
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=alpine.DEB.2.21.1808181323430.2151@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=anna-maria@linutronix.de \
--cc=fweisbec@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.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 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).