Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762996AbXHaGmG (ORCPT ); Fri, 31 Aug 2007 02:42:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758513AbXHaGly (ORCPT ); Fri, 31 Aug 2007 02:41:54 -0400 Received: from terminus.zytor.com ([198.137.202.10]:37857 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752929AbXHaGly (ORCPT ); Fri, 31 Aug 2007 02:41:54 -0400 Message-ID: <46D7B817.3060304@zytor.com> Date: Thu, 30 Aug 2007 23:41:27 -0700 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.5 (X11/20070719) MIME-Version: 1.0 To: Will Simoneau CC: linux-kernel@vger.kernel.org Subject: Re: new x86 setup code hangs on Dell Inspiron 5150 References: <20070831015620.GA6259@ele.uri.edu> <46D7AAF7.1030105@zytor.com> In-Reply-To: <46D7AAF7.1030105@zytor.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1148 Lines: 29 H. Peter Anvin wrote: > Will Simoneau wrote: >> While trying to put together a new kernel for my laptop (Dell I5150, as >> in subject) I found that recent kernels just don't boot. Right after >> grub loads the kernel, before the "Uncompressing Linux" message is >> shown, it hangs. The BIOS appears to still be alive (ctrl-alt-del works, >> keyboard lock LEDs respond). It seems to be caused by the new x86 setup >> code. >> >> My kernel is Linus' git as of a1c582d0720f2eff61043e90711767decf37b917. >> I bisected and confirmed that 4fd06960f120e02e9abc802a09f9511c400042a5 >> triggers a non-functioning boot. >> >> This system has Dell BIOS rev A38 and a P4 3.2 w/HT. >> >> What should I do next to debug this problem? > > Can you put in some printf's in the code and see how far it gets? > Specifically, the places to add printf's are to main() in main.c and go_to_protected_mode() in pm.c. -hpa - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/