From: David Miller <davem@davemloft.net>
To: Bryan.Whitehead@microchip.com
Cc: netdev@vger.kernel.org, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH v1 net] lan743x: Fix TX Stall Issue
Date: Wed, 13 Mar 2019 13:43:27 -0700 (PDT) [thread overview]
Message-ID: <20190313.134327.1436563233974528424.davem@davemloft.net> (raw)
In-Reply-To: <1552506948-6863-1-git-send-email-Bryan.Whitehead@microchip.com>
From: Bryan Whitehead <Bryan.Whitehead@microchip.com>
Date: Wed, 13 Mar 2019 15:55:48 -0400
> It has been observed that tx queue may stall while downloading
> from certain web sites (example www.speedtest.net)
>
> The cause has been tracked down to a corner case where
> the tx interrupt vector was disabled automatically, but
> was not re enabled later.
>
> The lan743x has two mechanisms to enable/disable individual
> interrupts. Interrupts can be enabled/disabled by individual
> source, and they can also be enabled/disabled by individual
> vector which has been mapped to the source. Both must be
> enabled for interrupts to work properly.
>
> The TX code path, primarily uses the interrupt enable/disable of
> the TX source bit, while leaving the vector enabled all the time.
>
> However, while investigating this issue it was noticed that
> the driver requested the use of the vector auto clear feature.
>
> The test above revealed a case where the vector enable was
> cleared unintentionally.
>
> This patch fixes the issue by deleting the lines that request
> the vector auto clear feature to be used.
>
> Fixes: 23f0703c125b ("lan743x: Add main source files for new lan743x driver")
> Signed-off-by: Bryan Whitehead <Bryan.Whitehead@microchip.com>
Applied and queued up for -stable.
next prev parent reply other threads:[~2019-03-13 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 19:55 [PATCH v1 net] lan743x: Fix TX Stall Issue Bryan Whitehead
2019-03-13 20:43 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-26 19:06 Bryan Whitehead
2019-03-01 19:34 ` David Miller
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=20190313.134327.1436563233974528424.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Bryan.Whitehead@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=netdev@vger.kernel.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).