search for: ffff0018

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

...142c c0261517 000003a6 00000800 c1309924 00000400 00000400 e0877267 dc8b1720 c1309924 00000400 00000800 00000801 c3a59000 da0c8480 c3a59000 00000001 00000400 00000000 d15a0c00 c02adfe0 c2f324e4 dc8b1720 e0877539 Call Trace: [<e0877267>] [<e0877539>] [<e0877ae9>] [<ffff0018>] [<c01056dc>] Code: 0f 0b 83 c4 0c 90 56 e8 f2 15 00 00 89 c7 b8 00 e0 ff ff 21 >>EIP; c015822a <ext3_prepare_write+5e/1f4> <===== Trace; e0877267 <END_OF_CODE+1000802f/????> Trace; e0877539 <END_OF_CODE+10008301/????> Trace; e0877ae9 <END_OF_CODE+100088b1...

...ReportID: 0x02, Offset: 8, Size: 8, Value: 0 32.407367 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.LCM...

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