From: stsp@list.ru (Stas Sergeev)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] n_tty: use kmalloc() instead of vmalloc() to avoid crash on armada-xp
Date: Wed, 11 Mar 2015 18:22:42 +0300 [thread overview]
Message-ID: <55005DC2.1060300@list.ru> (raw)
In-Reply-To: <55005B81.9020103@free-electrons.com>
11.03.2015 18:13, Gregory CLEMENT ?????:
> On 11/03/2015 16:01, Stas Sergeev wrote:
>> 11.03.2015 16:14, Russell King - ARM Linux ?????:
>>> On Wed, Mar 11, 2015 at 01:44:57PM +0100, Gregory CLEMENT wrote:
>>>> Hi Stas,
>>>>
>>>> On 10/03/2015 17:54, Stas Sergeev wrote:
>>>>> Hello, the patch below is needed for a successful boot on armada-xp.
>>>>>
>>>> I am really surprised by this patch because I used the Armada XP based
>>>> board in a daily base and I never saw this issue.
>>> Can you provide some details about your board - does it have 8GB of
>>> memory, ranging from 0-0xf0000000, and 4G-8G ?
>> I wonder about this 256Mb memory hole.
> This is where the SoC registers are.
OK but it seems I am loosing this region of _physical_ memory:
---
[ 0.000000] memory size = 0x1f0000000
[ 0.000000] memory.cnt = 0x2
[ 0.000000] memory[0x0] [0x00000000000000-0x000000efffffff],
0xf0000000 bytes
[ 0.000000] memory[0x1] [0x00000100000000-0x000001ffffffff],
0x100000000 bytes
---
As you can see, memory size is 0x1f0000000 instead of 0x20000000.
Why 256Mb are lost?
next prev parent reply other threads:[~2015-03-11 15:22 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 16:54 [PATCH] n_tty: use kmalloc() instead of vmalloc() to avoid crash on armada-xp Stas Sergeev
2015-03-10 17:17 ` Catalin Marinas
2015-03-10 17:27 ` Stas Sergeev
2015-03-10 17:38 ` Russell King - ARM Linux
2015-03-10 18:31 ` Stas Sergeev
2015-03-10 18:54 ` Russell King - ARM Linux
2015-03-11 12:30 ` Stas Sergeev
2015-03-11 12:47 ` Russell King - ARM Linux
2015-03-11 14:24 ` Stas Sergeev
2015-03-11 16:30 ` Peter Hurley
2015-03-11 16:39 ` Stas Sergeev
2015-03-12 12:33 ` Peter Hurley
2015-03-12 12:47 ` Stas Sergeev
2015-03-12 13:04 ` Russell King - ARM Linux
2015-03-12 13:11 ` Stas Sergeev
2015-03-12 15:34 ` Vladimir Murzin
2015-03-12 12:59 ` Russell King - ARM Linux
2015-03-10 17:29 ` Russell King - ARM Linux
2015-03-10 17:35 ` Peter Hurley
2015-03-10 17:51 ` Stas Sergeev
2015-03-10 18:45 ` Peter Hurley
2015-03-11 12:44 ` Gregory CLEMENT
2015-03-11 12:57 ` Stas Sergeev
2015-03-11 13:14 ` Russell King - ARM Linux
2015-03-11 14:33 ` Stas Sergeev
2015-03-11 15:01 ` Stas Sergeev
2015-03-11 15:13 ` Gregory CLEMENT
2015-03-11 15:22 ` Stas Sergeev [this message]
2015-03-12 13:06 ` Russell King - ARM Linux
2015-03-11 16:52 ` Thomas Petazzoni
2015-03-11 17:26 ` Stas Sergeev
2015-03-11 17:46 ` Russell King - ARM Linux
2015-03-11 17:56 ` Stas Sergeev
2015-03-11 18:11 ` Thomas Petazzoni
2015-03-11 18:38 ` Stas Sergeev
2015-03-11 18:41 ` Russell King - ARM Linux
2015-03-11 18:08 ` Stas Sergeev
2015-03-11 18:33 ` Thomas Petazzoni
2015-03-12 12:44 ` Stas Sergeev
2015-03-12 12:47 ` Thomas Petazzoni
2015-03-12 13:03 ` Stas Sergeev
2015-03-12 13:12 ` Russell King - ARM Linux
2015-03-12 13:16 ` Stas Sergeev
2015-03-12 13:55 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55005DC2.1060300@list.ru \
--to=stsp@list.ru \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).