Date: Tue, 29 Mar 2005 23:21:10 -0800
From: Eugene Surovegin <ebs@ebshome.net>
To: Ara Avanesyan <araav@hylink.am>
Cc: linux-kernel@vger.kernel.org, avila@lists.unixstudios.net
Subject: Re: Strange memory problem with Linux booted from U-Boot
Message-ID: <20050330072110.GA7027@gate.ebshome.net>
Mail-Followup-To: Ara Avanesyan <araav@hylink.am>,
	linux-kernel@vger.kernel.org, avila@lists.unixstudios.net
References: <006b01c5047e$1efc78a0$1000000a@araavanesyan> <20050127144441.GB4848@home.fluff.org> <00ae01c533a6$85ddf1f0$1000000a@araavanesyan>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <00ae01c533a6$85ddf1f0$1000000a@araavanesyan>
User-Agent: Mutt/1.5.5.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1201
Lines: 30

On Mon, Mar 28, 2005 at 07:57:52PM +0500, Ara Avanesyan wrote:
> Hi,
> 
> I need some help on solving this strange problem.
> Here is what I have,
> I have a loadable module (linux.2.4.20) which contains a 2 mb static gloabal
> array.
> When I load it from linux booted via U-Boot the system crashes.
> Everything works ok if I do the same thing with the same linux booted with
> RedBoot.

As usual for such problems, check how different firmware configure 
memory controller, etc. Get dump of relevant chip registers under 
U-Boot and RedBoot and compare them.

Other possible problem area can be firmware -> kernel interface. I'm 
not familiar with that particular chip and RedBoot, but it's not 
uncommon for different firmware to have different conventions for the 
environment in which kernel starts execution.

I'd recommend posting to the specific mail-lists, lkml doesn't seem 
a good place for embedded and firmware related questions :)

--
Eugene
-
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/