I have also tested $sudo nmcli connection reload" and some other “nmcli” command to restart the network device… There is one time, when i do a restart of Network device; the internet connection become good. but then after a few minutes… the network card disconnected again (same old issue is back)… restart using nmcli command won’t solve it…
so, it is not really issue with suspend… there is something going wrong behind constantly… which log can see what is the whole system doing behind ? things like API calls in windows os… etc…
I will provide boot log and suspend log here after filter out sensitive data… just for safe sake… it is open forum. Even so , i think it should do much harm for all those log data to be expose to public…
I would like to post std output of nmcli to you, but each terminal i opened now to to run “nmcli” the terminals are in freeze… both terminal freezed… BUT i can still type on the terminal,… just not more respond.
Don’t know what to do already… thinking of REINSTALL OVER the existing os… will that fix whatever problem that causing the os to BREAK ?
I would still like to post my boot log… because i got “shutdown” error… that causing the system not able to shutdown.
To be frank, i didn’t mess with this desktop … not that i know of… and it just broke. And worst thing is, i will never know what is the reason it break, “because of some software ? or some update ? or kernel update ? i have no idea… as i said, i didn’t do much on this desktop… and can’t remember i have done anything major changes of it…”
I won’t want to question you, but couldn’t help it to ask :
opengl and xrender… sounds like something to do with video or graphic … is it something to do with network interface card ?
It is not an ethernet problem, but a problem with suspend which caused a problem with ethernet, as you proved:
That could be somewhat related to the rendering with opengl instead of xrender with some low GPUs like this intel one:
What could affect this:
However… As I read from your posts, it works, except you suspend and wake up you pc. Is that correct?
If so, then I would rather say that there is Firmware Bug or Kernel Bug, or the firmware has not a proper implementation of the ACPI Specification, which the Linux Kernel follows strictly normally (but some BIOS Vendors make exceptions or workarounds for Windows, but left other OS).
I purposely powered on this desktop that have NIC issue.
It was all good at the beginning… , did a “$ systemctl suspend” and wake up, but the internet connection is still good. after around 2 hrs of idling (when i didn’t pay attention to it), i realized the internet connection is disconnected by itself and stay disconnected.
I have the "$journalctl -b -f " … But i don’t know what to look for to filter out the root cause of the internet disconnected.
which log this issue is most probably logged . Is it in kernel log ? surely not kwin log…
Which log to check when NIC not responding to “sudo nmcli monitor” ?
$ journalctl -b | grep net | less
Does this command works ? to grep “net” out ? but since too long, i pipe it to less… but this does not work.
-- Journal begins at Mon 2020-03-30 22:08:21 CEST, ends at Fri 2021-08-13 02:02:14 CEST. --
Aug 12 19:39:17 systemd[1]: Starting Modem Manager...
Aug 12 19:39:19 ModemManager[538]: <info> ModemManager (version 1.16.8) starting in system bus...
Aug 12 19:39:21 systemd[1]: Started Modem Manager.
Aug 12 19:39:24 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Aug 12 19:39:24 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0': not supported by any plugin
Aug 12 22:06:07 ModemManager[538]: <info> [sleep-monitor] system is about to suspend
Aug 12 22:06:18 ModemManager[538]: <info> [sleep-monitor] system is resuming
Aug 12 22:06:21 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Aug 12 22:06:21 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0': not supported by any plugin
Aug 12 23:37:13 ModemManager[538]: <info> [sleep-monitor] system is about to suspend
Aug 12 23:38:20 ModemManager[538]: <info> [sleep-monitor] system is resuming
Aug 12 23:38:23 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Aug 12 23:38:23 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0': not supported by any plugin
Aug 12 23:38:28 ModemManager[538]: <info> [sleep-monitor] system is about to suspend
Aug 12 23:39:35 ModemManager[538]: <info> [sleep-monitor] system is resuming
Aug 12 23:39:37 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Aug 12 23:39:37 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0': not supported by any plugin
Aug 12 23:39:40 ModemManager[538]: <info> [sleep-monitor] system is about to suspend
Aug 12 23:40:47 ModemManager[538]: <info> [sleep-monitor] system is resuming
Aug 12 23:40:50 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Aug 12 23:40:50 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0': not supported by any plugin
Aug 12 23:41:06 ModemManager[538]: <info> [sleep-monitor] system is about to suspend
Aug 12 23:42:13 ModemManager[538]: <info> [sleep-monitor] system is resuming
Aug 12 23:42:15 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Aug 12 23:42:15 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0': not supported by any plugin
Aug 13 01:28:22 ModemManager[538]: <info> caught signal, shutting down...
Aug 13 01:28:22 systemd[1]: Stopping Modem Manager...
Aug 13 01:28:22 ModemManager[538]: <info> ModemManager is shut down
Aug 13 01:28:22 systemd[1]: ModemManager.service: Deactivated successfully.
Aug 13 01:28:22 systemd[1]: Stopped Modem Manager.
I have read through the whole log… but can’t really grasp what most of the log means… however according to the time of nic issue occurs… these lines of log should be written when the nic issue reoccurance
Aug 12 22:06:07 NetworkManager[488]: <info> [1628798767.8368] manager: sleep: sleep requested (sleeping: no enabled: yes)
Aug 12 22:06:07 NetworkManager[488]: <info> [1628798767.8369] manager: NetworkManager state is now ASLEEP
Aug 12 22:06:18 NetworkManager[488]: <info> [1628798778.8218] manager: sleep: wake requested (sleeping: yes enabled: yes)
Aug 12 22:06:18 NetworkManager[488]: <info> [1628798778.8219] device (enp0s25): state change: activated -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Aug 12 22:06:18 NetworkManager[488]: <info> [1628798778.8220] dhcp4 (enp0s25): canceled DHCP transaction
Aug 12 22:06:18 NetworkManager[488]: <info> [1628798778.8220] dhcp4 (enp0s25): state changed extended -> terminated
Aug 12 22:06:18 NetworkManager[488]: <info> [1628798778.8222] dhcp6 (enp0s25): canceled DHCP transaction
Aug 12 22:06:18 NetworkManager[488]: <info> [1628798778.8222] dhcp6 (enp0s25): state changed bound -> terminated
Aug 12 22:06:18 NetworkManager[488]: <info> [1628798778.9457] manager: NetworkManager state is now CONNECTED_GLOBAL
Aug 12 22:06:19 NetworkManager[488]: <info> [1628798779.1429] manager: NetworkManager state is now DISCONNECTED
Aug 12 22:06:19 NetworkManager[488]: <info> [1628798779.1437] device (enp3s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
No idea which device this is: enp0s25 but enp3s0 is the one I saw in your inxi output (maybe the same device, but only renamed?)… however, I see this here:
It could be problem with ipv6, please disable it completely.
No, i have 2 ethernet card… 1 is the used, the other one is working but not used (enp3s0) . So the one show in inxi is the NIC that is plugged in (enp0s25) .
[How to Disable IPv6 on Linux](Disable ipv6)
I did as in the instruction to disabled permanently ipv6 already.
Is this instruction on the website is good set of instruction ?
