--- In Joe Bouchard <> wrote:
>
> On Fri, Dec 22, 2006 at 07:12:00PM -0000, charliem_1216 wrote:
> > Hi Folks,
> >
> > I've been working to get a 2.6 kernel up on my TS-7250, and I'm
> > running into a problem with RedBoot. While TS-BOOTROM finds all of
> > the 64MB ram, RedBoot finds only 32M. This is the original RedBoot
> > shipped with the board June-06.
> >
> > The 2.4 TS kernels are able to work around this and find all 64M, due
> > to the 2.4 TS kernel mods, it doesn't work with 2.6 kernels (at least
> > up to 2.6.19). I believe that RedBoot doesn't completely (or
> > correctly?) fill up the ATAG_MEM structure that get passed to the
> > kernel for booting.
>
> This may not be at all relevant, but it reminds me of a case where I
built my
> own kernel for my TS-7200 and it only saw 8MB instead of 32MB. Eddie
> immediately knew what the problem was... My memory is foggy, but I
think when I
> had built my cross compiler I had used too new a version of glibc,
and this
> affected the way the kernel interacted with redboot. Rather than
downgrade my
> compiler/kernel I think the fix was he sent me a new version of
redboot which I dd'ed
> into place, and everything was fine.
Looks like RedBoot is off the hook as a cause, but 2.6 kernels seem to
be broken with the 8-memory-bank 64M TS_7250 machines. Adding a
printascii (per Lennert's local patch), and a printk in
parse_tag_mem32 shows the right 8-node atag_mem32 stuff being passed OK:
RedBoot> load -v -r -b 0x218000 -h 192.168.2.1 -m http /~ccm/zImage
-
Raw file loaded 0x00218000-0x00357393, assumed entry at 0x00218000
RedBoot> exec -c "console=ttyAM0,115200 root=/dev/nfs
nfsroot=192.168.2.1:/home/ts7200 ip=192.168.2.30"
Using base address 0x00218000 and length 0x0013f394
Uncompressing
Linux...................................................................................
done, booting the kernel.
<5>Linux version 2.6.19 (gcc version 4.1.1
(CodeSourcery ARM Sourcery G++ 2006q3-26)) #11 Tue Dec 26 22:01:35 EST
2006
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=00007177
Machine: Technologic Systems TS-72xx SBC
<4>Parse_tag_mem32: adding memory bank 0x00000000 size 8192KB
<4>Parse_tag_mem32: adding memory bank 0x01000000 size 8192KB
<4>Parse_tag_mem32: adding memory bank 0x04000000 size 8192KB
<4>Parse_tag_mem32: adding memory bank 0x05000000 size 8192KB
<4>Parse_tag_mem32: adding memory bank 0xe0000000 size 8192KB
<4>Parse_tag_mem32: adding memory bank 0xe1000000 size 8192KB
<4>Parse_tag_mem32: adding memory bank 0xe4000000 size 8192KB
<4>Parse_tag_mem32: adding memory bank 0xe5000000 size 8192KB
Memory policy: ECC disabled, Data cache writeback
<4>BUG: not creating mapping for 0xe0000000 at 0xa0000000 in user region
<4>BUG: not creating mapping for 0xe1000000 at 0xa1000000 in user region
<4>BUG: not creating mapping for 0xe4000000 at 0xa4000000 in user region
<4>BUG: not creating mapping for 0xe5000000 at 0xa5000000 in user region
<7>On node 0 totalpages: 16384
<1>bootmem alloc of 30081024 bytes failed!
<0>Kernel panic - not syncing: Out of memory
Back in April, Mike Taht had the same results with a 64M TS7250, and
Lennert suggested changing PHYS_OFFSET to 0xe0000000 (from 0x0):
http://tech.groups.yahoo.com/group/ts-7000/message/2681
When I make that change, my kenel just hangs after the "uncompressing
linux ... ... booting the kernel" message.
Just to clarify, I can use 32M fine, but only if I add the first (4)
banks of memory on the command line. If I add any one of the higher
banks (starting at 0xe...) then I get the hard hang.
I've about exhausted my debugging skills, and I'll be grateful for any
suggestions for further debugging 64M on TS-7250 with 2.6 kernels.
Thanks ........ Charlie
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|