* NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
@ 2013-12-30 9:57 Fejes József
2013-12-30 13:22 ` Lukas Tribus
2013-12-30 23:38 ` Francois Romieu
0 siblings, 2 replies; 6+ messages in thread
From: Fejes József @ 2013-12-30 9:57 UTC (permalink / raw)
To: netdev
Hi,
I'm having the issue mentioned in the subject line with the latest
stable kernel, 3.12.6.
This network controller is integrated into a D945GSEJT motherboard, dmesg info:
[ 2.216912] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 2.217341] r8169 0000:01:00.0: irq 44 for MSI/MSI-X
[ 2.217852] r8169 0000:01:00.0 eth0: RTL8168d/8111d at 0xdff16000,
00:27:0e:01:af:d5, XID 081000c0 IRQ 44
[ 2.217869] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200
bytes, tx checksumming: ko]
I pasted the syslog message here: http://pastebin.com/6pqd03Jc
Can you please help me with this issue?
Please CC me, I'm not subscribed.
Thanks, Jozsef
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
2013-12-30 9:57 NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out Fejes József
@ 2013-12-30 13:22 ` Lukas Tribus
2013-12-30 23:38 ` Francois Romieu
1 sibling, 0 replies; 6+ messages in thread
From: Lukas Tribus @ 2013-12-30 13:22 UTC (permalink / raw)
To: Fejes József, netdev
Hi,
> I'm having the issue mentioned in the subject line with the latest
> stable kernel, 3.12.6.
>
> This network controller is integrated into a D945GSEJT motherboard, dmesg info:
>
> [ 2.216912] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
> [ 2.217341] r8169 0000:01:00.0: irq 44 for MSI/MSI-X
> [ 2.217852] r8169 0000:01:00.0 eth0: RTL8168d/8111d at 0xdff16000,
> 00:27:0e:01:af:d5, XID 081000c0 IRQ 44
> [ 2.217869] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200
> bytes, tx checksumming: ko]
>
> I pasted the syslog message here: http://pastebin.com/6pqd03Jc
> CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.11.6-joco #1
Looks like 3.11.6, not 3.12.6?
Lukas
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
2013-12-30 9:57 NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out Fejes József
2013-12-30 13:22 ` Lukas Tribus
@ 2013-12-30 23:38 ` Francois Romieu
2013-12-31 11:27 ` Fejes József
1 sibling, 1 reply; 6+ messages in thread
From: Francois Romieu @ 2013-12-30 23:38 UTC (permalink / raw)
To: Fejes József; +Cc: netdev
Fejes József <jozsef.fejes@gmail.com> :
[...]
> I'm having the issue mentioned in the subject line with the latest
> stable kernel, 3.12.6.
>
> This network controller is integrated into a D945GSEJT motherboard, dmesg info:
It's thus an old setup (bridge included), nothing changed recently
and it qualifies as a regression, right ?
If so, wherefrom ?
--
Ueimor
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
2013-12-30 23:38 ` Francois Romieu
@ 2013-12-31 11:27 ` Fejes József
2014-01-01 22:38 ` Francois Romieu
0 siblings, 1 reply; 6+ messages in thread
From: Fejes József @ 2013-12-31 11:27 UTC (permalink / raw)
To: Francois Romieu; +Cc: netdev
Hi,
The paste is from 3.11.6 actually, but 3.12.6 produces the same
behavior. Nothing changed recently in my networking setup.
Immediately, when I plug in my laptop to that interface, the error is
produced, ifconfig on the machine shows that packets are sent out, but
I see no received packets in my laptop on the other end.
I haven't used that interface for quite some time, a year at most. I
keep up to date with the stable kernels, so a version change broke it,
but I'm not sure which. Would it be the best course of action if I
tried some older versions?
Best regards, Jozsef
On Tue, Dec 31, 2013 at 12:38 AM, Francois Romieu <romieu@fr.zoreil.com> wrote:
> Fejes József <jozsef.fejes@gmail.com> :
> [...]
>> I'm having the issue mentioned in the subject line with the latest
>> stable kernel, 3.12.6.
>>
>> This network controller is integrated into a D945GSEJT motherboard, dmesg info:
>
> It's thus an old setup (bridge included), nothing changed recently
> and it qualifies as a regression, right ?
>
> If so, wherefrom ?
>
> --
> Ueimor
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
2013-12-31 11:27 ` Fejes József
@ 2014-01-01 22:38 ` Francois Romieu
2014-01-05 7:28 ` Fejes József
0 siblings, 1 reply; 6+ messages in thread
From: Francois Romieu @ 2014-01-01 22:38 UTC (permalink / raw)
To: Fejes József; +Cc: netdev
Fejes József <jozsef.fejes@gmail.com> :
[...]
> The paste is from 3.11.6 actually, but 3.12.6 produces the same
> behavior. Nothing changed recently in my networking setup.
> Immediately, when I plug in my laptop to that interface, the error is
> produced, ifconfig on the machine shows that packets are sent out, but
> I see no received packets in my laptop on the other end.
Ok.
Could you check the irq count and ethtool -S eth0 as well ?
Does the laptop also include a different operating system ?
> I haven't used that interface for quite some time, a year at most. I
> keep up to date with the stable kernels, so a version change broke it,
> but I'm not sure which. Would it be the best course of action if I
> tried some older versions?
Yes, please do.
There has been no specific change in this timeframe for the chipset you
use (RTL_GIGA_MAC_VER_25). The problem may have been unnoticed for a
rather long time. :o/
--
Ueimor
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
2014-01-01 22:38 ` Francois Romieu
@ 2014-01-05 7:28 ` Fejes József
0 siblings, 0 replies; 6+ messages in thread
From: Fejes József @ 2014-01-05 7:28 UTC (permalink / raw)
To: Francois Romieu; +Cc: netdev
> Could you check the irq count and ethtool -S eth0 as well ?
Here you go: http://pastebin.com/acabFBHv
> Does the laptop also include a different operating system ?
Yes, Windows 7.
>> I haven't used that interface for quite some time, a year at most. I
>> keep up to date with the stable kernels, so a version change broke it,
>> but I'm not sure which. Would it be the best course of action if I
>> tried some older versions?
>
> Yes, please do.
>
> There has been no specific change in this timeframe for the chipset you
> use (RTL_GIGA_MAC_VER_25). The problem may have been unnoticed for a
> rather long time. :o/
I booted into an old kernel I found in the Debian repository: Linux
wicklow 3.2.0-4-686-pae #1 SMP Debian 3.2.53-2 i686 GNU/Linux
And the same issue happened. Queue times out, no packets are received
on the other end.
Could it be that this regression ended up in this long-term supported
kernel? Or could it be a hardware problem? My Windows laptop's
ethernet definitely works in other places, so could be the cable or
the integrated NIC in the Linux machine...
Best regards,
Jozsef
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-01-05 7:28 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-12-30 9:57 NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out Fejes József
2013-12-30 13:22 ` Lukas Tribus
2013-12-30 23:38 ` Francois Romieu
2013-12-31 11:27 ` Fejes József
2014-01-01 22:38 ` Francois Romieu
2014-01-05 7:28 ` Fejes József
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).