From: Sasha Neftin <sasha.neftin@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] What to do with info log message: `e1000e: EEE TX LPI TIMER: 00000011`?
Date: Sun, 25 Jul 2021 08:33:23 +0300 [thread overview]
Message-ID: <958198de-818f-cebb-ec68-06dd2d6accb8@intel.com> (raw)
In-Reply-To: <04a175b6-797c-ab25-dbd4-f8bdbb165674@molgen.mpg.de>
On 7/23/2021 15:28, Paul Menzel wrote:
> Dear David, dear Linux folks,
>
>
> On several devices, like the Dell OptiPlex 3620, Linux 5.10.47 (and
> others) log the message below with info level (often during shutdown):
>
> ??? e1000e: EEE TX LPI TIMER: 00000011
>
> ??? $ git grep "LPI TIMER"
> ??? drivers/net/ethernet/intel/e1000e/netdev.c:???? pr_info("EEE TX LPI
> TIMER: %08X\n",
>
Hello Paul,
I believe it is a simple debug print that has forgotten to remove.(more
than seven years ago). It is comes just to inform: Low Power IDLE Entry
Time - minimum time between low power idle entry and exit request.
You can process the patch to remove this line. (or I can do it and add
you as "Suggested-by").
Thanks,
Sasha
>
> What information is that supposed to provide? For a normal user it looks
> like spam.
>
> Could you please extend the message what to do about it? Or should it be
> made a debug message?
>
>
> Kind regards,
>
> Paul
> _______________________________________________
> Intel-wired-lan mailing list
> Intel-wired-lan at osuosl.org
> https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
prev parent reply other threads:[~2021-07-25 5:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 12:28 [Intel-wired-lan] What to do with info log message: `e1000e: EEE TX LPI TIMER: 00000011`? Paul Menzel
2021-07-25 5:33 ` Sasha Neftin [this message]
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=958198de-818f-cebb-ec68-06dd2d6accb8@intel.com \
--to=sasha.neftin@intel.com \
--cc=intel-wired-lan@osuosl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.