-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Celestica][E1031] USB tty devices not listed under \dev
after SONiC installed
#6603
Comments
can you debug this with celestica? |
looks like their platform driver is not installed properly. |
Yes, the driver is missing. I've looped Celestica in an email thread. |
The driver missing caused this issue. Re-plug can bring the driver back. Below command can also bring the driver back without touch the box physically:
Before
After
But not sure why the usb uart bridge couldn't binding the cp210x driver automatically. Maybe a driver bug? |
First SONiC boot after installed
unbind USB Hub 1-1.1
bind USB Hub 1-1.1 again
Seems like the system not register USB interface during first boot except hub's interface. |
@lguohan The driver is embedded in kernel, usually we don't need to install it. Consider the issue only happens with coldplug device, it more likely a timing issue, I guess the usbcore/udev are not fully initialize during boot. |
Additional testing with 201911, no issue observed.
|
Base on current investigation, consider there are two possibility:
Here is my plan: No matter which one is the root cause, if we can't fix itself, the plan B will be:
Another possible fix is add |
Description
USB tty devices not listed under
\dev
folder after SONiC installed, however the USB devices already been recognized by system.Steps to reproduce the issue:
show version
lsusb -t
Run above test for
SONiC.202012.13-c8b3a709
andSONiC.master.565-e616a329
Describe the results you received:
Test Result for
SONiC.202012.13-c8b3a709
Test Result for
SONiC.master.565-e616a329
Describe the results you expected:
ttyUSB0 ~ ttyUSB47 should list under
\dev
folder.Additional information you deem important (e.g. issue happens only occasionally):
The driver missing caused this issue. Re-plug can bring the driver back. Below command can also bring the driver back without touch the box physically:
Before
After
The text was updated successfully, but these errors were encountered: