From: cgagneraud@techworks.ie (Christian Gagneraud)
To: linux-arm-kernel@lists.infradead.org
Subject: 2.6.32-rc3/sparsemem: kernel BUG at mm/bootmem.c:243
Date: Sat, 10 Oct 2009 16:41:33 +0100 [thread overview]
Message-ID: <4AD0AB2D.9000307@techworks.ie> (raw)
In-Reply-To: <4AD051D1.8060001@gmail.com>
Matthieu Crapet wrote:
> Hi Christian,
>
> It works fine here with my TS-7250. I'll send you asap my "ts72xx rebase
Matthieu,
Has your TS-7250 64MB? Are you using sparsemem or flatmem?
7250: 1x32MB at 0x00000000, using flatmem or sparsemem, always OK
7260: 1x32MB at 0x00000000, 32MB at 0xe0000000, using sparsemem, not OK
anymore (was OK with 2.6.32-rc2)
Hartley: 1x64MB at 0x00000000, using flatmem, OK
Btw Hartley, which board are you using for testing?
I'll check again the meminfo with 2.6.32-rc3, I did it for 2.6.32-rc2
and it showed 8 nodes of 8MB, each at the expected base addresse, as I
didn't change my bootloader I should still get the same result, let's see.
Regards,
Chris
prev parent reply other threads:[~2009-10-10 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 23:16 2.6.32-rc3/sparsemem: kernel BUG at mm/bootmem.c:243 Christian Gagneraud
2009-10-10 0:38 ` H Hartley Sweeten
2009-10-10 9:20 ` Matthieu Crapet
2009-10-10 15:41 ` Christian Gagneraud [this message]
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=4AD0AB2D.9000307@techworks.ie \
--to=cgagneraud@techworks.ie \
--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).