Nut upsuser - Dec 2007 - Battery is low bug (again) w/ Belkin/USB UPS (2.x=bug, < 2.0 works)

Hello,

http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-September/003137.html
http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-July/003014.html
http://permalink.gmane.org/gmane.comp.monitoring.nut.user/2552

I still have this problem:

$ dpkg -l | grep -i nut
ii  nut                                  2.2.0-2       The core system

I thought this bug was fixed :(
syslog:Dec 10 18:56:15 p34 upsmon[2672]: UPS belkin at localhost battery is 
low
syslog:Dec 10 18:57:05 p34 upsmon[2672]: UPS belkin at localhost battery is 
low
syslog:Dec 10 19:01:00 p34 upsmon[2672]: UPS belkin at localhost battery is 
low

Any work-arounds available if I want to run 2.2.0-2?

This was a bug one of the developers responded to earlier it was the way 
the kernel dealt with certain messages in the usb/kernel level.

Same UPS, old version, same thing works fine, but new version keeps saying 
battery is low, kernel 2.6.23.9:

Bus 005 Device 003: ID 050d:0912 Belkin Components
Device Descriptor:
   bLength                18
   bDescriptorType         1
   bcdUSB               1.10
   bDeviceClass            0 (Defined at Interface level)
   bDeviceSubClass         0
   bDeviceProtocol         0
   bMaxPacketSize0         8
   idVendor           0x050d Belkin Components
   idProduct          0x0912
   bcdDevice            0.06
   iManufacturer           4
   iProduct               20 UPS
   iSerial                 0
   bNumConfigurations      1
   Configuration Descriptor:
     bLength                 9
     bDescriptorType         2
     wTotalLength           34
     bNumInterfaces          1
     bConfigurationValue     1
     iConfiguration          0
     bmAttributes         0xc0
       Self Powered
     MaxPower               20mA
     Interface Descriptor:
       bLength                 9
       bDescriptorType         4
       bInterfaceNumber        0
       bAlternateSetting       0
       bNumEndpoints           1
       bInterfaceClass         3 Human Interface Devices
       bInterfaceSubClass      0 No Subclass
       bInterfaceProtocol      0 None
       iInterface              0
         HID Device Descriptor:
           bLength                 9
           bDescriptorType        33
           bcdHID               1.00
           bCountryCode           33 US
           bNumDescriptors         1
           bDescriptorType        34 Report
           wDescriptorLength     820
          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     0x0008  1x 8 bytes
         bInterval             248
Device Status:     0x0001
   Self Powered

Justin.

>
http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-September/003137.html
> http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-July/003014.html
> http://permalink.gmane.org/gmane.comp.monitoring.nut.user/2552
>
> I still have this problem:
>
> $ dpkg -l | grep -i nut
> ii  nut                                  2.2.0-2       The core system
>
> I thought this bug was fixed :(
It is, in nut-2.2.1 (which is scheduled to be released shortly) or in the
development version. The version you have now, was released early this
year, so that still has this bug.

[...]
> Any work-arounds available if I want to run 2.2.0-2?
No, you'll need to upgrade to nut-2.2.1 once that becomes available or run
the development version.
> This was a bug one of the developers responded to earlier it was the way
> the kernel dealt with certain messages in the usb/kernel level.
No, it's how NUT deals with a faulty report received over the interrupt
pipeline. Essentially, this is a bug in your UPS for which we have created
a workaround. So Belkin is to blame here, not NUT.
> Same UPS, old version, same thing works fine, but new version keeps saying
> battery is low, kernel 2.6.23.9:
Like we explained before, the older versions ignored this report on the
interrupt pipeline. However, the report buffering mechanism that was added
in nut-2.0.5 could let some faulty report leak through. This has been
fixed in nut-2.2.1.

Best regards, Arjen
-- 
Eindhoven - The Netherlands
Key fingerprint - 66 4E 03 2C 9D B5 CB 9B  7A FE 7E C1 EE 88 BC 57