intermittent Ethernet lockup until power cycle #26

Closed
opened 2020-04-28 14:02:51 +08:00 by sb10q · 3 comments

Sometimes Ethernet does not come up (the message eth: got Link { speed: S1000, duplex: Half } is not printed). The problem persists until the board is power cycled.

Sometimes Ethernet does not come up (the message ``eth: got Link { speed: S1000, duplex: Half }`` is not printed). The problem persists until the board is power cycled.

I did not experience the issue recently, maybe this is already resolved?

I did not experience the issue recently, maybe this is already resolved?

Having switched from gdb to remote_run.sh at the same time, startup reliability improved for me anyway. :-) I have not experienced the problem since then.

Having switched from gdb to remote_run.sh at the same time, startup reliability improved for me anyway. :-) I have not experienced the problem since then.
Poster
Owner

Have not seen it either recently.

Have not seen it either recently.
sb10q closed this issue 2020-07-20 10:37:58 +08:00
Sign in to join this conversation.
No Label
No Milestone
No Assignees
3 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/zynq-rs#26
There is no content yet.