Reopening this bug since we found a software workaround for it.
** Changed in: linux-bluefield (Ubuntu)
Status: Invalid => In Progress
** Changed in: linux-bluefield (Ubuntu Jammy)
Status: Invalid => In Progress
** Description changed:
SRU Justification:
[Impact]
This SW WA didnt work so the HW team will have to review it.
** Changed in: linux-bluefield (Ubuntu)
Status: New => Invalid
** Changed in: linux-bluefield (Ubuntu Jammy)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: linux-bluefield (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064163
Title:
mlxbf-gige: Vitesse PHY stuck in a bad state
** Description changed:
SRU Justification:
[Impact]
- During the QA reboot test, the BF3 Vitesse PHY gets stuck in a bad
- state, resulting in no ip provisioning. The only way to recover is to
- toggle the PHY hard reset pin via GPIO17 (or powercycle cycle since it
- achieves just
