Some versions of the spider have a firmware bug, where the
RX ring sequencer goes crazy when the RX RAM on the device
fills up. Appearently the only viable wrkaround is a soft
reset of the card.

Signed-off-by: Linas Vepstas <[EMAIL PROTECTED]>

----
 drivers/net/spider_net.c |   14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

Index: netdev-2.6/drivers/net/spider_net.c
===================================================================
--- netdev-2.6.orig/drivers/net/spider_net.c    2007-05-22 18:03:37.000000000 
-0500
+++ netdev-2.6/drivers/net/spider_net.c 2007-05-22 18:03:39.000000000 -0500
@@ -1506,11 +1506,17 @@ spider_net_handle_error_irq(struct spide
        case SPIDER_NET_GRFBFLLINT: /* fallthrough */
        case SPIDER_NET_GRFAFLLINT: /* fallthrough */
        case SPIDER_NET_GRMFLLINT:
-               if (netif_msg_intr(card) && net_ratelimit())
-                       pr_err("%s: Spider RX RAM full, incoming packets "
-                              "might be discarded!\n", card->netdev->name);
+               if (netif_msg_intr(card) && net_ratelimit()) {
+                       pr_err("%s: Spider RX RAM full, reseting device.\n",
+                              card->netdev->name);
+                       show_rx_chain(card);
+               }
                spider_net_rx_irq_off(card);
                netif_rx_schedule(card->netdev);
+
+               /* If the card is spewing rxramfulls, then reset */
+               atomic_inc(&card->tx_timeout_task_counter);
+               schedule_work(&card->tx_timeout_task);
                show_error = 0;
                break;
 
@@ -2087,6 +2093,8 @@ spider_net_workaround_rxramfull(struct s
 {
        int i, sequencer = 0;
 
+       printk(KERN_INFO "%s: calling rxramfull workaround\n", 
card->netdev->name);
+
        /* cancel reset */
        spider_net_write_reg(card, SPIDER_NET_CKRCTRL,
                             SPIDER_NET_CKRCTRL_RUN_VALUE);
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to