From owner-freebsd-stable@FreeBSD.ORG Wed Mar 7 18:16:01 2007 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EA03A16A409 for ; Wed, 7 Mar 2007 18:16:01 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id 5620813C4B9 for ; Wed, 7 Mar 2007 18:16:01 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (uhktgb@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l27IFsQe061557; Wed, 7 Mar 2007 19:15:59 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l27IFrnb061556; Wed, 7 Mar 2007 19:15:53 +0100 (CET) (envelope-from olli) Date: Wed, 7 Mar 2007 19:15:53 +0100 (CET) Message-Id: <200703071815.l27IFrnb061556@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, ivoras@fer.hr In-Reply-To: X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 07 Mar 2007 19:15:59 +0100 (CET) Cc: Subject: Re: USB problem - how to disable an umass device? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, ivoras@fer.hr List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2007 18:16:02 -0000 Ivan Voras wrote: > Oliver Fromme wrote: > > Of course, a better way to solve the problem would be to > > find out _why_ it is hanging in the first place. :-) > > The first step would be to enter the kernel debugger and > > take a stack trace, in order to find out where it is stuck. > > > > It might be a good idea to take this issue to the freebsd- > > usb mailing list. > > Actually, it resolved to be a very large timeout, on the order of > 5 minutes per step, before something gives up and the boot process > continues. That sounds like a bug where a loop counter isn't initialized correctly, so a loop wraps around and has to go through the whole range of a 32 bit int until it terminates, i.e. 2^32 which is 4 billion interations. Depending on what the loop actually contains, that could very well take 5 minutes. There have been bugs like that in the past. If you enter the Debugger during the hang and print a stack trace, you should be able to see where that loop is. Maybe it's easy to spot the incorrect loop counter and fix it. > > > I tried using loader hint hint.usb.2.disabled="1" but it doesn't > > > work. > > > > Unfortunately, hints cannot be used to disable devices in > > general (which would be a desirable feature). That only > > works for legacy devices (i.e. ISA) and some others. > > I'd argue that this is actually a bad thing - I'm sure there are > situations where it would be useful to disable (almost) arbitrary > nodes in the device tree, even down to specific pci busses. Yes, that's what I mean. I'm sure it could be useful. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "A language that doesn't have everything is actually easier to program in than some that do." -- Dennis M. Ritchie