From: Mike McCormack <mikem@ring3k.org>
To: netdev@vger.kernel.org,
Stephen Hemminger <shemminger@linux-foundation.org>
Subject: Re: [PATCH] sky2: Kick the transmit watchdog timer on transmit
Date: Sun, 12 Jul 2009 21:09:22 +0900 [thread overview]
Message-ID: <392fb48f0907120509t454d125ei3279022d28fd6092@mail.gmail.com> (raw)
In-Reply-To: <392fb48f0907120242r438411ccm5507998c3fcad877@mail.gmail.com>
Hi Stephen,
Ignore this. I was using 2.6.30 with the sky2 code from net-next-2.6,
and the core network core code changed (in cdd0db058d64f). I'll move
over to using net-next-2.6 and deal with the instability...
thanks,
Mike
2009/7/12 Mike McCormack <mikem@ring3k.org>:
> Hi Stephen,
>
> I was curious as to why sky2_tx_timeout() was being called once when
> the driver started, and never again (which originally caused the crash
> resolved by the previous patch).
>
> I might be missing something, but it looks like we the transmit
> watchdog needs to be kicked whenever a packet is transmitted.
>
> This patch has had a small amount of testing, but reviewing other
> drivers (e.g. net/atm/lec.c), this appears to be what is done.
>
> thanks,
>
> Mike
>
> ---
>
> If we don't kick the watchdog, it always triggers.
>
> Signed-off-by: Mike McCormack <mikem@ring3k.org>
> ---
> drivers/net/sky2.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/sky2.c b/drivers/net/sky2.c
> index 77fd1b9..48d58ec 100644
> --- a/drivers/net/sky2.c
> +++ b/drivers/net/sky2.c
> @@ -1708,6 +1708,8 @@ static int sky2_xmit_frame(struct sk_buff *skb,
> struct net_device *dev)
>
> sky2_put_idx(hw, txqaddr[sky2->port], sky2->tx_prod);
>
> + dev->trans_start = jiffies; /* restart tx timeout */
> +
> return NETDEV_TX_OK;
>
> mapping_unwind:
> --
> 1.5.6.5
>
prev parent reply other threads:[~2009-07-12 12:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-12 9:42 [PATCH] sky2: Kick the transmit watchdog timer on transmit Mike McCormack
2009-07-12 12:09 ` Mike McCormack [this message]
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=392fb48f0907120509t454d125ei3279022d28fd6092@mail.gmail.com \
--to=mikem@ring3k.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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