diff options
| author | Eric Dumazet <eric.dumazet@gmail.com> | 2012-02-15 20:43:11 +0000 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-03-19 08:57:46 -0700 |
| commit | f27ce05c2be6cb27a3cee72c4ec4794556d6ef9d (patch) | |
| tree | 02298a90e19b7d24c48291050f75442d79702880 /arch/s390 | |
| parent | 94962718da9d6df11a3a30511016707e4e9451dc (diff) | |
| download | kernel_samsung_smdk4412-f27ce05c2be6cb27a3cee72c4ec4794556d6ef9d.zip kernel_samsung_smdk4412-f27ce05c2be6cb27a3cee72c4ec4794556d6ef9d.tar.gz kernel_samsung_smdk4412-f27ce05c2be6cb27a3cee72c4ec4794556d6ef9d.tar.bz2 | |
atl1c: dont use highprio tx queue
[ Upstream commit 11aad99af6ef629ff3b05d1c9f0936589b204316 ]
This driver attempts to use two TX rings but lacks proper support :
1) IRQ handler only takes care of TX completion on first TX ring
2) the stop/start logic uses the legacy functions (for non multiqueue
drivers)
This means all packets witk skb mark set to 1 are sent through high
queue but are never cleaned and queue eventualy fills and block the
device, triggering the infamous "NETDEV WATCHDOG" message.
Lets use a single TX ring to fix the problem, this driver is not a real
multiqueue one yet.
Minimal fix for stable kernels.
Reported-by: Thomas Meyer <thomas@m3y3r.de>
Tested-by: Thomas Meyer <thomas@m3y3r.de>
Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Jay Cliburn <jcliburn@gmail.com>
Cc: Chris Snook <chris.snook@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch/s390')
0 files changed, 0 insertions, 0 deletions