From: Yinghai Lu <yinghai@kernel.org>
To: Eric Paris <eparis@redhat.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com
Subject: Re: irq_desc_lock_class is held when it is freed
Date: Sat, 31 Jan 2009 14:50:07 -0800 [thread overview]
Message-ID: <4984D59F.4030700@kernel.org> (raw)
In-Reply-To: <1233437601.11984.41.camel@localhost.localdomain>
Eric Paris wrote:
> I have an hp dl785g5 which is unable to successfully run
> 2.6.29-0.66.rc3.fc11.x86_64 or 2.6.29-rc2-next-20090126. During bootup
> (early in userspace daemons starting) I get the below BUG, which quickly
> renders the machine dead. I assume it is because sparse_irq_lock never
> gets released when the BUG kills that task. But maybe it dies for some
> other reason, but the machine is dead, gotta hit the vitual power
> button.
>
> setting CONFIG_NUMA_MIGRATE_IRQ_DESC=n allowed me to successfully boot
> the linux-next kernel. 2.6.28 booted and worked fine (although it
> doesn't have this config option, so that isn't surprising.)
>
> attached you will find the linux-next config and dmesg output from the
> machine in question when booted using linux-next WITHOUT the
> MIGRATE_IRQ_DESC. The only difference between the working and broken
> config is if CONFIG_NUMA_MIGRATE_IRQ_DESC is set or not.
>
> Please if there is anything I can collect, test, or do, don't hesitate
> to let me know.
>
it seems there is some merge problem... also there could be another problem...
please check
diff --git a/arch/x86/kernel/io_apic.c b/arch/x86/kernel/io_apic.c
index 6c02c25..610ce0a 100644
--- a/arch/x86/kernel/io_apic.c
+++ b/arch/x86/kernel/io_apic.c
@@ -2511,14 +2511,15 @@ static void irq_complete_move(struct irq_desc **descp)
vector = ~get_irq_regs()->orig_ax;
me = smp_processor_id();
+
+ if (vector == cfg->vector && cpumask_test_cpu(me, cfg->domain)) {
#ifdef CONFIG_NUMA_MIGRATE_IRQ_DESC
*descp = desc = move_irq_desc(desc, me);
/* get the new one */
cfg = desc->chip_data;
#endif
-
- if (vector == cfg->vector && cpumask_test_cpu(me, cfg->domain))
send_cleanup_vector(cfg);
+ }
}
#else
static inline void irq_complete_move(struct irq_desc **descp) {}
next prev parent reply other threads:[~2009-01-31 22:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 21:33 irq_desc_lock_class is held when it is freed Eric Paris
2009-01-31 22:50 ` Yinghai Lu [this message]
2009-02-01 1:05 ` Eric Paris
2009-02-01 1:19 ` Yinghai Lu
2009-02-01 1:55 ` Eric Paris
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=4984D59F.4030700@kernel.org \
--to=yinghai@kernel.org \
--cc=eparis@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=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