New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UPS-hid is severely dysfunctional on Qubes 3.2 #3140

Open
tonsimple opened this Issue Oct 1, 2017 · 0 comments

Comments

Projects
None yet
2 participants
@tonsimple

tonsimple commented Oct 1, 2017

Qubes OS version (e.g., R3.2):

R 3.2

Affected TemplateVMs (e.g., fedora-23, if applicable):

Dom0


Steps to reproduce the behavior:

  1. Have a UPS that has basic USB-hid functionality to provide linux with basic battery level monitoring features

//=====//

Tested: two powercom UPS (including SPT 3000)

One APC

One Cyberpower

//=====//

  1. Connect the UPS to a USB port that goes directly to Dom0 (where we would reasonably want all the battery-related actions, such as low power shutdown taking place)

  2. Observe some anomalies right away (see below)

  3. observe failure of low-battery shutdown if battery indeed is low.

Expected behavior:

Ups would report battery accurately and Dom0 would trigger a shutdown when a battery level specified in power manager is reached

Actual behavior:

  1. even when not on backup power, the power manager constantly spuriously reports "UPS is empty" followed by "UPS is full"

(it is full indeed). Frequent "UPS is empty" spam is both suspicious and frankly a bit scary. Spam usually stops after a while.)

  1. when on backup power, and power drops below the level specified as "shutdown" level in power manager (say, shutdown level set to 50%, and UPS drops to say, 49% or lower), no shutdown happens

General notes:

Before reporting, I gathered several UPS units from work and from friends, and tested them.

Same behavior on all of them, though "UPS is empty" message spam behavior seemed to differ between UPS models, being most frequent and persistent on powercoms, and only happening twice on APC.


Related issues:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment