Skip to contentSkip to conversation

Problem in arch/arm/mm between 2.6.13-rc1 and 2.6.15-rc2

DISCUSSION Romain Goyet 2 participants 2 messages Dec 2, 2005 – Dec 8, 2005

lore
Share & tools
lore
#0 lore raw

Hello everybody,
I'm still porting Linux to the Palm Tungsten E , and it happened that
Linux stopped working when I upgraded from 2.6.13 to 2.6.15-rc2.
My biggest problem is that this board has _no_ UART nor JTAG, so
it's _very_ difficult to debug. I managed to find out that the kernel crashes in paging_init, but I couldn't find out why.
Could you give me any suggestions ? In particular, I would like to
know what changed in arch/arm/mm between 2.6.13 and 2.6.15, since 2.6.13 was working like a charm.
What's rather weird is that it sounds to be working OK on other
OMAP1510 devices. As the Tungsten E uses an OMAP310 which defines IS_OMAP_15XX, I don't really understand why it doesn't work as well on the OMAP310.

Kind regards,

Romain Goyet

#1 lore raw

Hi Romain

Quoted 5 lines

I managed to find out that the kernel
crashes in paging_init, but I couldn't find out why.
Could you give me any suggestions ? In particular, I would like to
know what changed in arch/arm/mm between 2.6.13 and 2.6.15, since 2.6.13 was working like a charm.

You can see the changes made in arch/arm/mm/init.c in the git history at
http://source.mvista.com/git/gitweb.cgi?p=linux-omap-2.6.git;a=history;f=arch/arm/mm/init.c

Maybe you can try older versions to isolate the date of the patch...

Best Regards
Kristian