From owner-freebsd-current@FreeBSD.ORG Mon Jun 9 20:37:03 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7ED6481A for ; Mon, 9 Jun 2014 20:37:03 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3CCF62FCF for ; Mon, 9 Jun 2014 20:37:02 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id AC6921FE026; Mon, 9 Jun 2014 22:36:55 +0200 (CEST) Message-ID: <53961B06.4070909@selasky.org> Date: Mon, 09 Jun 2014 22:37:26 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Steve Kargl , freebsd-current@freebsd.org Subject: Re: ohci bricks a amd64 system References: <20140609203354.GA987@troutmask.apl.washington.edu> In-Reply-To: <20140609203354.GA987@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2014 20:37:03 -0000 On 06/09/14 22:34, Steve Kargl wrote: > I updated my FreeBSD-current system from an > April 9th kernel/world (r264280M, which was > running fine) to today sources (r267284), and > have successfully turned the system into a brick > if I include the USB ohci device in my kernel. > During the verbose boot process, the brick stops > with the message > > ohci early: SMM active, request owner change > > At this point, one must hit the reset button > as there is no keyboard, yet. If I remove the > ohci device from the kernel config file, the > resulting kernel boots but the usb mouse is > no longer available. > > Any pointers on how to debug/fix the ohci device > is appreciated. > Check USB BIOS settings. Thank you! --HPS