From owner-freebsd-current Wed Jul 18 22: 3:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from white.dogwood.com (white.dogwood.com [63.96.228.130]) by hub.freebsd.org (Postfix) with ESMTP id 7645737B405 for ; Wed, 18 Jul 2001 22:03:04 -0700 (PDT) (envelope-from dave@dogwood.com) Received: (from dave@localhost) by white.dogwood.com (8.11.4/8.11.3) id f6J531625072; Wed, 18 Jul 2001 22:03:01 -0700 (PDT) (envelope-from dave) From: Dave Cornejo Message-Id: <200107190503.f6J531625072@white.dogwood.com> Subject: Re: more on supermicro 6010H hang In-Reply-To: <200107181948.f6IJm6b23161@vashon.polstra.com> "from John Polstra at Jul 18, 2001 12:48:06 pm" To: John Polstra Date: Wed, 18 Jul 2001 22:03:01 -0700 (PDT) Cc: current@freebsd.org, dave@dogwood.com X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Well, damn. I've run it through a couple of reboots with a fresh current SMP kernel and it boots like a champ... Where were you a couple of weeks ago when I started trying to solve this problem? ;-) At least I learned a lot about debugging kernels... thanks for your guess! dave c > This is probably not it, but it's worth a peek. Check your BIOS > settings and see if there's one that controls whether the USB > interrupt is enabled. Make sure that this interrupt is enabled. If > it's not, I know you can get hangs at exactly the point where the > "Waiting 15 seconds.." message comes out. -- Dave Cornejo @ Dogwood Media, Fremont, California (also dcornejo@ieee.org) "There aren't any monkeys chasing us..." - Xochi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message