From: ryan@bluewatersys.com (Ryan Mallon)
To: linux-arm-kernel@lists.infradead.org
Subject: ts72xx: rc4 doesn't boot anymore
Date: Wed, 14 Oct 2009 13:02:35 +1300 [thread overview]
Message-ID: <4AD5151B.30300@bluewatersys.com> (raw)
In-Reply-To: <4AD5121D.4070309@techworks.ie>
Christian Gagneraud wrote:
> Hi all,
>
> I really don't understand what's happenning, nothing has changed on my
> side (same board, same bootloader), rc2 was booting OK, rc3 didn't boot
> unless I pass on the command line the config for half of my memory
> (mem=8M at 0x0 mem=8M at 16M mem=8M at 64M mem=8M at 80M). Now with rc4 it's even
> worth, the kernel complains about bad configuration page, detects 16MB
> of memory and ignore any mem= command line params (this board has 8
> nodes of 8MB each).
>
> Below is the trace of the crash, I've added some debug printk,
> especially concerning the atags (attached is my hack of
> arch/arm/kernel/setup.c and another patch i need to get the board
> booting (I know it's bad))
>
> Unless I'm missing something, the rc2 was booting OK, I'm sure.
>
> Any help greatly appreciate.
>
Can you do a bisect between rc4 and rc2 (or rc3 with the command line
arguments you gave) to see if you can track down a specific commit which
is breaking your setup.
Thanks,
~Ryan
--
Bluewater Systems Ltd - ARM Technology Solution Centre
Ryan Mallon 5 Amuri Park, 404 Barbadoes St
ryan at bluewatersys.com PO Box 13 889, Christchurch 8013
http://www.bluewatersys.com New Zealand
Phone: +64 3 3779127 Freecall: Australia 1800 148 751
Fax: +64 3 3779135 USA 1800 261 2934
next prev parent reply other threads:[~2009-10-14 0:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 23:49 ts72xx: rc4 doesn't boot anymore Christian Gagneraud
2009-10-14 0:02 ` Ryan Mallon [this message]
2009-10-14 0:51 ` H Hartley Sweeten
2009-10-14 19:45 ` Christian Gagneraud
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AD5151B.30300@bluewatersys.com \
--to=ryan@bluewatersys.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).