Why is carrier on in dmesg more than once?

Why does eth1 keep saying carrier on in dmesg?

[216068.724910] r8152 2-2:1.0 eth1: carrier on
[216087.792783] r8152 2-2:1.0 eth1: carrier on
[216106.810692] r8152 2-2:1.0 eth1: carrier on
[216125.823644] r8152 2-2:1.0 eth1: carrier on
[216144.909474] r8152 2-2:1.0 eth1: carrier on
[216164.019376] r8152 2-2:1.0 eth1: carrier on
[216182.965182] r8152 2-2:1.0 eth1: carrier on
[216202.058149] r8152 2-2:1.0 eth1: carrier on
[216220.972955] r8152 2-2:1.0 eth1: carrier on
[216239.914898] r8152 2-2:1.0 eth1: carrier on
[216258.908544] r8152 2-2:1.0 eth1: carrier on
[216278.242641] r8152 2-2:1.0 eth1: carrier on
[216297.214694] r8152 2-2:1.0 eth1: carrier on
[216316.166541] r8152 2-2:1.0 eth1: carrier on
[216335.116251] r8152 2-2:1.0 eth1: carrier on
[216354.084160] r8152 2-2:1.0 eth1: carrier on
[216373.229158] r8152 2-2:1.0 eth1: carrier on
[216392.280940] r8152 2-2:1.0 eth1: carrier on
[216411.214884] r8152 2-2:1.0 eth1: carrier on
[216430.160523] r8152 2-2:1.0 eth1: carrier on
[216449.066441] r8152 2-2:1.0 eth1: carrier on
[216468.005246] r8152 2-2:1.0 eth1: carrier on
[216487.113202] r8152 2-2:1.0 eth1: carrier on
[216506.017071] r8152 2-2:1.0 eth1: carrier on
[216524.954015] r8152 2-2:1.0 eth1: carrier on

Unless you have rebooted (or reconnected) the attached client that often, the first suspicion would be on the cables or connectors being broken or not seated properly (hardware damage might also be possible, driver side issues are not impossible either).

Shouldn't there be some sort of disconnect between all those?

I would expect that, but the messages still strongly imply something being amiss.

1 Like

I can't see any USB errors (eth1 is a TPLink UE300 on a raspberry pi4).
I'll reseat all the cables.

1 Like

No errors so far. :slight_smile:

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.