Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762812AbXEUQgL (ORCPT ); Mon, 21 May 2007 12:36:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756360AbXEUQf4 (ORCPT ); Mon, 21 May 2007 12:35:56 -0400 Received: from terminus.zytor.com ([192.83.249.54]:39766 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756019AbXEUQfz (ORCPT ); Mon, 21 May 2007 12:35:55 -0400 Message-ID: <4651CA63.9030903@zytor.com> Date: Mon, 21 May 2007 09:35:47 -0700 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.0 (X11/20070419) MIME-Version: 1.0 To: young dave CC: Linux Kernel Mailing List Subject: Re: 2.6.22-rc1-mm1 References: <20070515201914.16944e04.akpm@linux-foundation.org> <464DDA40.6010101@zytor.com> <465124EA.1020801@zytor.com> <46512821.9010905@zytor.com> <465138CC.3060605@zytor.com> In-Reply-To: X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 968 Lines: 30 young dave wrote: > Hi, > > kernel booting and stopped in edd.c:read_sector. > > I add debug messages around the two inline assemblly sentence, recompile > kernel, > now strange thing happend, the kernel booting directly, but the printf > messages can't be seen because it's too rapid. > > can we use printk in boot code? Well, it's spelt "printf", but same thing. (Since it doesn't take a logging priority, it seems better to name it printf.) This implies a miscompile somewhere, *or* that your bios stomps on registers that gcc expect preserved, and adding printf's disturbs the register allocation sufficiently. Could you send me the arch/i386/boot/setup.elf file from the original, failed, build? Thanks. -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/