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

Justin Piszcz jpiszcz at lucidpixels.com
Tue Dec 11 13:28:07 UTC 2007

On Tue, 11 Dec 2007, Arjen de Korte wrote:

>> 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
> 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

Is this available in unstable (the dev-version with the fix/if not what is 
the ETA and also the ETA for 2.2.1 in testing)?



More information about the Nut-upsuser mailing list