Project

General

Profile

Bug #17796

blazer_usb problem (but maybe not driver problem ?)

Added by Jan Brońka about 4 years ago. Updated almost 4 years ago.

Status:
Closed: Third party to resolve
Priority:
Nice to have
Assignee:
Jan Stevenson
Category:
OS
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

I have ups connected with FreeNas via USB (driver blazer_usb). Configuration works fine for several monthes with FreeNas 9.3 (updated with latest available updates). Now, after update to 9.10, regulary comunication with ups fails. It means... when I start service using UI all is working fine for few hours, next looks like driver crash and service reports communication problems. When I restart service again all is again working fine.

I checked folder /var/db/nut when all works fine and later when communication fails and I see that file blazer_usb-ugen0.3.pid does not exist, so looks like driver really crash.

Console log when I stop service (when it failed):
STOP:
Sep 27 07:21:26 PROD-1S notifier: Stopping nut_upslog.
Sep 27 07:21:26 PROD-1S notifier: Waiting for PIDS: 73617.
Sep 27 07:21:26 PROD-1S notifier: Stopping nut_upsmon.
Sep 27 07:21:26 PROD-1S upsmon73600: upsmon parent: read
Sep 27 07:21:27 PROD-1S notifier: Waiting for PIDS: 73601, 73601.
Sep 27 07:21:27 PROD-1S notifier: Stopping nut.
Sep 27 07:21:27 PROD-1S upsd73584: mainloop: Interrupted system call
Sep 27 07:21:27 PROD-1S notifier: Waiting for PIDS: 73584.
Sep 27 07:21:27 PROD-1S notifier: Can't open /var/db/nut/blazer_usb-ugen0.3.pid: No such file or directory

Console log when I start service again:
Sep 27 07:21:27 PROD-1S notifier: Network UPS Tools - UPS driver controller 2.7.3
Sep 27 07:22:04 PROD-1S notifier: Supported UPS detected with megatec protocol
Sep 27 07:22:04 PROD-1S notifier: Vendor information read in 1 tries
Sep 27 07:22:04 PROD-1S notifier: No values provided for battery high/low voltages in ups.conf
Sep 27 07:22:04 PROD-1S notifier:
Sep 27 07:22:04 PROD-1S notifier: Using 'guestimation' (low: 41.600000, high: 52.000000)!
Sep 27 07:22:04 PROD-1S notifier: Battery runtime will not be calculated (runtimecal not set)
Sep 27 07:22:05 PROD-1S notifier: Network UPS Tools - UPS driver controller 2.7.3
Sep 27 07:22:05 PROD-1S notifier: Starting nut.
Sep 27 07:22:05 PROD-1S notifier: fopen /var/db/nut/upsd.pid: No such file or directory
Sep 27 07:22:05 PROD-1S notifier: listening on 0.0.0.0 port 3493
Sep 27 07:22:05 PROD-1S notifier: Connected to UPS [ups]: blazer_usb-ups
Sep 27 07:22:05 PROD-1S notifier: /usr/local/etc/nut/cmdvartab not found - disabling descriptions
Sep 27 07:22:05 PROD-1S notifier: Starting nut_upsmon.
Sep 27 07:22:05 PROD-1S notifier: kill: No such process
Sep 27 07:22:05 PROD-1S notifier: UPS: ups (master) (power value 1)
Sep 27 07:22:05 PROD-1S notifier: Using power down flag file /etc/nokillpower
Sep 27 07:22:05 PROD-1S notifier: Starting nut_upslog.

History

#1 Avatar?id=14398&size=24x24 Updated by Kris Moore about 4 years ago

  • Assignee set to Suraj Ravichandran
  • Target version set to 9.10.1-U2

Over to Suraj for Investigation

#2 Updated by Vaibhav Chauhan about 4 years ago

  • Target version changed from 9.10.1-U2 to 9.10.1-U3

#3 Updated by Vaibhav Chauhan about 4 years ago

  • Target version changed from 9.10.1-U3 to 9.10.1-U2

#4 Updated by Suraj Ravichandran about 4 years ago

I have zero UPS experience and no blazer_usb ups hardware to test/investigate this.

The very fact that when the service starts up all is fine and later on it has issues, prompts me to suggest that there is something wrong within the nut ups code itself (maybe with their blazer_usb driver?) and that would mean I close this with a "Third Party to Resolve" and suggest you (@Jan Brońka) go over to the nut folks and ask them for help.

However, since I may be wrong, I am handing this over to @Jan Stevenson (she has some ups experience as of recently) to request her to take a looksy.

#5 Updated by Suraj Ravichandran about 4 years ago

  • Assignee changed from Suraj Ravichandran to Jan Stevenson
  • Priority changed from No priority to Nice to have

#6 Updated by Jan Stevenson about 4 years ago

Hi Jan,

May I request you attach a debug file to this ticket, please? From the UI, System->Advanced->Save Debug button at bottom of screen. Thanks.

#7 Updated by Jan Stevenson about 4 years ago

Hi Jan, on second thoughts, after looking at the contents of the debug file on my FreeNAS with the UPS service running, I'm not seeing the files that I wanted to see from your config, namely all the files in /etc/local/nut. Plus looking closer at your details, this issue is probably best worked out by contacting the NUT project people: http://networkupstools.org/support.html.

#8 Updated by Jan Stevenson about 4 years ago

  • Status changed from Unscreened to Screened

#9 Updated by Jan Stevenson about 4 years ago

  • Status changed from Screened to Closed: Third party to resolve

#10 Updated by Jan Brońka about 4 years ago

I just updated 9.10 with recent updates (provided today or yestaerday). Let me check if they fix anything. If not I will go follow your recommendation and contact NUT team directly.

#11 Updated by Jan Stevenson about 4 years ago

Thanks Jan. Yes please update back here with results you see from updating to a newer 9.10 build. Also, if you could update the seen-in field with the version you saw the blazer_usb driver crash in?

#12 Updated by Jan Brońka about 4 years ago

  • Seen in changed from Unspecified to 9.10.1

#13 Updated by Jan Brońka about 4 years ago

"Seen-in" updated but I'm not 100% sure it is this version as boot name is "FreeNAS-ca82ba222c0be179a6983636c50732c3" but backup of configuration is marked as "xxxx-FreeNAS-9.10.1 (d989edd)-20160917151516.db"

#14 Updated by Jan Brońka almost 4 years ago

  • Subject changed from blazer_usb problem to blazer_usb problem (but maybe not driver problem ?)
  • Seen in changed from 9.10.1 to 9.10.1-U4

Let me back to this, my problem...

I found in logs (and this is regular case) some interesting information:

PROD-2S.igexao.local kernel log messages:

ugen1.3: <Prolific Technology Inc.> at usbus1 (disconnected)
uplcom0: at uhub4, port 1, addr 3 (disconnected)
usb_alloc_device: set address 3 failed (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
ugen1.3: <Unknown> at usbus1 (disconnected)
uhub_reattach_port: could not allocate new device
usb_alloc_device: set address 3 failed (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
ugen1.3: <Unknown> at usbus1 (disconnected)
uhub_reattach_port: could not allocate new device
ugen1.3: <Prolific Technology Inc.> at usbus1
uplcom0: <Prolific Technology Inc. USB-Serial Controller D, class 0/0, rev 1.10/4.00, addr 3> on usbus1
ugen1.3: <Prolific Technology Inc.> at usbus1 (disconnected)
uplcom0: at uhub4, port 1, addr 3 (disconnected)
ugen1.3: <Prolific Technology Inc.> at usbus1
uplcom0: <Prolific Technology Inc. USB-Serial Controller D, class 0/0, rev 1.10/4.00, addr 3> on usbus1
ugen1.3: <Prolific Technology Inc.> at usbus1 (disconnected)
uplcom0: at uhub4, port 1, addr 3 (disconnected)
ugen1.3: <Prolific Technology Inc.> at usbus1
uplcom0: <Prolific Technology Inc. USB-Serial Controller D, class 0/0, rev 1.10/4.00, addr 3> on usbus1
ugen1.3: <Prolific Technology Inc.> at usbus1 (disconnected)
uplcom0: at uhub4, port 1, addr 3 (disconnected)
ugen1.3: <Prolific Technology Inc.> at usbus1
uplcom0: <Prolific Technology Inc. USB-Serial Controller D, class 0/0, rev 1.10/4.00, addr 3> on usbus1
ugen1.3: <Prolific Technology Inc.> at usbus1 (disconnected)
uplcom0: at uhub4, port 1, addr 3 (disconnected)
usb_alloc_device: set address 3 failed (USB_ERR_TIMEOUT, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
ugen1.3: <Unknown> at usbus1 (disconnected)
uhub_reattach_port: could not allocate new device
usb_alloc_device: set address 3 failed (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
ugen1.3: <Unknown> at usbus1 (disconnected)
uhub_reattach_port: could not allocate new device
usb_alloc_device: set address 3 failed (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
ugen1.3: <Unknown> at usbus1 (disconnected)
uhub_reattach_port: could not allocate new device
usb_alloc_device: set address 3 failed (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
ugen1.3: <Unknown> at usbus1 (disconnected)
uhub_reattach_port: could not allocate new device
ugen1.3: <Prolific Technology Inc.> at usbus1
uplcom0: <Prolific Technology Inc. USB-Serial Controller D, class 0/0, rev 1.10/4.00, addr 3> on usbus1

As I explained I have 2 systems on which I observate similar problem. I moved back one of them to FN9.3 (last update) and for 2 days system is working without problem (FY9.10 reports problem after few hours).

To have it working (FY9.10) I just need, from GUI restart UPS service... and again all is fine for few hours.

Also available in: Atom PDF