2013/1/6 Jörg Otte <jrg.o...@gmail.com>: > 2013/1/5 Francois Romieu <rom...@fr.zoreil.com>: >> Can you check if things improve with v3.8-rc2 after removing : >> >> 1. 9ecb9aabaf634677c77af467f4e3028b09d7bcda >> r8169: workaround for missing extended GigaMAC registers >> 2. d64ec841517a25f6d468bde9f67e5b4cffdc67c7 >> r8169: enable internal ASPM and clock request settings > > Doesn't help for this problem. > > However this fixes a second issue for me: > In 3.7.1 at startup the link came up after 15 sec.: > grep r8169 dmesg.3.7.1 > [ 1.956842] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded > [ 1.957059] r8169 0000:02:00.0: irq 42 for MSI/MSI-X > [ 1.957161] r8169 0000:02:00.0 eth0: RTL8168evl/8111evl at.. > [ 1.957163] r8169 0000:02:00.0 eth0: jumbo features [frames.. > [ 13.575452] r8169 0000:02:00.0 eth0: link down > [ 13.575475] r8169 0000:02:00.0 eth0: link down > [ 15.181317] r8169 0000:02:00.0 eth0: link up > > In 3.8rc the time increased to 24 seconds: > grep r8169 dmesg.3.8.0 > [ 1.852546] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded > [ 1.852765] r8169 0000:02:00.0: irq 42 for MSI/MSI-X > [ 1.852872] r8169 0000:02:00.0 eth0: RTL8168evl/8111evl at... > [ 1.852874] r8169 0000:02:00.0 eth0: jumbo features [frames... > [ 14.150212] r8169 0000:02:00.0 eth0: link down > [ 14.150229] r8169 0000:02:00.0 eth0: link down > [ 24.140263] r8169 0000:02:00.0 eth0: link up > > But with this revert I get the old performance: > dmesg | grep r8169 > [ 1.816613] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded > [ 1.816832] r8169 0000:02:00.0: irq 42 for MSI/MSI-X > [ 1.816947] r8169 0000:02:00.0 eth0: RTL8168evl/8111evl at... > [ 1.816948] r8169 0000:02:00.0 eth0: jumbo features [frames... > [ 13.986401] r8169 0000:02:00.0 eth0: link down > [ 13.986422] r8169 0000:02:00.0 eth0: link down > [ 15.623631] r8169 0000:02:00.0 eth0: link up > > Thus I recommend to revert this too. > >> 3. e0c075577965d1c01b30038d38bf637b027a1df3 >> r8169: enable ALDPS for power saving > > That's it! This fixes the problem for me! >
We are closely before v3.8 and I didn't see a solution so far. What is the plan regarding this issue(s)? Thanks, Jörg -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/