mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Realtek linux nic maintainers <nic_swsd@realtek.com>,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: Realtek NIC uses over 1 Watt with no traffic
Date: Tue, 20 Nov 2018 21:20:07 +0100	[thread overview]
Message-ID: <7714a7b7-ca22-19ea-499a-e2d60f3c9fb5@molgen.mpg.de> (raw)
In-Reply-To: <20181120144556.GC18335@lunn.ch>

Dear Andrew,


Am 20.11.18 um 15:45 schrieb Andrew Lunn:
> On Tue, Nov 20, 2018 at 09:40:25AM +0100, Paul Menzel wrote:

>> Using Ubuntu 18.10, Linux 4.18.0-11-generic, PowerTOP 2.9 shows, the NIC
>> uses 1.77 Watts. A network cable is plugged in, but there is no real traffic
>> according to `iftop`. Only an email program is running.
>>
>>      $ lspci -nn -s 3:00.1
>>      03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
>> RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev
>> 12)
>>
>> Is that a measurement error, or does the NIC really need that much power?

> This sounds like Energy Efficient Ethernet, EEE, is not enabled.

No, idea if the router from my provider supports that.

> What does ethtool --show-eee ethX say?

     $ sudo ethtool --show-eee enp3s0f1
     Cannot get EEE settings: Operation not supported


Kind regards,

Paul

  parent reply	other threads:[~2018-11-20 20:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20  8:40 Paul Menzel
2018-11-20 14:45 ` Andrew Lunn
2018-11-20 20:14   ` Heiner Kallweit
2018-11-20 20:31     ` Paul Menzel
2018-11-20 21:06       ` Heiner Kallweit
2018-11-20 22:25         ` Paul Menzel
2018-11-20 22:29           ` Heiner Kallweit
2018-11-20 20:20   ` Paul Menzel [this message]
2018-11-20 20:37     ` Andrew Lunn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7714a7b7-ca22-19ea-499a-e2d60f3c9fb5@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=hkallweit1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®