From owner-freebsd-usb@freebsd.org Wed May 2 13:57:46 2018 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 BD14CFAA81C for ; Wed, 2 May 2018 13:57:46 +0000 (UTC) (envelope-from lists@eitanadler.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 3BA897DB99 for ; Wed, 2 May 2018 13:57:46 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mailman.ysv.freebsd.org (Postfix) id F0A44FAA81B; Wed, 2 May 2018 13:57:45 +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 DAEDAFAA81A for ; Wed, 2 May 2018 13:57:45 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 632397DB97 for ; Wed, 2 May 2018 13:57:45 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yw0-x231.google.com with SMTP id l15-v6so4555905ywk.3 for ; Wed, 02 May 2018 06:57:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=cWTuQyNgJGN97J9zbfYZtWA4h4Gz8RP/v07v1YwRc1Q=; b=FgpB6Gzfe72tiVhPGU2Kf104phWAry+2pEgvMNvguQr2pygk4Fh2p7Q9HrkAB1gkZL pjM0+HFR+8EdZyt+xSbjATzx14IMO4lcfnUZt5i1RAIjwuVmlqD9ch89vyOAz9pcl58V yMmhuR0s1fk+BKfkSkODovhc3bDfGX3EUQwr4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=cWTuQyNgJGN97J9zbfYZtWA4h4Gz8RP/v07v1YwRc1Q=; b=Wh6njDMWp+cZJih8NqjI/+6CIaqKIAOxr9R2wegZ140vCEoTly6HbWSL2iLHeCtVK1 m6uGcjvTJR67e5TrBLB0vDNiig+TFO6ocUb3BPQRN8VVPXSWM0FNr9K+T2sRab2QSsEz JJ/TYSjeVke1E/q9fjOhtns2pAYXMWJlvk5TmUk1H9LE4Kght0bZjkBGf2TsuDh+/9+C vPjfT96MdkhJkrtJ6Hqq2C6kbLS7f3cb1YyMQInTyNTdlpYe/n72DiXtC2tPfxRO86oG VDhzQyXry88blq8crFCsueaaDFfTCVUG/yEma16sNR5LYMp4LoPKl+TeKq22nkcZ+jz8 hDLg== X-Gm-Message-State: ALQs6tB+wX2b64Sj9wYK26cU05EZdkEucXuIMfSLTNZt3dMA4Ilu1zpz k2Ay1g8bGyVjQSKSTF2qWjkvHMP2WI6T3gDNbNA/yA== X-Google-Smtp-Source: AB8JxZpgFDA1RVymbVAPcFlngF2gXicGWnWwNkHhLQLcYfKbOHjolMkk7uJG2IWSYmeqcZShtoGmBCpYqQj3LPidREM= X-Received: by 2002:a81:3e1f:: with SMTP id l31-v6mr10730224ywa.37.1525269464667; Wed, 02 May 2018 06:57:44 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:c709:0:0:0:0:0 with HTTP; Wed, 2 May 2018 06:57:14 -0700 (PDT) In-Reply-To: References: From: Eitan Adler Date: Wed, 2 May 2018 06:57:14 -0700 Message-ID: Subject: Re: IRQ storm on xhci0 To: Hans Petter Selasky Cc: usb@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 May 2018 13:57:47 -0000 On 2 May 2018 at 00:22, Hans Petter Selasky wrote: > On 05/02/18 06:22, Eitan Adler wrote: >> >> On 1 May 2018 at 20:53, Eitan Adler wrote: >>> >>> Hi all, >>> >>> I am noticing consistently high IRQ rates on xhci0 >>> >>> example from vmstat -i right now: >>> irq259: xhci0 2222153 1876 >>> >>> and this is not the highest I've seen. >>> >>> My understanding is that a rate of 1876/s is insane for USB devices. >>> Any suggestions of what I can do to debug? >>> >>> Things I've tried: >>> - disabling MSI interrupts >>> - disabling MSI-X interrupts >>> - powering off all usb devices using usbconfig >>> - unplugging all USB devices >>> >>> One thing of note: >>> My mobo has a broken USB connector resulting in one of the two front >>> USB-3 ports not working. I'm guessing this is related but I'd like >>> some confirmation and/or a way to bypass the issue in software. >> >> >> with insane debugging enabled: >> > > Try to see with usbdump if any traffic is passing on xhci0. Heh. should have added that to the list of things I did. There is no traffic. -- Eitan Adler