On Fri, Jan 14, 2011 at 11:12 AM, Bryan Wu <bryan.wu@xxxxxxxxxxxxx> wrote: > > On Fri, Jan 14, 2011 at 4:12 PM, Santosh Shilimkar > <santosh.shilimkar@xxxxxx> wrote: > > Bryan, > >> -----Original Message----- > >> From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- > >> owner@xxxxxxxxxxxxxxx] On Behalf Of Bryan Wu > >> Sent: Tuesday, January 11, 2011 10:22 PM > >> To: linux-omap@xxxxxxxxxxxxxxx; Ricardo Salveti de Araujo > >> Subject: Passing mem=1G to kernel on Panda, system is unstable. > >> > >> Hi folks, > >> > >> We are trying to build kernel package or GCC natively on OMAP4 panda > >> board. With the mainline 2.6.37 kernel or Ubuntu Natty 2.6.35 based > >> kernel, we met same instabilities on the system when we try to use > >> mem=1G on the board. > >> > >> Please find our bug tracker here: > >> https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/633227 > >> and I think another bug is also related: > >> https://bugs.launchpad.net/ubuntu/+source/linux-ti- > >> omap4/+bug/690370. > >> System will freeze at all when building GCC natively on Panda. > >> > >> Did any folks meet this issue? or we need more simple test case to > >> catch the root cause of this issue. > >> > > Haven't seen this issue on my SDP with 2.6.37. > Do you have Panda for testing? I don't have SDP. Maybe Sebastien can > help to verify on SDP. I reproduced the issue on my Blaze board, confirming that this issue is not specific to panda. > > Have you enabled HIGHMEM, when tried mem = 1G on 2.6.37 ? > > > > Yeah, CONFIG_HIGHMEM=y for this mainline testing. Please use this > kernel config file: > http://launchpadlibrarian.net/62061659/mainline_config So far, I have not been able to reproduce the issue with CONFIG_HIGHMEM option deactivated (I am cleaning/building kernels for more than 24 hours now), and mem=1G. I will keep my test run, but it seems that deactivating highmem at least hides the issue. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
