diff options
| author | Francois Romieu <romieu@fr.zoreil.com> | 2012-06-20 12:09:18 +0000 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-10-02 10:30:35 -0700 |
| commit | 6418cc471b5d8a64ce22d2aa827fcb275e61449c (patch) | |
| tree | d58cde6caef8705b0a9523320076b761ce78a5dd /kernel/sched/core.c | |
| parent | 9dd30d194e2e83be4e14d7b4bdf21087f389318b (diff) | |
| download | lwn-6418cc471b5d8a64ce22d2aa827fcb275e61449c.tar.gz lwn-6418cc471b5d8a64ce22d2aa827fcb275e61449c.zip | |
r8169: RxConfig hack for the 8168evl.
commit eb2dc35d99028b698cdedba4f5522bc43e576bd2 upstream.
The 8168evl (RTL_GIGA_MAC_VER_34) based Gigabyte GA-990FXA motherboards
are very prone to NETDEV watchdog problems without this change. See
https://bugzilla.kernel.org/show_bug.cgi?id=42899 for instance.
I don't know why it *works*. It's depressingly effective though.
For the record:
- the problem may go along IOMMU (AMD-Vi) errors but it really looks
like a red herring.
- the patch sets the RX_MULTI_EN bit. If the 8168c doc is any guide,
the chipset now fetches several Rx descriptors at a time.
- long ago the driver ignored the RX_MULTI_EN bit.
e542a2269f232d61270ceddd42b73a4348dee2bb changed the RxConfig
settings. Whatever the problem it's now labeled a regression.
- Realtek's own driver can identify two different 8168evl devices
(CFG_METHOD_16 and CFG_METHOD_17) where the r8169 driver only
sees one. It sucks.
Signed-off-by: Francois Romieu <romieu@fr.zoreil.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'kernel/sched/core.c')
0 files changed, 0 insertions, 0 deletions