Displaying 3 results from an estimated 3 matches for "ffff001a".
Did you mean:
ffff0015
2006 May 02
5
Newhidups gets unbound after a while
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
2014 May 29
0
Resetting replace battery status on Pulsar 1500
...hu_find_infoval: found !replacebatt (value: 0)
32.407369 process_boolean_info: !replacebatt
There is also this LCM (Life Cycle Monitoring) part:
22.677035 hid_lookup_path: 00840004 -> UPS
22.677037 hid_lookup_path: ffff0018 -> LCMSystem
22.677039 hid_lookup_path: ffff001a -> LCMAlarm
22.677045 hid_lookup_path: 00ff0001 -> not found in lookup table
22.677049 hid_lookup_path: 00840002 -> PresentStatus
22.677052 hid_lookup_path: ffff0093 -> TimerExpired
22.677055 Path: UPS.LCMSystem.LCMAlarm.[1].PresentStatus.TimerExpired, Type: Feat...
2014 May 29
2
Resetting replace battery status on Pulsar 1500
On 28 May 2014, at 21:59, Charles Lepple <clepple at gmail.com> wrote:
>> What would log it?
>
> The driver.
OK.
>> I could try running the driver with debugging and see if that shows anything of interest.
>
> That should help. Unfortunately for non-debug operation, it appears that most of the usbhid-ups instcmd messages are buried at debug level 3 or 5. That