Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Neftin, Sasha" <sasha.neftin@intel.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	"Avivi, Amir" <amir.avivi@intel.com>,
	"Ruinskiy, Dima" <dima.ruinskiy@intel.com>,
	"Fuxbrumer, Devora" <devora.fuxbrumer@intel.com>
Cc: intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] Link does not come up after resuming from ACPI S3
Date: Sun, 2 Oct 2022 09:57:23 +0300	[thread overview]
Message-ID: <d287a371-2a26-04f7-9adc-c7d8a19bfc14@intel.com> (raw)
In-Reply-To: <53c37a6f-c8cd-63d6-696f-6b50b70f78ea@molgen.mpg.de>

On 9/30/2022 18:56, Paul Menzel wrote:
> Dear Linux folks,
> 
> 
> On a Dell Latitude E7250 with Debian sid/unstable, resuming Linux 5.19.6 
> and connecting an Ethernet cable, the link did not come up.
Hello Paul,
What is the device ID you tried to operate on your board? Could you 
provide whole lspci output and particular for:
lspci -s 0000:00:19.0 -vvv and lspci -s 0000:00:1f.6 -vvv?
I've added the PAE expert (Amir).
Thanks,
Sasha
> 
>      $ lspci -s 02:00.0 -nn
>      02:00.0 Network controller [0280]: Intel Corporation Wireless 7265 
> [8086:095a] (rev 59)
> 
> ```
> […]
> [263232.060912] e1000e 0000:00:19.0 eno1: NIC Link is Down
> [263237.160937] e1000e 0000:00:19.0 eno1: NIC Link is Up 1000 Mbps Full 
> Duplex, Flow Control: Rx/Tx
> [263238.142253] e1000e 0000:00:19.0 eno1: NIC Link is Down
> [263245.687208] iwlwifi 0000:02:00.0: RF_KILL bit toggled to disable radio.
> [263245.687212] iwlwifi 0000:02:00.0: reporting RF_KILL (radio disabled)
> [263245.699263] iwlwifi 0000:02:00.0: Disabled INTA bits 0x10000000 were 
> pending
> [263246.796994] e1000e 0000:00:19.0 eno1: NIC Link is Up 1000 Mbps Full 
> Duplex, Flow Control: Rx/Tx
> [263247.778192] e1000e 0000:00:19.0 eno1: NIC Link is Down
> [263252.770667] e1000e 0000:00:19.0 eno1: NIC Link is Up 1000 Mbps Full 
> Duplex, Flow Control: Rx/Tx
> [263253.751948] e1000e 0000:00:19.0 eno1: NIC Link is Down
> […]
> ```
> 
> Enabling the debug message with
> 
>      echo "module e1000e +p" | sudo tee 
> /sys/kernel/debug/dynamic_debug/control
> 
> there is
> 
> ```
> [263463.845944] e1000e 0000:00:19.0 eno1: NIC Link is Up 1000 Mbps Full 
> Duplex, Flow Control: Rx/Tx
> [263464.839339] e1000e 0000:00:19.0 eno1: NIC Link is Down
> [263469.658556] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0x1
> [263469.658616] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0x1
> [263471.542403] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0x1
> [263471.542480] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0x1
> [263473.454131] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0x1
> [263473.454212] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0x1
> [263473.454280] e1000e 0000:00:19.0 eno1: 1000 Mbps, Full Duplex
> [263473.454298] e1000e 0000:00:19.0 eno1: Setting page 0x0
> [263473.454360] e1000e 0000:00:19.0 eno1: writing PHY page 0 (or 0x0 
> shifted) reg 0x10
> [263473.454420] e1000e 0000:00:19.0 eno1: Setting page 0x0
> [263473.454479] e1000e 0000:00:19.0 eno1: writing PHY page 0 (or 0x0 
> shifted) reg 0x11
> [263473.454538] e1000e 0000:00:19.0 eno1: Setting page 0x6080
> [263473.454596] e1000e 0000:00:19.0 eno1: reading PHY page 772 (or 
> 0x6080 shifted) reg 0x1c
> [263473.454656] e1000e 0000:00:19.0 eno1: Setting page 0x6080
> [263473.454714] e1000e 0000:00:19.0 eno1: writing PHY page 772 (or 
> 0x6080 shifted) reg 0x1c
> [263473.454773] e1000e 0000:00:19.0 eno1: Setting page 0x6040
> [263473.454831] e1000e 0000:00:19.0 eno1: reading PHY page 770 (or 
> 0x6040 shifted) reg 0x11
> [263473.454890] e1000e 0000:00:19.0 eno1: Setting page 0x6040
> [263473.454948] e1000e 0000:00:19.0 eno1: writing PHY page 770 (or 
> 0x6040 shifted) reg 0x11
> [263473.455059] e1000e 0000:00:19.0 eno1: 1000 Mbps, Full Duplex
> [263473.455073] e1000e 0000:00:19.0 eno1: Setting page 0x6080
> [263473.455131] e1000e 0000:00:19.0 eno1: reading PHY page 772 (or 
> 0x6080 shifted) reg 0x14
> [263473.455190] e1000e 0000:00:19.0 eno1: Setting page 0x0
> [263473.455248] e1000e 0000:00:19.0 eno1: writing PHY page 0 (or 0x0 
> shifted) reg 0x10
> [263473.455307] e1000e 0000:00:19.0 eno1: Setting page 0x0
> [263473.455365] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0x11
> [263473.455424] e1000e 0000:00:19.0 eno1: Setting page 0x0
> [263473.455482] e1000e 0000:00:19.0 eno1: writing PHY page 0 (or 0x0 
> shifted) reg 0x10
> [263473.455541] e1000e 0000:00:19.0 eno1: Setting page 0x0
> [263473.455599] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0x11
> [263473.455658] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0x5
> [263473.455716] e1000e 0000:00:19.0 eno1: Setting page 0x0
> [263473.455774] e1000e 0000:00:19.0 eno1: writing PHY page 0 (or 0x0 
> shifted) reg 0x10
> [263473.455833] e1000e 0000:00:19.0 eno1: Setting page 0x0
> [263473.455891] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0x11
> [263473.455950] e1000e 0000:00:19.0 eno1: Setting page 0x6080
> [263473.456008] e1000e 0000:00:19.0 eno1: writing PHY page 772 (or 
> 0x6080 shifted) reg 0x14
> [263473.456071] e1000e 0000:00:19.0 eno1: hw->fc.current_mode = 3
> [263473.456078] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0x1
> [263473.456140] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0x1
> [263473.456201] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0x4
> [263473.456262] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0x5
> [263473.456322] e1000e 0000:00:19.0 eno1: Flow Control = FULL.
> [263473.456326] e1000e 0000:00:19.0 eno1: 1000 Mbps, Full Duplex
> [263473.456330] e1000e 0000:00:19.0 eno1: hw->fc.current_mode = 3
> [263473.456340] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0x0
> [263473.456401] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0x1
> [263473.456463] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0x4
> [263473.456524] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0x5
> [263473.456585] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0x6
> [263473.456646] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0x9
> [263473.456708] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0xa
> [263473.456769] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0xf
> [263473.456829] e1000e 0000:00:19.0 eno1: 1000 Mbps, Full Duplex
> [263473.456836] e1000e 0000:00:19.0 eno1: NIC Link is Up 1000 Mbps Full 
> Duplex, Flow Control: Rx/Tx
> [263474.458100] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0x1
> [263474.458169] e1000e 0000:00:19.0 eno1: reading PHY page 0 (or 0x0 
> shifted) reg 0x1
> [263474.458233] e1000e 0000:00:19.0 eno1: NIC Link is Down
> ```
> 
> Removing and loading the module *e1000e* did not help. Suspending and 
> resume did not either. Only powering off the system (maybe restart would 
> have worked too).
> 
> The 8 MB output of `dmesg` (still missing the early messages) [1] 
> contains more lines from the subsequent tries.
> 
> It only happened once, and I am unable to reproduce it.
> 
> 
> Kind regards,
> 
> Paul
> 
> 
> [1]: https://owww.molgen.mpg.de/~pmenzel/linux-5.19.6--messages.txt
> _______________________________________________
> Intel-wired-lan mailing list
> Intel-wired-lan@osuosl.org
> https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  reply	other threads:[~2022-10-02  6:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30 15:56 [Intel-wired-lan] Link does not come up after resuming from ACPI S3 Paul Menzel
2022-10-02  6:57 ` Neftin, Sasha [this message]
2022-10-02  7:52   ` Paul Menzel
2022-10-02 13:27     ` Neftin, Sasha

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=d287a371-2a26-04f7-9adc-c7d8a19bfc14@intel.com \
    --to=sasha.neftin@intel.com \
    --cc=amir.avivi@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=devora.fuxbrumer@intel.com \
    --cc=dima.ruinskiy@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=pmenzel@molgen.mpg.de \
    /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