From mboxrd@z Thu Jan 1 00:00:00 1970 From: Romain Goyet Subject: Problem in arch/arm/mm between 2.6.13-rc1 and 2.6.15-rc2 Date: Fri, 2 Dec 2005 14:08:30 +0100 Message-ID: <8028e5750512020508g68c5fe5fl@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-omap-open-source-bounces@linux.omap.com Errors-To: linux-omap-open-source-bounces@linux.omap.com To: linux-omap-open-source@linux.omap.com List-Id: linux-omap@vger.kernel.org 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