Description of problem: The network device eth0 (p5p1) is consuming significant amount of power, when no wired connection. This can be seen in the powertop report below: Power Consumption Summary 651.0 wakeups/second, 11.2 GPU ops/second, 0.0 VFS ops/sec, 9.7 GFX wakes/sec and 8.4% CPU use Power est. Usage Events/s Category Description 12.4 W 100.0% Device Display backlight 8.15 W 0.0 pkts/s Device Network interface: eth0 (r8169) 830 mW 1.6% 237.9 Process /usr/bin/pulseaudio --start 175 mW 2.6% 91.5 Process skype 93.9 mW 1.4% 35.5 Process /usr/bin/gnome-shell 51.9 mW 0.8% 0.9 Process gnome-shell 44.8 mW 0.7% 13.9 Process elegance-colors 21.2 mW 1.9 pkts/s Device Network interface: wlo1 (ath9k) 15.1 mW 0.2% 16.8 Process /usr/lib64/firefox/firefox 10.0 mW 0.1% 77.4 Timer hrtimer_wakeup 8.95 mW 0.1% 3.0 Process /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-6AnIFT/database -seat seat0 -nolisten tcp vt1 Version-Release number of selected component (if applicable): the device driver is r8169 uname -a gives: Linux ma-fedora 3.12.7-300.fc20.x86_64 #1 SMP Fri Jan 10 15:35:31 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux lshw gives: *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@0000:05:00.0 logical name: eth0 version: 07 serial: [REMOVED] size: 10Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8168e-3_0.0.4 03/27/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:50 ioport:2000(size=256) memory:d0404000-d0404fff memory:d0400000-d0403fff How reproducible: Every time Steps to Reproduce: 1. Boot to fedora 20 2. NO lan cable is plugged in 3. open Powertop and see the abnormal result Actual results: Network devcie eth0 consume a lot of power Expected results: much less power (less then 1 W I believe, which is what I remember for my old fedora18 installation) is consumed by eth0, Additional info:
Hello. I'm unsure whether 'ethtool' is the right component for this report. I would start with the 'powertop' tool so that we know why it shows such values. Maybe it's a matter of calibration only. I'm switching the component to powertop. Regards, Jaromir.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.