On Thu, 9 Jun 2005, Adam Kropelin wrote: > Pete Zaitcev wrote: > > OK, here is the interesting part of the trace. > > Thanks for the decode... > > > Up to this point, something hits the UPS with control messages every > > 4ms > > (sounds crazy, but here it is: the daemon is obviously out of > > control). > > That is insane. No wonder the thing locks up eventually. > > Christian, back in mid-May I suggested a way you might be able to > reproduce the lockup faster: > > | One other thing to try on the apcupsd end is to edit > | src/drivers/usb/linux/linux-usb.c and modify the > | pusb_ups_check_state() function. Replace the entire > | body of that function with "return 1;" and| then > | rebuild apcupsd and run it. > > You're not still running with that change, are you? It would certainly > account for why the UPS is getting blasted with control transfers. But I > don't think this is the case since we'd see them in the HID debug > output.
Something else to try: Turn on the usbfs_snoop module parameter for usbcore.ko. The system log will then show if any processes are using usbfs to communicate with the UPS. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
