From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 16:03:12 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64C18106569F; Mon, 27 Oct 2008 16:03:12 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 7A1678FC20; Mon, 27 Oct 2008 16:03:11 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.3/8.14.3) with ESMTP id m9RG2Y1d012952; Mon, 27 Oct 2008 12:03:02 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Jeremy Chadwick Date: Mon, 27 Oct 2008 11:57:05 -0400 User-Agent: KMail/1.9.7 References: <20081025014218.GA47549@phat.za.net> <20081025080945.GA55413@icarus.home.lan> In-Reply-To: <20081025080945.GA55413@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200810271157.06096.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Mon, 27 Oct 2008 12:03:04 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/8508/Mon Oct 27 09:02:44 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Jo Rhett , Aragon Gouveia , freebsd-stable Stable Subject: Re: 6.4 RC1 locks up solid on first reboot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2008 16:03:12 -0000 On Saturday 25 October 2008 04:09:45 am Jeremy Chadwick wrote: > Just for posterity: the USB Legacy Support BIOS option does not affect > natively-connected PS/2 keyboards; you can leave the option enabled even > in the scenario where you have a USB keyboard *and* a PS/2 keyboard > plugged in; one will not "trump" the other. Instead, you should have > two keyboards which function in OSes/environments which lack a USB > stack. (That is, until something resets/reassigns the BIOS-controlled > interrupt, which will then break USB->PS/2 emulation; the native PS/2 > keyboard should not be affected by this) This last statement is not quite true (at least not always true). For many systems, the way the PS/2 emulation works is that accesses to the backing I/O ports (0x60 and 0x64) case a trap into SMM and the SMI handler in the BIOS then talks to the USB controller and keyboard and updates the register values to simulate the I/O port accesses. This is disabled by having the USB host controller driver frob flags in controller registers to disable the SMI traps. -- John Baldwin