From owner-freebsd-current@FreeBSD.ORG Tue Feb 23 15:28:59 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 646A71065676 for ; Tue, 23 Feb 2010 15:28:59 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-ew0-f225.google.com (mail-ew0-f225.google.com [209.85.219.225]) by mx1.freebsd.org (Postfix) with ESMTP id EA9DB8FC0C for ; Tue, 23 Feb 2010 15:28:58 +0000 (UTC) Received: by ewy25 with SMTP id 25so106257ewy.13 for ; Tue, 23 Feb 2010 07:28:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=A0m8s6Q08FUAqd0RiXAMQdUKWlyS1e3A/lIsGTKfve4=; b=w0gPweuTVH8acdvr7jLZslbiSkROWlkdBVnEJH2Lxx9gTAPg/SQTaBcBy05AxhkrU5 YcHXgge8jHo4gX2Nhm8+hlaBst8u+jeGVnsyxRml55vyQ6MnZvFseRdy9IwljTP35Ieu R+0i7GkYqSIrH2DJH6YDXNOKpVVUnTgnlY5HY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Af51R5a14Ep2NMPCpLDW2gJT/QczfMPka7JRgVWtbrr7UX9gp08RxhhHpPJgIIiYQn 8vNX5mpXV3eYokcWV61gx53yu8VrRN7akJMhNBOSjUmD25qojK9mVWqYZyTf0bIssGJd BptOieWRV5BUf7cR+ejoAsG7B8GvZItDfuNSQ= MIME-Version: 1.0 Received: by 10.213.97.78 with SMTP id k14mr644234ebn.45.1266938929342; Tue, 23 Feb 2010 07:28:49 -0800 (PST) In-Reply-To: <4B83D821.6000207@icyb.net.ua> References: <747dc8f31002220835g481b0baeqb1d6df32a79b7da2@mail.gmail.com> <747dc8f31002230318v384e0259mcfddbf137c0d5057@mail.gmail.com> <4B83D821.6000207@icyb.net.ua> Date: Tue, 23 Feb 2010 09:28:49 -0600 Message-ID: <179b97fb1002230728l4294916cs6b4b9a18b18f044a@mail.gmail.com> From: Brandon Gooch To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Renato Botelho , Chris Hedley , FreeBSD Current Subject: Re: Can't use USB keyboard during boot menu X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 23 Feb 2010 15:28:59 -0000 On Tue, Feb 23, 2010 at 7:29 AM, Andriy Gapon wrote: > on 23/02/2010 13:18 Renato Botelho said the following: >> On Mon, Feb 22, 2010 at 7:35 PM, Chris Hedley >> wrote: > [snip] >>> Do you have USB legacy support enabled in your BIOS? =A0I'm not sure if >>> there's an option for the loader to use USB devices natively, but the B= IOS's >>> legacy option where it provides AT/PS2 emulation is probably the easies= t way >>> to get the keyboard working. >> >> Yes, I do, but it seems to be a regression on FreeBSD itself, I had this= problem >> in the past and I checked the same things i need to check in the past ag= ain and >> everything is fine. > > A more precise way to state that would be "a regression in FreeBSD boot/l= oader". > I think that you are referring to the issue that was fixed by r189017. > It might be worthwhile investigating what was done in that revision and w= hat > happened in sys/boot code since then. > > One possibility is that your BIOS uses memory above 1MB for USB emulation= , but > doesn't mark that memory as used in system memory map. =A0In that case th= at memory > could be overwritten by the loader. =A0If that's true then the blame is o= n the BIOS. > =A0Alternatively, our code might be parsing the system memory map incorre= ctly. > But I am just making wild guesses here. > I don't know if it is at all related, but this commit has caused problems for me booting at least one of my machines: http://svn.freebsd.org/viewvc/base/head/sys/boot/i386/zfsboot/zfsboot.c?r1= =3D199714&r2=3D200309 Commit message: Revision 200309 - (view) (annotate) - [select for diffs] Modified Wed Dec 9 20:36:56 2009 UTC (2 months, 2 weeks ago) by jhb File length: 24893 byte(s) Diff to previous 199714 - Port bios_getmem() from libi386 to {gpt,}zfsboot() and use it to safely allocate a heap region above 1MB. This enables {gpt,}zfsboot() to allocate much larger buffers than before. - Use a larger buffer (1MB instead of 128K) for temporary ZFS buffers. Thi= s allows more reliable reading of compressed files in a raidz/raidz2 pool. Submitted by: Matt Reimer mattjreimer of gmail MFC after: 1 week Renato, are you booting ZFS? -Brandon