From: Takashi Iwai <tiwai@suse.de>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: regressions@lists.linux.dev, intel-wired-lan@lists.osuosl.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [REGRESSION] e1000e probe/link detection fails since 6.2 kernel
Date: Tue, 28 Mar 2023 14:40:33 +0200 [thread overview]
Message-ID: <87jzz13v7i.wl-tiwai@suse.de> (raw)
Hi,
we've got a regression report for e1000e device on Lenovo T460p since
6.2 kernel (with openSUSE Tumbleweed). The details are found in
https://bugzilla.opensuse.org/show_bug.cgi?id=1209254
It seems that the driver can't detect the 1000Mbps but only 10/100Mbps
link, eventually making the device unusable.
On 6.1.12:
[ 5.119117] e1000e: Intel(R) PRO/1000 Network Driver
[ 5.119120] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 5.121754] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 7.905526] e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): Failed to disable ULP
[ 7.988925] e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): registered PHC clock
[ 8.069935] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 50:7b:9d:cf:13:43
[ 8.069942] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
[ 8.072691] e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: 1000FF-0FF
[ 11.643919] e1000e 0000:00:1f.6 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
[ 15.437437] e1000e 0000:00:1f.6 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
On 6.2.4:
[ 4.344140] e1000e: Intel(R) PRO/1000 Network Driver
[ 4.344143] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 4.344933] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 7.113334] e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): Failed to disable ULP
[ 7.201715] e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): registered PHC clock
[ 7.284038] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 50:7b:9d:cf:13:43
[ 7.284044] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
[ 7.284125] e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: 1000FF-0FF
[ 10.897973] e1000e 0000:00:1f.6 eth0: NIC Link is Up 10 Mbps Full Duplex, Flow Control: None
[ 10.897977] e1000e 0000:00:1f.6 eth0: 10/100 speed: disabling TSO
[ 14.710059] e1000e 0000:00:1f.6 eth0: NIC Link is Up 10 Mbps Full Duplex, Flow Control: None
[ 14.710064] e1000e 0000:00:1f.6 eth0: 10/100 speed: disabling TSO
[ 59.894807] e1000e 0000:00:1f.6 eth0: NIC Link is Up 10 Mbps Full Duplex, Flow Control: None
[ 59.894812] e1000e 0000:00:1f.6 eth0: 10/100 speed: disabling TSO
[ 63.808662] e1000e 0000:00:1f.6 eth0: NIC Link is Up 10 Mbps Full Duplex, Flow Control: None
[ 63.808668] e1000e 0000:00:1f.6 eth0: 10/100 speed: disabling TSO
The same problem persists with 6.3-rc3.
Can you guys check what can go wrong, or if there is a fix?
Thanks!
Takashi
next reply other threads:[~2023-03-28 12:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 12:40 Takashi Iwai [this message]
2023-03-28 14:39 ` [Intel-wired-lan] [REGRESSION] e1000e probe/link detection fails since 6.2 kernel Paul Menzel
2023-03-28 15:16 ` Takashi Iwai
2023-03-29 8:40 ` Bagas Sanjaya
2023-03-29 8:48 ` Takashi Iwai
2023-03-29 19:12 ` Jakub Kicinski
2023-03-30 6:30 ` Takashi Iwai
2023-03-30 10:35 ` Takashi Iwai
2023-04-02 7:38 ` Neftin, Sasha
2023-03-29 8:43 ` Bagas Sanjaya
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=87jzz13v7i.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).