From: Thomas Gleixner <tglx@linutronix.de>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Jiang Liu <jiang.liu@linux.intel.com>,
Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [-next] !irqd_can_balance() WARNINGs at irq_move_masked_irq()
Date: Fri, 19 Jun 2015 11:25:21 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1506191104040.4107@nanos> (raw)
In-Reply-To: <20150619071123.GA511@swordfish>
On Fri, 19 Jun 2015, Sergey Senozhatsky wrote:
> [ 0.412291] WARNING: CPU: 0 PID: 0 at kernel/irq/migration.c:21 irq_move_masked_irq+0x57/0xc4()
> [ 0.412371] Can't balance irq 0 [edge]
Yuck.
> Do you guys want to replace WAN_ON() with WARN_ONCE(), perhaps? This, of course,
> doesn't fix anything; but at least one can boot the system. (not really a patch,
> just an idea).
Indeed. We really want to clear the move pending bit before the can
balance check. Patch below. But that does not explain why this happens
in the first place.
Can you please send me a full dmesg, kernel config and output of
/proc/interrupts ? (Private mail is fine, or upload it to some place)
Thanks,
tglx
---
diff --git a/kernel/irq/migration.c b/kernel/irq/migration.c
index dd203e276b07..8cf8c24afaab 100644
--- a/kernel/irq/migration.c
+++ b/kernel/irq/migration.c
@@ -12,16 +12,19 @@ void irq_move_masked_irq(struct irq_data *idata)
if (likely(!irqd_is_setaffinity_pending(&desc->irq_data)))
return;
+ irqd_clr_move_pending(&desc->irq_data);
+
/*
* Paranoia: cpu-local interrupts shouldn't be calling in here anyway.
*/
if (!irqd_can_balance(&desc->irq_data)) {
- WARN_ON(1);
+ pr_warn("Cannot move irq %d: %s\n",
+ desc->irq_data.irq,
+ irqd_is_per_cpu(&desc->irq_data) ?
+ "per cpu" : "balancing disabled");
return;
}
- irqd_clr_move_pending(&desc->irq_data);
-
if (unlikely(cpumask_empty(desc->pending_mask)))
return;
next prev parent reply other threads:[~2015-06-19 9:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 7:11 Sergey Senozhatsky
2015-06-19 9:25 ` Thomas Gleixner [this message]
2015-06-19 12:21 ` Thomas Gleixner
2015-06-19 13:11 ` Sergey Senozhatsky
2015-06-19 16:09 ` Jiang Liu
2015-06-19 16:12 ` Jiang Liu
2015-06-19 16:15 ` Thomas Gleixner
2015-06-19 16:21 ` Jiang Liu
2015-06-19 16:30 ` Thomas Gleixner
2015-06-19 16:47 ` Jiang Liu
2015-06-19 17:14 ` Sergey Senozhatsky
2015-06-20 4:32 ` Sergey Senozhatsky
2015-06-20 10:07 ` [tip:x86/apic] x86/hpet: Check for irq== 0 when allocating hpet MSI interrupts tip-bot for Jiang Liu
2015-06-19 16:23 ` [-next] !irqd_can_balance() WARNINGs at irq_move_masked_irq() Sergey Senozhatsky
2015-06-20 4:31 ` Sergey Senozhatsky
2015-06-20 7:52 ` Thomas Gleixner
2015-06-20 7:57 ` Sergey Senozhatsky
2015-06-20 8:13 ` Thomas Gleixner
2015-06-20 8:27 ` Sergey Senozhatsky
2015-06-20 9:12 ` Thomas Gleixner
2015-06-20 17:53 ` Sergey Senozhatsky
2015-06-21 4:15 ` Sergey Senozhatsky
2015-06-21 14:37 ` Thomas Gleixner
2015-06-21 14:43 ` [tip:x86/apic] x86/hpet: Use proper hpet device number for MSI allocation tip-bot for Thomas Gleixner
2015-06-20 17:20 ` [tip:irq/core] genirq: Remove bogus restriction in irq_move_mask_irq() tip-bot for Thomas Gleixner
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.11.1506191104040.4107@nanos \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=jiang.liu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.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
all inboxes | Powered by JetHome®