[Nut-upsdev] Newhidups gets unbound after a while

[Peter Selinger]

Yes, I'd also like to see the log of the initial connection, i.e., the
beginning of "newhidups -a ups_on_usb -DD". What is your device's
actual vendor/product ID? Is it 0463/FFFF? -- Peter

Patrick Agrain wrote:
> 
> Hi everybody,
> 
> If we let the feature running, it appears that the driver gets unbound 
> after a while ( variable from quarter of hour to 6 hours ) and cannot 
> reconnect.
> This behavior appear with both MGE Ellipse ASR and non-ASR models with 
> connection to an UHCI and OHCI controllers.
> The USB core is from 2.4.28 kernel.
> We use nut-2.0.3.
> 
> Start, powerfail and recovery detections, UPS shutdown work very well. Only 
> continous scanning seems to fail.
> 
> Following are the logs:
> [root at xa000000 root]# newhidups -a ups_on_usb -DD
> 
> <...> Time range from 15mn to 6 hours, depending...
> 
> upsdrv_updateinfo...
> Waiting for notifications...
> process_status_info: online
> process_status_info: !dischrg
> process_status_info: chrg
> process_status_info: !shutdownimm
> process_status_info: !lowbatt
> upsdrv_updateinfo...
> Waiting for notifications...
> process_status_info: online
> process_status_info: !dischrg
> process_status_info: chrg
> process_status_info: !shutdownimm
> Can't retrieve Report 1 (-32/32): Broken pipe
> ==================================================
> = device has been disconnected, try to reconnect =
> ==================================================
> Closing device
> Reopening device
> Checking device (0000/0000) (003/001)
> - VendorID: 0000
> - ProductID: 0000
> - Manufacturer: unknown
> - Product: unknown
> - Serial Number: unknown
> - Bus: 003
> Trying to match device
> Device does not match - skipping
> Checking device (0000/0000) (002/001)
> - VendorID: 0000
> - ProductID: 0000
> - Manufacturer: unknown
> - Product: unknown
> - Serial Number: unknown
> - Bus: 002
> Trying to match device
> Device does not match - skipping
> Checking device (0463/FFFF) (002/002)
> - VendorID: 0463
> - ProductID: ffff
> - Manufacturer: unknown
> - Product: unknown
> - Serial Number: 1HDF44001
> - Bus: 002
> Trying to match device
> Device does not match - skipping
> Checking device (0000/0000) (001/001)
> - VendorID: 0000
> - ProductID: 0000
> - Manufacturer: unknown
> - Product: unknown
> - Serial Number: unknown
> - Bus: 001
> Trying to match device
> Device does not match - skipping
> No appropriate HID device found
> upsdrv_updateinfo...
> 
> =>Got to reconnect!
> 
> ==================================================
> = device has been disconnected, try to reconnect =
> ==================================================
> Closing device
> Reopening device
> Segmentation fault
> [root at xa000000 root]#
> 
> Looking about the reason of the disconnection, I tried gdb but it failed ( 
> received : warning: Couldn't get registers ). Any ideas about what I could 
> also try ?
> For the non-reconnection problem, I suspect a pointer problem, but with no 
> more precision. I had less time to dig further.
> 
> Let me know if you need other logs.
> 
> Any help will be appreciated.
> Regards,
> Patrick Agrain
> 
> 
> _______________________________________________
> Nut-upsdev mailing list
> Nut-upsdev at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
>