Link RX remains UP despite the removal of the SFP module. #240

Open
opened 2023-06-27 15:33:08 +08:00 by den512 · 4 comments
Contributor

Sometimes, after the SFP module is removed, the link layer signal rx_up remains at 1 and data continues to be received. In this state, many errors appear in the log.
Maybe if the SFP module is missing, put the transceiver in a reset state?

Sometimes, after the SFP module is removed, the link layer signal rx_up remains at 1 and data continues to be received. In this state, many errors appear in the log. Maybe if the SFP module is missing, put the transceiver in a reset state?
Owner

Maybe if the SFP module is missing, put the transceiver in a reset state?

That's a bodge. The DRTIO core is supposed to report link down when it stops receiving valid data.

> Maybe if the SFP module is missing, put the transceiver in a reset state? That's a bodge. The DRTIO core is supposed to report link down when it stops receiving valid data.
Author
Contributor

In rare cases, BruteforceClockAligner does not find any errors when removing an SFP module, so everything continues to work. Perhaps it is data from the transceiver that looks like good data. For example, reading the input buffer in a loop.
In any case, looking for a comma without an SFP module does not make sense.

In rare cases, BruteforceClockAligner does not find any errors when removing an SFP module, so everything continues to work. Perhaps it is data from the transceiver that looks like good data. For example, reading the input buffer in a loop. In any case, looking for a comma without an SFP module does not make sense.
Owner

looking for a comma without an SFP module does not make sense.

It does. Economy of mechanism. Additionally this has to work on media other than SFP.

> looking for a comma without an SFP module does not make sense. It does. Economy of mechanism. Additionally this has to work on media other than SFP.
Author
Contributor

Ok. I will look for what is wrong.

Ok. I will look for what is wrong.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: M-Labs/artiq-zynq#240
No description provided.