All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: intel-wired-lan@lists.osuosl.org
Subject: [Intel-wired-lan] Fw: [Bug 218761] New: e1000e: One core of cpu reach 100% usage, after connecting ethernet.
Date: Mon, 22 Apr 2024 11:41:48 -0700	[thread overview]
Message-ID: <20240422114148.39b71a63@hermes.local> (raw)



Begin forwarded message:

Date: Mon, 22 Apr 2024 18:39:38 +0000
From: bugzilla-daemon@kernel.org
To: stephen@networkplumber.org
Subject: [Bug 218761] New: e1000e: One core of cpu reach 100% usage, after connecting ethernet.


https://bugzilla.kernel.org/show_bug.cgi?id=218761

            Bug ID: 218761
           Summary: e1000e: One core of cpu reach 100% usage, after
                    connecting ethernet.
           Product: Networking
           Version: 2.5
          Hardware: Intel
                OS: Linux
            Status: NEW
          Keywords: trivial
          Severity: high
          Priority: P3
         Component: Other
          Assignee: stephen@networkplumber.org
          Reporter: rafal200725@gmail.com
        Regression: No

When I connect ethernet to my laptop after it booted, one core of cpu reach
100%, and system start being unusable, command stop working.

On kernel 5.15 LTS, theres no issue, only on highest.

Bug appear for me in 6.8.7 stable and 6.6.28 LTS. (but may also on anothers,
that only I tested). It may be ralated to new commits from about 2 weeks ago,
that changes something in this driver.

Output from "lspci -k | grep -iA3 Ethernet":
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-LM
(rev 21)
        Subsystem: Lenovo Device 225d
        Kernel driver in use: e1000e
        Kernel modules: e1000e

In advance sorry for my English I'm still learning this language.

If you need more info, just tell. I'm newbie so you need to guide me, to get
some logs etc.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2024-04-22 18:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240422114148.39b71a63@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.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 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.