![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=774452
https://bugzilla.novell.com/show_bug.cgi?id=774452#c2
--- Comment #2 from Benjamin Poirier
I've reported the same problem in bnc #770760, but for me, 3.5-rc4 is stable (although I haven't tested with heavy network traffic for that long).
You're right that it's the same "symptom" but I think they are not duplicates. All of the following bugs show up as netdev watchdog timeouts with r8169 but have a different cause: https://bugzilla.kernel.org/show_bug.cgi?id=14962 a register configuration problem with a RTL8168evl/8111evl It is fixed in 3.5 by eb2dc35 r8169: RxConfig hack for the 8168evl. bnc#774557 an unknown problem with a RTL8168b/8111b bnc#770760 an unknown problem with a RTL8168c/8111c It is fixed in 3.5 by an unknown commit bnc#774452 This problem is introduced between 3.2 and 3.5 It is possibly the same thing as what is reported in http://thread.gmane.org/gmane.linux.network/229304/focus=239136 that is, bql support. If that's the case, it is "fixed" in 3.6-rc1 by 17bcb68 r8169: revert "add byte queue limit support". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.