Date: Fri, 25 Jan 2019 11:20:19 +0100 From: Hans Petter Selasky <hps@selasky.org> To: Phil Norman <philnorm@gmail.com> Cc: usb@freebsd.org Subject: Re: Diagnosing probable USB hardware failure Message-ID: <709569e7-a7f8-9431-a83b-ad8d9f5546ec@selasky.org> In-Reply-To: <CAOa8eG7wF12CcfqA8ppSkvOfkUvZ55-3qmtw0nUVR8hWqhWOPw@mail.gmail.com> References: <CAOa8eG5hnBYpuv3s8MR05UZNxN8n8W9=gPv%2BpKhFiARrvx0Lmg@mail.gmail.com> <2ef9ce91-27cb-fced-aa08-1c26b28f3991@selasky.org> <CAOa8eG7wF12CcfqA8ppSkvOfkUvZ55-3qmtw0nUVR8hWqhWOPw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/24/19 10:53 PM, Phil Norman wrote: > I hadn't; thanks for that. > > It certainly spams a lot. I've dumped /var/log/messages (since a recent > reboot with the USB system going nuts) here: > http://splodge.fluff.org/~phil/messages-2019-01-24.txt > Hi, Can you try these quirks in turn. Set them in /boot/loader.conf hw.usb.xhci.ctlstep=1 hw.usb.xhci.dma32=1 hw.usb.xhci.use_polling=1 hw.usb.xhci.xhci_port_route=1 --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?709569e7-a7f8-9431-a83b-ad8d9f5546ec>