System freezes upon losing Internet conection

Ask Fedora Ask in English
, , ,
1

Continuing the discussion from Freeze during heavy file transferral:

The referenced issue was most certainly caused by my dodgy PCI-e Wifi/Bluetooth adapter, but there’s more to the story.

Several times over the course of a few days now, I’ve come home to find my computer in a frozen up state. Upon having left, I’ve left the computer standing idle, but not suspended, and auto-suspend is toggled off.

For the moment the only Internet provision I have is my Smartphone’s Wifi hotspot, and so when I leave with my phone my other devices at home are obviously left without Internet entirely.

Judging by the logs it appears obvious that a networking-related crash is what happens, as a load of this sort of stuff is recorded right before the crash.

Mar 17 14:29:26 fedora systemd[1]: Finished dnf-makecache.service - dnf makecache.
Mar 17 14:29:26 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-makecache comm="syst>
Mar 17 14:29:26 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-makecache comm="syste>
Mar 17 14:29:52 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:30:48 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:31:44 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:32:40 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:33:19 fedora NetworkManager[1298]: <info>  [1679059999.2608] device (wlp3s0): set-hw-addr: set MAC address to 6E:C1:35:EA:C4:1E (scanning)
Mar 17 14:33:19 fedora NetworkManager[1298]: <info>  [1679059999.6303] device (wlp3s0): supplicant interface state: inactive -> interface_disabled
Mar 17 14:33:19 fedora NetworkManager[1298]: <info>  [1679059999.6304] device (p2p-dev-wlp3s0): supplicant management interface state: inactive -> interface_>
Mar 17 14:33:19 fedora NetworkManager[1298]: <info>  [1679059999.6307] device (wlp3s0): supplicant interface state: interface_disabled -> inactive
Mar 17 14:33:19 fedora NetworkManager[1298]: <info>  [1679059999.6307] device (p2p-dev-wlp3s0): supplicant management interface state: interface_disabled -> >
Mar 17 14:33:36 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:34:41 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:35:38 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:36:34 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:37:30 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:38:26 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:39:03 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:39:56 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:40:13 fedora NetworkManager[1298]: <info>  [1679060413.2860] device (wlp3s0): set-hw-addr: set MAC address to 9E:12:21:7B:A6:84 (scanning)
Mar 17 14:40:13 fedora NetworkManager[1298]: <info>  [1679060413.6553] device (wlp3s0): supplicant interface state: inactive -> interface_disabled
Mar 17 14:40:13 fedora NetworkManager[1298]: <info>  [1679060413.6553] device (p2p-dev-wlp3s0): supplicant management interface state: inactive -> interface_>
Mar 17 14:40:13 fedora NetworkManager[1298]: <info>  [1679060413.6663] device (wlp3s0): supplicant interface state: interface_disabled -> inactive
Mar 17 14:40:13 fedora NetworkManager[1298]: <info>  [1679060413.6663] device (p2p-dev-wlp3s0): supplicant management interface state: interface_disabled -> >
Mar 17 14:40:52 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:41:48 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:42:44 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:43:40 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:44:04 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:44:52 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:45:49 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:46:45 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:47:07 fedora NetworkManager[1298]: <info>  [1679060827.1959] device (wlp3s0): set-hw-addr: set MAC address to 1A:69:0B:4C:3E:E0 (scanning)
Mar 17 14:47:07 fedora NetworkManager[1298]: <info>  [1679060827.5652] device (wlp3s0): supplicant interface state: inactive -> interface_disabled
Mar 17 14:47:07 fedora NetworkManager[1298]: <info>  [1679060827.5653] device (p2p-dev-wlp3s0): supplicant management interface state: inactive -> interface_>
Mar 17 14:47:07 fedora NetworkManager[1298]: <info>  [1679060827.5734] device (wlp3s0): supplicant interface state: interface_disabled -> inactive
Mar 17 14:47:07 fedora NetworkManager[1298]: <info>  [1679060827.5734] device (p2p-dev-wlp3s0): supplicant management interface state: interface_disabled -> >
Mar 17 14:47:41 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:48:37 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:49:05 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:49:55 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:50:51 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:51:47 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:52:43 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:53:39 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:54:01 fedora NetworkManager[1298]: <info>  [1679061241.2870] device (wlp3s0): set-hw-addr: set MAC address to AE:D9:49:2A:50:59 (scanning)
Mar 17 14:54:01 fedora NetworkManager[1298]: <info>  [1679061241.6563] device (wlp3s0): supplicant interface state: inactive -> interface_disabled
Mar 17 14:54:01 fedora NetworkManager[1298]: <info>  [1679061241.6563] device (p2p-dev-wlp3s0): supplicant management interface state: inactive -> interface_>
Mar 17 14:54:01 fedora NetworkManager[1298]: <info>  [1679061241.6633] device (wlp3s0): supplicant interface state: interface_disabled -> inactive
Mar 17 14:54:01 fedora NetworkManager[1298]: <info>  [1679061241.6633] device (p2p-dev-wlp3s0): supplicant management interface state: interface_disabled -> >
Mar 17 14:54:06 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:54:55 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:55:52 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:56:48 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:57:44 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:58:40 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:59:07 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 14:59:56 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 15:00:52 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 17 15:00:55 fedora NetworkManager[1298]: <info>  [1679061655.2509] device (wlp3s0): set-hw-addr: set MAC address to A2:D6:6C:D6:14:37 (scanning)
Mar 17 15:00:55 fedora NetworkManager[1298]: <info>  [1679061655.6204] device (wlp3s0): supplicant interface state: inactive -> interface_disabled
Mar 17 15:00:55 fedora NetworkManager[1298]: <info>  [1679061655.6204] device (p2p-dev-wlp3s0): supplicant management interface state: inactive -> interface_>
Mar 17 15:00:55 fedora NetworkManager[1298]: <info>  [1679061655.6264] device (wlp3s0): supplicant interface state: interface_disabled -> inactive
Mar 17 15:00:55 fedora NetworkManager[1298]: <info>  [1679061655.6264] device (p2p-dev-wlp3s0): supplicant management interface state: interface_disabled -> >
Mar 17 15:01:48 fedora Tor[1329]: Failed to find node for hop #1 of our path. Discarding this circuit.

There have been very few preceding warnings, and none right before the freeze.

It obviously doesn’t seem right that a freeze or crash must occur in this sort of situation. By the timings given it appears the freeze occurs when the connection cuts out, rather than upon attempted reconnect as I get home.

As a side-question, any recommendations for checking out what hardware is installed, in particular PCI-e cards, would be much appreciated. I’ve tried lspci, dmidecode, /proc/vmstat, /proc/loadavg, and a bunch others, but none will give me a readable name for what card it is I have installed. I only get networking and meaningless PCI-slot numberings. I managed to print out a syslog before, but I am now failing to.

2

try lshw

3

People (including local emergency services) may rely on a wifi hotspot during emergencies, so time spent to sort out your issue may benefit ohers.

Have your tried lspci -v? If your system is a commercial build, you can search for it at Linux Hardware by vendor and model. If it is found there will be some wifi works or fails reports for various linux distros, but the reports don’t get to the level of detail for your use case.

You can work back from the name of your wifi kernel module (example below from a old iMac). Along the way you may encounter useful error messages

  1. What module is used by cfg80211?
% lsmod | grep ^cfg80211
cfg80211             1114112  1 wl
  1. use the name (wl) of the wifi module to find relevant lines in dmesg:
dmesg | grep -w "wl"
[   17.980065] wl: loading out-of-tree module taints kernel.
[   17.980613] wl: module license 'MIXED/Proprietary' taints kernel.
[   17.984103] wl: module verification failed: signature and/or required key missing - tainting kernel
[   17.991022] wl 0000:03:00.0: enabling device (0000 -> 0002)
[   18.040550] wl 0000:03:00.0 wlp3s0: renamed from eth0
  1. Use original (before renaming) device name (eth0) to find details:
% dmesg | grep eth0
[    2.607072] tg3 0000:04:00.0 eth0: Tigon3 [partno(BCM957766a) rev 57766001] (PCI Express) MAC address 68:5b:35:9d:59:af
[    2.607093] tg3 0000:04:00.0 eth0: attached PHY is 57765 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
[    2.607106] tg3 0000:04:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
[    2.607116] tg3 0000:04:00.0 eth0: dma_rwctrl[00000001] dma_mask[64-bit]
[    2.608994] tg3 0000:04:00.0 enp4s0f0: renamed from eth0
[   18.019992] eth0: Broadcom BCM43a0 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334)
[   18.040550] wl 0000:03:00.0 wlp3s0: renamed from eth0
[   23.707050] ipheth 1-2.4:4.2 enp0s20u2u4c4i2: renamed from eth0

The line(s) you want should come just before the “renamed” line found in step 2. Here it tells me the wifi is a “Broadcom BCM43a0 802.11 Hybrid Wireless Controller” and PCI address 03:00.0.


4) go back to `lspci`:

Use `lspci -n` to get the device ID:

% lspci -n | grep 03:00.0
03:00.0 0280: 14e4:43a0 (rev 03)


5) Finally, use the device if (here: `14e4:43a0`) to get verbose `lspci` output fro your device:

% lspci -d 14e4:43a0 -vv
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter (rev 03)
Subsystem: Apple Inc. Device 0111
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 256 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at b1a00000 (64-bit, non-prefetchable) [size=32K]
Region 2: Memory at b1800000 (64-bit, non-prefetchable) [size=2M]
Capabilities:
Kernel driver in use: wl
Kernel modules: bcma, wl


As in this example, there may be another kernel module to try (after searching the internet and the
Linux Hardware site to see what works for others.
1 Like
4

Thank you. I tried that command before, but missed the given model number.

5

Thank you.

There were some differing results to your example along the way, but I came up with the following result in the end

03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8192CE PCIe Wireless Network Adapter (rev 01)
	Subsystem: ASUSTeK Computer Inc. Device 84b6
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 18
	Region 0: I/O ports at e000 [size=256]
	Region 2: Memory at f7000000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: rtl8192ce
	Kernel modules: rtl8192ce

which is my Wifi card. I’ve been confused up until just now, because I’ve known my card by the name “ASUS PCE-N15”, while by your method of investigation, it comes up as named “RTL8192CE PCIe Wireless Network Adapter”. To make sure, I’ve correlated the two by searching for the two together online.

So I take it I should search to see if there’s a different Kernel module to this ‘RTL8192CE…’ one to install for the card.

6

does inxi -N provide the info you’re looking for?

7

That one works perfectly, thanks. I don’t think I tried it with that switch before. It still gives me the “RTL8192CE” name, but now I know that’s the right one.

I’ve been confused by believing I’d seen the “PCE-N15” name returned by some command before, but probably I was wrong about that.

8

The first step is to check for a firmware update. You may need to search for various combinations “RTL8192CE”, “ASUSTeK Device 84b6”, and “ASUS PCE-N15” for reports of your issue.

There are multiple variants of “rtl8192ce” chips. The driver supports them using “aliases”:

 % modinfo rtl8192ce | grep -w '^alias'
alias:          pci:v000010ECd00008176sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008177sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008178sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008191sv*sd*bc*sc*i*

Drivers often add “quirks” options to support these variants. One of the reasons for the 5 step chain to identify your chipset is that there can be informative messages associated with the details found in the search. There are procedures to diagnose linux system freezes .