Re: [3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
Jörg Otte :
[...]
> To Summarize: Two net-regressions where introduced in v3.8 (driver r8169):
>
> 1) NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
> was introduced by commit
> e0c075577965d1c01b30038d38bf637b027a1df3
> ("r8169: enable ALDPS for power saving")
Hayes Wang authored it. You should ask him
why commit e0c075577965d1c01b30038d38bf637b027a1df3 sometimes chokes
with the 8168evl.
And you can ask him if there is a chance that the non-8168evl that are
handled by the patch (mis-)behave the same too.
--
Ueimor
--
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/
Re: [3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
2013/2/3 Jörg Otte :
> 2013/1/6 Jörg Otte :
>> 2013/1/5 Francois Romieu :
>>> Can you check if things improve with v3.8-rc2 after removing :
>>>
>>> 2. d64ec841517a25f6d468bde9f67e5b4cffdc67c7
>>>r8169: enable internal ASPM and clock request settings
>>
>> 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 :02:00.0: irq 42 for MSI/MSI-X
>> [1.957161] r8169 :02:00.0 eth0: RTL8168evl/8111evl at..
>> [1.957163] r8169 :02:00.0 eth0: jumbo features [frames..
>> [ 13.575452] r8169 :02:00.0 eth0: link down
>> [ 13.575475] r8169 :02:00.0 eth0: link down
>> [ 15.181317] r8169 :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 :02:00.0: irq 42 for MSI/MSI-X
>> [1.852872] r8169 :02:00.0 eth0: RTL8168evl/8111evl at...
>> [1.852874] r8169 :02:00.0 eth0: jumbo features [frames...
>> [ 14.150212] r8169 :02:00.0 eth0: link down
>> [ 14.150229] r8169 :02:00.0 eth0: link down
>> [ 24.140263] r8169 :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 :02:00.0: irq 42 for MSI/MSI-X
>> [1.816947] r8169 :02:00.0 eth0: RTL8168evl/8111evl at...
>> [1.816948] r8169 :02:00.0 eth0: jumbo features [frames...
>> [ 13.986401] r8169 :02:00.0 eth0: link down
>> [ 13.986422] r8169 :02:00.0 eth0: link down
>> [ 15.623631] r8169 :02:00.0 eth0: link up
>>
>>
>>> 3. e0c075577965d1c01b30038d38bf637b027a1df3
>>>r8169: enable ALDPS for power saving
>>
>> That's it! This fixes the problem for me!
>>
>> Thanks, Jörg
>
>
> 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
No response, so I Cc to Linus:
To Summarize: Two net-regressions where introduced in v3.8 (driver r8169):
1) NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
was introduced by commit
e0c075577965d1c01b30038d38bf637b027a1df3
("r8169: enable ALDPS for power saving")
2) Boot-time increased from 15sec (V3.7) to 24sec (V3.8)
by commit:
d64ec841517a25f6d468bde9f67e5b4cffdc67c7
("r8169: enable internal ASPM and clock request settings")
Reverting the commits resolve the problems entirely.
As long as the issues are not fixed the commits should be reverted.
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/
Re: [3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
2013/2/3 Jörg Otte jrg.o...@gmail.com: 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 : 2. d64ec841517a25f6d468bde9f67e5b4cffdc67c7 r8169: enable internal ASPM and clock request settings 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 :02:00.0: irq 42 for MSI/MSI-X [1.957161] r8169 :02:00.0 eth0: RTL8168evl/8111evl at.. [1.957163] r8169 :02:00.0 eth0: jumbo features [frames.. [ 13.575452] r8169 :02:00.0 eth0: link down [ 13.575475] r8169 :02:00.0 eth0: link down [ 15.181317] r8169 :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 :02:00.0: irq 42 for MSI/MSI-X [1.852872] r8169 :02:00.0 eth0: RTL8168evl/8111evl at... [1.852874] r8169 :02:00.0 eth0: jumbo features [frames... [ 14.150212] r8169 :02:00.0 eth0: link down [ 14.150229] r8169 :02:00.0 eth0: link down [ 24.140263] r8169 :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 :02:00.0: irq 42 for MSI/MSI-X [1.816947] r8169 :02:00.0 eth0: RTL8168evl/8111evl at... [1.816948] r8169 :02:00.0 eth0: jumbo features [frames... [ 13.986401] r8169 :02:00.0 eth0: link down [ 13.986422] r8169 :02:00.0 eth0: link down [ 15.623631] r8169 :02:00.0 eth0: link up 3. e0c075577965d1c01b30038d38bf637b027a1df3 r8169: enable ALDPS for power saving That's it! This fixes the problem for me! Thanks, Jörg 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 No response, so I Cc to Linus: To Summarize: Two net-regressions where introduced in v3.8 (driver r8169): 1) NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out was introduced by commit e0c075577965d1c01b30038d38bf637b027a1df3 (r8169: enable ALDPS for power saving) 2) Boot-time increased from 15sec (V3.7) to 24sec (V3.8) by commit: d64ec841517a25f6d468bde9f67e5b4cffdc67c7 (r8169: enable internal ASPM and clock request settings) Reverting the commits resolve the problems entirely. As long as the issues are not fixed the commits should be reverted. 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/
Re: [3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
Jörg Otte jrg.o...@gmail.com : [...] To Summarize: Two net-regressions where introduced in v3.8 (driver r8169): 1) NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out was introduced by commit e0c075577965d1c01b30038d38bf637b027a1df3 (r8169: enable ALDPS for power saving) Hayes Wang hayesw...@realtek.com authored it. You should ask him why commit e0c075577965d1c01b30038d38bf637b027a1df3 sometimes chokes with the 8168evl. And you can ask him if there is a chance that the non-8168evl that are handled by the patch (mis-)behave the same too. -- Ueimor -- 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/
Re: [3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
2013/1/6 Jörg Otte : > 2013/1/5 Francois Romieu : >> 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 :02:00.0: irq 42 for MSI/MSI-X > [1.957161] r8169 :02:00.0 eth0: RTL8168evl/8111evl at.. > [1.957163] r8169 :02:00.0 eth0: jumbo features [frames.. > [ 13.575452] r8169 :02:00.0 eth0: link down > [ 13.575475] r8169 :02:00.0 eth0: link down > [ 15.181317] r8169 :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 :02:00.0: irq 42 for MSI/MSI-X > [1.852872] r8169 :02:00.0 eth0: RTL8168evl/8111evl at... > [1.852874] r8169 :02:00.0 eth0: jumbo features [frames... > [ 14.150212] r8169 :02:00.0 eth0: link down > [ 14.150229] r8169 :02:00.0 eth0: link down > [ 24.140263] r8169 :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 :02:00.0: irq 42 for MSI/MSI-X > [1.816947] r8169 :02:00.0 eth0: RTL8168evl/8111evl at... > [1.816948] r8169 :02:00.0 eth0: jumbo features [frames... > [ 13.986401] r8169 :02:00.0 eth0: link down > [ 13.986422] r8169 :02:00.0 eth0: link down > [ 15.623631] r8169 :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/
Re: [3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
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 :02:00.0: irq 42 for MSI/MSI-X [1.957161] r8169 :02:00.0 eth0: RTL8168evl/8111evl at.. [1.957163] r8169 :02:00.0 eth0: jumbo features [frames.. [ 13.575452] r8169 :02:00.0 eth0: link down [ 13.575475] r8169 :02:00.0 eth0: link down [ 15.181317] r8169 :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 :02:00.0: irq 42 for MSI/MSI-X [1.852872] r8169 :02:00.0 eth0: RTL8168evl/8111evl at... [1.852874] r8169 :02:00.0 eth0: jumbo features [frames... [ 14.150212] r8169 :02:00.0 eth0: link down [ 14.150229] r8169 :02:00.0 eth0: link down [ 24.140263] r8169 :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 :02:00.0: irq 42 for MSI/MSI-X [1.816947] r8169 :02:00.0 eth0: RTL8168evl/8111evl at... [1.816948] r8169 :02:00.0 eth0: jumbo features [frames... [ 13.986401] r8169 :02:00.0 eth0: link down [ 13.986422] r8169 :02:00.0 eth0: link down [ 15.623631] r8169 :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/
Re: [3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
2013/1/5 Francois Romieu : > 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 :02:00.0: irq 42 for MSI/MSI-X [1.957161] r8169 :02:00.0 eth0: RTL8168evl/8111evl at.. [1.957163] r8169 :02:00.0 eth0: jumbo features [frames.. [ 13.575452] r8169 :02:00.0 eth0: link down [ 13.575475] r8169 :02:00.0 eth0: link down [ 15.181317] r8169 :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 :02:00.0: irq 42 for MSI/MSI-X [1.852872] r8169 :02:00.0 eth0: RTL8168evl/8111evl at... [1.852874] r8169 :02:00.0 eth0: jumbo features [frames... [ 14.150212] r8169 :02:00.0 eth0: link down [ 14.150229] r8169 :02:00.0 eth0: link down [ 24.140263] r8169 :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 :02:00.0: irq 42 for MSI/MSI-X [1.816947] r8169 :02:00.0 eth0: RTL8168evl/8111evl at... [1.816948] r8169 :02:00.0 eth0: jumbo features [frames... [ 13.986401] r8169 :02:00.0 eth0: link down [ 13.986422] r8169 :02:00.0 eth0: link down [ 15.623631] r8169 :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! 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/
Re: [3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
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 :02:00.0: irq 42 for MSI/MSI-X [1.957161] r8169 :02:00.0 eth0: RTL8168evl/8111evl at.. [1.957163] r8169 :02:00.0 eth0: jumbo features [frames.. [ 13.575452] r8169 :02:00.0 eth0: link down [ 13.575475] r8169 :02:00.0 eth0: link down [ 15.181317] r8169 :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 :02:00.0: irq 42 for MSI/MSI-X [1.852872] r8169 :02:00.0 eth0: RTL8168evl/8111evl at... [1.852874] r8169 :02:00.0 eth0: jumbo features [frames... [ 14.150212] r8169 :02:00.0 eth0: link down [ 14.150229] r8169 :02:00.0 eth0: link down [ 24.140263] r8169 :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 :02:00.0: irq 42 for MSI/MSI-X [1.816947] r8169 :02:00.0 eth0: RTL8168evl/8111evl at... [1.816948] r8169 :02:00.0 eth0: jumbo features [frames... [ 13.986401] r8169 :02:00.0 eth0: link down [ 13.986422] r8169 :02:00.0 eth0: link down [ 15.623631] r8169 :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! 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/
Re: [3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
Jörg Otte :
[...]
> jojo@ahorn:~$ dmesg | grep XID
> [1.808847] r8169 :02:00.0 eth0: RTL8168evl/8111evl at
> 0xc9054000, 5c:9a:d8:69:2b:39, XID 0c900800 IRQ 42
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
3. e0c075577965d1c01b30038d38bf637b027a1df3
r8169: enable ALDPS for power saving
(you can directly try v3.7 r8169.c with v3.8-rc2 if it worked for you
so far)
If the regression is still there, please apply the patch below to both
v3.8-rc2 unpatched and a known working version then send me their dmesg
after you 'ip link set dev eth0 up'.
diff --git a/drivers/net/ethernet/realtek/r8169.c
b/drivers/net/ethernet/realtek/r8169.c
index ed96f30..3d2d2446 100644
--- a/drivers/net/ethernet/realtek/r8169.c
+++ b/drivers/net/ethernet/realtek/r8169.c
@@ -90,10 +90,28 @@ static const int multicast_filter_limit = 32;
#define RTL8169_TX_TIMEOUT (6*HZ)
#define RTL8169_PHY_TIMEOUT(10*HZ)
+static void rw8(void __iomem *ioaddr, u8 b)
+{
+ printk(KERN_DEBUG PFX "w %p %02x\n", ioaddr, b);
+ writeb(b, ioaddr);
+}
+
+static void rw16(void __iomem *ioaddr, u16 w)
+{
+ printk(KERN_DEBUG PFX "w %p %04x\n", ioaddr, w);
+ writew(w, ioaddr);
+}
+
+static void rw32(void __iomem *ioaddr, u32 d)
+{
+ printk(KERN_DEBUG PFX "w %p %08x\n", ioaddr, d);
+ writel(d, ioaddr);
+}
+
/* write/read MMIO register */
-#define RTL_W8(reg, val8) writeb ((val8), ioaddr + (reg))
-#define RTL_W16(reg, val16)writew ((val16), ioaddr + (reg))
-#define RTL_W32(reg, val32)writel ((val32), ioaddr + (reg))
+#define RTL_W8(reg, val8) rw8(ioaddr + (reg), (val8))
+#define RTL_W16(reg, val16)rw16(ioaddr + (reg), (val16))
+#define RTL_W32(reg, val32)rw32(ioaddr + (reg), (val32))
#define RTL_R8(reg)readb (ioaddr + (reg))
#define RTL_R16(reg) readw (ioaddr + (reg))
#define RTL_R32(reg) readl (ioaddr + (reg))
--
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/
Re: [3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
2013/1/5 Francois Romieu : > Jörg Otte : > [...] >> It's a regression, it never happend before 3.8-rc. > > Please check that 'dmesg | grep XID' exhibits a 8168evl. jojo@ahorn:~$ dmesg | grep XID [1.808847] r8169 :02:00.0 eth0: RTL8168evl/8111evl at 0xc9054000, 5c:9a:d8:69:2b:39, XID 0c900800 IRQ 42 jojo@ahorn:~$ > > I'll showe and dig it. It's epidemic. > 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/
Re: [3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
Jörg Otte : [...] > It's a regression, it never happend before 3.8-rc. Please check that 'dmesg | grep XID' exhibits a 8168evl. I'll showe and dig it. It's epidemic. -- Ueimor -- 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/
[3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
I frequently see the following in the syslog: [ 184.552914] [ cut here ] [ 184.552927] WARNING: at /data/kernel/linux/net/sched/sch_generic.c:254 dev_watchdog+0xf2/0x151() [ 184.552929] Hardware name: LIFEBOOK AH532 [ 184.552932] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out [ 184.552937] Pid: 0, comm: swapper/1 Not tainted 3.8.0-rc2-b11-00221-gd1c3ed6 #15 [ 184.552939] Call Trace: [ 184.552941][] ? dev_watchdog+0xf2/0x151 [ 184.552953] [] ? warn_slowpath_common+0x73/0x87 [ 184.552956] [] ? netif_tx_unlock+0x49/0x49 [ 184.552961] [] ? warn_slowpath_fmt+0x45/0x4a [ 184.552967] [] ? netif_tx_lock+0x40/0x75 [ 184.552971] [] ? dev_watchdog+0xf2/0x151 [ 184.552977] [] ? call_timer_fn.isra.32+0x1d/0x73 [ 184.552981] [] ? run_timer_softirq+0x154/0x194 [ 184.552988] [] ? timekeeping_get_ns.constprop.6+0xd/0x31 [ 184.552992] [] ? __do_softirq+0x96/0x139 [ 184.552997] [] ? call_softirq+0x1c/0x26 [ 184.553002] [] ? do_softirq+0x2e/0x62 [ 184.553006] [] ? irq_exit+0x3d/0x98 [ 184.553011] [] ? smp_apic_timer_interrupt+0x73/0x80 [ 184.553018] [] ? apic_timer_interrupt+0x6a/0x70 [ 184.553020][] ? cpuidle_wrap_enter+0x38/0x69 [ 184.553033] [] ? cpuidle_wrap_enter+0x34/0x69 [ 184.553039] [] ? cpuidle_enter_state+0xa/0x31 [ 184.553044] [] ? cpuidle_idle_call+0x99/0xb9 [ 184.553050] [] ? cpu_idle+0x99/0xe0 [ 184.553056] [] ? start_secondary+0x1d6/0x1dc [ 184.553059] ---[ end trace 54db26a54b22f673 ]--- [ 184.587487] r8169 :02:00.0 eth0: link up It's a regression, it never happend before 3.8-rc. -- 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/
[3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
I frequently see the following in the syslog: [ 184.552914] [ cut here ] [ 184.552927] WARNING: at /data/kernel/linux/net/sched/sch_generic.c:254 dev_watchdog+0xf2/0x151() [ 184.552929] Hardware name: LIFEBOOK AH532 [ 184.552932] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out [ 184.552937] Pid: 0, comm: swapper/1 Not tainted 3.8.0-rc2-b11-00221-gd1c3ed6 #15 [ 184.552939] Call Trace: [ 184.552941] IRQ [8138d4a2] ? dev_watchdog+0xf2/0x151 [ 184.552953] [81025c8a] ? warn_slowpath_common+0x73/0x87 [ 184.552956] [8138d3b0] ? netif_tx_unlock+0x49/0x49 [ 184.552961] [81025d02] ? warn_slowpath_fmt+0x45/0x4a [ 184.552967] [8138d332] ? netif_tx_lock+0x40/0x75 [ 184.552971] [8138d4a2] ? dev_watchdog+0xf2/0x151 [ 184.552977] [8102f1a1] ? call_timer_fn.isra.32+0x1d/0x73 [ 184.552981] [8102f34b] ? run_timer_softirq+0x154/0x194 [ 184.552988] [8104cb84] ? timekeeping_get_ns.constprop.6+0xd/0x31 [ 184.552992] [8102b4a5] ? __do_softirq+0x96/0x139 [ 184.552997] [8146b00c] ? call_softirq+0x1c/0x26 [ 184.553002] [81003cf4] ? do_softirq+0x2e/0x62 [ 184.553006] [8102b615] ? irq_exit+0x3d/0x98 [ 184.553011] [810184ad] ? smp_apic_timer_interrupt+0x73/0x80 [ 184.553018] [8146aa0a] ? apic_timer_interrupt+0x6a/0x70 [ 184.553020] EOI [81326f2b] ? cpuidle_wrap_enter+0x38/0x69 [ 184.553033] [81326f27] ? cpuidle_wrap_enter+0x34/0x69 [ 184.553039] [81326d81] ? cpuidle_enter_state+0xa/0x31 [ 184.553044] [81326e41] ? cpuidle_idle_call+0x99/0xb9 [ 184.553050] [81009059] ? cpu_idle+0x99/0xe0 [ 184.553056] [8145e3a4] ? start_secondary+0x1d6/0x1dc [ 184.553059] ---[ end trace 54db26a54b22f673 ]--- [ 184.587487] r8169 :02:00.0 eth0: link up It's a regression, it never happend before 3.8-rc. -- 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/
Re: [3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
Jörg Otte jrg.o...@gmail.com : [...] It's a regression, it never happend before 3.8-rc. Please check that 'dmesg | grep XID' exhibits a 8168evl. I'll showe and dig it. It's epidemic. -- Ueimor -- 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/
Re: [3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
2013/1/5 Francois Romieu rom...@fr.zoreil.com: Jörg Otte jrg.o...@gmail.com : [...] It's a regression, it never happend before 3.8-rc. Please check that 'dmesg | grep XID' exhibits a 8168evl. jojo@ahorn:~$ dmesg | grep XID [1.808847] r8169 :02:00.0 eth0: RTL8168evl/8111evl at 0xc9054000, 5c:9a:d8:69:2b:39, XID 0c900800 IRQ 42 jojo@ahorn:~$ I'll showe and dig it. It's epidemic. 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/
Re: [3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
Jörg Otte jrg.o...@gmail.com :
[...]
jojo@ahorn:~$ dmesg | grep XID
[1.808847] r8169 :02:00.0 eth0: RTL8168evl/8111evl at
0xc9054000, 5c:9a:d8:69:2b:39, XID 0c900800 IRQ 42
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
3. e0c075577965d1c01b30038d38bf637b027a1df3
r8169: enable ALDPS for power saving
(you can directly try v3.7 r8169.c with v3.8-rc2 if it worked for you
so far)
If the regression is still there, please apply the patch below to both
v3.8-rc2 unpatched and a known working version then send me their dmesg
after you 'ip link set dev eth0 up'.
diff --git a/drivers/net/ethernet/realtek/r8169.c
b/drivers/net/ethernet/realtek/r8169.c
index ed96f30..3d2d2446 100644
--- a/drivers/net/ethernet/realtek/r8169.c
+++ b/drivers/net/ethernet/realtek/r8169.c
@@ -90,10 +90,28 @@ static const int multicast_filter_limit = 32;
#define RTL8169_TX_TIMEOUT (6*HZ)
#define RTL8169_PHY_TIMEOUT(10*HZ)
+static void rw8(void __iomem *ioaddr, u8 b)
+{
+ printk(KERN_DEBUG PFX w %p %02x\n, ioaddr, b);
+ writeb(b, ioaddr);
+}
+
+static void rw16(void __iomem *ioaddr, u16 w)
+{
+ printk(KERN_DEBUG PFX w %p %04x\n, ioaddr, w);
+ writew(w, ioaddr);
+}
+
+static void rw32(void __iomem *ioaddr, u32 d)
+{
+ printk(KERN_DEBUG PFX w %p %08x\n, ioaddr, d);
+ writel(d, ioaddr);
+}
+
/* write/read MMIO register */
-#define RTL_W8(reg, val8) writeb ((val8), ioaddr + (reg))
-#define RTL_W16(reg, val16)writew ((val16), ioaddr + (reg))
-#define RTL_W32(reg, val32)writel ((val32), ioaddr + (reg))
+#define RTL_W8(reg, val8) rw8(ioaddr + (reg), (val8))
+#define RTL_W16(reg, val16)rw16(ioaddr + (reg), (val16))
+#define RTL_W32(reg, val32)rw32(ioaddr + (reg), (val32))
#define RTL_R8(reg)readb (ioaddr + (reg))
#define RTL_R16(reg) readw (ioaddr + (reg))
#define RTL_R32(reg) readl (ioaddr + (reg))
--
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/
