he LSB is set
it enables the task. So I'm guessing that is what gets things moving
again when the freeze happens.
My best guess is this is a race condition between the driver and the
dma controller. Is there any risk to just calling bcom_enable(tsk).
Maybe after
PU: MPC5200B v2.2, Core v1.4 at 396 MHz
Bus 132 MHz, IPB 132 MHz, PCI 33 MHz
Joey Nelson
On Wed, Feb 1, 2012 at 6:33 PM, Joey Nelson wrote:
> First I think the spin_locks in the irq handlers should be
> spin_lock_irqsave(), because the same lock is used in multiple irq
> handlers
;t think I've seen a
delayed packet larger than 1k.
@@ -382,6 +414,8 @@
dev_kfree_skb_irq(skb);
}
spin_unlock(&priv->lock);
+ js_irq_timestamps[js_irq_idx] = get_tbl();
+ js_irq_idx = (js_irq_idx+1 == TS_COUNT)? 0 : js_irq_idx+1;
netif_wake_queue(dev);
@@ -409,6 +443,7 @@
heets)
Thanks in advance.
Joey Nelson
j...@joescan.com
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
