[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADDKRnAHJAZBittLCFxjgWa1AWKxD7a4hn4v=xvax=ergkKjxA@mail.gmail.com>
Date: Wed, 6 Feb 2013 17:55:28 +0100
From: Jörg Otte <jrg.otte@...il.com>
To: Francois Romieu <romieu@...zoreil.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [3.8-rc] regression: NETDEV WATCHDOG: eth0 (r8169): transmit
queue 0 timed out
2013/2/3 Jörg Otte <jrg.otte@...il.com>:
> 2013/1/6 Jörg Otte <jrg.otte@...il.com>:
>> 2013/1/5 Francois Romieu <romieu@...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 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
>>
>>
>>> 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 majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists