From: tglx@linutronix.de (Thomas Gleixner)
Subject: A kernel warning when entering suspend
Date: Thu, 4 Apr 2019 13:14:27 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1904041312480.1685@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20190404085524.GA24927@ming.t460p>
On Thu, 4 Apr 2019, Ming Lei wrote:
> On Thu, Apr 04, 2019@08:23:59AM +0000, fin4478 fin4478 wrote:
> > Hi,
> >
> > I do not use suspend/resume but noticed this kernel warning when testing it. This warning is present in earlier kernels too. My system works fine after resume.
> > If there is a patch to fix this, I can test it.
> >
> > [ 53.403033] PM: suspend entry (deep)
> > [ 53.403034] PM: Syncing filesystems ... done.
> > [ 53.404775] Freezing user space processes ... (elapsed 0.001 seconds) done.
> > [ 53.405972] OOM killer disabled.
> > [ 53.405973] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
> > [ 53.407036] printk: Suspending console(s) (use no_console_suspend to debug)
> > [ 53.407491] ACPI Debug: "RRIO"
> > [ 53.407505] serial 00:03: disabled
> > [ 53.407560] r8169 0000:07:00.0 enp7s0: Link is Down
> > [ 53.415042] sd 5:0:0:0: [sda] Synchronizing SCSI cache
> > [ 53.415065] sd 5:0:0:0: [sda] Stopping disk
> > [ 53.428943] WARNING: CPU: 10 PID: 3127 at kernel/irq/chip.c:210 irq_startup+0xd6/0xe0
>
> Looks the 'WARN_ON_ONCE(force)' in irq_startup() is a bit too strict.
Why?
> irq_build_affinity_masks() doesn't guarantee that each IRQ's affinity
> can include at least one online CPU.
Then why is it tried to start up an interrupt which has no online cpu in
the mask? I'm missing context obviously.
Thanks,
tglx
next prev parent reply other threads:[~2019-04-04 11:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 8:23 A kernel warning when entering suspend fin4478 fin4478
2019-04-04 8:55 ` Ming Lei
2019-04-04 11:14 ` Thomas Gleixner [this message]
2019-12-23 14:52 ` Maxim Levitsky
2020-01-16 13:58 ` Maxim Levitsky
2019-04-04 15:37 ` Dongli Zhang
2019-04-04 16:18 ` Thomas Gleixner
2019-04-04 22:19 ` Ming Lei
2019-04-04 22:29 ` Keith Busch
2019-04-04 22:50 ` Ming Lei
2019-04-05 11:35 ` Thomas Gleixner
2019-04-06 14:29 ` Dongli Zhang
2019-04-06 15:31 ` Dongli Zhang
2019-04-06 16:12 ` fin4478 fin4478
2019-04-08 15:07 ` Keith Busch
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.1904041312480.1685@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
/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).