<div dir="ltr">I am also having this problem on a Asus B85M-G motherboard connected to a back usb2 port. It works for a few days, and then there is a usb disconnect and reconnect, and that's when I get the "broken pipe" error. Have tried on Gentoo Linux kernels: 3.14.49-hardened and 4.1.6-hardened. Using nut 2.7.2, libusb 1.0.19, and libusb-compat 0.1.5. Once this happens the only way to fix it seems to be to either power cycle the ups or sometimes rebooting the computer a few times might fix it. I did notice it is using the xhci driver even for the motherboard's usb2 ports though and the usb doesn't disconnect if I unbind the two usb2 pci devices from the ehci driver, only when I unbind the single usb3 pci device from the xhci driver.<br><div><br></div><div>Thanks</div><div>Matthew Stapleton</div><div><a href="mailto:matthew4196@gmail.com">matthew4196@gmail.com</a></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 10 August 2014 at 16:10, Leith Bade <span dir="ltr"><<a href="mailto:leith@leithalweapon.geek.nz" target="_blank">leith@leithalweapon.geek.nz</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 10 August 2014 09:05, Charles Lepple <<a href="mailto:clepple@gmail.com">clepple@gmail.com</a>> wrote:<br>
> On Aug 7, 2014, at 7:57 AM, Leith Bade <<a href="mailto:leith@leithalweapon.geek.nz">leith@leithalweapon.geek.nz</a>> wrote:<br>
><br>
</span><span class="">> Error -32 is EPIPE, which means that the PC didn't see a reply from the device during the descriptor read. I don't know that we have ever successfully run one of these issues to ground.<br>
><br>
<br>
</span>Considering Eaton do officially support Linux in their documentation<br>
for this product (as well as make their own Linux UPS client) I will<br>
see if they are able to fix it. Otherwise I will just have to return<br>
it and get another brand.<br>
<br>
Also do you know how I can log more detailed debug info from the<br>
Kernel for USB? Perhaps a dump of all USB data to a file somewhere may<br>
make it easier to see exactly what is going on.<br>
<span class=""><br>
> When you plug into the non-3.0 ports, what HCD driver is it using?<br>
><br>
</span>I generally keep it plugged into the 2.0 ports. Here is the output<br>
from dmesg at boot (when it is working)<br>
[ 0.374422] usbcore: registered new interface driver usbfs<br>
[ 0.374443] usbcore: registered new interface driver hub<br>
[ 0.374503] usbcore: registered new device driver usb:<br>
...<br>
[ 1.508833] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver<br>
[ 1.516042] ehci-pci: EHCI PCI platform driver<br>
[ 1.523181] ehci-platform: EHCI generic platform driver<br>
[ 1.530293] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver<br>
[ 1.537416] ohci-pci: OHCI PCI platform driver<br>
[ 1.544488] ohci-platform: OHCI generic platform driver<br>
[ 1.551537] uhci_hcd: USB Universal Host Controller Interface driver<br>
[ 1.558906] xhci_hcd 0000:00:14.0: xHCI Host Controller<br>
[ 1.565959] xhci_hcd 0000:00:14.0: new USB bus registered, assigned<br>
bus number 1<br>
[ 1.573220] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported<br>
[ 1.573270] xhci_hcd 0000:00:14.0: irq 44 for MSI/MSI-X<br>
[ 1.573418] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002<br>
[ 1.580669] usb usb1: New USB device strings: Mfr=3, Product=2,<br>
SerialNumber=1<br>
[ 1.587899] usb usb1: Product: xHCI Host Controller<br>
[ 1.595059] usb usb1: Manufacturer: Linux 3.13.0-32-generic xhci_hcd<br>
[ 1.602239] usb usb1: SerialNumber: 0000:00:14.0<br>
[ 1.609600] hub 1-0:1.0: USB hub found<br>
[ 1.616605] hub 1-0:1.0: 10 ports detected<br>
[ 1.629387] xhci_hcd 0000:00:14.0: xHCI Host Controller<br>
[ 1.636300] xhci_hcd 0000:00:14.0: new USB bus registered, assigned<br>
bus number 2<br>
[ 1.643425] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003<br>
[ 1.650424] usb usb2: New USB device strings: Mfr=3, Product=2,<br>
SerialNumber=1<br>
[ 1.657393] usb usb2: Product: xHCI Host Controller<br>
[ 1.664350] usb usb2: Manufacturer: Linux 3.13.0-32-generic xhci_hcd<br>
[ 1.671278] usb usb2: SerialNumber: 0000:00:14.0<br>
[ 1.678293] hub 2-0:1.0: USB hub found<br>
[ 1.684992] hub 2-0:1.0: 2 ports detected<br>
...<br>
[ 2.797764] usb 1-10: new low-speed USB device number 4 using xhci_hcd<br>
...<br>
[ 3.423585] usb 1-10: New USB device found, idVendor=0463, idProduct=ffff<br>
[ 3.423599] usb 1-10: New USB device strings: Mfr=1, Product=2,<br>
SerialNumber=0<br>
[ 3.423604] usb 1-10: Product: 5E<br>
[ 3.423605] usb 1-10: Manufacturer: EATON<br>
[ 3.424529] usb 1-10: ep 0x81 - rounding interval to 128<br>
microframes, ep desc says 160 microframes<br>
[ 3.472025] hidraw: raw HID events driver (C) Jiri Kosina<br>
...<br>
<br>
I guess that means it is using xhci_hcd. All USB ports show up as<br>
usb1-x (on both this motherboard and the other motherboard).<br>
<br>
Only other things of interest is that I have only ever had these<br>
plugged into the other USB ports - mouse, keyboard, Sierra 3G modem,<br>
Huawei 3G modem. On the current motherboard various 'virtual' devices<br>
such as mouse, keyboard, floppy, CD drive, and HDD also appear from<br>
the BIOS's remote control features.<br>
<br>
However when I first got these problems was with the previous<br>
motherboard and it would occur if nothing else was plugged in too.<br>
<span class=""><br>
<br>
> I wouldn't recommend using a hub in production, but if you have an older USB hub lying around, does that help? Shorter cables are also useful, though low-speed USB 1.1 is pretty resilient to noise.<br>
><br>
> Also, if you can fix it without rebooting the PC, the issue is probably external to the PC.<br>
><br>
<br>
</span>I will try it with a USB hub. Unfortunately I don't have a shorter<br>
cable currently. The one I am using is an aftermarket generic 1m USB<br>
2.0 cable purchased from a local office supply store (Office Works)<br>
since the UPS did not come with a cable :-( This cable appears to be<br>
good quality as it is rather thick.<br>
<span class=""><br>
><br>
> Did you have a chance to check the NUT archives? I vaguely remember some motherboard-specific threads.<br>
><br>
<br>
</span>A bit of searching did not turn up much. Only thing I found was a<br>
similar error with a MGE unit a few years ago. Did not say anything<br>
about the motherboard.<br>
<br>
Thanks,<br>
Leith Bade<br>
<a href="mailto:leith@leithalweapon.geek.nz">leith@leithalweapon.geek.nz</a><br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@lists.alioth.debian.org">Nut-upsuser@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Matthew Stapleton<br>Email: <a href="mailto:matthew4196@gmail.com" target="_blank">matthew4196@gmail.com</a></div>
</div>