NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out

2014-12-11 Thread Marco Berizzi
Hi Folks, I'm running slackware linux 14 32 bits as a firewall/ipsec gateway with linux 3.18.0 I got this error just after 12 hours uptime: WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:303 dev_watchdog+0xee/0x174() NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out Modules link

Re: [3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out

2013-02-06 Thread Francois Romieu
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&

Re: [3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out

2013-02-06 Thread Jörg Otte
gt;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

Re: [3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out

2013-02-03 Thread 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 : >> >> 1. 9ecb9aabaf634677c77af467f4e3028b09d7bcda >>r8169: workaround for missing extended GigaMAC registers >> 2. d64ec841517a25f6d468bde9f67e5b4cffdc67c7 >>r8169: enable int

Re: [3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out

2013-01-06 Thread 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

Re: [3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out

2013-01-05 Thread Francois Romieu
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: wo

Re: [3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out

2013-01-05 Thread Jörg Otte
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, X

Re: [3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out

2013-01-05 Thread 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. 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.

[3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out

2013-01-05 Thread Jörg Otte
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