From: Thomas Gleixner <tglx@linutronix.de>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>, x86@kernel.org
Subject: Re: 4.15: WARNING: CPU: 3 PID: 258 at kernel/irq/chip.c:244 __irq_startup+0x80/0x100
Date: Tue, 30 Jan 2018 19:36:32 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1801301935410.1797@nanos> (raw)
In-Reply-To: <alpine.DEB.2.20.1801291732092.1849@nanos>
On Mon, 29 Jan 2018, Thomas Gleixner wrote:
> On Mon, 29 Jan 2018, Meelis Roos wrote:
>
> > Upgraded some of my older machines to v4.15 today. On a quad P3 HP
> > NetServer,
>
> Your supply of vintage hardware is amazing.
>
> > I get a bootup warning at kernel/irq/chip.c:244
> > __irq_startup+0x80/0x100 (full dmesg below). It seems it was there
> > before but I did not notice it.
>
> > [ 11.180167] WARNING: CPU: 3 PID: 258 at kernel/irq/chip.c:244 __irq_startup+0x80/0x100
> > [ 11.180508] EIP: __irq_startup+0x80/0x100
> > [ 11.180912] irq_startup+0x7e/0x170
> > [ 11.180977] probe_irq_on+0x128/0x2b0
> > [ 11.181054] parport_irq_probe.constprop.18+0x8d/0x1af [parport_pc]
> > [ 11.181127] parport_pc_probe_port+0xf11/0x1260 [parport_pc]
> > [ 11.181202] parport_pc_init+0x78a/0xf10 [parport_pc]
> > [ 11.181273] ? parport_parse_param.constprop.16+0xf0/0xf0 [parport_pc]
> > [ 11.181338] do_one_initcall+0x45/0x1e0
>
> Bah, that's the irq probing code, which I obviously missed... I'll have a look.
Does the patch below fix the issue for you?
Thanks,
tglx
8<----------------
diff --git a/kernel/irq/autoprobe.c b/kernel/irq/autoprobe.c
index 4e8089b319ae..8c82ea26e837 100644
--- a/kernel/irq/autoprobe.c
+++ b/kernel/irq/autoprobe.c
@@ -71,7 +71,7 @@ unsigned long probe_irq_on(void)
raw_spin_lock_irq(&desc->lock);
if (!desc->action && irq_settings_can_probe(desc)) {
desc->istate |= IRQS_AUTODETECT | IRQS_WAITING;
- if (irq_startup(desc, IRQ_NORESEND, IRQ_START_FORCE))
+ if (irq_activate_and_startup(desc, IRQ_NORESEND))
desc->istate |= IRQS_PENDING;
}
raw_spin_unlock_irq(&desc->lock);
next prev parent reply other threads:[~2018-01-30 18:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 16:20 Meelis Roos
2018-01-29 16:35 ` Thomas Gleixner
2018-01-30 18:36 ` Thomas Gleixner [this message]
2018-01-31 7:21 ` Meelis Roos
2018-01-31 7:58 ` Thomas Gleixner
2018-01-31 8:09 ` Ingo Molnar
2018-01-31 11:23 ` Meelis Roos
2018-01-31 11:59 ` Ingo Molnar
2018-01-31 9:54 ` [tip:irq/urgent] genirq: Make legacy autoprobing work again tip-bot for Thomas Gleixner
2018-02-01 8:15 ` Geert Uytterhoeven
2018-02-01 9:56 ` Thomas Gleixner
2018-02-01 11:35 ` Arnd Bergmann
2018-02-01 9:58 ` tip-bot for Thomas Gleixner
2018-02-01 10:12 ` 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.20.1801301935410.1797@nanos \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=x86@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
all inboxes | Powered by JetHome®