Bug 1061984 - problem with interface smartups apcupsd
Summary: problem with interface smartups apcupsd
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: apcupsd
Version: 20
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Michal Hlavinka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-06 01:50 UTC by Mark Schlegel
Modified: 2015-12-29 15:13 UTC (History)
6 users (show)

Fixed In Version:
Clone Of: 904151
Environment:
Last Closed: 2015-06-29 15:01:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
copy of /etc/apcupsd/apcupsd.conf (12.18 KB, text/plain)
2014-02-06 01:51 UTC, Mark Schlegel
no flags Details

Description Mark Schlegel 2014-02-06 01:50:34 UTC
+++ This bug was initially created as a clone of Bug #904151 +++

Description of problem:
plug smartups SUA1500 USB. No update of data from UPS, and logs repeat several times (40 per minute):
"hid-generic 0003:051D:0002.0001: control queue full"


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.plug smartups
2.start apcupsd
3.view /var/log/messages log, it becomes full of repeated lines of:
Feb  2 03:28:12 host kernel: [101560.378131] hid-generic 0003:051D:0002.0001: control queue full
Feb  2 03:28:12 host kernel: [101560.398202] hid-generic 0003:051D:0002.0001: control queue full
Feb  2 03:28:12 host kernel: [101560.418269] hid-generic 0003:051D:0002.0001: control queue full
 
4. dmesg buffer is also filled

Actual results:
unexpected results

Expected results:
good data from ups and no log problem


Additional info:
lsusb -v -s 007:002

Bus 007 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x051d American Power Conversion
  idProduct          0x0002 Uninterruptible Power Supply
  bcdDevice            0.06
  iManufacturer           3 
  iProduct                1 
  iSerial                 2 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           34
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration         11 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower               30mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      0 No Subclass
      bInterfaceProtocol      0 None
      iInterface              0 
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.10
          bCountryCode           33 US
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength    1040
         Report Descriptors: 
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0006  1x 6 bytes
        bInterval             100

====================
version of apcupsd:

rpm -q apcupsd
apcupsd-3.14.10-11.fc19.x86_64
====================
version of kernel
uname -r
3.12.9-200.fc19.x86_64

===================
output of 'apcaccess' command
APC      : 001,042,1001
DATE     : 2014-02-05 20:47:00 -0500  
HOSTNAME : pither
VERSION  : 3.14.10 (13 September 2011) redhat
UPSNAME  : pither
CABLE    : USB Cable
DRIVER   : USB UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2014-02-04 23:16:58 -0500  
MODEL    : 
STATUS   : ONLINE 
LINEV    : 120.2 Volts
LOADPCT  :  19.5 Percent Load Capacity
BCHARGE  : 099.0 Percent
TIMELEFT :  48.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
OUTPUTV  : 120.2 Volts
SENSE    : High
DWAKE    : -01 Seconds
DSHUTD   : 090 Seconds
LOTRANS  : 106.0 Volts
HITRANS  : 127.0 Volts
RETPCT   : 000.0 Percent
ITEMP    : 19.3 C Internal
ALARMDEL : 30 seconds
BATTV    : 27.7 Volts
LINEFREQ : 60.0 Hz
LASTXFER : Automatic or explicit self test
NUMXFERS : 0
TONBATT  : 0 seconds
CUMONBATT: 0 seconds
XOFFBATT : N/A
SELFTEST : OK
STESTI   : 14 days
STATFLAG : 0x07000008 Status Flag
MANDATE  : 2007-05-30
SERIALNO : 
BATTDATE : 2013-06-23
NOMOUTV  : 120 Volts
NOMBATTV :  24.0 Volts
END APC  : 2014-02-05 20:47:18 -0500

Comment 1 Mark Schlegel 2014-02-06 01:51:46 UTC
Created attachment 859942 [details]
copy of /etc/apcupsd/apcupsd.conf

Comment 2 Mark Schlegel 2014-02-06 01:57:36 UTC
Re-ran 'lsusb -v -s 007:002' as root to get more info (iProduct was truncated):


iProduct                1 Smart-UPS 1500 FW:601.3.D USB FW:8.1

Comment 3 Mark Schlegel 2014-03-09 16:58:32 UTC
This is still broken in the latest kernel I've installed on Fedora 19:

kernel-3.13.5-103.fc19.x86_64


dmesg is full of repeated lines:

[85389.532602] hid-generic 0003:051D:0002.0001: control queue full
[85389.552669] hid-generic 0003:051D:0002.0001: control queue full
[85389.572737] hid-generic 0003:051D:0002.0001: control queue full
[85389.592805] hid-generic 0003:051D:0002.0001: control queue full
[85389.612873] hid-generic 0003:051D:0002.0001: control queue full
[85389.632940] hid-generic 0003:051D:0002.0001: control queue full
[85389.673067] hid-generic 0003:051D:0002.0001: control queue full
[85389.713195] hid-generic 0003:051D:0002.0001: control queue full

current apcupsd version used: apcupsd-3.14.10-10.fc19.x86_64

Comment 4 Mark Schlegel 2014-04-12 17:33:08 UTC
I've since upgraded to Fedora 20:

kernel:  kernel-3.13.9-200.fc20.x86_64
apcupsd-3.14.12-1.fc20.x86_64

and I'm still confirming that the dmesg is still overflowing with control queue full output

Comment 5 Mark Schlegel 2014-05-16 00:39:47 UTC
Reconfirmed on Fedora 20 with kernel 3.14.4-200.fc20.x86_64 from updates-testing

Comment 6 j.fikar 2014-06-16 14:16:58 UTC
had the same problem, check this quick fix:

http://forums.gentoo.org/viewtopic-p-7569028.html#7569028

Comment 7 Mark Schlegel 2015-01-06 04:09:31 UTC
This bug doesn't seem to exist anymore after I've upgraded to Fedora 21 x86_64: kernel 3.17.7-300.fc21.x86_64
apcupsd-3.14.12-3.fc21.x86_64
However the move to Fedora 21 also was done onto new hardware (new motherboard, new GPU, etc). It's possible the bug was hardware related and connected to the old motherboard.

Comment 8 j.fikar 2015-01-09 17:13:48 UTC
I still see the error on kernel 3.17.4 and with apcupsd 3.14.12. I think Mark does not see the error any more, as the corresponding /sys/class/usbmisc/hiddev0/device/../power/control is set to "on", while error shows when it is set to "auto", as it was probably before.

Can you check this?

cat /sys/class/usbmisc/hiddev0/device/../power/control
echo auto > /sys/class/usbmisc/hiddev0/device/../power/control

and wait for an hour or so.

Comment 9 Mark Schlegel 2015-01-14 01:48:28 UTC
@j.fikar

Yes, I've just checked the dmesg after doing the echo you posted to comment 8, 
I'm getting the queue full errors:


[1380214.449980] hid-generic 0003:051D:0002.0002: control queue full
[1380214.470104] hid-generic 0003:051D:0002.0002: control queue full
[1380214.490210] hid-generic 0003:051D:0002.0002: control queue full
[1380214.510314] hid-generic 0003:051D:0002.0002: control queue full


This is on:
Fedora 21 x86_64
Kernel 3.17.7-300.fc21.x86_64
Asus motherboard: P9X79 WS
32 GB RAM
Intel(R) Xeon(R) CPU E5-2609
and the same APC UPS Model SUA1500

Comment 10 Fedora End Of Life 2015-05-29 10:49:33 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 11 Fedora End Of Life 2015-06-29 15:01:52 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 12 Leslie Satenstein 2015-12-29 15:11:01 UTC
Same problem is with Fedora 23.

Comment 13 Leslie Satenstein 2015-12-29 15:13:42 UTC
The RedHat docs do not explain how to empty the queue

From the tail end of dmesg  (many lines)

hid-generic 0003:051D:0002.0001: control queue full


Note You need to log in before you can comment on or make changes to this bug.