From: David Miller <davem@davemloft.net>
To: cjren@qca.qualcomm.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
qca-linux-team@qualcomm.com, nic-devel@qualcomm.com
Subject: Re: [PATCH 1/1] atl1c: fix issue of transmit queue 0 timed out
Date: Mon, 09 Jul 2012 00:00:23 -0700 (PDT) [thread overview]
Message-ID: <20120709.000023.862144144755024401.davem@davemloft.net> (raw)
In-Reply-To: <1341370308-23233-1-git-send-email-cjren@qca.qualcomm.com>
From: <cjren@qca.qualcomm.com>
Date: Wed, 4 Jul 2012 10:51:48 +0800
> some people report atl1c could cause system hang with following
> kernel trace info:
> ---------------------------------------
> WARNING: at.../net/sched/sch_generic.c:258 dev_watchdog+0x1db/0x1d0()
> ...
> NETDEV WATCHDOG: eth0 (atl1c): transmit queue 0 timed out
> ...
> ---------------------------------------
> This is caused by netif_stop_queue calling when cable Link is down.
> So remove netif_stop_queue, because link_watch will take it over.
>
> Signed-off-by: xiong <xiong@qca.qualcomm.com>
> Cc: stable <stable@vger.kernel.org>
> Signed-off-by: Cloud Ren <cjren@qca.qualcomm.com>
Applied, thanks.
next prev parent reply other threads:[~2012-07-09 7:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 2:51 [PATCH 1/1] atl1c: fix issue of transmit queue 0 timed out cjren
2012-07-09 7:00 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-03 13:27 Ren, Cloud
2012-07-03 10:23 ` David Miller
2012-07-03 13:04 ` Huang, Xiong
2012-07-04 1:56 ` Ren, Cloud
2012-06-26 15:33 Ren, Cloud
2012-06-26 18:03 ` Luis R. Rodriguez
2012-06-26 20:41 ` Huang, Xiong
2012-06-26 20:54 ` Luis R. Rodriguez
2012-06-26 20:55 ` Huang, Xiong
2012-06-26 20:23 ` Ben Hutchings
2012-06-26 20:25 ` Huang, Xiong
2012-06-26 20:26 ` Huang, Xiong
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=20120709.000023.862144144755024401.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cjren@qca.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic-devel@qualcomm.com \
--cc=qca-linux-team@qualcomm.com \
/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