* Marcin Ślusarz <[email protected]> wrote:
> Ok, I've bisected this problem and found that this patch broke my NIC:
>
> 76d2160147f43f982dfe881404cfde9fd0a9da21 is first bad commit
> commit 76d2160147f43f982dfe881404cfde9fd0a9da21
> Author: Ingo Molnar <[email protected]>
> Date: Fri Feb 16 01:28:24 2007 -0800
>
> [PATCH] genirq: do not mask interrupts by default
thanks for tracking it down! Could you try the patch below (ontop an
otherwise unmodified kernel)? This tests the theory whether the problem
is related to the disable_irq_nosync() call in the ne2k driver's xmit
path. Does this solve the hangs too?
Ingo
Index: linux/kernel/irq/manage.c
===================================================================
--- linux.orig/kernel/irq/manage.c
+++ linux/kernel/irq/manage.c
@@ -102,7 +102,19 @@ void disable_irq_nosync(unsigned int irq
spin_lock_irqsave(&desc->lock, flags);
if (!desc->depth++) {
desc->status |= IRQ_DISABLED;
- desc->chip->disable(irq);
+ /*
+ * the _nosync variant of irq-disable suggests that the
+ * caller is not worried about concurrency but about the
+ * ordering of the irq flow itself. (such as hardware
+ * getting confused about certain, normally valid irq
+ * handling sequences.) So if the default disable handler
+ * is in place then try the more conservative masking
+ * instead:
+ */
+ if (desc->chip->disable == default_disable && desc->chip->mask)
+ desc->chip->mask(irq);
+ else
+ desc->chip->disable(irq);
}
spin_unlock_irqrestore(&desc->lock, flags);
}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
