From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 6 19:57:42 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5E00A318 for ; Sat, 6 Sep 2014 19:57:42 +0000 (UTC) Received: from bein.link (vps-6159-8629.cloud.tilaa.com [37.252.124.82]) by mx1.freebsd.org (Postfix) with ESMTP id 254801E2C for ; Sat, 6 Sep 2014 19:57:41 +0000 (UTC) Received: from quad.localnet (unknown [188.134.8.193]) by bein.link (Postfix) with ESMTPSA id D511640520 for ; Sat, 6 Sep 2014 21:57:38 +0200 (CEST) From: Maxim V FIlimonov To: freebsd-hackers@freebsd.org Subject: What to do if USB stack seems dead Date: Sat, 06 Sep 2014 23:57:37 +0400 Message-ID: <1455331.JKPkSxLmbq@quad> User-Agent: KMail/4.12.5 (FreeBSD/10.0-RELEASE-p7; KDE/4.12.5; amd64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Sep 2014 19:57:42 -0000 Lately, I've been heavily experimenting with different USB devices (for instance, USB to TTL one, but that's another story), and at a moment I encountered that the system doesn't react on new USB devices connected. The connected devices work fine, though. The question is: what can I do in such a case if I don't want to reboot my box? -- wbr, Maxim Filimonov che@bein.link