From owner-freebsd-usb@freebsd.org Fri Jan 25 16:16:53 2019 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A4BFF14BA8FD for ; Fri, 25 Jan 2019 16:16:53 +0000 (UTC) (envelope-from philnorm@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E6CE48AF1F for ; Fri, 25 Jan 2019 16:16:52 +0000 (UTC) (envelope-from philnorm@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id AAB1A14BA8FA; Fri, 25 Jan 2019 16:16:52 +0000 (UTC) Delivered-To: usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 87FC614BA8F8 for ; Fri, 25 Jan 2019 16:16:52 +0000 (UTC) (envelope-from philnorm@gmail.com) Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 034C58AF1C for ; Fri, 25 Jan 2019 16:16:52 +0000 (UTC) (envelope-from philnorm@gmail.com) Received: by mail-wm1-x32a.google.com with SMTP id r24so5150539wmh.0 for ; Fri, 25 Jan 2019 08:16:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Nz26DU8XfzcVQsW3mpcqwgO4WU1Cf6Ol01k9xNkvjRc=; b=uSZkurqDuQB6xceYAnWrDDHUrZQbpRM6okiLN2UUpGeFSC2mCPpfQwYLViWcMD7Jnr ADQNJiBgK9SRaMxKH+CmTVbxYKX7rH2S54iWuO+Iydadn9y6zXSI2zTX9HtLBAbZa7+6 leou4CwHWLu5bcLIOF17Hy+YMleX8uxFd8WXTnvMflZkHvpuWEfYfOzc2H9dFrB/8OQw Mj/Q6/kgeq2kslyRl7jBqpOFRhS1qw7yr2tVJbZeppD5M8JpAen/f8Sxud078Vsf2SAx mEpLx8ELbpmcHvf5r2nhdVMwRD0MI60SeAXQaMqxa3WIGAZPlmwypn00A9FBhc2A6N4f GC3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Nz26DU8XfzcVQsW3mpcqwgO4WU1Cf6Ol01k9xNkvjRc=; b=YHx7VZ7OghfB/f6UQwRMaH6yIb392nbJI+7uBTVcbBLjiVNnDQ+g2YTa4Q8ClRKK2X x031ytBLex4dborc7ysyKGsuuuT42V5EAisY+rhYqt0x44hlcHgE7Xq7S9dYTDfpmhSO SBAddBMzs46jEVOF2/7t/29e+hCt1tEMK199035dYa5tH3ysN4XyRS4q4dkJzHilZxQJ W4p2y1SftX7LfywZE90W1Fe3DG3Wi0jjMvs3+s36AX9eUnWrqqVSBDzd7/iKWYIgCmQ1 TxkPqSVhsT+h1lIhrYZqswQmSLpTKK0ViB14iZHvI1KGtiomo1fD7ql56LezEZUZCjJM sqoA== X-Gm-Message-State: AJcUukd+6cD1Rr4ZjwO/IbkB5IlO1n/BZ0tD8LjkV82m0YQw6zMgrS/h 3fdOhdk/4VhCAMXJF9RZw6xPsAFg/ORXnuqJSKU58Q== X-Google-Smtp-Source: ALg8bN5n3NeF1sb0iG5vtkuE+I/M8yTr8uDxExbrZYse2s1AqMVzeRyAfO1NKUBPfZm19xdXwMABFXzbWhSiJEsVLJw= X-Received: by 2002:a1c:1688:: with SMTP id 130mr7171449wmw.86.1548433010783; Fri, 25 Jan 2019 08:16:50 -0800 (PST) MIME-Version: 1.0 References: <2ef9ce91-27cb-fced-aa08-1c26b28f3991@selasky.org> <709569e7-a7f8-9431-a83b-ad8d9f5546ec@selasky.org> In-Reply-To: <709569e7-a7f8-9431-a83b-ad8d9f5546ec@selasky.org> From: Phil Norman Date: Fri, 25 Jan 2019 17:16:39 +0100 Message-ID: Subject: Re: Diagnosing probable USB hardware failure To: Hans Petter Selasky Cc: usb@freebsd.org X-Rspamd-Queue-Id: 034C58AF1C X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.96 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.96)[-0.957,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2019 16:16:53 -0000 Hi Thanks for the suggestion; I tried them all (enabling one at a time, but ending up with all four set), and I get the same USB_ERR_TIMEOUT loop on each boot. Note that even before I get to the FreeBSD bootloader screen (so while the UEFI thing is initialising), there's a very significant (5-10s) delay on a warm boot, during which the keyboard caps lock light won't toggle; this doesn't happen on a cold boot. For this reason, I strongly suspect a hardware failure. My main question is really, how I figure out if it's the CPU or the motherboard at fault. I'd rather not change the wrong one, or unnecessarily change a working part. I notice the internet has quite a few stories of this motherboard having USB difficulties (allegedly due to build quality issues); that would be my main suspicion, although I managed to bend some of the CPU pins, and had to bend them back with a needle, so I can't rule that out either (note: I did get all the pins back straight, and none fell off, or gave a feeling of wobbliness or weakness). Thanks, Phil On Fri, 25 Jan 2019 at 11:22, Hans Petter Selasky wrote: > 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 >