The busnum/devnum error usually occurs on some devices that are single-board computers, rather than full PCs such as your laptop, or a desktop computer. Examples of devices it has been reported on include small devices with Intel Atom processors such as the original Up Board and the Intel Compute Stick.
An excellent reply by Intel support member Juan N explains to an Up Board user why small devices that use a USB 3 OTG (On The Go) port can have problems with the 400 Series camera.
OTG is a mini-USB port designed for mobile devices that allows full USB 3.0 devices to be connected to it via an adapter or OTG cable.
The Intel Click store listing for the Aero Compute Board says that it also uses an OTG cable.
It does not necessarily mean the camera is unusable on an OTG port, but there may be power issues. There was another busnum/devnum case where the camera was usable for sample programs but would cut out when the ROS (Robot Operating System) software was additionally run.
Thanks for your quick reply. That answers my question. When the camera works it works with ros and other programs running and few other things connected to usb adapter. I can get it working by plugging/unplugging few times. Just one more question, is it going to be the same if I use intel NUC single board computer?
If you are having to unplug-replug to reset the camera when it stalls, and you can write your own scripts, you can reduce the chances of having to do this by inserting a hardware reset instruction called hardware_reset() at the start of a script.
Intel NUCs, though they are in a small form-factor, are not usually affected by busnum/devnum as far as I know, because they use a full USB 3 port instead of the mini OTG port.