On Thursday 25 September 2014 01:54 PM, Stefano wrote:
from some morning, when I boot my laptop I have a lot of lines like
Sep 25 08:10:06 hpdv5 laptop-mode: Laptop mode
Sep 25 08:10:06 hpdv5 laptop-mode: enabled, not active
Sep 25 08:10:06 hpdv5 kernel: [ 76.966266] r8169 0000:03:00.0 eth0:
rtl_phyar_cond == 1 (loop: 20, delay: 25).
Sep 25 08:10:06 hpdv5 kernel: [ 76.967192] r8169 0000:03:00.0 eth0:
rtl_phyar_cond == 1 (loop: 20, delay: 25).
Sep 25 08:10:06 hpdv5 kernel: [ 76.967963] r8169 0000:03:00.0 eth0:
rtl_phyar_cond == 1 (loop: 20, delay: 25).
Sep 25 08:10:06 hpdv5 kernel: [ 76.968742] r8169 0000:03:00.0 eth0:
rtl_phyar_cond == 1 (loop: 20, delay: 25).
Sep 25 08:10:06 hpdv5 avahi-daemon[2365]: Joining mDNS multicast group on
interface eth0.IPv4 with address 192.168.1.40.
Sep 25 08:10:06 hpdv5 avahi-daemon[2365]: New relevant interface eth0.IPv4 for
mDNS.
Sep 25 08:10:06 hpdv5 avahi-daemon[2365]: Registering new address record for
192.168.1.40 on eth0.IPv4.
Sep 25 08:10:06 hpdv5 kernel: [ 76.997522] r8169 0000:03:00.0 eth0: link down
Sep 25 08:10:06 hpdv5 kernel: [ 76.997613] IPv6: ADDRCONF(NETDEV_UP): eth0:
link is not ready
and the led on my router show the link down.
I recently bought an HP laptop and was given the same NIC.
14:18:27 rrs@learner:~$ dmesg | grep -i r8169
[ 15.871007] r8169 0000:0f:00.0: firmware: direct-loading firmware
rtl_nic/rtl8168g-2.fw
[ 15.913285] r8169 0000:0f:00.0 eth0: link down
[ 50.541260] r8169 0000:0f:00.0 eth0: link down
[38935.041500] r8169 0000:0f:00.0 eth0: link down
[38935.189645] r8169 0000:0f:00.0 eth0: link down
[49182.668076] r8169 0000:0f:00.0 eth0: link down
[49207.921116] r8169 0000:0f:00.0 eth0: link down
[49209.894375] r8169 0000:0f:00.0: no hotplug settings from platform
[49211.957799] r8169 0000:0f:00.0 eth0: link down
[49216.449479] r8169 0000:0f:00.0 eth0: link down
[64739.158471] r8169 0000:0f:00.0 eth0: link down
[64741.412907] r8169 0000:0f:00.0: no hotplug settings from platform
[64744.395701] r8169 0000:0f:00.0 eth0: link down
[64744.531811] r8169 0000:0f:00.0 eth0: link down
[64748.150777] r8169 0000:0f:00.0 eth0: link down
[67293.376212] r8169 0000:0f:00.0 eth0: link down
[67295.343379] r8169 0000:0f:00.0: no hotplug settings from platform
[67297.329963] r8169 0000:0f:00.0 eth0: link down
[67302.085830] r8169 0000:0f:00.0 eth0: link down
[76245.133588] r8169 0000:0f:00.0: no hotplug settings from platform
[76246.900415] r8169 0000:0f:00.0 eth0: rtl_ocp_gphy_cond == 1 (loop:
10, delay: 25).
[76246.900784] r8169 0000:0f:00.0 eth0: rtl_ocp_gphy_cond == 1 (loop:
10, delay: 25).
[76246.901159] r8169 0000:0f:00.0 eth0: rtl_ocp_gphy_cond == 1 (loop:
10, delay: 25).
[76246.960167] r8169 0000:0f:00.0 eth0: link down
[76248.565476] r8169 0000:0f:00.0 eth0: link down
I haven't faced your problem because I haven't used the ethernet NIC
much. I am on the wifi only.
We made a recent power saving change in the ethernet module to ensure
that we actually power down the device.
commit 8fff5eb2bfdde0fa15d8e7813d2399af78d1f064
Author: Stefan Huber <[email protected]>
Date: Sun May 25 09:41:20 2014 +0200
ethernet: replace sysfs/enabled by 'ip link down'
Disabeling the ethernet pci device via "echo 0" to sysfs attr "enabled"
does not necessarily power down the device but rather decrements the
enabled counter. Even if the counter reaches 0 the device may still
drain power.
Shutting down the ethernet device via 'ip link set dev DEV down',
however, reduces power consumptions to 0 mW as indicated by powertop.
The idea is to completely disable the battery when on battery. It is a
use case.
Can you check what the settings are for the following in
/etc/laptop-mode/conf.d/ethernet.conf ?
DISABLE_ETHERNET_ON_BATTERY=1
If it is set to 1, you need to set it to 0, and then re-test your scenario.
--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
