[PATCH 5.10 131/663] net: amd-xgbe: Fix NETDEV WATCHDOG transmit queue timeout warning

From: Shyam Sundar S K [ Upstream commit 186edbb510bd60e748f93975989ccba25ee99c50 ] The current driver calls netif_carrier_off() late in the link tear down which can result in a netdev watchdog timeout. Calling netif_carrier_off() immediately after netif_tx_stop_all_queues() avoids the warning

[PATCH 5.11 135/775] net: amd-xgbe: Fix NETDEV WATCHDOG transmit queue timeout warning

From: Shyam Sundar S K [ Upstream commit 186edbb510bd60e748f93975989ccba25ee99c50 ] The current driver calls netif_carrier_off() late in the link tear down which can result in a netdev watchdog timeout. Calling netif_carrier_off() immediately after netif_tx_stop_all_queues() avoids the warning

[PATCH 4.19 069/247] net: amd-xgbe: Fix NETDEV WATCHDOG transmit queue timeout warning

From: Shyam Sundar S K [ Upstream commit 186edbb510bd60e748f93975989ccba25ee99c50 ] The current driver calls netif_carrier_off() late in the link tear down which can result in a netdev watchdog timeout. Calling netif_carrier_off() immediately after netif_tx_stop_all_queues() avoids the warning

[PATCH 5.4 066/340] net: amd-xgbe: Fix NETDEV WATCHDOG transmit queue timeout warning

From: Shyam Sundar S K [ Upstream commit 186edbb510bd60e748f93975989ccba25ee99c50 ] The current driver calls netif_carrier_off() late in the link tear down which can result in a netdev watchdog timeout. Calling netif_carrier_off() immediately after netif_tx_stop_all_queues() avoids the warning

Re: NETDEV WATCHDOG: WARNING: at net/sched/sch_generic.c:442 dev_watchdog

On Wed, 19 Aug 2020 10:29:09 -0700 Jesse Brandeburg wrote: > What I don't understand in the stack trace is this: > > > [ 107.654661] Call Trace: > > > [ 107.657735] > > > [ 107.663155] ? ftrace_graph_caller+0xc0/0xc0 > > > [ 107.667929] call_timer_fn+0x3b/0x1b0 > > > [ 107.672238] ?

Re: NETDEV WATCHDOG: WARNING: at net/sched/sch_generic.c:442 dev_watchdog

r tracepoints stat_sleep, stat_iowait, > > stat_blocked and stat_runtime require the kernel parameter > > schedstats=enable or kernel.sched_schedstats=1 > > [ 88.139387] Scheduler tracepoints stat_sleep, stat_iowait, > > stat_blocked and stat_runtime require the kernel parameter

Re: NETDEV WATCHDOG: WARNING: at net/sched/sch_generic.c:442 dev_watchdog

hedstats=1 > [ 88.139387] Scheduler tracepoints stat_sleep, stat_iowait, > stat_blocked and stat_runtime require the kernel parameter > schedstats=enable or kernel.sched_schedstats=1 > [ 107.507991] [ cut here ] > [ 107.513103] NETDEV WATCHDOG: eth0 (igb):

NETDEV WATCHDOG: WARNING: at net/sched/sch_generic.c:442 dev_watchdog

or kernel.sched_schedstats=1 [ 107.507991] [ cut here ] [ 107.513103] NETDEV WATCHDOG: eth0 (igb): transmit queue 2 timed out [ 107.519973] WARNING: CPU: 1 PID: 331 at net/sched/sch_generic.c:442 dev_watchdog+0x4c7/0x4d0 [ 107.528907] Modules linked in: x86_pkg_temp_thermal

Re: stable-rc 4.19: NETDEV WATCHDOG: eth0 (asix): transmit queue 0 timed out - net/sched/sch_generic.c:466 dev_watchdog

While running selftests bpf test_sysctl on stable rc 5.6 branch kernel on arm64 hikey device. The following warning was noticed. [ 1097.207013] NETDEV WATCHDOG: eth0 (asix): transmit queue 0 timed out [ 1097.387913] WARNING: CPU: 0 PID: 206 at /usr/src/kernel/net/sched/sch_generic.c:443

stable-rc 4.19: NETDEV WATCHDOG: eth0 (asix): transmit queue 0 timed out - net/sched/sch_generic.c:466 dev_watchdog

While running selftests bpf test_sysctl on stable rc 4.19 branch kernel on arm64 hikey device. The following warning was noticed. [ 118.957395] test_bpf: #296 BPF_MAXINSNS: exec all MSH [ 148.966435] [ cut here ] [ 148.988349] NETDEV WATCHDOG: eth0 (asix): transmit

Re: NETDEV WATCHDOG: eth0 (tg3): transmit queue 0 timed out

On Tue, Mar 20, 2018 at 11:41:06AM +0530, Satish Baddipadige wrote: > Can you please test the attached patch? Well, the network connection just died with it. It didn't fire the netdev watchdog but I still had to down and up eth0 in order to continue using it. ssh connection into the box survi

Re: NETDEV WATCHDOG: eth0 (tg3): transmit queue 0 timed out

On Tue, Mar 20, 2018 at 11:41:06AM +0530, Satish Baddipadige wrote: > Can you please test the attached patch? Well, the network connection just died with it. It didn't fire the netdev watchdog but I still had to down and up eth0 in order to continue using it. ssh connection into the box survi

Re: NETDEV WATCHDOG: eth0 (tg3): transmit queue 0 timed out

On Tue, Mar 20, 2018 at 11:41:06AM +0530, Satish Baddipadige wrote: > Can you please test the attached patch? Sure, will do when I get back next week. Thx. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. Srsly.

Re: NETDEV WATCHDOG: eth0 (tg3): transmit queue 0 timed out

On Tue, Mar 20, 2018 at 11:41:06AM +0530, Satish Baddipadige wrote: > Can you please test the attached patch? Sure, will do when I get back next week. Thx. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. Srsly.

Re: NETDEV WATCHDOG: eth0 (tg3): transmit queue 0 timed out

On Wed, Feb 28, 2018 at 7:40 PM, Siva Reddy Kallam wrote: > On Sat, Feb 24, 2018 at 3:48 PM, Borislav Petkov wrote: >> Hi, >> >> this didn't happen before but after 4.16-rc1 my tg3 nic stops for >> whatever reason and the connection to the machine is

Re: NETDEV WATCHDOG: eth0 (tg3): transmit queue 0 timed out

On Wed, Feb 28, 2018 at 7:40 PM, Siva Reddy Kallam wrote: > On Sat, Feb 24, 2018 at 3:48 PM, Borislav Petkov wrote: >> Hi, >> >> this didn't happen before but after 4.16-rc1 my tg3 nic stops for >> whatever reason and the connection to the machine is dead. It didn't show >> anything in dmesg

Re: NETDEV WATCHDOG: eth0 (tg3): transmit queue 0 timed out

On Sat, Feb 24, 2018 at 3:48 PM, Borislav Petkov wrote: > Hi, > > this didn't happen before but after 4.16-rc1 my tg3 nic stops for > whatever reason and the connection to the machine is dead. It didn't show > anything in dmesg until today. > > The IO pagefaults look like it is

Re: NETDEV WATCHDOG: eth0 (tg3): transmit queue 0 timed out

On Sat, Feb 24, 2018 at 3:48 PM, Borislav Petkov wrote: > Hi, > > this didn't happen before but after 4.16-rc1 my tg3 nic stops for > whatever reason and the connection to the machine is dead. It didn't show > anything in dmesg until today. > > The IO pagefaults look like it is trying to access

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

flags=0x] [ 64.992145] [ cut here ] [ 64.992406] NETDEV WATCHDOG: eth0 (tg3): transmit queue 0 timed out [ 64.992742] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:464 dev_watchdog+0x1fe/0x210 [ 64.992744] Modules linked in: arc4 iwlmvm mac80211 amdgpu

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

flags=0x] [ 64.992145] [ cut here ] [ 64.992406] NETDEV WATCHDOG: eth0 (tg3): transmit queue 0 timed out [ 64.992742] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:464 dev_watchdog+0x1fe/0x210 [ 64.992744] Modules linked in: arc4 iwlmvm mac80211 amdgpu

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

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 linked

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

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 linked

Re: igb and bnx2: "NETDEV WATCHDOG: transmit queue timed out" when skb has huge linear buffer

x165/0x220() Nov 26 04:18:34 localhost kernel: [ 7814.197892] NETDEV WATCHDOG: eth0 (igb): transmit queue 7 timed out Nov 26 04:18:34 localhost kernel: [ 7814.197894] Modules linked in: tun nfsv3 nfs_acl nfs fscache dm_multipath scsi_dh lockd sunrpc openvswitch ipt_REJECT nf_conntrack_ipv4 nf_de

Re: igb and bnx2: NETDEV WATCHDOG: transmit queue timed out when skb has huge linear buffer

26 04:18:34 localhost kernel: [ 7814.197892] NETDEV WATCHDOG: eth0 (igb): transmit queue 7 timed out Nov 26 04:18:34 localhost kernel: [ 7814.197894] Modules linked in: tun nfsv3 nfs_acl nfs fscache dm_multipath scsi_dh lockd sunrpc openvswitch ipt_REJECT nf_conntrack_ipv4 nf_defrag_ip v4

Re: igb and bnx2: "NETDEV WATCHDOG: transmit queue timed out" when skb has huge linear buffer

On 05/02/14 20:43, Andrew Cooper wrote: On 05/02/2014 20:23, Zoltan Kiss wrote: On 04/02/14 19:47, Michael Chan wrote: On Fri, 2014-01-31 at 14:29 +0100, Zoltan Kiss wrote: [ 5417.275472] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x156/0x1f0() [ 5417.275474] NETDEV WATCHDOG: eth1

Re: igb and bnx2: NETDEV WATCHDOG: transmit queue timed out when skb has huge linear buffer

On 05/02/14 20:43, Andrew Cooper wrote: On 05/02/2014 20:23, Zoltan Kiss wrote: On 04/02/14 19:47, Michael Chan wrote: On Fri, 2014-01-31 at 14:29 +0100, Zoltan Kiss wrote: [ 5417.275472] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x156/0x1f0() [ 5417.275474] NETDEV WATCHDOG: eth1

Re: igb and bnx2: "NETDEV WATCHDOG: transmit queue timed out" when skb has huge linear buffer

On 05/02/2014 20:23, Zoltan Kiss wrote: > On 04/02/14 19:47, Michael Chan wrote: >> On Fri, 2014-01-31 at 14:29 +0100, Zoltan Kiss wrote: >>> [ 5417.275472] WARNING: at net/sched/sch_generic.c:255 >>> dev_watchdog+0x156/0x1f0() >>> [ 5417.275474] NETDEV WAT

Re: igb and bnx2: "NETDEV WATCHDOG: transmit queue timed out" when skb has huge linear buffer

On 05/02/14 20:23, Zoltan Kiss wrote: On 04/02/14 19:47, Michael Chan wrote: On Fri, 2014-01-31 at 14:29 +0100, Zoltan Kiss wrote: [ 5417.275472] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x156/0x1f0() [ 5417.275474] NETDEV WATCHDOG: eth1 (bnx2): transmit queue 2 timed out

Re: igb and bnx2: "NETDEV WATCHDOG: transmit queue timed out" when skb has huge linear buffer

On 04/02/14 19:47, Michael Chan wrote: On Fri, 2014-01-31 at 14:29 +0100, Zoltan Kiss wrote: [ 5417.275472] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x156/0x1f0() [ 5417.275474] NETDEV WATCHDOG: eth1 (bnx2): transmit queue 2 timed out The dump shows an internal IRQ pending on MSIX

Re: igb and bnx2: NETDEV WATCHDOG: transmit queue timed out when skb has huge linear buffer

On 04/02/14 19:47, Michael Chan wrote: On Fri, 2014-01-31 at 14:29 +0100, Zoltan Kiss wrote: [ 5417.275472] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x156/0x1f0() [ 5417.275474] NETDEV WATCHDOG: eth1 (bnx2): transmit queue 2 timed out The dump shows an internal IRQ pending on MSIX

Re: igb and bnx2: NETDEV WATCHDOG: transmit queue timed out when skb has huge linear buffer

On 05/02/14 20:23, Zoltan Kiss wrote: On 04/02/14 19:47, Michael Chan wrote: On Fri, 2014-01-31 at 14:29 +0100, Zoltan Kiss wrote: [ 5417.275472] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x156/0x1f0() [ 5417.275474] NETDEV WATCHDOG: eth1 (bnx2): transmit queue 2 timed out

Re: igb and bnx2: NETDEV WATCHDOG: transmit queue timed out when skb has huge linear buffer

On 05/02/2014 20:23, Zoltan Kiss wrote: On 04/02/14 19:47, Michael Chan wrote: On Fri, 2014-01-31 at 14:29 +0100, Zoltan Kiss wrote: [ 5417.275472] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x156/0x1f0() [ 5417.275474] NETDEV WATCHDOG: eth1 (bnx2): transmit queue 2 timed out

Re: igb and bnx2: "NETDEV WATCHDOG: transmit queue timed out" when skb has huge linear buffer

On 31/01/14 18:56, Wei Liu wrote: On Thu, Jan 30, 2014 at 07:08:11PM +, Zoltan Kiss wrote: Hi, I've experienced some queue timeout problems mentioned in the subject with igb and bnx2 cards. I haven't seen them on other cards so far. I'm using XenServer with 3.10 Dom0 kernel (however igb

Re: igb and bnx2: "NETDEV WATCHDOG: transmit queue timed out" when skb has huge linear buffer

On Fri, 2014-01-31 at 14:29 +0100, Zoltan Kiss wrote: > [ 5417.275472] WARNING: at net/sched/sch_generic.c:255 > dev_watchdog+0x156/0x1f0() > [ 5417.275474] NETDEV WATCHDOG: eth1 (bnx2): transmit queue 2 timed out The dump shows an internal IRQ pending on MSIX vector 2 whic

Re: igb and bnx2: NETDEV WATCHDOG: transmit queue timed out when skb has huge linear buffer

On Fri, 2014-01-31 at 14:29 +0100, Zoltan Kiss wrote: [ 5417.275472] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x156/0x1f0() [ 5417.275474] NETDEV WATCHDOG: eth1 (bnx2): transmit queue 2 timed out The dump shows an internal IRQ pending on MSIX vector 2 which matches the the queue

Re: igb and bnx2: NETDEV WATCHDOG: transmit queue timed out when skb has huge linear buffer

On 31/01/14 18:56, Wei Liu wrote: On Thu, Jan 30, 2014 at 07:08:11PM +, Zoltan Kiss wrote: Hi, I've experienced some queue timeout problems mentioned in the subject with igb and bnx2 cards. I haven't seen them on other cards so far. I'm using XenServer with 3.10 Dom0 kernel (however igb

Re: igb and bnx2: "NETDEV WATCHDOG: transmit queue timed out" when skb has huge linear buffer

On Thu, Jan 30, 2014 at 07:08:11PM +, Zoltan Kiss wrote: > Hi, > > I've experienced some queue timeout problems mentioned in the > subject with igb and bnx2 cards. I haven't seen them on other cards > so far. I'm using XenServer with 3.10 Dom0 kernel (however igb were > already updated to

Re: igb and bnx2: "NETDEV WATCHDOG: transmit queue timed out" when skb has huge linear buffer

that may be useful. Thanks. Hi, Here is some: [ 5417.275463] [ cut here ] [ 5417.275472] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x156/0x1f0() [ 5417.275474] NETDEV WATCHDOG: eth1 (bnx2): transmit queue 2 timed out [ 5417.275476] Modules linked in: tun nfsv3

Re: igb and bnx2: NETDEV WATCHDOG: transmit queue timed out when skb has huge linear buffer

On Thu, Jan 30, 2014 at 07:08:11PM +, Zoltan Kiss wrote: Hi, I've experienced some queue timeout problems mentioned in the subject with igb and bnx2 cards. I haven't seen them on other cards so far. I'm using XenServer with 3.10 Dom0 kernel (however igb were already updated to latest

Re: igb and bnx2: NETDEV WATCHDOG: transmit queue timed out when skb has huge linear buffer

that may be useful. Thanks. Hi, Here is some: [ 5417.275463] [ cut here ] [ 5417.275472] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x156/0x1f0() [ 5417.275474] NETDEV WATCHDOG: eth1 (bnx2): transmit queue 2 timed out [ 5417.275476] Modules linked in: tun nfsv3

Re: igb and bnx2: "NETDEV WATCHDOG: transmit queue timed out" when skb has huge linear buffer

On Thu, 2014-01-30 at 19:08 +, Zoltan Kiss wrote: > I've experienced some queue timeout problems mentioned in the subject > with igb and bnx2 cards. Please provide the full tx timeout dmesg. bnx2 dumps some diagnostic information during tx timeout that may be useful. Thanks. -- To

igb and bnx2: "NETDEV WATCHDOG: transmit queue timed out" when skb has huge linear buffer

Hi, I've experienced some queue timeout problems mentioned in the subject with igb and bnx2 cards. I haven't seen them on other cards so far. I'm using XenServer with 3.10 Dom0 kernel (however igb were already updated to latest version), and there are Windows guests sending data through

igb and bnx2: NETDEV WATCHDOG: transmit queue timed out when skb has huge linear buffer

Hi, I've experienced some queue timeout problems mentioned in the subject with igb and bnx2 cards. I haven't seen them on other cards so far. I'm using XenServer with 3.10 Dom0 kernel (however igb were already updated to latest version), and there are Windows guests sending data through

Re: igb and bnx2: NETDEV WATCHDOG: transmit queue timed out when skb has huge linear buffer

On Thu, 2014-01-30 at 19:08 +, Zoltan Kiss wrote: I've experienced some queue timeout problems mentioned in the subject with igb and bnx2 cards. Please provide the full tx timeout dmesg. bnx2 dumps some diagnostic information during tx timeout that may be useful. Thanks. -- To

Re: NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out

Nick, You could try 7.3.21-k8-NAPI in tree or the out-of-tree version as Bjorn mentioned. To read and debug an old version driver is not a interesting thing for somebody to do. Thanks, Ethan On Tue, Dec 3, 2013 at 9:33 PM, Nick Pegg wrote: > On Mon, Dec 2, 2013 at 10:51 PM, Ethan Zhao

Re: NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out

Nick, You could try 7.3.21-k8-NAPI in tree or the out-of-tree version as Bjorn mentioned. To read and debug an old version driver is not a interesting thing for somebody to do. Thanks, Ethan On Tue, Dec 3, 2013 at 9:33 PM, Nick Pegg n...@nickpegg.com wrote: On Mon, Dec 2, 2013 at 10:51 PM,

Re: NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out

On Mon, Dec 2, 2013 at 10:51 PM, Ethan Zhao wrote: > Bjorn, >Seems not the same bug as http://sourceforge.net/p/e1000/bugs/367/ > , Nick is not running his kernel on bare metal, per the error log, > he runs his kernel as HVM DomU guest or Dom0 on XEN ? so just a check > of NULL will not

Re: NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out

On Mon, Dec 2, 2013 at 10:51 PM, Ethan Zhao ethan.ker...@gmail.com wrote: Bjorn, Seems not the same bug as http://sourceforge.net/p/e1000/bugs/367/ , Nick is not running his kernel on bare metal, per the error log, he runs his kernel as HVM DomU guest or Dom0 on XEN ? so just a check of

Re: NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out

e.net/p/e1000/bugs/367/ (no > real data there). > >> >> Nov 16 07:03:19 rx [ cut here ]-------- >> Nov 16 07:03:19 rx WARNING: at net/sched/sch_generic.c:255 >> dev_watchdog+0x25b/0x270() >> Nov 16 07:03:19 rx Hardware name: X8DT6 >> No

RE: [E1000-devel] NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out

: Nick Pegg [mailto:n...@nickpegg.com] Sent: Monday, December 02, 2013 2:57 PM To: linux-kernel@vger.kernel.org; e1000-de...@lists.sourceforge.net Subject: Re: [E1000-devel] NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out > Intel maintains newer drivers out-of-tree at >

Re: NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out

> Intel maintains newer drivers out-of-tree at > http://sourceforge.net/projects/e1000/, and it's possible this is some > bug that has already been fixed. The current version there looks like > e1000e-2.5.4, released 2013-09-05. > > Possible similar report:

Re: NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out

Intel maintains newer drivers out-of-tree at http://sourceforge.net/projects/e1000/, and it's possible this is some bug that has already been fixed. The current version there looks like e1000e-2.5.4, released 2013-09-05. Possible similar report: http://sourceforge.net/p/e1000/bugs/367/ (no

RE: [E1000-devel] NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out

: Nick Pegg [mailto:n...@nickpegg.com] Sent: Monday, December 02, 2013 2:57 PM To: linux-kernel@vger.kernel.org; e1000-de...@lists.sourceforge.net Subject: Re: [E1000-devel] NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out Intel maintains newer drivers out-of-tree at http

Re: NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out

/sch_generic.c:255 dev_watchdog+0x25b/0x270() Nov 16 07:03:19 rx Hardware name: X8DT6 Nov 16 07:03:19 rx NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out Nov 16 07:03:19 rx Modules linked in: xt_u32 xt_physdev ip6table_mangle ip6_tables ebt_comment ebt_set ebt_arp ebt_limit ebt_ip6 ebt_ip

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

to this list. Thanks! -Nick Nov 16 07:03:19 rx [ cut here ] Nov 16 07:03:19 rx WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x25b/0x270() Nov 16 07:03:19 rx Hardware name: X8DT6 Nov 16 07:03:19 rx NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out

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

to this list. Thanks! -Nick Nov 16 07:03:19 rx [ cut here ] Nov 16 07:03:19 rx WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x25b/0x270() Nov 16 07:03:19 rx Hardware name: X8DT6 Nov 16 07:03:19 rx NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out

Re: niu lock-up (Transmit timed out, resetting) and NETDEV WATCHDOG

Hi > On 26 March 2013 13:44, Andrew Brooks wrote: >> Using niu driver for this card: Oracle/SUN Multithreaded 10-Gigabit >> Ethernet Network Controller and after a period the interface will hang >> with errors every 5 seconds >> "niu: xxx: eth2: Transmit timed out, resetting" Here's more

Re: niu lock-up (Transmit timed out, resetting) and NETDEV WATCHDOG

Hi On 26 March 2013 13:44, Andrew Brooks a...@sat.dundee.ac.uk wrote: Using niu driver for this card: Oracle/SUN Multithreaded 10-Gigabit Ethernet Network Controller and after a period the interface will hang with errors every 5 seconds niu: xxx: eth2: Transmit timed out, resetting Here's

Re: niu lock-up (Transmit timed out, resetting) and NETDEV WATCHDOG

" > > Sometimes also in syslog are messages > WARNING: at sch_generic:255 dev_watchdog > NETDEV WATCHDOG: eth2 (niu): transmit queue 10 timed out Do you think this could be caused by a problem I've seen reported by other machines on the network "received unsolicited ack for DL_UNITDAT

Re: niu lock-up (Transmit timed out, resetting) and NETDEV WATCHDOG

also in syslog are messages WARNING: at sch_generic:255 dev_watchdog NETDEV WATCHDOG: eth2 (niu): transmit queue 10 timed out Do you think this could be caused by a problem I've seen reported by other machines on the network received unsolicited ack for DL_UNITDATA_REQ on nxge0 ? Is there some bad

niu lock-up (Transmit timed out, resetting) and NETDEV WATCHDOG

es WARNING: at sch_generic:255 dev_watchdog NETDEV WATCHDOG: eth2 (niu): transmit queue 10 timed out Does anyone know which driver revision has fixed this problem or if it's still buggy? Thanks! Andrew P.S. My guess is the commit on 2012-10-02 ?? 2013-02-04 ethernet: Remove unnecessary alloc/OO

niu lock-up (Transmit timed out, resetting) and NETDEV WATCHDOG

: at sch_generic:255 dev_watchdog NETDEV WATCHDOG: eth2 (niu): transmit queue 10 timed out Does anyone know which driver revision has fixed this problem or if it's still buggy? Thanks! Andrew P.S. My guess is the commit on 2012-10-02 ?? 2013-02-04 ethernet: Remove unnecessary alloc/OOM messages

BUG: ipheth - NETDEV WATCHDOG: eth1 (ipheth): transmit queue 0 timed out

Mar 20 04:55:33 2013] WARNING: at /home/abuild/rpmbuild/BUILD/kernel-desktop-3.8.3/linux-3.8/net/sched/sch_generic.c:254 dev_watchdog+0x1e0/0x1f0() [Wed Mar 20 04:55:33 2013] Hardware name: 200763G [Wed Mar 20 04:55:33 2013] NETDEV WATCHDOG: eth1 (ipheth): transmit queue 0 timed out [Wed Mar 20 04

BUG: ipheth - NETDEV WATCHDOG: eth1 (ipheth): transmit queue 0 timed out

Mar 20 04:55:33 2013] WARNING: at /home/abuild/rpmbuild/BUILD/kernel-desktop-3.8.3/linux-3.8/net/sched/sch_generic.c:254 dev_watchdog+0x1e0/0x1f0() [Wed Mar 20 04:55:33 2013] Hardware name: 200763G [Wed Mar 20 04:55:33 2013] NETDEV WATCHDOG: eth1 (ipheth): transmit queue 0 timed out [Wed Mar 20 04

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&

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

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 No respons

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

-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

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

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

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.

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

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

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:

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,

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

[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

[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

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

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

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.

Re: NETDEV WATCHDOG (3Com 3c905 adapter)

Steffen Klassert wrote: On Fri, Nov 23, 2007 at 04:52:39PM +0100, BERTRAND Joël wrote: BERTRAND Joël wrote: Hello, Since I have installed a 2.6.23.1 linux kernel on my U60, I can see several NETDEV WATCHDOG. This trouble never occurs with 2.6.23-rc4. This bug occurs after a random

Re: NETDEV WATCHDOG (3Com 3c905 adapter)

On Fri, Nov 23, 2007 at 04:52:39PM +0100, BERTRAND Joël wrote: > BERTRAND Joël wrote: > >Hello, > > > >Since I have installed a 2.6.23.1 linux kernel on my U60, I can see > >several NETDEV WATCHDOG. This trouble never occurs with 2.6.23-rc4. > >This

Re: NETDEV WATCHDOG (3Com 3c905 adapter)

On Fri, Nov 23, 2007 at 04:52:39PM +0100, BERTRAND Joël wrote: BERTRAND Joël wrote: Hello, Since I have installed a 2.6.23.1 linux kernel on my U60, I can see several NETDEV WATCHDOG. This trouble never occurs with 2.6.23-rc4. This bug occurs after a random uptime. I have

Re: NETDEV WATCHDOG (3Com 3c905 adapter)

Steffen Klassert wrote: On Fri, Nov 23, 2007 at 04:52:39PM +0100, BERTRAND Joël wrote: BERTRAND Joël wrote: Hello, Since I have installed a 2.6.23.1 linux kernel on my U60, I can see several NETDEV WATCHDOG. This trouble never occurs with 2.6.23-rc4. This bug occurs after a random

Re: NETDEV WATCHDOG (3Com 3c905 adapter)

BERTRAND Joël wrote: Hello, Since I have installed a 2.6.23.1 linux kernel on my U60, I can see several NETDEV WATCHDOG. This trouble never occurs with 2.6.23-rc4. This bug occurs after a random uptime. I have made the same constation this evening on a amd64/up with two 3C905

Re: NETDEV WATCHDOG (3Com 3c905 adapter)

BERTRAND Joël wrote: Hello, Since I have installed a 2.6.23.1 linux kernel on my U60, I can see several NETDEV WATCHDOG. This trouble never occurs with 2.6.23-rc4. This bug occurs after a random uptime. I have made the same constation this evening on a amd64/up with two 3C905

Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"

Hi, after reading about issues with the nics on kontron boards I did a bios upgrade, but this did not change anything. However, yesterday the nic (onboard) I used died. No link at all, after switching to the next onboard nic I got a NETDEV transmit timeout with that one on kernel 2.6.22-r2. It

Re: PROBLEM: 2.6.23-rc NETDEV WATCHDOG: eth0: transmit timed out

Hi, after reading about issues with the nics on kontron boards I did a bios upgrade, but this did not change anything. However, yesterday the nic (onboard) I used died. No link at all, after switching to the next onboard nic I got a NETDEV transmit timeout with that one on kernel 2.6.22-r2. It

Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"

Hi Francois, this is what I found and sent: The error exists from patch 2 on. I did some network testing with patch 1 and currently use it and have no errors so far. >From my experiences up to now patch 1 should be error free. Do you need additional info? 2007/9/12, Francois Romieu <[EMAIL

Re: PROBLEM: 2.6.23-rc NETDEV WATCHDOG: eth0: transmit timed out

Hi Francois, this is what I found and sent: The error exists from patch 2 on. I did some network testing with patch 1 and currently use it and have no errors so far. From my experiences up to now patch 1 should be error free. Do you need additional info? 2007/9/12, Francois Romieu [EMAIL

Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"

Karl Meyer <[EMAIL PROTECTED]> : [...] > am am looking for this issue for some time now, but there where no > errors in 2.6.22-r2 (gentoo speak, I guess this is 2.6.22.2 > officially), I also ran git-bisect (for more information see the older > messages in this thread). 2.6.22-r2 in gentoo is

Re: PROBLEM: 2.6.23-rc NETDEV WATCHDOG: eth0: transmit timed out

Karl Meyer [EMAIL PROTECTED] : [...] am am looking for this issue for some time now, but there where no errors in 2.6.22-r2 (gentoo speak, I guess this is 2.6.22.2 officially), I also ran git-bisect (for more information see the older messages in this thread). 2.6.22-r2 in gentoo is based on

Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"

; > On 01/09/07, Karl Meyer <[EMAIL PROTECTED]> wrote: > > This is what happened today: > > > > Sep 1 21:08:01 frege NETDEV WATCHDOG: eth0: transmit timed out > > frege ~ # uname -r > > 2.6.22.5-cfs-v20.5 > > Can you reproduce this on 2.6.22 (not 2.

Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"

Hi, On 01/09/07, Karl Meyer <[EMAIL PROTECTED]> wrote: > This is what happened today: > > Sep 1 21:08:01 frege NETDEV WATCHDOG: eth0: transmit timed out > frege ~ # uname -r > 2.6.22.5-cfs-v20.5 Can you reproduce this on 2.6.22 (not 2.6.22.x - it might be a -stable regressi

Re: PROBLEM: 2.6.23-rc NETDEV WATCHDOG: eth0: transmit timed out

Hi, On 01/09/07, Karl Meyer [EMAIL PROTECTED] wrote: This is what happened today: Sep 1 21:08:01 frege NETDEV WATCHDOG: eth0: transmit timed out frege ~ # uname -r 2.6.22.5-cfs-v20.5 Can you reproduce this on 2.6.22 (not 2.6.22.x - it might be a -stable regression)? Regards, Michal

Re: PROBLEM: 2.6.23-rc NETDEV WATCHDOG: eth0: transmit timed out

, Karl Meyer [EMAIL PROTECTED] wrote: This is what happened today: Sep 1 21:08:01 frege NETDEV WATCHDOG: eth0: transmit timed out frege ~ # uname -r 2.6.22.5-cfs-v20.5 Can you reproduce this on 2.6.22 (not 2.6.22.x - it might be a -stable regression)? Regards, Michal -- LOG http

Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"

This is what happened today: Sep 1 21:08:01 frege NETDEV WATCHDOG: eth0: transmit timed out frege ~ # uname -r 2.6.22.5-cfs-v20.5 2007/8/16, Francois Romieu <[EMAIL PROTECTED]>: > (please do not remove the netdev Cc:) > > Francois Romieu <[EMAIL PROTECTED]> : > [...]

Re: PROBLEM: 2.6.23-rc NETDEV WATCHDOG: eth0: transmit timed out

This is what happened today: Sep 1 21:08:01 frege NETDEV WATCHDOG: eth0: transmit timed out frege ~ # uname -r 2.6.22.5-cfs-v20.5 2007/8/16, Francois Romieu [EMAIL PROTECTED]: (please do not remove the netdev Cc:) Francois Romieu [EMAIL PROTECTED] : [...] If it does not work I'll dissect

Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"

On 21-08-2007 12:56, Karl Meyer wrote: > fyi: > I do not know whether it is related to the problem, but since using > the version you told me there are these entries is my log: > frege Hangcheck: hangcheck value past margin! ... BTW, I don't know wheter it's related too, but I think you should

Re: PROBLEM: 2.6.23-rc NETDEV WATCHDOG: eth0: transmit timed out

On 21-08-2007 12:56, Karl Meyer wrote: fyi: I do not know whether it is related to the problem, but since using the version you told me there are these entries is my log: frege Hangcheck: hangcheck value past margin! ... BTW, I don't know wheter it's related too, but I think you should try

  1   2   3   >