From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754456AbbCLMrr (ORCPT ); Thu, 12 Mar 2015 08:47:47 -0400 Received: from smtp25.mail.ru ([94.100.181.180]:60166 "EHLO smtp25.mail.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753034AbbCLMrp (ORCPT ); Thu, 12 Mar 2015 08:47:45 -0400 Message-ID: <55018AE7.4070207@list.ru> Date: Thu, 12 Mar 2015 15:47:35 +0300 From: Stas Sergeev User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Peter Hurley , Russell King - ARM Linux CC: Catalin Marinas , Linux kernel , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] n_tty: use kmalloc() instead of vmalloc() to avoid crash on armada-xp References: <54FF21BE.2040506@list.ru> <20150310171751.GD13687@e104818-lin.cambridge.arm.com> <54FF2986.6020503@list.ru> <20150310173807.GU8656@n2100.arm.linux.org.uk> <55003569.1010200@list.ru> <20150311124730.GZ8656@n2100.arm.linux.org.uk> <5500502A.5060905@list.ru> <550187A4.8010704@hurleysoftware.com> In-Reply-To: <550187A4.8010704@hurleysoftware.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Spam: Not detected X-Mras: Ok Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 12.03.2015 15:33, Peter Hurley пишет: > On 03/11/2015 10:24 AM, Stas Sergeev wrote: >> However, while testing, I've suddenly got another crash happened >> a bit earlier than the previous one used to happen: (OOM? How??) >> --- >> [ 0.000000] Booting Linux on physical CPU 0x0 >> [ 0.000000] Linux version 4.0.0-rc2-00137-gb672c98-dirty >> (root@host-010-117) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) >> #2 SMP 5 >> [ 0.000000] CPU: ARMv7 Processor [562f5842] revision 2 (ARMv7), >> cr=10c5387d >> [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction >> cache >> [ 0.000000] Machine model: Marvell Armada XP Development Board >> DB-MV784MP-GP >> [ 0.000000] Ignoring memory block 0x100000000 - 0x200000000 > Once you patch your bootloader, you'll want to configure your kernel > for CONFIG_ARM_LPAE=y to enable the high 4GB of memory you have, as > it's being ignored in this config right now (as shown above and in > the oom message below). Hi Peter, thanks for this hint. I actually already tried with lpae, and, except for the missing 256Mb, everything works properly. :)