Bug 21382 - Unable to get a connection with r8169 driver on NIC RTL-8110SC/8169SC
Summary: Unable to get a connection with r8169 driver on NIC RTL-8110SC/8169SC
Status: RESOLVED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: Network (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Francois Romieu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-28 23:07 UTC by Sÿl
Modified: 2010-11-21 20:06 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.36
Subsystem:
Regression: Yes
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Sÿl 2010-10-28 23:07:33 UTC 
I upgraded to 2.6.36 my really old 2.6.30.5 kernel, but since I'm unable to use 3 of my NICs.
Those are all RTL-8110SC/8169SC used by r8169.

During first seconds right after "ip addr add x.x.x.x/24 dev eth1 broadcast +" I'm able to ping but I'm loosing 60 % of packets, then after a few minutes I finally don't ping at all.
I even tryed to change my NICs because I thought this was a coincidence, no success, still the same problem.
Comment 1 Sÿl 2010-10-28 23:10:33 UTC 
One other info, I also tryed realtek latest driver (http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=14&PFid=6&Level=5&Conn=4&DownTypeID=3&GetDown=false).
It's worse. When trying to ping I get a kernel panic.
Comment 2 Francois Romieu 2010-10-29 21:33:28 UTC 
Can you send a complete dmesg and an ethtool dump of the registers
for both 2.6.30.5 and 2.6.36 ?

1500 bytes MTU ?

-- 
Ueimor
Comment 3 Sÿl 2010-11-21 20:04:48 UTC 
Forget about it.

The problem disappeared after upgrading some other packages on my distribution.
Weird though, but it doesn't concern the kernel.

Sorry for bugging you for nothing.
Note You need to log in before you can comment on or make changes to this bug.