On Wed, 25 Feb 2009 00:21:21 -0500, "Paul O'Keefe" <paul@xxxxxxxxxxxxx> wrote: > With kernel packages of series 2.6.27 the btool -t command correctly > produces a list of databases. Since Kernel series 2.6.28 I have been > unable to communicate to the device without modifying the code. > I can run the "btool -t" command inside gdb without changing any code > and it performs as it should. Gdb is only adding a bit of latency, thus > my timing hypothesis. Please don't consider it fingerpointing, but I suspect that btool manages to get into some kind of loop where it constantly unlinks like crazy: > Attached is a usbmon trace from my box. It goes on and on, but all the > real action happens within the first 21 milliseconds. [] > f0ec5400 21.994583 S Bi:7:008:7 - 16384 < > f0ec5400 21.994709 C Bi:7:008:7 0 12 = 00000c00 13060100 00000000 > f0ec5400 21.994804 S Bi:7:008:7 - 16384 < > f0dd7680 21.995487 S Bo:7:008:9 - 8 = 00000800 0a060108 > f0dd7680 21.995580 C Bo:7:008:9 0 8 > > f0ec5400 22.994997 C Bi:7:008:7 -2 0 > f0dfc700 22.995272 S Bi:7:008:7 - 16384 < > f0dfc700 23.996244 C Bi:7:008:7 -2 0 ENOENT of this kind is probably an unlink. At this point, I think, the first order of business is to get an strace dump from btool. You'll see if it bombs your device with unlinks, or issues commands with impossible timeouts (causing unlinks by devio). -- Pete -- 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
