On Sun, 18 Oct 2009, Justin Piszcz wrote: > >> I have included debugging logs-- see below, is this a nut or kernel/USB > >> subsystem issue? > >> > >> Robert/Nut User List-- > >> > >> Looks like the data goes stale, please let me know if any more > >> logs/debugging is required, is this a kernel/usb problem or a nut issue? I > >> recall a change in the USB subsystem a few kernel versions back caused a > >> different issue (on a different UPS, but nevertheless it was kernel > >> related). > > > > The details+logs are here (previous e-mail did not go through, too large for > the list): > wget http://home.comcast.net/~jpiszcz/20091014/nut-problem.txt > > For now I have disabled nut-- is there any more debugging that I can do to > help find/solve the problem? Also cc'ing linux-usb & linux-kernel on this > one. You could collect a usbmon trace showing the problem. For instructions, see the kernel source file Documentation/usb/usbmon.txt. It might also help to provide the dmesg log from a kernel built with CONFIG_USB_DEBUG enabled. 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
