Flickering connection to UPS (again, but now I'm sure it is Ok under Windows)

[Lev Serebryakov]

On 07.05.2021 17:14, Hans Petter Selasky wrote:

>> ster kernel: xhci_roothub_exec: port status=0x000202a0
>> May  7 14:39:08 hamster kernel: xhci_roothub_exec: type=0x23 request=0x01 wLen=0x0000 wValue=0x0010 wIndex=0x0002
>> May  7 14:39:08 hamster kernel: xhci_roothub_exec: UR_CLEAR_PORT_FEATURE
>> May  7 14:39:08 hamster kernel: xhci_device_state_change: May  7 14:39:08 hamster kernel: ugen0.6: <PPC Offline UPS> at usbus0 (disconnected)
> 
> The value reported by XHCI PORTSC, 0x000202a0, indicates:
> 
> BIT5-8 : 5) Link is in the RxDetect State
> BIT9 : Port Power (PP) – RWS. Default = ‘1’
> BIT17 : Connect Status Change (CSC)
> 
> It is clear that the XHCI controller has received a disconnect event from the UPS.
> Can you check the other OS'es where this supposedly does not happen, if the UPS device attaches to the XHCI or EHCI controller?

  Windows 10 Device Manager shows it under "Intel(R) USB 3.1 eXtensible Host Controller". This laptop (with Windows 10) has only USB-C ports...

  I've captured sessions on Windows with "Device Monitoring Studio" and WireShark (it was two sessions, not one) and uploaded them at

http://lev.serebryakov.spb.ru/_sklad/ups/

ups-windows-dms.dump - dump from "Device Monitoring Studio"
ups-windows-dms.log  - log from "Device Monitoring Studio"
ups-windows-wireshark.pcapng - dump from WireShark
ups-windows-wireshark.txt    - dissection export from WireShark.

  My FreeBSD laptop (Lenovo T540p) has both USB 2.0 an USB 3.0 ports, and UPS flickers in both.

> Did you start any driver for the UPS?
  On FreeBSD — I'm not (`nut` supports this UPS, but it detects device slower than UPS stay connected).

  Windows 10, Windows installs something generic and not very useful (it shows battery level as 0%), but "provided" software (very crude one) works and shows plausible information.

  Windows 10 shows it as "HID UPS Battery" in device manager.


-- 
// Lev Serebryakov