> Thanks for that excellent tip. The code in the TS supplied
> __phys_to_virt and virt_to_phys is exactly what I was thinking of.
>
> I tried last night at around 10pm to implement the changes but ended
>up fighting with the "other" virt_to_phys macro. I'll likely get
>another chance at this later on today.
I commented out the other virt_to_phys/phys_to_virt to be safe. I was
able to boot OK with those 2 macros replaced but got the same behavior
as before (the oops from echo m > /proc/sysrq-trigger).
I also tried using the PFN_TO_NID from the 2.4 source but when I tried
that I was unable to boot (forget exactly what the error was at the moment).
> When you tried your changes did you update discontig.c appropriately
> in arch/arm/mm?
I did not make any changes to discontig.c however when I tried the
PFN_TO_NID from 2.4 I changed NODES_SHIFT from 6 down to 4
which would cause MAX_NUMNODES to be 16 (which seems correct
given the hacked PFN_TO_NID code). However as I said that one didn't
boot.
> We're getting close...
Yes we are! I plan on digging into this some more this weekend. I want
to understand exactly what the problem is that causes the oops from
show_mem and also the problem you saw when accessing large amounts
of memory.
If I remember correctly you said if you access more than 48M you got a
panic. Was that one big mmap of 48M or a bunch of little ones? Were
you calling mlock on it?
- Doug
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/
|