On Mon, 18 Jan 2010, Peter Kornatowski wrote: > The bluetooth adapters I use are from Vivanco (model number 25711, > USB 2.0, BT 2.1, Class1, EDR 3x), I don't know if they have the same > hardware problem. > > I also saved a usbmon-log, but it is huge (32GB)! I made the testrun > for about 15 hours and got 4 USB-disconnects (this time all 4 on the > same adapter, I will make some further tests after I exchange it, > maybe there is a hardware problem?). > The timestamp in the usbmon log is somehow strange. It is saved in > microseconds and has at most 10 digits, but after 3 hours more than > 10000000000 microseconds passed (so 11 digits). I tried to grep for > some timestamps from the syslog, but it did not work. So how does the > timestamp work or what should I look for in the usbmon log? The timestamp is in microseconds from system startup; it doesn't give the time of day. If you can match up one of the events in the usbmon log with something in the dmesg log then you can figure out the offset between the two time scales. Generally it doesn't matter. > Can you tell me if I logged the right thing? All 3 adapters were > connected to the same d-link 7-port usb-hub and I logged > cat /sys/kernel/debug/usb/usbmon/1u That's right. The interesting things to look for will be the messages that refer to the 7-port hub, together with some of the messages before and after. Messages for the hub will contain the string "1:002:" so you can search for that. 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
