> -----Original Message----- > From: Russell King - ARM Linux [mailto:li...@arm.linux.org.uk] > Sent: Wednesday, March 18, 2009 9:25 PM > To: Kamat, Nishant > Cc: linux-arm-ker...@lists.arm.linux.org.uk; Menon, Nishanth; linux- > o...@vger.kernel.org; Ramirez Luna, Omar; Kanigeri, Hari; Guzman Lugo, > Fernando; Kevin Hilman; 2am...@gmail.com > Subject: Re: dma_alloc_coherent fragmentation
> Make sure you're up to date with fixes to the ioremap code, specifically > 24f11ec001920f1cfaeeed8e8b55725d900bbb56. This is not in 2.6.28, > 2.6.29-rc1, 2.6.29-rc2, but is in -rc3 and later. 2.6.29 itself hasn't > been released yet so I don't know what "seems to happen on 2.6.28 and > 2.6.29" actually means because its nonsense. Apologies on the confusion. For this issue, the pertinent tree would be the master branch of [1] linux-omap tree which is synced to 2.6.29-rc8. And yes, the mentioned commit ID is part of the git log. Relevant test code and report of the crash is in [2]. Additional observation in [3] Regards, Nishanth Menon Ref: [1] http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git [2] http://marc.info/?l=linux-omap&m=123719772811746&w=2 [3] http://marc.info/?l=linux-omap&m=123722460022336&w=2 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
