Comment 2 for bug 1797358

Revision history for this message
Pieter Malan (pmalan) wrote :

I am seeing this behaviour when using nfp_p1 port and not nfp_p0.