You are not logged in.
Quick summary - System doesn't suspend when ethernet cable is unplugged.
Kernel - Tried both on 6.10.10.arch1-1 and 6.10.10.zen1-1
Machine - ThinkPad E16 Gen 2 (/w Intel Core Ultra 7 155H)
Hello,
I've been encountering issues whenever suspending my system with the ethernet cable unplugged or plugged in at least once. The system tries suspending, screen goes black, and turns right back on. The problem persists until I unload and reload the e1000e kernel module. Also the system suspends just fine with the e1000e module unloaded.
I tried the same scenario both on linux and linux-zen; linux-lts is out of the question, because sof-firmware crashes there, but that's not related to the current topic.
The logs below are from when the ethernet cable is plugged in.
Kernel Logs:
suspend_log_linux.txt - https://0x0.st/XgM3.txt
suspend_log_linux-zen.txt - https://0x0.st/XgM3.txt
Note related to logs: The only difference i spotted between both logs (besides timestamps) is that linux's e1000e logs
e1000e: EEE TX LPI TIMER: 00000011
, whereas linux-zen's e1000e logs
e1000e 0000:00:1f.6 enp0s31f6: Could not acquire PHY
This line and the three lines below it disappear after unloading the e1000e module.
Here's a diffchecker link (between linux and linux-zen's logs) for convenience - https://www.diffchecker.com/1RNyEi1R/
Thanks in advance!
Last edited by InsufficientCreativity (2024-09-30 15:43:16)
Offline
Offline
Thanks for the reply, for now I solved it by disabling the e1000e module on startup with a modprobe hook and I'll just enable the module whenever I need it
the hook file in question (/etc/modprobe.d/e1000e.conf):
# Do not load the 'e1000e' module on boot.
# This module is responsible for the Ethernet controller.
# Enable only when required via modprobe.
blacklist e1000e
I will check out this other topic tomorrow.
Offline
Hello seth,
I looked at the other topic and saw that the resolution was to install the LTS kernel. I'm having stability issues with it (as funny as it sounds) with sof-firmware, so I was looking for alternative ways. The modprobe hook is working great for me, and I haven't had any issues turning on the e1000e module whenever I need it. I'm gonna mark this topic as solved with the solution being the reply above this one.
Offline