From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Hzfi5-0004s5-Rm for qemu-devel@nongnu.org; Sat, 16 Jun 2007 17:21:29 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Hzfi3-0004rh-Nq for qemu-devel@nongnu.org; Sat, 16 Jun 2007 17:21:28 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hzfi3-0004re-EN for qemu-devel@nongnu.org; Sat, 16 Jun 2007 17:21:27 -0400 Received: from moutng.kundenserver.de ([212.227.126.177]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Hzfi2-00054t-VO for qemu-devel@nongnu.org; Sat, 16 Jun 2007 17:21:27 -0400 Message-ID: <46745455.7000305@mail.berlios.de> Date: Sat, 16 Jun 2007 23:21:25 +0200 From: Stefan Weil MIME-Version: 1.0 Subject: Re: [Qemu-devel] 2.6.21 kernel on emulated/real Malta board References: <20070616204834.GA610@farad.aurel32.net> In-Reply-To: <20070616204834.GA610@farad.aurel32.net> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hi, 2.6.21 with patches from OpenWrt works for AR7 with CONFIG_EARLY_PRINTK and real hardware or QEMU emulation. Maybe I can compare it to Malta tomorrow. Perhaps some environment settings are missing for early printk and result in a crash... Stefan Aurelien Jarno schrieb: > Hi all, > > Since I switch to 2.6.21 kernel on my emulated Malta board (QEMU), I > have noticed something strange. The kernel starts to boot up to the > timer calibration, and then it restart the boot again. A small example: > > ... > > I have traced the problem down to the CONFIG_EARLY_PRINTK option. > Disabling it in the .config file (be aware that running make *config > will reenable this function), removes the problem. > > The problem occurs for kernel 2.6.21 from both linux-mips.org and > kernel.org, on both endianness, and for both 32- and 64-bit kernels. > > It would be nice if somebody could tell me if the real board (I don't > own one) suffers from the same problem or not, so that I can look for a > possible bug in QEMU. > > Thanks, > Aurelien >