From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: [PATCH] sky2: fix hang on Yukon-EC (0xb6) rev 1
Date: Tue, 24 Jan 2006 14:19:56 +0100 [thread overview]
Message-ID: <43D6297C.8000900@gmx.net> (raw)
This patch for sky2 fixes a hang on Yukon-EC (0xb6) rev 1
where suddenly no more interrupts were delivered.
I don't know the real cause of the hang due to lack of docs,
but the patch has been running stable for a few hours
whereas the unmodified driver will hang after less than
2 minutes.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
--- linux-2.6.15/drivers/net/sky2.c 2006-01-23 23:41:35.000000000 +0100
+++ linux-2.6.15/drivers/net/sky2.c 2006-01-24 14:12:12.000000000 +0100
@@ -1913,8 +1913,26 @@
}
exit_loop:
+ /* Is this really a good idea?
+ * We clear all IRQs although there may be pending work due to
+ * - packets arrived since start of this function
+ * - the (++work_done >= to_do) abort
+ */
sky2_write32(hw, STAT_CTRL, SC_STAT_CLR_IRQ);
+ /* Pending resolution of the comment above, at least kick the
+ * STAT_LEV_TIMER_CTRL timer.
+ * This fixes my hangs on Yukon-EC (0xb6) rev 1.
+ * The if clause is there to start the timer only if it has been
+ * configured correctly and not been disabled via ethtool.
+ * Maybe it would be sufficient to only restart the timer if
+ * there is pending work. Without docs, that is hard to say.
+ */
+ if (sky2_read8(hw, STAT_LEV_TIMER_CTRL) == TIM_START) {
+ sky2_write8(hw, STAT_LEV_TIMER_CTRL, TIM_STOP);
+ sky2_write8(hw, STAT_LEV_TIMER_CTRL, TIM_START);
+ }
+
sky2_tx_check(hw, 0, tx_done[0]);
sky2_tx_check(hw, 1, tx_done[1]);
reply other threads:[~2006-01-24 13:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43D6297C.8000900@gmx.net \
--to=c-d.hailfinger.devel.2006@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.org \
/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;
as well as URLs for NNTP newsgroup(s).