From owner-freebsd-stable@freebsd.org Tue Apr 18 13:12:24 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 289D3D4320C for ; Tue, 18 Apr 2017 13:12:24 +0000 (UTC) (envelope-from kami@freebsd.org) Received: from bsdforen.de (bsdforen.de [82.193.243.115]) by mx1.freebsd.org (Postfix) with ESMTP id E5CD21AD1 for ; Tue, 18 Apr 2017 13:12:23 +0000 (UTC) (envelope-from kami@freebsd.org) Received: from localhost (iz-aix-213a.HS-Karlsruhe.DE [193.196.64.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by bsdforen.de (Postfix) with ESMTPSA id 2C4569C0F3 for ; Tue, 18 Apr 2017 15:03:56 +0200 (CEST) Date: Tue, 18 Apr 2017 15:03:43 +0200 From: Dominic Fandrey To: freebsd-stable@freebsd.org Subject: Re: Unsupported USB BT device causes high interrupt load Message-Id: <20170418150343.24c6e436bf5baecd835b2d0d@freebsd.org> In-Reply-To: <20170406121635.99a513360faaf2f40992fb8a@freebsd.org> References: <20170406121635.99a513360faaf2f40992fb8a@freebsd.org> Organization: FreeBSD X-Mailer: Sylpheed 3.5.1 Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA512"; boundary="Signature=_Tue__18_Apr_2017_15_03_44_+0200_y+dvKsE=o7L8I6XL" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2017 13:12:24 -0000 --Signature=_Tue__18_Apr_2017_15_03_44_+0200_y+dvKsE=o7L8I6XL Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > I have an Interrupt load of 2000 interrupts/s from xhci0. >=20 > As the culprit I have identified the following device: >=20 > ugen0.6: at usbus0, cfg=3D255 md=3DHOST sp= d=3DFULL (12Mbps) pwr=3DON (100mA) >=20 > =E2=80=A6 The device spamms me with interrupts after every boot and resume until I send it a power_off command. For anyone else with a similar problem, I'm using the following devd rule to mitigate the issue (https://pastebin.com/raw/HmDur3Le): notify 100 { match "system" "USB"; match "subsystem" "INTERFACE"; match "type" "ATTACH"; match "vendor" "0x8087"; match "product" "0x07dc"; action "usbconfig -d $cdev power_off"; }; --=20 A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?=20 --Signature=_Tue__18_Apr_2017_15_03_44_+0200_y+dvKsE=o7L8I6XL Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEfYhGEP+7uobxe8A3b/BdaakqWdsFAlj2DrBfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDdE ODg0NjEwRkZCQkJBODZGMTdCQzAzNzZGRjA1RDY5QTkyQTU5REIACgkQb/Bdaakq WdtQ5wgAnVrskRSNereWiH1EZDMAtf4ZUYS9bHQj79zKlwbghfjGIyxTdydJzDZZ RNI9UHHqYlfEoz4i8ua3mFlq3/GmWazCZt5p6gI3+GHEtFJysaD4R4pL5kBjxmDQ GXth7kY/gFeqHYwikrqjAD3ZZ50c9KDa7pQ1oR7DnfsNxfpMxSeJ8f/aU6wVLub6 qMnwLrlMCuZJZFReHeOLVRNA02YKkrhTDT3/pvH363s6yq3g+PAVr7sGJSoEu1zF Q1/Hvc9pXAtR2+urEjn/OwhdSn91OVNEaJDLPOTY2pGsJy+6AtclMHdH7AFNKe5E 1WFOZzP/HrfAAHeW6x7xcFfnhS0/ew== =dMjb -----END PGP SIGNATURE----- --Signature=_Tue__18_Apr_2017_15_03_44_+0200_y+dvKsE=o7L8I6XL--