Reboots after core update to 162

My perfectly stable IPFire 161 has now started rebooting at irregular intervals. Looking at the kernal logs I see this before it reboots:

IPv4: martian source 192.168.0.1 from 0.0.0.0, on dev green0
18:44:33	kernel:	ll header: 00000000: 00 01 2e 6e 6a 04 00 90 c2 e7 8a 65 08 00
19:14:37	kernel:	IPv4: martian source 192.168.0.1 from 0.0.0.0, on dev green0
19:14:37	kernel:	ll header: 00000000: 00 01 2e 6e 6a 04 00 90 c2 e7 8a 65 08 00
19:44:41	kernel:	IPv4: martian source 192.168.0.1 from 0.0.0.0, on dev green0
19:44:41	kernel:	ll header: 00000000: 00 01 2e 6e 6a 04 00 90 c2 e7 8a 65 08 00
20:14:45	kernel:	IPv4: martian source 192.168.0.1 from 0.0.0.0, on dev green0
20:14:45	kernel:	ll header: 00000000: 00 01 2e 6e 6a 04 00 90 c2 e7 8a 65 08 00

Can’t find anything in any other logs as to why this is happening. Anyone else have some light or a clue?
Thanks,
Dave

Hello

For an explanation of martian source, the following links may help:

https://www.suse.com/support/kb/doc/?id=000016540

edit
https://www.thegeekdiary.com/how-to-interpret-linux-martian-source-messages/

Merry Christmas
Tom

1 Like

Hi Tom

Thanks for the links, I did some research on this myself and hmmm. The next interesting thing is that after midnight last night the rebooting stopped. The martian source entries stopped.

Merry Christmas and Happy New Year to everyone.

Dave

martian source messages usually come up when some client in the network is misconfigured, or if different networks are physically connected.

Reloaded, working fine until setting up WiFi again. Hmm.

1 Like

Hi,

assuming you are using an USB-based WiFi equipment, this sounds related to a known XHCI regression in Linux kernel 5.15.x - please see this post for details.

Thanks, and best regards,
Peter MĂĽller

1 Like

Hi,

interesting. Such a Windows-like behaviour (“reinstall or restart, and everything is fine again”) isn’t what we strive for, but it’s good to hear things are now working for you again. :slight_smile:

Thanks, and best regards,
Peter MĂĽller

1 Like

Well turns out that swapping the Ethernet card assignments in SETUP solved the martian problem. Guess they got swapped when I reinstall from scratch. Still don’t understand why the offending card would cause these errors but glad this is finally resolved.

1 Like