From owner-freebsd-current@FreeBSD.ORG Tue May 31 20:50:22 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 7C601106564A; Tue, 31 May 2011 20:50:22 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: Xin LI Date: Tue, 31 May 2011 16:50:14 -0400 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201105311650.16164.jkim@FreeBSD.org> Cc: "George V. Neville-Neil" , freebsd-current@freebsd.org, Johannes Dieterich Subject: Re: Boot halts on Thinkpad X220 (Sandy Bridge) 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, 31 May 2011 20:50:22 -0000 On Friday 27 May 2011 01:14 pm, Xin LI wrote: > On Thu, May 19, 2011 at 5:18 AM, Johannes Dieterich > > wrote: > > On Wed, May 18, 2011 at 7:40 PM, Xin LI wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA256 > >> > >> Try this patch? > > > > The attached patch makes 9-CURRENT-amd64 boot on the X220 w/o any > > hints or BIOS fixes needed. Thanks a lot! :-) > > > >> (I'm still opted to disable the typematic rate detection by > >> default at least for amd64, as we don't do it in the past for > >> amd64) > > > > What does this mean concerning getting the fix into CURRENT? > > Well, that's not a perfect fix and we do lose the ability of > detecting typematic rate (by default), so technically it's a > workaround (sufficient to make the kernel boot and work, though) > and doesn't fix anything. > > I have committed it anyway since we do not have better fix (yet), > and have updated atkbd(4) manual page so one can enable it again > when wanted. > > The problem we had was that it seems that running the BIOS in the > x86emu emulator on amd64 would cause problem. This doesn't seem to > be fixable without hands-on experiments on a system in question, > it's either a BIOS bug or an emulator bug. The strange part of the > problem is that the functionality is quite common in the Good Old > Days (TM). I got BIOS dump from gnn last week. I've been scratching my head cause it should just fail and exit gracefully unless I am totally missing something. :-( Are you guys sure that INT 15h is causing hangs? Maybe INT 16h is the real culprit (which is more probable, BTW)? Jung-uk Kim