Kernel panic after plugging in ethernet cable

Yes, I’ve just removed it

┌─[user@Dell-Latitude]─[~]
└──╼ $sudo pacman -R broadcom-wl-dkms
[sudo] password for user: 
checking dependencies...

Package (1)       Old Version      Net Change

broadcom-wl-dkms  6.30.223.271-35   -7.61 MiB

Total Removed Size:  7.61 MiB

:: Do you want to remove these packages? [Y/n] y
:: Running pre-transaction hooks...
(1/1) Remove DKMS modules
==> dkms remove --no-depmod broadcom-wl/6.30.223.271 -k 5.15.77-1-lts
==> dkms remove --no-depmod broadcom-wl/6.30.223.271 -k 5.19.13-arch1-1
==> dkms remove --no-depmod broadcom-wl/6.30.223.271 -k 6.0.7-1-clear
==> dkms remove --no-depmod broadcom-wl/6.30.223.271 -k 6.0.7-arch1-1
==> dkms remove broadcom-wl/6.30.223.271
==> depmod 6.0.7-arch1-1
==> depmod 5.15.77-1-lts
==> depmod 6.0.7-1-clear
==> depmod 5.19.13-arch1-1
depmod: WARNING: could not open modules.order at /lib/modules/5.19.13-arch1-1: No such file or directory
depmod: WARNING: could not open modules.builtin at /lib/modules/5.19.13-arch1-1: No such file or directory
depmod: WARNING: could not open modules.builtin.modinfo at /lib/modules/5.19.13-arch1-1: No such file or directory
:: Processing package changes...
(1/1) removing broadcom-wl-dkms                    [----------------------] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
┌─[user@Dell-Latitude]─[~]
└──╼ $

See if that does anything as i don’t think you have any broadcom hardware that needs it.

It did a panic again :sweat_smile:

Honestly it doesn’t make any sense why?

I’m no expert here, but I think it’s a problem with the how the kernel treats the cpu.

Because I installed the clear-linux kernel that is known for its optimizations for intel cpus’

I don’t know. I’m far from an expert also and yes i do know the clear linux kernel is optimized for Intel hardware but there are others who have this same Intel Ethernet and WiFi. I haven’t seen this issue before.

The only other thing I can think of is that I had installed endeavouros without checking a box, it was called ‘endeavouros tweaks’ or ‘endeavouros themes’ something like that.

I’m not sure what it would be. Which ISO was it? The latest or prior?

I installed endeavouros on the 8th of April 2022

Edit: With the most recent ISO of that time

I’m not sure but sounds like a previous ISO then? Artemis Nova was Sept 2022.

You have Intel Ethernet and Wifi which should both be well supported. Is there a time frame for when the Kernel Panic started?

I know in most router configurations even for Intel NICs you want to disable hardware checksum offload, hardware TCP segmentation offload, and hardware large receive offload to avoid this sort of issue.

Ive also heard of that NIC having some issues with C states but I honestly cant be sure whats going on here. Im guessing its either firmware or related to hardware offloading which is the usual case for this sort of thing when Ive encountered it.

Usually this happens with Realtek NICs and not intel though

EDIT: Perhaps try this Intel Ethernet Driver from their site? https://www.intel.com/content/www/us/en/download/15084/intel-ethernet-adapter-complete-driver-pack.html?wapkw=I219-LM

this should work for making the driver

tar xfv "driverpkg".tar.gz

cd src

sudo make install

@E-Dolphin
What is the output here?

systemctl status wpa_supplicant.service
extra/rtkit 0.13-2 (27.4 KiB 85.6 KiB)
    Realtime Policy and Watchdog Daemon

missing …

I have recorded 2 different versions of output made by systemctl status wpa_supplicant.service stock kernel + ethernet

  • Version 1
● wpa_supplicant.service - WPA supplicant
     Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; disabled; preset: disabled)
     Active: active (running) since Mon 2022-11-07 13:48:41 +06; 16s ago
   Main PID: 478 (wpa_supplicant)
      Tasks: 1 (limit: 9213)
     Memory: 6.6M
        CPU: 44ms
     CGroup: /system.slice/wpa_supplicant.service
             └─478 /usr/bin/wpa_supplicant -u -s -O /run/wpa_supplicant

Nov 07 13:48:41 Dell-Latitude wpa_supplicant[478]: Successfully initialized wpa_supplicant
Nov 07 13:48:45 Dell-Latitude wpa_supplicant[478]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US
Nov 07 13:48:45 Dell-Latitude wpa_supplicant[478]: wlan0: SME: Trying to authenticate with 0c:80:63:5b:7f:55 (SSID='Titanium' freq=2457 MHz)
Nov 07 13:48:45 Dell-Latitude wpa_supplicant[478]: wlan0: Trying to associate with 0c:80:63:5b:7f:55 (SSID='Titanium' freq=2457 MHz)
Nov 07 13:48:45 Dell-Latitude wpa_supplicant[478]: RRM: Ignoring radio measurement request: Not associated
Nov 07 13:48:45 Dell-Latitude wpa_supplicant[478]: wlan0: Associated with 0c:80:63:5b:7f:55
Nov 07 13:48:45 Dell-Latitude wpa_supplicant[478]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Nov 07 13:48:45 Dell-Latitude wpa_supplicant[478]: wlan0: WPA: Key negotiation completed with 0c:80:63:5b:7f:55 [PTK=CCMP GTK=CCMP]
Nov 07 13:48:45 Dell-Latitude wpa_supplicant[478]: wlan0: CTRL-EVENT-CONNECTED - Connection to 0c:80:63:5b:7f:55 completed [id=0 id_str=]
Nov 07 13:48:46 Dell-Latitude wpa_supplicant[478]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-31 noise=9999 txrate=300000
  • Version 2
● wpa_supplicant.service - WPA supplicant
     Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; disabled; preset: disabled)
     Active: active (running) since Mon 2022-11-07 13:46:37 +06; 10s ago
   Main PID: 519 (wpa_supplicant)
      Tasks: 1 (limit: 9213)
     Memory: 6.6M
        CPU: 72ms
     CGroup: /system.slice/wpa_supplicant.service
             └─519 /usr/bin/wpa_supplicant -u -s -O /run/wpa_supplicant

Nov 07 13:46:37 Dell-Latitude systemd[1]: Started WPA supplicant.
Nov 07 13:46:37 Dell-Latitude wpa_supplicant[519]: Successfully initialized wpa_supplicant
Nov 07 13:46:40 Dell-Latitude wpa_supplicant[519]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=CN
Nov 07 13:46:41 Dell-Latitude wpa_supplicant[519]: wlan0: SME: Trying to authenticate with 90:9a:4a:06:0a:dc (SSID='Pikachu-5G' freq=5745 MHz)
Nov 07 13:46:41 Dell-Latitude wpa_supplicant[519]: wlan0: Trying to associate with 90:9a:4a:06:0a:dc (SSID='Pikachu-5G' freq=5745 MHz)
Nov 07 13:46:41 Dell-Latitude wpa_supplicant[519]: wlan0: Associated with 90:9a:4a:06:0a:dc
Nov 07 13:46:41 Dell-Latitude wpa_supplicant[519]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Nov 07 13:46:41 Dell-Latitude wpa_supplicant[519]: wlan0: WPA: Key negotiation completed with 90:9a:4a:06:0a:dc [PTK=CCMP GTK=CCMP]
Nov 07 13:46:41 Dell-Latitude wpa_supplicant[519]: wlan0: CTRL-EVENT-CONNECTED - Connection to 90:9a:4a:06:0a:dc completed [id=0 id_str=]
Nov 07 13:46:41 Dell-Latitude wpa_supplicant[519]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-54 noise=9999 txrate=433300

I’ve installed ‘rtkit’ but it doesn’t make a difference it still does a kernel panic

┌─[user@Dell-Latitude]─[~]
└──╼ $sudo pacman -S rtkit
[sudo] password for uset: 
resolving dependencies...
looking for conflicting packages...

Package (1)  New Version  Net Change  Download Size

extra/rtkit  0.13-2         0.08 MiB       0.03 MiB

Total Download Size:   0.03 MiB
Total Installed Size:  0.08 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 rtkit-0.13-2-x86_64    27.4 KiB   351 KiB/s 00:00 [----------------------] 100%
(1/1) checking keys in keyring                     [----------------------] 100%
(1/1) checking package integrity                   [----------------------] 100%
(1/1) loading package files                        [----------------------] 100%
(1/1) checking for file conflicts                  [----------------------] 100%
:: Processing package changes...
(1/1) installing rtkit                             [----------------------] 100%
:: Running post-transaction hooks...
(1/4) Creating system user accounts...
Creating group 'rtkit' with GID 133.
Creating user 'rtkit' (RealtimeKit) with UID 133 and GID 133.
(2/4) Reloading system manager configuration...
(3/4) Arming ConditionNeedsUpdate...
(4/4) Reloading system bus configuration...
┌─[user@Dell-Latitude]─[~]
└──╼ $

yes its only for audio system… i was only seeing the error in the log…