Originally Posted by StringCheesian
But that patch doesn't look like a fix. In fact, it looks like it's probably the patch that introduced the warning in the first place. Which is good, it exposed a preexisting problem between the kernel and the nvidia driver. But it's definitely not a fix.
sorry, I of course meant the 4th
kernel/irq/manage.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
--- a/kernel/irq/manage.c 2008-06-30 12:28:58.000000000 -0700
+++ b/kernel/irq/manage.c 2008-06-30 12:46:54.000000000 -0700
@@ -539,6 +539,18 @@ int request_irq(unsigned int irq, irq_ha
struct irqaction *action;
+ * handle_IRQ_event() always ignores IRQF_DISABLED except for
+ * the _first_ irqaction (sigh). That can cause oopsing, but
+ * the behavior is classified as "will not fix" so we need to
+ * start nudging drivers away from using that idiom.
+ if ((irqflags & (IRQF_SHARED|IRQF_DISABLED))
+ == (IRQF_SHARED|IRQF_DISABLED))
+ pr_warning("IRQ %d/%s: IRQF_DISABLED is not "
+ "guaranteed on shared IRQs\n",
+ irq, devname);
* Lockdep wants atomic interrupt handlers: