nut/apc values sparse after update to 11.2

2018-09-03 Thread Gerrit Kühn
Hi all, I just upgraded a server from 11.1 to 11.2. After this, nut appears to read only very few values from the ups attached via usbhid to the box. With 11.1, upslog recorded all relevant values: --- 20180903 134024 100.00 226.30 46.30 [OL] 27.00 50.00 --- With 11.2, upslog only reports

Re: nut/apc values sparse after update to 11.2

2018-09-03 Thread Hans Petter Selasky
On 9/3/18 3:08 PM, Gerrit Kühn wrote: Hi all, I just upgraded a server from 11.1 to 11.2. After this, nut appears to read only very few values from the ups attached via usbhid to the box. With 11.1, upslog recorded all relevant values: --- 20180903 134024 100.00 226.30 46.30 [OL] 27.00 50.00

Re: nut/apc values sparse after update to 11.2

2018-09-03 Thread Gerrit Kühn
On Mon, 3 Sep 2018 15:37:18 +0200 Hans Petter Selasky wrote about Re: nut/apc values sparse after update to 11.2: > Did you check the permissions for the USB device? Yes, they should be fine: --- # ll /dev/uhid0 crw-r- 1 uucp uucp 0xde Sep 3 15:40 /dev/uhid0 --- > Did you try to re-att

Re: nut/apc values sparse after update to 11.2

2018-09-03 Thread Hans Petter Selasky
On 9/3/18 4:05 PM, Gerrit Kühn wrote: On Mon, 3 Sep 2018 15:37:18 +0200 Hans Petter Selasky wrote about Re: nut/apc values sparse after update to 11.2: Did you check the permissions for the USB device? Yes, they should be fine: --- # ll /dev/uhid0 crw-r- 1 uucp uucp 0xde Sep 3 15:40

Re: nut/apc values sparse after update to 11.2

2018-09-03 Thread Gerrit Kühn
On Mon, 3 Sep 2018 16:14:34 +0200 Hans Petter Selasky wrote about Re: nut/apc values sparse after update to 11.2: > What does uname -a tell about your current kernel? It's the latest I got via freebsd-update: --- # uname -a FreeBSD crest.rt.aei.uni-hannover.de 11.2-RELEASE-p2 FreeBSD 11.2-RELE

[Bug 231076] libusb_cancel_transfer() does NOT cancel a transfer after the USB device is removed

2018-09-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231076 --- Comment #3 from Ludovic Rousseau --- I added logs in my code. When I start the transfer I have: 0006 ccid_usb.c:1329:InterruptRead() uxfer->dev_handle: 0x28c0c9c0 When I cancel the transfer I have: 0004 ccid_usb.c:1399:Interrup

[Bug 231076] libusb_cancel_transfer() does NOT cancel a transfer after the USB device is removed

2018-09-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231076 --- Comment #4 from Hans Petter Selasky --- >I added a call to libusb_set_debug(ctx, LIBUSB_LOG_LEVEL_DEBUG); in my code but >I don't see more debug. >I see that libusb uses DPRINTF(). How can I get the generated log messages? LIBU