On 25 March 2013 18:07, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > On Mon, 25 Mar 2013, David Linares wrote: > >> > Start with usbmon (see Documentation/usb/usbmon.txt). >> >> Thanks Alan. I have just compiled my kernel with debugfs and usbmon. >> I can now easily capture raw text traces after boot-up. But I am interested >> in capturing these traces at boot time because that's when the problems >> occur. Any way to achieve that? > > No, there isn't any way. The best you can do is build the host > controller driver as a module, and start up usbmon before the module is > loaded. > >> While enabling usbmon, I noticed something that can be related. >> There is a config: "Maximum VBUS Power usage" which is currently set to >> 300mA in my case. > > That option (USB_GADGET_VBUS_DRAW) applies only to gadgets. That is, > it's meant for the part of the USB stack used in peripherals, not in > hosts. > Ok, so I guess these are the 300mA which are currently reported by the HID keyboard emulation for example, as I do have this gadget. >> But here is the USB dongle I am using: >> >> lsusb -v >> ... >> idVendor 0x148f Ralink Technology, Corp. >> idProduct 0x5370 RT5370 Wireless Adapter >> .. >> MaxPower 450mA >> >> I guess setting 450mA will sort out my issue number 4 and avoid the >> "usb 1-1.1: rejected 1 configuration due to insufficient available bus power" >> right? > > No, it won't have any effect at all. What might help would be to plug > the wireless adapter into a powered hub instead of directly into your > computer. > The device I am working on is an embedded device, therefore the wireless adapter has to be connected to the internal hub. This hub and the whole device are powered via an usb cable. I have posted a full "lsub -v" that I ran on the device when everything works, just in case someone spots something very obvious: http://pastebin.com/HypTRS9J Thanks again. > Alan Stern > -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
