From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932522Ab0CNMAK (ORCPT ); Sun, 14 Mar 2010 08:00:10 -0400 Received: from caramon.arm.linux.org.uk ([78.32.30.218]:58844 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757872Ab0CNMAB (ORCPT ); Sun, 14 Mar 2010 08:00:01 -0400 Date: Sat, 13 Mar 2010 15:06:51 +0000 From: Russell King - ARM Linux To: Marek Vasut Cc: linux-arm-kernel@lists.infradead.org, Daniel Walker , Iliyan Malchev , Brian Swetland , kernel list , Arve Hj?nnev?g , Pavel Machek Subject: Re: scary warning in atags.c -- 2.6.34-rc1 Message-ID: <20100313150651.GB4627@n2100.arm.linux.org.uk> References: <20100313103913.GA9812@elf.ucw.cz> <201003131415.00156.marek.vasut@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201003131415.00156.marek.vasut@gmail.com> User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Mar 13, 2010 at 02:15:00PM +0100, Marek Vasut wrote: > Dne So 13. března 2010 11:39:13 Pavel Machek napsal(a): > > Hi! > > > > Scary warning on HTC Dream: > > > > [ 0.220000] ------------[ cut here ]------------ > > [ 0.220000] WARNING: at arch/arm/kernel/atags.c:60 > > init_atags_procfs+0x5c/0xe8() > > [ 0.220000] Modules linked in: > > [ 0.220000] [] (unwind_backtrace+0x0/0xdc) from > > [] (warn_slowp) > > [ 0.220000] [] (warn_slowpath_common+0x4c/0x80) from > > [] (init_) > > [ 0.220000] [] (init_atags_procfs+0x5c/0xe8) from > > [] (do_one_i) > > [ 0.220000] [] (do_one_initcall+0x5c/0x1bc) from > > [] (kernel_in) > > [ 0.220000] [] (kernel_init+0x94/0x148) from [] > > (kernel_thread) > > [ 0.220000] ---[ end trace 1b75b31a2719ed1c ]--- > > [ 0.230000] bio: create slab at 0 > > [ 0.230000] Switching to clocksource dg_timer > > > > Hmm, what are atags anyway? > > Pavel > > > Atags are data passed by the bootloader to kernel (like memory size, > machine id ...). Your bootloader is broken - it doesn't terminate the ATAG list correctly. You'd have thought that getting two values correct would be simple...