From owner-freebsd-stable@FreeBSD.ORG Fri Sep 26 12:15:31 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE34016A4B3 for ; Fri, 26 Sep 2003 12:15:31 -0700 (PDT) Received: from rutger.owt.com (rutger.owt.com [204.118.6.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96BC044055 for ; Fri, 26 Sep 2003 12:15:24 -0700 (PDT) (envelope-from kstewart@owt.com) Received: from topaz-out (owt-207-41-94-233.owt.com [207.41.94.233]) by rutger.owt.com (8.11.6p2/8.9.3) with ESMTP id h8QJFKw31044; Fri, 26 Sep 2003 12:15:20 -0700 From: Kent Stewart To: Joe Kelsey , Brandon Fosdick Date: Fri, 26 Sep 2003 12:15:19 -0700 User-Agent: KMail/1.5.4 References: <3F746937.2070409@mail.flyingcroc.net> <3F7486B3.4090009@terrandev.com> <3F748E20.4070605@mail.flyingcroc.net> In-Reply-To: <3F748E20.4070605@mail.flyingcroc.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309261215.19852.kstewart@owt.com> cc: stable@freebsd.org Subject: Re: 4.9 Boot Hang when USB Devices Attached X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Sep 2003 19:15:31 -0000 On Friday 26 September 2003 12:06 pm, Joe Kelsey wrote: > Brandon Fosdick wrote: > > Joe Kelsey wrote: > >> When I upgraded to fix the OpenSSH problems, the system started > >> hanging at boot time right after the USB/OHCI messages whenever I > >> had devices plugged into the USB ports (mainly a USB mouse). Now, > >> in order to boot, I have to unplug the mouse and wait for the > >> system to pass the USB part of boot before replugging. > > > > There are several threads discussing this ATM. If you have an > > nforce2 board search for the thread with the subject > > "fix/workaround for usb probe lockups on nForce2 mbs". Andrew > > Atrens posted a patch that worked for me. In the same thread Ian > > Dowse has offered a few other ideas to try. I haven't tried them > > yet. > > I have an ASUS A7S333 which does *not* have an nforce2 chipset. > Mine doesn't either and the fact it dies in the boot -s phase of updating the system is a verification of the reason to boot to single user mode. I have tried unplugging the USB devices and it will finish the boot. I won't, however, finish the installworld. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html